Failure in Dumping Registers from Sensor: AR0231

roshan.shenoy · August 16, 2023, 2:56pm

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

Hello,

When i try to dump registers from the sensor, I get an error stating Failed to read to regsiters over I2C
Please find below the terminal log

nvidia@tegra-ubuntu:~/drive-t186ref-linux/samples/nvmedia/img_cc$ sudo ./nvmimg_cc -wrregs ddpx-a/dvp_m_ar0231_rccb_raw12_1920x1236_ab_ta.script -d 0 -w 1 -rdregs test
Module_id 22 Severity 6 : ICP Major version number 4
Module_id 22 Severity 6 : ICP Minor version number 22
Module_id 22 Severity 6 : NvMediaICPCreateEx 76
Module_id 22 Severity 6 : T19x VI version  0x000019
Module_id 22 Severity 2 : SetChannelConfig 761
Module_id 22 Severity 2 : Sensor framerate is below minimum to guarantee VI PFSD FDTI
Capturing Frames...
nvmedia: ERROR: _CaptureThreadFunc: keep failing at NvMediaICPGetImageGroup for 11 times
Module_id 22 Severity 2 : sReleaseImage 2112
Module_id 22 Severity 2 : CaptureGet failed with status  3
Module_id 22 Severity 2 : sICPReleaseImageGroup 2177
Module_id 22 Severity 2 : Failed to release an image from the group. Image number  0
^Cnvmedia: ERROR: ProcessCommands: Failed to read I2C 40 4d
nvmedia: ERROR: _ReadSensorRegisters: Failed to read to registers over I2C
nvmedia: ERROR: CaptureFini: Failed to read sensor registers

Could you please provide a reason for this?

Best regards,
Roshan

VickNV · August 16, 2023, 4:31pm

I would like to point out that ICP (Image Capture Processor) has been deprecated, as mentioned in my post. It’s worth noting that using the ICP application is not recommended due to its deprecated status.

However, I’d like to mention that another developer was able to successfully run a similar command. You can find more details in his/her topic. This might provide some insights or references that could help you troubleshoot and resolve the issue.

roshan.shenoy · August 17, 2023, 6:43am

Hi,

Thank you for your response. I tried this, but in my case i was not able to read the sensor register values.

Could you please share information on how we can read the sensor register values?

Best regards,
Roshan

roshan.shenoy · August 17, 2023, 1:51pm

Hello,

Short update, i’m now able to capture the frames for AR0231, please find the log below and the register dump file
regdump_ar0231.dat (4.9 KB)

nvidia@tegra-ubuntu:~/drive-t186ref-linux/samples/nvmedia/img_cc$ sudo ./nvmimg_cc -wrregs ddpx-a/dvp_m_ar0231_rccb_raw12_1920x1236_ab_ta.script -d 0 -w 1 -rdregs regdump_ar0231_1
Module_id 22 Severity 6 : ICP Major version number 4
Module_id 22 Severity 6 : ICP Minor version number 22
Module_id 22 Severity 6 : NvMediaICPCreateEx 76
Module_id 22 Severity 6 : T19x VI version  0x000019
Module_id 22 Severity 2 : SetChannelConfig 761
Module_id 22 Severity 2 : Sensor framerate is below minimum to guarantee VI PFSD FDTI
Capturing Frames...

Could you please provide us a (dvp_m_ar0231_rccb_raw12_1920x1236_ab_ta.script) similar script file for Entron F008A120RM0A (AR0820), so that we can also dump the registers for this camera?

Best regards,
Roshan

VickNV · August 17, 2023, 3:35pm

It’s still unclear why the previous issue happened. Could you share how you resolved it?

We don’t have a script for the module. As I mentioned earlier, the ICP API has been deprecated, and it’s recommended to transition to SIPL APIs. Could you please share the specific reason you need to dump the registers?

roshan.shenoy · August 17, 2023, 7:01pm

Hello,
we were previously using camera group b instead of camera group a in the AGX, which led to the issue, sorry for the trouble

roshan.shenoy · August 18, 2023, 8:12am

Hello,

In the past we used the ICP framework to verify our emulation.
We have digital twins/emulations for AR0231 and AR0820, we would like to compare the dumped registers between the emulation and the actual camera module

Could you please let us know how we can dump the registers with SIPL APIs?

Thanks in advance!

Best regards,
Roshan

roshan.shenoy · August 18, 2023, 4:22pm

We have a developed a device which emulates a camera, you can consider it as a digital twin of Sekonix SF33325-100.

We compared our emulation with the real camera with “nvsipl_camera” example and notice the difference in the initialization phase.
Attached the dumps from Real camera(RealCamera.out) and our emulation(VIBX.out).
It seems to us that the CHIP_ID for the the sensor doesn’t match with the one needed by the SIPL driver. We have programmed the CHIP_ID for AR0231 to be 0x0354 and this was never a problem with the ICP based driver and also worked DriveOS: 5.1.6 DW 2.2. In SIPL this seems to be different, somehow without the source code we are unable to identify the difference.

Our problem today is after after updating to DriveOS: 5.2.6 and DW: 4.0 our sensor emulation doesn’t work any more.

RealCamera.out (271.0 KB)
VIBX.out (26.5 KB)

PS: Our NVIDIA representative has so far not answered our Email, sent out on 24.07.23, and we are stuck. Kindly help!

VickNV · August 18, 2023, 4:59pm

I have sent you a private message to understand the context better.

VickNV · August 21, 2023, 3:37pm

Did you mean your emulation works with ‘nvsipl_camera’ on DriveOS 5.1.6.1 but not on DriveOS 5.2.6?

Could you please elaborate on what you mean by the ‘CHIP_ID’? Is this related to SIPL in some way?

roshan.shenoy · August 21, 2023, 4:32pm

We meant that the emulation previously worked with DriveOS 5.1.6 using NvMedia Image Capture Processing (ICP) and with the sample_camera in DW 2.2 but now it does not work after upgrading to DriveOS 5.2.6 with nvsipl_camera (SIPL) and with sample_camera in DW 4.0

We observe here in the log below we get a message

nvidia@tegra-ubuntu:~/drive-t186ref-linux/samples/nvmedia/nvsipl/test/camera$ ./nvsipl_camera --platform-config "SF3325_CPHY_x4" --link-enable-masks "0x0001 0x0000 0x0000 0x0000" -d 0 -w 1 --enableRawOutput --disableISP0Output --disableISP1Output
MAX96712: Revision 2 detected
MAX96712: Enable periodic AEQ on Link 0
MAX96705: Pre-emphasis set to 0xaa
MAX96705: Revision 1 detected!
Module_id 30 Severity 2 : src/devblk/nonfusa/cameramodule/MAX96712cameramodule/ar0231/cdi_ar0231_rccb.c 646
Module_id 30 Severity 2 : AR0231RCCB: RCCB mode for this sensor version is not supported 0x000354
Module_id 30 Severity 2 : src/devblk/nonfusa/cameramodule/MAX96712cameramodule/ar0231/CNvMMAX96712_96705_AR0231.cpp 66
Module_id 30 Severity 2 : AR0231RCCB: AR0231RCCBCheckPresence failed with NvMedia error 7
Module_id 30 Severity 2 : src/devblk/nonfusa/cameramodule/MAX96712cameramodule/CNvMMAX96712CameraModule.cpp 53
Module_id 30 Severity 2 : MAX96712: Sensor Detection failed with SIPL error 127
Module_id 30 Severity 2 : src/devblk/common/core/CNvMDeviceBlock.cpp 711
Module_id 30 Severity 2 : Init failed for module on link 0
DEVBLK_WORKER_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMDeviceBlockMgr.cpp: 435: ThreadFunc: Device block init failed(7f)
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 144
Module_id 30 Severity 2 : Device block action failed for block (action, block) 10
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 180
Module_id 30 Severity 2 : Failed to initialize device blocks

Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 436: Init: DeviceBlock manager init failed
nvsipl_camera: ERROR: NvSIPLCamera Init failed

nvsipl_camera: ERROR: Master initialization failed. status: 127

Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/CNvMSensorPipeline.cpp: 705: Deinit: Deinit() call in wrong state
Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 994: DeinitPipelines: Pipeline deinit failed for pipeline:0
Module_id 30 Severity 2 : src/devblk/fusa/cameramodule/common/utils/pwr_utils.cpp 464
Module_id 30 Severity 2 : nvccp_set_aggreg_pwr_off failed with status 2
Module_id 30 Severity 2 : src/devblk/nonfusa/devices/MAX96712DeserializerDriver/CNvMMax96712.cpp 566
Module_id 30 Severity 2 : MAX96712: CNvMMax96712::DoSetPower failed with SIPL error 127
Module_id 30 Severity 2 : src/devblk/common/ddi/DeserializerIF/CNvMDeserializer.cpp 42
Module_id 30 Severity 2 : CNvMDeserializer::SetPower failed with SIPL error 127
Module_id 30 Severity 2 : src/devblk/common/core/CNvMDeviceBlock.cpp 845
Module_id 30 Severity 2 : Deserializer SetPower failed with SIPL error 127
DEVBLK_WORKER_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMDeviceBlockMgr.cpp: 456: ThreadFunc: Device block deinit failed(7f)
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 144
Module_id 30 Severity 2 : Device block action failed for block (action, block) 40
Module_id 30 Severity 2 : src/core/CNvMDeviceBlockMgr.cpp 244
Module_id 30 Severity 2 : Failed to deinit device blocks

Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 1016: Deinit: DeviceBlock manager fails to deinit
Main: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/CNvMCamera.cpp: 49: ~CNvMCamera: CNvMCamera object fails to deinit

AR0231RCCB: RCCB mode for this sensor version is not supported and then the value 0x000354 is shown,

We referred to the below article in the forum

and found the message

nvmedia: ERROR: [AR0231RCCBCheckPresence:721] Chip Id register read failed

So we checked for the chip id register in the AR0231AT register reference document and it is mentioned as the (chip_version_reg) value for the register address 0x3000,

We have set it correctly in our emulation and still the error persists

Could you please provide us the source code for the SIPL query and device block driver, so that we can solve the issue?

Best regards,
Roshan

VickNV · August 21, 2023, 6:38pm

How can camera modules, like the Sekonix SF3325, be emulated? Does the emulation process primarily involve replicating register contents to avoid camera driver development, or are there additional considerations and steps to consider?

roshan.shenoy · August 22, 2023, 10:17am

Yes, in our emulation we replicate the register contents. This means that the driver is unaltered

Our camera emulation is able to replicate a GMSL camera

The front channel is injected with the synthetic camera data from our simulation along with the corresponding embedded lines
The back channel is emulated in the FPGA Hardware (see link below)

Video Interface Box X | IPG Automotive (ipg-automotive.com)

Also below is the link to our youtube video

Since the SIPL library is a closed library we are finding it difficult to identify the reason for this issue. In the past with the NvMedia ICP we didnot have this challenge

So we request your support in the form of a source code for the SIPL query and device block driver, such that we can update our systems to the latest versions for our use

Best regards,
Roshan

VickNV · August 22, 2023, 8:45pm

You might attempt to modify the register settings to make it appear as a revision 7 of ar0231.

roshan.shenoy · August 23, 2023, 1:04pm

Thankyou for the information,

Could you please let me know how do we change register setting to revision 7?

We had a look at the datasheet for AR0231 and found the register address 0x300E for the revision number with value 0x1234

Could you please let us know if this is the correct register address and value?

In addition, we used the following command to dump the registers for our emulation,

sudo ./nvmimg_cc -wrregs ddpx-a/dvp_m_ar0231_rccb_raw12_1920x1236_ab_ta.script -d 0 -w 1 -rdregs regdump_ar0231_1

please could you share us a command where we can dump all the registers ? so that we can also check if the right values are being set or not?

Best regards,
Roshan

VickNV · August 24, 2023, 12:32am

Please try setting the lowest byte of the register at 0x31FE as 0x37.

roshan.shenoy · August 24, 2023, 5:51pm

Hello,

Thanks a lot for the help, Our emulation works with SIPL now,

but still with driveworks-4.0 sample_camera we have an issue,
please find the log below

nvidia@tegra-ubuntu:/usr/local/driveworks-4.0/bin$ ./sample_camera --rig=/usr/local/driveworks-4.0/data/samples/sensors/camera/camera/rig.json
[24-08-2023 19:47:01] Platform: Detected DDPX - Tegra A
[24-08-2023 19:47:01] TimeSource: monotonic epoch time offset is 1692887056991915
[24-08-2023 19:47:01] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[24-08-2023 19:47:01] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[24-08-2023 19:47:01] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[24-08-2023 19:47:01] Platform: number of GPU devices detected 1
[24-08-2023 19:47:01] Platform: currently selected GPU device integrated ID 0
[24-08-2023 19:47:01] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/bin/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/bin/data/[.pak]'
[24-08-2023 19:47:01] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/bin/../data
[24-08-2023 19:47:01] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/bin/../data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/bin/../data/[.pak]'
[24-08-2023 19:47:01] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-4.0/data
[24-08-2023 19:47:01] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-4.0/data/': VirtualFileSystem: Failed to mount '/usr/local/driveworks-4.0/data/[.pak]'
[24-08-2023 19:47:01] SDK: No resources(.pak) mounted, some modules will not function properly
[24-08-2023 19:47:01] SDK: Create NvMediaDevice
[24-08-2023 19:47:01] SDK: Create NvMedia2D
[24-08-2023 19:47:01] SDK: use EGL display as provided
[24-08-2023 19:47:02] TimeSource: monotonic epoch time offset is 1692887056991915
[24-08-2023 19:47:02] TimeSource: Could not detect valid PTP time source at nvpps. Fallback to eth0
[24-08-2023 19:47:02] TimeSource Eth: Lost PTP time synchronizaton. Synchronized time will not be available from this timesource.
[24-08-2023 19:47:02] TimeSource: Could not detect valid PTP time source at 'eth0'. Fallback to CLOCK_MONOTONIC.
[24-08-2023 19:47:02] Initialize DriveWorks SDK v4.0.0
[24-08-2023 19:47:02] Release build with GNU 7.3.1 from no-gitversion-build against Drive PDK v5.2.6.0
[24-08-2023 19:47:02] Rig::fromFile: Loading rig file: /usr/local/driveworks-4.0/data/samples/sensors/camera/camera/rig.json
[24-08-2023 19:47:02] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
[24-08-2023 19:47:02] No valid data file found for camera:sample0 in parameter string: camera-name=SF3324,interface=csi-a,link=0,output-format=processed (using configuration folder /usr/local/driveworks-4.0/data/samples/sensors/camera/camera/)
[24-08-2023 19:47:02] rig::DatabaseOverlayer: Failed to open a file '/tmp/car_vin' - file likely does not exist - skipping overlay
onInitialize: creating camera.gmsl with params: camera-name=SF3324,interface=csi-a,link=0,output-format=processed
[24-08-2023 19:47:02] SensorFactory::createSensor() -> camera.gmsl, camera-name=SF3324,interface=csi-a,link=0,output-format=processed
[24-08-2023 19:47:02] CameraBase: pool size set to 8
[24-08-2023 19:47:02] SensorFactory::createSensor() -> camera.gmsl.master, 
[24-08-2023 19:47:02] CameraMaster::parseDevBlock Getting device info list.
[24-08-2023 19:47:02] devBlock: 1 Slave = 0 Interface = csi-a Camera_name = SF3324 Link = 0
[24-08-2023 19:47:02] Camera Match Name: SF3324 Description: Sekonix SF3324 module - 120-deg FOV, DVP AR0231-RCCB, MAX96705 linkIndex: 4294967295 serInfo.Name: MAX96705
[24-08-2023 19:47:02] Client, Setting up information for camera ID 0
[24-08-2023 19:47:02] Client, successfully found info for camera ID 0 bound to id 0
[24-08-2023 19:47:02] CameraClient: no NITO found at /opt/nvidia/nvmedia/nit/SF3324.nito
[24-08-2023 19:47:02] CameraClient: using NITO found at /opt/nvidia/nvmedia/nit/sf3324.nito
[24-08-2023 19:47:02] Initialize DriveWorks VisualizationSDK v4.0.0
[24-08-2023 19:47:02] Initialize DriveWorksGL SDK v4.0.0
onInitialize: Total cameras 1
onInitialize: getting image props 0
onInitialize: initilizing stream: 0
[24-08-2023 19:47:02] StreamConsumerGL: successfully initialized
[24-08-2023 19:47:02] StreamProducerCUDA: successfully initialized
Main: Starting master.
[24-08-2023 19:47:02] CameraGSMLMaster: starting...
[24-08-2023 19:47:02] SIPLMaster::SIPLMaster: Setting up master camera
[24-08-2023 19:47:02] Platform: 
[24-08-2023 19:47:02] Platform Config: 
[24-08-2023 19:47:02] Description: 
[24-08-2023 19:47:02] Number of device blocks: 1
[24-08-2023 19:47:02] Device Block : 0
[24-08-2023 19:47:02] 	csiPort: 0
[24-08-2023 19:47:02] 	i2cDevice: 0
[24-08-2023 19:47:02] 	Deserializer Name: MAX96712
[24-08-2023 19:47:02] 	Deserializer Description: Maxim 96712 Aggregator
[24-08-2023 19:47:02] 	Deserializer i2cAddress: 41
[24-08-2023 19:47:02] 	Simulator Mode: 0
[24-08-2023 19:47:02] 	Slave Mode: 0
[24-08-2023 19:47:02] 	Phy Mode: 0
[24-08-2023 19:47:02] 	Number of camera modules: 1
[24-08-2023 19:47:02] 	CameraModule index: 0
[24-08-2023 19:47:02] 		Name :SF3324
[24-08-2023 19:47:02] 		Description: Sekonix SF3324 module - 120-deg FOV, DVP AR0231-RCCB, MAX96705
[24-08-2023 19:47:02] 		Serializer name: MAX96705
[24-08-2023 19:47:02] 		Serializer description: Maxim 96705 Serializer
[24-08-2023 19:47:02] 		Serializer i2cAdress: 64
[24-08-2023 19:47:02] 			Sensor ID: 0
[24-08-2023 19:47:02] 			Sensor name: AR0231
[24-08-2023 19:47:02] 			Sensor description: OnSemi AR0231 Sensor
[24-08-2023 19:47:02] 			Sensor i2cAddress: 16
[24-08-2023 19:47:02] 			Sensor isTPGEnabled: 0
[24-08-2023 19:47:02] 			Sensor isTriggerMode: 1
[24-08-2023 19:47:02] 				 cfa: 39
[24-08-2023 19:47:02] 				 embeddedTopLines: 24
[24-08-2023 19:47:02] 				 embeddedBottomLines: 4
[24-08-2023 19:47:02] 				 inputFormat: 8
[24-08-2023 19:47:02] 				 height: 1208
[24-08-2023 19:47:02] 				 width: 1920
[24-08-2023 19:47:02] 				 fps: 30.0000000
[24-08-2023 19:47:02] 				 Embedded Data: 0
[24-08-2023 19:47:02] CameraMaster available outputs: 1
[24-08-2023 19:47:02] CameraClient: setting pipeline config for camera ID 0
[24-08-2023 19:47:02] CameraMaster: master initiation
MAX96712: Revision 2 detected
MAX96712: Enable periodic AEQ on Link 0
MAX96705: Pre-emphasis set to 0xaa
MAX96705: Revision 1 detected!
Sensor AR0231 RCCB Rev7 detected!
[24-08-2023 19:47:03] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:03] SIPLClient: ImageQueue timeout
Module_id 22 Severity 6 : NvMediaICPCreateEx 76
Module_id 22 Severity 6 : T19x VI version  0x000019
[24-08-2023 19:47:04] CameraClient: allocating RAW surfaces, nvmedia surface 210
[24-08-2023 19:47:04] Registering imagegroups for pipeline 0 NO COOKIES
[24-08-2023 19:47:04] CameraClient: allocating ISP surfaces 36
[24-08-2023 19:47:04] CameraClient: format not specified. Using h264 in Codec Header.
[24-08-2023 19:47:04] CameraMaster: bootstrap complete
Module_id 30 Severity 2 : src/control/common/camrangecheck.cpp 71
Module_id 30 Severity 2 : parameter is out of range
Module_id 30 Severity 2 : src/control/common/camrangecheck.cpp 306
Module_id 30 Severity 2 : Bad input parameter : Exposure Time
Module_id 30 Severity 2 : src/control/common/camrangecheck.cpp 349
Module_id 30 Severity 2 : Bad input parameter : EmbInfo
Module_id 30 Severity 2 : src/control/auto/SiplControlAuto.cpp 468
Module_id 30 Severity 2 : Bad input parameter currFrameEmbedInfo
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/blocks/CNvMISPBlock.cpp: 673: ProgramISP: GetNoiseProfile failed. status:1
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/blocks/CNvMISPBlock.cpp: 613: ProcessISP: ProgramISP failed
SIPL_ICP_ISP_0: /dvs/git/dirty/git-master_linux/camera/fusa/sipl/src/core/pipelineMgr/spmgr/pipeline/CNvMSensorPipeline.cpp: 1088: DoISPProcessing: ISP block process isp failed
[24-08-2023 19:47:04] CameraClient: Notification received from pipeline index:0 of type: NOTIF_ERROR_ISP_PROCESSING_FAILURE
[24-08-2023 19:47:05] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:05] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:06] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:06] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:07] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:07] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:08] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:08] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:09] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:09] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:10] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:10] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:11] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:11] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:12] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:12] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:13] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:13] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:14] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:14] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:15] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:15] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:16] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:16] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:17] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:17] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:18] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:18] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:19] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:19] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:20] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:20] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:21] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:21] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:22] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:22] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:23] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:23] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:24] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:24] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:25] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:25] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:26] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:26] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:27] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:27] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:28] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:28] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:29] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:29] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:30] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:30] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:31] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:31] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:32] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:32] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:33] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:33] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:34] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:34] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:35] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:35] SIPLNotifier: Event notification queue timeout
[24-08-2023 19:47:36] SIPLClient: ImageQueue timeout
[24-08-2023 19:47:36] SIPLNotifier: Event notification queue timeout

Could you please provide us an explanation for this issue?

Best regards,
Roshan

roshan.shenoy · August 24, 2023, 6:09pm

Hello,
I modified the rig.json file, based on the solution provided in one of the discussions

Please find below the snippet showing the modification done

    "rig": {
        "sensors": [
            {
                "name": "camera:sample0",
                "nominalSensor2Rig_FLU": {
                    "roll-pitch-yaw": [
                        2.35183835029602,
                        -0.275122250318527,
                        -0.685646653175354
                    ],
                    "t": [
                        0.921000003814697,
                        -0.105129279196262,
                        1.25
                    ]
                },
                "parameter": "camera-name=SF3324,interface=csi-a,link=0,output-format=processed,skip-eeprom=0",
                "properties": {
                    "Model": "ftheta",
                    "width": "1920",
                    "height": "1208",
                    "cx": "960",
                    "cy": "604",
                    "bw-poly": "0.0 0.000545421498827636 -1.6216719633103e-10 -4.64720492990289e-12 2.85224527762934e-16"
                },
                "protocol": "camera.gmsl"
            }
        ],
        "vehicle": {
            "valid": false
        }
    },
    "version": 2

Thanks for the help,

Best regards,
Roshan

VickNV · August 24, 2023, 6:28pm

Please create a separate topic for the issue on DriveWorks.

Additionally, I want to emphasize that camera development is beyond the scope of forum support, and camera emulation is a grey area. I recommend discussing your expectations with your NVIDIA representative in parallel.

VickNV · August 24, 2023, 6:31pm

Good to hear that the issues were resolved.