Please provide the following info (tick the boxes after creating this topic): Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
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)
SDK Manager Version
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
I am trying to use check the sample_camera application with multiple camera. As i increase the number of cameras i see that the frame rate is dropping . can you please point at some documentation that i can refer to and use to improve this. From a single camera 30 fps to 4 cameras it dropped to 15fps.
Please let me know what logs are needed to assess.
Which specific cameras did you use in the setup?
I used Valeo cameras(V1SIM728S2RU4070HB20) in one case and Entron cameras (F008A120RM0AV2)in the other time.
How were these cameras connected to the devkit?
all 4 valeo are connected to group A or Group C. Similarly all 4 Entron are connected to either group A or group C or D.
In all the cases i see the frame rate dropping.
Could you elaborate on how you measured the frame rate drop from 30 fps to 15 fps?
I am using the sample application sample_camera and modified the code to add time stamping dwSensorCamera_getTimestamp(). But the native code from nvidia displays (or outputs) the frame rate for the cameras all time.
Pls let me know what logs will be helpful in debugging this.
As i understand the sample_camera may not be optimized for the ISP pipeline. Please let me know the best possible methods for achieving 30FPS provided by the camera sensor.
nvsipl shows 29fps , but i am currently trying to use the simple_camera test where i can use the rig.json
I am yet to identify the changes between nvsipl and simple_camera.
The only reason i moved to simple_camera is that i can use the rig file and use even 8 cameras at same time.
i am not sure why it is not possible to use the same rig file that i am able to use with simple_camera when trying to run nvsipl.
To clarify, are you experiencing the frame-dropping issue consistently when running the application with multiple specific cameras only on a single group (either Group A, C, D)? Also, have you tested the scenario with just two cameras to check if the issue persists?
when i use simple_camera test framwork , i see on a single group as i increase the number of cameras the frames drop (Frame rate being reported as ~20 for 4 cameras on single group).
I also checked the way above siva proposed to use nvsipl_camera, with that i dont see this behavior all 4 cameras report 29pfs which is almost the same as per camera spec.
when working with simple_camera i was able to use the rig file to run 8 cameras (4 of each type) . I was not able to use the same rig file with nvsipl_camera. Do you have any command reference that can help me to run nvsipl with rig.json?
Also i am trying to understand the difference between simple_camera test and nvsipl test . why with simple_Camera the frames drop or it reports Frame rate as less and in case of nvsipl there is no frame drop issue.
What if you test with two cameras? If the frame drop persists, please test with two cameras on different groups.
As the number of cameras increases when we use the sample_camera we can see a drop in framerate reported. even if the cameras are on the same group or even if they are on different group.
The ‘rig’ interface is part of the DriveWorks API and is not utilized in the DRIVE OS sample application.
Are we saying that we can not use rig.json at drive os application level ? At the Drive OS application level if we want to use 2 variants of cameras (like from 2 different vendors) how can that be done in that case ? nvsipl_camera -t option gives custom camera platform configuration but when i use nvsiple with -t it doesnt work .
The platform configuration JSON file used in DRIVE OS is distinct from the rig file used in DriveWorks. You’ve already initiated several topics regarding nvsipl_camera and the configuration file. Please continue the discussion there, and focus this one on the original issue with my question below. Thanks.
Considering the application doesn’t work with more than one camera, as you reported in the topic below, I suspect that the frame rate drop issue might not have been identified by our QA either. I am currently checking this with our team.
Sample_camera works definitely with multiple number of cameras. I tried with all 8 in place . can you check with your internal team if they saw the similar behavior of frame drop when using multiple cameras either on same port or different port?
If this is already observed what is the possible solution for this