Frequently Asked Questions

Where can I get answers to my NVIDIA^® DriveWorks questions?

On the NVIDIA DRIVE Platforms forum, you can search through discussions on questions posed by the community. If you can also ask your own questions. You must create an account before you can access this information.

https://devtalk.nvidia.com/default/board/376/general/

Which sensors are currently supported?

For the full list of supported sensors is available here: Sensors .

Integration with custom sensors is also possible: Integrating with Custom Sensors .

Is DriveWorks thread safe?

Currently, the APIs that DriveWorks modules expose do not follow any thread-safety paradigm to avoid the overhead of memory locks. Exceptions are individually documented.

How to achieve the maximum USB 3.0 write throughput for data acquisition?

NVIDIA testing easily achieved USB3.0-SSD write speeds between 300- to 400- megabytes /second, depending on the brand of the USB 3.0 SSD. NVIDIA has tested extensively with Samsung 850/750 Evo SSD with ext4 format.

For guidance on optimizing data storage to your USB disk, see High Throughput Recording in this guide.

Why does does the log show 'Unable to Create YUV Surface'

If you are trying to record and you see an output such as the following, try reducing fifo-size in the config file.

Error while starting /usr/local/driveworks/tools/recorder:

NvMediaImageCreateNew: Unable to create YUV surface

What are the networking settings needed for the best results for Lidar capture ?

For guidance on configuring network settings for Lidar capture, see Lidar in this guide.

Can the data I recorded with the NVIDIA DRIVE™ PX 2 be used with NVIDIA DRIVE™ AGX Developer Kit?

If the recorded data is RAW or LRAW, you can use it on NVIDIA DRIVE PX 2 or NVIDIA DRIVE AGX Developer Kit.

If the data was recorded on NVIDIA DRIVE PX 2 and that data was processed (output as an .h264 video) before being recorded, compatibility with NVIDIA DRIVE AGX Developer Kit depends on how the data was processed

Processing	DW Applications
.h264 processed with HW ISP	Compatible
.h264 processed with SoftISP(?)	Likely compatible, but unsuitable

Note that SoftISP has been deprecated, so videos processed using it are not guaranteed to be ideal for our applications

How can I troubleshoot issues with GMSL Cameras?

• The first step is to identify whether the issue lies within NvMedia or within DriveWorks. NvMedia and DriveWorks provide samples of similar functionality; the output of these samples can be compared to identify the potential source of the issue.
  • NvMedia's nvsipl_camera

Why does the log show 'Stream doesn't contain valid AUD units'?

Driveworks requires h264/h265 videos to have AUD units. Otherwise it is unable to create index table and seeking is not available. For Driveworks recordings it is always take care of. If using external video AUDs can be added by the following ffmpeg command:

• ffmpeg -y -i your.h264 -c:v copy -bsf:v h264_metadata=aud=insert your.h264
• ffmpeg -y -i your.h265 -c:v copy -bsf:v hevc_metadata=aud=insert your.h265