My rig json file does not let me record lidar data

I am currently running Driveworks v5.20 on NVIDIA Orin that has DriveOS: 6.0.10.0-36101120

Not sure if there is something wrong with the rig file, but I am trying to record only lidar data. I am able to visualize it live without issues, however I’ve been running into issues with recording. This is the rig json file that I am using:

{
“rig_version_major”: 2,
“rig_version_minor”: 0,
“rig”: {
“vehicle”: {
“name”: “default_vehicle”
},
“sensors”: [
{
“name”: “lidar:front”,
“type”: “lidar”,
“model”: “lidar.socket”,
“parameters”: {
“protocol”: “udp”,
“ip”: “192.168.1.100”,
“port”: “64896”,
“device”: “eqos_0”,
“scan-frequency”: “10”
},
“output”: {
“file”: “lidar.bin”
}
}
]
}
}

-I have also created a file at /tmp/ called car_vin which contains a dummy VIN number
-I have created a dummy_resources package to remove dependency on resources.pak

The command that I run for recording is
./recorder --dataPath=path to dummy_resources package path to rig json file.

At this point, I get an error that says
“AES key length incorrect”.

Furthermore, I am not sure how to proceed after trying all these workarounds. Is there something I can do to ensure I can record data via Orin?

Dear @mukund.viswanathan ,
Please use DRIVE AGX Orin General - NVIDIA Developer Forums to report issues on DRIVE AGX Orin.

Please file a new topic with details of lidar and used command to test live data with lidar replay (DriveWorks SDK Reference: Lidar Replay Sample) sample.

Also, check /usr/local/driveworks/data/samples/lidar/rig.json and DriveWorks SDK Reference: Rig File Format for lidar entries.

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