Reset OAK-D CM4 PoE

Babacar

Dear forum,

I would like to reset my OAK-D CM4 PoE camera as I'm experiencing difficulties in connecting to it and identifying it on my network. I used Wireshark to analyze the network traffic and discovered that the camera's IP address is set to 10.0.0.1, which seems unusual.

I intend to perform a factory reset on my camera, and I'd like to know if the procedure simply involves opening the camera and pressing the reset button. Is that correct?

Additionally, I've noticed that the left LED of the camera is orange, while the right LED is blinking. Is this a normal configuration, or is there an issue?

Any assistance or guidance you can provide would be greatly appreciated.

Thank you in advance!

Best regards,
Babacar

jakaskerl

Hi Babacar
You can use device manager app to reset the device to factory settings. The app is located under depthai-python/utilities/device_manager.py

As for LEDs, GPT says:

The solid orange left LED indicates that the device is powered on, while the blinking green right LED suggests that the device is actively streaming data or processing frames.

Thanks,
Jaka

Babacar

hi jakaskerl

Dear Jaka,

Thank you for providing information about the LEDs on the OAK-D CM4 PoE camera. It helps me understand their functionality.

However, I'm still facing issues with connecting to the device and detecting it in the device_manager's dropdown list. Even when attempting to use the "specify ip" option to manually input the IP address, I'm uncertain if I have the correct IP address for my camera.

In this situation, could you please provide detailed instructions on how to perform a factory reset using the device_manager tool? Additionally, if there are any steps to verify or obtain the correct IP address for the camera, I would greatly appreciate your guidance.

Thank you in advance for your support.

Best,

Babacar

jakaskerl

Hi Babacar
The easiest way to find the IP of the camera is through your router. If the device is located at IP outside your subnet, the usual detection methods won't work. If despite everything you still can't connect to the camera, you can perform the reset manually as described in factory reset doc.

Thanks,
Jaka

Babacar

Hi jakaskerl ,

I have opened the camera, but the configuration doesn't match the one described. How can I proceed with the factory reset on my camera? Please refer to the image below for the configuration I have.

Thank you for your assistance.

Best regards,

Babacar

jakaskerl

Hi Babacar
Sorry I didn't realize you were using CM4 poe. In this case, follow this tutorial to reflash the device.

Thanks,
Jaka

Babacar

hi jakaskerl ,

Thank you for your assistance. I have followed the steps in the tutorial you suggested, but I'm still encountering some issues.

When I attempt to run device_manager, I'm not detecting any devices. Also, when I run depthai_demo.py, I receive the following error message: "AttributeError: 'Demo' object has no attribute '_pm'". I have tried to follow all your tutorials but I can't seem to find a solution for this issue.

I have also used Wireshark to try to find the camera's IP address. It gave me the following line: "2 1.022676 Raspberr_63:0b:05 Broadcast ARP 60 Who has 8.8.8.8? Tell 169.254.90.79". I assumed that 169.254.90.79 was the camera's IP address so I entered it into device_manager using the specifyip option for detection, but it didn't find anything.

Could you help me resolve this issue? I'm looking forward to being able to use the OAK-D PoE CM4 camera and I greatly appreciate any help you can provide.

Best regards,
Babacar

jakaskerl

Hi Babacar
You can't really use the device manager with CM4 since it's the RPI that connects to the outside. The PI acts as a host machine and doesn't really work like the rest of the POE devices.
Imagine you have a raspberry pi with a POE hat, that is also connected to a Depthai SOM via USB and is able to communicate with it.
Here is a guide on how to connect to a raspberry pi and execute scripts that can run on the SOM (you can't directly access the SOM).

Again, sorry for the confusion.

Thanks,
Jaka

Babacar

Hi jakaskerl

Thank you for your explanation. I understand that the Device Manager may not be compatible with the Compute Module 4 (CM4) setup where the Raspberry Pi acts as the host machine and communicates with the DepthAI System-on-Module (SOM) via USB.

To recap my installation process, I followed the steps from the beginning, including adding the "wpa_supplicant.conf" and "ssh" files using USB boot and moving the connector to the EN pins. Then, I moved the connector back to its initial position, DIS.

I connected to the Raspberry Pi via SSH using the command "ssh -X @ipaddress" in my terminal. However, when I tried to run the test shown in the tutorial, it showed "No available devices." I also tried running the "device_manager.py" script, but it doesn't detect the camera.

Could you please guide me on how to proceed further and troubleshoot the issue?

Thank you for your assistance.

Best regards, Babacar

erik

Hi Babacar ,
We apologize for the inconvenience. Could you try running the 2 troubleshooting steps described here? https://docs.luxonis.com/en/latest/pages/troubleshooting/#depthai-can-t-connect-to-an-oak-camera
If device isn't found, it's likely a HW issue, and we will replace the device.

Babacar

hi erik

For the first command (lsusb | grep 03e7), my terminal returns nothing, and for the second command, I have the following output:
[ 563.098515] usb 1-1.1: USB disconnect, device number 3 [ 1489.849467] usb 1-1.1: new high-speed USB device number 4 using xhci_hcd [ 1489.950031] usb 1-1.1: New USB device found, idVendor=03e7, idProduct=2485, bcdDevice= 0.01 [ 1489.950049] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1489.950056] usb 1-1.1: Product: Movidius MyriadX [ 1489.950062] usb 1-1.1: Manufacturer: Movidius Ltd. [ 1489.950067] usb 1-1.1: SerialNumber: 03e72485 [ 1933.231278] usb 1-1.1: USB disconnect, device number 4"

Please let me know if you need any further information. Thank you for your assistance in resolving this issue

erik

Hi Babacar ,
It seems like device is detected. Are you using preconfigured RPi image? It might be that you don't have udev rules setup.

Babacar

erik

I initially didn't use a preconfigured RPi image, but I reinstalled it, and now it works perfectly fine. Thank you!