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
We have got Livox Lidar mid-360, and have the source code for the lidar to launch and start working, we are trying to integrate the Lidar into the DRIVE, and are following the Documentation to create a custom plugin for the same, however, there are several stages of building this, and considering the source code from Livox, we are trying to map the driveworks function table with Livox SDK c++ file.
We need guidance on what are the steps needed to create this mapping from driveworks and livox, example, handling the sensors, starting the sensor and parsing the data.
we can think of two ways but needed support whether we on right track for this:
1.can we use NVIDIA’s sample plugin i.e NV_Lidar and set the decoder path with .so that of Livox, which would mean rebuilding the sample_lidar_replay script and running the lidar from this.
2. or build custom plugin and just only map the function table from Driveworks using livox_lidar_sdk.cpp, if so, do we need to follow a similar pattern for the NV_Lidar plugin?