Teltonika Telematics Wiki - User contributions [en]

Category:Speed Limiting Solution

2023-06-14T12:05:01Z

Ahmed Hossam: Created page with "2"

[[Category:Usage scenarios|2]]

TeraCom-TSH202

2023-06-12T13:25:11Z

Ahmed Hossam:

[[File:1-wire-humidity-sensor-tsh202-gal-1-w.jpg|thumb|400px|TeraCom TSH202]]
==Introduction==

TeraCom TSH202 is humidity and temperature sensors with a 1-Wire interface. The device integrates basic elements plus signals processing, and provides a fully calibrated digital output. A unique capacitive element is used for measuring relative humidity while the temperature is measured by a band gap sensor. Both sensors are seamlessly coupled to a 12-bit analog to digital converter. This results in superior signal quality and fast response time.

==Applications==

*Server room and data centers monitoring.
*Environmental quality monitoring and assessment.
*Humidity and temperature monitoring in building management systems.
*Humidity and temperature monitoring for mobile operator facilities, vineyards, greenhouses, etc.

==Technical parameters==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |NAME
! style="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;" |Interface
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-Wire Interface
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Wiring
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White = 1-wire signal, Red = 1-wire power, Black = Ground
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |-20 ºC to +60 ºC
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating humidity
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |10 to 90%RH
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance typ.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±3.0 %RH (20 to 80 %RH), ±0.4 °C (-10 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance max.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±5.0 %RH (10 to 90) %RH, ±1.0 °C (-20 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply/consumption
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4.0 to 5.5 VDC, 5 mA
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Dimensions
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |45 x 16 x 10
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Cable length
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1 m
|-
|}

'''<nowiki>*</nowiki>''' Recommended operating range is 20% to 80% RH (non-condensing) over -10°C to +60°C.

Prolonged operation beyond these ranges may result in a shift of sensor reading, with slow recovery time.

==Installation==

*TSH202 will be connected with FM devices via 1-wire interface.
*To connect the 1-wire TSH202 sensor you have to make sure to connect 3 PINs of the sensor to the PINs of your device correctly.

[[File:TSH202 Scheme.PNG|frameless|800x420px]] [[File:FMB120-2x6 socket pinout.png|thumb|400px|FMB120-2x6 socket pinout]]
[[File:FMC130-2x6 socket pinout.png|thumb|400px|FMC130-2x6 socket pinout]]

==Connections==

We tested TSH202 sensor with FMB120 & FMC130 devices and connections will be as per following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |TSH202 wire color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connections
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDD (+4.0 to +5.5V) 1-wire power of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-wire signal of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground of FM device
|-
|}

==Configuration==

#Use '''Firmware ver.03.27.13.Rev.480.e''' and above.
#Use '''Teltonika.Configurator_1.7.30_E.THS202_R.4''' and above.

===With FMB120:===

[[File:TSH202-FMB120.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:TSH202-FMC130.mp4|none|thumb|1920x1080px]]

'''''<nowiki>*</nowiki>''' The used Firmware is tested with '''TSH202v3 model'''.''

==Demonstration in Flespi platform==
Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.

===With FMB120:===

[[File:FMB120 TSH202-server.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:FMC130 TSH202-server.mp4|none|thumb|1920x1080px]]

==Downloads==
'''Manual & Documentation''' 

[[File:pdf_icon.png|32px|link=]]
[[Media:Tsh202v3-1-wire-humidity-temperature-sensor-brochure-r1.10.pdf|1-Wire humidity and temperature sensor TSH202 brochure(v1.10)]]

[[Category:Accessories]]

TeraCom-TSH202

2023-06-12T13:24:03Z

Ahmed Hossam:

[[File:1-wire-humidity-sensor-tsh202-gal-1-w.jpg|thumb|400px|TeraCom TSH202]]
==Introduction==

TeraCom TSH202 is humidity and temperature sensors with a 1-Wire interface. The device integrates basic elements plus signals processing, and provides a fully calibrated digital output. A unique capacitive element is used for measuring relative humidity while the temperature is measured by a band gap sensor. Both sensors are seamlessly coupled to a 12-bit analog to digital converter. This results in superior signal quality and fast response time.

==Applications==

*Server room and data centers monitoring.
*Environmental quality monitoring and assessment.
*Humidity and temperature monitoring in building management systems.
*Humidity and temperature monitoring for mobile operator facilities, vineyards, greenhouses, etc.

==Technical parameters==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |NAME
! style="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;" |Interface
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-Wire Interface
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Wiring
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White = 1-wire signal, Red = 1-wire power, Black = Ground
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |-20 ºC to +60 ºC
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating humidity
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |10 to 90%RH
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance typ.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±3.0 %RH (20 to 80 %RH), ±0.4 °C (-10 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance max.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±5.0 %RH (10 to 90) %RH, ±1.0 °C (-20 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply/consumption
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4.0 to 5.5 VDC, 5 mA
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Dimensions
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |45 x 16 x 10
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Cable length
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1 m
|-
|}

'''<nowiki>*</nowiki>''' Recommended operating range is 20% to 80% RH (non-condensing) over -10°C to +60°C.

Prolonged operation beyond these ranges may result in a shift of sensor reading, with slow recovery time.

==Installation==

*TSH202 will be connected with FM devices via 1-wire interface.
*To connect the 1-wire TSH202 sensor you have to make sure to connect 3 PINs of the sensor to the PINs of your device correctly.

[[File:TSH202 Scheme.PNG|frameless|800x420px]] [[File:FMB120-2x6 socket pinout.png|thumb|400px|FMB120-2x6 socket pinout]]
[[File:FMC130-2x6 socket pinout.png|thumb|400px|FMC130-2x6 socket pinout]]

==Connections==

We tested TSH202 sensor with FMB120 & FMC130 devices and connections will be as per following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |TSH202 wire color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connections
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDD (+4.0 to +5.5V) 1-wire power of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-wire signal of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground of FM device
|-
|}

==Configuration==

#Use '''Firmware ver.03.27.13.Rev.480.e''' and above.
#Use '''Teltonika.Configurator_1.7.30_E.THS202_R.4''' and above.

===With FMB120:===

[[File:TSH202-FMB120.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:TSH202-FMC130.mp4|none|thumb|1920x1080px]]

'''''<nowiki>*</nowiki>''' The used Firmware is tested with '''TSH202v3 models'''.''

==Demonstration in Flespi platform==
Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.

===With FMB120:===

[[File:FMB120 TSH202-server.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:FMC130 TSH202-server.mp4|none|thumb|1920x1080px]]

==Downloads==
'''Manual & Documentation''' 

[[File:pdf_icon.png|32px|link=]]
[[Media:Tsh202v3-1-wire-humidity-temperature-sensor-brochure-r1.10.pdf|1-Wire humidity and temperature sensor TSH202 brochure(v1.10)]]

[[Category:Accessories]]

Accessories

2023-06-12T05:46:47Z

Ahmed Hossam:

'''Satellite data, relays, readers & IP67 cases''' 
[[TSM232|TSM232]] 
[[TSM232-Hybrid]] 
[[Iridium Edge]] 
[[Automotive Relay]] 
[[NBL-2]] 
[[Inateck BCST-70 Barcode Scanner]] 
[[IP67 Case]] 
'''Fuel & temperature sensors''' 
[[Analog Fuel Sensor|Analog Fuel Sensor]] 
[[TeraCom-TSH202]] 
[[1-Wire Temperature Sensors|1-Wire Temperature Sensors]] 
[[TTJ Temperature sensor|TTJ Temperature sensor]] 
[[UL202 Ultrasonic Fuel Sensor|UL202 Ultrasonic Fuel Sensor]] 
[[Technoton DUT-E S7 Fuel Level Sensor|Technoton DUT-E S7]] 
[[Technoton DFM D S7 Differential Fuel Flow Meter|Technoton DFM (D) S7]] 
[[Technoton GNOM DDE/DP S7 Axle Load Sensors|Technoton GNOM DDE/DP S7]] 
'''1-Wire readers''' 
[[1-Wire iButton Reader]] 
[[1-Wire RFID Reader]] 

[[Category:Main Page]]

TeraCom-TSH202

2023-06-08T06:57:41Z

Ahmed Hossam:

[[File:1-wire-humidity-sensor-tsh202-gal-1-w.jpg|thumb|400px|TeraCom TSH202]]
==Introduction==

TeraCom TSH202 is humidity and temperature sensors with a 1-Wire interface. The device integrates basic elements plus signals processing, and provides a fully calibrated digital output. A unique capacitive element is used for measuring relative humidity while the temperature is measured by a band gap sensor. Both sensors are seamlessly coupled to a 12-bit analog to digital converter. This results in superior signal quality and fast response time.

==Applications==

*Server room and data centers monitoring.
*Environmental quality monitoring and assessment.
*Humidity and temperature monitoring in building management systems.
*Humidity and temperature monitoring for mobile operator facilities, vineyards, greenhouses, etc.

==Technical parameters==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |NAME
! style="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;" |Interface
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-Wire Interface
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Wiring
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White = 1-wire signal, Red = 1-wire power, Black = Ground
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |-20 ºC to +60 ºC
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating humidity
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |10 to 90%RH
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance typ.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±3.0 %RH (20 to 80 %RH), ±0.4 °C (-10 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance max.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±5.0 %RH (10 to 90) %RH, ±1.0 °C (-20 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply/consumption
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4.0 to 5.5 VDC, 5 mA
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Dimensions
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |45 x 16 x 10
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Cable length
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1 m
|-
|}

'''<nowiki>*</nowiki>''' Recommended operating range is 20% to 80% RH (non-condensing) over -10°C to +60°C.

Prolonged operation beyond these ranges may result in a shift of sensor reading, with slow recovery time.

==Installation==

*TSH202 will be connected with FM devices via 1-wire interface.
*To connect the 1-wire TSH202 sensor you have to make sure to connect 3 PINs of the sensor to the PINs of your device correctly.

[[File:TSH202 Scheme.PNG|frameless|800x420px]] [[File:FMB120-2x6 socket pinout.png|thumb|400px|FMB120-2x6 socket pinout]]
[[File:FMC130-2x6 socket pinout.png|thumb|400px|FMC130-2x6 socket pinout]]

==Connections==

We tested TSH202 sensor with FMB120 & FMC130 devices and connections will be as per following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |TSH202 wire color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connections
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDD (+4.0 to +5.5V) 1-wire power of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-wire signal of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground of FM device
|-
|}

==Configuration==

#Use '''Firmware ver.03.27.13.Rev.480.e''' and above.
#Use '''Teltonika.Configurator_1.7.30_E.THS202_R.4''' and above.

===With FMB120:===

[[File:TSH202-FMB120.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:TSH202-FMC130.mp4|none|thumb|1920x1080px]]

'''''<nowiki>*</nowiki>''' The used Firmware is tested with '''TSH202v3 models and above'''.''

==Demonstration in Flespi platform==
Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.

===With FMB120:===

[[File:FMB120 TSH202-server.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:FMC130 TSH202-server.mp4|none|thumb|1920x1080px]]

==Downloads==
'''Manual & Documentation''' 

[[File:pdf_icon.png|32px|link=]]
[[Media:Tsh202v3-1-wire-humidity-temperature-sensor-brochure-r1.10.pdf|1-Wire humidity and temperature sensor TSH202 brochure(v1.10)]]

[[Category:Accessories]]

TeraCom-TSH202

2023-06-06T12:12:48Z

Ahmed Hossam: Created page with "TeraCom TSH202 ==Introduction== TeraCom TSH202 is humidity and temperature sensors with a 1-Wire interface. The..."

[[File:1-wire-humidity-sensor-tsh202-gal-1-w.jpg|thumb|400px|TeraCom TSH202]]
==Introduction==

TeraCom TSH202 is humidity and temperature sensors with a 1-Wire interface. The device integrates basic elements plus signals processing, and provides a fully calibrated digital output. A unique capacitive element is used for measuring relative humidity while the temperature is measured by a band gap sensor. Both sensors are seamlessly coupled to a 12-bit analog to digital converter. This results in superior signal quality and fast response time.

==Applications==

*Server room and data centers monitoring.
*Environmental quality monitoring and assessment.
*Humidity and temperature monitoring in building management systems.
*Humidity and temperature monitoring for mobile operator facilities, vineyards, greenhouses, etc.

==Technical parameters==

{| class="wikitable"
|+
! style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |NAME
! style="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;" |Interface
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-Wire Interface
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Wiring
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White = 1-wire signal, Red = 1-wire power, Black = Ground
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |-20 ºC to +60 ºC
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |'''*''' Operating humidity
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |10 to 90%RH
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance typ.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±3.0 %RH (20 to 80 %RH), ±0.4 °C (-10 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Tolerance max.
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |±5.0 %RH (10 to 90) %RH, ±1.0 °C (-20 to +60°C)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Power supply/consumption
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |4.0 to 5.5 VDC, 5 mA
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Dimensions
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |45 x 16 x 10
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Cable length
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1 m
|-
|}

'''<nowiki>*</nowiki>''' Recommended operating range is 20% to 80% RH (non-condensing) over -10°C to +60°C.

Prolonged operation beyond these ranges may result in a shift of sensor reading, with slow recovery time.

==Installation==

*TSH202 will be connected with FM devices via 1-wire interface.
*To connect the 1-wire TSH202 sensor you have to make sure to connect 3 PINs of the sensor to the PINs of your device correctly.

[[File:TSH202 Scheme.PNG|frameless|800x420px]] [[File:FMB120-2x6 socket pinout.png|thumb|400px|FMB120-2x6 socket pinout]]
[[File:FMC130-2x6 socket pinout.png|thumb|400px|FMC130-2x6 socket pinout]]

==Connections==

We tested TSH202 sensor with FMB120 & FMC130 devices and connections will be as per following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |TSH202 wire color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connections
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDD (+4.0 to +5.5V) 1-wire power of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |1-wire signal of FM device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground of FM device
|-
|}

==Configuration==

#Use the tested '''Firmware ver.03.27.13.Rev.480.e'''
#Use '''Teltonika.Configurator_1.7.30_E.THS202_R.4'''

===With FMB120:===

[[File:TSH202-FMB120.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:TSH202-FMC130.mp4|none|thumb|1920x1080px]]

'''''<nowiki>*</nowiki>''' The used Firmware is tested with '''TSH202v3 models and above'''.''

==Demonstration in Flespi platform==
Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.

===With FMB120:===

[[File:FMB120 TSH202-server.mp4|none|thumb|1920x1080px]]

===With FMC130:===

[[File:FMC130 TSH202-server.mp4|none|thumb|1920x1080px]]

==Downloads==
'''Manual & Documentation''' 

[[File:pdf_icon.png|32px|link=]]
[[Media:Tsh202v3-1-wire-humidity-temperature-sensor-brochure-r1.10.pdf|1-Wire humidity and temperature sensor TSH202 brochure(v1.10)]]

[[Category:Accessories]]

File:FMC130 TSH202-server.mp4

2023-06-06T11:39:01Z

Ahmed Hossam:

File:FMB120 TSH202-server.mp4

2023-06-06T11:37:58Z

Ahmed Hossam:

File:TSH202-FMC130.mp4

2023-06-06T11:34:58Z

Ahmed Hossam:

File:TSH202-FMB120.mp4

2023-06-06T11:34:34Z

Ahmed Hossam:

File:TSH202 Scheme.PNG

2023-06-06T11:31:03Z

Ahmed Hossam:

File:FMC130 server.mp4

2023-06-01T13:53:29Z

Ahmed Hossam:

File:Tsh202v3-1-wire-humidity-temperature-sensor-brochure-r1.10.pdf

2023-05-31T13:55:31Z

Ahmed Hossam:

File:TSH202v3-FMC130.mp4

2023-05-31T13:44:06Z

Ahmed Hossam:

File:TSH202v3-FMB120.mp4

2023-05-31T13:33:14Z

Ahmed Hossam:

File:FMC130-2x6 socket pinout.png

2023-05-31T07:15:12Z

Ahmed Hossam:

File:FMB120-2x6 socket pinout.png

2023-05-31T07:14:38Z

Ahmed Hossam:

File:1-wire-humidity-sensor-tsh202-gal-1-w.jpg

2023-05-29T05:48:18Z

Ahmed Hossam:

Speed Limiting Solution

2023-05-24T08:20:26Z

Ahmed Hossam:

Speed Limiting Solution MSP500+ETC

2023-05-14T05:28:19Z

Ahmed Hossam: /* 1. Relay test: */

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

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

==What you need for a solution?==

*'''[https://wiki.teltonika-gps.com/view/MSP500 MSP500]''' device.
*<nowiki></nowiki>'''Electronic Throttle Controller.'''
*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.
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.
*<nowiki>*</nowiki>'''Solenoid Valve.'''

<nowiki>*</nowiki>'''Solenoid Valve''' is optional for one of the wiring schemes shown below

==Installation==

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.

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 3 ways of connecting the MSP500 device which are displayed below:

[[File:Elthrottlecontr.png|none|thumb|832x832px]]
[[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. 

==ETC Connections==

==='''1. ETC connection between vehicle ECU and Accelerator Pedal:'''===

*Test the connection between ECU and Accelerator Pedal to detect the +V and -V wires using Multimeter.
*Unplug vehicle battery cable before connecting ETC and MSP500.
*Connect wires as per the following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |ETC cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V-/0.40V from Accelerator pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Brown
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V+/0.70V from Accelerator Pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yellow
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S+/0.70V from ECU
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Grey
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S-/0.40V from ECU
|-
|}

[[File:ETC_ECU and Accelerator Pedal.png|none|thumb|800x520px]]
'''Note:''' Voltage may vary depending on vehicle model.

[[File:ETC.mp4|none|thumb|1920x1080px]]
''In this tested vehicle. Voltages of the connections between ECU and Accelerator Pedal are (+) 0.49V and (-) 0.25V.''

==='''2. ETC connection with MSP500:'''===

*Use a cable extension (optional) to connect ETC with MSP500.
*Connect wires as per the following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |ETC cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDC (+10...32) (COM Relay of MSP500)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground (Ground of MSP500)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Green
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |NC Relay of MSP500
|-
|}

[[File:ETC2.png|none|thumb|800x520px]]

==ETC Calibration==

*Plug vehicle battery cable.
*Start the vehicle engine for ETC calibration.
*Open ETC and press the calibration button for 3 seconds to store the IDLE voltage coming from the accelerator pedal.

[[File:Calibration Button.mp4|none|thumb|1920x1080px]]

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

 

*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, 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]]. [[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 [[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-GNSS.png|left|thumb]]
[[File:Overspeeding-AIN1.png|left|thumb]]

 
Over speeding settings

*11100 – Scenario settings (0 – Disable, 1 – Low Priority, 2 – '''High Priority''' (Default), 3 – Panic Priority)
*11104 - Max Speed (Default value - 90 km/h), here we tested on '''40 km/h'''
*13217 - Speed Source (0 - '''GNSS''' (Default), 1 - OBD, 2 - AIN1)
In case of '''AIN1''', if you use only A2 - the formula would look like ''Speed = A2 * Pulses''
*13223 - Over speeding Hysteresis (Default value - '''8%'''), value that determines what would be the threshold speed level that would activate the speed limiting feature
*11103 - Output Control (0 - None (Default), 1 - DOUT1), '''DOUT1''' needs to be enabled to use the speed limiting feature

 

'''Quickstart:''' From default configuration to Speed Limiting solution in one SMS:

" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;11100:2;11104:40;13217:0;13223:8;11103:1"
 
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.

==Testing==
==='''1. Relay test:'''===
*Go to Maintenance.
*Switch DOUT 1 option to ON when pressing the accelerator pedal.
*RPM should be decreased to idle when the relay is ON.

[[File:Relay OFF.png|none|thumb|800x556px]]
[[File:Relay ON.png|none|thumb|800x556px]]

==='''2. Road test:'''===
*We tested the over speed scenario on '''40 km/h''' using '''GNSS''' as a speed source.
*The AVL ID of over speeding scenario is '''io_255'''.
*In this scenario we monitored the speed change from 39 km/h to 41 km/h
*A record has been sent with the over speeding event io_255 when the speed exceed/fall behind 40 km/h.

==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;" |
000000000000005E8E010000017DE72C308A012100F6F60EF8A0FE0000008F0A002900FF0010000700EF0100F00100150200C80000450101F60000FF29000500B5 000F00B60008004238D500431F5000440027000200F10000A5A200100000BF7B000000000100006D90

|}
{| 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 5E
|-
| 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 7D E7 2C 30 8A (Thursday, December 23, 2021 12:02:52 PM GMT+04:00)
|-
| 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;" |21 00 F6 F6
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |0E F8 A0 FE
|-
| 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 8F
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0A
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 29
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 FF (Over Speeding)
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 0E
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 07
|-
| 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;" |01
|-
| 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;" |01
|-
| style="vertical-align: middle; text-align: center;" |3'rd IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |02
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |00 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;" |01 F6 (AVL ID: 502, Name: MSP500 Speed Sensor 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;" |00 FF (AVL ID: 255, Name: Over Speeding)
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |29 (Speed is 41 km/h)
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 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 0F
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 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 08
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |38 D5
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |00 43 (AVL ID: 67, Battery Voltage)
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |1F 50
|-
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |00 44 (AVL ID: 68, Battery Current)
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |00 27
|-
| 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;" |00 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 A5 A2
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 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 BF 7B
|-
| 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 6D 90
|}

==Demonstration in Wialon platform==
 Wialon: Open Wialon application → Select Messages → Select Unit → Select the date interval → Select Chart → Select io_255.
 

[[File:Wialon io.png|none|thumb|618x436px]]
[[File:Wialon Overspeed.png|none|thumb|800x542px]]

==Demonstration in Flespi platform==
 Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.
 

[[File:Flespi.mp4|none|thumb|1920x1080px]]

==Demonstration in TAVL platform==
 TAVL: Open TAVL application → Select Client → Select Device → Select the date interval → Select Track→ Select Advanced → Chose Show button see in left down corner all the information.
 

[[File:Msp500Overspeed.png|alt=|frameless|1000x1000px]]
 

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: Speed Limiting Solution]]

Speed Limiting Solution MSP500+ETC

2023-05-11T13:55:58Z

Ahmed Hossam:

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

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

==What you need for a solution?==

*'''[https://wiki.teltonika-gps.com/view/MSP500 MSP500]''' device.
*<nowiki></nowiki>'''Electronic Throttle Controller.'''
*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.
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.
*<nowiki>*</nowiki>'''Solenoid Valve.'''

<nowiki>*</nowiki>'''Solenoid Valve''' is optional for one of the wiring schemes shown below

==Installation==

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.

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 3 ways of connecting the MSP500 device which are displayed below:

[[File:Elthrottlecontr.png|none|thumb|832x832px]]
[[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. 

==ETC Connections==

==='''1. ETC connection between vehicle ECU and Accelerator Pedal:'''===

*Test the connection between ECU and Accelerator Pedal to detect the +V and -V wires using Multimeter.
*Unplug vehicle battery cable before connecting ETC and MSP500.
*Connect wires as per the following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |ETC cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V-/0.40V from Accelerator pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Brown
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V+/0.70V from Accelerator Pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yellow
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S+/0.70V from ECU
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Grey
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S-/0.40V from ECU
|-
|}

[[File:ETC_ECU and Accelerator Pedal.png|none|thumb|800x520px]]
'''Note:''' Voltage may vary depending on vehicle model.

[[File:ETC.mp4|none|thumb|1920x1080px]]
''In this tested vehicle. Voltages of the connections between ECU and Accelerator Pedal are (+) 0.49V and (-) 0.25V.''

==='''2. ETC connection with MSP500:'''===

*Use a cable extension (optional) to connect ETC with MSP500.
*Connect wires as per the following sequence.

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |ETC cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |+VDC (+10...32) (COM Relay of MSP500)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Ground (Ground of MSP500)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Green
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |NC Relay of MSP500
|-
|}

[[File:ETC2.png|none|thumb|800x520px]]

==ETC Calibration==

*Plug vehicle battery cable.
*Start the vehicle engine for ETC calibration.
*Open ETC and press the calibration button for 3 seconds to store the IDLE voltage coming from the accelerator pedal.

[[File:Calibration Button.mp4|none|thumb|1920x1080px]]

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

 

*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, 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]]. [[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 [[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-GNSS.png|left|thumb]]
[[File:Overspeeding-AIN1.png|left|thumb]]

 
Over speeding settings

*11100 – Scenario settings (0 – Disable, 1 – Low Priority, 2 – '''High Priority''' (Default), 3 – Panic Priority)
*11104 - Max Speed (Default value - 90 km/h), here we tested on '''40 km/h'''
*13217 - Speed Source (0 - '''GNSS''' (Default), 1 - OBD, 2 - AIN1)
In case of '''AIN1''', if you use only A2 - the formula would look like ''Speed = A2 * Pulses''
*13223 - Over speeding Hysteresis (Default value - '''8%'''), value that determines what would be the threshold speed level that would activate the speed limiting feature
*11103 - Output Control (0 - None (Default), 1 - DOUT1), '''DOUT1''' needs to be enabled to use the speed limiting feature

 

'''Quickstart:''' From default configuration to Speed Limiting solution in one SMS:

" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;11100:2;11104:40;13217:0;13223:8;11103:1"
 
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.

==Testing==
==='''1. Relay test:'''===
# Go to Maintenance.
# Switch DOUT 1 option to ON when pressing the accelerator pedal.
# RPM should be decreased to idle when the relay is ON.

[[File:Relay OFF.png|none|thumb|800x556px]]
[[File:Relay ON.png|none|thumb|800x556px]]

==='''2. Road test:'''===
*We tested the over speed scenario on '''40 km/h''' using '''GNSS''' as a speed source.
*The AVL ID of over speeding scenario is '''io_255'''.
*In this scenario we monitored the speed change from 39 km/h to 41 km/h
*A record has been sent with the over speeding event io_255 when the speed exceed/fall behind 40 km/h.

==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;" |
000000000000005E8E010000017DE72C308A012100F6F60EF8A0FE0000008F0A002900FF0010000700EF0100F00100150200C80000450101F60000FF29000500B5 000F00B60008004238D500431F5000440027000200F10000A5A200100000BF7B000000000100006D90

|}
{| 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 5E
|-
| 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 7D E7 2C 30 8A (Thursday, December 23, 2021 12:02:52 PM GMT+04:00)
|-
| 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;" |21 00 F6 F6
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |0E F8 A0 FE
|-
| 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 8F
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |0A
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 29
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |00 FF (Over Speeding)
|-
| style="vertical-align: middle; text-align: center;" |N of Total ID
| style="vertical-align: middle; text-align: center;" |00 0E
|-
| style="vertical-align: middle; text-align: center;" |N1 of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 07
|-
| 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;" |01
|-
| 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;" |01
|-
| style="vertical-align: middle; text-align: center;" |3'rd IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |02
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |00 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;" |01 F6 (AVL ID: 502, Name: MSP500 Speed Sensor 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;" |00 FF (AVL ID: 255, Name: Over Speeding)
|-
| style="vertical-align: middle; text-align: center;" |7'th IO Value
| style="vertical-align: middle; text-align: center;" |29 (Speed is 41 km/h)
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Byte IO
| style="vertical-align: middle; text-align: center;" |00 05
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 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 0F
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 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 08
|-
| style="vertical-align: middle; text-align: center;" |3’rd IO ID
| style="vertical-align: middle; text-align: center;" |00 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;" |38 D5
|-
| style="vertical-align: middle; text-align: center;" |4'th IO ID
| style="vertical-align: middle; text-align: center;" |00 43 (AVL ID: 67, Battery Voltage)
|-
| style="vertical-align: middle; text-align: center;" |4'th IO Value
| style="vertical-align: middle; text-align: center;" |1F 50
|-
| style="vertical-align: middle; text-align: center;" |5'th IO ID
| style="vertical-align: middle; text-align: center;" |00 44 (AVL ID: 68, Battery Current)
|-
| style="vertical-align: middle; text-align: center;" |5'th IO Value
| style="vertical-align: middle; text-align: center;" |00 27
|-
| 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;" |00 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 A5 A2
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 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 BF 7B
|-
| 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 6D 90
|}

==Demonstration in Wialon platform==
 Wialon: Open Wialon application → Select Messages → Select Unit → Select the date interval → Select Chart → Select io_255.
 

[[File:Wialon io.png|none|thumb|618x436px]]
[[File:Wialon Overspeed.png|none|thumb|800x542px]]

==Demonstration in Flespi platform==
 Flespi: Open Flespi application → Select Device → Select Logs & Messages → Select the record interval → Tap to see all information.
 

[[File:Flespi.mp4|none|thumb|1920x1080px]]

==Demonstration in TAVL platform==
 TAVL: Open TAVL application → Select Client → Select Device → Select the date interval → Select Track→ Select Advanced → Chose Show button see in left down corner all the information.
 

[[File:Msp500Overspeed.png|alt=|frameless|1000x1000px]]
 

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: Speed Limiting Solution]]

File:Overspeeding-AIN1.png

2023-05-11T13:53:05Z

Ahmed Hossam:

File:Flespi.mp4

2023-05-11T11:48:37Z

Ahmed Hossam: Ahmed Hossam uploaded a new version of File:Flespi.mp4

File:Flespi.mp4

2023-05-11T11:44:49Z

Ahmed Hossam: Ahmed Hossam uploaded a new version of File:Flespi.mp4

File:Flespi.mp4

2023-05-11T11:07:23Z

Ahmed Hossam:

File:Wialon io.png

2023-05-11T08:03:34Z

Ahmed Hossam:

File:Wialon Overspeed.png

2023-05-11T07:57:27Z

Ahmed Hossam:

File:Relay ON.png

2023-05-10T12:18:30Z

Ahmed Hossam:

File:Relay OFF.png

2023-05-10T12:16:48Z

Ahmed Hossam:

File:Overspeeding-GNSS.png

2023-05-10T08:36:37Z

Ahmed Hossam:

File:Calibration Button.mp4

2023-05-10T07:10:44Z

Ahmed Hossam: Ahmed Hossam uploaded a new version of File:Calibration Button.mp4

File:Calibration Button.mp4

2023-05-10T07:03:18Z

Ahmed Hossam:

File:ETC2.png

2023-05-10T05:58:48Z

Ahmed Hossam:

File:ETC.mp4

2023-05-09T13:30:35Z

Ahmed Hossam:

File:ETC ECU and Accelerator Pedal.png

2023-05-08T08:50:46Z

Ahmed Hossam:

Speed Limiting Solution MSP500+ETC

2023-05-07T11:06:13Z

Ahmed Hossam:

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

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

==What you need for a solution?==

*'''[https://wiki.teltonika-gps.com/view/MSP500 MSP500]''' device

*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
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.
*<nowiki>*</nowiki>'''Solenoid Valve'''

<nowiki>*</nowiki>'''Solenoid Valve''' is optional for one of the wiring schemes shown below

==Installation==

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.

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 3 ways of connecting the MSP500 device which are displayed below:

[[File:Elthrottlecontr.png|none|thumb|832x832px]]
[[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. 

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

 

*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, 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]]. [[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 [[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]]

 
Over speeding settings

*11100 – Scenario settings(0 – Disable, 1 – Low Priority, 2 – High Priority, 3 – Panic Priority)
*11104 - Max Speed (Default value - 90 km/h)
*13217 - Speed Source (0 - GNSS (Default), 1 - OBD, 2 - AIN1)
*13223 - Over speeding Hysteresis (Default value - 8%), value that determines what would be the threshold speed level that would activate the speed limiting feature
*11103 - Output Control (0 - None (Default), 1 - DOUT1), DOUT1 needs to be enabled to use the speed limiting feature

 

'''Quickstart:''' From default configuration to Speed Limiting solution in one SMS:

" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;11100:2;11104:90;13217:0;13223:8;11103:1"
 
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;" |
00000000000000758E010000017CB7A57370000F0E53AE209AB86A007F00110D000000FF0015000800EF0100F00100500100150300C80000450100010000B30100 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;" |00 FF (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
|}
==Demonstration in TAVL platform ==
 TAVL: Open TAVL application → Select Client → Select Device → Select the date interval → Select Track→ Select Advanced → Chose Show button see in left down corner all the information.
 

[[File:Msp500Overspeed.png|alt=|frameless|1000x1000px]]
 

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: Speed Limiting Solution]]

Speed Limiting Solution FMC130+ETC

2023-05-07T11:05:51Z

Ahmed Hossam:

==Introduction==

The loss incurred globally by corporate fleet and insurance businesses due to accidents caused by over speeding is significant. This can often lead to the loss in productivity and multiple other evident collateral damage costs. We at Teltonika Telematics have developed a unique solution to help tackle over speeding in the fleet.

==Solution description==

Using the combination of Teltonika FM device with the Automotive relay and the Electronic throttle controller to achieve speed limiter feature.

==What you need for a solution?==

*'''[https://wiki.teltonika-gps.com/view/FMC130 FMC130]''' device
*<nowiki></nowiki>'''Electronic Throttle Controller'''
*'''[https://wiki.teltonika-gps.com/view/Automotive_Relay Automotive Relay]'''
*The '''[https://wiki.teltonika-gps.com/view/FMC130_First_Start#How_to_insert_Micro-SIM_card_and_connect_the_battery SIM card]''' in order to get data to your server
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.
*<nowiki>*</nowiki>'''Solenoid Valve'''

<nowiki>*</nowiki>'''Solenoid Valve''' is optional for one of the wiring schemes shown below

==Installation==

This solution can be implemented in 3 different ways based on the speed limiting scenario. It’s important to install the device and the relay in an hidden place inside dashboard.

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.

There are 3 ways of connecting the FM device which are displayed below:

==='''A. Installation - Electronic Throttle Controller'''===

[[File:Seco function topology v1.8 scenario1.png]]

==='''B. Installation - Fuel Pump'''===

[[File:Seco function topology v1.8 scenario2.png]]

==='''C. Installation - Solenoid Valve'''===

[[File:Seco function topology v1.8 scenario3.png]]

==Wiring Scheme==

===''Relay Wiring Scheme''===

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Relay PIN
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Relay cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |30
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Blue
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | +VDC (Common connection to NO & NC terminals)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |85
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |DOUT of FM Device
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |86
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | +VDC (Coil)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |87
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yellow
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Not Required to connect (Normally Open (NO))
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |87a
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Green Wire from ETC '''or''' Wire to Fuel Pump '''or''' Wire to Solenoid Valve
|-
|}

===''ETC Wiring Scheme''===

{| class="wikitable"
|+
! style="width:20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |ETC cable color
! style="width:40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |Connection
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Red
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | +VDC (+10...32)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Black
| 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;" |Green
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | PIN 87a (NC of Relay)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |White
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V-/0.40V from Accelerator pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Brown
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | V+/0.70V from Accelerator Pedal
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Yellow
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S+/0.70V from ECU
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |Grey
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | S-/0.40V from ECU
|-
|}

'''Note:''' Voltage may vary depending on vehicle model.

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

*while the connecting the wires, please ensure the module is '''not plugged''' IN.
*Ensure the car ECU falls asleep, measure voltage on the chosen wire if it is still available. It usually takes 5 to 30 minutes period for the ECU to completely shutdown depending on the model of the vehicle.
*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/FMC130_First_Start First start guide]====
====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Sleep_Mode Sleep modes].====
==='''2. Configuration - Speed limiting:'''===
[[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, FM 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]]. [[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 [https://wiki.teltonika-gps.com/view/FMC130_Sleep_modes#Deep_Sleep_mode| Deep Sleep] and [https://wiki.teltonika-gps.com/view/FMC130_Sleep_modes#Ultra_Deep_Sleep_mode| 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.png|alt=|left|thumb]]

 
Over speeding settings

*11100 – Scenario settings(0 – Disable, 1 – Low Priority, 2 – High Priority, 3 – Panic Priority)
*11104 - Max Speed (Default value - 90 km/h)
*11103 - Output Control (0 - None (Default), 1 - DOUT1), DOUT1 needs to be enabled to use the speed limiting feature

 

Note: Detected speed has to be greater than (configured max speed +3% of configured max speed) for Over speed start event; detected speed has to be lower than(configured max speed -3% of configured max speed) for Over speed end event. 

'''Quickstart:''' From default configuration to Speed Limiting solution in one SMS:

" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;11100:2;11104:90;13217:0;13223:8;11103:1;11101:5000;11102:0"
 
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.

==='''3. Configuration - Speed Limiting based on Geo-Fence'''===

[[File:Manual Geofence OVERSPEEDING.png|left|frame]]

 

Manual Geofence settings

*20100 – Scenario settings(0 – Disable, 1 – Low Priority, 2 – High Priority, 3 – Panic Priority)
*20101 - Generate Event(0 - Disable, 1 - Low Priority, 2 - High Priority, 3 - Panic Priority)
*20104 - Shape Type(0 - Circle,1 - Rectangle)
*20105 - Radius in Metres
*20106 - X1 Coordinate
*20107 - Y1 Coordinate
*20108 - X2 Coordinate
*20109 - Y2 Coordinate
*20110 - Overspeeding(0 - Disable, 1- Enable) should be enabled for speed limiting functionality.
*2005 - Max allowed speed km/h.

Note: Detected speed has to be greater than (configured max speed +3% of configured max speed) for Over speed start event; detected speed has to be lower than(configured max speed -3% of configured max speed) for Over speed end event. 

==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;" |
00000000000000758E010000018494E2DAFA000F0E53AE209AB86A007F00110D000000FF0015000800EF0100F00100500100150300C800009B0300010000B301000A00B5000A00B6000
600423FC9001800000043000000440000001100220012FFBA0013FC34000F0000000200F10000601A0010002D97E0000000000100002136

|}
{| 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;" |00 FF (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;" | 009B (AVL ID: 155, Name: Geofence zone 01)
|-
| 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
|}
==Demonstration in Wialon platform ==
 Wialon: Open Wialon application → Select unit→ Select Device → Select the date interval → Select Track→ to access all the information.
 

[[File:Wialon+etc.png]]

'''Graphical Representation:'''

[[File:Graphetc.png]]

 

==Conclusion==

Speed limiting is achieved when max speed is exceeded. Relay is activated on DOUT1 which will disable the acceleration pedal, turn off the fuel pump or close the solenoid valve.

'''Note: Detected speed has to be greater than (configured max speed +3% of configured max speed) for Over speed start event; detected speed has to be lower than(configured max speed -3% of configured max speed) for Over speed end event.'''

[[Category: Speed Limiting Solution]]

Template:Usage Scenarios

2023-05-07T11:03:24Z

Ahmed Hossam: /* Use cases */

== Introduction ==

Our devices can be as simple or as complicated as you want them to be.
Having one firmware and one configurator for all the devices allows different devices to be used in a broad spectrum of use cases.
Other use cases have specific devices assigned.

To show how easy it is to use our devices in different use cases we prepared a technical description of what steps are needed to integrate our device into your use case.

Each category explains what parameters have to be configured and why as well as showing examples of what information you should expect on your server and how to read it.

The '''General''' use case descriptions, an overview of the most commonly used solutions, their topologies, and possibilities, provided on the Teltonika website [https://teltonika-gps.com/industries/use-cases/ '''USE CASES''']. '''Technical''' use case description provided below.

== Use cases ==
* [[GPS Electronic Logbook]]
* [[Green Driving Solution]]
* [[Anti-Theft Solution and Stolen Vehicle Recovery]]
* [[CONTINUOUS NETWORK CONNECTIVITY WITH AUTO TOP-UP FEATURE]]
* [[FLEET MAINTENANCE SCHEDULES (DELIVERY)]]
* [[DIGITAL TACHOGRAPH MONITORING]]
* [[BASIC TRACK & TRACE]]
* [[Private/Business Driving Mode Functionality]]
* [[Geofence Solution in the Event of Pandemic]]
* [[Secure vehicle disabling|Secure Vehicle Disabling]]
* [[TELEMATICS FOR AGRICULTURE AND FARMING INDUSTRY]]
* [[Police Fleet Management]]
* [[Car Sharing Solution]]
* [[FISHING BOATS TRACKING WITH IP67 RATING GPS DEVICES]]
* [[FAMILY CAR TRACKING AND MONITORING WITH OBD GPS DEVICES]]
* [[Pay as You Drive]]
* [[TRACKER’S SECURITY]]
* [[Speed Limiting Solution]]

Speed Limiting Solution

2023-05-07T10:59:33Z

Ahmed Hossam: Replaced content with "= Use cases = * Speed Limiting Solution MSP500+ETC * Speed Limiting Solution FMC130+ETC Category:Usage scenarios"

= Use cases =
* [[Speed Limiting Solution MSP500+ETC]]
* [[Speed Limiting Solution FMC130+ETC]]

[[Category:Usage scenarios]]

Speed Limiting Solution MSP500+ETC

2023-05-07T10:55:26Z

Ahmed Hossam: Created page with " ==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...."

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

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

==What you need for a solution?==

*'''[https://wiki.teltonika-gps.com/view/MSP500 MSP500]''' device

*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
*[https://wiki.teltonika-gps.com/view/FOTA_WEB '''FOTA WEB'''] to remotely send the configuration to the device.
*<nowiki>*</nowiki>'''Solenoid Valve'''

<nowiki>*</nowiki>'''Solenoid Valve''' is optional for one of the wiring schemes shown below

==Installation==

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.

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 3 ways of connecting the MSP500 device which are displayed below:

[[File:Elthrottlecontr.png|none|thumb|832x832px]]
[[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. 

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

 

*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, 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]]. [[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 [[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]]

 
Over speeding settings

*11100 – Scenario settings(0 – Disable, 1 – Low Priority, 2 – High Priority, 3 – Panic Priority)
*11104 - Max Speed (Default value - 90 km/h)
*13217 - Speed Source (0 - GNSS (Default), 1 - OBD, 2 - AIN1)
*13223 - Over speeding Hysteresis (Default value - 8%), value that determines what would be the threshold speed level that would activate the speed limiting feature
*11103 - Output Control (0 - None (Default), 1 - DOUT1), DOUT1 needs to be enabled to use the speed limiting feature

 

'''Quickstart:''' From default configuration to Speed Limiting solution in one SMS:

" setparam 2001:APN;2002:APN_user;2003:APN_password;2004:Domain;2005:Port;2006:0;102:3;11100:2;11104:90;13217:0;13223:8;11103:1"
 
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;" |
00000000000000758E010000017CB7A57370000F0E53AE209AB86A007F00110D000000FF0015000800EF0100F00100500100150300C80000450100010000B30100 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;" |00 FF (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
|}
==Demonstration in TAVL platform ==
 TAVL: Open TAVL application → Select Client → Select Device → Select the date interval → Select Track→ Select Advanced → Chose Show button see in left down corner all the information.
 

[[File:Msp500Overspeed.png|alt=|frameless|1000x1000px]]
 

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