depthai-python: [BUG] Cam Test Fails on OAK-FFP-3P with 2x AR0234 and IMX378

Check if issue already exists

I have found no reference by searching online or the forums

Describe the bug I have an OAK-FFP-3P with the following configuration: Left: AR0234 Centre: IMX378 Right: AR0234

When I try to run cam_test.py using the develop branch of depthai-python (which includes depthai-core) it fails. The AR0234 are also not detected. Note, if I switch to the ar0234_x3 branch, all the cameras are detected.

Image showing only the IMX378 detected when using the develop branch: image

Image showing the same script reporting all three cameras, running from the ar0234_x3 branch: image

Minimal Reproducible Example

python cam_test.py -cams rgb,c left,c right,c            

Enabled cameras:
    rgb : color
   left : color
  right : color
DepthAI version: 2.20.2.0
DepthAI path: C:\Users\keegan\Documents\GitHub\depthai-python\venv\lib\site-packages\depthai.cp39-win_amd64.pyd
Traceback (most recent call last):
  File "C:\Users\keegan\Documents\GitHub\depthai-python\utilities\cam_test.py", line 181, in <module>
    cam[c].setIsp3aFps(args.isp3afps)
AttributeError: 'depthai.node.ColorCamera' object has no attribute 'setIsp3aFps'

Expected behavior I would expect cam_test.py to succeed and be able to stream all cameras.

Additional context I have attached the simple preview script I’ve been using to test the cameras on each branch. preview.zip

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 32 (1 by maintainers)

Most upvoted comments

I was running -cams rgb,c left,c right,c as the option by the way

I was running in depthai rather than depthai-python, I have updated the eeprom and cam_test.py now runs!

image

It’s previewing the cameras all in colour but still listing them as mono. Not sure if this is actually an issue or not as it’s at least functioning ok?

cc also @njezersek on calibration part. @kneave shared on forum:

Apparently this combo of cameras should work but the config file on the 3P may now be in a bad state prevent calibration from working. I've tried running the factory_reset script and it just says the factory calibration isn't present, I've no idea where to find an empty one either.