Exception while opening the camera. No available devices

Mehtab

Im getting an error on my OAK-D-CM4-PoE: Exception while opening the camera. No available devices.

I've tried to reconfigure this device and also reimaged the device as I was not able to find the root cause of this error.

Also, other OAK devices do work on the same ethernet cable, so I do not think it is network related. I have looked through the troubleshooting page as well - PoE deployment guide (luxonis.com)

Any ideas on how to resolve this error?

Thanks,

Mehtab

jakaskerl

Hi @Mehtab
Can you ssh into the device? If so, try running lsusb and check if MX device shows up. Also make sure the boot switch is set to DIS.

Thanks,
Jaka

Mehtab

Hey Jaka,

Thanks for getting back to me.

Yes I can ssh into the device and I have switched the usb boot to DIS.

When I run lsusbon the device, this is the output I get, I don't see any MX device.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Please let me know next steps.

Thank you,

Mehtab

erik

@Mehtab what do you mean wrt "usb boot to DIS"? Also note that "PoE deployment guide" does not apply for your camera, as it's POE connection to RPI, not OAK. RPI to OAK connection is via USB, so you should follow that guide (perhaps udev rules problem?).

Mehtab

erik I followed the instructions here for flashing an image to the eMMC: Deploy with Raspberry Pi (luxonis.com)

This is what I mean by switching USB boot back to DIS after flashing the image.
"After flashing is complete, make sure to disable the USB boot (by switching the connector again) and restart the device. It should boot from the newly flashed image".

Also, I did see my specific model in this documentation:
OAK-D CM4 and OAK-D CM4 PoE have Raspberry Pi Compute module 4 (CM4) on-board. Most OAK-D-CM4 batches have CM4 with an eMMC memory on there.

It's also recommended in the documentation for users to use the RPI OS (default one) for all OAK cameras.

Hoping to hear back soon!

Mehtab

erik

@Mehtab recommended is the prebult image we provide (on top of Deploy to RPI docs), as otherwise you need to go through the installation process.

Mehtab

erik do you mean the installation process for DepthAI (that's what I see at the top of the documentation), if so, I have completed those steps as well.

I also tried updating the udev rules.

The main difference I see is the missing MX device as @jakaskerl mentioned, on a working OAK device that is detecting the camera,

I get the output:
lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 002: ID 03e7:f63b Intel Myriad VPU [Movidius Neural Compute Stick]

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 002: ID 03e7:2485 Intel Movidius MyriadX

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Whereas on the reimaged device, I only get:

lsusb

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

erik

@Mehtab no, you'll also need to flash some driver for USB hub (see V8 last line: https://docs.google.com/document/d/1c4JhIY2ulcgaaycUBOsAbUI1EJ_7Zx4ux4alaxFc_ts/edit ), which has been done in preconfigured img.

Mehtab

erik I see, would it be possible to flash the entire preconfigured image?
I see the OS image for V8 that you mentioned here: RPI OS Images - Google Drive

Just to clarify, is OAK-CM4-POE the same as OAK-D-CM4-POE?

Thanks,

Mehtab

erik

@Mehtab yes, use that image

Mehtab

erik Hi Erik, I've been experimenting with the OS images, and V8 still gave me the same error (it was not able to detect the MX device)

However, V9 worked, and my device is successfully detecting the camera and capturing images.

Thank you both @erik and @jakaskerl for the support!

Best,

Mehtab