Unable to Connect Cameras of Different Types on Port A and D or C – Drive OS 6.0.10

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Software Version
DRIVE OS 6.0.10.0

Target Operating System
Linux

Hardware Platform

DRIVE AGX Orin Developer Kit (not sure its number)

SDK Manager Version
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers

Issue Description
Hi,

I’m using Drive OS 6.0.10 and I’m having trouble connecting cameras of different types.

I can successfully read 3 cameras of the same type on Port A, which corresponds to NB3 in the rig file.
However, I’m not able to read the front camera (NB2) defined in the rig file and assigned to Port D.

I can only read NB2 when it’s connected to Port A using the sample camera app.
But I can’t get both NB3 and NB2 (different camera types) to work together on the same port (Port A), or across Ports A and D or C .

Has anyone managed to get different camera types (like NB2 and NB3) working on different ports at the same time?

Thanks in advance!

rig.txt (3.5 KB)

image
image321×327 43.9 KB

image
image125×180 18.5 KB

Error String

error logs.txt (94.4 KB)

4

Dear @yanis.ikhlef-extern ,

When you run NB2 camera alone , is it working?
Could you check running 2 instances of nvsipl_camera for port A and D in parallel where NB3 is connected to port A and NB2 connected to port D. This confirms if there is any issue from NVSIPL. Also, see if modifying format=processed,output-format=yuv to output-format=processed helps?

6

Hi @SivaRamaKrishnaNV

When running the NB2 camera alone, it works well using NVSIPL across the different ports A, C, and D.

However, when trying to run two instances of nvsipl_camera in parallel —

  • NB3 connected to port A

  • NB2 connected to port D or A

(using split terminals and launching both with display and without display using -d 0),
it does not work.

I also tried modifying the configuration:

  • Changed format=processed and output-format=yuv to format=processed,output-format=processed

  • Tried different formats like raw and mp4

But none of these changes worked, and I encountered the same error as before in the logs.

image (4)
image (4)1367×577 35 KB

image (5)
image (5)1434×268 17.4 KB

image (6)
image (6)1585×679 49.9 KB

8

Sorry for the late response.
Is this still an issue to support? Any result can be shared?

9

Hi @kayccc

Thanks for following up,

The configuration I used is included in the rig file. Unfortunately, I still haven’t resolved the issue of reading cameras of different types. If there are any solutions or suggestions you can share, I’d really appreciate it.

10

Does that mean,
you have ran two instances on nvsipl_camera in two different terminal with no display.NB2 is connected to port D and NB3 connected to port A. Please share the nvsipl_camera logs with -v 4 (verbose mode) and also /var/log/syslog for further investigation. Note that, sample_Camera is expected to work only when nvsipl_camera works in the same configuration.

11

Hello,

syslog.txt (46.7 MB)

log DriveAGX.txt (93.1 KB)

image
image1111×142 13.1 KB

Please note that we are not able to run nvsipl_camera without display, we did test but it did not work in this configuration.

Please find attached:

  • The nvsipl_camera logs with the -v 4 (verbose) option

  • The /var/log/syslog file for further investigation

We understand that sample_Camera is expected to work only when nvsipl_camera is running properly with the same configuration.

Let us know if you need any additional information.