Hi @tinito
Run the cam_test with cam_test.py -cams cama,c camb,c camd,c -cres 12mp -rs. You should be getting a 12MP stream.

Thanks,
Jaka

Hi @jakaskerl

thanks for your hint, I get a warning saying that the 12mp resolution is not supported and the closest one is 1920x1080.

Here the output I get (with a single camera):

$ python3 cam_test.py -cams camb,c -cres 12mp -rs
Enabled cameras:
camb : color
DepthAI version: 2.23.0.0.dev0+ff929745dc99589a560217f857f49d8bf00a5463
DepthAI path: /home/mmigliavacca/.local/lib/python3.10/site-packages/depthai.cpython-310-x86_64-linux-gnu.so
Connected cameras: [{socket: CAM_B, sensorName: IMX412, width: 1920, height: 1080, orientation: AUTO, supportedTypes: [COLOR], hasAutofocus: 0, hasAutofocusIC: 0, name: CAM-SA}]
-socket CAM_B : IMX412 1920 x 1080 focus:fixed - COLOR
USB speed: UNKNOWN
IR drivers: []
[41524016838860C6] [192.168.197.55] [1712841310.197] [ColorCamera(3)] [warning] No calibration data found, ColorCamera won't add FOVs to the color frames!
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
[41524016838860C6] [192.168.197.55] [1712841310.198][ColorCamera(3)] [warning] Resolution 4056x3040 not supported, closest supported resolution is 1920x1080
[41524016838860C6] [192.168.197.55] [1712841310.198] [ColorCamera(3)] [warning] Device will still try to force the specified resolution.
Cam: camb [host | capture timestamp]
FPS: 2.95| 2.95

Here a screenshot of the corresponding preview image:

    @tinito Sorry for this problem, I checked and we can reproduce. Currently for IMX577 these configs are exposed by the imx412 driver:

    • 4056 x 3040 on 4 lanes
    • 3840 x 2160 on 4 lanes
    • 1920 x 1080 on 2 lanes

    And as all camera sockets on OAK-FFC-6P are only 2-lane capable, the 1080p config is selected which will not work with the higher resolutions. We need to add more configs in the kernel driver, I hope to have an update on this in the following days. A quick fix may be to revert to using the IMX378 configs, which work with IMX577 unless 180 rotation is enabled.

    Thanks @Luxonis-Alex for checking and clarifing this issue.
    Having more configs in the kernel driver would be great. How can I force the use of the IMX378 configs in the meantime?

      tinito
      You can't directly specify the config used since that is part of the FW. Using IMX378 config probably wouldn't work since sensors don't have the same decoding.

      Thanks for the patience,
      Jaka

        10 days later

        @jakaskerl
        Any updates on this?

        We can also consider changing sensor, if there are options that can work at 12MP with the standard drivers.

        As we also have this issue, it would be very helpful if you can suggest a sensor that:
        a) works at 12MP out of the box
        b) works with 6 sensors simultaneusly connected to the OAK-FFC-6P

          Hi tinito
          No good support for multiple same sensors on same I2C bus currently, other than OV9282, OV9782...

          Thanks,
          Jaka

            Hi @jakaskerl

            ok thanks, today we ordered some IMX378 AF boards (from Luxonis) which have the SLASEL signal exposed so we can change the I2C address.
            Will the standard driver look for both I2C addresses or do we need a custom module?

            Thank you,
            Martino

              Hi tinito
              Yes, 2 sensors IMX378/477/577 on same bus should work if SLASEL can be changed for the other.

                8 days later

                Hi tinito
                The 12MP issue has been fixed for IMX577 in this build.

                Install with mender -install FILE_or_LINK.mender && reboot

                Thanks,
                Jaka

                  Hi @jakaskerl

                  indeed the IMX577 is working now at both 4k and 12mp resolutions, thanks for your support!