Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”): Software Version 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 Operatin…

Dear @hitesh.pandya1 , Could you confirm if you are able to open the lidar configuration page via URL with Lidar IP? Did you make any changes in network configuration files? Did you check running DW Lidar sample? If so, could you share the output log?

LiDAR is not getting connected. The lights on the dongle are both red and blinking. Not able to connect to LiDAR. Have also tried connecting to 3/4 HSD connector but the result is the same. The network configuration file is as attached. The changes have been done for eth0. Tried changing eth0:400 to…

Please note that the LiDAR configuration shown in the image above is when the LiDAR is connected to the host machine. When we connect the LiDAR to the Drive AGX, the both dongle LEDs are blinking and not able to access LiDAR

Thanks for the input. Have already tried the link. Also, tried changing ifconfig into 2 sections as mentioned but doesn’t help. Can you please check the details that I have shared and see if something is missing.

Dear @hitesh.pandya1 , Could you change the Lidar IP to 192.168.1.211 via lidar configuration page on host and check connecting on target again?

Thanks for the input. Does not make any difference. Both the lights on the dongle are flickering red/orange. Changing Channel A to Channel B and vice-versa has no impact. Internet connectivity on both channels.

Just to clarify. On the host machine the lidar works with Veloview application but does not work with driveworks sample. The error is “device type does not match product ID 0x22” ./sample_lidar_replay --protocol=lidar.socket --params=device=VELO_VLP16HR,ip=192.168.1.201,port=2368,scan-frequency=25 …

The image showing the model of our Velodyne Lidar is attached herewith. [20210825_143227]

Dear @hitesh.pandya1 , Could you check Cannot record LiDAR(VLP16-HiRes) - device type does not match product ID 0x22 if it helps. Please check the product ID in lidar packets

Lidar Connection to Nvidia Drive AGX

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General

SivaRamaKrishnaNV August 24, 2021, 3:22pm 6

Dear @hitesh.pandya1,
Could you check the discussion on Drive AGX Xavier : try sample_lidar_replay buy cannect fail if it helps?

Topic		Replies	Views
Drive AGX Xavier : try sample_lidar_replay buy cannect fail DRIVE AGX Xavier General driveworks-lidar	14	1672	January 25, 2021
Launching the velodyne lidar VLP16 is getting failed, this is while it is working with ROS DRIVE AGX Xavier General driveworks-lidar	9	3027	March 23, 2022
VLP-16HR device is provided with lidar.socket, however Driveworks is rejecting it DRIVE AGX Orin General driveworks-lidar	13	473	June 20, 2025
Connection Issue while connecting Velodyne Lidar VLP-16 DRIVE AGX Orin General driveworks-lidar	9	514	June 25, 2024
Integrating Velodyne LiDAR DRIVE AGX Xavier General	1	1661	February 13, 2020
Hesai Lidar Connection error DRIVE AGX Xavier General	12	1599	November 5, 2019
LIDAR INTEGRATION WITH DRIVEWORKS DriveWorks	6	1126	November 15, 2019
Connect lidar to NVIDIA DRIVE AGX on J14 DRIVE AGX Xavier General drive-hardware-setup , drive-os-networking	3	910	October 26, 2020
Cannot record LiDAR(VLP16-HiRes) - device type does not match product ID 0x22 DRIVE AGX Xavier General driveworks	5	1154	November 30, 2020
Problem connecting lidar to NVIDIA Drive AGX DRIVE AGX Xavier General driveworks-lidar	4	1138	November 12, 2021

Lidar Connection to Nvidia Drive AGX

Related topics