Teltonika Telematics Wiki - User contributions [en]

FMC880

2024-10-07T10:11:59Z

Paulius.peciulis:

{{Template:FM Home|model=FMC880|description=Special and small waterproof LTE CAT 1 GNSS tracker with built-in accelerometer|image=FMC880-QJABO-side-2023-11-29.png|link=https://teltonika-gps.com/products/trackers/fmc880}}

[[Category:Fast & Easy Trackers]]

Secure vehicle disabling

2024-08-21T07:27:03Z

Paulius.peciulis:

==Introduction==
Motor vehicle theft is one of the world’s biggest concerns and the fastest growing crimes in many countries around the world. This great challenge for car rental agencies, car sharing clubs, businesses, state organizations and private car owners caused properly losses of over 6 billion US dollar globally in 2018. Luckily for them, Teltonika GPS trackers gave a remote secure engine cut-off (SECO) functionality that can help to recover a stolen vehicle and prevent the loss.

We glad that you decided to test our “Secure vehicle disabling” solution.

Here you will find how to prepare and to test this solution.

==Solution description==
From the firmware version '''03.28.02''' Secure vehicle disabling was introduced. This solution is intended to stop the stolen vehicle regardless of the thief's actions. Best way to do so is to disable fuel pump in order to prevent vehicle to be driven further away. However, disconnecting fuel pump on high speed will definitely cause an accident and innocent people may be harmed.

Therefore we came up with a logic how to force vehicle to stop without causing an accident. Pulsing digital output disables fuel pump in intervals until vehicle slows down to configured speed from which pump is fully disabled.
==What you need for a solution?==

*The secure vehicle disabling solution is supported by '''any Teltonika FMB series tracker (excluding FMX6 series trackers) which has''' one or more '''digital output''' (DOUT) which in this scenario is used to control fuel pump of the car.
*The SIM card in order to get data to your server.
*[[Automotive_Relay|Automotive Relay]] to cut off the fuel pump
*The secure engine cut-off (SECO) functionality is only available in Teltonika FMB series GPS trackers starting with the firmware version 03.28.02.
*FOTA WEB to remotely send the configuration to the device.

==Installation==
It’s important to well hide tracker, so it would not be a simple task for the thieves to find and unplug it. But also, please do not forget to follow [https://wiki.teltonika-gps.com/view/FMB130_First_Start#Mounting_recommendations mounting recommendations] as well. [[File:Wiring scheme.png|alt=|right|frameless|357x357px]]

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.

During installation please follow recommendations in order to avoid damaging device and vehicle:
*Wires should be connected while the module is not plugged in.
*Be sure that after the car computer falls asleep, power is still available on the chosen wire. Depending on the car, this may happen in a 5 to 30 minutes period.
*When the module is connected, be sure to measure the voltage again if it did not decrease.
*The ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.

== Configuration==

==='''1. Prerequisites:'''===
====1.1. Read through [https://wiki.teltonika-gps.com/view/FMB130_First_Start First start guide]====
====1.2. Understanding of possible [https://wiki.teltonika-gps.com/view/FMB130_System_settings#Sleep_Mode Sleep modes].====

==='''2. Configuring SECO scenario'''===
 
[[File:GPRS settings.png|alt=|left|257x257px|thumb]]
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|258x258px|thumb]]Server settings:
*2004 – Domain
*2005 – Port
*2006 – Data sending protocol (0 – TCP, 1 – UDP) 
 
 
 
After successful GPRS/SERVER settings configuration, FMB130 device will '''synchronize time''' and '''update records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMB920 Parameter list|SMS parameters]].
 
 
[[File:Codec 8E.png|alt=|left|frame]]
System settings:
 
*113 - Data protocol (0 – Codec 8, 1 – Codec 8 Extended)
 
[[File:Sleep_mode.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 [[FMB130 Sleep modes#Deep%20Sleep%20mode|Deep Sleep]] and [[FMB130 Sleep modes#Ultra%20Deep%20Sleep%20mode|Ultra Deep Sleep]] since they disable the device's GSM module to save power.
 
 
[[File:SECO.png|alt=|left|451x451px|thumb]]
SECO scenario settings:
 
*12250 – Scenario priority (0 - Disable, 1 - Low, 2 - High, 3 - Panic).
*12251 – Eventual settings (0 – Disable, 1 – Enable), if disabled - scenario status value will be appended in each AVL record.
*12252 – Output Control (0 – None, 1 – DOUT1, 2 – DOUT2, 3 – DOUT3)
* 12254 - Speed (km/h). Digital output will be activated if vehicle speed consistently lower than configured during "Speed check period".
* 12259 - Speed Pulse Scenario (km/h). Valid if "Output Pulse" feature enabled. Scenario will be activated if vehicle speed consistently lower than configured during "Speed check period". After activation digital output will be activated and disabled continuously until speed will be lower then configured in "Speed" field and longer then "Speed check period".
*12255 - Speed check period (s). Time span during which vehicle speed must be lower than configured for output to activate.
*12256 - Movement timeout (s). Accelerometer's instant movement timeout after which output will be activated (GNSS OFF).
*12253 - Output Pulse (0 – Disable, 1 – Enable). Pulse scenario adds additional output control which helps to slow down vehicle before fully disabling fuel pump.
*12257 – DOUT ON Duration (ms)
* 12258 – DOUT OFF Duration (ms)
*7377 – Send SMS To
*8377 – SMS text 

 
'''Quick start''': From default configuration to SECO detection in one SMS:
" setparam 2001:APN;2002:APN_username;2003:APN_password;2004:Domain;2005:Port;2006:0;113:1;102:1;12250:2;12252:1"
This SMS will set up your device for Secure Vehicle Disabling scenario - remote secure engine cut-off (SECO) functionality.

'''Note''': Before SMS text, two space symbols should be inserted if no SMS username or password was set in SMS \ Call settings.

==SECO SMS Commands==

Secure engine cut-off (SECO) functionality is available for device with at least one DOUT. For SECO functionality to work, DOUT must to be selected. SECO has DOUT control priority higher than immobilizer scenario.

SECO scenario can only be enabled or disabled by SMS commands:

*"secoon" - to activate SECO functionality.

*"secooff" - to disable SECO functionality.

The structure of sending SMS commands: [[FMB130 SMS/GPRS Commands]]

=== 1. SMS responses===

To SMS command „secooff“ device will give response: „Seco off received. DOUTX off“.

To SMS command „secoon“ response:

1. „Seco on received. Waiting for conditions“.

2. „Seco on received. DOUTX pulsing“.

3. „Seco on received. DOUTX on“.

When response is not 3 all later SMS will be received. Example: SMS 1 received and pulse configured, then SMS 2 will be received when speed is lower than configured and SMS 3 will be received when speed reaches 0 km/h.

'''Note:''' Sending commands to the device without DOUT will give response "SECO not available for this device". When DOUT is not selected in configuration response will be: "Error. no DOUT configured".

===2. SECO Pulse functionality===

In case SECO pulse (12253) is enabled device will not activate DOUT immediately.

'''GNSS fix present''': when speed is lower than configured Speed Pulse Scenario (12259) for configured amount of time (12255), device will pulse DOUT until GNSS speed reaches configured speed (12254) then DOUT will stop pulsing and stay active (ON) until „secooff“ SMS is received.

'''GNSS fix unavailable:''' wait until movement timeout (12256) is reached then DOUT will stay active until „secooff“ SMS is received.

In case SECO pulse is disabled while pulsing, device will activate DOUT.

===3. GNSS fix available===

After "secoon" SMS is received, command will be saved to the device memory and check vehicle speed. When speed is lower than configured (12254) for configured amount of time (12255), device will activate configured DOUT.

===4. GNSS fix unavailable===

After "secoon" SMS is received, command will be saved to device memory and movement timeout. When movement timeout (12256) is reached, device will activate configured DOUT.

==Parsing information==

==='''1.Prerequisites:'''===

====1.1. Open [[Opening TCP/UDP port|TCP/UDP port]]====

==== 1.2. Go to [[Java Parser First Start Guide|Java parser 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;" |00000000000000678E02000001774D66D5A8010F1267D220979FC600BE00C1050028018C0004000400EF0100
F00100B300018C010000000000000000000001774D66D990010F12663120979BFF00BE00C1050028018C0004

000400EF0100F00100B300018C020000000000000000020000A65F
|-
|}
{| class="nd-othertables_2" style="width:100%;"
! colspan="2" style="border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |AVL Data Packet
|-
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |AVL Data Packet Part
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |HEX Code Part
|-
| style="vertical-align: middle; text-align: center;" |Zero Bytes
| style="vertical-align: middle; text-align: center;" |00 00 00 00
|-
| style="vertical-align: middle; text-align: center;" |Data Field Length
| style="vertical-align: middle; text-align: center;" |00 00 00 67
|-
| 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 (Records)
| style="vertical-align: middle; text-align: center;" |02
|-
| style="vertical-align: middle; text-align: center;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 77 4D 66 D5 A8 (Friday, January 29, 2021 9:08:41 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |0F 12 67 D2
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 97 9F C6
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 BE
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 C1
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 28
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01 8C (AVL ID: 396, Name: Seco)
|-
| style="vertical-align: middle; text-align: center;" |of Total ID
| style="vertical-align: middle; text-align: center;" |00 04
|-
| style="vertical-align: middle; text-align: center;" |of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 04
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID: 239; Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 F0 (AVL ID: 240; Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |3’th IO ID
| style="vertical-align: middle; text-align: center;" |00 B3 (AVL ID: 179; Name: Digital Output 1)
|-
| style="vertical-align: middle; text-align: center;" |3’th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
| style="vertical-align: middle; text-align: center;" |01 8C (AVL ID: 396, Name: Seco)
|-
| style="vertical-align: middle; text-align: center;" |4’th IO Value
| style="vertical-align: middle; text-align: center;" |01 ( 0 - SECO DOUT OFF; 1- SECO DOUT pulsing; 2 - SECO DOUT ON)
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes 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;" |Timestamp
| style="vertical-align: middle; text-align: center;" |00 00 01 77 4D 66 D9 90 (Friday, January 29, 2021 9:08:42 AM)
|-
| style="vertical-align: middle; text-align: center;" |Priority
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |Longitude
| style="vertical-align: middle; text-align: center;" |0F 12 66 3
|-
| style="vertical-align: middle; text-align: center;" |Latitude
| style="vertical-align: middle; text-align: center;" |20 97 9B FF
|-
| style="vertical-align: middle; text-align: center;" |Altitude
| style="vertical-align: middle; text-align: center;" |00 BE
|-
| style="vertical-align: middle; text-align: center;" |Angle
| style="vertical-align: middle; text-align: center;" |00 C1
|-
| style="vertical-align: middle; text-align: center;" |Satellites
| style="vertical-align: middle; text-align: center;" |05
|-
| style="vertical-align: middle; text-align: center;" |Speed
| style="vertical-align: middle; text-align: center;" |00 28
|-
| style="vertical-align: middle; text-align: center;" |Event IO ID
| style="vertical-align: middle; text-align: center;" |01 8C (AVL ID: 396, Name: Seco)
|-
| style="vertical-align: middle; text-align: center;" |of Total ID
| style="vertical-align: middle; text-align: center;" |00 04
|-
| style="vertical-align: middle; text-align: center;" |of One Byte IO
| style="vertical-align: middle; text-align: center;" |00 04
|-
| style="vertical-align: middle; text-align: center;" |1’st IO ID
| style="vertical-align: middle; text-align: center;" |00 EF (AVL ID: 239; Name: Ignition)
|-
| style="vertical-align: middle; text-align: center;" |1’st IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO ID
| style="vertical-align: middle; text-align: center;" |00 F0 (AVL ID: 240; Name: Movement)
|-
| style="vertical-align: middle; text-align: center;" |2’nd IO Value
| style="vertical-align: middle; text-align: center;" |01
|-
| style="vertical-align: middle; text-align: center;" |3’th IO ID
| style="vertical-align: middle; text-align: center;" |00 B3 (AVL ID: 179; Name: Digital Output 1)
|-
| style="vertical-align: middle; text-align: center;" |3’th IO Value
| style="vertical-align: middle; text-align: center;" |00
|-
| style="vertical-align: middle; text-align: center;" |4’th IO ID
| style="vertical-align: middle; text-align: center;" |01 8C (AVL ID: 396, Name: Seco)
|-
| style="vertical-align: middle; text-align: center;" |4’th IO Value
| style="vertical-align: middle; text-align: center;" |02 ( 0 - SECO DOUT OFF; 1- SECO DOUT pulsing; 2 - SECO DOUT ON)
|-
| style="vertical-align: middle; text-align: center;" |N2 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N4 of Two Bytes IO
| style="vertical-align: middle; text-align: center;" |00 00
|-
| style="vertical-align: middle; text-align: center;" |N8 of Two Bytes 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;" |02
|-
| style="vertical-align: middle; text-align: center;" |CRC-16
| style="vertical-align: middle; text-align: center;" |00 00 A6 5F
|}

==Demonstration in platform==
TAVL: Open TAVL → select client → select Street Map → select device → choose the date from which to which to show the records → push advanced → push show button and then you will see in left down corner all information.

[[File:Tavl Seco 1.png|alt=|frameless|1153x1153px]]

[[File:Tavl Seco 2.png|alt=|frameless|1153x1153px]]

WIALON: Open WIALON → open messages → push unit ( select your device) → choose the date from which to show the records → select message (data messages) → push execute button and you will see all information.

[[File:Wialon Seco 1.png|alt=|frameless|1153x1153px]]

[[File:Wialon Seco 2.png|alt=|frameless|1153x1153px]]
 
 
[[Category: Usage scenarios]]

FMC125 Anatel certificate

2024-04-22T08:19:11Z

Paulius.peciulis: /* Attachments */

== Description ==
A certification of radio products for the Brazilian market is based on the approval of the local authority Agência Nacional De Telecomunicações (Anatel). The certification relates to national specifications for the testing and certification process and is the basis for market approval for Brazil. This document approves, in accordance with the Telecommunication Rules and Regulations, the Certificate of Conformity number 00647-20-08591, issued by "Instituto Brasileiro de Certificação para Produtos de Telecomunicações". This approval is issued on behalf of the applicant here identified and is valid only for the product described below for use under the Anatels Rules and Regulations.

== Attachments ==
[[File:Screenshot 2024-04-22 111149.png|alt=]] 
[[File:Anatel 70 BB.png|alt=]]

You can download the ANATEL certificate [https://wiki.teltonika-gps.com/view/File:CoH_20500-23-16220-2.pdf here].

[[Category: FMC125 Certification & Approvals]]

FMC125 Anatel certificate

2024-04-22T08:17:50Z

Paulius.peciulis:

== Description ==
A certification of radio products for the Brazilian market is based on the approval of the local authority Agência Nacional De Telecomunicações (Anatel). The certification relates to national specifications for the testing and certification process and is the basis for market approval for Brazil. This document approves, in accordance with the Telecommunication Rules and Regulations, the Certificate of Conformity number 00647-20-08591, issued by "Instituto Brasileiro de Certificação para Produtos de Telecomunicações". This approval is issued on behalf of the applicant here identified and is valid only for the product described below for use under the Anatels Rules and Regulations.

== Attachments ==
[[File:Anatel 70 A.png|alt=]] 
[[File:Anatel 70 BB.png|alt=]]

You can download the ANATEL certificate [https://wiki.teltonika-gps.com/view/File:CoH_20500-23-16220-2.pdf here].

[[Category: FMC125 Certification & Approvals]]

FMC125 Anatel certificate

2024-04-22T08:15:03Z

Paulius.peciulis: /* Attachments */

== Description ==
A certification of radio products for the Brazilian market is based on the approval of the local authority Agência Nacional De Telecomunicações (Anatel). The certification relates to national specifications for the testing and certification process and is the basis for market approval for Brazil. This document approves, in accordance with the Telecommunication Rules and Regulations, the Certificate of Conformity number 00647-20-08591, issued by "Instituto Brasileiro de Certificação para Produtos de Telecomunicações". This approval is issued on behalf of the applicant here identified and is valid only for the product described below for use under the Anatels Rules and Regulations.

== Attachments ==
[[File:Anatel 70 A.png|alt=]] 
[[File:Anatel 70 BB.png|alt=]]

You can download the ANATEL certificate [https://wiki.teltonika-gps.com/view/File:CoH_20500-23-16220.pdf here].

[[Category: FMC125 Certification & Approvals]]

File:Screenshot 2024-04-22 111157.png

2024-04-22T08:14:50Z

Paulius.peciulis:

Anatel Certificate

File:Screenshot 2024-04-22 111149.png

2024-04-22T08:14:11Z

Paulius.peciulis:

Anatel Certificate

FMM650 Manual

2024-04-22T07:45:20Z

Paulius.peciulis:

* [[FMM650 General description|General description]]
* [[FMM650 LED status|LED behaviour description]]
* [[FMM650 Sleep modes|Sleep modes]]
* [[FMM650 Dual SIM|Dual SIM]]
* [[FMM650 Configuration|Configuration using Teltonika Configurator]]
* [[FMM650 RS-232 and RS-485|RS-232 and RS-485]]
* [[FMM650 Mobileye|Mobileye]]
* [[FMM650 CAN adapters]]
* [[FMM650 Short Burst Data]]
* [[FMM650 J1708|FMM650 and J1708 Connection]]
* [[FMM650 Carrier|FMM650 and Carrier Freezer]]
* [[FMM650 Thermograph]]
* [[FMM650 SMS/GPRS command list|SMS/GPRS command list]]
* [[FMM650 Device Family Parameter list|Parameter list]]
* [[FMM650 Glossary|Glossary]]
* [[Tachograph Lookup]]
* [[Tachograph files download with Wialon platform]]
* [[Mounting recommendations]]
* [[How to connect FMM650 with FMS Cable]]
* [[How to Install FMM650 on DAF XF]]
* [[How to install FMM650 to MB Actros]]
* [[FMM640 BLE module update|FMM650 BLE module update]]
* [[How to download DDD files with Front Panel Cable|How to download DDD files with Front Panel Cable]]
* [[FMM650 Accessories|Accessories]]
* [[FMS_Tell_Tale_Status|FMS Tell Tale Status]]
* [[FMM650 Locked FMS Feature|FMM650 Locked FMS Feature]]

[[Category:FMM650]]

FMC650 Manual

2024-04-22T07:37:55Z

Paulius.peciulis:

* [[FMC650 General description|General description]]
* [[FMC650 LED status|LED behaviour description]]
* [[FMC650 Sleep modes|Sleep modes]]
* [[FMC650 Dual SIM|Dual SIM]]
* [[FMC650 Configuration|Configuration using Teltonika Configurator]]
* [[FMC650 RS-232 and RS-485|RS-232 and RS-485]]
* [[FMC650 Mobileye|Mobileye]]
* [[FMC650 CAN adapters]]
* [[FMC650 Short Burst Data]]
* [[FMC650 J1708|FMC650 and J1708 Connection]]
* [[FMC650 Carrier|FMC650 and Carrier Freezer]]
* [[FMC650 Thermograph]]
* [[FMC650 SMS/GPRS command list|SMS/GPRS command list]]
* [[FMC650 Device Family Parameter list|Parameter list]]
* [[FMC650 Glossary|Glossary]]
* [[Tachograph Lookup]]
* [[Tachograph files download with Wialon platform]]
* [[Mounting recommendations]]
* [[How to connect FMC650 with FMS Cable]]
* [[How to Install FMC650 on DAF XF]]
* [[How to install FMC650 to MB Actros]]
* [[How to download DDD files with Front Panel Cable|How to download DDD files with Front Panel Cable]]
* [[FMC640 BLE module update|FMC650 BLE module update]]
* [[FMC650 Accessories|Accessories]]
* [[FMS_Tell_Tale_Status|FMS Tell Tale Status]]
* [[FMC650 Locked FMS Feature|FMC650 Locked FMS Feature]]
[[Category:FMC650|2]]

Template:FMC640 and FMM640 BLE module update

2024-04-22T07:20:47Z

Paulius.peciulis:

==Introduction==
The Bluetooth Low Energy (BLE) firmware update can enhance the performance and stability of BLE devices. It is mandatory to update the device with at least 0.1.5 BLE firmware version to have the possibility to use {{{model|FMC640}}} with BLE accessories or use the device as a beacon (to broadcast the ID).

The BLE firmware can be obtained by contacting the sales manager or creating a ticket for technical support via the Helpdesk platform. 
'''Note: The BLE firmware received from the sales manager or technical support can be used with FMX640 devices. And with 03.00.15.Rev.13 firmware update, the BLE firmware can be used with FMX650 devices.

The update can be made in the following ways:
*[[#Update_via_Configurator|Via Configurator]]
*[[#Update_via_FOTA_WEB|Via Fota web]]

==Update via Configurator==
Follow the procedure below to update BLE firmware via the configurator: 
1) Connect the device to the PC and open the configurator. 
2) Go to the "Bluetooth 4.0" tab. At the bottom, you will find the "Transfer BLE Firmware file" with the "Upload" button. Press it and choose the BLE FW file, click OK and the device will be updated shortly. 
[[File:BLE Update Configurator.png|center]]

==Update via FOTA WEB==
Check if the device is updated with at least the 01.00.02 firmware version before starting the BLE firmware update. It is the minimal device firmware version that supports BLE firmware updates over the air. If the current firmware version is older than 01.00.12, download the latest base firmware from [[Firmware_versions#PROFESSIONAL_trackers|'''here''']] and update the device.

When the device is prepared, the BLE firmware update can be accomplished according to a quick and simple step-by-step guide below:

1) {{{model|FMC640}}} device must be registered in FOTA Web – device‘s model, firmware version, serial number, and other information must be shown.

{{{model|FMC640}}}device must have a correct device firmware version uploaded (Minimal device firmware 01.00.02). Once the device with the correct device firmware version connects to FOTA Web on the next scheduled connection (or instant connection, initiated by an SMS command "web_connect"), the data about the device will be updated.

[[File:04 FMx640 bluetooth update.jpg|center]]

2) To update BLE a checkbox needs to be ticked, then the „Create task“ button pressed, and the „Update BLE firmware“ option selected:

[[File:03 FMX640 bluetooth update.gif]]

Once the firmware update task has been assigned, it can be seen in the main window. Please note that uploading will start after the next scheduled connection to Fota Web. The instant connection to the FOTA WEB can be initiated by an SMS command "web_connect".

Template:FMC640 and FMM640 BLE module update

2024-04-22T07:20:14Z

Paulius.peciulis:

==Introduction==
The Bluetooth Low Energy (BLE) firmware update can enhance the performance and stability of BLE devices. It is mandatory to update the device with at least 0.1.5 BLE firmware version to have the possibility to use {{{model|FMC640}}} with BLE accessories or use the device as a beacon (to broadcast the ID).

The BLE firmware can be obtained by contacting the sales manager or creating a ticket for technical support via the Helpdesk platform. 
'''Note: The BLE firmware received from the sales manager or technical support can be used only with FMX640 devices. With 03.00.15.Rev.13 firmware update, the BLE firmware can be used with FMX650 devices.

The update can be made in the following ways:
*[[#Update_via_Configurator|Via Configurator]]
*[[#Update_via_FOTA_WEB|Via Fota web]]

==Update via Configurator==
Follow the procedure below to update BLE firmware via the configurator: 
1) Connect the device to the PC and open the configurator. 
2) Go to the "Bluetooth 4.0" tab. At the bottom, you will find the "Transfer BLE Firmware file" with the "Upload" button. Press it and choose the BLE FW file, click OK and the device will be updated shortly. 
[[File:BLE Update Configurator.png|center]]

==Update via FOTA WEB==
Check if the device is updated with at least the 01.00.02 firmware version before starting the BLE firmware update. It is the minimal device firmware version that supports BLE firmware updates over the air. If the current firmware version is older than 01.00.12, download the latest base firmware from [[Firmware_versions#PROFESSIONAL_trackers|'''here''']] and update the device.

When the device is prepared, the BLE firmware update can be accomplished according to a quick and simple step-by-step guide below:

1) {{{model|FMC640}}} device must be registered in FOTA Web – device‘s model, firmware version, serial number, and other information must be shown.

{{{model|FMC640}}}device must have a correct device firmware version uploaded (Minimal device firmware 01.00.02). Once the device with the correct device firmware version connects to FOTA Web on the next scheduled connection (or instant connection, initiated by an SMS command "web_connect"), the data about the device will be updated.

[[File:04 FMx640 bluetooth update.jpg|center]]

2) To update BLE a checkbox needs to be ticked, then the „Create task“ button pressed, and the „Update BLE firmware“ option selected:

[[File:03 FMX640 bluetooth update.gif]]

Once the firmware update task has been assigned, it can be seen in the main window. Please note that uploading will start after the next scheduled connection to Fota Web. The instant connection to the FOTA WEB can be initiated by an SMS command "web_connect".

File:CoH 20500-23-16220-2.pdf

2024-04-22T06:24:37Z

Paulius.peciulis:

File:CoH 20500-23-16220-1.pdf

2024-04-22T06:15:55Z

Paulius.peciulis:

FMC125 Anatel certificate

2024-04-22T06:13:56Z

Paulius.peciulis:

== Description ==
A certification of radio products for the Brazilian market is based on the approval of the local authority Agência Nacional De Telecomunicações (Anatel). The certification relates to national specifications for the testing and certification process and is the basis for market approval for Brazil. This document approves, in accordance with the Telecommunication Rules and Regulations, the Certificate of Conformity number 00647-20-08591, issued by "Instituto Brasileiro de Certificação para Produtos de Telecomunicações". This approval is issued on behalf of the applicant here identified and is valid only for the product described below for use under the Anatels Rules and Regulations.

== Attachments ==
[[File:Anatel 70 A.png]] 
[[File:Anatel 70 BB.png]]

You can download the ANATEL certificate [https://wiki.teltonika-gps.com/view/File:CoH_20500-23-16220.pdf here].

[[Category: FMC125 Certification & Approvals]]

CAN-CONTROL

2024-04-15T09:23:28Z

Paulius.peciulis:

[[File:CAN-CONTROL-side-2024-01-08.png||500px|right]]
[https://teltonika-gps.com/products/accessories/can-adapters/can-control CAN-CONTROL] is designed to acquire [https://en.wikipedia.org/wiki/CAN_bus CAN Bus] data and remotely control:
* Light vehicles (including electric cars)

Teltonika delivers a solution for [https://en.wikipedia.org/wiki/Carsharing car sharing] and mobility applications. CAN-CONTROL
allows to read essential [https://en.wikipedia.org/wiki/CAN_bus CAN Bus] data from the vehicle and remotely control doors (lock/
unlock) and windows.

__TOC__

==Supported vehicles features'''*'''==
===Control features===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Central lock control

# Turn signal control
# Comfort closure (Central locking, Windows, Power folding mirrors)
# Trunk release
# Factory alarm management
# Control central lock when ignition is on
</div>
===CAN bus data===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Total fuel consumption
# Fuel level (Dashboard) — Fuel level - percent or Fuel level - Liters
# Vehicle mileage — Vehicle mileage from dashboard or Vehicle mileage counted (from adapter installation)
# Door status — Front left door, Front right door, Rear right door, Rear left door, Trunk cover, Engine cover (hood)
# Engine speed (RPM)
# Oil pressure/level status
# Engine temperature
# Vehicle speed
# Accelerator pedal position
# VIN number
# Lights status (Parking, Dipped, Full beam, Front/Rear fog lights)
# [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] level
# Total [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] consumption
# Engine is working on [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] status
# AND MORE...
</div>
===Electric vehicles CAN bus data===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Charging cable status
# Charging status
# Battery level
# Vehicle range on battery
</div>
'''*''' Number of features depends on vehicle model, year and equipment.

==Supported vehicles list==

CAN-CONTROL supported vehicle list:
:*To download the xlsx version of supported vehicle list for CAN-CONTROL, [[Media:CANCONTROL list 2024 03 11 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + DTC, [[Media:CAN-CONTROL DTC 2024 03 11 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + IMMO, [[Media:CAN-CONTROL IMMO 2024 04 02 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + IMMO DIG1, [[Media:CANCONTROL IMMO DIG1 2024 04 02 en.xlsx|click here]].

==Technical features==

{| class="wikitable" style="width:70%;"
|+
! rowspan="2" style="width:30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | PARAMETER
! colspan="4" style="border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;"| VALUE
|-
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Minimum
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Typical
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Maximum
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Unit
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Supply Voltage
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Supply Voltage (Recommended Operating Conditions)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +9
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +12
| 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;" | V
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Current Consumption
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Working Mode (with 12V)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 23,6
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | mA
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Sleep Mode (with 12V)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0,95
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | mA
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Operating Temperature
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Operating Temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | -40
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +85
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | °C
|-
|}

==Certification & Approvals==
*[[CAN-CONTROL E-Mark]]

== Memberships ==

* [[CAN-CONTROL WEEE|WEEE]]

==Nomenclature, classification codes==
* [[CAN-CONTROL LITAR]]

==FAQ==
* How to connect CAN-CONTROL to: <div style="webkit-columns: 4 100px; moz-columns: 4 100px; columns: 4 100px;">
** [[FMB110_CAN_adapters|FMB110]]
** [[FMB120_CAN_adapters|FMB120]]
** [[FMB122_CAN_adapters|FMB122]]
** [[FMB125_CAN_adapters|FMB125]]
** [[FMB130_CAN_adapters|FMB130]]
** [[FMB640_CAN_adapters|FMB640]]
** [[FMU125_CAN_adapters|FMU125]]
** [[FMU126_CAN_adapters|FMU126]]
** [[FMU130_CAN_adapters|FMU130]]
** [[FMC125_CAN_adapters|FMC125]]
** [[FMC130_CAN_adapters|FMC130]]
** [[FMC640_CAN_adapters|FMC640]]
** [[FMM125_CAN_adapters|FMM125]]
** [[FMM130_CAN_adapters|FMM130]]
** [[FMM640_CAN_adapters|FMM640]]
</div>

br>
{{Template:FAQ can adapters}}

==Product Change Notifications==
[[CAN-CONTROL_Product_Change_Notifications|CAN-CONTROL Product Change Notifications]] 

==Promotional Material==
[[CAN-CONTROL design material|CAN-CONTROL Promotional Material]]

==Downloads==

<big>'''Manual & Documentation'''</big> 
{|
|[[File:pdf_icon.png|32px|link=]]
|[[Media:Datasheet-CANCONTROL.pdf|CAN-CONTROL Datasheet (EN)]]
|(Updated on: 2023-07-03)
|-
|[[File:pdf_icon.png|32px|link=]]
|[[Media:CAN-ADAPTERS-flyer.pdf|CAN ADAPTERS flyer (EN)]]
|(Updated on: 2023-06-22)
|
|}

==External links==
[https://teltonika-gps.com/products/accessories/can-adapters/can-control https://teltonika-gps.com/products/accessories/can-adapters/can-control]

[[Category:CAN Trackers & Adapters]]

CAN-CONTROL

2024-04-15T09:22:44Z

Paulius.peciulis: /* External links */

[[File:CAN-CONTROL-side-2024-01-08.png||500px|right]]
[https://teltonika-gps.com/products/accessories/can-adapters/can-control CAN-CONTROL] is designed to acquire [https://en.wikipedia.org/wiki/CAN_bus CAN Bus] data and remotely control:
* Light vehicles (including electric cars)

Teltonika delivers a solution for [https://en.wikipedia.org/wiki/Carsharing car sharing] and mobility applications. CAN-CONTROL
allows to read essential [https://en.wikipedia.org/wiki/CAN_bus CAN Bus] data from the vehicle and remotely control doors (lock/
unlock) and windows.

__TOC__

==Supported vehicles features'''*'''==
===Control features===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Central lock control

# Turn signal control
# Comfort closure (Central locking, Windows, Power folding mirrors)
# Trunk release
# Factory alarm management
# Control central lock when ignition is on
</div>
===CAN bus data===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Total fuel consumption
# Fuel level (Dashboard) — Fuel level - percent or Fuel level - Liters
# Vehicle mileage — Vehicle mileage from dashboard or Vehicle mileage counted (from adapter installation)
# Door status — Front left door, Front right door, Rear right door, Rear left door, Trunk cover, Engine cover (hood)
# Engine speed (RPM)
# Oil pressure/level status
# Engine temperature
# Vehicle speed
# Accelerator pedal position
# VIN number
# Lights status (Parking, Dipped, Full beam, Front/Rear fog lights)
# [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] level
# Total [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] consumption
# Engine is working on [https://en.wikipedia.org/wiki/Compressed_natural_gas CNG] status
# AND MORE...
</div>
===Electric vehicles CAN bus data===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
# Charging cable status
# Charging status
# Battery level
# Vehicle range on battery
</div>
'''*''' Number of features depends on vehicle model, year and equipment.

==Supported vehicles list==

CAN-CONTROL supported vehicle list:
:*To download the xlsx version of supported vehicle list for CAN-CONTROL, [[Media:CANCONTROL list 2024 03 11 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + DTC, [[Media:CAN-CONTROL DTC 2024 03 11 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + IMMO, [[Media:CAN-CONTROL IMMO 2024 04 02 en.xlsx|click here]].
:*To download the xlsx version of supported vehicle list for CAN-CONTROL + IMMO DIG1, [[Media:CANCONTROL IMMO DIG1 2024 04 02 en.xlsx|click here]].

==Technical features==

{| class="wikitable" style="width:70%;"
|+
! rowspan="2" style="width:30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | PARAMETER
! colspan="4" style="border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;"| VALUE
|-
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Minimum
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Typical
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Maximum
! style="width:10%;border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" | Unit
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Supply Voltage
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Supply Voltage (Recommended Operating Conditions)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +9
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +12
| 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;" | V
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Current Consumption
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Working Mode (with 12V)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 23,6
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | mA
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Sleep Mode (with 12V)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0,95
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | mA
|-
! colspan="5" style="border: 1px solid white; border-bottom: 1px solid #0054A6; background: white; color: #0054A6; text-align: left;"| Operating Temperature
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | Operating Temperature
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | -40
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +85
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | °C
|-
|}

==Certification & Approvals==
*[[CAN-CONTROL E-Mark]]

== Memberships ==

* [[CAN-CONTROL WEEE|WEEE]]

==Nomenclature, classification codes==
* [[CAN-CONTROL LITAR]]

==FAQ==
* How to connect CAN-CONTROL to: <div style="webkit-columns: 4 100px; moz-columns: 4 100px; columns: 4 100px;">
** [[FMB110_CAN_adapters|FMB110]]
** [[FMB120_CAN_adapters|FMB120]]
** [[FMB122_CAN_adapters|FMB122]]
** [[FMB125_CAN_adapters|FMB125]]
** [[FMB130_CAN_adapters|FMB130]]
** [[FMB640_CAN_adapters|FMB640]]
** [[FMU125_CAN_adapters|FMU125]]
** [[FMU126_CAN_adapters|FMU126]]
** [[FMU130_CAN_adapters|FMU130]]
** [[FMC125_CAN_adapters|FMC125]]
** [[FMC130_CAN_adapters|FMC130]]
** [[FMC640_CAN_adapters|FMC640]]
** [[FMM125_CAN_adapters|FMM125]]
** [[FMM130_CAN_adapters|FMM130]]
** [[FMM640_CAN_adapters|FMM640]]
</div>

br>
{{Template:FAQ can adapters}}

==Product Change Notifications==
[[CAN-CONTROL_Product_Change_Notifications|CAN-CONTROL Product Change Notifications]] 

==Promotional Material==
[[CAN-CONTROL design material|CAN-CONTROL Promotional Material]]

==Downloads==

<big>'''Manual & Documentation'''</big> 
{|
|[[File:pdf_icon.png|32px|link=]]
|[[Media:Datasheet-CANCONTROL.pdf|CAN-CONTROL Datasheet (EN)]]
|(Updated on: 2023-07-03)
|-
|[[File:pdf_icon.png|32px|link=]]
|[[Media:CAN-ADAPTERS-flyer.pdf|CAN ADAPTERS flyer (EN)]]
|(Updated on: 2023-06-22)
|
|}

==External links==
[https://teltonika-gps.com/products/accessories/can-adapters/can-control https://teltonika-gps.com/product/can-control]

[[Category:CAN Trackers & Adapters]]

Template:FMC Features settings

2024-03-26T09:27:18Z

Paulius.peciulis:

==Eco/Green Driving==

[[Image:eco_green_driving_calculator.PNG|{{{general|size}}}|right]]

When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated, and the digital output status is changed to 1 when configured. You can configure all three parameters in m/s2 units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value. Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

<table class="nd-othertables" style="width: 65%;">
<tr>
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Scenario Settings</td>
<td style="width: 8%; text-align:left">Enable/Disable Green driving functionality</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Max Acceleration</td>
<td style="width: 8%; text-align:left">Value which can be reached while accelerating without triggering harsh acceleration event.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Max Braking Acceleration</td>
<td style="width: 8%; text-align:left">Value which can be reached while braking without triggering harsh braking event.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Calculate</td>
<td style="width: 8%; text-align:left">Setting which can be used to create customised calculations for Max Acceleration, Max Braking and Max Cornering based on the users vehicle. PLEASE NOTE: calculations will show as 0.5 until vehicle weight and power number will not be inserted.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Select Drive Type</td>
<td style="width: 8%; text-align:left">Based on vehicle's drive type, e.g. front-wheel drive, rear-wheel drive, all-wheel drive</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Select Transmission Type</td>
<td style="width: 8%; text-align:left">Based on vehicle's transmission type e.g. manual, automatic, dual clutch (DCT)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Select Driving Mode</td>
<td style="width: 8%; text-align:left">This is used to set low, medium and high settings for early acceleration. Sensitive - for most restrictive settings, for example carrying cargo. Normal - medium restrictive settings, used for normal day to day operations. Insentitive Clutch - least restrictive settings for drivers</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Enter Vehicle Weight (kg)</td>
<td style="width: 8%; text-align:left">Actual weight of the car or the one registered in the logbook (required)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Enter Vehicle Power (kw)</td>
<td style="width: 8%; text-align:left">Actual engine power of the vehicle, same as registered in the logbook (required)</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Source</td>
<td style="width: 8%; text-align:left">Which source (GPS or accelerometer) data will be collected from.</td>
</tr>
{{{txt_advanced|<tr>
<td style="width: 8%; text-align:left">[[{{{model|FMB1YX}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>
<td style="width: 8%; text-align:left">When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below.</td>
</tr>}}}
<tr>
<td style="width: 8%; text-align:left">Eco/Green Driving Duration</td>
<td style="width: 8%; text-align:left">If enabled, additional record with Eco/Green Driving event duration (ms) will be saved and send to server. When GPS is selected as the data source duration accuracy will be in seconds.</td>
</tr>
{{{txt_ecodout|<tr>
<td style="width: 8%; text-align:left">Output Control</td>
<td style="width: 8%; text-align:left">Which [[{{{model|FMB1YX}}}]] Digital Output will be used for accesory (buzzer, LED and etc.) activation/deactivation.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT ON Duration</td>
<td style="width: 8%; text-align:left">A value in miliseconds (ms), for how long DOUT should be active.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT OFF Duration</td>
<td style="width: 8%; text-align:left">A value in miliseconds (ms), for how long DOUT should be inactive.</td>
</tr>}}}

</table>

{{{FMT100_eco|==Advanced Eco Driving==

From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.

When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMT100_Teltonika_Data_Sending_Parameters_ID|254]]'''.
<table class="nd-othertables" style="width: 68%;">
<tr>
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Eco Driving Average</td>
<td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Average will cause records with Eco Driving event Average value to be saved and send to the server.</td>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Eco Driving Maximum</td>
<td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>
</tr>
</table>}}}

===Data output===
----
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ([[{{{model|FMB1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving records to get more precision when displaying data.{{{text_dout| }}} <youtube>RlkJELdVGRs</youtube>

===Auto calibration===
----
The auto-calibration process is following:

#The vehicle is stopped.
#There is a straight road ahead.
#Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.
#Accelerate to >30 km/h for 5 sec.
#{{{model_2|FMB}}} will send a response when calibration is completed successfully.

Calibration is saved to internal flash memory, which means it will stay after a reset.
To check auto-calibration status send a following short text message to the {{{model_2|FMB}}} device: ''"auto_calibrate:get"''.

==Over Speeding==

When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated. Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed. Configurable parameters:
[[Image:Over_Speeding.PNG|{{{general|size}}}|right]]
 
*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.
*Send SMS to – GSM number to which SMS event will be sent.
*SMS text – SMS text.
 
{{{jamming1|
==Jamming==

[[Image:Jamming.gif|{{{general|size}}}|right]]

When a device detects GSM signal jamming, it activates the Jamming scenario. The device then starts a configurable timeout before responding that is intended to reduce false positives. After the timeout ends, the device generates an event record and digital output status is changed to 1 when configured If the device regains a GSM signal before the countdown ends, no event will be generated and output will not be controlled. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GSM signal jamming to steal your vehicle.

Connecting a Buzzer to the Digital Output to emit sounds as soon as jamming is detected is the most straightforward use of this scenario.

The Digital Output can be directly connected to the vehicle's alarm system to ensure the thief can not avoid triggering it.

It can also be connected to the central lock system to ensure that all the doors are locked.

A relay can be used to disable the starter motor. Usually used with the Immobilizer scenario.

Alternatively, the Digital output can also be connected to an LED visible to the driver to inform the driver when Jamming occurs.

'''Note that this scenario will not work with [[{{{model|FMB1YX}}}_Sleep_modes#Deep_Sleep_mode|Deep Sleep]], [[{{{model|FMB1YX}}}_Sleep_modes#Ultra_Deep_Sleep_mode|Ultra Deep Sleep]] and [[{{{model|FMB1YX}}}_Sleep_modes#Online_Deep_Sleep_mode|Online Deep Sleep]] modes, since they disable the device's GSM module to save power.'''

''Eventual Records'' parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise, it will be appended only to eventual records.

For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
}}}
{{{dout_control_via_call_feature|==DOUT Control Via Call==

[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]

The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list. 
Call control functionality is the following:
* When [[{{{model|FMB1YX}}}]] is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model|FMB1YX}}}]] turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF.
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}.
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to the maximum value (2147483647) which is about 68 years.}}}

{{{immobilizer_feature|==Immobilizer==

[[Image:Immobilizer.gif|{{{general|size}}}|right]]

If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID (or RFID card) is attached, {{{text_dout|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list. 
 

From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_Beacon_List here]'''.

By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
 <youtube>gjuiJjAejWU</youtube>}}}

The "Ignition Off Timeout" parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the Ignition off timeout is set to 30 seconds when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.

The "No Authentification Timeout" is used as a backup option in order to turn on the vehicle. For example if you set the "No Authentification Timeout" to 60 seconds, then you need to turn on the ignition and keep it active for 60 seconds, then the authorization will be successful (it will bypass the iBeacon or iButton authorization) and user will be able to turn on the vehicle on.

{{{seco_feature|==SECO==
[[Image:SECO.png|right]]
The solution, introduced in firmware version 03.28.02, is designed to stop a stolen vehicle without causing accidents. It accomplishes this by pulsing digital output to disable the fuel pump at intervals until the vehicle slows down to a configured speed, at which point the pump is fully disabled. Parameters used with ''SECO'' functionality are given in a table below.

<table class="nd-othertables" style="width: 80%;">
<tr>
<th style="width: 20%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
<th style="width: 71%; text-align:center; vertical-align:middle; color:black">Description</th>
<th style="width: 9%; text-align:center; vertical-align:center; color:black">Parameter ID</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Scenario Settings</td>
<td style="width: 8%; text-align:left">Enable/Disable SECO functionality</td>
<td style="width: 8%; text-align:center">12250</td>
</tr>
<tr>
<td style="width: 8%; text-align:left;">Eventual Records</td>
<td style="width: 8%; text-align:left">If disabled - scenario status value will be appended in each AVL record</td>
<td style="width: 8%; text-align:center">12251</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Output Control</td>
<td style="width: 8%; text-align:left">Available scenario settings for module Digital output activation/deactivation</td>
<td style="width: 8%; text-align:center">12252</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Speed</td>
<td style="width: 8%; text-align:left">Digital output will be activated if vehicle speed consistently lower than configured during "Speed check period"</td>
<td style="width: 8%; text-align:center">12254</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Speed Pulse scenario</td>
<td style="width: 8%; text-align:left">Valid if "Output Pulse" feature enabled. Scenario will be activated if vehicle speed consistently lower than configured during "Speed check period". After activation digital output will be activated and disabled continuously until speed will be lower then configured in "Speed" field and longer then "Speed check period"</td>
<td style="width: 8%; text-align:center">12259</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Speed check period</td>
<td style="width: 8%; text-align:left">Time span during which vehicle speed must be lower than configured for output to activate.</td>
<td style="width: 8%; text-align:center">12255</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Momevemt timeout</td>
<td style="width: 8%; text-align:left">Accelerometer's instant movement timeout after which output will be activated (GNSS OFF)</td>
<td style="width: 8%; text-align:center">12256</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Output pulse</td>
<td style="width: 8%; text-align:left">Pulse scenario adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
<td style="width: 8%; text-align:center">12253</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT ON duration</td>
<td style="width: 8%; text-align:left">A value in milliseconds, for how long DOUT should be active</td>
<td style="width: 8%; text-align:center">12257</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT OFF duration</td>
<td style="width: 8%; text-align:left">A value in milliseconds, for how long DOUT should be inactive</td>
<td style="width: 8%; text-align:center">12258</td>
</tr>
</table>

===SECO SMS Commands===

Secure engine cut-off (SECO) functionality is available for device with at least one DOUT. For SECO functionality to work, DOUT must to be selected. SECO has DOUT control priority higher than immobilizer scenario. 
SECO scenario can only be enabled or disabled by SMS commands: 
*"secoon" - to activate SECO functionality.

*"secooff" - to disable SECO functionality.
The structure of sending SMS commands: [[FMB130 SMS/GPRS Commands]]

==== 1. SMS responses====

To SMS command „secooff“ device will give response: „Seco off received. DOUTX off“.

To SMS command „secoon“ response:

1. „Seco on received. Waiting for conditions“.

2. „Seco on received. DOUTX pulsing“.

3. „Seco on received. DOUTX on“.

When response is not 3 all later SMS will be received. Example: SMS 1 received and pulse configured, then SMS 2 will be received when speed is lower than configured and SMS 3 will be received when speed reaches 0 km/h. 
'''Note:'''
Sending commands to the device without DOUT will give response "SECO not available for this device". When DOUT is not selected in configuration response will be: "Error. no DOUT configured". This secure vehicle disabling solution is supported by any Teltonika FMB series tracker (excluding FMX640 series trackers), also SIM card is in order to get data to your server.

For more information about SECO configuring please see [https://wiki.teltonika-gps.com/view/Secure_vehicle_disabling '''here''']

}}}

{{{ibutton_feature|==iButton Read Notification==
[[Image:IButton_Read_Notification.gif|{{{general|size}}}||right]]
Output control parameter let user chose which DOUT will iButton blink. After connecting of iButton DOUT will blink for period of time, which configured in DOUT ON Duration parameter. The iButton List checking parameter configures that device reads the iButton ID from list or not. For example if configured as Enabled, device will not blink DOUT unless the iButton is in iButton list.
If Depend on Ignition parameter is enabled then Output will be triggered only if ignition is off (in addition to being in a list if iButton List Checking is also enabled).
Output control examples when iButton is detected (if None is selected in Output Control – all of the following steps will be skipped):

*If both iButton List Checking and Depend on Ignition are disabled – Output is triggered.
*If iButton List Checking is enabled and Depend on Ignition is disabled – Output is triggered only if iButton is in the list.
*If iButton List Checking is disabled but Depend on Ignition is enabled – Output is triggered only if ignition is off.
*If both iButton List Checking and Depend on Ignition are enabled – Output will trigger if iButton is in the list and ignition is off.

iButton Read Notification parameters:

*Output control – available scenario settings for module Digital output activation/deactivation
*DOUT ON/OFF duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.
*iButton List checking - parameter configures that device reads the iButton ID from list or not.
*Depend on Ignition - Output will be triggered only if ignition is off
}}}

{{{gnss_fuel|
==GNSS Fuel Counter==

[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]

To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in the technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed.

When speed is higher than the highway fuel consumption speed, x% of highway fuel consumption is added every extra y km/h, by default [[{{{model|FMB1YX}}}]] adds 20% every 50 km/h of extra speed. For example, the fuel consumption is (1.2 * (Highway Fuel Consumption)) at 140 km/h and (1.4 * (Highway Fuel Consumption)) at 190 km/h.

''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default, it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when the correction coefficient is 1 and [[{{{model|FMB1YX}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.

''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.
}}}
{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==

[[Image:DOUT_Control_Via_Ignition.gif|{{{dout_control_via_ignition|size}}}|right]]

This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off a timeout, selected DOUT (Digital Output) will be turned On. 

Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V. 

<table class="nd-othertables" style="width: 68%;">
<tr>
<th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
<th style="width: 20%; text-align:center; vertical-align:middle; color:black">Description</th>
</tr>
<tr>
<td style="width: 8%; text-align:left;">DOUT Control via Ignition Scenario</td>
<td style="width: 8%; text-align:left">Enable/Disable DOUT Control Via Ignition scenario</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT Control</td>
<td style="width: 8%; text-align:left">Scenario controls configured DOUT if ignition timeout exceeds its limit</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">DOUT Deactivation Via DIN</td>
<td style="width: 8%; text-align:left">DOUT is turned off if configured DIN is in on (voltage applied) state</td>
</tr>
<tr>
<td style="width: 8%; text-align:left">Ignition Off timeout</td>
<td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>
</tr>
</table>}}}

==Ignition ON Counter==
[[File:Ignition on.gif|right]]
'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. 
It is possible to configure a starting value of the counter. Maximum value: '''2147483647''' seconds or 596523.235 hours
'''NOTE THAT''', when entering a starting value, the value must be in seconds!

Example of Ignition On Counter '''I/O''' element:
[[File:Ingintion On counter.gif|left]]
 
{{{dout_type|
==DOUT 1 Output Type==
[[File:Dout1 output type.gif|right]] '''DOUT 1 Output Type''' functionality sets the initial ''DOUT1'' state. If functionality is configured in ''Normal'' mode digital output inactive state is low and when it is controlled by any scenario digital output is set to high state. Whenever functionality is configured in ''Inverted'' mode digital output inactive state is high and when it is controlled by any scenario digital output is set to low state. 

DOUT1 in '''Normal''' state:
[[File:DoutNormal.jpg|thumb|left|500px]]
 

DOUT1 in '''Inverted''' state:
[[File:InvertedDout.png|thumb|left|500px]]
 

*'''Notice!''' Digital output type control functionality will not affect SMS/GPRS command '''setdigout''' execution. 

[[File:Alert.png|50px]] Available from Firmware version: [[ {{{model|}}}_firmware_errata|3.27.07.Rev.00]] 

}}}
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}

Template:FMB GPRS settings

2024-03-26T08:40:15Z

Paulius.peciulis:

==GPRS Settings==
[[File:GPRS 2.PNG|right]]
These settings define the main parameters for {{{model|FMB1YX}}}. 
GPRS Context:
* Device ability to enable or disable GPRS connection.
APN:
*Access point name, a mandatory parameter which is used to connect to the internet (GPRS). Access Point Name is the name of a gateway between a mobile operator and the public internet. It can be obtained from your SIM card provider.
APN Username:
*Access point name username (optional – depending on operator)
APN Password:
*Access point name password (optional – depending on operator). 
Limit connection errors:
*When enabled (default option) device will try to open GPRS or socket and if it fails it will introduce additional delays on the next try. The delays are incremented based on the consecutive network errors received:
1. No delays 
2. 1 minute. 
3. 1 minute. 
4. 2 minutes. 
5. 2 minutes. 
6. 4 minutes. 
7. 6 minutes. 
8. 8 minutes. 
9. 10 minutes. 

Once 10 minutes is reached and if errors continue to occur the delay will not reset. When connection is succesful the delay resets. This feature is enabled for every socket and SIM1 or SIM2 (if available) GPRS context.

*When disabled (option introduced from 03.29.00.Rev.10 base firmware version) device will spam the network with GPRS or socket related network operations with no additional delays. This might introduce operators bans on some devices if the network signal quality is poor and device tries its best to connect to the network.
GPRS Authentication:
* Some operators use a specific type of authentification for GPRS sessions. It could be CHAP or PAP authentifications. In configurator's GPRS settings there are option to select which GPRS authentification could be used. Information about the APN details and authentification should be provided by your GSM operator. 
{{{txt_sim2|SIM1 and SIM2 ''GPRS Settings'' can be configured separately. }}}
 
{{{auto_apn|
[[File:Animation SMS.gif|Animation SMS.gif]]

==Auto APN==
[[File:Auto APN Search.png|right]]
Auto APN:
*This feature allows the device to select the correct APN from integrated into the firmware APN database. After the tracker turns ON it will automatically search APN settings depending on the inserted SIM card.
*This feature is used form 03.25.15.Rev.32 and up, explained in more detail in [[Auto_APN_feature_for_FM_trackers|this page]].
*This feature can be disabled in the device configuration if the device GPRS settings are configured before installation or during installation of device.
}}}

==Transfer APN File==
[[File:Transfer APN File .png|right]]
APN file Upload / Download: 
*Connect to the device using configurator and look for Transfer APN file section. Press the Upload button and locate your APN_list.bin file. (binary APN list can be named differently, make sure to use the correct file).
*This transfer APN File option is valid from 03.25.15.Rev.32 and up.
*The AutoAPN file comes with the device form the factory, but if the GPRS settings are configured before installation or during installation of device - APN file is not required.
 
==First Server Settings==
[[Image:Example Server settings.png|right]]
[[File:IP.png|right]]
Domain:
*Server or Domain adress, can be written either IP address or Domain.
Port:
*Server Port
Protocol:
*Defines GPRS data transport protocol, used for data transfers – TCP or UDP. From the device side TCP and UDP work almost the same, only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that, and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator.
TLS encryption:
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
[[File:Alert.png|left|30px|link=]] All the information in photos must not be used, just for demonstrational use only.
 
 
 
 
 

==Second Server Settings==
[[File:Screenshot 9.png|right]]
Second server has 4 different modes: 
Disable:
*Second server is not used.
Backup:
*Records are sent to second server if main server is not available (for example: device fails to open link with main server) or when main server response timeout has been reached 5 times in a row.
Duplicate:
*Records are sent to both servers (main and second), records are deleted from SD-card (or Flash storage) only if both servers confirmed that the records were received from device.
EGTS:
*Records are sent to both servers (main and second), records are sent to the backup server using the EGTS protocol. '''RNIS''' system is supported with EGTS protocol. ('''Relevant just in CIS Regions''') 
Backup server Domain:
*Server or Domain adress, can be written either IP address or Domain.
Back up server Port:
*Server Port
Backup server Protocol:
*Defines GPRS data transport protocol, used for data transfers – TCP or UDP. From the device side TCP and UDP both protocols require a confirmation from the server to the device sent packets. However, data consumption will be less using UDP due to differences in the Network layer of TCP/UDP and also packet structure of Codec8 using UDP protocol. More information -[[Teltonika_Data_Sending_Protocols|here]].

Encryption:
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
[[File:Alert.png|left|30px|link=]] All the information in photos must not be used, just for demonstrational use only.
 

==Records Settings==
[[File:Record settings.png|right]]
Open Link Timeout:
*The parameter used to define a timeout between the fleet management device and the server. If the device has sent all records, device holds the link for duration of the confugured timeout. “Open link timeout” will refresh after device sends a new record. If there is a need to keep a constant link with a server, increasing the value of the parameter is needed.
Server Response Timeout:
*Is used to set a period of time waiting for the response from the server-side. If there is no response from the server during the timeout, the device will close the link and according to device configuration resend the same packet.
[[File:Alert.png|left|20px|link=]] NOTE! If Data [[Codec|protocols]] are not implemented correctly, device will not send data correctly. 
Network Ping Timeout:
*Enables network ping after timeout to prevent link close by operator. For example, if the operator closes the active link after 15 minutes when no data is sent, you can set the "network ping" timeout to 10 minutes then the device sends a 0xFF byte to server to keep the link open. This functionality works only for Record and Backup Servers. '''Network Ping Timeout should be always lower than Open Link Timeout.'''
Sort by:
* Can be set either Newest or Oldest. For example if the Oldest is marked the device first will send the Oldest information, if Newest then Device will send the newest information. If the device had no connection (GSM or GPRS) due to bad coverage or being in an area with no signal. Device continues to save records into internal memory, once GSM and GPRS are recovered device will start sending saved data to server. In this example, if Oldest is configured - until newest data is seen on the server all of the oldest records have to be sent first. If Newest is configured - previous data and track won't be seen until newest data is sent first. If high priority on I/O parameters or Features are configured device will send the generated records with High Priority first.
ACK Type:
*Determines what method the device uses to receive confirmation from the server TCP/IP or AVL. TCP/IP means that the confirmation will be included in the TCP/IP layer and no additional message will be needed to acknowledge the record receiving. AVL means that the device will expect an additional AVL message from the server - according to the Data sending protocols described [[Codec|here]].

{{{fota_web|
==FOTA WEB Settings==
[[File:Fotawebsets.png|right]]
These settings are used to configure FOTA WEB server connection parameters. 
Status:
*Enables or disables FOTA WEB functionality. '''If FOTA WEB Status is set to "Disable" - the configuration will not be allowed to be uploaded into FOTA WEB.'''
Domain:
*The address of the FOTA website is entered to Domain field.
Port:
*The Port of the FOTA website is entered to Port field.
Period:
*Is used to set the timeout of repeat connections to the FOTA WEB server. 

[[File:Alert.png|left|80px|link=]]From 03.27.02 firmware version, FOTA WEB connection period randomizer is added. The randomizer will choose a +-2.5 period for each connection. For example, then the connection period is set to 30 minutes, device with each connection will choose a new connection (from 27.5 min to 32.5 minutes). This also applies to the "web_connect" SMS/GRRS command. This has been implemented to ensure smoother operation of FOTA WEB services by spreading out large numbers of simultaneous device connections over a longer timeframe.
}}}

{{{tls/dtls|
==TLS/DTLS==

From 03.27.02 firmware version, TLS/DTLS functionality was implemented for FMB0YX, FMB9X0, FMB96X, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FM30XY, FMB2YX, FMT100 device.
'''Note!''' Currently only TLS encryption functionality is fully implemented, if needed DTLS encryption is possible to implement.

Supported versions: '''1.1/1.2'''

[[image:TLSDTLS.gif]]

===TLS/DTLS certificate generation===
Instructions cover how to generate an encryption certificate and how the device should be configured in order to send encrypted records into the client-server can be downloaded [[Media:FMBXX_TLSDTLS_encryption_configuration_v0.2.pdf|'''HERE''']]. 
'''Server configuration and encryption certificate implementation is mandatory from the client-server side!'''
}}}

Template:FMC GPRS settings

2024-03-26T08:14:18Z

Paulius.peciulis:

==GPRS Settings==
[[File:GPRS 2.PNG|right]]
These settings define the main parameters for {{{model|FMC130}}}. 
GPRS Context:
* Device ability to enable or disable GPRS connection.
APN:
*Access point name, a mandatory parameter which is used to connect to the internet (GPRS). Access Point Name is the name of a gateway between a mobile operator and the public internet. It can be obtained from your SIM card provider.
APN Username:
*Access point name username (optional – depending on operator)
APN Password:
*Access point name password (optional – depending on operator). 
Limit connection errors:
*When enabled (default option) device will try to open GPRS or socket and if it fails it will introduce additional delays on the next try. The delays are incremented based on the consecutive network errors received:
1. No delays 
2. 1 minute. 
3. 1 minute. 
4. 2 minutes. 
5. 2 minutes. 
6. 4 minutes. 
7. 6 minutes. 
8. 8 minutes. 
9. 10 minutes. 

Once 10 minutes is reached and if errors continue to occur the delay will not reset. When connection is succesful the delay resets. This feature is enabled for every socket and SIM1 or SIM2 (if available) GPRS context.

*When disabled (option introduced from 03.29.00.Rev.10 base firmware version) device will spam the network with GPRS or socket related network operations with no additional delays. This might introduce operators bans on some devices if the network signal quality is poor and device tries its best to connect to the network.
GPRS Authentication:
* Some operators use a specific type of authentification for GPRS sessions. It could be CHAP or PAP authentifications. In configurator's GPRS settings there are option to select which GPRS authentification could be used. Information about the APN details and authentification should be provided by your GSM operator. 

{{{txt_sim2|SIM1 and SIM2 ''GPRS Settings'' can be configured separately. }}}
 
{{{auto_apn|
[[File:Animation SMS.gif|Animation SMS.gif]]

==Auto APN==
[[File:Auto APN Search.png|right]]
Auto APN:
*This feature allows the device to select the correct APN from integrated into the firmware APN database. After the tracker turns ON it will automatically search APN settings depending on the inserted SIM card.
*This feature is used form 03.25.15.Rev.32 and up, explained in more detail in [[Auto_APN_feature_for_FM_trackers|this page]].
*This feature can be disabled in the device configuration if the device GPRS settings are configured before installation or during installation of device.
}}}

==Transfer APN File==
[[File:Transfer APN File .png|right]]
APN file Upload / Download: 
*Connect to the device using configurator and look for Transfer APN file section. Press the Upload button and locate your APN_list.bin file. (binary APN list can be named differently, make sure to use the correct file).
*This transfer APN File option is valid from 03.25.15.Rev.32 and up.
*The AutoAPN file comes with the device form the factory, but if the GPRS settings are configured before installation or during installation of device - APN file is not required.
 

==First Server Settings==
[[Image:Example Server settings.png|right]]
[[File:IP.png|right]]
Domain:
*Server or Domain adress, can be written either IP address or Domain.
Port:
*Server Port
Protocol:
*Defines GPRS data transport protocol, used for data transfers – TCP or UDP. From the device side TCP and UDP work almost the same, only difference is that UDP doesn't need additional confirmation from the server side, that the data packet was received. TCP has that, and uses more network data for the confirmation. The desired data transfer protocol can be selected through the configurator.
TLS encryption:
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
[[File:Alert.png|left|30px|link=]] All the information in photos must not be used, just for demonstrational use only.
 
 
 
 
 

==Second Server Settings==
[[File:Screenshot 9.png|right]]
Second server has 4 different modes: 
Disable:
*Second server is not used.
Backup:
*Records are sent to second server if main server is not available (for example: device fails to open link with main server) or when main server response timeout has been reached 5 times in a row.
Duplicate:
*Records are sent to both servers (main and second), records are deleted from SD-card (or Flash storage) only if both servers confirmed that the records were received from device.
EGTS:
*Records are sent to both servers (main and second), records are sent to the backup server using the EGTS protocol. '''RNIS''' system is supported with EGTS protocol. ('''Relevant just in CIS Regions''') 
Backup server Domain:
*Server or Domain adress, can be written either IP address or Domain.
Back up server Port:
*Server Port
Backup server Protocol:
*Defines GPRS data transport protocol, used for data transfers – TCP or UDP. From the device side TCP and UDP both protocols require a confirmation from the server to the device sent packets. However, data consumption will be less using UDP due to differences in the Network layer of TCP/UDP and also packet structure of Codec8 using UDP protocol. More information -[[Teltonika_Data_Sending_Protocols|here]].

Encryption:
*An additional option is the use of TLS encryption for sending records to the main server and backup server.
[[File:Alert.png|left|30px|link=]] All the information in photos must not be used, just for demonstrational use only.
 

==Records Settings==
[[File:Record settings.png|right]]
Open Link Timeout:
*The parameter used to define a timeout between the fleet management device and the server. If the device has sent all records, device holds the link for duration of the confugured timeout. “Open link timeout” will refresh after device sends a new record. If there is a need to keep a constant link with a server, increasing the value of the parameter is needed.
Server Response Timeout:
*Is used to set a period of time waiting for the response from the server-side. If there is no response from the server during the timeout, the device will close the link and according to device configuration resend the same packet.
[[File:Alert.png|left|20px|link=]] NOTE! If Data [[Codec|protocols]] are not implemented correctly, device will not send data correctly. 
Network Ping Timeout:
*Enables network ping after timeout to prevent link close by operator. For example, if the operator closes the active link after 15 minutes when no data is sent, you can set the "network ping" timeout to 10 minutes then the device sends a 0xFF byte to server to keep the link open. This functionality works only for Record and Backup Servers. '''Network Ping Timeout should be always lower than Open Link Timeout.'''
Sort by:
* Can be set either Newest or Oldest. For example if the Oldest is marked the device first will send the Oldest information, if Newest then Device will send the newest information. If the device had no connection (GSM or GPRS) due to bad coverage or being in an area with no signal. Device continues to save records into internal memory, once GSM and GPRS are recovered device will start sending saved data to server. In this example, if Oldest is configured - until newest data is seen on the server all of the oldest records have to be sent first. If Newest is configured - previous data and track won't be seen until newest data is sent first. If high priority on I/O parameters or Features are configured device will send the generated records with High Priority first.
ACK Type:
*Determines what method the device uses to receive confirmation from the server TCP/IP or AVL. TCP/IP means that the confirmation will be included in the TCP/IP layer and no additional message will be needed. AVL means that the device will expect an additional AVL message from the server - according to the Data sending protocols described [[Codec|here]].

{{{fota_web|
==FOTA WEB Settings==
[[File:Fotawebsets.png|right]]
These settings are used to configure FOTA WEB server connection parameters. 
Status:
*Enables or disables FOTA WEB functionality. '''If FOTA WEB Status is set to "Disable" - the configuration will not be allowed to be uploaded into FOTA WEB.'''
Domain:
*The address of the FOTA website is entered to Domain field.
Port:
*The Port of the FOTA website is entered to Port field.
Period:
*Is used to set the timeout of repeat connections to the FOTA WEB server. 

[[File:Alert.png|left|80px|link=]]From 03.27.02 firmware version, FOTA WEB connection period randomizer is added. The randomizer will choose a +-2.5 period for each connection. For example, then the connection period is set to 30 minutes, device with each connection will choose a new connection (from 27.5 min to 32.5 minutes). This also applies to the "web_connect" SMS/GRRS command. This has been implemented to ensure smoother operation of FOTA WEB services by spreading out large numbers of simultaneous device connections over a longer timeframe.
}}}

{{{tls/dtls|
==TLS/DTLS==

From 03.27.02 firmware version, TLS/DTLS functionality was implemented for FMB0YX, FMB9X0, FMB96X, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FM30XY, FMB2YX, FMT100 device.
'''Note!''' Currently only TLS encryption functionality is fully implemented, if needed DTLS encryption is possible to implement.

Supported versions: '''1.1/1.2'''

[[image:TLSDTLS.gif]]

===TLS/DTLS certificate generation===
Instructions cover how to generate an encryption certificate and how the device should be configured in order to send encrypted records into the client-server can be downloaded [[Media:FMBXX_TLSDTLS_encryption_configuration_v0.2.pdf|'''HERE''']]. 
'''Server configuration and encryption certificate implementation is mandatory from the client-server side!'''
}}}