OAK 1 PoE "no devices available" on NUC Mini-PC (works on other PCs)

userOfCamera

Hello,

I've got an OAK 1 PoE connected to my NUC Mini-PC via ethernet (with a power supply + injector to provide power too). The light inside the camera lights/boots up when I connect it to the NUC Mini PC.

However, when I try running any script it always errors as:
with depthai.Device(pipeline) as device:
RuntimeError: No available devices

The scripts work perfectly fine on my USB Oak camera. Furthermore, when I run the script to list recognized devices (https://docs.luxonis.com/projects/api/en/latest/samples/host_side/device_information/?highlight=IP#device-information) I get different outputs on my Windows laptop and NUC Mini PC (running Ubuntu)

NUC Output:
Searching for all available devices...

Couldn't find any available devices.

My Laptop Output:
Found device '169.254.1.222', MxId: '14442C1081E73BD200', State: 'BOOTLOADER'

Booting the first available camera (169.254.1.222)...
Available camera sensors: {<CameraBoardSocket.RGB: 0>: 'IMX378'}
Product name: OAK-1-W-POE, board name PA2096

I don't understand why the NUC simply doesn't even see the PoE device, especially as the Ethernet connection seems good (lights up both ends, I've tried multiple working ethernet cables)

jakaskerl

Hi @userOfCamera
Seems you are using a DHCP-less network, which means your devices will all fall back to their static IP.
Your NUC is likely not inside the same subnet (169.254.x.x), that's why autodiscovery doesn't work [more info].

Thanks,
Jaka

userOfCamera

@jakaskerl I set the static IP of the OAK to the same subnet as my NUC using both device_manager.py and running the script here (https://docs.luxonis.com/projects/api/en/latest/samples/bootloader/poe_set_ip/)

However, the static IP remains the default one. Running the script in the URL linked above 10 seconds after changing the static IP gives the following output:

Found device '169.254.1.222', MxId: '14442C1081E73BD200', State: 'BOOTLOADER'

I was expecting the IP of the device to be the newly set static IP.

I'm doing this on a separate Windows laptop (since my NUC can't recognize the camera right now)

jakaskerl

Hi userOfCamera
You can change the NUC ip and mask to be in the same range as the device. I think the laptop manually changes its settings, but the NUC doesn't, that's why the discrepancy.

Thanks,
Jaka

userOfCamera

I wasn't able to change the NUC's IP due to certain constraints, but I fixed this problem.

I was putting in the wrong Mask and Gateway. Fixing this solved my problem.

jakaskerl

userOfCamera

userOfCamera I was putting in the wrong Mask and Gateway. Fixing this solved my problem.

When flashing the new IP to the device? That would explain why it didn't flash properly.

Thanks,
Jaka