Teltonika Telematics Wiki - User contributions [en]

Template:FM36 CAN adapters

2018-06-12T09:00:22Z

Mantas.slipaitis:

==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]]): ''"lvcansetprog X"'' 

===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.

Technical details
* 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. 

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]]
 
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==

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

 
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. 
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. 
Pin 9 and 10 connections are optional depending on the exact car model. For exact pinout see the sticker of light vehicle CAN adapter. 

{| 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. 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.
 [[Image:FM36YX_scan_function.png|589px]] 
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. 
There are two types of operations with CAN data elements:
* Monitoring of CAN bus data
* CAN bus data event capturing
 Monitoring method is used when user wants to receive CAN data on regular basis, for example every 20 seconds. 
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. 
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. 

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.
 
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.
 
'''PICTURE''' ?????
 [[File:FM36XX_Configurator_LVCAN.png|800px]] 
Available CAN Bus IO parameters and configuration can be found in Configurators CAN tab (Figure above) and in “Parameters ID”. ?????
 
All information about I/O element parameters description is in section [[{{{model|FM36YX}}} I/O settings|I/O settings]]. 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): 0x01 – STOP 0x02 – Oil pressure / level 0x04 – Coolant liquid temperature / level 0x08 – Handbrake system 0x20 – AIRBAG 
Byte1: 0x01 – CHECK ENGINE 0x02 – Lights failure 0x04 – Low tire pressure 0x08 – Wear of brake pads 0x10 – Warning 0x20 – ABS 0x40 – Low Fuel 
Byte2: 0x01 – ESP 0x02 – Glow plug indicator 0x04 – FAP 0x08 – Electronics pressure control 0x10 – Parking lights 0x20 – Dipped headlights 0x40 – Full beam headlights 
Byte3: 0x40 – Passenger's seat belt 0x80 – Driver's seat belt 
|-
! 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): 0x01 – Mowing 0x02 – Grain release from hopper 0x04 – First front hydraulic turned on 0x08 – Rear Power Take-Off turned on 
Byte1: 0x01 – Excessive play under the threshing drum 0x02 – Grain tank is open 0x04 – 100% of Grain tank 0x08 – 70% of Grain tank 0x10 – Drain filter in hydraulic system of drive cylinders is plugged 0x20 – Pressure filter of drive cylinders hydraulic system is plugged 0x40 – Alarm oil level in oil tank 0x80 – Pressure filter of brakes hydraulic system is plugged 
Byte2: 0x01 – Oil filter of engine is plugged 0x02 – Fuel filter is plugged 0x04 – Air filter is plugged 0x08 – Alarm oil temperature in hydraulic system of chassis 0x10 – Alarm oil temperature in hydraulic system of drive cylinders 0x20 – Alarm oil pressure in engine 0x40 – Alarm coolant level 0x80 – Overflow chamber of hydraulic unit 
Byte3: 0x01 – Unloader drive is ON. Unloading tube pivot is in idle position 0x02 – No operator! 0x04 – Straw walker is plugged 0x08 – Water in fuel 0x10 – Cleaning fan RPM 0x20 – Trashing drum RPM 
Byte4: 0x02 – Low water level in the tank 0x04 – First rear hydraulic turned on 0x08 – Standalone engine working 0x10 – Right joystick moved right 0x20 – Right joystick moved left 0x40 – Right joystick moved front 0x80 – Right joystick moved back 
Byte5: 0x01 – Brushes turned on 0x02 – Water supply turned on 0x04 – Vacuum cleaner 0x08 – Unloading from the hopper 0x10 – High Pressure washer (Karcher) 0x20 – Salt (sand) disperser ON 0x40 – Low salt (sand) level 
Byte6: 0x01 – Second front hydraulic turned on 0x02 – Third front hydraulic turned on 0x04 – Fourth front hydraulic turned on 0x08 – Second rear hydraulic turned on 0x10 – Third rear hydraulic turned on 0x20 – Fourth rear hydraulic turned on 0x40 – Front three-point Hitch turned on 0x80 – Rear three-point Hitch turned on 
Byte7: 0x01 – Left joystick moved right 0x02 – Left joystick moved left 0x04 – Left joystick moved front 0x08 – Left joystick moved back 0x10 – Front Power Take-Off turned on 
|-
! 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): 0x20 – Bit appears when any operate button in car was put 0x40 – Bit appears when immobiliSer is in service mode 0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car 
Byte1: 0x01 – the key is in ignition lock 0x02 – Ignition on 0x04 – Dynamic ignition on 0x08 – Webasto 0x20 – Car closed by factory's remote control 0x40 – Factory-installed alarm system is actuated (is in panic mode) 0x80 – Factory-installed alarm system is emulated by module 
Byte2: 0x01 – Parking activated (automatic gearbox) 0x10 – Handbrake is actuated (information available only with ignition on) 0x20 – Footbrake is actuated (information available only with ignition on) 0x40 – Engine is working (information available only when the ignition on) 0x80 – Reverse is on 
Byte3: 0x01 – Front left door opened 0x02 – Front right door opened 0x04 – Rear left door opened 0x08 – Rear right door opened 0x10 – Engine cover opened 0x20 – Trunk door opened 
Byte4: 0x01 – Car was closed by the factory's remote control 0x02 – Car was opened by the factory's remote control 0x03? – Trunk cover was opened by the factory's remote control 0x04 – Module has sent a rearming signal 0x05? – Car was closed three times by the factory's remote control 
- High nibble (mask 0xF0 bit) 0x80 – CAN module goes to sleep mode 
|-
! 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;" | 0x00 – No driver card 0x01 – Driver1 card presence 0x02 – Driver2 card presence 0x03 – Driver1 and driver2 cards present 
|-
|-
! 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 | 0xX0 – Break/rest 0xX1 – Availability 0xX2 – Work 0xX3 – Driving 0x0X – No time-related warning detected 0x1X – Limit #1: 15 min before 4 1/2 h 0x2X – Limit #2: 4 1/2 h reached (continuous driving time exceeded) 0x3X – Limit #3: 15 minutes before optional warning 1 0x4X – Limit #4: optional warning 1 reached 0x5X – Limit #5: 15 min before optional warning 0x6X – Limit #6: optional warning 2 reached 
|-
! 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. 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. 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]]

Template:FM36 CAN adapters

2018-06-12T08:59:43Z

Mantas.slipaitis:

==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 [[FM3622_SMS/GPRS_command_list|SMS/GPRS command list]]): ''"lvcansetprog X"'' 

===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.

Technical details
* 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. 

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]]
 
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==

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

 
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. 
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. 
Pin 9 and 10 connections are optional depending on the exact car model. For exact pinout see the sticker of light vehicle CAN adapter. 

{| 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. 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.
 [[Image:FM36YX_scan_function.png|589px]] 
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. 
There are two types of operations with CAN data elements:
* Monitoring of CAN bus data
* CAN bus data event capturing
 Monitoring method is used when user wants to receive CAN data on regular basis, for example every 20 seconds. 
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. 
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. 

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.
 
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.
 
'''PICTURE''' ?????
 [[File:FM36XX_Configurator_LVCAN.png|800px]] 
Available CAN Bus IO parameters and configuration can be found in Configurators CAN tab (Figure above) and in “Parameters ID”. ?????
 
All information about I/O element parameters description is in section [[{{{model|FM36YX}}} I/O settings|I/O settings]]. 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): 0x01 – STOP 0x02 – Oil pressure / level 0x04 – Coolant liquid temperature / level 0x08 – Handbrake system 0x20 – AIRBAG 
Byte1: 0x01 – CHECK ENGINE 0x02 – Lights failure 0x04 – Low tire pressure 0x08 – Wear of brake pads 0x10 – Warning 0x20 – ABS 0x40 – Low Fuel 
Byte2: 0x01 – ESP 0x02 – Glow plug indicator 0x04 – FAP 0x08 – Electronics pressure control 0x10 – Parking lights 0x20 – Dipped headlights 0x40 – Full beam headlights 
Byte3: 0x40 – Passenger's seat belt 0x80 – Driver's seat belt 
|-
! 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): 0x01 – Mowing 0x02 – Grain release from hopper 0x04 – First front hydraulic turned on 0x08 – Rear Power Take-Off turned on 
Byte1: 0x01 – Excessive play under the threshing drum 0x02 – Grain tank is open 0x04 – 100% of Grain tank 0x08 – 70% of Grain tank 0x10 – Drain filter in hydraulic system of drive cylinders is plugged 0x20 – Pressure filter of drive cylinders hydraulic system is plugged 0x40 – Alarm oil level in oil tank 0x80 – Pressure filter of brakes hydraulic system is plugged 
Byte2: 0x01 – Oil filter of engine is plugged 0x02 – Fuel filter is plugged 0x04 – Air filter is plugged 0x08 – Alarm oil temperature in hydraulic system of chassis 0x10 – Alarm oil temperature in hydraulic system of drive cylinders 0x20 – Alarm oil pressure in engine 0x40 – Alarm coolant level 0x80 – Overflow chamber of hydraulic unit 
Byte3: 0x01 – Unloader drive is ON. Unloading tube pivot is in idle position 0x02 – No operator! 0x04 – Straw walker is plugged 0x08 – Water in fuel 0x10 – Cleaning fan RPM 0x20 – Trashing drum RPM 
Byte4: 0x02 – Low water level in the tank 0x04 – First rear hydraulic turned on 0x08 – Standalone engine working 0x10 – Right joystick moved right 0x20 – Right joystick moved left 0x40 – Right joystick moved front 0x80 – Right joystick moved back 
Byte5: 0x01 – Brushes turned on 0x02 – Water supply turned on 0x04 – Vacuum cleaner 0x08 – Unloading from the hopper 0x10 – High Pressure washer (Karcher) 0x20 – Salt (sand) disperser ON 0x40 – Low salt (sand) level 
Byte6: 0x01 – Second front hydraulic turned on 0x02 – Third front hydraulic turned on 0x04 – Fourth front hydraulic turned on 0x08 – Second rear hydraulic turned on 0x10 – Third rear hydraulic turned on 0x20 – Fourth rear hydraulic turned on 0x40 – Front three-point Hitch turned on 0x80 – Rear three-point Hitch turned on 
Byte7: 0x01 – Left joystick moved right 0x02 – Left joystick moved left 0x04 – Left joystick moved front 0x08 – Left joystick moved back 0x10 – Front Power Take-Off turned on 
|-
! 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): 0x20 – Bit appears when any operate button in car was put 0x40 – Bit appears when immobiliSer is in service mode 0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car 
Byte1: 0x01 – the key is in ignition lock 0x02 – Ignition on 0x04 – Dynamic ignition on 0x08 – Webasto 0x20 – Car closed by factory's remote control 0x40 – Factory-installed alarm system is actuated (is in panic mode) 0x80 – Factory-installed alarm system is emulated by module 
Byte2: 0x01 – Parking activated (automatic gearbox) 0x10 – Handbrake is actuated (information available only with ignition on) 0x20 – Footbrake is actuated (information available only with ignition on) 0x40 – Engine is working (information available only when the ignition on) 0x80 – Reverse is on 
Byte3: 0x01 – Front left door opened 0x02 – Front right door opened 0x04 – Rear left door opened 0x08 – Rear right door opened 0x10 – Engine cover opened 0x20 – Trunk door opened 
Byte4: 0x01 – Car was closed by the factory's remote control 0x02 – Car was opened by the factory's remote control 0x03? – Trunk cover was opened by the factory's remote control 0x04 – Module has sent a rearming signal 0x05? – Car was closed three times by the factory's remote control 
- High nibble (mask 0xF0 bit) 0x80 – CAN module goes to sleep mode 
|-
! 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;" | 0x00 – No driver card 0x01 – Driver1 card presence 0x02 – Driver2 card presence 0x03 – Driver1 and driver2 cards present 
|-
|-
! 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 | 0xX0 – Break/rest 0xX1 – Availability 0xX2 – Work 0xX3 – Driving 0x0X – No time-related warning detected 0x1X – Limit #1: 15 min before 4 1/2 h 0x2X – Limit #2: 4 1/2 h reached (continuous driving time exceeded) 0x3X – Limit #3: 15 minutes before optional warning 1 0x4X – Limit #4: optional warning 1 reached 0x5X – Limit #5: 15 min before optional warning 0x6X – Limit #6: optional warning 2 reached 
|-
! 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. 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. 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]]

FM3612 Configuration

2018-06-12T08:49:30Z

Mantas.slipaitis:

*[[FM3612 Read records|Read records]]
*[[FM3612 System settings|System settings]]
*[[FM3612 Records settings|Records settings]]
*[[FM3612 GSM settings, GPRS part|GSM settings, GPRS part]]
*[[FM3612 GSM settings, SMS part|GSM settings, SMS part]]
*[[FM3612 GSM settings, operator list|GSM settings, operator list]]
*[[FM3612 Data acquisition mode settings|Data acquisition mode settings]]
*[[FM3612 Features settings|Features settings]]
**[[FM3612 Features settings#Scenarios settings|Scenarios settings]]
**[[FM3612 Features settings#Trip_and_Odometer_settings|Trip and odometer settings]]
**[[FM3612 Features settings#Geofencing settings|Geofencing settings]]
*[[FM3612 I/O settings|I/O settings]]
**[[FM3612 I/O settings#Monitoring|Monitoring]]
**[[FM3612 I/O settings#Event generating|Event generating]]
**[[FM3612 I/O settings#Hysteresis|Hysteresis]]
*[[FM3612 SMS events|SMS events]]

FM3622 Configuration

2018-06-12T08:48:07Z

Mantas.slipaitis:

*[[FM3622 Read records|Read records]]
*[[FM3622 System settings|System settings]]
*[[FM3622 Records settings|Records settings]]
*[[FM3622 GSM settings, GPRS part|GSM settings, GPRS part]]
*[[FM3622 GSM settings, SMS part|GSM settings, SMS part]]
*[[FM3622 GSM settings, operator list|GSM settings, operator list]]
*[[FM3622 Data acquisition mode settings|Data acquisition mode settings]]
*[[FM3622 Features settings|Features settings]]
**[[FM3622 Features settings#Scenarios settings|Scenarios settings]]
**[[FM3622 Features settings#Trip_and_Odometer_settings|Trip and odometer settings]]
**[[FM3622 Features settings#Geofencing settings|Geofencing settings]]
*[[FM3622 I/O settings|I/O settings]]
**[[FM3622 I/O settings#Monitoring|Monitoring]]
**[[FM3622 I/O settings#Event generating|Event generating]]
**[[FM3622 I/O settings#Hysteresis|Hysteresis]]
*[[FM3622 SMS events|SMS events]]

FMT100 Configuration

2018-06-12T08:17:48Z

Mantas.slipaitis:

* [[FMT100 Status info|Status info]]
* [[FMT100 Security info|Security info]]
* [[FMT100 System settings|System settings]]
* [[FMT100 GPRS settings|GPRS settings]]
* [[FMT100 SMS/Call settings|SMS/Call settings]]
* [[FMT100 GSM Operators settings|GSM Operators settings]]
* [[FMT100 Data acquisition settings|Data acquisition settings]]
* [[FMT100 Features settings|Features settings]]
** [[FMT100 Features settings#Green Driving|Green Driving]]
** [[FMT100 Features settings#Over Speeding|Over Speeding]]
** [[FMT100 Features settings#Jamming|Jamming]]
** [[FMT100 Features settings#GPS Fuel Counter|GPS Fuel Counter]]
* [[FMT100 Accelerometer Features settings|Accelerometer Features settings]]
** [[FMT100 Accelerometer Features settings#Excessive Idling|Excessive Idling]]
** [[FMT100 Accelerometer Features settings#Unplug Detection|Unplug Detection]]
** [[FMT100 Accelerometer Features settings#Towing Detection|Towing Detection]]
** [[FMT100 Accelerometer Features settings#Crash Detection|Crash Detection]]
* [[FMT100 Auto Geofence settings|Auto Geofence settings]]
* [[FMT100 Manual Geofence settings|Manual Geofence settings]]
* [[FMT100 Trip/Odometer settings|Trip/Odometer settings]]
** [[FMT100 Trip/Odometer settings#Trip Settings|Trip Settings]]
** [[FMT100 Trip/Odometer settings#Advanced Trip Settings|Advanced Trip Settings]]
** [[FMT100 Trip/Odometer settings#Odometer|Odometer]]
* [[FMT100 Bluetooth settings|Bluetooth settings]]
** [[FMT100 Bluetooth settings#General functionality|General functionality]]
** [[FMT100 Bluetooth settings#How to connect Bluetooth Hands Free adapter to FMB device|How to connect Bluetooth Hands Free adapter to FMB device]]
** [[FMT100 Bluetooth settings#Logging the FMT100 device using your mobile phone|Logging the FMT100 device using your mobile phone]]
** [[FMT100 Bluetooth settings#Device debug over Android smartphone|Device debug over Android smartphone]]
** [[FMT100 Bluetooth settings#How to connect OBD II Bluetooth Dongle to FMB device|How to connect OBD II Bluetooth Dongle to FMB device]]
* [[FMT100 I/O settings|I/O settings]]
** [[FMT100 I/O settings#Operands|Operands]]
** [[FMT100 I/O settings#Avg Const|Avg Const]]
** [[FMT100 I/O settings#OBD II (Bluetooth) and LVCAN I/O elements| OBD II (Bluetooth) and LVCAN I/O elements]]
* [[FMT100 SMS events|SMS events]]

Template:FMB Blue-tooth settings

2018-06-12T08:13:45Z

Mantas.slipaitis:

==General functionality==

{{{pic_bt_general|[[Image:Fmb120_bt_general.png|300px|right]]}}}
General functionality configures Bluetooth to work in slave mode. This mode allows any external device to connect to {{{model|FMB1YX}}}. Parameter ''BT Radio'' allows enabling or disabling Bluetooth. There are three different settings:
# Disabled – Bluetooth functionality will be disabled.
# Enable (hidden) – Bluetooth functionality will be enabled, external devices will be able to connect to {{{model|FMB1YX}}}, but no devices will be able to detect it.
# Enable (visible) – Bluetooth functionality will be enabled and any external device will be able to detect and connect to {{{model|FMB1YX}}}. ''Local Name'' parameter lets user declare a visible name of {{{model|FMB1YX}}} to external devices. ''Local PIN'' parameter lets user configure Bluetooth PIN of {{{model|FMB1YX}}} device. 
{{{model|FMB1YX}}} Bluetooth has several different ''Security Modes'':
* PIN only – only Local PIN will be reacquired to complete connection to {{{model|FMB1YX}}}.
* PIN + MAC list – PIN and Authorized Devices MAC List will be checked against to allow connection to {{{model|FMB1YX}}}. If the external device MAC ID is in the list and correct ''Local PIN'' is entered then connection will be established, otherwise {{{model|FMB1YX}}} will reject connection.
* MAC list only – only ''Authorized Devices MAC List'' will be checked when trying to connect to {{{model|FMB1YX}}}. If external device MAC ID is in the list then connection will be established, otherwise {{{model|FMB1YX}}} will reject connection.
* None – neither ''Local PIN'' nor ''Authorized Device MAC List'' will be checked.

Auto connection functionality configures {{{model|FMB1YX}}} as master device, which allows connecting {{{model|FMB1YX}}} to an external device. {{{model|FMB1YX}}} currently supports these modes:
* None – disables auto connection functionality.
* Hands Free or OBDII – {{{model|FMB1YX}}} starts searching for an external hands free headset. If {{{model|FMB1YX}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then {{{model|FMB1YX}}} will try to pair with that external device. If the external device asks for PIN then {{{model|FMB1YX}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMB1YX}}} will connect to paired device.
* Data Link – BT Data link mode is enabled by Configurator ''Data Link'' parameter: when Data Link is configured and {{{model_2|FMB}}} has a link with the server, paired device can send messages via Bluetooth SPP profile directly to the server. Messages will be encoded by codec12.

{| 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;" | {{{model|FMB1YX}}} supports ONE connection at a time. {{{model|FMB1YX}}} can see up to 10 available devices. If there are more than 10 devices, the list may change with each new scan.
|}

''External Name'' parameter works as a substring, which allows user to enter a part of the full external device name. For example, if external device name is "HandsFreeHeadset" and user enters "HandsFree" in ''External Name'' parameter window, then {{{model|FMB1YX}}} will be allowed to connect to an external device named "HandsFreeHeadset".

==How to connect Bluetooth Hands Free adapter to {{{model_2|FMB}}} device==

{{{pic_bt_settings|[[Image:Fmb120_bt_settings.png|thumb|300px|right|Bluetooth settings]]}}}
[[Image:Fmb120_inc_call_action_settings.png|thumb|300px|right|Incoming Call Action settings under SMS/Call Settings]]
===Bluetooth settings configuration===

These are instructions on how to easily create a connection between a Bluetooth Hands Free device and an {{{model_2|FMB}}} device. First the {{{model_2|FMB}}} device Bluetooth settings need to be configured. These are the required steps:

* Press Bluetooth settings (position 1).
* Turn on BT Radio by pressing Enable (visible) (position 2). ''Local name'' (position 3) will be "{{{model|FMB1YX}}}_last 7 imei digits" by default, which can be changed.
* Set ''Security Mode'' (position 4) to PIN only or None. PIN + MAC list or MAC list only security modes could also be selected, but in that case external device MAC address is required to be entered to ''Authorized Devices MAC List'' (position 7).
* Set connection mode to Hands Free (position 5).
* Set ''External Name'' (position 6) as your hands-free device name for proper identification. In the given example hands-free headset name is "DMH10" but at least 2 characters are required to recognize it and connect to it. For better and quicker adapter identification on the network you could enter a full device name. You could check your hands-free adapter Bluetooth name by scanning nearby Bluetooth devices using a mobile phone or a computer with Bluetooth adapter.
* Go to SMS/Call Settings in main menu and set ''Incoming Call Action'' to Do Nothing as shown on next figure.
* After all these steps press Save to device to save configuration.
* Now {{{model_2|FMB}}} device can be disconnected from the configurator.
 

===Connecting Bluetooth Hands Free adapter===
----
Turn on hands-free device and then turn on its Bluetooth connection for pairing following your model instructions. Hands-free adapter should make a specific sound in the speakers or its LED identification should inform about a successful connection. To check if the adapter is successfully connected, dial the {{{model_2|FMB}}} device phone number and the hands-free device should start ringing. If you later restart {{{model_2|FMB}}} device it will automatically reconnect to this adapter.
 

==Logging the {{{model|FMB1YX}}} device using your mobile phone==

Bluetooth starts automatically when {{{model_2|FMB}}} device is on. Take your mobile phone, go to Settings->Bluetooth and turn it on. Scan for nearby devices, find the device in the list, distinguish the device by last IMEI digits on device module. Press pair, wait until device asks to enter pairing password, type: ''"5555"'' (as in the example on the figure). Paired device will show up in the paired device list. Download a terminal for Bluetooth e.g. BlueTerm from Play Store/App store. Run app, click Find->Connect to your paired device. Now we need to send a command to {{{model|FMB1YX}}} from Bluetooth terminal, type: ''".log:1"'' Device will respond with ''"Debug enabled"'' and {{{model|FMB1YX}}} log will show up. Do not forget to save the log file to mobile phone.

==Device debug over Android smartphone==

[[Image:Fmb120_bt_general_vis.png|300px|right]]

In order to pair {{{model_2|FMB}}} device with Android smartphone, make sure that BT radio is enabled (visible) in device configuration. It can be checked via SMS command too: ''"getparam 800"'' The answer has to be ''"2"'', which means "Enabled and visible".
 

[[Image:Android_bt.png|300px|right]]

* Scan for visible BT devices using your Android smartphone and connect to your {{{model_2|FMB}}} device. Default {{{model_2|FMB}}} BT name is: ''"{{{model|FMB1YX}}}_last_7_imei_digits"''. Default PIN code is: ''"5555"''.

 

* Download "Bluetooth Terminal" application. Following link can be used: https://play.google.com/store/apps/details?id=com.hatflabs.btt

[[Image:Android_bt_serial.png|300px|right]]

* Run "Bluetooth Terminal", in menu press "Connect" and select paired {{{model_2|FMB}}} device. To start log check "CR" and enter the command into terminal: ''".log:1"''.

* Wait ~10 minutes and press "Save" button in menu. You will find the saved log file in device folder "My Files/Bluetooth Terminal", select log files and press "Share via Email" and send them to Teltonika support.

 

<gallery widths=100px perrow=3 caption="Saving and sharing the log">
Image:Android_bt_log1.png
Image:Android_bt_log2.png
Image:Android_bt_log3.png
</gallery>

 

{| 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;" | Unfortunately it is not possible to perform debug the same way on iPhone, because there is no native SPP Bluetooth profile support on iPhone.
|}

{{{
para_obd|
{{
Template:FMB1 Bluetooth OBD dongle
|model={{{model|FMBXXX}}}
|model_2={{{model_2|FMB}}}
}}
}}}

Template:FMB Blue-tooth settings

2018-06-12T08:11:00Z

Mantas.slipaitis:

==General functionality==

{{{pic_bt_general|[[Image:Fmb120_bt_general.png|300px|right]]}}}
General functionality configures Bluetooth to work in slave mode. This mode allows any external device to connect to {{{model|FMB1YX}}}. Parameter ''BT Radio'' allows enabling or disabling Bluetooth. There are three different settings:
# Disabled – Bluetooth functionality will be disabled.
# Enable (hidden) – Bluetooth functionality will be enabled, external devices will be able to connect to {{{model|FMB1YX}}}, but no devices will be able to detect it.
# Enable (visible) – Bluetooth functionality will be enabled and any external device will be able to detect and connect to {{{model|FMB1YX}}}. ''Local Name'' parameter lets user declare a visible name of {{{model|FMB1YX}}} to external devices. ''Local PIN'' parameter lets user configure Bluetooth PIN of {{{model|FMB1YX}}} device. 
{{{model|FMB1YX}}} Bluetooth has several different ''Security Modes'':
* PIN only – only Local PIN will be reacquired to complete connection to {{{model|FMB1YX}}}.
* PIN + MAC list – PIN and Authorized Devices MAC List will be checked against to allow connection to {{{model|FMB1YX}}}. If the external device MAC ID is in the list and correct ''Local PIN'' is entered then connection will be established, otherwise {{{model|FMB1YX}}} will reject connection.
* MAC list only – only ''Authorized Devices MAC List'' will be checked when trying to connect to {{{model|FMB1YX}}}. If external device MAC ID is in the list then connection will be established, otherwise {{{model|FMB1YX}}} will reject connection.
* None – neither ''Local PIN'' nor ''Authorized Device MAC List'' will be checked.

Auto connection functionality configures {{{model|FMB1YX}}} as master device, which allows connecting {{{model|FMB1YX}}} to an external device. {{{model|FMB1YX}}} currently supports these modes:
* None – disables auto connection functionality.
* Hands Free or OBDII – {{{model|FMB1YX}}} starts searching for an external hands free headset. If {{{model|FMB1YX}}} finds a device which matches user defined ''External MAC'' or ''External Name'' then {{{model|FMB1YX}}} will try to pair with that external device. If the external device asks for PIN then {{{model|FMB1YX}}} will send user defined ''External PIN''. After successfully pairing {{{model|FMB1YX}}} will connect to paired device.
* Data Link – BT Data link mode is enabled by Configurator ''Data Link'' parameter: when Data Link is configured and {{{model_2|FMB}}} has a link with the server, paired device can send messages via Bluetooth SPP profile directly to the server. Messages will be encoded by codec12.

{| 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;" | {{{model|FMB1YX}}} supports ONE connection at a time. {{{model|FMB1YX}}} can see up to 10 available devices. If there are more than 10 devices, the list may change with each new scan.
|}

''External Name'' parameter works as a substring, which allows user to enter a part of the full external device name. For example, if external device name is "HandsFreeHeadset" and user enters "HandsFree" in ''External Name'' parameter window, then {{{model|FMB1YX}}} will be allowed to connect to an external device named "HandsFreeHeadset".

==How to connect Bluetooth Hands Free adapter to {{{model_2|FMB}}} device==

{{{pic_bt_settings|[[Image:Fmb120_bt_settings.png|thumb|300px|right|Bluetooth settings]]}}}
[[Image:Fmb120_inc_call_action_settings.png|thumb|300px|right|Incoming Call Action settings under SMS/Call Settings]]
===Bluetooth settings configuration===

These are instructions on how to easily create a connection between a Bluetooth Hands Free device and an {{{model_2|FMB}}} device. First the {{{model_2|FMB}}} device Bluetooth settings need to be configured. These are the required steps:

* Press Bluetooth settings (position 1).
* Turn on BT Radio by pressing Enable (visible) (position 2). ''Local name'' (position 3) will be "{{{model|FMB1YX}}}_last 7 imei digits" by default, which can be changed.
* Set ''Security Mode'' (position 4) to PIN only or None. PIN + MAC list or MAC list only security modes could also be selected, but in that case external device MAC address is required to be entered to ''Authorized Devices MAC List'' (position 7).
* Set connection mode to Hands Free (position 5).
* Set ''External Name'' (position 6) as your hands-free device name for proper identification. In the given example hands-free headset name is "DMH10" but at least 2 characters are required to recognize it and connect to it. For better and quicker adapter identification on the network you could enter a full device name. You could check your hands-free adapter Bluetooth name by scanning nearby Bluetooth devices using a mobile phone or a computer with Bluetooth adapter.
* Go to SMS/Call Settings in main menu and set ''Incoming Call Action'' to Do Nothing as shown on next figure.
* After all these steps press Save to device to save configuration.
* Now {{{model_2|FMB}}} device can be disconnected from the configurator.
 

===Connecting Bluetooth Hands Free adapter===
----
Turn on hands-free device and then turn on its Bluetooth connection for pairing following your model instructions. Hands-free adapter should make a specific sound in the speakers or its LED identification should inform about a successful connection. To check if the adapter is successfully connected, dial the {{{model_2|FMB}}} device phone number and the hands-free device should start ringing. If you later restart {{{model_2|FMB}}} device it will automatically reconnect to this adapter.
 

==Logging the {{{model|FMB1YX}}} device using your mobile phone==

Bluetooth starts automatically when {{{model_2|FMB}}} device is on. Take your mobile phone, go to Settings->Bluetooth and turn it on. Scan for nearby devices, find the device in the list, distinguish the device by last IMEI digits on device module. Press pair, wait until device asks to enter pairing password, type: ''"5555"'' (as in the example on the figure). Paired device will show up in the paired device list. Download a terminal for Bluetooth e.g. BlueTerm from Play Store/App store. Run app, click Find->Connect to your paired device. Now we need to send a command to {{{model|FMB1YX}}} from Bluetooth terminal, type: ''".log:1"'' Device will respond with ''"Debug enabled"'' and {{{model|FMB1YX}}} log will show up. Do not forget to save the log file to mobile phone.

==Device debug over Android smartphone==

[[Image:Fmb120_bt_general_vis.png|300px|right]]

In order to pair {{{model_2|FMB}}} device with Android smartphone, make sure that BT radio is enabled (visible) in device configuration. It can be checked via SMS command too: ''"getparam 800"'' The answer has to be ''"2"'', which means "Enabled and visible".
 

[[Image:Android_bt.png|300px|right]]

* Scan for visible BT devices using your Android smartphone and connect to your {{{model_2|FMB}}} device. Default {{{model_2|FMB}}} BT name is: ''"{{{model|FMB1YX}}}_last_7_imei_digits"''. Default PIN code is: ''"5555"''.

 

* Download "Bluetooth Terminal" application. Following link can be used: https://play.google.com/store/apps/details?id=com.hatflabs.btt

[[Image:Android_bt_serial.png|300px|right]]

* Run "Bluetooth Terminal", in menu press "Connect" and select paired {{{model_2|FMB}}} device. To start log check "CR" and enter the command into terminal: ''".log:1"''.

* Wait ~10 minutes and press "Save" button in menu. You will find the saved log file in device folder "My Files/Bluetooth Terminal", select log files and press "Share via Email" and send them to Teltonika support.

 

<gallery widths=100px perrow=3 caption="Saving and sharing the log">
Image:Android_bt_log1.png
Image:Android_bt_log2.png
Image:Android_bt_log3.png
</gallery>

 

{| 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;" | Unfortunately it is not possible to perform debug the same way on iPhone, because there is no native SPP Bluetooth profile support on iPhone.
|}

{{{para_obd| {{Template:FMB1 Bluetooth OBD dongle|model={{{model|FMBXXX}}}|model_2={{{model_2|FMB}}} }} }}}

Template:FMB1 Bluetooth OBD dongle

2018-06-12T08:10:29Z

Mantas.slipaitis:

===Bluetooth settings configuration===

[[Image:Fmb120_bt_odbii_settings.png|300px|right]]
Following are the instructions on how to easily prepare Bluetooth Dongle connection to the {{{model_2|FMB}}} device. First we need to configure {{{model_2|FMB}}} device Bluetooth settings. These are the required steps:
* Go to Bluetooth section similarly to as shown in the figure to the right (position 1).
* Turn on BT Radio by pressing Enable (visible) (position 2). "Local name" (position 3) will automatically be "{{{model|FMB1YX}}}_last 7 imei digits", you can leave it or type your own name.
* Set ''Security Mode'' (position 4) to PIN only or None (you could select PIN + MAC list or MAC list only security mode but in this case you need to type external device MAC address in ''Authorized Devices MAC List'' (position 7).
* Set connection mode to OBDII (position 5).
* Set ''External Name'' as your Bluetooth OBD II device name for proper device identification and connection to it. In this example OBDII device name is "DONGLE", at least 2 characters are needed to recognize it and connect to it. For better and faster adapter identification in network you could enter a full device name. You could check your OBDII adapter Bluetooth name by scanning nearby Bluetooth devices using a mobile phone or a computer with Bluetooth adapter.
* Go to OBD II in main menu and select priority and others parameters visible in the following figure.

[[Image:Fmb120_odbii_settings.png|800px|none]]

* After all these steps press Save to device to save configuration (position 8 in the top right hand figure).
* Now you can disconnect {{{model_2|FMB}}} device from the configurator.

===Connecting to Bluetooth OBD II dongle===
----
After this configuration OBDII dongle can be connected to {{{model_2|FMB}}} device. Turn on ignition, then turn on its Bluetooth connection. For pairing follow dongle instructions. OBDII device notification about paired Bluetooth connection depends on the specific model. If you later restart {{{model_2|FMB}}} device it will automatically reconnect to this dongle.

===Supported Bluetooth OBD II dongles===
----
{{{model_2|FMB}}} module works with Bluetooth OBD II dongles which are based on ELM327 or STN1110 chips. Comparison of these chips is presented in the image below:

[[Image:Elm317_stn1110_comp.png|400px|none]]

Template:FMB1 Bluetooth OBD dongle

2018-06-12T08:09:07Z

Mantas.slipaitis:

===Bluetooth settings configuration===

[[Image:Fmb120_bt_odbii_settings.png|300px|right]]
Following are the instructions on how to easily prepare Bluetooth Dongle connection to the {{{model|FMB}}} device. First we need to configure {{{model|FMB}}} device Bluetooth settings. These are the required steps:
* Go to Bluetooth section similarly to as shown in the figure to the right (position 1).
* Turn on BT Radio by pressing Enable (visible) (position 2). "Local name" (position 3) will automatically be "{{{model|FMB1YX}}}_last 7 imei digits", you can leave it or type your own name.
* Set ''Security Mode'' (position 4) to PIN only or None (you could select PIN + MAC list or MAC list only security mode but in this case you need to type external device MAC address in ''Authorized Devices MAC List'' (position 7).
* Set connection mode to OBDII (position 5).
* Set ''External Name'' as your Bluetooth OBD II device name for proper device identification and connection to it. In this example OBDII device name is "DONGLE", at least 2 characters are needed to recognize it and connect to it. For better and faster adapter identification in network you could enter a full device name. You could check your OBDII adapter Bluetooth name by scanning nearby Bluetooth devices using a mobile phone or a computer with Bluetooth adapter.
* Go to OBD II in main menu and select priority and others parameters visible in the following figure.

[[Image:Fmb120_odbii_settings.png|800px|none]]

* After all these steps press Save to device to save configuration (position 8 in the top right hand figure).
* Now you can disconnect {{{model|FMB}}} device from the configurator.

===Connecting to Bluetooth OBD II dongle===
----
After this configuration OBDII dongle can be connected to {{{model|FMB}}} device. Turn on ignition, then turn on its Bluetooth connection. For pairing follow dongle instructions. OBDII device notification about paired Bluetooth connection depends on the specific model. If you later restart {{{model|FMB}}} device it will automatically reconnect to this dongle.

===Supported Bluetooth OBD II dongles===
----
{{{model|FMB}}} module works with Bluetooth OBD II dongles which are based on ELM327 or STN1110 chips. Comparison of these chips is presented in the image below:

[[Image:Elm317_stn1110_comp.png|400px|none]]

FMT100 Status info

2018-06-12T07:44:50Z

Mantas.slipaitis:

{{
Template:FMB Status info
|model=FMT100
|status_picture=[[Image:FMT100_status_info.png|none]]
|txt_fmb0=''OBD Info'' shows the main OBD information (when the device connected to the vehicle via OBD II Bluetooth dongle adapter): vehicle VIN code and OBD protocol used. 
}}

File:FMT100 status info.png

2018-06-12T07:44:27Z

Mantas.slipaitis:

FMT100 Status info

2018-06-12T07:44:18Z

Mantas.slipaitis:

{{
Template:FMB Status info
|model=FMT100
|status_picture=[[Image:FMT100_status_info.png|800px|none]]
|txt_fmb0=''OBD Info'' shows the main OBD information (when the device connected to the vehicle via OBD II Bluetooth dongle adapter): vehicle VIN code and OBD protocol used. 
}}

Template:FMB Status info

2018-06-12T07:43:25Z

Mantas.slipaitis:

Status info enables the user to monitor real time information of {{{model|FMB1YX}}}. Following fields are displayed: ''Device Info'' field, ''GNSS Info'' field, ''GSM Info'' field, {{{txt_fmb0|''OBD/CAN Adapter Info'' field }}}and ''I/O Info'' field. User is able to export all of the information to .HTML file using an icon which is at the top right corner of the ''Device Info'' area.

{{{status_picture|[[Image:Fmb120_status_info.png|800px|none]]}}}

''Device Info'' shows device name, firmware version, last device start time, RTC Time, power voltage (mV), device IMEI, SD card free space, Device uptime, Battery voltage (mV) and internal battery status. ''GNSS Info'' shows:
* Real time GNSS status information: module status (ON, Deep/GPS/Online 'Sleep mode), the amount of GNSS packets device received from startup, fix status and the last GNSS fix time.
* Satellite information: the amount and type of satellites that are visible, and the amount of satellites used for location positioning.
* Location information: latitude, longitude, altitude, angle, HDOP, PDOP and speed. 
''GSM Info'' shows:
* GSM status: modem status, SIM status, GPRS status, actual operator code and GSM signal level.
* GPRS traffic: the amount of data that has been sent and received by the device.
* Sockets information: which server domain and port is used.
* Records: how many records were sent to the server since last data reset, when the last record was sent and when was the last server response.
* SMS count: the amount of SMS messages {{{model|FMB1YX}}} has received and the amount of SMS responses that were sent from the device.
 {{{txt_fmb0|''OBD Info'' shows the main OBD information (when the device connected to the vehicle via OBD II Bluetooth dongle adapter): vehicle VIN code and OBD protocol used. In ''CAN Adapter Info'' user is able to see main information from LV-CAN200/ALL-CAN300 (when the device connected to LV-CAN200/ALL-CAN300): program number and LV-CAN200/ALL-CAN300 software version. }}}''I/O Info'' shows the values from all configurable I/O elements.

Template:FMB System settings

2018-06-12T07:38:47Z

Mantas.slipaitis:

System settings have following configurable parameters:
* ''Sleep Settings'', where user can choose sleep mode;
* ''Ignition Source'', where user can choose an ignition source from digital input 1, power voltage{{{txt_fmb0|, engine RPM}}} and accelerometer. More than one ignition source can be selected at the same moment. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: eco driving, excessive idling, fuel consumption, over speeding, towing and trip;
* Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMB1YX}}} detects movement and change its working mode (for more information refer to section {{{ctrDaq|[[{{{model|Template:}}} Data acquisition settings]]}}}). Other functionalities that depend on movement source are: power manager, fuel consumption and trip;
* ''Static Navigation Settings'', where user can turn static navigation on or off. Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation;
* Records settings (no time synchronization), where user can enable or disable records when GPS is not available;
* ''GNSS Source'' settings, where user can choose the necessary satellite system(s);
* ''LED Indication'', where user can turn on or off the indication LEDs;
* ''Battery Charge Mode'', where user can choose when battery will be charged: On Need (battery will be charged anytime when it needs to be charged) and After Ignition ON (battery will be charged only when ignition is on);{{{txt_fmb0|
* ''Analog Input Value Range'', where user can choose analog input range of 10 V or 30 V;}}}
* ''Time Synchronization'' settings, where user can choose which source(s) to use for {{{model|FMB1YX}}} time synchronization. User has a choice to: use only one synchronization source (Disable (GPS only)), allow synchronization from both the GNSS and NTP server (NTP), select synchronization through GNSS and GSM operator (NITZ) or from all three sources (when NITZ+NTP is selected). User can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time.

{{{template_link|}}}

''Static Navigation'' mode is a filter, which filters out track jumps when the object is stationary. If static navigation filter is disabled, it will apply no changes to GPS data. If static navigation filter is enabled, it will filter changes in GPS position if no movement (as defined by configured movement source) or ignition (as defined by configured ignition source) is detected. It allows filtering GPS jumps when the object is parked (not moving) and GPS position is still traced.

{{{pic_system|[[Image:fmb120_system.png|800px|none]]}}}

In ''GNSS Source'' settings user can configure which GNSS system(s) to use. User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together. Examples of non-configurable GNSS source combinations are:
* GLONASS + BeiDou;
* Galileo + GLONASS + BeiDou;
* GPS + GLONASS + BeiDou;
* GPS + Galileo + GLONASS + BeiDou.

{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;" | Selected source(s)
! style="width: 100px; background: black; color: white;" | ID
|-
! style="text-align: left; vertical-align: top;" | BeiDou only
| style="text-align: left; vertical-align: top;" | 01
|-
! style="text-align: left; vertical-align: top;" | GLONASS only
| style="text-align: left; vertical-align: top;" | 02
|-
! style="text-align: left; vertical-align: top;" | Galileo only
| style="text-align: left; vertical-align: top;" | 04
|-
! style="text-align: left; vertical-align: top;" | Galileo + Beidou
| style="text-align: left; vertical-align: top;" | 05
|-
! style="text-align: left; vertical-align: top;" | Galileo + Glonass
| style="text-align: left; vertical-align: top;" | 06
|-
! style="text-align: left; vertical-align: top;" | GPS only
| style="text-align: left; vertical-align: top;" | 08
|-
! style="text-align: left; vertical-align: top;" | GPS + BeiDou
| style="text-align: left; vertical-align: top;" | 09
|-
! style="text-align: left; vertical-align: top;" | GPS + GLONASS
| style="text-align: left; vertical-align: top;" | 10
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo
| style="text-align: left; vertical-align: top;" | 12
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo + BeiDou
| style="text-align: left; vertical-align: top;" | 13
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo + GLONASS
| style="text-align: left; vertical-align: top;" | 14
|-
|}

Template:FMB System settings

2018-06-12T07:38:01Z

Mantas.slipaitis:

System settings have following configurable parameters:
* ''Sleep Settings'', where user can choose sleep mode;
* ''Ignition Source'', where user can choose an ignition source from digital input 1, power voltage{{{txt_fmb0|, engine RPM}}} and accelerometer. More than one ignition source can be selected at the same moment. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: eco driving, excessive idling, fuel consumption, over speeding, towing and trip;
* Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMB1YX}}} detects movement and change its working mode (for more information refer to section {{{ctrDaq|[[{{{model|Template:}}} Data acquisition settings|Data acquisition settings]]}}}). Other functionalities that depend on movement source are: power manager, fuel consumption and trip;
* ''Static Navigation Settings'', where user can turn static navigation on or off. Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation;
* Records settings (no time synchronization), where user can enable or disable records when GPS is not available;
* ''GNSS Source'' settings, where user can choose the necessary satellite system(s);
* ''LED Indication'', where user can turn on or off the indication LEDs;
* ''Battery Charge Mode'', where user can choose when battery will be charged: On Need (battery will be charged anytime when it needs to be charged) and After Ignition ON (battery will be charged only when ignition is on);{{{txt_fmb0|
* ''Analog Input Value Range'', where user can choose analog input range of 10 V or 30 V;}}}
* ''Time Synchronization'' settings, where user can choose which source(s) to use for {{{model|FMB1YX}}} time synchronization. User has a choice to: use only one synchronization source (Disable (GPS only)), allow synchronization from both the GNSS and NTP server (NTP), select synchronization through GNSS and GSM operator (NITZ) or from all three sources (when NITZ+NTP is selected). User can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time.

{{{template_link|}}}

''Static Navigation'' mode is a filter, which filters out track jumps when the object is stationary. If static navigation filter is disabled, it will apply no changes to GPS data. If static navigation filter is enabled, it will filter changes in GPS position if no movement (as defined by configured movement source) or ignition (as defined by configured ignition source) is detected. It allows filtering GPS jumps when the object is parked (not moving) and GPS position is still traced.

{{{pic_system|[[Image:fmb120_system.png|800px|none]]}}}

In ''GNSS Source'' settings user can configure which GNSS system(s) to use. User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together. Examples of non-configurable GNSS source combinations are:
* GLONASS + BeiDou;
* Galileo + GLONASS + BeiDou;
* GPS + GLONASS + BeiDou;
* GPS + Galileo + GLONASS + BeiDou.

{| class="wikitable"
|+
! style="width: 250px; background: black; color: white;" | Selected source(s)
! style="width: 100px; background: black; color: white;" | ID
|-
! style="text-align: left; vertical-align: top;" | BeiDou only
| style="text-align: left; vertical-align: top;" | 01
|-
! style="text-align: left; vertical-align: top;" | GLONASS only
| style="text-align: left; vertical-align: top;" | 02
|-
! style="text-align: left; vertical-align: top;" | Galileo only
| style="text-align: left; vertical-align: top;" | 04
|-
! style="text-align: left; vertical-align: top;" | Galileo + Beidou
| style="text-align: left; vertical-align: top;" | 05
|-
! style="text-align: left; vertical-align: top;" | Galileo + Glonass
| style="text-align: left; vertical-align: top;" | 06
|-
! style="text-align: left; vertical-align: top;" | GPS only
| style="text-align: left; vertical-align: top;" | 08
|-
! style="text-align: left; vertical-align: top;" | GPS + BeiDou
| style="text-align: left; vertical-align: top;" | 09
|-
! style="text-align: left; vertical-align: top;" | GPS + GLONASS
| style="text-align: left; vertical-align: top;" | 10
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo
| style="text-align: left; vertical-align: top;" | 12
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo + BeiDou
| style="text-align: left; vertical-align: top;" | 13
|-
! style="text-align: left; vertical-align: top;" | GPS + Galileo + GLONASS
| style="text-align: left; vertical-align: top;" | 14
|-
|}

FMT100 SMS events

2018-06-12T07:17:19Z

Mantas.slipaitis: Created page with "{{ Template:FMB SMS events |model=FMT100 }}"

FMT100 I/O settings

2018-06-12T07:15:12Z

Mantas.slipaitis:

{{
Template:FMB I/O settings
|model=FMT100
|section_fmb0=
==OBD II (Bluetooth) I/O elements==
''OBD II (Bluetooth)'' section show I/O elements that can be obtained accordingly from OBD II Bluetooth dongle connected to FMT100 device. All I/O configuration is as described in [[FMT100_I/O_settings|I/O settings]] section, except OBD II (Bluetooth) I/O elements does not have an averaging constant parameter.
}}

FMT100 I/O settings

2018-06-12T07:14:45Z

Mantas.slipaitis:

{{
Template:FMB I/O settings
|model=FMT100
|section_fmb0=
==OBD II (Bluetooth) I/O elements==
''OBD II (Bluetooth)'' section show I/O elements that can be obtained accordingly from OBD II Bluetooth dongle connected to FMT100 device. All I/O configuration is as described in [[FMT100_I/O_settings|FMT I/O settings]] section, except OBD II (Bluetooth) I/O elements does not have an averaging constant parameter.
}}

FMT100 I/O settings

2018-06-12T07:14:20Z

Mantas.slipaitis: Created page with "{{ Template:FMB I/O settings |model=FMT100 |section_fmb0= ==OBD II (Bluetooth) I/O elements== ''OBD II (Bluetooth)'' section show I/O elements that can be obtained accordingly..."

FMB920 BT settings

2018-06-12T07:11:42Z

Mantas.slipaitis:

FMT100 Trip/Odometer settings

2018-06-12T07:10:50Z

Mantas.slipaitis: Created page with "{{ Template:FMB Trip/Odometer settings |model=FMT100 |txt_ibutton= |pic_advtrip=right |pic_odometer=Image:Fmb920_odometer.png|300..."

{{
Template:FMB Trip/Odometer settings
|model=FMT100
|txt_ibutton=
|pic_advtrip=[[Image:Fmb920_advtrip_settings.png|300px|right]]
|pic_odometer=[[Image:Fmb920_odometer.png|300px|right]]
|txt_lvcan=
}}

FMT100 Manual Geofence settings

2018-06-12T07:04:31Z

Mantas.slipaitis: Created page with "{{ Template:FMB Manual Geofence settings |model=FMT100 |ctrIO=I/O settings section }}"

{{
Template:FMB Manual Geofence settings
|model=FMT100
|ctrIO=[[FMT100 I/O settings|I/O settings section]]
}}

FMT100 Auto Geofence settings

2018-06-12T06:59:50Z

Mantas.slipaitis: Created page with "{{ Template:FMB Auto Geofence settings |model=FMT100 |pic_autogeofence=right |text_din= * Power Voltage</span..."

{{
Template:FMB Auto Geofence settings
|model=FMT100
|pic_autogeofence=[[Image:Fmb920 autogeofence.png|300px|right]]
|text_din=
* Power Voltage – If power voltage becomes higher than low voltage level (defined in Ignition settings).
* Engine RPM – If engine RPM value becomes higher than 0. 
}}

FMT100 Accelerometer Features settings

2018-06-12T06:36:10Z

Mantas.slipaitis:

{{
Template:FMB Accelerometer Features settings
|model=FMT100
|pic_idling=[[Image:Fmt100 excessive idling.png|right]]
|par_dout=
}}

FMT100 Accelerometer Features settings

2018-06-12T06:35:19Z

Mantas.slipaitis:

{{
Template:FMB Accelerometer Features settings
|model=FMT100
|pic_idling=[[Image:Fmt100 excessive idling.png|right]]
}}

File:Fmt100 excessive idling.png

2018-06-12T06:34:31Z

Mantas.slipaitis:

FMT100 Accelerometer Features settings

2018-06-12T06:32:15Z

Mantas.slipaitis: Created page with "{{ Template:FMB Accelerometer Features settings |model=FMT100 |pic_idling=right }}"

{{
Template:FMB Accelerometer Features settings
|model=FMT100
|pic_idling=[[Image:Fmt100 excessive idling.png|300px|right]]
}}

File:FMT100 jamming.png

2018-06-12T06:29:14Z

Mantas.slipaitis:

File:FMT100 over speeding.png

2018-06-12T06:28:29Z

Mantas.slipaitis:

File:FMT100 green driving.png

2018-06-12T06:27:52Z

Mantas.slipaitis:

FMT100 Features settings

2018-06-12T06:26:59Z

Mantas.slipaitis:

{{
Template:FMB Features settings
|model=FMT100
|text_dout=
|pic_greendriving=[[Image:FMT100_green_driving.png|250px|right]]
|pic_overspeeding=[[Image:FMT100 over speeding.png|300px|right]]
|pic_jamming=[[Image:FMT100_jamming.png|300px|right]]
|template_link=
|par_dout=
}}

FMT100 Features settings

2018-06-12T06:26:35Z

Mantas.slipaitis:

FMT100 Features settings

2018-06-12T06:24:30Z

Mantas.slipaitis:

FMT100 Features settings

2018-06-12T06:12:54Z

Mantas.slipaitis: Created page with "{{ Template:FMB Features settings |model=FMB920 |pic_greendriving=right |pic_overspeeding=Image:Fmb920 over speeding.png|300px|right..."

{{
Template:FMB Features settings
|model=FMB920
|pic_greendriving=[[Image:Fmb920_green_driving.png|250px|right]]
|pic_overspeeding=[[Image:Fmb920 over speeding.png|300px|right]]
|pic_jamming=[[Image:Fmb920_jamming.png|300px|right]]
|template_link={{Template:FMB9 Features settings|model=FMB920}}
}}

FMT100 Data acquisition settings

2018-06-12T06:09:51Z

Mantas.slipaitis: Created page with "{{ Template:FMB Data acquisition settings |model=FMT100 |ctrGsm=GSM Operators settings |ctrSystem=System settings..."

{{
Template:FMB Data acquisition settings
|model=FMT100
|ctrGsm=[[FMT100 GSM Operators settings|GSM Operators settings]]
|ctrSystem=[[FMT100 System settings|System settings]]
|fmb_picture=[[Image:Fmb920_daq_mode_config.png|800px|none]]
}}

File:Fmt100 gsm roaming+bl.png

2018-06-12T05:56:27Z

Mantas.slipaitis:

FMT100 GSM Operators settings

2018-06-12T05:55:42Z

Mantas.slipaitis:

{{
Template:FMB GSM Operators settings
|model=FMT100
|ctrDaq=[[FMT100 Data acquisition settings|Data acquisition settings]]
|pic_operators=[[Image:Fmt100_gsm_roaming%2Bbl.png|800px|none]]
}}

FMT100 GSM Operators settings

2018-06-12T05:53:39Z

Mantas.slipaitis: Created page with "{{ Template:FMB GSM Operators settings |model=FMT100 |ctrDaq=Data acquisition settings }}"

{{
Template:FMB GSM Operators settings
|model=FMT100
|ctrDaq=[[FMT100 Data acquisition settings|Data acquisition settings]]
}}

FMT100 SMS/Call settings

2018-06-12T05:50:55Z

Mantas.slipaitis:

File:Fmt100 handsfree.png

2018-06-12T05:49:09Z

Mantas.slipaitis:

File:Fmt100 smscall settings.png

2018-06-12T05:48:57Z

Mantas.slipaitis:

FMT100 SMS/Call settings

2018-06-12T05:48:43Z

Mantas.slipaitis: Created page with "{{ Template:FMB SMS/Call settings |model=FMT100 |pic_call_settings=none |pic_handsfree=right |..."

{{
Template:FMB SMS/Call settings
|model=FMT100
|pic_call_settings=[[Image:fmt100_smscall_settings.png|800px|none]]
|pic_handsfree=[[Image:fmt100_handsfree.png|300px|right]]
|text_din=''Outgoing Call Trigger'' parameter determines which event will trigger a call. {{{model|FMB920}}} supports eight call trigger settings:
* None selected – disables call trigger functionality.
* DIN1 – first digital input event triggers a call to user selected GSM number.
* Crash Event – crash event triggers a call to user selected GSM number.
* DIN1 and Crash Event – both events trigger a call to user selected GSM number.
}}

FMT100 GPRS settings

2018-06-12T05:43:07Z

Mantas.slipaitis:

{{
Template:FMB GPRS settings
|model=FMT100
|ctrSleepModes=[[FMT100 Sleep modes#Deep Sleep mode|Deep Sleep mode]]
|pic_gprs=[[Image:Fmb920_gprs.png|800px|center]]
|txt_sim2=
}}

FMT100 GPRS settings

2018-06-12T05:41:34Z

Mantas.slipaitis: Created page with "{{ Template:FMB GPRS settings |model=FMT100 |ctrSleepModes=Deep Sleep mode |pic_gprs=center |txt_sim2= }}"

{{
Template:FMB GPRS settings
|model=FMT100
|ctrSleepModes=[[FMBT100 Sleep modes#Deep Sleep mode|Deep Sleep mode]]
|pic_gprs=[[Image:Fmb920_gprs.png|800px|center]]
|txt_sim2=
}}

FMT100 System settings

2018-06-12T05:38:04Z

Mantas.slipaitis:

{{
Template:FMB System settings
|model=FMT100
|template_link={{Template:FMB9 Movement parameters}}
|pic_system=[[Image:fmt100_system.png|none]]
}}

File:Fmt100 system.png

2018-06-12T05:24:20Z

Mantas.slipaitis:

FMT100 System settings

2018-06-12T05:24:06Z

Mantas.slipaitis:

{{
Template:FMB System settings
|model=FMT100
|template_link={{Template:FMB9 Movement parameters}}
|pic_system=[[Image:fmt100_system.png|800px|none]]
}}

FMT100 System settings

2018-06-12T05:19:37Z

Mantas.slipaitis: Created page with "{{ Template:FMB System settings |model=FMT100 |template_link={{Template:FMB9 Movement parameters}} |pic_system=none }}"

{{
Template:FMB System settings
|model=FMT100
|template_link={{Template:FMB9 Movement parameters}}
|pic_system=[[Image:fmb920_system.png|800px|none]]
}}

FMT100 Security info

2018-06-12T05:01:42Z

Mantas.slipaitis: Created page with "{{ Template:FMB Security info |model=FMT100 |txt_sim2= }}"

FMT100 Status info

2018-06-12T05:00:45Z

Mantas.slipaitis: Created page with "{{ Template:FMB Status info |model=FMT100 |txt_fmb0=''OBD Info'' shows the main OBD information (when the device connected to the vehicle via OBD II Bluetooth dongle adapter):..."

{{
Template:FMB Status info
|model=FMT100
|txt_fmb0=''OBD Info'' shows the main OBD information (when the device connected to the vehicle via OBD II Bluetooth dongle adapter): vehicle VIN code and OBD protocol used. 
}}