Difference between revisions of "CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE"

From Wiki Knowledge Base | Teltonika GPS
 
(13 intermediate revisions by 2 users not shown)
Line 9: Line 9:
  
 
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.
 
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.
 
Consider this situation – a day-long queue of vehicles is formed near a customs gate. By the time a lorry crosses the border, the data volume may be already depleted or the SIM card plan may have expired, and a fleet administration has not received automated notifications of such events and remains unaware of the situation. Consequently, the lorry driver may not download the digital tachograph data on time which could result in hefty fines for the fleet owner.
 
 
Going further, logistics, utilities, and delivery services are often on duty at the weekends, when administration personnel or managers in charge may have a day off. This could mean that nobody reads (or has access to) the relevant system notifications. If all the SIM card data is used up by, let’s say, Saturday evening, there possibly will be no one to top up them manually. Once again, vehicle GPS trackers will not be connected to a network and will not be able to transmit either tachograph data or transport of interest location and journey whereabouts to servers of the E-TOLL payment management system. The office administration may not realise the gravity of the situation until the upcoming Monday, and, in many cases, it will already be too late to avoid penalties.
 
  
 
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.
 
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.
+
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 [https://teltonika-gps.com/products/solutions/teltonika-connectivity-solution 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.
+
For example, the Teltonika Global Plan currently allows you to prevent roaming costs in 134 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.
 
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.
 
Please note, the mobile top-ups themselves need to be purchased in advance, so that they can automatically top up SIM cards of GPS trackers mounted on vehicles. To get ready to use the Auto Top-Up feature, please contact your Teltonika Sales Manager at your convenience. Handily, any number of top-ups can be purchased in advance, so fleets of any size will not be short of connectivity options.
 
  
 
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.
 
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.
 
Going back to our challenge examples above, if the data volume is exhausted when parcels are being delivered on a Sunday afternoon, or a lorry driver finally arrives at the destination after a day of queuing outside office working hours, all Teltonika vehicle GPS trackers will remain connected to the mobile network and fully operational. No data loss, no fines, no hassle. Read more about Digital Tachograph Monitoring and e-TOLL Certified Vehicle GPS Trackers in our published use case articles.
 
 
To sum up, the Auto Top-Up feature provides an effective way to automate the top-up procedure, stay continuously connected online, avoid data flow interruptions and/or unwanted penalties when a SIM card is used up or expires. Get as many mobile top-ups as your business needs, set the rules with an IoT Platform, never be disconnected again and keep your reputation intact!
 
 
 
==What you need for a solution?==
 
==What you need for a solution?==
  
*'''FMx1YX''' device ([https://wiki.teltonika-gps.com/view/FMB130 '''FMB130''']is taken as example) which is used to connect to a CAN-CONTROL adapter.
+
*Any [https://teltonika-gps.com/ru/products/vehicle-tracking/ '''FMx'''] device
{| class="mw-collapsible mw-collapsed wikitable"
+
*The [https://teltonika-gps.com/ru/product/connectivity-solution/ '''GLOBAL CONNECTIVITY SOLUTION SIM card'''] in order to get data to your server
| Other devices that work with this solution:
+
*[https://account.truphone.com/login?redirectUrl=https://iot.truphone.com/ '''IoT Platform'''] to manage SIM cards.<br />
|-
 
| [https://wiki.teltonika-gps.com/view/FMB110 '''FMB110'''], [https://wiki.teltonika-gps.com/view/FMB120 '''FMB120'''], [https://wiki.teltonika-gps.com/view/FMB122 '''FMB122'''], [https://wiki.teltonika-gps.com/view/FMB125 '''FMB125'''], [https://wiki.teltonika-gps.com/view/FMU125 '''FMU125'''], [https://wiki.teltonika-gps.com/view/FMC125 '''FMC125'''], [https://wiki.teltonika-gps.com/view/FMM125 '''FMM125'''], [https://wiki.teltonika-gps.com/view/FMU130 '''FMU130'''], [https://wiki.teltonika-gps.com/view/FMC130 '''FMC130'''], [https://wiki.teltonika-gps.com/view/FMM130 '''FMM130'''], [https://wiki.teltonika-gps.com/view/FMU126 '''FMU126''']
 
|}
 
 
 
*The [https://wiki.teltonika-gps.com/view/FMB130_First_Start#How_to_insert_Micro-SIM_card '''SIM card'''] in order to get data to your server
 
*[https://wiki.teltonika-gps.com/view/CAN-CONTROL '''CAN-CONTROL adapter''']. The adapter allows you to control car doors and it works with many of our products
 
*[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/FMB130_First_Start#Mounting_recommendations mounting recommendations] as well.
+
Install the tracker according to [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.
 
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].
+
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].
  
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>
 
  
 
==Configuration==
 
==Configuration==
  
==='''1. Prerequisites:'''===
+
==='''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 />
 
 
 
 
 
  
 +
====Read through [https://wiki.teltonika-gps.com/view/FMB130_First_Start First start guide]====
 +
====Understanding of possible [https://wiki.teltonika-gps.com/view/FMB130_Sleep_modes Sleep modes].====
 +
====Activate on the [https://account.truphone.com/login?redirectUrl=https://iot.truphone.com/ IoT Platform] using the details provided by the sales manager.====
 +
==='''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|frameless|1155x1155px|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|frameless|1155x1155px|Picture 2. '''Label'''|link=Special:FilePath/AutoTopUp2.jpg]]
  
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 />
+
3.    In the "Rule Triggers" select the following settings (Please refer to Picture 3):
[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]
 
  
 +
* 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|frameless|1155x1155px|Picture 3. '''Rule Triggers'''|link=Special:FilePath/AutoTopUp3.jpg]]
  
Sleep settings:
+
4.    In SIM Card(s) window select "All SIM Cards" (Please refer to Picture 4)
<br />
+
[[File:AutoTopUp5.jpg|thumb|none|frameless|1155x1155px|Picture 4. '''SIM Card(s)'''|link=Special:FilePath/AutoTopUp5.jpg]]
*<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.
 
  
 +
5.    In the Actions window select the rate plan that will be applied to the SIM card and <b>Uncheck</b> "Change next billing cycle" (Please refer to Picture 5)
 +
[[File:AutoTopUp6.jpg|thumb|none|frameless|1155x1155px|Picture 6. '''Actions'''|link=Special:FilePath/AutoTopUp6.jpg]]
  
 
+
6.    Select an email where the notification will be sent (Please refer to Picture 6)
[[File:Can adapter settings carsharing solution.JPG|alt=|left|frame]]
+
[[File:AutoTopUp7.jpg|thumb|none|frameless|1155x1155px|Picture 7. '''Notifications'''|link=Special:FilePath/AutoTopUp7.jpg]]
<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 />
 
 
 
 
 
 
 
 
 
 
 
 
 
*<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 />
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
*<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 />
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
*<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]]
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
*<span style="background-color:#bce5d7;">45430</span> – Security State Flags, Priority "Low" (0 – Disabled 1 – Low 2 – High 3 – Panic )
 
<br />
 
<br />
 
<br />
 
 
 
<br />
 
'''Quickstart:''' From default configuration to Car sharing 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"
 
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==
 
==Parsing information==
  
==='''1.Prerequisites:'''===
+
==='''Prerequisites:'''===
  
==== 1.1.  Open [https://wiki.teltonika-gps.com/view/Opening_TCP/UDP_port TCP/UDP port]====
+
====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]====
+
====Read Java parser  [https://wiki.teltonika-gps.com/view/Java_Parser_First_Start_Guide first start guide]====
  
=== '''2. Parsing example:''' ===
+
=== '''Parsing example:''' ===
 
{| class="nd-othertables_2" style="width:100%;"
 
{| class="nd-othertables_2" style="width:100%;"
 +
|+
 
! 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;" | 000000000000008F080100000177B0A5F838000000000000000000004400280D0000001F09EF00F0001504B301B40051005200590098000B42307443
+
| style="vertical-align: middle; text-align: center;" |000000000000004608010000017501DAF828010F0E4792209AC4FB00C200D70C0000F90D06EF01F00
0F8244000011001812002D13FFE85400BE5500005A0000970000A800000AF10000601A53000000005703CB6B986400002E
+
01503C8004501F900B50005B6000342334D43000044000002F10000601A100000000000010000732E
97660000000069023B33856B000065B27B000000007D00000000BD000000000184<span style="background:#0b9768">0080000030000005</span>0100005C92
+
|-
 +
|}
 +
 
  
|}
 
 
{| class="nd-othertables_2" style="width:100%;"
 
{| class="nd-othertables_2" style="width:100%;"
 +
|+
 +
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
 
|-
 
|-
 
! 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;" |AVL Data Packet Part
 
! 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 8F
+
| style="vertical-align: middle; text-align: center;" |00 00 00 D6
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Codec ID
 
| style="vertical-align: middle; text-align: center;" |Codec ID
Line 213: Line 105:
 
|-
 
|-
 
| 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 77 B0 A5 F8 38 (Thursday, February 18, 2021 3:43:00 PM GMT+02:00)
+
| style="vertical-align: middle; text-align: center;" |00 00 01 75 01 DA F8 28 (Wed Oct 07 06:58:49 UTC 2020)
 
|-
 
|-
| 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;" |01
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Longitude
 
| 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;" |0F 0E 47 92
 
|-
 
|-
 
| 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;" |20 9A C4 FB
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 44
+
| style="vertical-align: middle; text-align: center;" |00 C2
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 28
+
| style="vertical-align: middle; text-align: center;" |00 D7
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Satellites
 
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0D
+
| style="vertical-align: middle; text-align: center;" |0C
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |Speed
 
| style="vertical-align: middle; text-align: center;" |Speed
Line 237: Line 129:
 
|-
 
|-
 
| 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
+
| style="vertical-align: middle; text-align: center;" |F9 (AVL ID: 249, Name: Jamming)
 
|-
 
|-
 
| 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;" |1F
+
| style="vertical-align: middle; text-align: center;" |0D
 
|-
 
|-
 
| 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;" |09
+
| style="vertical-align: middle; text-align: center;" |06
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
Line 249: Line 141:
 
|-
 
|-
 
| 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;" |00
+
| style="vertical-align: middle; text-align: center;" |01
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
Line 257: Line 149:
 
| style="vertical-align: middle; text-align: center;" |00
 
| 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;" |15 (AVL ID: 21, Name: GSM Signal)
 
| 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;" |3’rd IO Value
| style="vertical-align: middle; text-align: center;" |04
+
| style="vertical-align: middle; text-align: center;" |03
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| 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;" |C8 (AVL ID: 200, Name: Sleep Mode)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 
| 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;" |00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 
| 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;" |45 (AVL ID: 69, Name: GNSS Status)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 
| 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;" |01
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO ID
 
| 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;" |F9 (AVL ID: 249, Name: Jamming)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO Value
 
| 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;" |00 (0 – jamming stop, 1 – jamming start)
|-
 
| 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;" |N1 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |00
+
| style="vertical-align: middle; text-align: center;" |05
|-
 
| 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;" |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;" |B5 (AVL ID: 181, Name: GNSS PDOP)
 
|-
 
|-
 
| 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;" |30 74
+
| style="vertical-align: middle; text-align: center;" |00 05
 
|-
 
|-
 
| 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;" |43 (AVL ID: 67, Name: Battery Voltage)
+
| style="vertical-align: middle; text-align: center;" |B6 (AVL ID: 182, Name: GNSS HDOP)
 
|-
 
|-
 
| 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;" |0F 82
+
| style="vertical-align: middle; text-align: center;" |00 03
 
|-
 
|-
 
| 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;" |44 (AVL ID: 68, Name: Battery Current)
+
| style="vertical-align: middle; text-align: center;" |42 (AVL ID: 66, Name: External Voltage)
 
|-
 
|-
 
| 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;" |00 00
+
| style="vertical-align: middle; text-align: center;" |33 4D
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| 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;" |43 (AVL ID: 67, Name: Battery Voltage)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 
| 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;" |00 00
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 
| 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;" |44 (AVL ID: 68, Name: Battery Current)
 
|-
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 
| 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;" |00 00
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |9'th IO ID
+
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
| style="vertical-align: middle; text-align: center;" |5A (AVL ID:90, Name: Door Status)
+
| style="vertical-align: middle; text-align: center;" |02
 
|-
 
|-
| style="vertical-align: middle; text-align: center;" |9’th IO Value
+
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| 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;" |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;" | 00 00 60 1A
+
| 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;" |53 (AVL ID: 83, Name: Fuel Consumed)
+
| style="vertical-align: middle; text-align: center;" |10 (AVL ID: 16, Name: Total Odometer)
 
|-
 
|-
 
| 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;" |00 00 00 00
 
| 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;" |N8 of Eight Bytes IO
| style="vertical-align: middle; text-align: center;" |57 (AVL ID: 87, Name: Total Mileage)
+
| style="vertical-align: middle; text-align: center;" |00
|-
 
| 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;" |<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 444: Line 228:
 
|-
 
|-
 
| 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 5C 92
+
| style="vertical-align: middle; text-align: center;" |00 00 73 2E
 +
|-
 
|}
 
|}
  
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:
+
==Demonstration in platform==
  
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
+
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.
*1) To unlock all doors use this command: "lvcanopenalldoors"
+
[[File:Wialon_CONTINUOUS_NETWORK_CONNECTIVITY_WITH_AUTO_TOP-UP_FEATURE.png|left|frameless|1155x1155px]]
*2) To lock all doors use this command: "lvcanclosealldoors"
 
  
 
[[Category: Usage scenarios]]
 
[[Category: Usage scenarios]]

Latest revision as of 08:51, 23 February 2023

Main Page > General Information > Usage scenarios > CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE

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.

Truphone solution.png

For example, the Teltonika Global Plan currently allows you to prevent roaming costs in 134 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?

Installation

Install the tracker according to 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 install it yourself.


Configuration

Prerequisites:

Read through First start guide

Understanding of possible Sleep modes.

Activate on the IoT Platform using the details provided by the sales manager.

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)

Picture 1. Rules menu

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)

Picture 2. Label

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
Picture 3. Rule Triggers

4.    In SIM Card(s) window select "All SIM Cards" (Please refer to Picture 4)

Picture 4. SIM Card(s)

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)

Picture 6. Actions

6.    Select an email where the notification will be sent (Please refer to Picture 6)

Picture 7. Notifications

Parsing information

Prerequisites:

Open TCP/UDP port

Read Java parser first start guide

Parsing example:

Unparsed received data in hexadecimal stream
000000000000004608010000017501DAF828010F0E4792209AC4FB00C200D70C0000F90D06EF01F00

01503C8004501F900B50005B6000342334D43000044000002F10000601A100000000000010000732E


AVL Data Packet
AVL Data Packet Part HEX Code Part
Zero Bytes 00 00 00 00
Data Field Length 00 00 00 D6
Codec ID 08 (Codec 8)
Number of Data 1 (Number of Total Records) 01
Timestamp 00 00 01 75 01 DA F8 28 (Wed Oct 07 06:58:49 UTC 2020)
Priority 01
Longitude 0F 0E 47 92
Latitude 20 9A C4 FB
Altitude 00 C2
Angle 00 D7
Satellites 0C
Speed 00 00
Event IO ID F9 (AVL ID: 249, Name: Jamming)
N of Total ID 0D
N1 of One Byte IO 06
1’st IO ID EF (AVL ID: 239, Name: Ignition)
1’st IO Value 01
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 03
4'th IO ID C8 (AVL ID: 200, Name: Sleep Mode)
4'th IO Value 00
5'th IO ID 45 (AVL ID: 69, Name: GNSS Status)
5'th IO Value 01
6'th IO ID F9 (AVL ID: 249, Name: Jamming)
6'th IO Value 00 (0 – jamming stop, 1 – jamming start)
N1 of Two Byte IO 05
1’st IO ID B5 (AVL ID: 181, Name: GNSS PDOP)
1’st IO Value 00 05
2’nd IO ID B6 (AVL ID: 182, Name: GNSS HDOP)
2’nd IO Value 00 03
3’rd IO ID 42 (AVL ID: 66, Name: External Voltage)
3’rd IO Value 33 4D
4'th IO ID 43 (AVL ID: 67, Name: Battery Voltage)
4'th IO Value 00 00
5'th IO ID 44 (AVL ID: 68, Name: Battery Current)
5'th IO Value 00 00
N4 of Four Bytes IO 02
1’st IO ID F1 (AVL ID: 241, Name: Active GSM Operator)
1’st IO Value 00 00 60 1A
2’nd IO ID 10 (AVL ID: 16, Name: Total Odometer)
2’nd IO Value 00 00 00 00
N8 of Eight Bytes IO 00
Number of Data 2 (Number of Total Records) 01
CRC-16 00 00 73 2E


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.

Wialon CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE.png