EasyManua.ls Logo

OXTS RT3000 - Page 121

OXTS RT3000
133 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
123
Offset
(bits)
Offset
(bits)
Length
(bits)
Length
(bits)
Type
Type
Units
Units
Factor
Factor
Offset
Offset
Table 61. Identifier 62Fh (1583), PosLocalNE
0 32 S m 0.0001 0 Northing PosLocalNorth
Table 62. Identifier 630h (1584), MilliTime
0 48 S ms 1 0
Milliseconds since the
start of GPS time
MilliTime
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 63. Identifier 633h (1587), IsoOrientation
0 16 S ° 0.01 0 ISO 8855 yaw angle IsoYawAngle
32 16 S ° 0.01 0 ISO 8855 roll angle IsoRollAngle
Table 64. Identifier 634h (1588), IsoVsVelocity
0 16 S m/s 0.01 0
ISO 8855 vehicle
system longitudinal
IsoVsLongitudinalVelocity
32
32
0.0001
0 Easting
PosLocalEast
Description Signal name
48
0.001
Seconds since the start
of GPS time
MilliTimeSeconds
16
16
0.01
0 ISO 8855 pitch angle
IsoPitchAngle
Description Signal name
Description Signal name
Description Signal name
Offset
(bits)
Offset
(bits)
Length
(bits)
Length
(bits)
Type
Type
Units
Units
Factor
Factor
Offset
Offset

Table of Contents

Related product manuals