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
I’m using an Xsens MTI-710 sensor, and I’m experiencing a very low accuracy (up to about 50 meters, horizontally), when the sensor is connected to the Xavier board. If the sensor is connected to a Windows laptop using the Xsens MT Manager software, the precision drop to less than 5 meters.
In the following image it is possible to see the track recorded using the Xavier with the
recorder-tui application (the black line) and a set of 4 other records (green, red, yellow and cyan lines), made using a laptop and the Xsens MT Manager software.
The recording where made the same day, on the same vehicle (so the GPS antenna was not moved). The drawn black line is from the last of the loops we performed, so the sensor was working from many minutes and had enough time to align. Immediately after the end of the loop, we performed the recording on the same route using Xsens MT Manager software. Also, when recording with the laptop, and it find a very good position just in some seconds. The behavior is present both when we travel in a city zone or in open fields.
What could be the cause of this position error?
Also, there is some place where ALL the possible sensor parameters for the Xsens sensor are described?
Using the sample_sensors_info, the parameters showed are:
gps.xsens ? device=0[,frequency=100,xsens-raw-gps=true,time-smoothing=false,fifo-size=1024,baudrate=115200,stop-bits=2]
stop-bits parameters are for the serial connection, and the
fifo-size is the dimension of the buffer to store the received data.
- What behavior do the
In this forum thread (which is for the IMU section of the sensor):
is described that exists also the
slave=true parameter, and in the section from the
/usr/local/driveworks/tools/capture/configs/rwd/hyperion7_1/release.json file, another parameter is added (
index_table=off) that is not in the output from
sample_sensors_info. Both the
index_table parameters can not be found in the documentation (I checked also on the online documentation for driveworks-4.0 release).
index_tableparameters applicable also for the GPS configuration? What do they mean?
There are other un-documented parameters?
slave=truemeans that also the GPS sensor retains the configuration set previously using the Xsens utility?