Please provide the following info (check/uncheck the boxes after creating this topic):
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
Target Operating System
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
SDK Manager Version
Host Machine Version
native Ubuntu 18.04
We are attempting to vet the Drive Chauffeur and Drive Concierge elements of Drive. It appears these were factored out of the DriveWorks in the move from 3.5 to 4.0. What are the correct element versions to allow compilation and test of the AV and IX components under Driveworks 4.0 ?
The last release for Xavier generation providing DRIVE CHAUFFEUR (AV) and DRIVE CONCIERGE (IX) is DRIVE Software 10.0. Please see the details at NVIDIA DRIVE SDK | NVIDIA Developer.
The Drive 10 Software package installs Driveworks 2.2 and an attempting to use this with Driveworks 4.0 yields a number of version conflicts.
Do clear instructions exist for making this configuration work or are Drive AV and Drive IX simply not supported by current Driveworks ?
No, DRIVE AV and DRIVE IX are only compatible with DriveWorks 2.2.
What is the suggested path forward for those attempting to develop path planning with Drive ?
Are you asking about development using the Path Perception module (NVIDIA proprietary DNN named PathNet)?
I am asking about the functionality contained in Drive AV and Drive IX in general. What is the proposed plan to access obstacle detection, mapping and path planning going forward ?
It’s not publicly available after DRIVE Software 10 so developers need to discuss the access with their nvidia representative accordingly.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.