Purpose and particularities
bus header for OBD/UDS (hexadecimal) 0 = no protocol
or specific Can Bus Identifier for protocol
Can Bus Identifier (hexadecimal)
when using OBD/UDS/TP2.0: Address for querying the device
0 -> Big endian; 1-> little endian; 2 -> VEMS (serial);
4 -> IEEE-754 float (Lenght=4)
First byte in Can Bus packet (0-7)
Length in bytes - 1, 2 or 4
for AINs: Attenuation strength 0-249 (0 = no attenuation)
if the value is negative, please do not tick the box
moves the bit within the value to the right by position X
Masks the value before shift (0 -> no mask applied)
Sensor name (maximum 15 characters, no special characters)
Can Bus value gets multiplied by this number
Result= ((Can Bus value & MASK)>>SHIFT) *INITCALC+INITOFFSET
after multiplication this value is added
OFF, MAP (linear analog sensors); NTC (3 constants and pull-up
resistor (Steinhart-Hart))
Internal analog sensor only; enables input pin polling
reference sensor: only if the RefValue for this sensor is exceeded,
warning is active
Reference value for enabling the alert
Popup active when exceeding or falling below the warning value
6.1 Name encoding of TRI/TRX files
Our TRI/TRX files always have the following name:
𝑋 − 𝐴𝐵𝐶 − 𝑋. 𝑇𝑅𝐼 or 𝑋 − 𝐴𝐵𝐶 − 𝑋. 𝑇𝑅𝑋
The first letter identifies the protocol used. More information on the protocols can be found in
Chapter 6.2
The letters two to four identify the engine code letter or ECU. The engine code DAZA becomes X-
DAZ-X or a Syvecs ECU becomes X-SYV-X here. For freely programmable ECUs, however, the names
can also be longer than three digits (e.g. MaxxECU -> X-Maxx-X). The maximum number of digits
including ending is 15 characters.
The fifth or fifth last letter in the name of the TRI/TRX file indicates the units or languages used to
name the sensors:
• -G stands for the language German and units metric