110
Supporting information:
PGN 61444
Note: Value sent to server is already adjusted with bitgain. Since data as sent as U32, value after
floating point is ignored.
Axle weight:
Total mass imposed by the tires on the road surface at the specified axle.
Data Length: 2 bytes
Resolution: 0.5 kg/bit, 0 offset
Data Range: 0 to 32,127.5 kg Operational Range: same as data range
Type: Measured
Supporting information:
PGN 65258
Note: Value sent to server is already adjusted with bitgain. Data sent to server is a sum of all
weights per tire per specific axle [1-15]. I.e. axle[1].total_weight, axle[2].total_weight etc. Since
data is sent as U32, value after floating point is ignored.
Engine total hours of operation:
Accumulated time of operation of engine.
Data Length: 4 bytes
Resolution: 0.05 hour/bit, 0 offset
Data Range: 0 to 210,554,060.75 hour. Operational Range: same as data range
Type: Measured
Supporting information:
PGN 65253
Note: Value sent to server is already adjusted with bitgain. Since data as sent as U32, value after
floating point is ignored.
Vehicle identification number:
Vehicle Identification Number (VIN) as assigned by the vehicle manufacturer.
NOTE The ASCII character “*” is reserved as a delimiter.
Data Length: Variable – up to 200 characters (“*” delimited)
Resolution: ASCII, 0 offset
Data Range: 0 to 255 per byte Operational Range: same as data range
Type: Measured
Supporting information:
PGN 65260
Note: Firmware expects VIN to fit into 24 bytes. According to captured VIN length either 1/2/3 IO
ID’s will be sent to server (8 Bytes each). I.e. if VIN length <= 8, only one IO ID (105) will be sent
to server, if VIN length >9 and <= 16, then two IO ID’s will be sent to server (105,106), and if VIN
length > 16 and <= 24 then three IO ID’s will be sent to server (105,106,107).
FMS-standard SW version supported:
Information that identifies which issue level of the FMS-standard document the software
included in the FMS gateway
supports. Four bytes, representing xx.yy type revision level identification.
