View source for Template:FM36 CAN adapters

==Purpose of CAN adapters LV-CAN200 and ALL-CAN300==

LV-CAN200 is used to read data from light vehicles, while ALL-CAN300 is used to read data from any type of transport: light vehicles, trucks, buses, agriculture transport and other special transport. Using these adapters {{{model|FM36YX}}} device is able to collect and send vehicle data.

{| class="wikitable"
|+
! style="width: 200px; background: black; color: white;"  | Parameter
! style="width: 300px; background: black; color: white;" | Value
|-
! style="text-align: left; vertical-align: top;" | Supply voltage
| style="text-align: left; vertical-align: top;" | +9..+50 V
|-
! style="text-align: left; vertical-align: top;" | Power supply current
| style="text-align: left; vertical-align: top;" | Average 10 mA. Max (peak) 100 mA
|-
! style="text-align: left; vertical-align: top;" | Working temperature
| style="text-align: left; vertical-align: top;" | -40..+85 ºC
|-
! style="text-align: left; vertical-align: top;" | Max working humidity
| style="text-align: left; vertical-align: top;" | 60 % (non condensate).
|-
|}

==LV-CAN200 and ALL-CAN300 program number selection==
LV-CAN200 or ALL-CAN300 must be set to program number which depends on the vehicle model. '''Needed program number is always written on LV-CAN200 or ALL-CAN300 mounting scheme.''' Please contact Teltonika sales manager to get the latest supported vehicle list and mounting scheme for your vehicle providing information about car manufacturer, model and year.

===LV-CAN200 and ALL-CAN300 program number configuration via SMS command===
----
LV-CAN200 and ALL-CAN300 program number can be set remotely, using SMS command, where X is new program number value (more CAN commands can be found in section [[{{{model|FM3622}}}_SMS/GPRS_command_list|SMS/GPRS command list]]):<br/>''"lvcansetprog X"''<br/>

===Selecting LV-CAN200 and ALL-CAN300 program number manually===
----

[[Image:Fmb120_adapter_led.png|300px|right]]
Steps to set program number:
* Hold SWITCH down until LED stars blinking.
* Release the SWITCH.
* Then LED starts blinking and counting first digit of program number (one blink means digit 1, two blinks mean digit 2 etc).
* To stop counter push SWITCH.
* Release the SWITCH, then LED starts blinking and counting second digit of program number.
* To stop counter push SWITCH.
* Release the SWITCH, then LED starts blinking and counting third digit on program number.
* To stop counter push SWITCH.
* Release SWITCH, if programming is successful LED will blink 10 times.

==SIMPLE-CAN - contactless CAN-BUS reader==

[[Image:Fmb120_simplecan.png|300px|right]]
SIMPLE-CAN is a contactless adapter used to read vehicle CAN data with LV-CAN200 or ALL-CAN300. If LV-CAN200 or ALL-CAN300 connection requires two CAN lines to get all data, then two SIMPLE-CAN readers are required.

<font size="+1">Technical details</font>
* Power supply voltage +9..+63 V.
* Power supply current: standby 1.6 mA, active 8.3 mA @ 12 V; standby 0.91 mA, active 4.3 mA @ 24 V.
* CAN-BUS speeds from 33.33 to 500 kb/s.
* Automatically sets CAN Low, CAN High polarity.
* Automatically adjusts signal level and speed.<br/><br/>

SIMPLE-CAN works in the '''listening mode only''', so that not all the data available on the CAN-BUS may be received using this solution. '''The device automatically sets CAN L/H polarity''', but the calibration has to be always performed during installation process. Connection of previously calibrated unit to another car needs new calibration because the reader '''automatically adjusts signal level and speed''' to different CAN buses. The device also '''automatically adapts''' to the found '''noise level'''.

[[Image:Fmb120_simplecan_pinout.png|800px]]
<br>
When power supply is connected, the LED shines continuously. It means that device is waiting for calibration. '''Calibration process''' has to be carried out when CAN-BUS twisted pair is tightened on SIMPLE-CAN and when ignition is ON. Please press the switch briefly and wait for the LED to start blinking every second. Automatic calibration process takes up to 10 seconds depending on the vehicle's model. Correct calibration process is confirmed by LED starting to blink every 2 seconds (when the CAN-BUS is active). When the CAN-BUS enters sleep mode, SIMPLE-CAN device also enters sleep mode and takes 1.6mA @ 12V. In the sleep mode LED does not shine. If after calibration process LED shines continuously, it means that device is not calibrated yet, CAN-BUS transmission has failed or ignition during calibration was not ON.

==Connecting {{{model|FM36YX}}} CAN adapters ALL-CAN300 and LV-CAN200==

{{{model|FM36YX}}} connection with CAN adapter is different than with other FM devices, when connecting ALL-CAN300 and LV-CAN200 adapters. {{{model|FM36YX}}} has closed USB connector and CAN adapter is connected with INPUT 5 and INPUT 6 wires as shown in figure below.
<br>
[[File:LV-CAN200 ALL-CAN300 Adapter connection cable pinout.png|800px]]

<br>
Connect LV-CAN200/ALL-CAN300 Pin 5 to {{{model|FM36YX}}} Pin 12 (INPUT 5) or Pin 6 (INPUT 6) and connect light vehicle CAN adapter to other end of the cable.<br/>
Connect CAN adapter Pin 1 and Pin 2 to car's CAN bus. CAN interface location of the supported light vehicle is described on mounting scheme. Connect car power supply lines to Pin 3 positive, Pin 4 negative.<br/>
Pin 9 and 10 connections are optional depending on the exact car model.<br/>For exact pinout see the sticker of light vehicle CAN adapter.<br/>


{| class="wikitable" style="border-style: solid; border-width: 0px"
|+ 
|-
| style="text-align: left; background: #F6F6FB;"         | [[Image:Bw_nb.png|50px]]
| style="text-align: left; background: #F6F6FB;"         | '''ATTENTION! For detailed diagram of connection between adapter and light vehicle please contact Teltonika sales representative and provide information about car manufacturer, model and year.'''
|-
| style="text-align: left; background: #F6F6FB;"         | [[Image:Bw_nb.png|50px]]
| style="text-align: left; background: #F6F6FB;"         | '''ATTENTION! Do not swap CAN L and CAN H lines.<br/>Do not swap power supply lines. Make sure that voltage does not exceed 30V. Power supply lines should be connected at the end of installation work.'''
|}

=={{{model|FM36YX}}} ALL-CAN300 and LV-CAN200 parameters configuration==
===SCAN function===
Scan function can be used when {{{model|FM36YX}}} is connected to CAN adapter and PC (Figure below). After connection is made Press scan button to see available CAN parameters (Note, that car engine must be started). Enable CAN data which needs to be sent to server and save configuration by pressing “Save” button. 
<br> [[Image:FM36YX_scan_function.png|589px]] <br>
CAN bus data which can be read from your car is shown in “Light Vehicles Can adapter supported cars” document.

===Offline configuration===
Comming soon
User can select which CAN parameter should be sent to server without connection to adapter. Please note that parameters depend on vehicle manufacturer and vehicle model. Please for further information check “Light Vehicles Can adapter supported cars” document.<br>
There are two types of operations with CAN data elements:
* Monitoring of CAN bus data
* CAN bus data event capturing
<br> Monitoring method is used when user wants to receive CAN data on regular basis, for example every 20 seconds.<br>
Event functionality is used to store additional AVL packet when state of CAN element is changing. For example Speed changes, low fuel level, engine temperate, etc. <br>
Send data to server field – allows enabling CAN element so it is added to the AVL data packet and sent to the server. By default, all CAN elements are disabled and {{{model|FM36YX}}} records only GPS data.<br>

It is possible to set CAN message priority: On Low Priority, On High Priority, and On Panic. Regular packets are sent as Low priority records. When low priority event is triggered, {{{model|FM36YX}}} makes additional record with indication what was the reason for that was CAN element change. When High priority is selected, module makes additional record with high priority flag and sends event packet immediately to the server by GPRS. Panic priority triggers same actions as high priority, but if GPRS fails, it sends AVL packet to server using SMS mode if SMS is enabled in SMS settings.
<br>
Data Acquisition Type – defines when to generate event – when value enters defined range, exits it or both, also is possible to select event which you want to generate then you change values, like crossing both values in high and low levels (Hysteresis). High and Low levels – defines CAN value range. If CAN value enter or exits this range, {{{model|FM36YX}}} generates event by “Data Acquisition Type” settings. Figure below show example of {{{model|FM36YX}}} CAN configuration.
<br>
'''PICTURE''' ?????
<br> [[File:FM36XX_Configurator_LVCAN.png|800px]] <br>
Available CAN Bus IO parameters and configuration can be found in Configurators CAN tab (Figure above) and in  “Parameters ID”. ?????
<br><br>
All information about I/O element parameters description is in section [[{{{model|FM36YX}}} I/O settings|I/O settings]].<br/>All LV-CAN200/ALL-CAN300 I/O parameters configuration settings are described in "{{{model|FM36YX}}} Protocols" document, except ALL-CAN300 bitmasks, which are described in the table below.''

{| class="wikitable"
|+
! style="width: 150px; background: black; color: white;"  | Property name
! style="width: 50px; background: black; color: white;" | Size, bytes
! style="width: 400px; background: black; color: white;" | Value bitmasks
|-
! style="text-align: left; vertical-align: top;" | Control state flags
| style="text-align: left; vertical-align: top;" | 4
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#FF6600>0x01</span> – STOP<br/><span style=color:#FF6600>0x02</span> – Oil pressure / level<br/><span style=color:#FF6600>0x04</span> – Coolant liquid temperature / level<br/><span style=color:#FF6600>0x08</span> – Handbrake system<br/><span style=color:#FF6600>0x20</span> – AIRBAG<br/><br/>
Byte1:<br/><span style=color:#0000FF>0x01</span> – CHECK ENGINE<br/><span style=color:#0000FF>0x02</span> – Lights failure<br/><span style=color:#0000FF>0x04</span> – Low tire pressure<br/><span style=color:#0000FF>0x08</span> – Wear of brake pads<br/><span style=color:#0000FF>0x10</span> – Warning<br/><span style=color:#0000FF>0x20</span> – ABS<br/><span style=color:#0000FF>0x40</span> – Low Fuel<br/><br/>
Byte2:<br/><span style=color:#339A6C>0x01</span> – ESP<br/><span style=color:#339A6C>0x02</span> – Glow plug indicator<br/><span style=color:#339A6C>0x04</span> – FAP<br/><span style=color:#339A6C>0x08</span> – Electronics pressure control<br/><span style=color:#339A6C>0x10</span> – Parking lights<br/><span style=color:#339A6C>0x20</span> – Dipped headlights<br/><span style=color:#339A6C>0x40</span> – Full beam headlights<br/><br/>
Byte3:<br/><span style=color:#9A3300>0x40</span> – Passenger's seat belt<br/><span style=color:#9A3300>0x80</span> – Driver's seat belt<br/>
|-
! style="text-align: left; vertical-align: top;" | Agricultural machinery flags
| style="text-align: left; vertical-align: top;" | 8
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#FF6600>0x01</span> – Mowing<br/><span style=color:#FF6600>0x02</span> – Grain release from hopper<br/><span style=color:#FF6600>0x04</span> – First front hydraulic turned on<br/><span style=color:#FF6600>0x08</span> – Rear Power Take-Off turned on<br/><br/>
Byte1:<br/><span style=color:#0000FF>0x01</span> – Excessive play under the threshing drum<br/><span style=color:#0000FF>0x02</span> – Grain tank is open<br/><span style=color:#0000FF>0x04</span> – 100% of Grain tank<br/><span style=color:#0000FF>0x08</span> – 70% of Grain tank<br/><span style=color:#0000FF>0x10</span> – Drain filter in hydraulic system of drive cylinders is plugged<br/><span style=color:#0000FF>0x20</span> – Pressure filter of drive cylinders hydraulic system is plugged<br/><span style=color:#0000FF>0x40</span> – Alarm oil level in oil tank<br/><span style=color:#0000FF>0x80</span> – Pressure filter of brakes hydraulic system is plugged<br/><br/>
Byte2:<br/><span style=color:#339A6C>0x01</span> – Oil filter of engine is plugged<br/><span style=color:#339A6C>0x02</span> – Fuel filter is plugged<br/><span style=color:#339A6C>0x04</span> – Air filter is plugged<br/><span style=color:#339A6C>0x08</span> – Alarm oil temperature in hydraulic system of chassis<br/><span style=color:#339A6C>0x10</span> – Alarm oil temperature in hydraulic system of drive cylinders<br/><span style=color:#339A6C>0x20</span> – Alarm oil pressure in engine<br/><span style=color:#339A6C>0x40</span> – Alarm coolant level<br/><span style=color:#339A6C>0x80</span> – Overflow chamber of hydraulic unit<br/><br/>
Byte3:<br/><span style=color:#9A3300>0x01</span> – Unloader drive is ON. Unloading tube pivot is in idle position<br/><span style=color:#9A3300>0x02</span> – No operator!<br/><span style=color:#9A3300>0x04</span> – Straw walker is plugged<br/><span style=color:#9A3300>0x08</span> – Water in fuel<br/><span style=color:#9A3300>0x10</span> – Cleaning fan RPM<br/><span style=color:#9A3300>0x20</span> – Trashing drum RPM<br/><br/>
Byte4:<br/><span style=color:#FF00FF>0x02</span> – Low water level in the tank<br/><span style=color:#FF00FF>0x04</span> – First rear hydraulic turned on<br/><span style=color:#FF00FF>0x08</span> – Standalone engine working<br/><span style=color:#FF00FF>0x10</span> – Right joystick moved right<br/><span style=color:#FF00FF>0x20</span> – Right joystick moved left<br/><span style=color:#FF00FF>0x40</span> – Right joystick moved front<br/><span style=color:#FF00FF>0x80</span> – Right joystick moved back<br/><br/>
Byte5:<br/><span style=color:#339A6C>0x01</span> – Brushes turned on<br/><span style=color:#339A6C>0x02</span> – Water supply turned on<br/><span style=color:#339A6C>0x04</span> – Vacuum cleaner<br/><span style=color:#339A6C>0x08</span> – Unloading from the hopper<br/><span style=color:#339A6C>0x10</span> – High Pressure washer (Karcher)<br/><span style=color:#339A6C>0x20</span> – Salt (sand) disperser ON<br/><span style=color:#339A6C>0x40</span> – Low salt (sand) level<br/><br/>
Byte6:<br/><span style=color:#66D6AD>0x01</span> – Second front hydraulic turned on<br/><span style=color:#66D6AD>0x02</span> – Third front hydraulic turned on<br/><span style=color:#66D6AD>0x04</span> – Fourth front hydraulic turned on<br/><span style=color:#66D6AD>0x08</span> – Second rear hydraulic turned on<br/><span style=color:#66D6AD>0x10</span> – Third rear hydraulic turned on<br/><span style=color:#66D6AD>0x20</span> – Fourth rear hydraulic turned on<br/><span style=color:#66D6AD>0x40</span> – Front three-point Hitch turned on<br/><span style=color:#66D6AD>0x80</span> – Rear three-point Hitch turned on<br/><br/>
Byte7:<br/><span style=color:#00331A>0x01</span> – Left joystick moved right<br/><span style=color:#00331A>0x02</span> – Left joystick moved left<br/><span style=color:#00331A>0x04</span> – Left joystick moved front<br/><span style=color:#00331A>0x08</span> – Left joystick moved back<br/><span style=color:#00331A>0x10</span> – Front Power Take-Off turned on<br/>
|-
! style="text-align: left; vertical-align: top;" | Security state flags
| style="text-align: left; vertical-align: top;" | 8
| style="text-align: left; vertical-align: top;" | Byte0 (LSB):<br/><span style=color:#008181>0x20</span> – Bit appears when any operate button in car was put<br/><span style=color:#008181>0x40</span> – Bit appears when immobiliSer is in service mode<br/><span style=color:#008181>0x80</span> – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car<br/><br/>
Byte1:<br/><span style=color:#FF6600>0x01</span> – the key is in ignition lock<br/><span style=color:#FF6600>0x02</span> – Ignition on<br/><span style=color:#FF6600>0x04</span> – Dynamic ignition on<br/><span style=color:#FF6600>0x08</span> – Webasto<br/><span style=color:#FF6600>0x20</span> – Car closed by factory's remote control<br/><span style=color:#FF6600>0x40</span> – Factory-installed alarm system is actuated (is in panic mode)<br/><span style=color:#FF6600>0x80</span> – Factory-installed alarm system is emulated by module<br/><br/>
Byte2:<br/><span style=color:#339A6C>0x01</span> – Parking activated (automatic gearbox)<br/><span style=color:#339A6C>0x10</span> – Handbrake is actuated (information available only with ignition on)<br/><span style=color:#339A6C>0x20</span> – Footbrake is actuated (information available only with ignition on)<br/><span style=color:#339A6C>0x40</span> – Engine is working (information available only when the ignition on)<br/><span style=color:#339A6C>0x80</span> – Reverse is on<br/><br/>
Byte3:<br/><span style=color:#0000FF>0x01</span> – Front left door opened<br/><span style=color:#0000FF>0x02</span> – Front right door opened<br/><span style=color:#0000FF>0x04</span> – Rear left door opened<br/><span style=color:#0000FF>0x08</span> – Rear right door opened<br/><span style=color:#0000FF>0x10</span> – Engine cover opened<br/><span style=color:#0000FF>0x20</span> – Trunk door opened<br/><br/>
Byte4:<br/><span style=color:#9DCD00>0x01</span> – Car was closed by the factory's remote control<br/><span style=color:#9DCD00>0x02</span> – Car was opened by the factory's remote control<br/><span style=color:#9DCD00>0x03?</span> – Trunk cover was opened by the factory's remote control<br/><span style=color:#9DCD00>0x04</span> – Module has sent a rearming signal<br/><span style=color:#9DCD00>0x05?</span> – Car was closed three times by the factory's remote control<br/>
- High nibble (mask 0xF0 bit)<br/><span style=color:#9DCD00>0x80</span> – CAN module goes to sleep mode<br/>
|-
! style="text-align: left; vertical-align: top;" | Tachograph driver card presence
| style="text-align: left; vertical-align: top;" | 1
| style="text-align: left; vertical-align: top;" | <span style=color:#9A3300>0x00</span> – No driver card<br/><span style=color:#9A3300>0x01</span> – Driver1 card presence<br/><span style=color:#9A3300>0x02</span> – Driver2 card presence<br/><span style=color:#9A3300>0x03</span> – Driver1 and driver2 cards present<br/>
|-
|-
! style="text-align: left; vertical-align: top;" | Driver 1 states
| style="text-align: left; vertical-align: top;" | 1
| style="text-align: left; vertical-align: top;" rowspan=2 | <span style=color:#124806>0xX0</span> – Break/rest<br/><span style=color:#124806>0xX1</span> – Availability<br/><span style=color:#124806>0xX2</span> – Work<br/><span style=color:#124806>0xX3</span> – Driving<br/><span style=color:#124806>0x0X</span> – No time-related warning detected<br/><span style=color:#124806>0x1X</span> – Limit #1: 15 min before 4 1/2 h<br/><span style=color:#124806>0x2X</span> – Limit #2: 4 1/2 h reached (continuous driving time exceeded)<br/><span style=color:#124806>0x3X</span> – Limit #3: 15 minutes before optional warning 1<br/><span style=color:#124806>0x4X</span> – Limit #4: optional warning 1 reached<br/><span style=color:#124806>0x5X</span> – Limit #5: 15 min before optional warning<br/><span style=color:#124806>0x6X</span> – Limit #6: optional warning 2 reached<br/>
|-
! style="text-align: left; vertical-align: top;" | Driver 2 states
| style="text-align: left; vertical-align: top;" | 1
|}

==Send data with 0, if ignition is off==

Depending on LV-CAN200/ALL-CAN300 I/O parameters and ignition status, {{{model|FM36YX}}} can send locked (last known) LV-CAN200/ALL-CAN300 I/O and active (real time) parameters values or reset values to 0. When ignition is off, LV-CAN200/ALL-CAN300 I/O parameters values sent to server are:

{| class="wikitable"
|+
! style="width: 300px; background: black; color: white;"  | LV-CAN200/ALL-CAN300 I/O element
! style="width: 100px; background: black; color: white;" | Status
|-
! style="text-align: left; vertical-align: top;" | Vehicle Speed
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Accelerator pedal position
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Total fuel used
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Fuel level (liters)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Engine RPM
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Total mileage
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Fuel level (%)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Program number
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Module ID
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Engine Work Time
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Engine Work Time (counted)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Total Mileage (counted)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Fuel Consumed (counted)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Fuel Rate
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Program number
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | AdBlue Level (%)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | AdBlue Level (liters)
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Engine Load
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Engine Temperature
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Axle 1 Load
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Axle 2 Load
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Axle 3 Load
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Axle 4 Load
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Axle 5 Load
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Control State Flags
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Agricultural Machinery Flags
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Harvesting Time
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Area of Harvest
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Mowing Efficiency
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Grain Mown Volume
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Grain Moisture
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Harvesting Drum RPM
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Gap Under Harvesting Drum
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Security State Flags
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Tachograph Total Vehicle Distance
| style="text-align: left; vertical-align: top;" | lock
|-
! style="text-align: left; vertical-align: top;" | Trip Distance
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Tachograph Vehicle Speed
| style="text-align: left; vertical-align: top;" | reset
|-
! style="text-align: left; vertical-align: top;" | Tachograph Driver Card Presence
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver1 States
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver2 States
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver1 Continuous Driving Time
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver2 Continuous Driving Time
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver1 Cumulative Break Time
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver2 Cumulative Break Time
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver1 Selected Activity Duration
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver2 Selected Activity Duration
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver1 Cumulative Driving Time
| style="text-align: left; vertical-align: top;" | active
|-
! style="text-align: left; vertical-align: top;" | Driver2 Cumulative Driving Time
| style="text-align: left; vertical-align: top;" | active
|-
|}

==LV-CAN200/ALL-CAN300 Important Information==
===Program Number logic change===
Due to the growing number of supported cars, program numbers have exceeded "999". In order to maintain one number format, we are moving from 3-digit to 4-digit program numbers.<br/>In new LV-CAN200/ALL-CAN300 firmware (from 2017-09-01) all program numbers that were up to 999 are changed to start from 1000. So that further program numbers would continue the counting with 4-digit numbers.<br/>However, all existing program numbers stay the same, but "1" is added to the front. Device still understands the entered 3-digit program number (via SMS/GPRS), it will automatically add "1" before it. If you enter "247" - device number will turn into "1247". In Bootloader only 4-digit format is available, just add "1" to the front of the needed program number.

===Example===
When using older connection schemes where program number displayed as 3-digit program number:
[[Image:Fmb120_can_prog_number.png|600px|center]]

Using LV-CAN200/ALL-CAN300 Bootloader from soft version 2017-09-27 it is necessary to add "1" to the front of program number:
[[Image:Fmb120_can_updater.png|400px|center]]