DMI File
The generic DMI (Distance Measurement Instrument) is used to input a body velocity from a wheel speed encoder (odometer) for example. It's basically just a time stamped velocity along the vehicle X axis expressed in m.s^-1
Conventions
Qinertia expect a velocity information in m.s^-1 and expressed in the vehicle X axis reference frame. The velocity is positive forward and negative backward.
ASCII DMI Format
This is the easiest way to input odometer data using a CSV like text file format.
The file format is composed of an optional header followed by odometer velocities stored line by line. If Qinertia doesn't find the header, the default configuration values are used. The file can use either Windows, Unix or Linux line ending conventions and should use UTF-8 encoding.
ASCII header
The header is used to configure how Qinertia should parse and import the file. The header always starts with the $qdmi
magic keyword to identify it. Then each parameter can be set using a succession of <param>:<value>
pairs stored line by line.
If there is no header or the parameter is not present in the file, Qinertia will use the default value that is indicated in bold.
Param | Optional | Description |
---|---|---|
| DMI ASCII file format version, should be set to 1 | |
| DMI data time stamp format:
Default value is | |
| GPS week number to use in case If |
ASCII data
he ASCII DMI data part is just a succession of velocity measurement stored line per line. Each column field is separated by a tabulation '\t'
or semicolon ';'
character.
Field | Type | Unit | Optional | Description |
---|---|---|---|---|
| - | - | The velocity data time stamp expressed in the format specified by the | |
| double | m.s^-1 | Vehicle velocity along the body X axis. |
Example
The example below shows a few DMI measurements with the file header:
Zero Velocity Update
Qinertia can both use zero velocities updates generated by your system as shown in the example above
Binary DMI Format
For now, there is no binary file format for the DMI.