Overview
Every status can have extra information associated with it – values of
analog or digital sensors, OBD2 PID/DTC data, J1939 SPN/FMI and custom
Trakopolis extra data.
Terminal Analog Sensors
Depending of type terminal can have analog sensors associated with it. By
default they are not active and website needs to be used to enable them for
terminal. Sensor is identified by numeric sensor number.
Trakopolis stores raw value in the database, calculation formula and units.
Sensor data is a float value. Every time when sensor data is displayed or used
in report, recalculation is done using calculation formula. Division-related
measurement system is not used, so kilometers value won’t be converted
automatically to miles.
Terminal Digital Sensors
Similar to analog sensors, digital sensors needs to be activated prior to
usage. Sensor is identified by numeric sensor number.
Digital sensor value is either true (1) or false (0). There are no any
recalculations done by Trakopolis system.
Trakopolis Extra Data
Trakopolis-specific values that can be associated with status are divided into
3 types:
- Float
- Set
- String
Extra Data params are identified by unique string code.
Float values may have measurement units associated and can be recalculated
using division-specific measurement system (km => mi, C => F), otherwise
value is returned “as is”.
Set type values are restricted by list of possible string values (“OptionKey”)
that parameter can take. There is special dictionary of available option keys
and corresponding values. For example, “CENTRIFUGE_MESSAGE_TYPE” code,
OptionKey=”06” has “Critical Fault Detected” option value
String type value represent single string value with no restrictions on
it.
OBD PID
OBD PID values are identified by pair of PID Code and PID param number. Some
PID codes can represent 2 different values, for example single 2-bytes value
actually stores two 1-byte values for different sensors with different
meaning.
OBD PID records have float value associated with it. Float values may have
measurement units associated and can be recalculated using division-specific
measurement system.
OBD DTC
OBD DTC values are identified by unique string OBD DTC code. Value stored in
Trakopolis system is not changed and not converted.
J1939 SPN / FMI
J1939 SPN value is identified by SPN Number property.
Depending on SPN number, value can be 2 types:
- Float
- State
Float values may have measurement units associated and can be recalculated
using division-specific measurement system.
State type value are restricted by list of possible integer values. Every state
has associated state name.
J1939 SPN value may have FMI number associated with it. FMI stores extra
information about failure type. If FMI number is associated with J1939 SPN
record, then Float or State values may be empty.