Jump to content

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
Line 1: Line 1:
===Behavior Description===
=Table - New Content=
Device is blocked when it connects to an operator with restricted '''Mobile Country Code (MCC)''' it saves blocking timestamp (current timestamp + 28 days) and starts the counter. The counter tracks the cumulative number of days the device spends connected to an operator with restricted MCC.
{{#switch: {{{model}}}
| #default =
[[File:FTX power saving settings.png|right|500 px]]
| ATC700
| ATM700 =  
[[File:ATX power saving settings.png|right|500 px]]
}}
Puts the device into a power-saving mode, preserving the power consumption from the external source or the internal battery.
{{#switch: {{{model}}}
| #default =
| ATC700
| ATM700 =
}}


If the device reaches '''28 cumulative days''' of connection to to an operator with restricted '''MCC''', it will be '''automatically blocked'''.
==Online Sleep==
*In Online Sleep mode, the device manages the connection only when records need to be sent. The connection is opened at periodic intervals to send records and closed immediately after, without any timeout.
*Changing the Permanent Link setting during Online Sleep will wake up the device to apply the new configuration.
*With Permanent Link enabled, the device maintains a constant connection, sending records immediately as they are generated, rather than waiting for the next scheduled send. After sending connection remains open.
<br>


===Blacklisted Countries===
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #111;">


The below table provides blacklisted '''Mobile Country Codes'''.
<table class="nd-othertables_2" style="width:30%; border-collapse: collapse;">
<tr>
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">MCC</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Country</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
</tr>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<tr>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>
<td style="vertical-align: middle; text-align: center;">250</td>
 
<td style="vertical-align: middle; text-align: center;">Russia</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">257</td>
<td style="vertical-align: middle; text-align: center;">Belarus</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">368</td>
<td style="vertical-align: middle; text-align: center;">Cuba</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">438</td>
<td style="vertical-align: middle; text-align: center;">Iran</td>
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;">467</td>
<td style="vertical-align: middle; text-align: center;">North Korea</td>
</tr>
</table>
===Resetting the Counter===
To reset the counter and timestamp, the device must connect to a non-restricted '''MCC''' continuously for '''7 uninterrupted days'''.
If the device disconnects from operator with a '''non-restricted MCC''' or connects to operator with a restricted MCC during this 7-day reset period, the reset process fails, and the 28-day counter continues accumulating.
===Unblocking Conditions===
In order for device to be unblocked it must maintain a continuous connection to operators with non-restricted '''MCCs for a full 7 days'''. Additionally, the device must have an active time synchronization and an inserted SIM card. If the device connects to a restricted operator MCC during this period, the unblocking counter resets.
===Blocked Actions===
While device is in a blocked state the following services are restricted:
<table class="nd-othertables_2" style="width:50%; border-collapse: collapse;">


<tr>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #111;">'''''Main'''''</td>
<th style="width:1%; vertical-align: middle; text-align: center;">Service</th>
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #111;">
<th style="width:1%; vertical-align: middle; text-align: center;">Status</th>
*Ignition (configured ignition source) is off.<br>
</tr>
*Movement is not detected by the configured movement source.<br>
*Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.<br>
*After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.<br>
*After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.<br>
*Always - device will enter sleep mode without time synchronization and GPS fix.<br>
*Sleep timeout is reached.<br>
*There are no SMS messages being received.<br>
*Data sockets are closed (ignored when permanent link is enabled)<br>
*FOTA WEB connection is not in progress.<br>
</td>
<td style="vertical-align: middle; vertical-align: top; min-width: 150px; border-bottom: 3px solid #111;">
*Ignition is ON.<br>
*Movement is detected.<br>
*Periodic wake-up (if enabled).<br></td>
<td style="vertical-align: middle; vertical-align: top; min-width: 100px; border-bottom: 3px solid #111;">  
*GNSS<br>
*Odometer<br>
*Data acquisition<br>
*SNTP time synchronization<br>
*Overspeeding<br>
*Trip<br>
*Unplug Detection<br>
*Jamming Detection<br>
*Eco Driving<br>
</td>


<tr>
<td style="vertical-align: middle; text-align: center;"> Record Saving</td>
<td style="vertical-align: middle; text-align: center;">Stopped</td>
</tr>


<tr>
<td style="vertical-align: middle; text-align: center;"> Record Sending</td>
<td style="vertical-align: middle; text-align: center;">Stopped</td>
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;">DOUT</td>
<td style="vertical-align: middle; text-align: center;">Disabled</td>
</tr>


<tr>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #111;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: center;">SMS/GPRS Commands</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #111;">
<td style="vertical-align: middle; text-align: center;">Disabled</td>
*No communication with Main module for 1 second.
</tr>
*No configured CAN data is read for 5 seconds.
*At least 1 second has passed since the last module wake up.</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #111;"">
*Main module sends any request via UART.<br>
*Any CAN data is present on the CAN bus.<br></td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #111;">
*CAN
</td>


<tr>
<td style="vertical-align: middle; text-align: center;">Sleep Modes</td>
<td style="vertical-align: middle; text-align: center;">Disabled</td>
</tr>
</tr>
<tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Features</td>
<td style="vertical-align: middle; text-align: center;">Suspended</td>
</tr>


<tr>
<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
<td style="vertical-align: middle; text-align: center;">Bluetooth</td>
<td style="vertical-align: middle; text-align: left;">
<td style="vertical-align: middle; text-align: center;">Suspended</td>
*Main module enters Online/Deep sleep modes.
</tr>
*No communication with Main module for 1 second.
*At least 1 second has passed since the last module wake up.</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*The device can wake up from sleep when a DIN input changes (detected through the external MCU).
*DIN pins remain active in sleep mode and can be used as wake-up sources for the device.</td>
<td style="vertical-align: middle; text-align: left;"> </td>


<tr>
<td style="vertical-align: middle; text-align: center;">CAN/OBD</td>
<td style="vertical-align: middle; text-align: center;">Suspended</td>
</tr>
</tr>
</table>
</table>
===Firmware Protection===
Firmware can not be downgraded below '''3.7.0''' where Country Blocking Service was introduced.

Revision as of 14:03, 3 February 2026

Table - New Content

Puts the device into a power-saving mode, preserving the power consumption from the external source or the internal battery.


Online Sleep

  • In Online Sleep mode, the device manages the connection only when records need to be sent. The connection is opened at periodic intervals to send records and closed immediately after, without any timeout.
  • Changing the Permanent Link setting during Online Sleep will wake up the device to apply the new configuration.
  • With Permanent Link enabled, the device maintains a constant connection, sending records immediately as they are generated, rather than waiting for the next scheduled send. After sending connection remains open.


Module Entry Conditions Exit conditions Disabled functions
Main
  • Ignition (configured ignition source) is off.
  • Movement is not detected by the configured movement source.
  • Device time must be synchronized. This condition depends on the “Record Settings -> Saving / sending mode parameter.
  • After Position Fix - device time is synchronized with GNSS satellites and GPS fix is obtained.
  • After Time Sync - device time is synchronized over NTP, NITZ, or GNSS satellites.
  • Always - device will enter sleep mode without time synchronization and GPS fix.
  • Sleep timeout is reached.
  • There are no SMS messages being received.
  • Data sockets are closed (ignored when permanent link is enabled)
  • FOTA WEB connection is not in progress.
  • Ignition is ON.
  • Movement is detected.
  • Periodic wake-up (if enabled).
  • GNSS
  • Odometer
  • Data acquisition
  • SNTP time synchronization
  • Overspeeding
  • Trip
  • Unplug Detection
  • Jamming Detection
  • Eco Driving
CAN
  • No communication with Main module for 1 second.
  • No configured CAN data is read for 5 seconds.
  • At least 1 second has passed since the last module wake up.
  • Main module sends any request via UART.
  • Any CAN data is present on the CAN bus.
  • CAN
BLE
  • Main module enters Online/Deep sleep modes.
  • No communication with Main module for 1 second.
  • At least 1 second has passed since the last module wake up.
  • The device can wake up from sleep when a DIN input changes (detected through the external MCU).
  • DIN pins remain active in sleep mode and can be used as wake-up sources for the device.