SIPL timestamps invalid

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

Hello,

We are seeing an issue with SIPL where the INvSIPLClient::ImageMetaData does not have a valid timestamp populated in the frameTimestampInfo. The DevBlkCDIFrameTimestamp::frameTimestampValid field is always false and the DevBlkCDIFrameTimestamp::frameTimestamp field is always 0.

We are using IMX728 cameras & have checked with our driver supplier (Quanta) and they said this is not something that they can control. We also ran a test with default IMX728 drivers that ship with DriveOS and the timestamp field is also not populated when using those.

Questions:

  1. Why would the timestamp field not be populated?
  2. What does the timestamp stored in the frameTimestampInfo represent semantically? The docs state “Holds parsed embedded data frame timestamp info for the captured frame.” Is that the timestamp of the capture? The timestamp when SIPL received the image? Something else?

Thank you!

Some sensors provide timestamps as part of embedded data, which is sent from the sensor, and then the frameTimestampInfo.frameTimestamp field is set accordingly. However, it seems that the relevant timestamp data is not present in the embedded data from the Valeo IMX728 camera. As a result, both frameTimestampInfo.frameTimestamp and frameTimestampInfo.frameTimestampValid are set to zero.

To understand the exact meaning of the timestamp and why it might not be populated, I recommend checking with your camera vendor to confirm whether the sensor you are using supports timestamp data.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.