NVSIPL. 3 cameras running is stable. 4 cameras running causes crash

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu 18.04
other

Hi,

I’m having an issue running 4 cameras on 4 separate processes in NVSIPL. I was able to stream a video feed running 3 cameras for an entire weekend. When I run 4 cameras, all processes will crash after ~5 minutes.

I’m getting a failure status code of 5 (NVSIPL_STATUS_TIMED_OUT). Below is an excerpt from the console:

The processes crash on an INvSIPLFrameCompletionQueue derived class Get() method.

This issue only occurs with our 8MP Entron F008 cameras. This issue does not occur while using 4, 2MP Entron F003 cameras.

What might be a good route to begin debugging this issue?

Thanks,
Mick

You may want to check if this issue is specific to the camera modules. One possible solution could be to reduce the resolution and see if it improves stability.

In the nvsipl_camera sample application, I do not see a way to change the resolution of the camera. Is this done by the ISP or does the image sensor reduce the amount of pixels it outputs?

To reduce the resolution, do I require a new NITO file? Lastly, what nvsipl method do I use to chagne the resolution.

Thanks Again,
Mick

I assumed that you are developing drivers for a custom camera module and have control over its specifications, so I thought you might be able to adjust the resolution. Have you considered increasing the timeout value? Alternatively, you could try using one of the supported 8 MP modules listed on https://developer.nvidia.com/drive/ecoystem-xavier#camera to see if that resolves the issue.

Oh, no. We’re not developing the drivers. We’re creating on an autonomous car project. I am developing an API for our company’s application team so that they can pass the video data into their AI model. The camera we’re using was developed by Entron, and it’s on the supported camera list. The full model name is Entron F008A120RM0AES.

Another camera we’re using is the Entron F003A208RM0A. This one is working well fortunately.

I increased the timeout earlier today to 10 seconds, unfortunately, the same issue is occurring.

I’ve also now tested this on a different Drive AGX Xavier and the same issue is occurring.

According to https://developer.nvidia.com/drive/ecoystem-xavier#camera, you should contact Onsemi support for assistance with the Entron F008A120RM0AES camera issue. They should be able to help you troubleshoot and resolve the problem. If you need help finding their contact information, please let me know.