Driveworks camera parameters to capture frame

[stefan65]

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

I am using OX03C10_MAX96717F and IMX623_MAX96717F cameras. OX03C10 connected to group C and IMX623 connected to group B. I am able to view capture frame and view FPS using the ./nvsipl_camera tool. I am now trying to capture the frame using driveworks SAL. However, the parameters are different than nvsipl_camera, especially the link mask and the csi-interface. What parameters do I pass to dwSensorParams paramsClient to make it capture frame. Currently I am getting DW_NOT_AVAILABLE indefinitely when trying to capture frame. Here is the nvispl commands that worked for the OX03C10_MAX96717F camera connected to group C:

/nvsipl_camera -c DSV_MULTIPLE_CAMERA -m "0 0 1111 0" -1 -2 -s -a -R

and the driveworks params I am trying right now is:

 paramsClient.parameters = "camera-name=OX03C10_MAX96717F,interface=csi-ab,output-format=processed,link=2,async-record=1,file-buffer-size=16777216,nito-file=/usr/share/camera/OX03C10_MAX96717F.nito";

[VickNV]

It appears that the camera modules you’re using (OX03C10_MAX96717F and IMX623_MAX96717F) are currently not listed as supported on these pages:

• https://developer.nvidia.com/drive/ecosystem-hw-sw#cameras
• https://developer.nvidia.com/drive/ecosystem-orin#camera

If that’s the case, they are not supported through the forum. We recommend reaching out to your NVIDIA representative to determine the appropriate channel for assistance. Custom camera module support is not handled through the general forum. Thank you.

[stefan65]

Thanks,

But I see the Sensors OX03C10 and IMX623 supported by Nvidia out-of-the-box.
Let’s assume I have the cameras “Sony IMX623EVB-MLH-SMM3” with IMX623 sensor and “OmniVision OX03C10-EXAL-BA0C” with OX03C10 which are supported by Nvidia.

Are there any general guidelines and some parameters in the driveworks API that are specific to the sensors? especially the interface. The driveworks documentation mentions: The choice for csi-port depend on the sensor. What would be the csi-port interface for OX03C10 and IMX623 ?

There are four connectors on each camera group. so how do we set the parameter to pick one camera connected to say group B? what goes into the link parameter? I would assume this parameter is independent of make and model of the camera sensor

[VickNV]

As indicated in the table on the page, even for “Sony IMX623EVB-MLH-SMM3” and “OmniVision OX03C10-EXAL-BA0C”, developers have to contact Sony and Omnivision as our ecosystem to get the support. Our team doesn’t have the experience with all the sensors and accessories.

[stefan65]

Can you atleast help me out with the link parameter. That is independent of the camera make and model and points to the connector on the Orin Dev Kit

There are four connectors on each camera group. so how do we set the parameter to pick one camera connected to say group B?

Thanks

[VickNV]

To set the interface and link parameters for a camera connected to the first link of group B, you can refer to the following example from a rig file:

# grep -r "csi-cd" --include=*\.json /usr/local/driveworks | grep 623
/usr/local/driveworks/data/samples/sensors/camera/camera/rig_imx728_imx623_ar0820.json:                "parameter": "camera-name=V1SIM623S3RU3200NB20,interface=csi-cd,CPHY-mode=1,link=0,output-format=processed,async-record=1,file-buffer-size=16777216",

[stefan65]

is this rig file available in drive OS 6.0.6 sdk? I can’t seem to find it, I have these

$ ls
rig.json  rig_ar0820.json  rig_imx390_ar0820.json

can you point me to where I can find this file?

Thanks

[VickNV]

You can refer to the ‘csi-cd’ parameter from the release you’re using. However, I would recommend always upgrading to the latest release (currently 6.0.8.1).