Hello, I’m currently trying to use an **OAK-4-D-FF (RVC4)** camera and I’m stuck with device discovery on Linux. ### **Hardware / Device** * Model: **OAK-4-D-FF** * Board: **3525B1** * Serial: **4DFF-T2536-0034** --- ### **Working Environment (Windows)** * OS: **Windows 11** * `oakctl list` detects the camera immediately * **OAK Viewer works normally** * Camera info shown by `oakctl list` on Windows: * OS version: **1.18.3 (debug)** * IP address: **192.168.137.114** No manual network configuration was required on Windows (just Ethernet connection). --- ### **Non-Working Environments (Linux)** I tested on multiple Linux systems: * **Ubuntu 20.04 on Jetson** * **Ubuntu 20.04 on Neousys POC-545** In all cases: * `oakctl list` does **not** detect the camera * `oakctl discover` also finds nothing * `depthai` Python examples fail (no device detected) * `depthai-core/device_manager.py` does **not** detect the RVC4 device at all --- ### **Network Configuration Attempts** Since the camera IP is known from Windows, I tried manual network setups on Ubuntu: 1. Static IP matching Windows ICS subnet: $$ 192.168.137.1 / 255.255.255.0 $$ 2. Alternative private network: $$ 169.254.1.1 / 255.255.0.0 $$ In both cases: * The camera is **not detected** * `oakctl list` still returns nothing * Even with correct subnet alignment, discovery fails --- ### **Additional Tests / Limitations** * I tried connecting the device via **Luxonis Hub** on Ubuntu * `oakctl setup` cannot be used (device is not discovered) * `oak-viewer` is unavailable (Ubuntu 22.04+ only) * Since the device cannot be discovered, **I cannot retrieve or configure the IP from Linux** * I confirmed that **Luxonis software / firmware updates cannot be applied** (see attached image) [upl-image-preview uuid=fb097f3c-0558-4fb2-a8b0-1c2f44051cf8 url=https://discuss.luxonis.com/assets/files/2026-01-29/1769673444-151658-image.png alt={TEXT?}] --- ### **Background / Experience** I have extensive experience with **RVC2-based OAK cameras**: * I regularly configure devices via `device_manager` * Setting static IPs and handling network-based OAK devices is familiar territory for me * RVC2 devices work as expected in similar Linux environments However, **RVC4 behaves very differently**, and I cannot even reach the point where the device becomes visible on Linux. --- ### **Main Questions** 1. Is there a **supported way to use OAK-4-D-FF (RVC4) on Ubuntu 20.04**? 2. Is there a **known issue with RVC4 discovery on Linux** (oakctl / depthai)? 3. How can I **retrieve or assign the camera IP from Linux** if discovery does not work? 4. Are there **additional services, ports, or discovery mechanisms** required for RVC4 that differ from RVC2? Any guidance or confirmation would be greatly appreciated. At the moment, the device is fully usable on Windows but completely inaccessible on Linux. Thank you.

Hey @"shAhn"#p32928 - firstly I would suggest updating the camera to the newest OS. The error you got is because the camera needs to have access to the internet to perform the update the way you wanted to do it. So either connect internet to it or do the update from Host [Option 2](https://docs.luxonis.com/software-v3/sw-stack/luxonis-os/). For linux can you completely remove the oakctl and reinstall it again. You can try running with sudo also. Also you can directly connect to camera with `oakctl connect 192.168.137.114`. One more question, how are you connecting to the camera? Are you on same subnet? Is connection with windows same as with Linux devices you tried? Thanks, Oskar

@"OskarSonc"#p32931 Hi Oskar, Thank you for the clarification. I’d like to provide a bit more detail from my side. First, on Linux the camera is **not detected at all** by `oakctl list`. Therefore, **all attempts using the `oakctl` commands mentioned below were performed on Windows**, where the device is at least visible. 1. **OS update issue (even with internet access)** Even when the camera is connected to the internet, `oakctl device update` does not work. I checked the changelog page below: For all changelog entries, the linked ZIP files **cannot be downloaded manually** (the page returns “Bad Page…”, see attached screenshot). [upl-image-preview uuid=14045883-c3fc-40d3-bfe3-2aef02566087 url=https://discuss.luxonis.com/assets/files/2026-01-30/1769736517-638056-image.png alt={TEXT?}] Because of this, it does not appear to be a local network issue on my side. It seems that the **download server may not be functioning correctly**. Could you please check whether these OS package links are currently valid? 2. **SSH access issue** I tried to access the device via: $$ ssh root@ $$ However, I was prompted for a password, even though I never configured one. According to the documentation: > By default, SSH access via password is disabled on devices running OS version 1.18 and newer. I therefore tried: * `oakctl device unlock` * `oakctl start-setup` But both workflows eventually require an **OS update** to proceed further. [upl-image-preview uuid=bd5fe937-4c74-45e8-9798-79889a28ac2f url=https://discuss.luxonis.com/assets/files/2026-01-30/1769736555-264575-image.png alt={TEXT?}] Since the OS update itself is currently failing (likely due to the server issue mentioned above), I am blocked at this step as well. At the moment, the inability to update the OS (either online or via manual ZIP download) seems to be the main blocker. I would appreciate it if you could confirm whether there is an issue with the OS download server or provide an alternative way to obtain the update packages. Thank you for your help.

OAK-4-D-FF detected on Windows but not on Ubuntu (oakctl / depthai / RVC4 issue)

shAhn

Hello,

I’m currently trying to use an OAK-4-D-FF (RVC4) camera and I’m stuck with device discovery on Linux.

Hardware / Device

Model: OAK-4-D-FF
Board: 3525B1
Serial: 4DFF-T2536-0034

Working Environment (Windows)

OS: Windows 11
oakctl list detects the camera immediately
OAK Viewer works normally
Camera info shown by oakctl list on Windows:
- OS version: 1.18.3 (debug)
- IP address: 192.168.137.114

No manual network configuration was required on Windows (just Ethernet connection).

Non-Working Environments (Linux)

I tested on multiple Linux systems:

Ubuntu 20.04 on Jetson
Ubuntu 20.04 on Neousys POC-545

In all cases:

oakctl list does not detect the camera
oakctl discover also finds nothing
depthai Python examples fail (no device detected)
depthai-core/device_manager.py does not detect the RVC4 device at all

Network Configuration Attempts

Since the camera IP is known from Windows, I tried manual network setups on Ubuntu:

Static IP matching Windows ICS subnet:

$$
192.168.137.1 / 255.255.255.0

$$
Alternative private network:

$$
169.254.1.1 / 255.255.0.0

$$

In both cases:

The camera is not detected
oakctl list still returns nothing
Even with correct subnet alignment, discovery fails

Additional Tests / Limitations

I tried connecting the device via Luxonis Hub on Ubuntu
- oakctl setup cannot be used (device is not discovered)
- oak-viewer is unavailable (Ubuntu 22.04+ only)
Since the device cannot be discovered, I cannot retrieve or configure the IP from Linux
I confirmed that Luxonis software / firmware updates cannot be applied (see attached image)

Background / Experience

I have extensive experience with RVC2-based OAK cameras:

I regularly configure devices via device_manager
Setting static IPs and handling network-based OAK devices is familiar territory for me
RVC2 devices work as expected in similar Linux environments

However, RVC4 behaves very differently, and I cannot even reach the point where the device becomes visible on Linux.

Main Questions

Is there a supported way to use OAK-4-D-FF (RVC4) on Ubuntu 20.04?
Is there a known issue with RVC4 discovery on Linux (oakctl / depthai)?
How can I retrieve or assign the camera IP from Linux if discovery does not work?
Are there additional services, ports, or discovery mechanisms required for RVC4 that differ from RVC2?

Any guidance or confirmation would be greatly appreciated.
At the moment, the device is fully usable on Windows but completely inaccessible on Linux.

Thank you.

OskarSonc

Hey shAhn - firstly I would suggest updating the camera to the newest OS. The error you got is because the camera needs to have access to the internet to perform the update the way you wanted to do it. So either connect internet to it or do the update from Host Option 2.

For linux can you completely remove the oakctl and reinstall it again. You can try running with sudo also. Also you can directly connect to camera with oakctl connect 192.168.137.114.
One more question, how are you connecting to the camera? Are you on same subnet? Is connection with windows same as with Linux devices you tried?

Thanks,
Oskar

shAhn

OskarSonc

Hi Oskar,

Thank you for the clarification. I’d like to provide a bit more detail from my side.

First, on Linux the camera is not detected at all by oakctl list.
Therefore, all attempts using the oakctl commands mentioned below were performed on Windows, where the device is at least visible.

OS update issue (even with internet access)
Even when the camera is connected to the internet, oakctl device update does not work.
I checked the changelog page below:

https://docs.luxonis.com/software-v3/sw-stack/luxonis-os/

For all changelog entries, the linked ZIP files cannot be downloaded manually (the page returns “Bad Page…”, see attached screenshot).

Because of this, it does not appear to be a local network issue on my side. It seems that the download server may not be functioning correctly.
Could you please check whether these OS package links are currently valid?

SSH access issue
I tried to access the device via:

$$
ssh root@<IP_ADDRESS>
$$

However, I was prompted for a password, even though I never configured one.

According to the documentation:

By default, SSH access via password is disabled on devices running OS version 1.18 and newer.

I therefore tried:

oakctl device unlock
oakctl start-setup

But both workflows eventually require an OS update to proceed further.

Since the OS update itself is currently failing (likely due to the server issue mentioned above), I am blocked at this step as well.

At the moment, the inability to update the OS (either online or via manual ZIP download) seems to be the main blocker.
I would appreciate it if you could confirm whether there is an issue with the OS download server or provide an alternative way to obtain the update packages.

Thank you for your help.

shAhn

Update: Issue Resolved

This issue was caused by network security restrictions on our university internet, which blocked access to the OS download server.
After switching to a different network, the OS update completed successfully.

Thanks for the support.

@OskarSonc

OskarSonc

Hey shAhn - sorry for late answear, I was absent. Happy to hear it's now working.

Best,
Oskar

PujaJaiswal

Hey,

I've tried to convert my custom yolov8n_seg model for rvc4 using modelconverter, but after the yolov8-seg stage completes i get this error typeerror "TypeError: Inferer.from_config() missing 4 required positional arguments: 'model_path', 'src', 'dest', and 'config' ". I tried multiple ways to make changes in the yaml file and .py file still i can't resolve the error. can you help me to solve the error?

KlemenSkrlj

Hi @PujaJaiswal ,
looks like something went wrong in the multistage exporter. Would you be able to provide us a MRE which would consist of the:

input model (ONNX or ONNX NNarchive)
config.yaml that was used
CLI command that you used
version of the modelconverter (+ version of SNPE used)

You can share this to me directly through email (klemen.skrlj@luxonis.com) and I'll investigate further.

As a side note though: We do support YOLOv8 instance segmentation model export directly through our HubAI platform (through the YOLO Path). You can just pass in the .pt file and it will automatically convert it for the device you want to deploy the model too. This is usually easier path since you don't need to bother with local conversion. And we also have an HubAI-SDK package if you want to do this through code instead of through UI.

Best,
Klemen