Please provide the following info (tick the boxes after creating this topic): Software Version
[*] 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-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.1.10844
[*] 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
Hi sir
About the lidar, I have two questions:
1. whether the drive Orin support 1588v2 to do the time sync with the lidar? If yes, how to enable it?
2. How to check whether the lidar work normally?
Thanks!
@SivaRamaKrishnaNV
If we use Hesai P128 which in the support list, How to do time sync with the 1588v2,and how to check the pointcloud? can you give me an example?
Thanks!
Dear @sunjiandong,
I am yet to get information on time sync with the 1588v2.
Please confirm if the used platform is DRIVE AGX Xavier or DRIVE AGX Orin?
How to check whether the lidar work normally? how to check the pointcloud? can you give me an example?
For supported sensors, we have sample_record, lidar replay point cloud samples in DW already. Did you check them?
Dear @SivaRamaKrishnaNV
The platform is DRIVE AGX Orin.
And whether have a tool to see the point cloud in real time?
Can you give me a sample_record example for Lidar?
Dear @sunjiandong ,
If you are referring to the PTP sync protocol 1588v2, hesai specs don’t explicitly mention about the ptp version.
You would probably need to check with hesai on this.
@SivaRamaKrishnaNV
I do the time sync over the eqos_0 with the command “sudo ptp4l -i eqos_0 -S -m”, it will report sync failed. Please see the log:
nvidia@tegra-ubuntu:/etc$ sudo ptp4l -i eqos_0 -S -m
[sudo] password for nvidia:
ptp4l[56267.975]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[56267.975]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[56275.572]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[56275.572]: selected local clock 48b02d.fffe.a471fe as best master
ptp4l[56275.572]: port 1: assuming the grand master role
ptp4l[56276.573]: timed out while polling for tx timestamp
ptp4l[56276.573]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[56276.573]: port 1: send sync failed
ptp4l[56276.573]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[56292.574]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[56300.181]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[56300.181]: selected local clock 48b02d.fffe.a471fe as best master
ptp4l[56300.181]: port 1: assuming the grand master role
ptp4l[56301.182]: timed out while polling for tx timestamp
ptp4l[56301.182]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[56301.182]: port 1: send sync failed
ptp4l[56301.182]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[56317.183]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[56325.107]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[56325.108]: selected local clock 48b02d.fffe.a471fe as best master
ptp4l[56325.108]: port 1: assuming the grand master role
ptp4l[56326.109]: timed out while polling for tx timestamp
ptp4l[56326.109]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
Thanks!