Please provide the following info (tick the boxes after creating this topic):
Software Version
[*] DRIVE OS 6.0.10.0
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
2.1.0
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
Issue Description
why does the latest driveworks even doesn’t support the device? protocol specifies a device id to be 0x22, while VeloView, webinterface and wireshark can evidence the presence on the Lidar on network.
Ive got both VELO_VLP16 and VELO_VPL16HR, why such discrepancy?
Error String
root@6.0.10.0-0009-build-linux-sdk:/usr/local/driveworks/bin# ./sample_lidar_replay --protocol=lidar.socket --params=device=VELO_VLP16HR,ip=192.168.2.202,port=2368,scan-frequency=10,decoder-path=./libsample_nv_lidar_plugin.so --show-intensity=true
ProgramArguments: Missing argument 'dwTracePath' requested
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to create bus connection: Host is down
Starting my sample application...
[16-05-2025 15:57:30] Platform: Detected Generic x86 Platform
[16-05-2025 15:57:30] Adding variable DW_Base:DW_Version
[16-05-2025 15:57:30] Added variable DW_Base:DW_Version
[16-05-2025 15:57:30] Platform: number of GPU devices detected 1
[16-05-2025 15:57:30] Platform: currently selected GPU device 0, Resource Data Dir: trt_08_06_12_04, Arch: ga1xx-discrete
[16-05-2025 15:57:30] Platform: currently selected GPU device discrete ID 0
[16-05-2025 15:57:30] Context::mountResourceCandidateDataPath resource FAILED to mount from './resources': VirtualFileSystem: Failed to mount './resources/resources.pak'
[16-05-2025 15:57:30] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.20/bin/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.20/bin/data/resources.pak'
[16-05-2025 15:57:30] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.20/bin/../data
[16-05-2025 15:57:30] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.20/bin/../data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.20/bin/../data/resources.pak'
[16-05-2025 15:57:30] Context::findDataRootInPathWalk data/DATA_ROOT found at: /usr/local/driveworks-5.20/data
[16-05-2025 15:57:30] Context::mountResourceCandidateDataPath resource FAILED to mount from '/usr/local/driveworks-5.20/data': VirtualFileSystem: Failed to mount '/usr/local/driveworks-5.20/data/resources.pak'
[16-05-2025 15:57:30] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.20/bin/../lib/libdw_base.so.5.20
[16-05-2025 15:57:30] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.20/targets/x86_64-Linux/lib/libdw_base.so.5.20
[16-05-2025 15:57:30] SDK: No resources(.pak) mounted, some modules will not function properly
[16-05-2025 15:57:30] [16-05-2025 15:57:30] Initialize DriveWorks SDK v5.20.24
[16-05-2025 15:57:30] [16-05-2025 15:57:30] Release build with GNU 9.3.0 from buildbrain-branch-0-gb4c0b405b15
[16-05-2025 15:57:30] SensorFactory::loadPluginLibraryHelper:Succeed to load dynamic lib - /usr/local/driveworks-5.20/bin/../lib/libsensor_plugin_public_radar.so
[16-05-2025 15:57:30] SensorFactory::createSensor() -> lidar.socket, device=VELO_VLP16HR,ip=192.168.2.202,port=2368,scan-frequency=10,decoder-path=./libsample_nv_lidar_plugin.so
[16-05-2025 15:57:30] Found driver: lidar.socket
[16-05-2025 15:57:30] LidarSocket::getParameters, return-mode not specified. Using default value 2
[16-05-2025 15:57:30] hfov-start is empty, default value 0 will be used
[16-05-2025 15:57:30] hfov-end is empty, default value 360 will be used
[16-05-2025 15:57:30] Destination IP address, Horizontal Resolution is used only by OUSTER and Hesai Lidars
[16-05-2025 15:57:30] Return Mode is used only by Velodyne and Hesai Lidars
[16-05-2025 15:57:30] Horizontal FOV is used only by Ouster, Velodyne and Hesai Lidars
[16-05-2025 15:57:30] Driveworks exception thrown: DW_FAILURE: DecoderVelodyne::processStatus, device type does not match product ID 0x22
terminate called after throwing an instance of 'std::runtime_error'
what(): [2025-05-16 15:57:30] DW Error DW_FAILURE executing DW function:
dwSAL_createSensor(&m_lidarSensor, params, m_sal)
at samples/sensors/lidar/lidar_replay/main.cpp:149
Aborted (core dumped)
root@6.0.10.0-0009-build-linux-sdk:/usr/local/driveworks/bin#
I found similar query threads Lidar Connection to Nvidia Drive AGX - #13 by hitesh.pandya1
any status on this yet? : Cannot record LiDAR(VLP16-HiRes) - device type does not match product ID 0x22 - #8 by SivaRamaKrishnaNV