Difference between revisions of "Speed Limiting Solution"

From Wiki Knowledge Base | Teltonika GPS
 
(6 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
Due to the accidents caused by over speeding, corporate fleet businesses and insurance companies suffer from huge losses in most of the countries globally. This can often lead to a loss in productivity, reduction in revenue, paying insurance costs (if it’s the driver’s fault), as well as medical and collateral damage costs. To help resolve this major concern, here at Teltonika Telematics we have developed and manufactured a unique GPS tracker with the speed limiter feature.
 
Due to the accidents caused by over speeding, corporate fleet businesses and insurance companies suffer from huge losses in most of the countries globally. This can often lead to a loss in productivity, reduction in revenue, paying insurance costs (if it’s the driver’s fault), as well as medical and collateral damage costs. To help resolve this major concern, here at Teltonika Telematics we have developed and manufactured a unique GPS tracker with the speed limiter feature.
  
==Solution description==
+
==Challenge==
Utilizing a modern and comprehensive GPS tracking method allows you to monitor driver (including novice) behaviour, improve safety, and reduce the fleet running costs and legal liability. And that is where Teltonika '''MSP500''' comes into the play.
 
  
Teltonika '''MSP500''' is a special tracking terminal with GNSS/GSM/Bluetooth 4.0 connectivity, internal GNSS/GSM antennas, RS232 interface, internal Ni-Mh battery, and waterproof IP65 casing. The device has been specifically designed with the key feature – speed limiting control.
+
Utilizing a modern and comprehensive GPS tracking method allows you to monitor driver (including novice) behavior, improve safety, and reduce the fleet running costs and legal liability. And that is where Teltonika '''FMx series''' and '''MSP500 tracker-speed limiter''' come into the play.
  
==What you need for a solution?==
+
==Scenarios==
  
*'''[https://wiki.teltonika-gps.com/view/MSP500 MSP500]''' device
+
* [[Speed Limiting Solution MSP500+ETC]]
 +
* [[Speed Limiting Solution FMC130+ETC]]
  
*The '''[https://wiki.teltonika-gps.com/view/MSP500_First_Start#How_to_insert_Micro-SIM_card_and_connect_the_battery SIM card]''' in order to get data to your server
+
==Benefits==
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.<br />
 
  
==Installation==
+
*'''Over speeding quick fix for good''' – the most common and widely spread speeding problem is resolved at once and for all with a minimum effort and maximum results.
 +
*'''Extensive functionality to serve your needs''' – highly advanced, configurable and efficient speed limiting solution. The rich set of features can be utilised in a combination with speed limiter functionality making it a truly comprehensive all-in-one solution for any fleet.
 +
*'''Improves drivers’ discipline and time efficiency''' – great assistance for novice drivers and seasoned professionals helping to stay safe and perform daily tasks with the least waste of time.
 +
*'''Lower expenses, higher profits''' – by preventing traffic accidents, speed tickets, delays, casualties, and insurance cost rise, this tracker very likely will improve fleet operational cost, company cash flow, and ROI.
 +
*'''Various fleets, one solution''' – suitable for all sorts of fleets and logistic businesses including freight forwarders, carriers, international and domestic couriers, 3rd party logistic service providers, livestock transportation, luxury and executive class fleets, etc.
  
MSP500 tracker can be connected in 3 different ways based on the speed limiting scenario that will be implemented. It’s important to hide the tracker, so it would not be a simple task for the thieves to find and unplug it.
+
[[Category:Usage scenarios]]
 
 
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.
 
 
 
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 device when implementing electronic throttle controller solution.
 
 
 
[[File:MSP500 schema 1.7.png|783x783px]]
 
 
 
There are 2 other ways of connecting the MSP500 device which are displayed below:
 
 
 
[[File:Fuel Pump Installation.png|none|thumb|832x832px]]
 
[[File:Solenoid Installation.png|none|thumb|892x892px]]
 
 
 
 
 
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==
 
 
 
==='''1. Prerequisites:'''===
 
 
 
====1.1. Read through [https://wiki.teltonika-gps.com/view/MSP500_First_Start First start guide]====
 
====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/MSP500_Sleep_modes Sleep modes].====
 
==='''2. Speed limiting 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 />
 
 
 
 
 
After successful GPRS/SERVER settings configuration, MSP500 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 [[MSP500 Parameter list|SMS parameters]].<br />[[File:Online_deep_sleep_carsharing.PNG|alt=|left|thumb]]
 
 
 
 
 
Sleep settings:
 
<br />
 
*<span style="background:#05CC6F">102</span> – Sleep settings(0 – Disable, 1 – Gps sleep, 2 – Deep sleep, 3 – Online Deep sleep, 4 – Ultra sleep)
 
'''Note''': This scenario will not work with [[MSP500 Sleep modes|Deep Sleep]] and [[MSP500 Sleep modes|Ultra Sleep]] modes, since they disable the device's GSM module to save power.
 
 
 
 
 
 
 
To setup the speed limiting feature in the configurator we should navigate to '''Features → Over Speeding''' where we would set a priority for the event, speed source and DOUT 1 for the relay to work properly.
 
 
 
[[File:Overspeeding feature.png|left|thumb]]
 
 
 
<br />
 
Over speeding settings
 
 
 
*<span style="background:#1cbef4">11100</span> – Scenario settings(0 – Disable, 1 – Low Priority, 2 – High Priority, 3 – Panic Priority)
 
*<span style="background:#f47a8a">11104</span> - Max Speed (Default value - 90 km/h)
 
*<span style="background:#c16c2d">13217</span> - Speed Source (0 - GNSS (Default), 1 - OBD, 2 - AIN1)
 
*<span style="background:#f63a0e">13223</span> - Over speeding Hysteresis (Default value - 8%), value that determines what would be the threshold speed level that would activate the speed limiting feature
 
*<span style="background:#33be9e">11103</span> - Output Control (0 - None (Default), 1 - DOUT1), DOUT1 needs to be enabled to use the speed limiting feature
 
 
 
 
 
<br />
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
'''Quickstart:''' From default configuration to Speed Limiting 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:#1cbef4">11100</span>:2;<span style="background:#f47a8a">11104</span>:90;<span style="background:#c16c2d">13217</span>:0;<span style="background:#f63a0e">13223</span>:8;<span style="background:#33be9e">11103</span>:1"
 
<br />
 
This SMS will set up your device to report the Speed Limiting scenario to the server.
 
 
 
'''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;" |
 
00000000000000758E010000017CB7A57370000F0E53AE209AB86A007F00110D0000<span style="color:red;">00FF</span>0015000800EF0100F00100500100150300C80000450100010000B30100 0A00B5000A00B6000600423FC900180000004300000044000000
 
1100220012FFBA0013FC34000F0000000200F10000601A0010002D97E0000000000100002136
 
 
 
|}
 
{| 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 75
 
|-
 
| 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 7C B7 A5 73 70 00 (Monday, October 25, 2021 4:30:46 PM GMT+03: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;" |0F 0E 53 AE
 
|-
 
| style="vertical-align: middle; text-align: center;" |Latitude
 
| style="vertical-align: middle; text-align: center;" |20 9A B8 6A
 
|-
 
| style="vertical-align: middle; text-align: center;" |Altitude
 
| style="vertical-align: middle; text-align: center;" |00 7F
 
|-
 
| style="vertical-align: middle; text-align: center;" |Angle
 
| style="vertical-align: middle; text-align: center;" |00 11
 
|-
 
| 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;" |<span style="background:#c668ae">00 FF</span> (Over Speeding)
 
|-
 
| style="vertical-align: middle; text-align: center;" |N of Total ID
 
| style="vertical-align: middle; text-align: center;" |00 15
 
|-
 
| style="vertical-align: middle; text-align: center;" | N1 of One Byte IO
 
| style="vertical-align: middle; text-align: center;" |00 08
 
|-
 
| 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;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" | 3’rd IO ID
 
| style="vertical-align: middle; text-align: center;" |50 (AVL ID: 80, Name: Data Mode)
 
|-
 
| style="vertical-align: middle; text-align: center;" |3’rd IO Value
 
| style="vertical-align: middle; text-align: center;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| style="vertical-align: middle; text-align: center;" |15 (AVL ID: 21, Name: GSM Signal)
 
|-
 
| 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;" |C8 (AVL ID: 200, Name: Sleep Mode)
 
|-
 
| 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;" | 45 (AVL ID: 69, Name: GNSS Status)
 
|-
 
| 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;" |01 (AVL ID: 1, Name: Digital Input 1)
 
|-
 
| style="vertical-align: middle; text-align: center;" |7'th IO Value
 
| style="vertical-align: middle; text-align: center;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" |8'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;" |8'th IO Value
 
| style="vertical-align: middle; text-align: center;" |01
 
|-
 
| style="vertical-align: middle; text-align: center;" | N2 of Two 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;" |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 0A
 
|-
 
| 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 06
 
|-
 
| 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;" |3F C9
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO ID
 
| style="vertical-align: middle; text-align: center;" |18 (AVL ID: 24, Speed)
 
|-
 
| style="vertical-align: middle; text-align: center;" |4'th IO Value
 
| style="vertical-align: middle; text-align: center;" |5F
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO ID
 
| style="vertical-align: middle; text-align: center;" |43 (AVL ID: 67, Battery Voltage)
 
|-
 
| style="vertical-align: middle; text-align: center;" |5'th IO Value
 
| style="vertical-align: middle; text-align: center;" |00 07
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO ID
 
| style="vertical-align: middle; text-align: center;" |44 (AVL ID: 68, Battery Current)
 
|-
 
| style="vertical-align: middle; text-align: center;" |6'th IO Value
 
| style="vertical-align: middle; text-align: center;" |00 C8
 
|-
 
| style="vertical-align: middle; text-align: center;" |7'th IO ID
 
| style="vertical-align: middle; text-align: center;" |11 (AVL ID:17, Axis X)
 
|-
 
| style="vertical-align: middle; text-align: center;" |7’th IO Value
 
| style="vertical-align: middle; text-align: center;" |00 22
 
|-
 
| style="vertical-align: middle; text-align: center;" |8'th IO ID
 
| style="vertical-align: middle; text-align: center;" |12 (AVL ID:18, Axis Y)
 
|-
 
| style="vertical-align: middle; text-align: center;" |8’th IO Value
 
| style="vertical-align: middle; text-align: center;" |FF BA
 
|-
 
| style="vertical-align: middle; text-align: center;" |9'th IO ID
 
| style="vertical-align: middle; text-align: center;" |13 (AVL ID:19, Axis Z)
 
|-
 
| style="vertical-align: middle; text-align: center;" | 9'th IO Value
 
| style="vertical-align: middle; text-align: center;" | FC 34
 
|-
 
| style="vertical-align: middle; text-align: center;" |10'th IO ID
 
| style="vertical-align: middle; text-align: center;" |0F (AVL ID: 15, ECO Score)
 
|-
 
| 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;" | N4 of Four Byte IO
 
| style="vertical-align: middle; text-align: center;" |00 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 00 10
 
|-
 
| 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 2D 97 E0
 
|-
 
| style="vertical-align: middle; text-align: center;" |N8 of Eight Byte IO
 
| style="vertical-align: middle; text-align: center;" |00 00
 
|-
 
| 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 7F CF
 
|}
 
 
 
 
 
Speed limiting is activated when max speed is exceeded. Relay is activated on DOUT1 which can either disable the acceleration pedal, turn off the fuel pump or close the solenoid valve. Only one scenario can be used per MSP500 device.
 
 
 
[[Category: Usage scenarios]]
 

Latest revision as of 11:20, 24 May 2023

Main Page > General Information > Usage scenarios > Speed Limiting Solution

Introduction

Due to the accidents caused by over speeding, corporate fleet businesses and insurance companies suffer from huge losses in most of the countries globally. This can often lead to a loss in productivity, reduction in revenue, paying insurance costs (if it’s the driver’s fault), as well as medical and collateral damage costs. To help resolve this major concern, here at Teltonika Telematics we have developed and manufactured a unique GPS tracker with the speed limiter feature.

Challenge

Utilizing a modern and comprehensive GPS tracking method allows you to monitor driver (including novice) behavior, improve safety, and reduce the fleet running costs and legal liability. And that is where Teltonika FMx series and MSP500 tracker-speed limiter come into the play.

Scenarios

Benefits

  • Over speeding quick fix for good – the most common and widely spread speeding problem is resolved at once and for all with a minimum effort and maximum results.
  • Extensive functionality to serve your needs – highly advanced, configurable and efficient speed limiting solution. The rich set of features can be utilised in a combination with speed limiter functionality making it a truly comprehensive all-in-one solution for any fleet.
  • Improves drivers’ discipline and time efficiency – great assistance for novice drivers and seasoned professionals helping to stay safe and perform daily tasks with the least waste of time.
  • Lower expenses, higher profits – by preventing traffic accidents, speed tickets, delays, casualties, and insurance cost rise, this tracker very likely will improve fleet operational cost, company cash flow, and ROI.
  • Various fleets, one solution – suitable for all sorts of fleets and logistic businesses including freight forwarders, carriers, international and domestic couriers, 3rd party logistic service providers, livestock transportation, luxury and executive class fleets, etc.