CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE

2023-02-21T08:44:36Z

AndrewBakalov:

==Introduction==

Many transport businesses are regulated by governments worldwide. For example, lorries must be equipped with digital tachographs so that the data is sent according to a schedule; E-TOLL, modern toll collection solutions, are governed and electronically charged. Reporting is being digitised and made mandatory at the government level. Given this, measures should be put in place to facilitate the ease of data transfer and ensure its stability.

==Solution description==
As most transport and logistics companies are controlled by public authorities, fleet owners are required to submit digital tachograph charts regularly based on strict rules. Failure to submit data on time will inevitably result in heavy fines. According to the UK government website GOV.UK, the maximum fine for failing to do so can reach up to £10,000 and as much as 2-year imprisonment!

In the case of E-TOLL, a GPS tracker sends information on the location of a vehicle, the data is processed in the payment collection system, and a local National Revenue Administration automatically taxes the vehicle or fleet owners respectively. For example, if the data is not submitted on time in Poland, a car owner has to pay a fine, which starts at €300 per violation, as stated on the Ministry of Finance website etoll.gov.pl.

But what happens if the data is used up or the mobile network SIM card expires? Of course, the tracking device will be disconnected from the GSM network and no data will be sent at all.

Fortunately, Teltonika Telematics has a practical solution to help corporate fleets avoid such needless fines and ensure that the SIM cards of GPS trackers are always connected to the GSM network.

Every single Teltonika vehicle GPS tracker has a placeholder for a plastic (regular) SIM card or a possibility to install an eSIM module. The SIM card or eSIM is part of the Teltonika Global Connectivity Solution and is used to connect to mobile networks, and the GPS device will be able to send and receive data to and from locations covered by the data plan.
[[File:Truphone_solution.png|left|frameless|700x700px]]
For example, the Teltonika Global Plan currently allows you to prevent roaming costs in 110 countries around the world and uses the same amount of data anywhere. But the fact is, any data plan has a limited number of megabytes, and if they are used up, a GPS tracker loses an access to the mobile network.

How it works - to keep SIM cards up and running continuously without physical and manual interference, we offer the convenient and practical Auto Top-Up feature. As the name implies, when properly set up, this function automatically renews the same data plan under the same conditions when the remaining amount of data has been used up to a specified limit. Thanks to it, fleet managers and business owners will not run into trouble if a SIM card plan data is nearly used up, or expiration term is around the corner but a person in charge has missed all the notifications, off duty, or simply forgot to top up the plan timely.

With the SIM card management IoT Platform, you can set up specific SIM cards to be topped up, choose notification rules (via email or SMS) when 90% or any other percentage of data is used up, or inform a person in charge that the last top-up has been depleted and there are no more of them left. As a result, there is no point to monitor the amount of data or the expiry date anymore, as automatic top-ups reduce the need for manual maintenance of the SIM cards, and fleet GPS trackers will always remain connected to the GSM network with no service interruptions.
==What you need for a solution?==

*Any [https://teltonika-gps.com/ru/products/vehicle-tracking/ '''FMx'''] device
*The [https://teltonika-gps.com/ru/product/connectivity-solution/ '''GLOBAL CONNECTIVITY SOLUTION SIM card'''] in order to get data to your server
*[https://account.truphone.com/login?redirectUrl=https://iot.truphone.com/ '''IoT Platform'''] to manage SIM cards. 

==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/FMB130_First_Start#Mounting_recommendations mounting recommendations] as well (using the FMB130 device as an example).

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 solution in this case is the automatic charging of traffic in the IoT platform. If the Truphone SIM card is not installed from the factory, then [https://wiki.teltonika-gps.com/view/FMB130_First_Start#How_to_insert_Micro-SIM_card install it yourself].

==Configuration==

==='''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].====
====1.3. Activate on the [https://account.truphone.com/login?redirectUrl=https://iot.truphone.com/ IoT Platform] using the details provided by the sales manager.====
==='''2. CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE configuration:'''===

1. Navigate to the "Rules" menu and add a new Usage rule (Please refer to Picture 1)
[[File:AutoTopUp1.jpg|thumb|none|Picture 1. '''Rules menu'''|link=Special:FilePath/AutoTopUp1.jpg]]

2. In the "Label" window enter Your preferred name. To distinguish different rules, in this example name is "Auto Top Up" (Please refer to Picture 2)
[[File:AutoTopUp2.jpg|thumb|none|Picture 2. '''Label'''|link=Special:FilePath/AutoTopUp2.jpg]]

3. In the "Rule Triggers" select the following settings (Please refer to Picture 3):

* When — Data Usage.
* Of — Each SIM Card.
* Is greater than — In this example value is 490 MB, but it can be customized according to Your needs.
* Over the — Current Rate Plan
* Country/Network — Any Country/Network
[[File:AutoTopUp3.jpg|thumb|none|Picture 3. '''Rule Triggers'''|link=Special:FilePath/AutoTopUp3.jpg]]

4. In SIM Card(s) window select "All SIM Cards" (Please refer to Picture 4)
[[File:AutoTopUp5.jpg|thumb|none|Picture 4. '''SIM Card(s)'''|link=Special:FilePath/AutoTopUp5.jpg]]

5. In the Actions window select the rate plan that will be applied to the SIM card and Uncheck "Change next billing cycle" (Please refer to Picture 5)
[[File:AutoTopUp6.jpg|thumb|none|Picture 6. '''Actions'''|link=Special:FilePath/AutoTopUp6.jpg]]

6. Select an email where the notification will be sent (Please refer to Picture 6)
[[File:AutoTopUp7.jpg|thumb|none|Picture 7. '''Notifications'''|link=Special:FilePath/AutoTopUp7.jpg]]
==Parsing information==

==='''1.Prerequisites:'''===

==== 1.1. Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====

==== 1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====

=== '''2. Parsing example:''' ===
{| class="nd-othertables_2" style="width:100%;"
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
|-
| style="vertical-align: middle; text-align: center;" | 000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443
0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E
97660000000069023B33856B000065B27B000000007D00000000BD00000000018400800000300000050100005C92

|}
{| class="nd-othertables_2" style="width:100%;"
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |AVL Data Packet 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;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| 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;" |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;" |01
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| 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;" |00
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| 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;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 44
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 28
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0D
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| 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;" |1F
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| 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;" |EF (AVL ID: 239, Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| 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;" |F0 (AVL ID: 240, Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| 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;" |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;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" | 00
|-
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |52 (AVL ID: 82, Name: Accelerator Pedal Position)
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |8'th IO ID
| style="vertical-align: middle; text-align: center;" |59 (AVL ID: 89, Name: Fuel level)
|-
| style="vertical-align: middle; text-align: center;" |8'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |9'th IO ID
| style="vertical-align: middle; text-align: center;" |98 (AVL ID: 152, Name: Geofence zone 05)
|-
| style="vertical-align: middle; text-align: center;" |9'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" | N2 of Two Byte IO
| 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;" |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;" |30 74
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| 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;" |0F 82
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| 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;" |00 00
|-
| 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;" |11'th IO ID
| 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;" |N4 of Four Byte IO
| 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;" | 00 00 60 1A
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| 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;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| 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;" |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;" |9’th IO Value
| 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;" |84 (AVL ID: 132, Name: Security State Flags)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 80 00 00 30 00 00 05
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 5C 92
|}

==Demonstration in platform==

WIALON: Open WIALON → open messages → push unit ( select your device) → choose the date from which to show the records → select message (data messages) → push execute button and you will see all information.
[[File:Wialon_CONTINUOUS_NETWORK_CONNECTIVITY_WITH_AUTO_TOP-UP_FEATURE.png|left|frameless|1155x1155px]]

[[Category: Usage scenarios]]

2022-11-04T05:59:23Z

AndrewBakalov:

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

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 ([https://wiki.teltonika-gps.com/view/FMB920 '''FMB920'''] is taken as example) a simple tracker with a basic set of functions.
{| class="mw-collapsible mw-collapsed wikitable"
| Other devices that work with this solution:
|-
| [https://wiki.teltonika-gps.com/view/FMB965 '''FMB965'''], [https://wiki.teltonika-gps.com/view/FMC920 '''FMC920'''], [https://wiki.teltonika-gps.com/view/FMB003 '''FMB003'''], [https://wiki.teltonika-gps.com/view/FMB001 '''FMB001'''], [https://wiki.teltonika-gps.com/view/FMC003 '''FMC003'''], [https://wiki.teltonika-gps.com/view/FMM920 '''FMM920'''], [https://wiki.teltonika-gps.com/view/FMM003 '''FMM003'''], [https://wiki.teltonika-gps.com/view/FMB002 '''FMB002'''], [https://wiki.teltonika-gps.com/view/FMB020 '''FMB020''']
|}

*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/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 

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

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

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].
[[File:OBDdongle.png|alt=|left|thumb|800x300px]]

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

 

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

 

*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)

[[File:SERVER settings.png|alt=|left|thumb|259x259px]]

 Server settings:

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

 

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]. 
[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]

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

 
 
 
 
Can adapter settings:
 

[[File:Obdii.png|alt=|left|455x455px|thumb]]

 
 
 
 
 
 
*807 – OBDII mode (This setting enables the BT module in ODBII mode)
 
 

*805 – This field contains the name of the device to which the tracker will connect via the BT channel

 
 
 
 
 
 
 
 

[[File:ObdIO.png|alt=|left|452x452px|thumb]]
 
 
 
*40100 – Number Of DTC, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )

*40160 – Engine RPM, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )

*40170 – Vehicle Speed, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 
 
 
 
 
 
 
'''Quickstart:''' From default configuration to BASIC TRACK & TRACE solution in one SMS:
" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;807:2;805:DONGLE;40100:1;40160:1;40170:1"
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.

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

 
 
 
 
 
*Set the Data Protocol setting to Codec 8 Extended
 
 
 
 
 
[[File:Sensor settings.png|alt=|left|452x452px|thumb]]
 
*In the Bluetooth 4.0 section, set the operating mode for one of the 4 sensors as Advanced
 
 
*Enter the MAC address of the sensor
 
 
*Select the appropriate preset and load it
 
 
[[File:Sensor IO.png|alt=|left|452x452px|thumb]]
 
 
 
 
 
 
*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.
 
 
 
 
 
==Parsing information==

==='''1.Prerequisites:'''===

==== 1.1. Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====

==== 1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====

=== '''2. Parsing example:''' ===
{| class="nd-othertables_2" style="width:100%;"
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
|-
| style="vertical-align: middle; text-align: center;" | 00000000000000328E010000017E065DE1B80000000000000000000000000000000000000003000300EF0000F0000187010000000000000000010000793F

|}
{| class="nd-othertables_2" style="width:100%;"
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |AVL Data Packet 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;" |00 00 00 00
|-
| 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;" |Codec ID
| style="vertical-align: middle; text-align: center;" |8E (Codec 8 Extended)
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 1 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| 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;" |Priority
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| 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;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| 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;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 C0
|-
| 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;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID 239, Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| 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;" |00 F0 (AVL ID 240, Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| 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;" |00 01 (AVL ID 1, Name: Digital Input 1)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |01 (Digital Input 1 state 1 - Digital Input 1 on)
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
| style="vertical-align: middle; text-align: center;" |00 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 (Digital Output 1 state 1 - Digital Output 1 on)
|-
| style="vertical-align: middle; text-align: center;" |5’th IO ID
| style="vertical-align: middle; text-align: center;" |00 1E (AVL ID 30, Name: Number of DTC)
|-
| style="vertical-align: middle; text-align: center;" |5’th IO Value
| style="vertical-align: middle; text-align: center;" |00 (Number of DTC state 0 - without DTC)
|-
| style="vertical-align: middle; text-align: center;" |6’th IO ID
| style="vertical-align: middle; text-align: center;" |00 25 (AVL ID 37, Name: Vehicle Speed)
|-
| style="vertical-align: middle; text-align: center;" |6’th IO Value
| style="vertical-align: middle; text-align: center;" |00 (Vehicle Speed 0 )
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 03
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 19 (AVL ID 25, Name: BLE Temperature #1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 7D (Temperature value 1.25 degrees Celsius)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 56 (AVL ID 86, Name: BLE Humidity #1)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |03 25 (Humidity 80.5%)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 24 (AVL ID 36, Name: Engine RPM)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |03 84 (Engine RPM state 900 RPM)
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| 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;" |00 03
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 19 (AVL ID 25, Name: BLE Temperature #1)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 7D (Temperature value 1.25 degrees Celsius)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 56 (AVL ID 86, Name: BLE Humidity #1)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |03 25 (Humidity 80.5%)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 24 (AVL ID 36, Name: Engine RPM)
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |03 84 (Engine RPM state 900 RPM)
|-
| style="vertical-align: middle; text-align: center;" |NX of X Byte IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 79 3F
|}

 
[[Category: Usage scenarios]]

BASIC TRACK & TRACE

2022-11-04T05:21:05Z

AndrewBakalov:

2022-10-28T11:54:05Z

AndrewBakalov:

==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 ([https://wiki.teltonika-gps.com/view/FMB920 '''FMB920'''] is taken as example) a simple tracker with a basic set of functions.
{| class="mw-collapsible mw-collapsed wikitable"
| Other devices that work with this solution:
|-
| [https://wiki.teltonika-gps.com/view/FMB965 '''FMB965'''], [https://wiki.teltonika-gps.com/view/FMC920 '''FMC920'''], [https://wiki.teltonika-gps.com/view/FMB003 '''FMB003'''], [https://wiki.teltonika-gps.com/view/FMB001 '''FMB001'''], [https://wiki.teltonika-gps.com/view/FMC003 '''FMC003'''], [https://wiki.teltonika-gps.com/view/FMM920 '''FMM920'''], [https://wiki.teltonika-gps.com/view/FMM003 '''FMM003'''], [https://wiki.teltonika-gps.com/view/FMB002 '''FMB002'''], [https://wiki.teltonika-gps.com/view/FMB020 '''FMB020''']
|}

*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/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 

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

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. 

==Configuration==

==='''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:

 

*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)

[[File:SERVER settings.png|alt=|left|thumb|259x259px]]

 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 [[FMB130 Parameter list|SMS parameters]]. 
[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]

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 [[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]]
 
 
 
 
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)

[[File:Can_adapter_door_status_settings.PNG|alt=|left|455x455px|thumb]]
 

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

[[File:Can_adapter_fuel_level_settings.PNG|alt=|left|453x453px|thumb]]
 

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

[[File:Can_adapter_settings_total_milage_counted.PNG|alt=|left|452x452px|thumb]]
 

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

[[File:Sec_state_flag_P2.PNG|alt=|left|453x453px|thumb]]

*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 [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====

==== 1.2. Read Java parser [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====

=== '''2. Parsing example:''' ===
{| class="nd-othertables_2" style="width:100%;"
! rowspan="1" style="width:100%; vertical-align: middle; text-align: center;" |Unparsed received data in hexadecimal stream
|-
| style="vertical-align: middle; text-align: center;" | 000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443
0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E
97660000000069023B33856B000065B27B000000007D00000000BD00000000018400800000300000050100005C92

|}
{| class="nd-othertables_2" style="width:100%;"
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |AVL Data Packet 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;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| 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;" |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;" |01
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| 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;" |00
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| 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;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 44
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 28
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0D
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| 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;" |1F
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| 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;" |EF (AVL ID: 239, Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| 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;" |F0 (AVL ID: 240, Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| 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;" |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;" |6'th IO Value
| style="vertical-align: middle; text-align: center;" | 00
|-
| style="vertical-align: middle; text-align: center;" |7'th IO ID
| style="vertical-align: middle; text-align: center;" |52 (AVL ID: 82, Name: Accelerator Pedal Position)
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |8'th IO ID
| style="vertical-align: middle; text-align: center;" |59 (AVL ID: 89, Name: Fuel level)
|-
| style="vertical-align: middle; text-align: center;" |8'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |9'th IO ID
| style="vertical-align: middle; text-align: center;" |98 (AVL ID: 152, Name: Geofence zone 05)
|-
| style="vertical-align: middle; text-align: center;" |9'th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" | N2 of Two Byte IO
| 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;" |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;" |30 74
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| 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;" |0F 82
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| 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;" |00 00
|-
| 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;" |11'th IO ID
| 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;" |N4 of Four Byte IO
| 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;" | 00 00 60 1A
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| 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;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| 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;" |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;" |9’th IO Value
| 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;" |84 (AVL ID: 132, Name: Security State Flags)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |00 80 00 00 30 00 00 05
|-
| style="vertical-align: middle; text-align: center;" |Number of Data 2 (Number of Total Records)
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |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"

[[Category: Usage scenarios]]