===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
367 KB (38,713 words) - 10:21, 10 May 2024
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
367 KB (38,713 words) - 10:22, 10 May 2024
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
367 KB (38,713 words) - 10:29, 10 May 2024
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
274 KB (29,393 words) - 16:19, 28 December 2023
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
301 KB (32,262 words) - 16:16, 28 December 2023
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O Elements
301 KB (32,262 words) - 16:21, 28 December 2023
===Permanent I/O elements===
| style="vertical-align: middle; text-align: center;" |Permanent I/O elements
43 KB (4,313 words) - 17:34, 17 November 2020
...ign: left; vertical-align: center; background: white;" | Eco score allowed events<br />
...ign: left; vertical-align: center; background: white;" | Eco score allowed events value was increased to 100 for more accurate evaluation. <br />
19 KB (2,648 words) - 17:22, 7 December 2018
...d for wireless open/close detection and notifications such as trailer door events, etc. EYE sensor supports iBeacon and Eddystone protocols. The device is fu
...ion type*. For more settings go to Advanced settings tab to enable various events.
184 KB (22,443 words) - 10:33, 11 April 2024
...d for wireless open/close detection and notifications such as trailer door events, etc. EYE sensor supports iBeacon and Eddystone protocols. The device is fu
...ion type*. For more settings go to Advanced settings tab to enable various events.
141 KB (17,785 words) - 14:07, 13 May 2024
:*[[{{{model|FMM880}}} Status info#I/O Info|I/O Info]]
*[[{{{model|FMM880}}} I/O settings|I/O settings]] <span class="mw-customtoggle-myEOLproducts7" style="color
6 KB (640 words) - 16:16, 28 December 2023
:*[[{{{model|FMC880}}} Status info#I/O Info|I/O Info]]
*[[{{{model|FMC880}}} I/O settings|I/O settings]] <span class="mw-customtoggle-myEOLproducts7" style="color
6 KB (640 words) - 16:17, 28 December 2023
:*[[{{{model|FMC800}}} Status info#I/O Info|I/O Info]]
*[[{{{model|FMC800}}} I/O settings|I/O settings]] <span class="mw-customtoggle-myEOLproducts7" style="color
6 KB (642 words) - 16:21, 28 December 2023
:*[[{{{model|FMM800}}} Status info#I/O Info|I/O Info]]
*[[{{{model|FMM800}}} I/O settings|I/O settings]] <span class="mw-customtoggle-myEOLproducts7" style="color
6 KB (665 words) - 16:22, 28 December 2023
...going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until t
...ng (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are ac
4 KB (596 words) - 08:32, 20 September 2022
...going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until t
...ng (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are ac
4 KB (634 words) - 15:42, 5 September 2022
...going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until t
...ng (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are ac
4 KB (634 words) - 12:58, 23 March 2023
-
227 bytes (33 words) - 13:54, 10 March 2023
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
* '''NEW!''' CAN service and LPG I/O elements added
54 KB (7,294 words) - 12:03, 7 December 2023
-
157 bytes (20 words) - 12:37, 22 January 2020
|<strong>How do I send SMS command to Teltonika Telematics device? </strong>
IO settings guide: [[FMC920 I/O settings]]
17 KB (2,649 words) - 16:45, 26 March 2024
...going to be counted between every record made. This value is written to I/O ''Trip Odometer'' value field and is reset to zero every new record until t
...ng (harsh acceleration, braking, cornering), excessive idling and high RPM events (latter one requires OBD BT dongle). If less of parameters/scenarios are ac
4 KB (596 words) - 08:31, 20 September 2022
**<code>YY</code> – branch number, shows major changes in firmware, i.e. new module support added or new major feature added.
*SMS Data Sending improvements on events generation
48 KB (6,493 words) - 12:03, 7 December 2023
-
85 bytes (10 words) - 12:51, 22 January 2020
* [[FMB962 I/O settings|I/O settings]]
** [[FMB962 I/O settings#Priority|Priority]]
2 KB (252 words) - 07:55, 6 May 2019
==Removal of I/O elements' "Send SMS To" and "SMS Text" parameters in 03.29.00 firmware vers
...r text. Functionality changes defined in wiki page [[FMB920_SMS_events|SMS events]]
6 KB (559 words) - 13:25, 3 October 2023
==Removal of I/O elements' "Send SMS To" and "SMS Text" parameters in 03.29.00 firmware vers
...r text. Functionality changes defined in wiki page [[FMB920_SMS_events|SMS events]]
5 KB (487 words) - 09:53, 1 February 2024
...ure ECO Driving, Idling detection, Overspeeding, and High RPM features and events are enabled. ''NOTE: High RPM event is available from FMB001/FM3001, FMB1 s
...– it will generate harsh acceleration, harsh breaking and harsh cornering events. Depending on required sensitivity – you can adjust acceleration, braking
5 KB (763 words) - 15:05, 6 December 2023
* [[FMB920 I/O settings|I/O settings]]
** [[FMB920 I/O settings#Operands|Operands]]
3 KB (323 words) - 15:09, 6 December 2023
* [[FMB204 I/O settings|I/O settings]]
** [[FMB204 I/O settings#Operands|Operands]]
3 KB (330 words) - 15:10, 6 December 2023
* [[TFT100 SMS events|SMS events]]
* [[TFT100 I/O settings|I/O settings]]
1 KB (175 words) - 09:52, 4 March 2024
==SMS Events==
...figurable sms text and number fields, now it can only be configured in SMS Events tab with 10 slots in total.
1 KB (214 words) - 10:11, 4 March 2024
==SMS Events==
...figurable sms text and number fields, now it can only be configured in SMS Events tab with 10 slots in total.
1 KB (221 words) - 16:32, 26 March 2024
==SMS Events==
...figurable sms text and number fields, now it can only be configured in SMS Events tab with 10 slots in total.
1 KB (227 words) - 16:34, 26 March 2024
...y numbers has to be defined in <b>GSM Predefined Numbers</b> block. If SMS events are activated but there are no numbers defined in this list, then the devic
== Configure I/O section==
2 KB (352 words) - 12:11, 22 May 2023
*SMS events moved to a separate tab
*SMS events moved to a separate tab
144 KB (18,642 words) - 07:43, 6 May 2024
*[[FM3612 I/O settings|I/O settings]]
**[[FM3612 I/O settings#Monitoring|Monitoring]]
1 KB (131 words) - 07:09, 7 October 2019
*[[FM3622 I/O settings|I/O settings]]
**[[FM3622 I/O settings#Monitoring|Monitoring]]
935 bytes (118 words) - 14:47, 30 April 2019
*[[FM36M1 I/O settings|I/O settings]]
**[[FM36M1 I/O settings#Monitoring|Monitoring]]
961 bytes (140 words) - 12:23, 27 May 2019
*[[FMA120 I/O settings|I/O settings]]
**[[FMA120 I/O settings#Monitoring|Monitoring]]
912 bytes (115 words) - 08:19, 6 May 2019
*[[FMA110 I/O settings|I/O settings]]
**[[FMA110 I/O settings#Monitoring|Monitoring]]
912 bytes (115 words) - 00:17, 3 April 2020
*[[FMA202 I/O settings|I/O settings]]
**[[FMA202 I/O settings#Monitoring|Monitoring]]
950 bytes (118 words) - 08:40, 6 May 2019
*[[FMA204 I/O settings|I/O settings]]
**[[FMA204 I/O settings#Monitoring|Monitoring]]
950 bytes (118 words) - 09:04, 6 May 2019
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
19 KB (3,110 words) - 11:40, 6 February 2024
...All I/O configuration is as described [[{{{model|FMC640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
51 KB (7,317 words) - 13:03, 8 February 2023
...All I/O configuration is as described [[{{{model|FMB640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
44 KB (6,307 words) - 09:25, 9 September 2022
...All I/O configuration is as described [[{{{model|FMM640}}}_I/O_settings|I/O elements]].
LVCAN elements can be configured in the same way as normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
51 KB (7,317 words) - 13:05, 8 February 2023
...cted to {{{model|FMC640}}} device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,227 words) - 10:44, 17 January 2024
...cted to {{{model|FMM650}}} device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,226 words) - 10:44, 17 January 2024
...evices connected to FMB641 device. All I/O configuration is as described I/O elements}
LVCAN elements can be configured in same way like with normal I/O elements. LVCAN IO elements can also be configured remotely via SMS command
58 KB (8,228 words) - 10:45, 17 January 2024
...on your needs). Also set operand and low/high settings in order to receive events based on specific conditions, e.g.: '''Yawning - Low priority - Low/High le
...M''' in the Mode drop-down menu, afterwards '''DSM COM1''' and '''Camera I/O''' should appear in the tab list.
10 KB (1,629 words) - 15:52, 11 April 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,486 words) - 11:39, 6 February 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,486 words) - 11:39, 6 February 2024
* Device has up to 3 min. hardcoded time to get fixed position while it i's awake from a Sleep Mode. <br>
...after fix is obtained. Data could be sent according to I/O parameters in I/O section.
15 KB (2,480 words) - 10:35, 13 March 2024
...n data will be used to determine harsh acceleration, braking and cornering events.<br />
...on the impact magnitude that is required to be detected. TFT100 can detect events ranging between a slight tapping on the device and a severe accident.<br />
10 KB (1,539 words) - 14:24, 23 March 2023
...ion type*. For more settings go to Advanced settings tab to enable various events.
...n: left;" |<br>'''Magnetic field event''' - adjust if the device generates events based on detection or exit (loss) of the magnet.
13 KB (1,817 words) - 15:07, 6 December 2023
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 10:09, 2 May 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 10:39, 30 July 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 09:44, 8 August 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 15:05, 13 September 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
732 bytes (145 words) - 11:05, 16 September 2019
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
735 bytes (146 words) - 16:50, 28 June 2022
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
735 bytes (145 words) - 17:19, 14 July 2022
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
735 bytes (145 words) - 17:22, 14 July 2022
..., just that it is included as IO element to have the possibility to create events for it.
* There is a I/O element with ID 37. This is a 1 byte element - it is speed from OBDII data.
735 bytes (146 words) - 15:26, 25 August 2022
| colspan="15" |0 – Global (same for all events)
==DSM I/O elements==
10 KB (935 words) - 13:35, 1 March 2023
| style="text-align: center; vertical-align: center;" |Eco score allowed events
==I/O parameters==
264 KB (26,821 words) - 10:30, 8 April 2024
Template:FMB SMS events
77 bytes (9 words) - 12:40, 22 January 2020
...910 Basic sends a configured SMS message to a defined phone number. If SMS events are activated but there are no numbers defined in ''GSM Predefined Numbers'
2 KB (309 words) - 17:09, 17 November 2020
...FMC800}}} sends a configured SMS message to a defined phone number. If SMS events are activated but there are no numbers defined in ''GSM Predefined Numbers'
{{{pic_IO|[[Image:FMB120 SMS events.png|800px|none]]}}}
2 KB (313 words) - 11:15, 1 September 2022
...FMM800}}} sends a configured SMS message to a defined phone number. If SMS events are activated but there are no numbers defined in ''GSM Predefined Numbers'
{{{pic_IO|[[Image:FMB120 SMS events.png|800px|none]]}}}
2 KB (313 words) - 11:17, 1 September 2022
...FMC880}}} sends a configured SMS message to a defined phone number. If SMS events are activated but there are no numbers defined in ''GSM Predefined Numbers'
{{{pic_IO|[[Image:FMB120 SMS events.png|800px|none]]}}}
2 KB (313 words) - 15:44, 5 September 2022
...FMM880}}} sends a configured SMS message to a defined phone number. If SMS events are activated but there are no numbers defined in ''GSM Predefined Numbers'
{{{pic_IO|[[Image:FMB120 SMS events.png|800px|none]]}}}
2 KB (313 words) - 13:17, 23 March 2023
*Man-Down&No movement events
**Movement or any other I/O event;
12 KB (1,621 words) - 16:22, 28 December 2023
*[[TMT250 SMS events|SMS events]]
*[[TMT250 I/O settings|I/O settings]]
891 bytes (104 words) - 14:53, 18 March 2024
* [[GH5200 SMS Events|SMS Events]]
* [[GH5200 I/O settings|I/O settings]]
966 bytes (109 words) - 11:25, 26 March 2024
...n data will be used to determine harsh acceleration, braking and cornering events.<br />
...t magnitude that is required to be detected. {{{model|FMT100}}} can detect events ranging between a slight tapping on the device and a severe accident.<br/>
12 KB (1,942 words) - 12:29, 13 April 2021
** Ignition or any other I/O event;
* GPRS and SMS I/O events;
4 KB (463 words) - 07:57, 6 May 2019
** Ignition or any other I/O event;
* GPRS and SMS I/O events;
1 KB (127 words) - 15:37, 19 May 2022
** Ignition or any other I/O event;
* GPRS and SMS I/O events;
1 KB (131 words) - 12:40, 30 June 2021
** Ignition or any other I/O event;
* GPRS and SMS I/O events;
1 KB (125 words) - 14:04, 24 May 2022
** Ignition or any other I/O event;
*GPRS and SMS I/O events;
5 KB (607 words) - 16:21, 30 March 2023
* NXP i.MX RT1064 processor;
** Ignition or any other I/O event;
20 KB (2,471 words) - 09:54, 10 October 2023
..._Status_info#GSM_Info|GSM]], [[{{{model|FMM80A}}}_Status_info#I.2FO_Info|I/O]], [[{{{model|FMM80A}}}_Status_info#Maintenance|Maintenance]]''' and etc. {
<td colspan="4">Device makes a record '''On Moving''' if one of these events happen:</td>
13 KB (1,743 words) - 16:19, 28 December 2023
*I/O event;
*GPRS and SMS I/O events;
2 KB (294 words) - 16:28, 28 December 2023
*I/O event;
*GPRS and SMS I/O events;
3 KB (341 words) - 16:29, 28 December 2023
*I/O event;
*GPRS and SMS I/O events;
3 KB (459 words) - 16:29, 28 December 2023
**Movement or any other I/O event;
*GPRS and SMS I/O events;
8 KB (1,079 words) - 15:35, 25 January 2024
*I/O event;
*GPRS and SMS I/O events;
3 KB (439 words) - 14:24, 1 March 2024
*I/O event;
*GPRS and SMS I/O events;
3 KB (413 words) - 14:25, 1 March 2024
..._Status_info#GSM_Info|GSM]], [[{{{model|FMB1YX}}}_Status_info#I.2FO_Info|I/O]], [[{{{model|FMB1YX}}}_Status_info#Maintenance|Maintenance]]''' and etc. {
<td colspan="4">Device makes a record '''On Moving''' if one of these events happen:</td>
18 KB (2,568 words) - 14:49, 1 March 2024
...Fill in '''SMS Text''' field. '''SMS Text''' field can include different I/O values. More information on how to code '''SMS Text''' field can be found
..., when worker is constantly tilting up and down so to prevent fake ManDown events you can use Silent pre-alarm. </br>
5 KB (688 words) - 13:15, 14 April 2023
...Fill in '''SMS Text''' field. '''SMS Text''' field can include different I/O values. More information on how to code '''SMS Text''' field can be found
..., when worker is constantly tilting up and down so to prevent fake ManDown events you can use Silent pre-alarm. </br>
4 KB (661 words) - 13:26, 14 April 2023
...APP]] / Driver application to monitor and score driver behavior. Real time events notifications about harsh acceleration, braking, cornering, over speeding,
...te records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMB920 Par
20 KB (2,648 words) - 16:16, 28 December 2023
...te records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMB920 Par
*700 - Eco Score Allowed Events.
21 KB (2,847 words) - 16:22, 28 December 2023
|ctrIO=[[FMB206 I/O settings|I/O settings section]]
143 bytes (19 words) - 12:36, 22 January 2020
...trailer such as Temperature, Fridge door status, Alarms, etc. and generate events according to your needs. For more information please refer to the installat
The screenshot below displays Reefer I/O parameters section, here you can set up your device to send required parame
2 KB (259 words) - 09:26, 14 October 2020
...trailer such as Temperature, Fridge door status, Alarms etc. and generate events according to your needs. For more information please refer to the installat
The screenshot below displays Reefer I/O parameters section, here you can set up your device to send required parame
2 KB (252 words) - 16:59, 3 August 2020
...trailer such as Temperature, Fridge door status, Alarms etc. and generate events according to your needs. For more information please refer to the installat
The screenshot below displays Reefer I/O parameters section, here you can set up your device to send required parame
2 KB (252 words) - 17:00, 3 August 2020
...te records''' to '''the configured server'''. Time intervals and default I/O elements can be changed by using [[Teltonika Configurator]] or [[FMM130 Par
...a certain date frame for the device that you're watching, you can see the events that are generated when the Geofence is crossed (depending on what was chos
17 KB (2,229 words) - 13:56, 10 September 2021