Difference between revisions of "BASIC TRACK & TRACE"

From Wiki Knowledge Base | Teltonika GPS
m (Text replacement - "Bluetooth" to "Bluetooth®")
(20 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
==Solution description==
 
==Solution description==
 
Teltonika GPS trackers are developed on one '''common firmware platform''', which is constantly being developed and extended with new features. A common platform means that the main core of functionality is the same on all types of our trackers – be it professional, advanced or simple tracker. Smart usage of functions opens for a user various possibilities and brings a valuable advantage comparing to other GPS trackers of a similar price range in the market, making them suitable for different telematics solutions.
 
Teltonika GPS trackers are developed on one '''common firmware platform''', which is constantly being developed and extended with new features. A common platform means that the main core of functionality is the same on all types of our trackers – be it professional, advanced or simple tracker. Smart usage of functions opens for a user various possibilities and brings a valuable advantage comparing to other GPS trackers of a similar price range in the market, making them suitable for different telematics solutions.
[[File:BasicTrackAndTrace.png|alt=|right|thumb|800x400px]]
+
 
 
For a fast and easy “Teltonika data protocols” implementation, data packets parser tool and source code examples of communication server are prepared. For an easy control of the whole fleet, customers get access to '''FOTA WEB''' service for free. FOTA WEB is a powerful tool for remote configuration and firmware updates. Trackers support '''universal configurator''' – a tool for configuration, firmware updates and testing.
 
For a fast and easy “Teltonika data protocols” implementation, data packets parser tool and source code examples of communication server are prepared. For an easy control of the whole fleet, customers get access to '''FOTA WEB''' service for free. FOTA WEB is a powerful tool for remote configuration and firmware updates. Trackers support '''universal configurator''' – a tool for configuration, firmware updates and testing.
  
 
The basic firmware functionality supports such generic features like sleep modes, trip detection, and different data acquisition modes that depend on ignition/movement source or even the connected GSM operator. The device supports different ignition detection modes, depending on the installation variant. Moreover, it supports such advanced functions like auto geofence, towing detection, green driving, crash event detection, virtual odometer, unplug detection, GPRS/SMS notifications and many more. The user can easily enable the function he needs using the configurator or FOTA WEB and change the configuration in accordance with the changing needs of the client.
 
The basic firmware functionality supports such generic features like sleep modes, trip detection, and different data acquisition modes that depend on ignition/movement source or even the connected GSM operator. The device supports different ignition detection modes, depending on the installation variant. Moreover, it supports such advanced functions like auto geofence, towing detection, green driving, crash event detection, virtual odometer, unplug detection, GPRS/SMS notifications and many more. The user can easily enable the function he needs using the configurator or FOTA WEB and change the configuration in accordance with the changing needs of the client.
  
Teltonika trackers also support '''BLE technology''' that significantly expands their functionality. For example, if a client wants to get more telemetric vehicle data, it is possible to connect via Bluetooth® OBDII dongle and read such data like millage, engine hours, engine faults, fuel level, etc. Advanced BLE mode lets to configure BLE beacons and various BLE sensors (temperature, humidity, movement, etc.). BLE beacons can be used as an immobilizer or for the authentication of drivers and passengers. Another possible way of using them is to monitor assets during transportation, even for indoor tracking. By the way, it also is possible to configure a device via Bluetooth®. Teltonika provides Bluetooth® communication protocols so that users could develop their own mobile application to read notifications in real time and do many other useful functions with their trackers.
+
Teltonika trackers also support '''BLE technology''' that significantly expands their functionality. For example, if a client wants to get more telemetric vehicle data, it is possible to connect via Bluetooth OBDII dongle and read such data like millage, engine hours, engine faults, fuel level, etc. Advanced BLE mode lets to configure BLE beacons and various BLE sensors (temperature, humidity, movement, etc.). BLE beacons can be used as an immobilizer or for the authentication of drivers and passengers. Another possible way of using them is to monitor assets during transportation, even for indoor tracking. By the way, it also is possible to configure a device via Bluetooth. Teltonika provides Bluetooth communication protocols so that users could develop their own mobile application to read notifications in real time and do many other useful functions with their trackers.
  
 
==What you need for a solution?==
 
==What you need for a solution?==
Line 23: Line 23:
 
*The [https://wiki.teltonika-gps.com/view/FMB920_First_Start#How_to_insert_Micro-SIM_card '''SIM card'''] in order to get data to your server
 
*The [https://wiki.teltonika-gps.com/view/FMB920_First_Start#How_to_insert_Micro-SIM_card '''SIM card'''] in order to get data to your server
 
*[https://wiki.teltonika-gps.com/view/EYE_FAQ '''EYE BEACON/SENSOR'''] BLE sensors that can be additionally connected if necessary
 
*[https://wiki.teltonika-gps.com/view/EYE_FAQ '''EYE BEACON/SENSOR'''] BLE sensors that can be additionally connected if necessary
*[https://wiki.teltonika-gps.com/view/How_to_connect_OBD_II_Bluetooth®_Dongle_to_FMB_device#Supported_Bluetooth®_OBD_II_dongles '''Bluetooth® OBD II dongles'''] Bluetooth® OBD II dongles from other manufacturers can be connected if necessary to receive data from the OBD connector
+
*[https://wiki.teltonika-gps.com/view/How_to_connect_OBD_II_Bluetooth_Dongle_to_FMB_device#Supported_Bluetooth_OBD_II_dongles '''Bluetooth OBD II dongles'''] Bluetooth OBD II dongles from other manufacturers can be connected if necessary to receive data from the OBD connector
 
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />
 
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device<br />
  
 
==Installation==
 
==Installation==
  
It’s important to hide the tracker, so it would not be a simple task for the thieves to find and unplug it. But also, please do not forget to follow [https://wiki.teltonika-gps.com/view/FMB920_First_Start#Mounting_recommendations mounting recommendations] as well.
+
It’s important to hide the tracker, so it would not be a simple task for the thieves to find and unplug it. But also, please do not forget to follow [https://wiki.teltonika-gps.com/view/FMB130_First_Start#Mounting_recommendations mounting recommendations] as well.
  
 
Although devices have high gain antennas it’s important to mount devices with stickers on top and in metal-free space. The device should be firmly fixed to the surface or cables. Please make sure, that device is not fixed to heat emitting or moving parts.
 
Although devices have high gain antennas it’s important to mount devices with stickers on top and in metal-free space. The device should be firmly fixed to the surface or cables. Please make sure, that device is not fixed to heat emitting or moving parts.
  
[[File:MAGNET.png|alt=|left|thumb|600x200px]]
+
The main accessory for the solution is '''CAN-CONTROL adapter''', please make sure that the right contacts are connected. Also, check more detailed information [https://wiki.teltonika-gps.com/view/FMB130_CAN_adapters#Installing_LV-CAN200.2FALL-CAN300.2FCAN-CONTROL here] and [https://wiki.teltonika-gps.com/wikibase/images/f/f1/CANCONTROL_list_2020_09_16_en.pdf supported vehicle list].
  
 +
To have a working solution it’s important to properly wire the devices. In the picture below it's shown how to correctly wire the devices.
  
 +
[[File:Can-control_connection_example_updated.png|alt=|middle|frameless|1100x357px]]
  
 +
During installation please follow recommendations in order to '''avoid damaging''' device and vehicle:
  
 +
*Wires should be connected while the module is '''not plugged''' in.
 +
*Be sure that after the car computer falls asleep, power is still available on the chosen wire. Depending on the car, this may happen in a 5 to 30 minutes period.
 +
*When the module is connected, be sure to measure the voltage again if it did not decrease.
 +
*The ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.<br>
  
Additional accessories such as '''EYE SENSOR''' or '''EYE BEACON''' can be used for this solution. EYE SENSOR can transmit to the tracker parameters such as temperature, humidity, angle, movement, data on the presence of a magnetic field. EYE SENSOR and EYE BEACON can transmit a unique identification number, which can be used in many scenarios, such as an immobilizer, more details [https://wiki.teltonika-gps.com/view/FMB920_Features_settings#Immobilizer here]. Also, check more detailed information about EYE SENSOR and EYE BEACON [https://wiki.teltonika-gps.com/view/EYE_SENSOR_/_BTSMP1 here] and [https://wiki.teltonika-gps.com/view/EYE_BEACON_/_BTSID1 here].
+
==Configuration==
[[File:OBDdongle.png|alt=|left|thumb|800x300px]]
 
  
 +
==='''1. Prerequisites:'''===
  
 +
====1.1. Read through [https://wiki.teltonika-gps.com/view/FMB130_First_Start First start guide]====
 +
====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/FMB130_Sleep_modes Sleep modes].====
 +
==='''2. Car sharing configuration:'''===
 +
[[File:GPRS settings.png|alt=|left|thumb|258x258px]]
  
 +
Parameter ID – Parameter name GPRS settings:
  
 +
<br />
  
 +
*<span style="background-color:#91b9d4;">2001</span> – APN
 +
*<span style="background-color:#91d4b9;">2002</span> – APN username (if there are no APN username, empty field should be left)
 +
*<span style="background-color:#b991d4;">2003</span> – APN password (if there are no APN password, empty field should be left)
  
 +
[[File:SERVER settings.png|alt=|left|thumb|259x259px]]
  
  
  
 +
<br />Server settings:
  
 +
*<span style="background-color:#b9d491;">2004</span> – Domain
 +
*<span style="background-color:#d491b9;">2005</span> – Port
 +
*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
  
 +
<br />
  
  
  
You can also use third-party '''OBD BT dongles''' for this solution (if there is a need to get data from the vehicle's OBDII interface. You can read more about selecting the appropriate OBD BT dongle models [https://wiki.teltonika-gps.com/view/How_to_connect_OBD_II_Bluetooth®_Dongle_to_FMB_device#Supported_Bluetooth®_OBD_II_dongles here].
 
  
<br>
 
  
  
 +
After successful GPRS/SERVER settings configuration, FMB130 device will '''synchronize time''' and '''update records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMB130 Parameter list|SMS parameters]].<br />
 +
[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]
  
  
 +
Sleep settings:
 +
<br />
 +
*<span style="background:#05CC6F">102</span> – Sleep settings(0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep)
 +
'''Note''': This scenario will not work with [[FMB130 Sleep modes#Deep%20Sleep%20mode|Deep Sleep]] and [[FMB130 Sleep modes#Ultra%20Deep%20Sleep%20mode|Ultra Sleep]] modes, since they disable the device's GSM module to save power.
  
  
  
 +
[[File:Can adapter settings carsharing solution.JPG|alt=|left|frame]]
 +
<br />
 +
<br />
 +
<br />
 +
<br />
 +
Can adapter settings:
  
 +
*<span style="background-color:#E18DE7;">45002</span> – CAN Adapter program number (This code is written in every connection diagram and it is specific for every vehicle model and make year)
  
 +
[[File:Can_adapter_door_status_settings.PNG|alt=|left|455x455px|thumb]]
 +
<br />
  
==Configuration==
 
  
==='''1. Prerequisites:'''===
 
  
====1.1. Read through [https://wiki.teltonika-gps.com/view/FMB920_First_Start First start guide]====
 
====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/FMB920_Sleep_modes Sleep modes].====
 
==='''2. BASIC TRACK & TRACE configuration:'''===
 
[[File:GPRS settings.png|alt=|left|thumb|258x258px]]
 
  
  
  
Parameter ID Parameter name GPRS settings:
+
*<span style="background-color:#dee11d;">45170</span> – Door status, Priority "Low" (0 – Disabled 1 – Low 2 High 3 – Panic )
  
 +
[[File:Can_adapter_fuel_level_settings.PNG|alt=|left|453x453px|thumb]]
 
<br />
 
<br />
  
*<span style="background-color:#91b9d4;">2001</span> – APN
 
*<span style="background-color:#91d4b9;">2002</span> – APN username (if there are no APN username, empty field should be left)
 
*<span style="background-color:#b991d4;">2003</span> – APN password (if there are no APN password, empty field should be left)
 
  
[[File:SERVER settings.png|alt=|left|thumb|259x259px]]
 
  
  
Line 92: Line 118:
  
  
<br />Server settings:
 
  
*<span style="background-color:#b9d491;">2004</span> – Domain
 
*<span style="background-color:#d491b9;">2005</span> – Port
 
*<span style="background-color:#d4b991;">2006</span> – Data sending protocol (0 – TCP, 1 – UDP)
 
  
 +
*<span style="background-color:#1de1d2;">45130</span> – Fuel level, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 +
 +
[[File:Can_adapter_settings_total_milage_counted.PNG|alt=|left|452x452px|thumb]]
 
<br />
 
<br />
  
  
After successful GPRS/SERVER settings configuration, FMB920 device will '''synchronize time''' and '''update records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [https://wiki.teltonika-gps.com/view/Teltonika_Configurator_versions Teltonika Configurator] or [https://wiki.teltonika-gps.com/view/FMB920_Parameter_list FMB920 Parameter list|SMS parameters].<br />
 
[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]
 
  
  
Sleep settings:
 
<br />
 
*<span style="background:#05CC6F">102</span> – Sleep settings(0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep)
 
'''Note''': This scenario will not work with [[FMB130 Sleep modes#Deep%20Sleep%20mode|Deep Sleep]] and [[FMB130 Sleep modes#Ultra%20Deep%20Sleep%20mode|Ultra Sleep]] modes, since they disable the device's GSM module to save power.
 
  
  
  
  
<br />
 
<br />
 
<br />
 
<br />
 
Can adapter settings:
 
<br />
 
  
[[File:Obdii.png|alt=|left|455x455px|thumb]]
+
*<span style="background-color:#e1701d;">45220</span> – Total milage (Counted), Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 +
 
 +
[[File:Sec_state_flag_P2.PNG|alt=|left|453x453px|thumb]]
 +
 
  
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
*<span style="background-color:#E18DE7;">807</span> – OBDII mode (This setting enables the BT module in ODBII mode)
 
<br />
 
<br />
 
  
  
  
*<span style="background-color:#dee11d;">805</span> – This field contains the name of the device to which the tracker will connect via the BT channel
 
  
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
  
[[File:ObdIO.png|alt=|left|452x452px|thumb]]
 
<br />
 
<br />
 
<br />
 
*<span style="background-color:#1de1d2;">40100</span> – Number Of DTC, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 
  
  
  
*<span style="background-color:#e1701d;">40160</span> – Engine RPM, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 
  
  
  
*<span style="background-color:#bce5d7;">40170</span> – Vehicle Speed, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
+
*<span style="background-color:#bce5d7;">45430</span> – Security State Flags, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
<br />
 
<br />
 
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 +
 
<br />
 
<br />
<br />
+
'''Quickstart:''' From default configuration to Car sharing solution in one SMS:
'''Quickstart:''' From default configuration to BASIC TRACK & TRACE solution in one SMS:
+
  "  setparam <span style="background-color:#91b9d4;">2001</span>:APN;<span style="background-color:#91d4b9;">2002</span>:APN_user;<span style="background-color:#b991d4;">2003</span>:APN_password;<span style="background-color:#b9d491;">2004</span>:Domain;<span style="background-color:#d491b9;">2005</span>:Port;<span style="background-color:#d4b991;">2006</span>:0;<span style="background:#05CC6F">102</span>:3;<span style="background:#E18DE7">45002</span>:ProgramNumber;<span style="background-color:#dee11d;">45170</span>:1;<span style="background-color:#1de1d2;">45130</span>:1;<span style="background-color:#e1701d;">45220</span>:1;<span style="background-color:#bce5d7;">45430</span>:1"
  "  setparam <span style="background-color:#91b9d4;">2001</span>:APN;<span style="background-color:#91d4b9;">2002</span>:APN_user;<span style="background-color:#b991d4;">2003</span>:APN_password;<span style="background-color:#b9d491;">2004</span>:Domain;<span style="background-color:#d491b9;">2005</span>:Port;<span style="background-color:#d4b991;">2006</span>:0;<span style="background:#05CC6F">102</span>:3;<span style="background:#E18DE7">807</span>:2;<span style="background-color:#dee11d;">805</span>:DONGLE;<span style="background-color:#1de1d2;">40100</span>:1;<span style="background-color:#e1701d;">40160</span>:1;<span style="background-color:#bce5d7;">40170</span>:1"
+
This SMS will set up your device to report the Car Sharing scenario to the server and the possibility for remote control of vehicle components.
This SMS will set up your device to report the BASIC TRACK & TRACE scenario to the server and the possibility receive data when using OBDII BT dongle.
 
  
 
'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.
 
'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.
  
 
'''To use EYE SENSOR sensors''', it is best to use the Teltonika configurator, as it becomes necessary to select the correct preset.
 
 
[[File:Codec 8.png|alt=|left|452x452px|thumb]]
 
 
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
*Set the Data Protocol setting to Codec 8 Extended
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
[[File:Sensor settings.png|alt=|left|452x452px|thumb]]
 
<br />
 
*In the Bluetooth® 4.0 section, set the operating mode for one of the 4 sensors as Advanced
 
<br />
 
<br />
 
*Enter the MAC address of the sensor
 
<br />
 
<br />
 
*Select the appropriate preset and load it
 
<br />
 
<br />
 
[[File:Sensor IO.png|alt=|left|452x452px|thumb]]
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
*In the I / O section, select the sensor parameters of interest: these can be temperature, humidity, motion sensor, magnetic field sensor, tilt angle sensor, sensor battery level.
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
 
==Parsing information==
 
==Parsing information==
  
Line 224: Line 173:
 
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
 
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" | 00 00 00 00 00 00 00 32 8E 01 00 00 01 7E 06 5D E1 B8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C0 00 06 <span style="background:#0b9768">00 EF</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 F0</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 01</span> <span style="background:#d4f991">01</span> <span style="background:#0b9768">00 B3</span> <span style="background:#d4f991">01</span> <span style="background:#0b9768">00 1E</span> <span style="background:#d4f991">00</span> <span style="background:#0b9768">00 25</span> <span style="background:#d4f991">00</span> 00 03 <span style="background:#0b9768">00 19</span> <span style="background:#d4f991">00 7D</span> <span style="background:#0b9768">00 56</span> <span style="background:#d4f991">03 25</span> <span style="background:#0b9768">00 24</span><span style="background:#d4f991"> 03 84 </span> 00 00 00 03 <span style="background:#0b9768">01 4B</span> <span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> <span style="background:#0b9768">01 CF</span> <span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> <span style="background:#0b9768">01 D0</span> <span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> 00 00 01 00 00 79 3F
+
| style="vertical-align: middle; text-align: center;" | 000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443
 +
0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E
 +
97660000000069023B33856B000065B27B000000007D00000000BD000000000184<span style="background:#0b9768">0080000030000005</span>0100005C92
  
 
|}
 
|}
Line 232: Line 183:
 
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
 
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
+
| style="vertical-align: middle; text-align: center;" | Zero Bytes
 
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Data Field Length
 
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 32
+
| style="vertical-align: middle; text-align: center;" |00 00 00 8F
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Codec ID
 
| style="vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E (Codec 8 Extended)
+
| style="vertical-align: middle; text-align: center;" |08 (Codec 8)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
 
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
Line 245: Line 196:
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Timestamp
 
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 7E 06 5D E1 B8
+
| style="vertical-align: middle; text-align: center;" |00 00 01 77 B0 A5 F8 38 (Thursday, February 18, 2021 3:43:00 PM GMT+02:00)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |Priority
+
| style="vertical-align: middle; text-align: center;" | Priority
 
| style="vertical-align: middle; text-align: center;" |00
 
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
Line 254: Line 205:
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00  
+
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
+
| style="vertical-align: middle; text-align: center;" |00 44
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
+
| style="vertical-align: middle; text-align: center;" |00 28
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Satellites
 
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
+
| style="vertical-align: middle; text-align: center;" |0D
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Speed
 
| style="vertical-align: middle; text-align: center;" |Speed
Line 269: Line 220:
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Event IO ID
 
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 00
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |N of Total ID
 
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 C0
+
| style="vertical-align: middle; text-align: center;" |1F
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
 
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 06
+
| style="vertical-align: middle; text-align: center;" |09
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 EF</span> (AVL ID 239, Name: Ignition)
+
| style="vertical-align: middle; text-align: center;" |EF (AVL ID: 239, Name: Ignition)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00</span>
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 F0</span> (AVL ID 240, Name: Movement)
+
| style="vertical-align: middle; text-align: center;" |F0 (AVL ID: 240, Name: Movement)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00</span>
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
+
| style="vertical-align: middle; text-align: center;" | 3’rd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 01</span> (AVL ID 1, Name: Digital Input 1)
+
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" | 3’rd IO Value
 +
| style="vertical-align: middle; text-align: center;" |04
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |B3 (AVL ID: 179, Name: Digital Output 1)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |B4 (AVL ID: 180, Name: Digital Output 2)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 +
| style="vertical-align: middle; text-align: center;" | 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |51 (AVL ID: 81, Name: Vehicle Speed)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
+
| style="vertical-align: middle; text-align: center;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">01</span> (Digital Input 1 state 1 - Digital Input 1 on)
+
| style="vertical-align: middle; text-align: center;" | 00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
+
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 B3</span> (AVL ID 179, Name: Digital Output 1)
+
| style="vertical-align: middle; text-align: center;" |52 (AVL ID: 82, Name: Accelerator Pedal Position)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |4’th IO Value
+
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">01</span> (Digital Output 1 state 1 - Digital Output 1 on)
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |5’th IO ID
+
| style="vertical-align: middle; text-align: center;" |8'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 1E</span> (AVL ID 30, Name: Number of DTC)
+
| style="vertical-align: middle; text-align: center;" |59 (AVL ID: 89, Name: Fuel level)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |5’th IO Value
+
| style="vertical-align: middle; text-align: center;" |8'th IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00</span> (Number of DTC state 0 - without DTC)
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |6’th IO ID
+
| style="vertical-align: middle; text-align: center;" |9'th IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 25</span> (AVL ID 37, Name: Vehicle Speed)
+
| style="vertical-align: middle; text-align: center;" |98 (AVL ID: 152, Name: Geofence zone 05)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |6’th IO Value
+
| style="vertical-align: middle; text-align: center;" |9'th IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00</span> (Vehicle Speed 0 )
+
| style="vertical-align: middle; text-align: center;" |00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
+
| style="vertical-align: middle; text-align: center;" | N2 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |00 03
+
| style="vertical-align: middle; text-align: center;" |0B
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 19</span> (AVL ID 25, Name: BLE Temperature #1)
+
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00 7D</span> (Temperature value 1.25 degrees Celsius)
+
| style="vertical-align: middle; text-align: center;" |30 74
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 56</span> (AVL ID 86, Name: BLE Humidity #1)
+
| style="vertical-align: middle; text-align: center;" |43 (AVL ID: 67, Name: Battery Voltage)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">03 25</span> (Humidity 80.5%)
+
| style="vertical-align: middle; text-align: center;" |0F 82
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
 
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 24</span> (AVL ID 36, Name: Engine RPM)
+
| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Name: Battery Current)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
 
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">03 84</span> (Engine RPM state 900 RPM)
+
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
+
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |11 (AVL ID: 17, Name: Axis X)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 18
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |12 (AVL ID: 18,Name: Axis Y)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |0F 8A
 +
|-
 +
| style="vertical-align: middle; text-align: center;" | 6'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |13 (AVL ID: 19, Name: Axis Z)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |FF E8
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |7'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |54 (AVL ID: 84,Name: Fuel level)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |7'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 BE
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |8'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |55 (AVL ID:85, Name: Engine RPM)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |8’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |9'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |5A (AVL ID:90, Name: Door Status)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |9’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |10'th IO ID
 +
| style="vertical-align: middle; text-align: center;" |97 (AVL ID:151, Name: Battery Temperature)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |10'th IO Value
 
| style="vertical-align: middle; text-align: center;" |00 00
 
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes IO
+
| style="vertical-align: middle; text-align: center;" |11'th IO ID
| style="vertical-align: middle; text-align: center;" |00 03
+
| style="vertical-align: middle; text-align: center;" |A8 (AVL ID: 168, Battery Voltage)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |11'th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
+
| style="vertical-align: middle; text-align: center;" |N4 of Four Byte IO
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 4B</span> (AVL ID 331, Name: BLE 1 Custom #1)
+
| style="vertical-align: middle; text-align: center;" |0A
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1'st IO ID
 +
| style="vertical-align: middle; text-align: center;" |F1 (AVL ID: 241, Name: Active GSM Operator)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00 00 00 00 00 00 00 H7</span> (Flags. Each set bit (0-7) means the presence of value (0-7).)
+
| style="vertical-align: middle; text-align: center;" | 00 00 60 1A
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 CF</span> (AVL ID 463, Name: BLE 1 Custom #2)
+
| style="vertical-align: middle; text-align: center;" |53 (AVL ID: 83, Name: Fuel Consumed)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
 
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00 00 00 00 00 00 0C CB</span> (Movement status)
+
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
 
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 D0</span> (AVL ID 464, Name: BLE 1 Custom #3)
+
| style="vertical-align: middle; text-align: center;" |57 (AVL ID: 87, Name: Total Mileage)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
 
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |<span style="background:#d4f991">00 00 00 00 00 0B FF C7</span> (Angle. 0B – Most significant byte represents device pitch. FFC7– Two least significant bytes represent device roll.)
+
| style="vertical-align: middle; text-align: center;" |03 CB 6B 98
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |64 (AVL ID: 100, Name: Program Number)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |4’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 2E 97
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |66 (AVL ID: 102, Name: Engine Worktime)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |5’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |69 (AVL ID: 105, Name: Total Mileage (counted))
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |6’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |02 3B 33 85
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |7’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |6B (AVL ID: 107, Name: Fuel Consumed(counted))
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |7’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 65 B2
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |8’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |7B (AVL ID: 123, Name: Control State Flags)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |8’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |9’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |7D (AVL ID: 125, Name: Harvesting Time)
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |NX of X Byte IO
+
| style="vertical-align: middle; text-align: center;" |9’th IO Value
| style="vertical-align: middle; text-align: center;" |00 00
+
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |10’th IO ID
 +
| style="vertical-align: middle; text-align: center;" |BD (AVL ID: 189, Name: Cruise Time)
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |10’th IO Value
 +
| style="vertical-align: middle; text-align: center;" |00 00 00 00
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |N8 of Eight Byte IO
 +
| style="vertical-align: middle; text-align: center;" |01
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1'st IO ID
 +
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">84 (AVL ID: 132, Name: Security State Flags)</span>
 +
|-
 +
| style="vertical-align: middle; text-align: center;" |1’st IO Value
 +
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">00 80 00 00 30 00 00 05</span>
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
 
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
Line 365: Line 427:
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |CRC-16
 
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 79 3F
+
| style="vertical-align: middle; text-align: center;" |00 00 5C 92
 
|}
 
|}
  
 +
Security State Flag Examples:
 +
*1) Locked doors <span style="background:#0b9768">00 80 00 00 30 00 00 05</span>
 +
*2) Unlocked doors <span style="background:#d4f991">00 80 00 00 00 00 00 05</span>
 +
 +
Convert HEX value to BIN value:
 +
 +
Then count 28'th BIT from the back (28'th bit value shows locked/unlocked states)
 +
*1) 100000000000000000000000001<span style="background:#0b9768">1</span>0000000000000000000000000101
 +
*2) 100000000000000000000000000<span style="background:#d4f991">0</span>0000000000000000000000000101
 +
If car is locked value is <span style="background:#0b9768>1</span> and if car is unlocked value is <span style="background:#d4f991">0</span>
 +
 +
To test the car unlocking and locking use these GPRS commands
 +
*1) To unlock all doors use this command: "lvcanopenalldoors"
 +
*2) To lock all doors use this command: "lvcanclosealldoors"
  
<br>
 
 
[[Category: Usage scenarios]]
 
[[Category: Usage scenarios]]

Revision as of 13:54, 28 October 2022

Main Page > General Information > Usage scenarios > BASIC TRACK & TRACE

Introduction

Nowadays, when smart devices are progressing very fast, the phrase “basic track and trace” has a new meaning. Getting only the coordinates from the device is not enough anymore. Therefore, GPS trackers must be universal to meet various requirements. Among other things, when choosing a GPS tracker, it is very important to understand what additional services and tools you will get with the device.

Solution description

Teltonika GPS trackers are developed on one common firmware platform, which is constantly being developed and extended with new features. A common platform means that the main core of functionality is the same on all types of our trackers – be it professional, advanced or simple tracker. Smart usage of functions opens for a user various possibilities and brings a valuable advantage comparing to other GPS trackers of a similar price range in the market, making them suitable for different telematics solutions.

For a fast and easy “Teltonika data protocols” implementation, data packets parser tool and source code examples of communication server are prepared. For an easy control of the whole fleet, customers get access to FOTA WEB service for free. FOTA WEB is a powerful tool for remote configuration and firmware updates. Trackers support universal configurator – a tool for configuration, firmware updates and testing.

The basic firmware functionality supports such generic features like sleep modes, trip detection, and different data acquisition modes that depend on ignition/movement source or even the connected GSM operator. The device supports different ignition detection modes, depending on the installation variant. Moreover, it supports such advanced functions like auto geofence, towing detection, green driving, crash event detection, virtual odometer, unplug detection, GPRS/SMS notifications and many more. The user can easily enable the function he needs using the configurator or FOTA WEB and change the configuration in accordance with the changing needs of the client.

Teltonika trackers also support BLE technology that significantly expands their functionality. For example, if a client wants to get more telemetric vehicle data, it is possible to connect via Bluetooth OBDII dongle and read such data like millage, engine hours, engine faults, fuel level, etc. Advanced BLE mode lets to configure BLE beacons and various BLE sensors (temperature, humidity, movement, etc.). BLE beacons can be used as an immobilizer or for the authentication of drivers and passengers. Another possible way of using them is to monitor assets during transportation, even for indoor tracking. By the way, it also is possible to configure a device via Bluetooth. Teltonika provides Bluetooth communication protocols so that users could develop their own mobile application to read notifications in real time and do many other useful functions with their trackers.

What you need for a solution?

  • FMx920 device (FMB920 is taken as example) a simple tracker with a basic set of functions.
Other devices that work with this solution:
FMB965, FMC920, FMB003, FMB001, FMC003, FMM920, FMM003, FMB002, FMB020
  • The SIM card in order to get data to your server
  • EYE BEACON/SENSOR BLE sensors that can be additionally connected if necessary
  • Bluetooth OBD II dongles Bluetooth OBD II dongles from other manufacturers can be connected if necessary to receive data from the OBD connector
  • FOTA WEB to remotely send the configuration to the device

Installation

It’s important to hide the tracker, so it would not be a simple task for the thieves to find and unplug it. But also, please do not forget to follow mounting recommendations as well.

Although devices have high gain antennas it’s important to mount devices with stickers on top and in metal-free space. The device should be firmly fixed to the surface or cables. Please make sure, that device is not fixed to heat emitting or moving parts.

The main accessory for the solution is CAN-CONTROL adapter, please make sure that the right contacts are connected. Also, check more detailed information here and supported vehicle list.

To have a working solution it’s important to properly wire the devices. In the picture below it's shown how to correctly wire the devices.

During installation please follow recommendations in order to avoid damaging device and vehicle:

  • Wires should be connected while the module is not plugged in.
  • Be sure that after the car computer falls asleep, power is still available on the chosen wire. Depending on the car, this may happen in a 5 to 30 minutes period.
  • When the module is connected, be sure to measure the voltage again if it did not decrease.
  • The ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.

Configuration

1. Prerequisites:

1.1. Read through First start guide

1.2. Understanding of possible Sleep modes.

2. Car sharing configuration:

Parameter ID – Parameter name GPRS settings:


  • 2001 – APN
  • 2002 – APN username (if there are no APN username, empty field should be left)
  • 2003 – APN password (if there are no APN password, empty field should be left)



Server settings:

  • 2004 – Domain
  • 2005 – Port
  • 2006 – Data sending protocol (0 – TCP, 1 – UDP)





After successful GPRS/SERVER settings configuration, FMB130 device will synchronize time and update records to the configured server. Time intervals and default I/O elements can be changed by using Teltonika Configurator or SMS parameters.


Sleep settings:

  • 102 – Sleep settings(0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep)

Note: This scenario will not work with Deep Sleep and Ultra Sleep modes, since they disable the device's GSM module to save power.






Can adapter settings:

  • 45002 – CAN Adapter program number (This code is written in every connection diagram and it is specific for every vehicle model and make year)





  • 45170 – Door status, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )






  • 45130 – Fuel level, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )






  • 45220 – Total milage (Counted), Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )







  • 45430 – Security State Flags, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )





Quickstart: From default configuration to Car sharing solution in one SMS:

"  setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;45002:ProgramNumber;45170:1;45130:1;45220:1;45430:1"

This SMS will set up your device to report the Car Sharing scenario to the server and the possibility for remote control of vehicle components.

Note: Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.

Parsing information

1.Prerequisites:

1.1. Open TCP/UDP port

1.2. Read Java parser first start guide

2. Parsing example:

Unparsed received data in hexadecimal stream
000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443

0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E 97660000000069023B33856B000065B27B000000007D00000000BD00000000018400800000300000050100005C92

AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 8F
Codec ID 08 (Codec 8)
Number of Data 1 (Number of Total Records) 01
Timestamp 00 00 01 77 B0 A5 F8 38 (Thursday, February 18, 2021 3:43:00 PM GMT+02:00)
Priority 00
Longitude 00 00 00 00
Latitude 00 00 00 00
Altitude 00 44
Angle 00 28
Satellites 0D
Speed 00 00
Event IO ID 00
N of Total ID 1F
N1 of One Byte IO 09
1’st IO ID EF (AVL ID: 239, Name: Ignition)
1’st IO Value 00
2’nd IO ID F0 (AVL ID: 240, Name: Movement)
2’nd IO Value 00
3’rd IO ID 15 (AVL ID: 21, Name: GSM Signal)
3’rd IO Value 04
4'th IO ID B3 (AVL ID: 179, Name: Digital Output 1)
4'th IO Value 01
5'th IO ID B4 (AVL ID: 180, Name: Digital Output 2)
5'th IO Value 00
6'th IO ID 51 (AVL ID: 81, Name: Vehicle Speed)
6'th IO Value 00
7'th IO ID 52 (AVL ID: 82, Name: Accelerator Pedal Position)
7'th IO Value 00
8'th IO ID 59 (AVL ID: 89, Name: Fuel level)
8'th IO Value 00
9'th IO ID 98 (AVL ID: 152, Name: Geofence zone 05)
9'th IO Value 00
N2 of Two Byte IO 0B
1’st IO ID 42 (AVL ID: 66, Name: External Voltage)
1’st IO Value 30 74
2’nd IO ID 43 (AVL ID: 67, Name: Battery Voltage)
2’nd IO Value 0F 82
3’rd IO ID 44 (AVL ID: 68, Name: Battery Current)
3’rd IO Value 00 00
4'th IO ID 11 (AVL ID: 17, Name: Axis X)
4'th IO Value 00 18
5'th IO ID 12 (AVL ID: 18,Name: Axis Y)
5'th IO Value 0F 8A
6'th IO ID 13 (AVL ID: 19, Name: Axis Z)
6'th IO Value FF E8
7'th IO ID 54 (AVL ID: 84,Name: Fuel level)
7'th IO Value 00 BE
8'th IO ID 55 (AVL ID:85, Name: Engine RPM)
8’th IO Value 00 00
9'th IO ID 5A (AVL ID:90, Name: Door Status)
9’th IO Value 00 00
10'th IO ID 97 (AVL ID:151, Name: Battery Temperature)
10'th IO Value 00 00
11'th IO ID A8 (AVL ID: 168, Battery Voltage)
11'th IO Value 00 00
N4 of Four Byte IO 0A
1'st IO ID F1 (AVL ID: 241, Name: Active GSM Operator)
1’st IO Value 00 00 60 1A
2’nd IO ID 53 (AVL ID: 83, Name: Fuel Consumed)
2’nd IO Value 00 00 00 00
3’rd IO ID 57 (AVL ID: 87, Name: Total Mileage)
3’rd IO Value 03 CB 6B 98
4’th IO ID 64 (AVL ID: 100, Name: Program Number)
4’th IO Value 00 00 2E 97
5’th IO ID 66 (AVL ID: 102, Name: Engine Worktime)
5’th IO Value 00 00 00 00
6’th IO ID 69 (AVL ID: 105, Name: Total Mileage (counted))
6’th IO Value 02 3B 33 85
7’th IO ID 6B (AVL ID: 107, Name: Fuel Consumed(counted))
7’th IO Value 00 00 65 B2
8’th IO ID 7B (AVL ID: 123, Name: Control State Flags)
8’th IO Value 00 00 00 00
9’th IO ID 7D (AVL ID: 125, Name: Harvesting Time)
9’th IO Value 00 00 00 00
10’th IO ID BD (AVL ID: 189, Name: Cruise Time)
10’th IO Value 00 00 00 00
N8 of Eight Byte IO 01
1'st IO ID 84 (AVL ID: 132, Name: Security State Flags)
1’st IO Value 00 80 00 00 30 00 00 05
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 5C 92

Security State Flag Examples:

  • 1) Locked doors 00 80 00 00 30 00 00 05
  • 2) Unlocked doors 00 80 00 00 00 00 00 05

Convert HEX value to BIN value:

Then count 28'th BIT from the back (28'th bit value shows locked/unlocked states)

  • 1) 10000000000000000000000000110000000000000000000000000101
  • 2) 10000000000000000000000000000000000000000000000000000101

If car is locked value is 1 and if car is unlocked value is 0

To test the car unlocking and locking use these GPRS commands

  • 1) To unlock all doors use this command: "lvcanopenalldoors"
  • 2) To lock all doors use this command: "lvcanclosealldoors"