Drive Software 10.0 and Best Hardware Choices

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
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 Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.7.1.8928
other

Host Machine Version
native Ubuntu 18.04
other

Hello,

We have purchased a Nvidia Drive Xavier AGX and successfully flashed Driveworks 4.0 on it, I have enabled display on it as well. We are planning to use the Nvidia Drive packages to create a localization project. We will be using Aceinna IMU/GNSS but for other sensors we will be using Nvidia supported devices. Current approach is to use Nvidia software for all functions it can support. Could you please answer the following questions? We are looking to purchase the sensor suite and have some questions before we make decisions on hardware.

Is there a localization module for Driveworks 4.0 like there is for Nvidia Drive Software 10.0? The last Nvidia Drive Software was 10.0 in 2019. When will Nvidia offer a new Drive SDK which can support Ampere GPU architecture?

Is it possible for us to convert the machine learning models that Nvidia provides in the Drive Software 10.0 to support newer GPUs? Is there a conversion toolkit available?

Is the Nvidia Drive Map available now to be integrated to Nvidia Drive SDK? If not, when is the scheduled release for customers to get access to HD Maps provided by Nvidia?

If Nvidia Deep Map cannot be used now what is the best alternative (TomTom, Here, …) to be used with Nvidia Drive SDK without any or least amount of issues? What does Nvidia recommend in this scenario?

In Nvidia Drive SDK front side camera samples, 2.3 Mega-pixel 60-degrees-HFOV cameras (Sekonix SF3325 we guess) are used. If instead we choose 8.3 Mega-pixel 70-degrees-HFOV cameras (Entron F008A070RM0AES) will that have any negative impact on the performance of the sample solutions?

In the “stereo” sample code we see a comment line about the possibility/assumption of (side-by-side) ZED camera usage. Does that mean we can integrate and use a ZED stereo camera without any issue? The model we are referring to is not automotive compliant. It is a USB-C cable camera.

All LIDARs have their driver support from driveworks 3.5 onwards. Is it possible for us to use the drivers on old Drive Software 10.0? Are the drivers backwards compatible?

Dear @ktmakwanaaceinna,

We are looking to purchase the sensor suite and have some questions before we make decisions on hardware

The supported sensors for each DRIVE release are listed at DRIVE Ecosystem Hardware and Software Components | NVIDIA Developer

Is there a localization module for Driveworks 4.0 like there is for Nvidia Drive Software 10.0? The last Nvidia Drive Software was 10.0 in 2019. When will Nvidia offer a new Drive SDK which can support Ampere GPU architecture?

There is no localization module, perception module in DW 4.0. These are part of only DRIVE SW. DRIVE OS 5.2.6 + DW 4.0 and DRIVE SW 10 are last releases for DRIVE AGX Xavier based platform. All future releases are targeted on Orin based platform

Is it possible for us to convert the machine learning models that Nvidia provides in the Drive Software 10.0 to support newer GPUs? Is there a conversion toolkit available?

The NVIDIA DNN models works on Volta/Turing based GPUs. These NVIDIA DNN models used only by perception module

Is the Nvidia Drive Map available now to be integrated to Nvidia Drive SDK? If not, when is the scheduled release for customers to get access to HD Maps provided by Nvidia?

No. Please check schedule related queries with your NVIDIA representative.

If Nvidia Deep Map cannot be used now what is the best alternative (TomTom, Here, …) to be used with Nvidia Drive SDK without any or least amount of issues? What does Nvidia recommend in this scenario?

DRIVE SW 10.0 provides map conversion tools to convert Tomtom, HERE maps to convert to Driveworks map format( Please check /path/to/DRIVE_SW_10.zip/DRIVE_SW_10.0_References/DRIVE_Software/DRIVE_AV_doxy_files/dwx_tools_section.html#dwx_tools_datamapping

In Nvidia Drive SDK front side camera samples, 2.3 Mega-pixel 60-degrees-HFOV cameras (Sekonix SF3325 we guess) are used. If instead we choose 8.3 Mega-pixel 70-degrees-HFOV cameras (Entron F008A070RM0AES) will that have any negative impact on the performance of the sample solutions?

DRIVE SW 10.0 does not support Entron cameras.

In the “stereo” sample code we see a comment line about the possibility/assumption of (side-by-side) ZED camera usage. Does that mean we can integrate and use a ZED stereo camera without any issue? The model we are referring to is not automotive compliant. It is a USB-C cable camera

Are you asking if sample_stereo_disparity sample can be run with any ZED camera?

All LIDARs have their driver support from driveworks 3.5 onwards. Is it possible for us to use the drivers on old Drive Software 10.0? Are the drivers backwards compatible?

No. Please check DRIVE SW HW ecosystem page supported sensors

Please make a note to create separate topics each issue to avoid cluttering of topics and better readability.