Jump to content
  • EN

TEST-DM: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(35 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Cyber Security RED DA===
<!---This template works like this:
The Cyber Security RED DA table below applies to all products using the radio frequency spectrum.
Use basic text and images everytime, BUT
for "Deactivate by:" parameter values - we maintain in this template a list of standard values, from which which you need to select and copy directly to your Auto Geofence settings page, as plain text, when invoking this template there.--->


<div class="mw-collapsible mw-collapsed" style="border: 1px solid #aaa; padding: 0.5em; background-color: #f9f9f9;">
[[Image:FM auto geofence.png|300px|right]]
<span style="float: none; text-align: left;">'''Click to expand'''</span>
'''Auto Geofence''' allows sending notifications if your tracker leaves/re-enters the last known stationary position. Auto Geofence does not require entering coordinates –it requires GNSS visibility.
<div class="mw-collapsible-content">


'''Basic function''': when the tracker has stopped, ignition has been turned off, and “Activation Timeout” has passed, the device automatically creates a geozone of size “Radius” around the last known location. If the device leaves/re-enters this zone, it can send a record.


{| style="margin: 0 auto;valign=" left""
'''“Activation Timeout” has a second function. It works together with GNSS fix to indicate if the tracker moves after GNSS fix is lost:'''
|[[File:EC Declaration of Conformity, ET25A0564, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0564, 2025-08-01]]
|[[File:EC Declaration of Conformity, ET25A0565, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0565, 2025-08-01]]
|[[File:EC Declaration of Conformity, ET25A0566, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0566, 2025-08-01]]
|[[File:EC Declaration of Conformity, ET25A0567, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0567, 2025-08-01]]
|[[File:EC Declaration of Conformity, ET25A0568, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0568, 2025-08-01]]
|[[File:EC Declaration of Conformity, ET25A0570, 2025-08-01.png|thumb|left|x200px|EC Declaration of Conformity, ET25A0570, 2025-08-01]]
|}


You can the find PDF version of the declarations here:
When the geozone is created, and later these conditions are met:
<br>
* GNSS fix is lost;
'''[[Media:EC_Declaration_of_Conformity,_ET25A0564,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0564,_2025-08-01.pdf]]''':
* Movement is detected by Movement Source;
* FMC150-QJIB0, FMC250-QJIB0, FMC920-QJIB0, FMC800-QJIB0, FMC880-QJAB0, TAT240-QJIB0, TAT140-QJIB0, FTC921-QJAB0, FTC920-QJAB0, FTC961-QJAB0, FTC880-QJAB0, FTC305-QJAB0, FTC305-QJXB0
* Deactivation is not performed by the user;
'''[[Media:EC_Declaration_of_Conformity,_ET25A0565,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0565,_2025-08-01.pdf]]''':
* FMC125-MBIB0, FMC130-ME3, FMC230-MBIB0, FMC234-MBIB0, FMC003-MBIB0, FMC225-MBIB0, FMC650-MBX50
'''[[Media:EC_Declaration_of_Conformity,_ET25A0566,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0566,_2025-08-01.pdf]]''':
* FMC125-MCIB0, FMC00-MCIB0, FMC225-MCIB0, FMC130-MCIB0, FMC230-MCIB0, FMC234-MCIB0, FMC650-MCX50
'''[[Media:EC_Declaration_of_Conformity,_ET25A0567,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0567,_2025-08-01.pdf]]''':
* FMB110-TAIB0, FMB120-TAIB0, FMB122-TAEB0, FMB130-TAIB0, FMB202, FMB204, FMB209, FMB230-TAIX0, FMB150-TAIB0, FMB140, FMB240-TAIX0, FMB900, FMB910, FMB920, FMB930-TAIB0, FMB965-TAIB0, FMB010, FMB020, FMP100, FMT100, FMB125-TAIB0, FMB125-TAEB0, TAT100-TAIB0, TAT100-TAIBA, TFT100, GH5200-TAIB0
'''[[Media:EC_Declaration_of_Conformity,_ET25A0568,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0568,_2025-08-01.pdf]]''':
* FMM125-Q3IB0, FMM130-QG5, FMM230-Q3IB0, FMM150-Q3IB0, FMM250-Q3IB0, FMM003-Q3IB0, FMM920-Q3IB0, FMM800-Q3IB0, FMM880-Q3AB0, FMM650-Q3X50, TAT141-Q3IB0, FMT880-Q3AB0, FMT305-Q3AB0
'''[[Media:EC_Declaration_of_Conformity,_ET25A0570,_2025-08-01.pdf|EC_Declaration_of_Conformity,_ET25A0570,_2025-08-01.pdf]]''':
* FMC640


the tracker starts monitoring GNSS status for the duration of “Activation Timeout”. If GNSS fix is achieved – the timeout pauses and will continue again once all 3 conditions are satisfied. If GNSS fix is not achieved during “Activation Timeout” – the tracker sends an eventual record with AVL ID 175 and value 0 (regardless of if the vehicle moves from or stays in the geozone). This timeout can be reset by triggering “Deactivate by” source, or if movement stops when there is no GNSS fix.


</div>
'''Auto Geofence parameters''':
</div>
* Eventual Records - enable or disable Eventual Records functionality.
* Generate Event – configures event generation on auto geofence entrance, exit, or in both cases.
* Activation timeout (s) - defines the delay between Ignition OFF and the creation of the auto geofence of size “Radius” around the tracker’s most recent position.
* Radius (m) – sets the radius of the auto geofence.
* Deactivate by: - select deactivation source.
* Send SMS to – selects the number from predefined list for notification.
* SMS Text -text of SMS to send.
 
'''Auto Geofence can be deactivated by:'''<br>
<!--- PASTE LIST OF PARAMETERS HERE --->

Latest revision as of 10:15, 29 January 2026


Auto Geofence allows sending notifications if your tracker leaves/re-enters the last known stationary position. Auto Geofence does not require entering coordinates –it requires GNSS visibility.

Basic function: when the tracker has stopped, ignition has been turned off, and “Activation Timeout” has passed, the device automatically creates a geozone of size “Radius” around the last known location. If the device leaves/re-enters this zone, it can send a record.

“Activation Timeout” has a second function. It works together with GNSS fix to indicate if the tracker moves after GNSS fix is lost:

When the geozone is created, and later these conditions are met:

  • GNSS fix is lost;
  • Movement is detected by Movement Source;
  • Deactivation is not performed by the user;

the tracker starts monitoring GNSS status for the duration of “Activation Timeout”. If GNSS fix is achieved – the timeout pauses and will continue again once all 3 conditions are satisfied. If GNSS fix is not achieved during “Activation Timeout” – the tracker sends an eventual record with AVL ID 175 and value 0 (regardless of if the vehicle moves from or stays in the geozone). This timeout can be reset by triggering “Deactivate by” source, or if movement stops when there is no GNSS fix.

Auto Geofence parameters:

  • Eventual Records - enable or disable Eventual Records functionality.
  • Generate Event – configures event generation on auto geofence entrance, exit, or in both cases.
  • Activation timeout (s) - defines the delay between Ignition OFF and the creation of the auto geofence of size “Radius” around the tracker’s most recent position.
  • Radius (m) – sets the radius of the auto geofence.
  • Deactivate by: - select deactivation source.
  • Send SMS to – selects the number from predefined list for notification.
  • SMS Text -text of SMS to send.

Auto Geofence can be deactivated by:

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=TEST-DM&oldid=110879"