Does OAK-FFC-6P support for 4-lane MIPI Cameras?

DavidCharlot

I bought the OAK-FFC-6p with the impression that it is able to work with both 2-lane and 4-lane cameras as is described on the product page.

I am successfully able to populate 6, 2-Lane OV9282 (https://shop.luxonis.com/collections/oak-modules/products/oak-ffc-ov9282-pair) in all 4 of the OAK-FFC-6p I have and they work without issue.

The boards have been updated to have:

luxonisos-1.12.dm-verity.mender

fip-oak-ffc-6p-kb-1.5.0.bin

With camtest.py in the utilities folder on the rvc3develop build of depthai version 2.22.0.0.dev+82677440ff840579162511c89e5301aef485504c, I am only able to run 4 of the 6 cameras at the same time. But I can change which 4 are being used so they all work as expected. CamA (RGB), CamB (Left), CamC (Right), CamD, CamE, and CamF work.

When I attempt to use OAK-FFC IMX378 FF (https://shop.luxonis.com/collections/oak-modules/products/oak-ffc-imx378-ff) on CamA or CamD positions of any of the OAK-FFC-6P they don't run.

I also have attempted to use the OAK-FFC ToF 33D and the devices don't run.

Do I have to make a setting to allow them to run, or does the OAK-FFC-6P not support 4-lane MIPI cameras at all?

jakaskerl

Hi DavidCharlot
The 6P has 6 2-lane mipi sockets, but this does not mean it doesn't work with IMX378 ( I think only full resolution 12MP requires 4 lanes).

Could you run cam_test.py in debug mode (DEPTHAI_LEVEL=debug python3 cam_test.py) and post the terminal output?

Thanks,
Jaka

DavidCharlot

**Hi,

This is what happens when I have the IMX378 FF in CamA position on the Oak-FFC-6P

Enabled cameras:**

rgb : color

DepthAI version: 2.22.0.0.dev+82677440ff840579162511c89e5301aef485504c

DepthAI path: /home/dcharlot/.local/lib/python3.11/site-packages/depthai.cpython-311-x86_64-linux-gnu.so

Connected cameras: [{socket: CAM_A, sensorName: IMX316, width: 240, height: 180, orientation: AUTO, supportedTypes: [COLOR], hasAutofocus: 0, name: CAM-A}]

-socket CAM_A : IMX316 240 x 180 focus:fixed - COLOR

USB speed: UNKNOWN

IR drivers: []

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] No calibration data found, ColorCamera won't add FOVs to the color frames!

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] Resolution 1920x1080 not supported, closest supported resolution is 240x180

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] Device will still try to force the specified resolution.

Cam: rgb [host | capture timestamp]

DavidCharlot

@erik

DavidCharlot This is what happens when I have the IMX378 FF in CamA position on the Oak-FFC-6P

Enabled cameras:**

rgb : color

DepthAI version: 2.22.0.0.dev+82677440ff840579162511c89e5301aef485504c

DepthAI path: /home/dcharlot/.local/lib/python3.11/site-packages/depthai.cpython-311-x86_64-linux-gnu.so

Connected cameras: [{socket: CAM_A, sensorName: IMX316, width: 240, height: 180, orientation: AUTO, supportedTypes: [COLOR], hasAutofocus: 0, name: CAM-A}]

-socket CAM_A : IMX316 240 x 180 focus:fixed - COLOR

USB speed: UNKNOWN

IR drivers: []

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] No calibration data found, ColorCamera won't add FOVs to the color frames!

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] Resolution 1920x1080 not supported, closest supported resolution is 240x180

[42B2F016838860C6] [192.168.197.55] [1689777615.462] [ColorCamera(3)] [warning] Device will still try to force the specified resolution.

Cam: rgb [host | capture timestamp]

DavidCharlot

I see there is an OAK-SOM-MAX-2 variant that has 2x 4-Lane and 2x 2-Lane. I will give that a try. I plan to swap out the existing OAK-SOM-MAX (variant 0 / default variant) on the OAK-FFC-6P with has 6x 2-Lane positions.

I hope this addresses the issue.

erik

Hi @DavidCharlot ,
Unfortunately, it's not possible. The thing is that connectors do expose 6x2-lane at the moment and we would need to change the design to enable 4-lane connections on a single connector either with assembly variant or using MUX.

DavidCharlot

Hi @erik , Thanks for sharing.

I think it would be a good idea to remove any mention of compatibility with the OAK-FFC-6P for your 4 Lane MIPI cameras.

I would have purchased 4 OAK-FFC-4Ps.

I suppose I didn't read the fine print. I assumed it would work because there is a mention of the ability to use. Especially in the compatible with and pairs well with section.

erik

Hi @DavidCharlot ,
I believe we already specified it's only 2lane camera ports in our docs/shop, have you found some confusing info online?

DavidCharlot

@erik I'm sure your post is not meant to be funny. But quite literally the cameras I purchased to use with the OAK-FFC-6P you all list and say they are compatible.

OAK-FFC-IMX378

OAK-FFC ToF 33D

DavidCharlot

@erik I also see that you sell an OAK-SOM-MAX-2 (variant 2 which allows 2x, 2-Lane, and 2x 4-Lane).

I made the assumption based on the product literature from the various cameras and from the OAK-SOM-MAX-2 descriptions that you must have made a mechanism for the OAK-FFC-6p to support 6x 2-Lane and 2x 4-Lane because you must have used the OAK-SOM-Max-2 in the OAK-FFC-6p.

It is very clear to me with the products in my hand and attempting to use that:

All your product literature claiming any 4-Lane cameras to be compatible with the OAK-FFC-6P is not accurate. The 4-Lane cameras do, in fact, not work because they are not compatible.

You are not able to run a 4-Lane camera in a port that only supports 2-Lane and get the functionality. Which I see you clearly agree with.

So I agree with your comment that you do specify the OAK-FFC-6P to be 6x 2-Lane. It is just that you also claim 4-Lane cameras can work with the OAK-FFC-6P elsewhere (I'm sharing you should probably change the product language on those products).

erik

Hi @DavidCharlot ,
IMX378 is used only in 2lane config - I believe all our cameras are for RVC3, perhaps only IMX582. So IMX378 should work with the FFC-6P - is that not the case?

erik

Hi @DavidCharlot ,
We apologize for the inconvenience, but could you try with either older fip (1.2), or using a port that isn't CAM_A? As there's a bug with cam_a port on latest fip version.

DavidCharlot

@erik will do. Thanks for sharing. Does the OAK-FFC ToF 33D also have the potential to work in reduced 2-Lane mode on the 6P if I use an alternate port?

erik

Hi @DavidCharlot ,
Yes, there aren't that many pixels/sec for ToF so there wouldn't be a requirement for 4lane mipi.

DavidCharlot

Hi @erik

I purchased a OAK-FFC-4P and received it this week. I tested the 3 camera types I have on each position for the 4p:

4P has 2x 4-Lane and 2x 2-Lane.

CAM_A (RGB): 4-Lane
CAM_B (Left): 2-Lane
Cam_C (Right): 2-Lane
CAM_D: 4-Lane

I can confirm the 3 camera types I have work on all of the 4 positions without any issue. Cameras I use: OAK-FFC-IMX378, OAK-FFC ToF 33D, OAK-FFC OV9282.

I used the OAK-FFC-4P to establish the baseline of expected performance of the OAK-FFC-6P. I do now understand what you were referring that all 3 camera types should work in the 2-Lane slot for the OAK-FFC-6p without issue because they work in the OAK-FFC-4P in the 2-Lane slot without issue.

Can you confirm for me which OS and FIP I need to have on the OAK-FFC-6P to have them work as intended. I made the assumption I'm supposed to use the latest OS and FIP you have on the directory available to download in order to work with the lastest rvc3_develop branch on Github.

erik

Hi @DavidCharlot ,
You should use FIP 1.2, or use a different port than CAM_A. Unfortunately, the FFC-6P isn't actively being updated, as also RVC3 isn't our priority atm (docs here).

DavidCharlot

Hi @erik Thanks for sharing. I didn't know this about the RVC3. I will pause my work on the OAK-FFC-6P and just use the OAK-FFC-4P.