EasyManua.ls Logo

OXTS RT3003 - Page 125

Default Icon
132 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RT User Manual
Revision: 190204
125
8 8 U 1 0
Trigger count,
increments with each
new trigger
TriggerCountRising
16 16 U s 0.0002 0 Time since last trigger TriggerTimeRising
32 32 U m 0.001 0
Distance with hold
since last trigger
TriggerDistanceRising
Table 71. Identifier 62Fh (1583), PosLocalNE
Offset
(bits)
Length
(bits)
Type
Units
Factor
Offset
Description Signal name
0 32 S m 0.0001 0 Northing PosLocalNorth
32 32 S m 0.0001 0 Easting PosLocalEast
Table 72. Identifier 630h (1584), MilliTime
Offset
(bits)
Length
(bits)
Type
Units
Factor
Offset
Description Signal name
0 48 S ms 1 0
Milliseconds since the
start of GPS time
MilliTime
0 48 S s 0.001 0
Seconds since the start
of GPS time
MilliTimeSeconds
48 8 S s 1 0 GPS UTC offset UtcOffset
Note: MilliTime and MilliTimeSeonds both refer to the same bits on the CAN bushowever they are
decoded twice with a different scale in the DBC file. MilliTime needs to be stored as a signed 64-bit integer
value as the current value already exceeds the limits of a 32-bit integer, however this is not supported by
all CAN software. To overcome that problem MilliTimeSeconds can be stored as a 32-bit double-precision
value, however limitations in the double-precision format mean there may be an error of up to 5 ms and
the resulting decimal numbers may contain rounding errors. Where possible MilliTime should be used,
otherwise use MilliTimeSeconds with care.
Table 73. Identifier 633h (1587), IsoOrientation
Offset
(bits)
Length
(bits)
Type
Units
Factor
Offset
Description Signal name
0 16 S ° 0.01 0 ISO 8855 yaw angle IsoYawAngle

Table of Contents

Related product manuals