Criteria for timestamps in the dwSensorCamera_getTimestamp()

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
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


I noticed that the timestamps obtained by the dwSensorCamera_getTimestamp() function are different for Xavier and Orin.

  • Xavier + DRIVE OS 5.2.0: UNIX Time (counting up from Jan 1, 1970)
  • Orin + DRIVE OS 6.0.6: uptime (counting up from device power-on)

If I were to adapt the code I developed for the DRIVE AGX Xavier, I would be hampered by the different treatment of time. Is there an option to get the timestamp in UNIX Time as before?

Dear @LiltoneJG,
How about using PTP synced time stamp?

Thank you for your quick reply!
I’m tring to activate PTP, but dwContext_isTimePTPSynchronized() returns false

I think i should use the mgbe_2 port, where is it?

I was finally able to get UNIX Time with the following command

sudo chmod a+rw /dev/nvpps0

ref:
https://forums.developer.nvidia.com/t/bug-driveworks-sample-camera-report-can-not-create-time-sensor-with-open-nvpps-device-error-permission-denied/

1 Like

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