Difference between revisions of "Geofence Solution in the Event of Pandemic"

From Wiki Knowledge Base | Teltonika GPS
(92 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Solution description==
+
==Project description==
  
 
One of the more advanced features of GPS trackers is the ability to create Geofence scenarios in a real-time with triggered alerts. Geofences are designated areas or zones that can be defined on a map or as a distance from the specific location. The feature may help to comply with some pandemic lockdown measures and greatly benefit private car owners, families, corporate fleet managers and business owners. All Teltonika GPS tracker models have Geofence as a standard feature.
 
One of the more advanced features of GPS trackers is the ability to create Geofence scenarios in a real-time with triggered alerts. Geofences are designated areas or zones that can be defined on a map or as a distance from the specific location. The feature may help to comply with some pandemic lockdown measures and greatly benefit private car owners, families, corporate fleet managers and business owners. All Teltonika GPS tracker models have Geofence as a standard feature.
Line 13: Line 13:
  
 
Since Geofence can be used in all of Teltonika devices, it is important to follow your specific device [https://wiki.teltonika-gps.com/view/FMM130_First_Start#Mounting_recommendations mounting recommendations]. This is because if you were to install the tracker following the instructions of a different one, your device may not work properly in the end. Also, we offer a wide range of trackers that have different connectors, some of the devices we offer are "Plug and Track" (devices that have OBD-II connectors), other may demand more wiring work to be done. The list of all Teltonika Fleet Management devices can be found [[Fleet management | here]].
 
Since Geofence can be used in all of Teltonika devices, it is important to follow your specific device [https://wiki.teltonika-gps.com/view/FMM130_First_Start#Mounting_recommendations mounting recommendations]. This is because if you were to install the tracker following the instructions of a different one, your device may not work properly in the end. Also, we offer a wide range of trackers that have different connectors, some of the devices we offer are "Plug and Track" (devices that have OBD-II connectors), other may demand more wiring work to be done. The list of all Teltonika Fleet Management devices can be found [[Fleet management | here]].
<!--
 
==== Connection scheme ====
 
[[File:Fmx130 installation.png|frameless|690x690px]]
 
 
{| class="wikitable"
 
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NUMBER
 
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| PIN NAME
 
! style="width:25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DESCRIPTION
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 1
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|<span style="color:#FF0000">'''VCC (+10-30 V DC).'''</span>
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Power supply (+10-30 V DC).
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 7
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|'''GND''' (-)
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Ground
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 8
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"|<span style="color:#FF6600">'''DOUT 1'''
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Digital output, channel 1. Open collector output. Max. 0,5 A DC.
 
|-
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| 9
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| <span style="color:#842BD7">'''DOUT 2'''
 
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;"| Digital output, channel 2. Open collector output. Max. 0,5 A DC.
 
|-
 
|}
 
-->
 
==Configuration==
 
 
==='''1. Prerequisites:'''===
 
 
====1.1. Read through [https://wiki.teltonika-gps.com/view/FMM130_First_Start First start guide]====
 
 
====1.2. Understanding what [https://wiki.teltonika-gps.com/view/FMM130_Manual_Geofence_settings manual Geofence] has to offer.====
 
 
 
'''2. Configuration of Manual Geofence feature'''[[File:GPRS settings.png|alt=|left|frame]]
 
 
[[FMM001 Parameter list|Parameter ID]] – Parameter name GPRS settings:<br />
 
<br />
 
<br />
 
*<span style="background-color:#91b9d4;">2001</span> – APN
 
*<span style="background-color:#91d4b9;">2002</span> – APN username (if there are no APN username, empty field should be left)
 
*<span style="background-color:#b991d4;">2003</span> – APN password (if there are no APN password, empty field should be left)
 
 
[[File:SERVER settings.png|alt=|left|frame]]
 
<br />
 
<br />
 
<br />
 
<br />
 
 
<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 />
 
<br />
 
<br />
 
 
After successful GPRS/SERVER settings configuration, FMM130 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 [[FMM130 Parameter list|SMS parameters]].<br />
 
 
[[File:manual_geofence_selection.jpg|alt=|left|665x665px|thumb]]
 
 
 
 
 
 
 
 
 
 
 
Manual Geofence settings:
 
 
*<span style="background-color:#73e2f2;">20100</span> - Feature priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic)
 
 
*<span style="background-color:#fafa37;">20101</span> - Generate Event (0 - No Event, 1 - On Exit, 2 - On Entrance, 3 - On Both)
 
* 20102 - Eventual Records (0 - Disable, 1 - Enable)
 
<br />
 
 
* 20103 - Frame Border (m)
 
*<span style="background-color:#82e3d4;">20104</span> - Shape Type (0 - Circle, 1 - Rectangle)
 
* 20105 - Radius (m)
 
*<span style="background-color:#3a90ff;">20106</span> - Coordinate Y1
 
*<span style="background-color:#ff7e66;">20107</span> - Coordinate X1
 
*<span style="background-color:#d6f6fb;">20108</span> - Coordinate Y2
 
*<span style="background-color:#5c7b90;">20109</span> - Coordinate X2
 
<br />
 
 
* 20110 - Overspeeding (0 - Disable, 1 - Enable)
 
 
* 20111 - Max allowed speed (km/h)
 
 
 
 
* 7025 - Phone Number
 
* 8025 - SMS Text
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
<br />
 
'''Note''': Radius is only calculated if the chosen Shape Type is a Circle. In this example, Radius cannot be seen since the shape chosen is the Rectangle. Also, Latitude Y2 and Longitude X2 are only used when Rectangle is the chosen shape.
 
 
<br />
 
 
[[File:Screenshot 4.jpg|left|frameless|200x150px]]
 
It is also important to mention that the map in the [https://wiki.teltonika-gps.com/view/FMM130_Manual_Geofence_settings Manual Geofence] function section has a few features as well if you wish to make some adjustments using the interface:
 
 
Manual Geofence also has a nifty feature that allows the user to draw their wanted Geofence using only the mouse. There are 4 buttons that make this feature into reality.
 
 
First two are for drawing a circle or a rectangle. Simply press on the button, drag your mouse for the area you want the Geofence to be located and release. The Configurator will automatically calculate the size.
 
 
The 3rd button is for deleting the Geofence which is currently chosen.
 
 
The last button on the interface is used to zoom in on all of the available geozones.
 
 
<br />
 
<br />
 
<br />
 
 
'''Quickstart:''' From default configuration to Geofence crossing detection in two SMS:
 
"  setparam <span style="background-color:#91b9d4;">2001</span>:APN;<span style="background-color:#91d4b9;">2002</span>:APN_username;<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"
 
 
"  setparam <span style="background-color:#73e2f2;">20100</span>:2;<span style="background-color:#fafa37;">20101</span>:2;<span style="background-color:#82e3d4;">20104</span>:1;<span style="background-color:#3a90ff;">20106</span>:latitudeY1;<span style="background-color:#ff7e66;">20107</span>:longitudeX1;<span style="background-color:#d6f6fb;">20108</span>:latitudeY2;<span style="background-color:#5c7b90;">20109</span>:longitudeX2"
 
 
This SMS will set up your device to report Geofence Crossing Detection scenario to the server.
 
 
'''Note''': We're sending two instead of one configuration messages since one SMS can contain up to 160 characters. For this scenario, we exceed the maximum allowed character amount. Therefore, we split the message into two.
 
 
==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;" | 00000000000000460801000001776D581890010F07C39A
 
209CE0C2009C009D05000F<span style="background:#0b9768">9B</span>0D06EF01F0001505C8004501<span style="background:#0b9768">9B01</span>05B5000BB6000
 
A424257430F8044000002F1000060191000000BE1000100005139
 
|-
 
|}
 
 
 
{| 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;" |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 46
 
|-
 
| 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 49 BC 8E 70 (Thursday, February 4, 2021 2:00:26 PM)
 
|-
 
| style="vertical-align: middle; text-align: center;" |Priority
 
| style="vertical-align: middle; text-align: center;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" |Longitude
 
| style="vertical-align: middle; text-align: center;" |0F 07 C3 9A
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |20 9C E0 C2
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |00 9C
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |00 9D
 
|-
 
| style="vertical-align: middle; text-align: center;" |Satellites
 
| style="vertical-align: middle; text-align: center;" |05
 
|-
 
| style="vertical-align: middle; text-align: center;" |Speed
 
| style="vertical-align: middle; text-align: center;" |00 0F
 
|-
 
| style="vertical-align: middle; text-align: center;" |Event IO ID
 
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">9B (AVL ID: 155, Name: Geofence zone 01)</span>
 
|-
 
| style="vertical-align: middle; text-align: center;" |N of Total ID
 
| 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;" |06
 
|-
 
| 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;" |01
 
|-
 
| 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;" |05
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| 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;" |00
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 
| 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;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO ID
 
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">9B (AVL ID: 155, Name: Geofence zone 01)</span>
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO Value
 
| style="vertical-align: middle; text-align: center;" |<span style="background:#0b9768">01 (00 – target left zone, 01 – target entered zone, 02 – over speeding end, 03 – over speeding start)
 
</span>
 
|-
 
| style="vertical-align: middle; text-align: center;" |N1 of Two Byte IO
 
| style="vertical-align: middle; text-align: center;" |05
 
|-
 
| style="vertical-align: middle; text-align: center;" |1’st IO ID
 
| 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;" |00 0B
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| 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;" |00 0A
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
 
| 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;" |42 57
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| 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;" |0F 80
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 
| 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;" |00 00
 
|-
 
| style="vertical-align: middle; text-align: center;" |N4 of Four Bytes IO
 
| style="vertical-align: middle; text-align: center;" |02
 
|-
 
| 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 19
 
|-
 
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
 
| 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;" |00 00 0B E1
 
|-
 
| style="vertical-align: middle; text-align: center;" |N8 of Eight Bytes IO
 
| style="vertical-align: middle; text-align: center;" |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 51 39
 
|-
 
|}
 
 
==Demonstration in platform==
 
[[Category:Usage scenarios]]
 
 
TAVL: Open TAVL → select client → Track. By choosing a certain date frame for the device that you're watching, you can see the events that are generated when the Geofence is crossed (depending on what was chosen on the Configurator: On entry, on exit, on both).
 
 
[[File:Screenshot 5.jpg|alt=|frameless|1153x1153px]]
 
 
Wialon: Open WIALON → open messages → push unit ( select your device) → choose the date from which to which to show the records → select message  (data messages) → push execute button and you will see all information.
 
 
[[File:Screenshot 3.jpg|alt=|frameless|1153x1153px]]
 

Revision as of 19:42, 22 January 2021

Main Page > General Information > Usage scenarios > Geofence Solution in the Event of Pandemic

Project description

One of the more advanced features of GPS trackers is the ability to create Geofence scenarios in a real-time with triggered alerts. Geofences are designated areas or zones that can be defined on a map or as a distance from the specific location. The feature may help to comply with some pandemic lockdown measures and greatly benefit private car owners, families, corporate fleet managers and business owners. All Teltonika GPS tracker models have Geofence as a standard feature.

What you need for a solution?

  • Geofence solution is supported by all Teltonika devices. To show this scenario, we will be using the FMM130 model.
  • The SIM card in order to receive data to your server.
  • Teltonika Configurator to make the configurations for your Teltonika device.
  • FOTA WEB to send the configurations to your device remotely.

Installation

Since Geofence can be used in all of Teltonika devices, it is important to follow your specific device mounting recommendations. This is because if you were to install the tracker following the instructions of a different one, your device may not work properly in the end. Also, we offer a wide range of trackers that have different connectors, some of the devices we offer are "Plug and Track" (devices that have OBD-II connectors), other may demand more wiring work to be done. The list of all Teltonika Fleet Management devices can be found here.