Convert Capture Time stamp in NvSIPL driver to epoch time

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 used nvsipl driver to capture the raw frames from the camera. We also enabled timestamp logging.
We get below values.

Capture Timestamp (us) 11763516267 11763616269 11763716270 11763816271 11763916272 11764016274 11764116275 11764216276 11764316277 11764416279 11764516280 11764616281 11764716282 11764816284 11764916285

Values seem to be of only 11 digits also epoch conversion gives me strange values. I understand that its TSC ticks and not ptp time so doing direct epoch conversion makes no sense. Currently this is post recorded data values hence, as i remember once being told to append getTimestamp function in code to get the timestamp, we cant do that either.

How do I convert this to epoch time correctly in this scenario?

Thanks!!
Jishnu

Dear @jishnuw ,
did you use nvsipl sample and captured timestamp.
How do I convert this to epoch time correctly in this scenario?

can we get current TSC , epoch time and find the difference to old TSC timestamp to get corresponding epoch time? Does that work?

If the system is rebooted already and you have only TSC timestamp of recorded data, then it does not work

@SivaRamaKrishnaNV yes they used nvsipl and shared the camera timestamp dump csv. System has been rebooted after that. Since that is ticks and monotonic like clock we can’t recover right. Understood!! I was trying my luck.

Just for someone in the future who ends up here, essentially when capturing raw, it would be good to append or make another csv that also dumps UTC time is the conclusion if we want to match say like lidar timestamp and camera frame time stamp.

Thanks!!
Jishnu

1 Like