IO1 -> D1 (digital sensor D1)
IO2 -> D2 (digital sensor D2)
IO3 -> D3 (digital sensor D3)
IO4 -> D4 (digital sensor D4)
IO9 -> X1 (analogue sensor X1)
IO10 -> X2 (analogue sensor X2)
IO11 -> X3 (analogue sensor X3)
IO72 -> T1 (temperature sensor T1)
IO73 -> T2 (temperature sensor T2)
IO74 -> T3 (temperature sensor T3)
IO239 -> SS (ignition state 0/1)
IO66 -> D (external power)
IO67 -> B (battery)
All other IO events are stored in IOcode variables: IO221, IO61, ... What events are received for a specific tracker can be viewed in the "Latest messages" panel:
In order for the event to be displayed in the service's interface (tooltip, plotting) it is necessary to define it in the script:
DEF IO42 : "Fuel level"
When parsing attributes, they are interpreted as positive integers. But some values may actually have negative values, or they need to be divided by a given value. The necessary transformations are made by the following script operators:
LET IO2 = @TOSIGNED IO2 2
LET IO3 = IO3/1000;
The second parameter of the @TOSIGNED function determines the dimension of the incoming attribute in bytes. Valid values are 1,2 or 4.
Based on the incoming attributes, you can create events in the VIALATM service:
IF IO247 > 0 THEN EVENT "Crash detection"