Teltonika Telematics Wiki - User contributions [en]

Iridium Edge Communication Protocol

2023-10-05T08:11:16Z

Jayesh:

__TOC__

==Communication Protocol==
{| class="wikitable" style="width:50%;"
|+
! colspan="7" style="width:50%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| SBD Packet structure
|-
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Timestamp
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Longitude
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Latitude
! style="width:15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| SBD AVL ID and flags
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| DIN/DOUT info
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Reserved
! style="width:10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Speed
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 4 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 3 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 3 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 1 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 1 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 1 bytes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 1 bytes
|}

'''Definitions'''

* Timestamp – Indicates when record was generated
* Longitude - encoded in 3 bytes data. Server which gets this data should divide result from 46603,375 and subtract 180 in order to get actual longitude value. This coefficient is got in following way: 16777215(maximum 3 bytes value) divided from 360 (maximum longitude value then 180 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.

*Latitude - Latitude is calculated in same way as longitude but since latitude maximum value is two times smaller than longitude it can produce a bit more accurate data. Coefficient for latitude is 93206,75. This coefficient is got in following way: 16777215(maximum 3 bytes value) divided from 180 (maximum latitude value then 90 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.
*SBD AVL ID and flags – Custom id that will indicate what caused the record to be generated (as only periodic records are generated, id is not used)
*Din/Dout info - Displays configured IO elements in parameter id 99422
*Reserved - Not used anywhere, but left due to compatibility with fm6 project.
*Speed – Indicates the speed of the vehicle if configured. If not (or in case of no gps) – will display 255

==Data Sending Parameters==
Information here includes the data sending parameters which identifies the naming of the parameter in accordance to it's number.
 
{| class="wikitable"
|+
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter ID'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Parameter name'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Min values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Max values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Default values'''
! rowspan="1" style="width: 400px; background: #0054A6; color: white;" |'''Description'''
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |99420
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Iridium Edge
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |This parameter enables or disables Iridium Edge functionality
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |99421
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Save/Send period
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1440
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |1440
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |This parameter lets to configure Iridium Edge sending period
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |99422
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |SBD IO source
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |6
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |SBD IO elements which when enabled are included into the SBD record
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |151
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |RS232 Mode
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |26
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Implement ability to select "Sattelite backup"
|-
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |99423
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |SBD Upload Limit
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |0
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |30000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |8000
| rowspan="1" style="text-align: center; style=" width: 150px; background: white; color: black;" |Limit to save user from exceeding the monthly plan. Max limit of 30000 due to 30KB plan. If set to 0 – limit will be off.
|}
[[Category: Iridium Edge]]

==SBD IO source==
Configures IO source which can trigger SBD record saving. 9 elements can generate Alarm for SDB sending. These elements are:
*Digital input 1
*Digital input 2
*Digital output 1
*Speed
*Crash
 
Configurator parameter IDs and their explanation:
{| class="nd-othertables_2" style="width:100%;"
|- style="font-weight:bold; text-align:center;"
!'''Parameter ID''' 
!'''Parameter name'''
! colspan="3" |'''Values'''
!'''Explanation'''
|- style="font-weight:bold; text-align:center;"
| style="font-weight:normal;" |
| style="font-weight:normal;" |
|'''Min'''
|'''Max'''
|'''Default'''
| style="font-weight:normal;" |
|-
|99420
|Iridium Edge
|0
|1
|0
|This parameter enables or disables Iridium Edge functionality
|-
|99421
|Save/Send period
|0
|1440
|1440
|This parameter lets to configure Iridium Edge sending period
|-
|99422
|SBD IO source'''*'''
|0
|8
|0
|SBD IO elements which when enabled are included into the SBD record
|-
|99423
|SBD UploadLimit
|0
|30000
|8000
|Limit to save user from exceeding the monthly plan. Max limit of 30000 due to 30KB plan. If set to 0 – limit will be off.
|-
|99424
|Power control DOUT
|1
|5
|0
|Device DOUT which can control ON/OFF pin of the Iridium Edge
|-
|151
|RS232 Mode
|0
|23
|0
|RS-232 mode selection. "Satellite backup" - 15
|}
 
In order to configure parameter 99422 manually users must simply set the appropriate values of bit positions, according to their needs:
*Bit1 - DIN 1
*Bit2 - DIN 2
*Bit5 - DOUT 1
*Bit9 - Speed
*Bit10 - Crash

==SDB record structure==
SDB Record which will be sent through the Iridium satellites network will be different than the regular record. It will contain 4 bytes timestamp, 3 bytes longitude, 3 bytes latitude, 1 byte record generation info, 1 byte DIN,DOUT info, 1 byte Speed value.

{| class="nd-othertables_2" style="width:100%;"
|- style="text-align:center"
!Timestamp
!Longitude
!Latitude
!SDB AVL ID and flags
!DIN/DOUT info
!Reserved
!Speed
|- style="font-weight:normal;"
|4B
|3B
|3B
|1B
|1B
|1B
|1B
|}

'''''Timestamp''''' - Indicates when record was generated.
 
'''''Longitude''''' - In this packet is encoded in 3 bytes data. The server that gets this data should divide the result from 46603,375 and subtract 180 to get the actual longitude value. This coefficient is got in the following way: 16777215(maximum 3 bytes value) divided by 360 (maximum longitude value then 180 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.

Example:

Longitude: 910DA0 (in hexadecimal) → 9506208 (in decimal)

To convert Longitude:

(9506208 / 46603,375) - 180 = 23.9811065 
'''''Latitude''''' - Is calculated in the same way as longitude but since latitude maximum value is two times smaller than longitude it can produce a bit more accurate data. The coefficient for latitude is 93206,75. This coefficient is got in the following way: 16777215(maximum 3 bytes value) divided by 180 (maximum latitude value then 90 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.

Example:

Latitude: CE1AEB (in hexadecimal) → 13507307 (in decimal)

To convert Latitude:

(13507307 / 93206.750) - 90 = 54.91769 
'''Din/Dout info''' - Displays configured IO elements in parameter id 99422 (only din/dout). If IO is not set, it will send be replaced by 0.
 
'''Reserved''' - Not used anywhere.
 
'''Speed''' – Indicates the speed (from GNSS) of the vehicle if configured. If not (or in case of no gps) – will display 255.
 
'''''SBD AVL ID and flags''''' – Custom ID that will indicate what caused the record to be generated
This byte is divided in two parts of four bits, as shown in table below:

{| class="nd-othertables_2" style="width:100%;" font-weight:bold; vertical-align:middle;"
! style="font-weight:bold;" | ID
! 0
! 1
! 2
! 24
! 179
! 247
|-
| style="font-weight:bold;" | IO element
| Periodic rec.
| Digital Input 1
| Digital input 2
| Speed
| DOUT1
| Crash
|}
 

==SBD packet example==
'''Unparsed data:'''

''01004C01001CF99DD263333030323334303634303730383330000018000059282DBC03000B0036A2B8193D120000000302001C''
 ''59282BA391F5ABCDBFDD0180000059282BA891F5ABCDBFDD0180000059282BA391F5AB'' 
 
{01} – Protocol revision number 
{00}{4C} – overall message length 
{01} – MO header IEI 
{00}{1C} – MO header length 
{F9}{9D}{D2}{63} – CDR Reference 
{33}{30}{30}{32}{33}{34}{30}{36}{34}{30}{37}{30}{38}{33}{30} – IMEI of the device 
{00} – Session status (Transfer OK in this case) 
{00}{18} – MOMSN 
{00}{00} – MTMSN 
{59}{28}{2D}{BC} – Time of session 
{03} – MO Location information IEI 
''The location values included in this IE provide an estimate of the originating IMEI’s location. The inclusion of this information in an MO message delivery is optional. Whether or not it is included is established when the IMEI is provisioned and may be changed at any time via SPNet. The CEP radius provides the radius around the center point within which the unit is located. While the resolution of the reported position is given to 1/1000th of a minute, it is only accurate to within 10Km 80% of the time. 
{00}{0B} – MO Location information length'' 
{00}{36}{A2}{B8}{19}{3D}{12} – MO latitude and longitude as described in Iridium documentation. 
{00}{00}{00}{03} – CEP radius 
{02} – Payload IEI 
{00}{1C} – Payload length 
{59}{28}{2B}{A3}{91}{F5}{AB}{CD}{BF}{DD}{01}{80}{00}{00} – Record 1 
{59}{28}{2B}{A8}{91}{F5}{AB}{CD}{BF}{DD}{01}{80}{00}{00} – Record 2 

There blue part of record is satellite device generated data and green is actual record payload which was sent to server from {{{device|}}}. Information of the first record should be parsed like this:
 
{59}{28}{2B}{A3} – Timestamp of record generation in GMT0; 
{91}{F5}{AB} – Longitude (recalculated value is 25,255756) 
{CD}{BF}{DD} – Latitude (recalculated value is 54,832396) 
{01} – DIN1 generated event 
{80} – DIN1 on, while DIN2, DOUT1, – off 
{00} – Reserved byte 
{00} – Vehicle was stopped when the record was generated

Template:FMC650 Basic characteristics

2023-06-07T11:31:54Z

Jayesh:

Cellular:
{| class="wikitable"
|style="background: #0054A6; color:white" |'''Technology'''
|style="background: #0054A6; color:white" |'''Supported bands'''
|-
| rowspan="2" |2G bands (SLM320)
|SLM320-PE2C: B2/B3/B5/B8
|-
|SLM320-L16A: B2/B3/B5/B8
|-
| rowspan="2" |4G bands (SLM320)
|SLM320-PE2C:
LTE-FDD:B1/B3/B7/B8/B20/B28 
LTE-TDD:B38/B40/B41
|-
|SLM320-L16A:
LTE-FDD:B1/B2/B3/B4/B5/B7/B8/B20/B28 
LTE-TDD:B40
|-
| rowspan="3" |Data transfer
|LTE FDD: Max 10Mbps (DL)/Max 5Mbps (UL) LTE TDD
|-
|Max 8Mbps (DL)/Max 2Mbps (UL)
GPRS: Max 85.6Kbps (DL)/Max 85.6Kbps (UL)
|-
|}



GNSS features:
*module name: Airoha AG3335MB
* L1 and L5 dual-band GNSS receiver
* -165 dBM sensitivity
* Hot start <1s
* Warm Start < 25s
* Cold start < 35s
* GPS, GLONASS, GALILEO, BEIDOU, SBAS, QZSS
* Accuracy < 2,5 CEP

Template:FMX125 RS232/485

2023-04-04T05:53:29Z

Jayesh:

==RS-232 / RS-485 modes==
Available modes for RS-232 and RS-485 interfaces:

{| class="wikitable" style="text-align:center; background-color:#ffffff;"
|- style="text-align:left;"
! rowspan="2" style="text-align:center; vertical-align:middle; font-weight:bold; background: #0054A6; color: white;" | Interface
! colspan="16" style="text-align:center; background: #0054A6; color: white;" | Mode
|-
| Log Mode
| NMEA
| LLS
| LCD
| RFID HID
| RFID MF7
| Garmin FMI
| TCP/UDP Ascii
| TCP/UDP Binary
| TCP/UDP Ascii Buffered
| TCP/UDP Binary Buffered
| Mercury C4
| ULF202 Fuel Sensor
|[[Teltonika DualCam|DualCam]]
|[[Teltonika ADAS|ADAS]]
| Delimiter
|-
| style="vertical-align:middle;" | RS-232
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| style="vertical-align:middle;" | RS-485
| ✔
| ✔
| ✔
|
|
|
|
| ✔
| ✔
| ✔1
| ✔1
|
|
|
|
|
|}
1 – available from FW version 03.28.XX.
 
{|
|[[File:Alert.png|left|link=|50px]]||Swapping RS485 A and B lines(or RS232 Tx and Rx) of the external device and also not connecting ground together - May cause irreparable damage.
|}
 
====Log mode====
In this mode via RS-232 or RS-485 interface prints the {{{model|FMX125}}} device log and does not respond to commands. 

====GNSS NMEA mode====
In NMEA mode via RS-232 or RS-485 interface {{{model|FMX125}}} prints GNSS NMEA log and does not respond to commands. 

====LLS mode====
In LLS mode RS-232 supports one and RS-485 supports up to five LLS sensors - each of which has a receiver ID. 
Up to 16 LLS sensors are supported with 03.28.XX firmware version.
Up to 8 passenger counter sensors "PP-01" can be connected each requiring 2 LLS addresses. The passenger counter sensor "PP-01" provides the possibility to count passengers getting either on or off public transport (bus, trolleybus, etc.).

====TCP (ASCII/Binary) modes====

In ''TCP Ascii/Binary'' mode all data received from the external device is sent directly to the server. Data is encapsulated in codec 12 format. ''TCP Binary'' Mode has a delay of 30 ms, if no data is received for 30 ms, data is sent to the server. ''TCP Ascii'' mode waits for the End of Line (EOL) character (0x0D0A, \r\n, <CR><LF>) to pack data and send it to the server.

''TCP Ascii Buffered'' and ''TCP Binary Buffered'' modes are used to collect data from RS232 and save it in the buffer if there is no link with the server and data cannot be sent immediately. When the link is established and there is data to transmit, then RS232 data from the buffer is transmitted after all records are sent. Data is sent in codec 13 protocol. Note. That in ''TCP Ascii'' and ''TCP Binary'' modes device sends data from the external device only to the main server. In Buffered modes – to both main and backup/duplicate servers.

{| class="nd-othertables_2" style="width:100%;"
|-
!
! TCP Binary/TCP ASCII mode
! TCP Binary/TCP ASCII Buffered mode
|-
| '''Data is saved in buffer'''
| No
| Yes
|-
| '''Data sending protocol'''
| Codec 12
| Codec 13*
|-
| '''Timestamp'''
| Not using
| Is using*
|-
| '''To which server is sent'''
| Main
| Main and backup
|}
''*If the Timestamp parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.''
 

Short video explaining TCP binary mode:
[[File:TCP Binary vid.mp4|1080px|none]]
 
Short video explaining TCP Ascii mode:
[[File:TCP ASCII vid.mp4|1080px|none]]

=====TCP Binary settings=====
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2, or Prefix 3. These prefixes can be used separately or in unison.
To configure this setting a value from 0 to 255 in decimal has to be entered. The device will convert this value to HEX and compare the 1st, 2nd, or 3rd byte from incoming data. If the values do not match, the device will not accept incoming data.

Video explaining TCP Binary settings: 
[[File:TCP Binary prefixes.mp4|1080px|none]]

=====Message Timestamp=====
[[File:Timestamp.gif|right]] Message Timestamp parameter is used to determine if it is necessary to include timestamp in RS-232 TCP packet when sending to server. If parameter is Enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.

=====Codec 12/13 Packet Merge=====
This additional option configures the device to merge RS-232 records into a single packet instead of sending many separate packets.[[File:MERGE.gif|right]] This functionality only affects '''TCP Binary Buffered''' or '''TCP Ascii Buffered''' RS232 modes.

When enabled, the device will merge saved RS-232 records together into a single data packet until it is able to send it to the server.
This optimizes RS-232 data sending by not having to send each RS-232 record separately. If the amount of saved RS-232 data exceeds the maximum 4 bytes of data in one Codec 12 packet, the device will start saving incoming RS-232 data into a new record.

===== RS-232 / RS-485 CMD ID=====
This parameter is used when {{{model|}}} is sending RS232/RS485 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). {{{model|}}} behavior when it receives different CMD ID (Type) values in GPRS packet from server.
[[File:CMD.gif|right]]

When {{{model|}}} receives these CMD ID values in the GPRS packet it behaves accordingly:

{| class="wikitable" style="width:70%;"
|+
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | CMD ID
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Functionality
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Parse Codec12/Codec14 packet from the server
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |7
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet meant for Garmin system
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |14
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to external device via uart using RS232/RS485
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |16
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to paired Bluetooth device
|-
|}
 

==RS-232 Modes==

====RS-232 LCD mode====
In this mode, the user is able to communicate with the server through the terminal. A link between the FMB device and the server has to be established for this mode to function properly.

To communicate from terminal to server - in terminal send command - <code>WT^W <text></code>

To communicate with the server to the terminal send command - <code>#DO DAT= <text></code> packet in [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols#Codec_12 Codec12 protocol]

====RS-232 RFID HID/RFID MF7 mode====
The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode {{{model|}}} understands RFID messages that are in hexadecimal text format and RFID HID Mode interprets messages that are in binary format. The type of RFID message sent to {{{model|}}} depends on the RFID reader. For example, the RFID MF7 mode message looks like <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code>

The selected mode has to correspond to the RFID reader's mode.
Please contact your local sales representative for more information about RFID IDs and devices.

====RS-232 Garmin mode====
Garmin provides a Fleet Management Interface Tool Kit, once {{{model|}}} is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging and offers job dispatch capabilities to help them be more efficient. {{{model|}}} and Garmin operational diagram is shown on the figure below.
[[Image:FMX125_GARMIN_BLOCK.png|900px|none]]

====RS-232 Delimiter mode====
* This feature works from '''Ver.03.28.05.Rev.00+''' with Codec 8 Extended enabled. 
'''Delimiter mode''' have two configurable delimiters to mark start and end of packet received from external device. Delimiter is configured as HEX string, max length 3 Bytes.

''Examples:''
START delimiter param ‘3C’ and END delimiter param: ‘3E’ (3C = ASCII ‘<’ and 3E = ASCII ‘>’), '''<''' payload '''>''' (in ASCII) where ‘<’ and ‘>’ are the start and end delimiter
START delimiter param: ‘02’ and END delimiter param: ‘0A 0D 03’,
'''0x02''' 0xFF 0xFF 0xFF 0xFF '''0x0A 0x0D 0x03''' (hexadecimal) where ‘0x02’ and ‘0x0A 0x0D 0x03’ is a delimiter

''Note: If payload is empty. Record will be generated with empty payload.''

{| class="wikitable"
|- style="font-size:14px; background-color:#9CF;"
! Name
! ID
! Min symbols
! Max symbols
! Description
|- style="font-size:14px;"
| Start delimiter
| 167
| rowspan="2" style="text-align:center;" | 0 (empty)
| rowspan="2" style="text-align:center;" | 6 (3 bytes)
| rowspan="2" | Dynamic HEX string value from 0 symbols (not configured) to 6 symbols (delimiter 3 bytes). Configured value have to be even number of symbols
|-
| style="font-size:14px;" | End delimiter
| style="font-size:14px;" | 168
|}
<div style="text-align: center;">Table 1. START and END delimiters are configurable via SMS/GPRS Configurator</div>

{| class="wikitable" style="width:100%;"
|- style="font-size:15px; background-color:#9CF;"
! Start delimiter
! End delimiter
! Description
|- style="font-size:15px;"
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:15px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:15px;"
| style="font-size:14px;" | 1 second of silence in the line is counted as the end of the packet.
|- style="font-size:15px;"
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| rowspan="4" style="background-color:#CFC;" | Configured
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:15px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:15px;"
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| style="font-size:14px;" | After record was generated by detected end delimiter, FMB will start collect data for next record right away.
|- style="font-size:15px;"
| rowspan="5" style="background-color:#CFC;" | Configured
| rowspan="5" style="background-color:#C0C0C0;" | Empty
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:12px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:12px;"
| style="font-size:14px;" | Data before Start delimiter will be discarded.
|-
| style="font-size:14px;" | 1 second of silence in the line is counted as the end of the packet.
|-
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| rowspan="4" style="background-color:#CFC;" | Configured
| rowspan="4" style="background-color:#CFC;" | Configured
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|-
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|-
| style="font-size:14px;" | Data before Start delimiter will be discarded.
|-
| style="font-size:14px;" | After record was generated by detected end delimiter, FMB will start searching for next payload in received packet right away.
|}

<div style="text-align: center;">Table 2. Functionality description by delimiter configuration</div>
'''Baudrate and parity configurable in base functionality'''
* New IO element '''Serial Packet''' ID:109:
When '''Delimiter mode''' is selected and packet is received via RS232 FMB will save record with added '''Serial Packet''' IO element with HIGH priority. If any other mode than

'''Delimiter''' is selected “Serial Packet” IO element will not be saved in records;

'''Serial Packet''' length will be variable, max length 257 bytes;

While no '''Serial Packet''' is received from external device FMB will save other periodic or eventual records without '''Serial Packet''' IO element.

{| class="wikitable" style="text-align:center; font-size:15px;"
|- style="background-color:#9CF;"
! colspan="11" | Record with Serial Packet
|-
| rowspan="2" | Preamble 4 bytes
| AVL Data length
| Timestamp
| GPS element
| Event ID,
| IOs,
| IO[109],
| rowspan="2" | Index, 1 Byte
| rowspan="2" | Data Length, 1 Byte
| rowspan="2" | Payload, 255 Bytes
| CRC
|-
| 4 Bytes
| 8 Bytes
| 15 Bytes
| 2 Bytes
| X Bytes
| 2 Byte
| 4 Bytes
|}

<div style="text-align: center;">Table 3. Example of serial packet with Codec8 Extended Protocol</div>

'''Index:''' Indicates the number of generated payload. Starting from 0 index.

'''Data Length:''' Length of payload.

'''Payload:''' Data parsed by delimiter functionality.

'''Note:''' Delimiter IO element is string type. Each type of IO elements has identifier byte that identify how many IOs of that type stored in record.

'''IO Types:'''
* 1byte IO elements
* 2 bytes IO elements
* 4 bytes IO elements
* 8 bytes IO elements
* String IO elements

{| class="wikitable" style="width:100%;"
|-
! style="background-color:#efefef;" | Event ID
! 109 (delimiter)
|-
| style="background-color:#efefef;" | Total IO count
| All configured + 1 (delimiter)
|-
| style="background-color:#efefef;" | 1 byte IO’s count
| All configured 1 byte IO’s count
|-
| style="background-color:#efefef;" | 1 byte IOs
| All configured 1 byte IOs
|-
| style="background-color:#efefef;" | 2 bytes IO’s count
| All configured 2 bytes IO’s count
|-
| style="background-color:#efefef;" | 2 bytes IOs
| All configured 2 bytes IOs
|-
| style="background-color:#efefef;" | 4 bytes IO’s count
| All configured 4 bytes IO’s count
|-
| style="background-color:#efefef;" | 4 bytes IOs
| All configured 4 bytes IOs
|-
| style="background-color:#efefef;" | 8 bytes IO’s count
| All configured 8 bytes IO’s count
|-
| style="background-color:#efefef;" | 8 bytes IOs
| All configured 8 bytes IOs
|- style="background-color:#efefef;"
| String type IO’s count
| style="background-color:#FF9;" | All string type IO’s count
|-
| style="background-color:#efefef;" | String type IOs
| ID, index, length, serial packet
|-
| style="background-color:#efefef;" | …
| …
|}

<div style="text-align: center;">Table 4. Record structure</div>

 

String type IO count byte will be added to the record only if record was generated with event ID equal to serial packet. Regular records that were generated not by Serial Packet will NOT have string type IO count identifier byte.

===== Configurable parameters =====

------------------

[[File:RS232 delimiter.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''New RS232 mode '''Delimiter'''''</div>
 

[[File:RS232 delimiter startstop.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''Start and Stop Delimeter for new RS232 mode '''Delimiter''' value in HEX''</div>
 

 
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of {{{model|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.

'''Standard protocols'''
------------------
Text Message Protocol:

*Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
*Garmin can provide a confirmation that message was read;
*Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
*Messages can be up to 199 characters long;
*Messages can also be generated from the device and sent to dispatcher/office;
*Messages received will be notified to the driver through a pop-up alert on the Garmin screen;
*Garmin provides a "virtual keyboard" for text communication.

Stop (Destination) Protocol:

* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";
*Driver has the ability to navigate directly to Stop from the list;
* Garmin can provide status of a current Stop in progress;
*Garmin can indicate whether the driver has stopped at the location;
*Garmin can inform how far the driver has progressed through the list of Stops;
*Garmin can provide confirmation that the driver has received a particular Stop, familiarized himself/herself with its details, or removed it from the list;
*Can provide confirmation that a Stop has been reached.

Estimated Time of Arrival Protocol:

*Dispatcher/office can request the ETA of the current Stop/job in progress;
*Garmin can notify about the actual time of arrival as well as the distance remaining to a Stop.

Auto-Arrival at Stop Protocol:

*This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if he/she would like to mark the Stop as done and begin navigating to a next Stop on the list;
*Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated.

Data Deletion Protocol:

* Dispatcher/office has the ability to wipe clean the data on Garmin PND;
*It allows to clean messages in the inbox and remove stops.

'''Enhanced protocols'''
------------------
Canned Responses/Messages:

*Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
*Up to 50 of these canned responses can be utilized for any given scenario;
*Drivers can store up to 120 canned messages, eliminating the need to type while driving.

Status Protocol:

*Up-to-the-minute communications that allow drivers to automatically send status updates;
*Driver's units can store up to 16 status indicators such as start/stop shift, on/off break, etc.

'''Supported features on TAVL client application'''
------------------
TAVL client application lets users use the following features of Garmin FMI:

*Text messaging;
*Destination message;
*ETA request.
'''
'''Text messaging'''
------------------
The text messaging feature lets the user communicate with the driver (the user that operates the Garmin device) by sending text messages via GPRS.

'''Destination message'''
------------------
Destination message is used to inform the driver of a new destination. When the Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver the ability to start navigating to the Stop location. A new destination in the TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

'''ETA request message'''
------------------
''Estimated Time of Arrival'' request message is used when the user wants to know an expected arrival time to the currently active destination and the distance (in meters) from the current object location to the destination.

Template:FMX125 RS232/485

2023-04-03T10:35:22Z

Jayesh:

==RS-232 / RS-485 modes==
Available modes for RS-232 and RS-485 interfaces:

{| class="wikitable" style="text-align:center; background-color:#ffffff;"
|- style="text-align:left;"
! rowspan="2" style="text-align:center; vertical-align:middle; font-weight:bold; background: #0054A6; color: white;" | Interface
! colspan="16" style="text-align:center; background: #0054A6; color: white;" | Mode
|-
| Log Mode
| NMEA
| LLS
| LCD
| RFID HID
| RFID MF7
| Garmin FMI
| TCP/UDP Ascii
| TCP/UDP Binary
| TCP/UDP Ascii Buffered
| TCP/UDP Binary Buffered
| Mercury C4
| ULF202 Fuel Sensor
|[[Teltonika DualCam|DualCam]]
|[[Teltonika ADAS|ADAS]]
| Delimiter
|-
| style="vertical-align:middle;" | RS-232
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
| ✔
|-
| style="vertical-align:middle;" | RS-485
| ✔
| ✔
| ✔
|
|
|
|
| ✔
| ✔
| ✔1
| ✔1
|
|
|
|
|
|}
1 – available from FW version 03.28.XX.
[[File:Alert.png|50px|left|link=]]</td><td>Do not swap RS232/485 A and B lines while connecting to devices.</td></table>
 
====Log mode====
In this mode via RS-232 or RS-485 interface prints the {{{model|FMX125}}} device log and does not respond to commands. 

====GNSS NMEA mode====
In NMEA mode via RS-232 or RS-485 interface {{{model|FMX125}}} prints GNSS NMEA log and does not respond to commands. 

====LLS mode====
In LLS mode RS-232 supports one and RS-485 supports up to five LLS sensors - each of which has a receiver ID. 
Up to 16 LLS sensors are supported with 03.28.XX firmware version.
Up to 8 passenger counter sensors "PP-01" can be connected each requiring 2 LLS addresses. The passenger counter sensor "PP-01" provides the possibility to count passengers getting either on or off public transport (bus, trolleybus, etc.).

====TCP (ASCII/Binary) modes====

In ''TCP Ascii/Binary'' mode all data received from the external device is sent directly to the server. Data is encapsulated in codec 12 format. ''TCP Binary'' Mode has a delay of 30 ms, if no data is received for 30 ms, data is sent to the server. ''TCP Ascii'' mode waits for the End of Line (EOL) character (0x0D0A, \r\n, <CR><LF>) to pack data and send it to the server.

''TCP Ascii Buffered'' and ''TCP Binary Buffered'' modes are used to collect data from RS232 and save it in the buffer if there is no link with the server and data cannot be sent immediately. When the link is established and there is data to transmit, then RS232 data from the buffer is transmitted after all records are sent. Data is sent in codec 13 protocol. Note. That in ''TCP Ascii'' and ''TCP Binary'' modes device sends data from the external device only to the main server. In Buffered modes – to both main and backup/duplicate servers.

{| class="nd-othertables_2" style="width:100%;"
|-
!
! TCP Binary/TCP ASCII mode
! TCP Binary/TCP ASCII Buffered mode
|-
| '''Data is saved in buffer'''
| No
| Yes
|-
| '''Data sending protocol'''
| Codec 12
| Codec 13*
|-
| '''Timestamp'''
| Not using
| Is using*
|-
| '''To which server is sent'''
| Main
| Main and backup
|}
''*If the Timestamp parameter is enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.''
 

Short video explaining TCP binary mode:
[[File:TCP Binary vid.mp4|1080px|none]]
 
Short video explaining TCP Ascii mode:
[[File:TCP ASCII vid.mp4|1080px|none]]

=====TCP Binary settings=====
TCP Binary has a setting Prefix. It is possible to set Prefix 1, Prefix 2, or Prefix 3. These prefixes can be used separately or in unison.
To configure this setting a value from 0 to 255 in decimal has to be entered. The device will convert this value to HEX and compare the 1st, 2nd, or 3rd byte from incoming data. If the values do not match, the device will not accept incoming data.

Video explaining TCP Binary settings: 
[[File:TCP Binary prefixes.mp4|1080px|none]]

=====Message Timestamp=====
[[File:Timestamp.gif|right]] Message Timestamp parameter is used to determine if it is necessary to include timestamp in RS-232 TCP packet when sending to server. If parameter is Enabled, then Codec 13 is used for data sending. Otherwise, Codec 12 is used.

=====Codec 12/13 Packet Merge=====
This additional option configures the device to merge RS-232 records into a single packet instead of sending many separate packets.[[File:MERGE.gif|right]] This functionality only affects '''TCP Binary Buffered''' or '''TCP Ascii Buffered''' RS232 modes.

When enabled, the device will merge saved RS-232 records together into a single data packet until it is able to send it to the server.
This optimizes RS-232 data sending by not having to send each RS-232 record separately. If the amount of saved RS-232 data exceeds the maximum 4 bytes of data in one Codec 12 packet, the device will start saving incoming RS-232 data into a new record.

===== RS-232 / RS-485 CMD ID=====
This parameter is used when {{{model|}}} is sending RS232/RS485 packet to a server, it overrides command type value in Codec12/Codec13 with user defined CMD ID value (1 - 14). {{{model|}}} behavior when it receives different CMD ID (Type) values in GPRS packet from server.
[[File:CMD.gif|right]]

When {{{model|}}} receives these CMD ID values in the GPRS packet it behaves accordingly:

{| class="wikitable" style="width:70%;"
|+
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | CMD ID
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Functionality
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Parse Codec12/Codec14 packet from the server
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |7
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet meant for Garmin system
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |14
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to external device via uart using RS232/RS485
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |16
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |Forward packet to paired Bluetooth device
|-
|}
 

==RS-232 Modes==

====RS-232 LCD mode====
In this mode, the user is able to communicate with the server through the terminal. A link between the FMB device and the server has to be established for this mode to function properly.

To communicate from terminal to server - in terminal send command - <code>WT^W <text></code>

To communicate with the server to the terminal send command - <code>#DO DAT= <text></code> packet in [https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols#Codec_12 Codec12 protocol]

====RS-232 RFID HID/RFID MF7 mode====
The difference between RFID HID Mode and RFID MF7 Mode is that in RFID MF7 Mode {{{model|}}} understands RFID messages that are in hexadecimal text format and RFID HID Mode interprets messages that are in binary format. The type of RFID message sent to {{{model|}}} depends on the RFID reader. For example, the RFID MF7 mode message looks like <code>$aa$02$03$04$17$89$00$01</code> while HID mode message is of the following format: <code>1213141519</code>

The selected mode has to correspond to the RFID reader's mode.
Please contact your local sales representative for more information about RFID IDs and devices.

====RS-232 Garmin mode====
Garmin provides a Fleet Management Interface Tool Kit, once {{{model|}}} is connected to the navigator it enables the driver to have a "screen" in their vehicle for real-time navigation and messaging and offers job dispatch capabilities to help them be more efficient. {{{model|}}} and Garmin operational diagram is shown on the figure below.
[[Image:FMX125_GARMIN_BLOCK.png|900px|none]]

====RS-232 Delimiter mode====
* This feature works from '''Ver.03.28.05.Rev.00+''' with Codec 8 Extended enabled. 
'''Delimiter mode''' have two configurable delimiters to mark start and end of packet received from external device. Delimiter is configured as HEX string, max length 3 Bytes.

''Examples:''
START delimiter param ‘3C’ and END delimiter param: ‘3E’ (3C = ASCII ‘<’ and 3E = ASCII ‘>’), '''<''' payload '''>''' (in ASCII) where ‘<’ and ‘>’ are the start and end delimiter
START delimiter param: ‘02’ and END delimiter param: ‘0A 0D 03’,
'''0x02''' 0xFF 0xFF 0xFF 0xFF '''0x0A 0x0D 0x03''' (hexadecimal) where ‘0x02’ and ‘0x0A 0x0D 0x03’ is a delimiter

''Note: If payload is empty. Record will be generated with empty payload.''

{| class="wikitable"
|- style="font-size:14px; background-color:#9CF;"
! Name
! ID
! Min symbols
! Max symbols
! Description
|- style="font-size:14px;"
| Start delimiter
| 167
| rowspan="2" style="text-align:center;" | 0 (empty)
| rowspan="2" style="text-align:center;" | 6 (3 bytes)
| rowspan="2" | Dynamic HEX string value from 0 symbols (not configured) to 6 symbols (delimiter 3 bytes). Configured value have to be even number of symbols
|-
| style="font-size:14px;" | End delimiter
| style="font-size:14px;" | 168
|}
<div style="text-align: center;">Table 1. START and END delimiters are configurable via SMS/GPRS Configurator</div>

{| class="wikitable" style="width:100%;"
|- style="font-size:15px; background-color:#9CF;"
! Start delimiter
! End delimiter
! Description
|- style="font-size:15px;"
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:15px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:15px;"
| style="font-size:14px;" | 1 second of silence in the line is counted as the end of the packet.
|- style="font-size:15px;"
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| rowspan="4" style="background-color:#C0C0C0;" | Empty
| rowspan="4" style="background-color:#CFC;" | Configured
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:15px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:15px;"
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| style="font-size:14px;" | After record was generated by detected end delimiter, FMB will start collect data for next record right away.
|- style="font-size:15px;"
| rowspan="5" style="background-color:#CFC;" | Configured
| rowspan="5" style="background-color:#C0C0C0;" | Empty
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|- style="font-size:12px;"
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|- style="font-size:12px;"
| style="font-size:14px;" | Data before Start delimiter will be discarded.
|-
| style="font-size:14px;" | 1 second of silence in the line is counted as the end of the packet.
|-
| style="font-size:14px;" | After end detected FMB will generated record with collected data.
|- style="font-size:15px;"
| rowspan="4" style="background-color:#CFC;" | Configured
| rowspan="4" style="background-color:#CFC;" | Configured
| style="font-size:14px;" | Packet received from RS232 will be saved to record. If payload is bigger than 254 bytes it will be separated to 2 or more records.
|-
| style="font-size:14px;" | Each record will be saved with incremented index starting from 0 index.
|-
| style="font-size:14px;" | Data before Start delimiter will be discarded.
|-
| style="font-size:14px;" | After record was generated by detected end delimiter, FMB will start searching for next payload in received packet right away.
|}

<div style="text-align: center;">Table 2. Functionality description by delimiter configuration</div>
'''Baudrate and parity configurable in base functionality'''
* New IO element '''Serial Packet''' ID:109:
When '''Delimiter mode''' is selected and packet is received via RS232 FMB will save record with added '''Serial Packet''' IO element with HIGH priority. If any other mode than

'''Delimiter''' is selected “Serial Packet” IO element will not be saved in records;

'''Serial Packet''' length will be variable, max length 257 bytes;

While no '''Serial Packet''' is received from external device FMB will save other periodic or eventual records without '''Serial Packet''' IO element.

{| class="wikitable" style="text-align:center; font-size:15px;"
|- style="background-color:#9CF;"
! colspan="11" | Record with Serial Packet
|-
| rowspan="2" | Preamble 4 bytes
| AVL Data length
| Timestamp
| GPS element
| Event ID,
| IOs,
| IO[109],
| rowspan="2" | Index, 1 Byte
| rowspan="2" | Data Length, 1 Byte
| rowspan="2" | Payload, 255 Bytes
| CRC
|-
| 4 Bytes
| 8 Bytes
| 15 Bytes
| 2 Bytes
| X Bytes
| 2 Byte
| 4 Bytes
|}

<div style="text-align: center;">Table 3. Example of serial packet with Codec8 Extended Protocol</div>

'''Index:''' Indicates the number of generated payload. Starting from 0 index.

'''Data Length:''' Length of payload.

'''Payload:''' Data parsed by delimiter functionality.

'''Note:''' Delimiter IO element is string type. Each type of IO elements has identifier byte that identify how many IOs of that type stored in record.

'''IO Types:'''
* 1byte IO elements
* 2 bytes IO elements
* 4 bytes IO elements
* 8 bytes IO elements
* String IO elements

{| class="wikitable" style="width:100%;"
|-
! style="background-color:#efefef;" | Event ID
! 109 (delimiter)
|-
| style="background-color:#efefef;" | Total IO count
| All configured + 1 (delimiter)
|-
| style="background-color:#efefef;" | 1 byte IO’s count
| All configured 1 byte IO’s count
|-
| style="background-color:#efefef;" | 1 byte IOs
| All configured 1 byte IOs
|-
| style="background-color:#efefef;" | 2 bytes IO’s count
| All configured 2 bytes IO’s count
|-
| style="background-color:#efefef;" | 2 bytes IOs
| All configured 2 bytes IOs
|-
| style="background-color:#efefef;" | 4 bytes IO’s count
| All configured 4 bytes IO’s count
|-
| style="background-color:#efefef;" | 4 bytes IOs
| All configured 4 bytes IOs
|-
| style="background-color:#efefef;" | 8 bytes IO’s count
| All configured 8 bytes IO’s count
|-
| style="background-color:#efefef;" | 8 bytes IOs
| All configured 8 bytes IOs
|- style="background-color:#efefef;"
| String type IO’s count
| style="background-color:#FF9;" | All string type IO’s count
|-
| style="background-color:#efefef;" | String type IOs
| ID, index, length, serial packet
|-
| style="background-color:#efefef;" | …
| …
|}

<div style="text-align: center;">Table 4. Record structure</div>

 

String type IO count byte will be added to the record only if record was generated with event ID equal to serial packet. Regular records that were generated not by Serial Packet will NOT have string type IO count identifier byte.

===== Configurable parameters =====

------------------

[[File:RS232 delimiter.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''New RS232 mode '''Delimiter'''''</div>
 

[[File:RS232 delimiter startstop.jpg|alt=|thumb|center|934x425px]]
<div style="text-align: center;">''Start and Stop Delimeter for new RS232 mode '''Delimiter''' value in HEX''</div>
 

 
==Garmin protocols==
The following is a list of protocols supported and the corresponding list of features/benefits. {{{model|FMB125}}} can fully support Fleet Management Interface (FMI) versions up to 2.1. Other or higher versions may be supported, but Teltonika is not responsible for the changes made by Garmin, which may affect the function of {{{model|FMB125}}} and Garmin products. For more information about Garmin products and FMI versions, please refer to https://www.garmin.com/en-US/fleet-ready-navigators/. Notice that some Garmin products use different connection cables than others.

'''Standard protocols'''
------------------
Text Message Protocol:

*Allows text messages sent to the device to be displayed in "inbox" on navigation unit;
*Garmin can provide a confirmation that message was read;
*Garmin can also provide a yes/no box below the text of the message to enable a quicker response;
*Messages can be up to 199 characters long;
*Messages can also be generated from the device and sent to dispatcher/office;
*Messages received will be notified to the driver through a pop-up alert on the Garmin screen;
*Garmin provides a "virtual keyboard" for text communication.

Stop (Destination) Protocol:

* Garmin can display a list of Stops/Jobs reported to the device in a separate category called "My Stops";
*Driver has the ability to navigate directly to Stop from the list;
* Garmin can provide status of a current Stop in progress;
*Garmin can indicate whether the driver has stopped at the location;
*Garmin can inform how far the driver has progressed through the list of Stops;
*Garmin can provide confirmation that the driver has received a particular Stop, familiarized himself/herself with its details, or removed it from the list;
*Can provide confirmation that a Stop has been reached.

Estimated Time of Arrival Protocol:

*Dispatcher/office can request the ETA of the current Stop/job in progress;
*Garmin can notify about the actual time of arrival as well as the distance remaining to a Stop.

Auto-Arrival at Stop Protocol:

*This feature is used to tell Garmin PND to automatically detect that it has arrived at a Stop and then to prompt the driver if he/she would like to mark the Stop as done and begin navigating to a next Stop on the list;
*Auto-arrival can be determined by how long the unit is stopped close to the destination (in the case driver has to park and walk) or by how close the unit needs to be to the destination before the Auto-arrival feature is activated.

Data Deletion Protocol:

* Dispatcher/office has the ability to wipe clean the data on Garmin PND;
*It allows to clean messages in the inbox and remove stops.

'''Enhanced protocols'''
------------------
Canned Responses/Messages:

*Fleet managers can communicate by sending up to 200 "canned" responses from the server to be stored directly on Garmin devices;
*Up to 50 of these canned responses can be utilized for any given scenario;
*Drivers can store up to 120 canned messages, eliminating the need to type while driving.

Status Protocol:

*Up-to-the-minute communications that allow drivers to automatically send status updates;
*Driver's units can store up to 16 status indicators such as start/stop shift, on/off break, etc.

'''Supported features on TAVL client application'''
------------------
TAVL client application lets users use the following features of Garmin FMI:

*Text messaging;
*Destination message;
*ETA request.
'''
'''Text messaging'''
------------------
The text messaging feature lets the user communicate with the driver (the user that operates the Garmin device) by sending text messages via GPRS.

'''Destination message'''
------------------
Destination message is used to inform the driver of a new destination. When the Garmin device receives a destination message from the server it displays it as a Stop to the driver and also gives the driver the ability to start navigating to the Stop location. A new destination in the TAVL client is represented as a Geozone so a new Geozone (as destination) has to be created first.

'''ETA request message'''
------------------
''Estimated Time of Arrival'' request message is used when the user wants to know an expected arrival time to the currently active destination and the distance (in meters) from the current object location to the destination.

Iridium Edge Firmware errata

2023-01-24T12:49:17Z

Jayesh:

__TOC__

==Firmware errata==

===Firmware errata for FMX125===

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.104'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Added SBD message buffer limit of 300 messages
*Fixed part of SBD records that were of empty size
*Added NBLMULT callstack and abnormal restarts
*Fixed FS spam on iridium initialization
*Fixed incorrect timestamp from SBD Buffer
*Added ability to use SBD buffer in transmitting FSM
*Added ability to generate sbd_records with AVL id
*Added ability to read messages from SBD Buffer
*Added ability to save messages to SBD Buffer
*Fixed iridium not detecting GSM connection
*Fixed iridium communication issues
*Fixed incorret data usege calculation
*Fixed callstacks if iridium disconnected
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.100'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-06-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added data usage limit for sending via Iridium
* Added Iridium data sending logic
* Added Iridium FSM for parsing iridium edge terminal messages
* Added Irdium RS232 support
* Added SBD Record format
* Added implementation of configuration parameters for Iridium Edge control
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-03-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed Lipo battery max voltage limit increased
* Fixed no SMS response to short number
* Fixed parameter 11712 cannot be configured with value 10
* Added cpureset command to only work with external power
* Added iButton file open/close traces
* Fixed FMP100 LED constantly on after fw update
* Added road sign CAN elements
* Fixed security states P2 bitfield map fix
* Fixed Jamming records saved as low priority
* Fixed Fluid Market GGPS command
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.03.Rev.01'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-09-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}

===Firmware errata for FMX640/641===
{| class="wikitable" style="width: 100%;"
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.24.Rev.00''' (Latest firmware release version for {{{model|FMX640}}})
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Improvements for manufacturing process. (No any functionality improvements made)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.18.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-12-23
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added advanced BLE Advertisement data are not send on server completely.
* Fixed no ID [1077]: 4 event generated after "Time TO Clear ID" timer ran out.
* Fixed event ID [1077]: 4 generation and DOUT setting to '1' on key clear timer exparation code added.
* Fixed FMB640 DOUTs bug fix, when DOUTs turns on for a moment after startup.
* Fixed CAN2 bus normal mode is not working.
* Added no BT changes and version/mod fix.
* Fixed after DriverAuthorization device does not send SMS bug fix.
* Added Contipressure new parameters.
* Fixed device reset after configuration saving
* Added Iridium Edge support Fixed AVL unnecessary records after restart.
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.17.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed FMC640 Improve gprs context opening.
* Fixed FMC640 Improve new gprs configuration for BG96.
* Added LVCAN adapter compatibility over RS232 functionality.
* Fixed periodic AVL packet sending (when connecting to DDD server).
* Fixed RS232 Buffered long message when SD storage is used
* Added periodic total odometer value save (if moving).
* Added total odometer value save (on stop).
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.16.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added allow not available (3,7) value for tachoraph driver.id IO.
* Fixed scenarios are saving records even if not enabled
* Fixed unstable additional beacons
* Fixed FMC64 stability (try socket connection once)
* Fixed jamming detection for FMC64 devices
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.15.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-04-15
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}
[[Category: Iridium Edge]]

Iridium Edge Firmware errata

2023-01-24T12:44:20Z

Jayesh:

__TOC__

==Firmware errata==

===Firmware errata for FMX125===

{| class="wikitable" style="width: 100%;"
|+
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.104'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Added SBD message buffer limit of 300 messages
*Fixed part of SBD records that were of empty size
*Added NBLMULT callstack and abnormal restarts
*Fixed FS spam on iridium initialization
*Fixed incorrect timestamp from SBD Buffer
*Added ability to use SBD buffer in transmitting FSM
*Added ability to generate sbd_records with AVL id
*Added ability to read messages from SBD Buffer
*Added ability to save messages to SBD Buffer
*Fixed iridium not detecting GSM connection
*Fixed iridium communication issues
*Fixed incorret data usege calculation
*Fixed callstacks if iridium disconnected
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.100'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-06-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added data usage limit for sending via Iridium
* Added Iridium data sending logic
* Added Iridium FSM for parsing iridium edge terminal messages
* Added Irdium RS232 support
* Added SBD Record format
* Added implementation of configuration parameters for Iridium Edge control
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.04.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-03-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed Lipo battery max voltage limit increased
* Fixed no SMS response to short number
* Fixed parameter 11712 cannot be configured with value 10
* Added cpureset command to only work with external power
* Added iButton file open/close traces
* Fixed FMP100 LED constantly on after fw update
* Added road sign CAN elements
* Fixed security states P2 bitfield map fix
* Fixed Jamming records saved as low priority
* Fixed Fluid Market GGPS command
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''03.28.03.Rev.01'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2021-09-17}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}

===Firmware errata for FMX640/641===
{| class="wikitable" style="width: 100%;"
|-
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE VERSION
! style="width: 20%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE
! style="width: 60%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" |CHANGES
|-
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.24.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |{{{release_date| 2022-11-29}}}
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Improvements for manufacturing process. (No any functionality improvements made)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.18.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-12-23
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added advanced BLE Advertisement data are not send on server completely.
* Fixed no ID [1077]: 4 event generated after "Time TO Clear ID" timer ran out.
* Fixed event ID [1077]: 4 generation and DOUT setting to '1' on key clear timer exparation code added.
* Fixed FMB640 DOUTs bug fix, when DOUTs turns on for a moment after startup.
* Fixed CAN2 bus normal mode is not working.
* Added no BT changes and version/mod fix.
* Fixed after DriverAuthorization device does not send SMS bug fix.
* Added Contipressure new parameters.
* Fixed device reset after configuration saving
* Added Iridium Edge support Fixed AVL unnecessary records after restart.
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.17.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Fixed FMC640 Improve gprs context opening.
* Fixed FMC640 Improve new gprs configuration for BG96.
* Added LVCAN adapter compatibility over RS232 functionality.
* Fixed periodic AVL packet sending (when connecting to DDD server).
* Fixed RS232 Buffered long message when SD storage is used
* Added periodic total odometer value save (if moving).
* Added total odometer value save (on stop).
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.16.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-05-24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
* Added allow not available (3,7) value for tachoraph driver.id IO.
* Fixed scenarios are saving records even if not enabled
* Fixed unstable additional beacons
* Fixed FMC64 stability (try socket connection once)
* Fixed jamming detection for FMC64 devices
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |'''01.02.15.Rev.00'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |2022-04-15
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" |
*Initial release
|-
|}
[[Category: Iridium Edge]]

Template:Usage Scenarios

2022-12-08T13:10:49Z

Jayesh:

== 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]]
* [[FLEET MAINTENANCE SCHEDULES (DELIVERY)]]
* [[DIGITAL TACHOGRAPH MONITORING]]
* [[Private/Business Driving Mode Functionality]]
* [[Geofence Solution in the Event of Pandemic]]
* [[Secure vehicle disabling|Secure Vehicle Disabling]]
* [[Car Sharing Solution]]
* [[FAMILY CAR TRACKING AND MONITORING WITH OBD GPS DEVICES]]
* [[Pay as You Drive]]
* [[Speed Limiting Solution]]
* [[Speed Limiting Solution FMC130+ETC]]

Speed Limiting Solution FMC130+ETC

2022-12-08T12:20:45Z

Jayesh:

==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: Usage scenarios]]

File:Seco function topology v1.8 scenario1.png

2022-12-08T10:15:44Z

Jayesh: Jayesh uploaded a new version of File:Seco function topology v1.8 scenario1.png

FMCETC-TOPOLOGY

Speed Limiting Solution FMC130+ETC

2022-12-08T10:06:57Z

Jayesh:

==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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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: The speed will be limited within +10 km/h from the configured value when the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS. To achieve the accurate speed limiting [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented.'''

[[Category: Usage scenarios]]

File:Seco function topology v1.8 scenario3.png

2022-12-08T10:06:16Z

Jayesh:

solenoid

File:Seco function topology v1.8 scenario2.png

2022-12-08T10:03:56Z

Jayesh:

fuel+FMC130

File:Seco function topology v1.8 scenario1.png

2022-12-08T09:57:55Z

Jayesh:

FMCETC-TOPOLOGY

Speed Limiting Solution FMC130+ETC

2022-11-28T06:56:55Z

Jayesh:

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

==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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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: The speed will be limited within +10 km/h from the configured value when the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS. To achieve the accurate speed limiting [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented.'''

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-27T12:39:26Z

Jayesh: /* Conclusion */

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

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

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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: The speed will be limited within +10 km/h from the configured value when the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS. To achieve the accurate speed limiting [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented.'''

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-27T12:35:29Z

Jayesh:

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

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

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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: The speed will be limited within +10 km/h from the configured value when the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS. To achieve the accurate speed limiting [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented.'''

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-25T15:28:20Z

Jayesh:

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

==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
*13223 - DOUT ON Duration should be set to 5000 ms and DOUT OFF Duration should be set to 0 ms

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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;" |03
|-
| 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]]

 

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.

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-23T13:41:50Z

Jayesh:

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

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

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

==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;" |03
|-
| 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]]

 

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.

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-23T13:07:56Z

Jayesh:

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

[[File:FMCETC.png|700x700px]]

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

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

[[File:FMCETC.png|700x700px]]

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

[[File:FuelPump Installation.png|650x650px]]

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

[[File:Solenoid valve.png|700x700px]]

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

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

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

 

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.

[[Category: Usage scenarios]]

Speed Limiting Solution FMC130+ETC

2022-11-23T12:51:37Z

Jayesh: Created page with " ==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 l..."

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

[[File:FMCETC.png]]

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

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

[[File:FMCETC.png]]

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

[[File:FuelPump Installation.png]]

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

[[File:Solenoid valve.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)
*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

 

Note: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

'''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: The speed will be limited within +10 km/h from the configured speed if the [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Speed_Source speed source] is set to GNSS and for more accuracy [https://teltonika-gps.com/product/lv-can200/ CAN adapters] can be implemented. 

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

 

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.

[[Category: Usage scenarios]]

File:Wialon+etc.png

2022-11-23T12:49:49Z

Jayesh: Jayesh uploaded a new version of File:Wialon+etc.png

etc

File:Graphetc.png

2022-11-23T12:44:45Z

Jayesh: Jayesh uploaded a new version of File:Graphetc.png

etc

File:Graphetc.png

2022-11-23T12:38:39Z

Jayesh:

etc

File:Wialon+etc.png

2022-11-23T12:36:02Z

Jayesh:

etc

File:Manual Geofence OVERSPEEDING.png

2022-11-23T08:23:55Z

Jayesh: Jayesh uploaded a new version of File:Manual Geofence OVERSPEEDING.png

File:Manual Geofence OVERSPEEDING.png

2022-11-23T08:20:23Z

Jayesh: Jayesh uploaded a new version of File:Manual Geofence OVERSPEEDING.png

File:Manual Geofence OVERSPEEDING.png

2022-11-23T08:18:44Z

Jayesh:

File:OVERSPEEDING.png

2022-11-23T05:35:22Z

Jayesh:

SPEEDING

File:Solenoid valve.png

2022-11-23T05:19:59Z

Jayesh:

Solenoid_Valve

File:FuelPump Installation.png

2022-11-23T05:18:39Z

Jayesh:

File:FMCETC.png

2022-11-23T05:12:44Z

Jayesh:

FMC+ETC