OV9782 detected as OV9282 on OAK-FFC 4P

NathanLynx

Hello,

I am using 4 OAK-FFC OV9782 W (D/C: 4623 and D/C: 1823) on OAK-FFC 4P (D/C: 1824C2) but only one of them is detected correctly. The 3 others are detected as OV9282 when I am running the cameras on DepthAI Viewer and even through ROS.

Here is what DepthAI Viewer gives me :

Connected camera features: [{socket: CAM_A, sensorName: OV9782, width: 1280, height: 800, orientation: AUTO, supportedTypes: [COLOR, MONO], hasAutofocus: 0, hasAutofocusIC: 0, name: CAMA-4L}, {socket: CAM_B, sensorName: OV9282, width: 1280, height: 800, orientation: AUTO, supportedTypes: [MONO, COLOR], hasAutofocus: 0, hasAutofocusIC: 0, name: CAMB-2L}, {socket: CAM_C, sensorName: OV9282, width: 1280, height: 800, orientation: AUTO, supportedTypes: [MONO, COLOR], hasAutofocus: 0, hasAutofocusIC: 0, name: CAMC-2L}, {socket: CAM_D, sensorName: OV9282, width: 1280, height: 800, orientation: AUTO, supportedTypes: [MONO, COLOR], hasAutofocus: 0, hasAutofocusIC: 0, name: CAMD-4L}]

Do you have any ideas why they are not detected as OV9782 ?

Thanks,
Nathan

lovro

Hi,

thanks for the info. Could you try running this example to check how the cameras are detected:

https://docs.luxonis.com/software/depthai/examples/device_information

Please use the latest DepthAI version if possible. Just want to make sure it's not a software issue.

Best,
Lovro

NathanLynx

To give you more information, I am running the OAK-FFC 4P through USB 3.0 on a Jetson Orin NX (Jetpack 5.1.1 / Ubuntu 20.04) and I have the following wheel installed depthai-2.30.0.0-cp38-cp38-manylinux_2_28aarch64.whl.

When I run the device_information.py example it gives the following output :

Searching for all available devices...

Found device '1.2.3', MxId: '14442C10A1A79ED200', State: 'BOOTLOADER'

Booting the first available camera (1.2.3)...

device_information.py:22: DeprecationWarning: Use constructor taking 'UsbSpeed' instead

with dai.Device(dai.Pipeline(), infos[0], usb2Mode=False) as device:

Available camera sensors: {<CameraBoardSocket.CAM_B: 1>: 'OV9282', <CameraBoardSocket.CAM_A: 0>: 'OV9782', <CameraBoardSocket.CAM_C: 2>: 'OV9282', <CameraBoardSocket.CAM_D: 3>: 'OV9282'}

Product name: OAK-FFC-4P, board name DD2090

lovro

Hi,

this could possibly be related to the issue discussed here:

https://discuss.luxonis.com/d/1550-oak-ffc-ov9782-w-not-giving-rgb-image

In that case, the user also had OV9782 modules being detected as OV9282, and was only getting grayscale output. Might be worth checking if something similar is going on with how the sensor is initialized or recognized.

Best,

Lovro

NathanLynx

This might be almost the same case. The ones detected as OV9282 give grayscale output and the only one detected as OV9782 gives color output.
The only thing I am worried about is that the file (in the discussion) used to flash is for the OAK-FFC 6P if I am not wrong.

Should I try to use this file on my OAK-FFC 4P ?

Best,
Nathan

lovro

cc: @Luxonis-Alex to confirm it.

NathanLynx

Since I will use them with ROS, I found a temporarily solution even if it is detected as OV9282 instead of OV9782 by modifying the sensor_helpers.cpp file in depthai_ros_driver. I changed the line of the OV9282 by telling it is in color instead of mono.
For now it is working, but I don't know if it can cause problems elsewhere since it is still detected as OV9282.

lovro

Hi,

glad to hear you found a fix. If it works, maybe fine for now — but could cause issues later (exposure, color, etc.). Don’t flash 6P firmware on 4P yet, I will communicate this back to the team.

NathanLynx

Hi,

Do you have any news about my problem ?

Thanks,
Nathan