Jump to content
  • EN

Test-AC: Difference between revisions

From Teltonika Telematics Wiki
← Older editNewer edit →
VisualWikitext
No edit summary
No edit summary
Line 1: Line 1:
==Power Saving settings==
=Two-Factor Authentication (2FA) on the 1Global Platform=
{{#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 =  
}}


===Online Sleep===
==Overview==
*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.
Starting '''February 17, 2026''', Two-Factor Authentication (2FA) will become mandatory for all users accessing the 1Global IoT Connectivity platform at https://iot.truphone.com/. This update enhances account protection and aligns the platform with modern security standards.
*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.
*All listed entry conditions must be met in order to enter Online Sleep.
*At least one exit condition must be met in order to wake up from Online Sleep.
<br>


<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">
==Description==
2FA adds an extra verification step during login. Along with your email and password, you will need to provide a unique code generated by an authentication app. This ensures stronger protection against unauthorized access.


<tr>
==How 2FA Works==
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
To complete the login process, use an authentication app such as:
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>


</tr>
*'''Microsoft Authenticator'''
<tr>


<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
*'''Google Authenticator'''
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Configured '''Ignition source''' is off.<br>
*Movement is not detected by the configured '''Movement source'''.<br>
*Device time must be synchronized, as 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>
*No SMS messages are being received.<br>
*No open Data sockets (ignored with enabled permanent link)<br>
*No active FOTA WEB connection progress.<br>
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Ignition is ON.<br>
*Movement is detected.<br>
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is activated }}
*Periodic wake-up (if enabled).<br></td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*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>
Once two-factor authentication (2FA) becomes mandatory, please follow the login procedure outlined below:
<tr>


<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |--->
#Log in using your '''email''' and '''password'''.
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
#A QR code will appear on the screen.
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
#Open your chosen authentication app and '''scan the QR code'''.
*No communication with Main module for 1 second.
#Enter the generated verification code.
*No configured CAN data is read for 5 seconds.
#Provide a device name for identification.
*At least 1 second has passed since the last module wake up.</td>
#Select '''Save''' to finalize the setup.
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*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 #336699;">
*CAN
</td>
}}


</tr>
[[File:1Global 2FA authentication screen.png]]
<tr>
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual BT}} |--->
<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
<td style="vertical-align: middle; text-align: left;">
*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.</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: center;">'''---'''</td>
}}


</tr>
'''Note:''' If the verification code is entered incorrectly, the system will display an error message and prompt you to try again.
</table>


===Deep Sleep===
If you have any questions or need assistance enabling and using Two-Factor Authentication, please contact Teltonika support team.
{{#switch: {{{model}}}
| #default =
*During Deep Sleep mode, the device generates and stores periodic records.
*All listed entry conditions must be met in order to enter Deep Sleep.
*At least one exit condition must be met in order to wake up from Deep Sleep.
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">
 
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Configured '''Ignition source''' is off.
*Movement is not detected by the configured '''Movement source'''.
*Device time must be synchronized, as 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.
*No SMS messages are being received.
*No open Data sockets (ignored with enabled permanent link)<br>
*No active FOTA WEB connection progress.
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Ignition is ON.
*Movement is detected.
*Periodic wake-up (if enabled).
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*Modem
*Record sending
*GNSS
*IMU (Inertial Measurement Unit)
*FOTA WEB
*LEDs (Navigation and Status)
*Odometer
*Data acquisition
*SNTP time synchronization
*Overspeeding
*Trip
*Unplug Detection
*Jamming Detection
*Eco Driving
</td>
</tr>
<tr>
 
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |--->
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*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.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*Main module sends any request via UART.
*Any CAN data is present on the CAN bus.
</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN
</td>
}}
 
</tr>
<tr>
 
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual BT}} |--->
<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
<td style="vertical-align: middle; text-align: left;">
*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.
</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 module).
*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;">
*BLE scanning
</td>
}}
 
</tr>
</table>
| ATC700
| ATM700 =
}}
===Power Off Sleep===
*All listed entry conditions must be met in order to enter Power Off Sleep.
*At least one exit condition must be met in order to wake up from Power Off Sleep.
When device goes into sleep mode, some modules are turned off to consume less power. Listed below are the modules and scenarios that are turned off in common with all modes and those that are disabled specifically for the '''Power off sleep''' mode:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse; border-bottom: 3px solid #336699;">
 
<tr>
<th style="width:1%; vertical-align: middle; text-align: center;">Module</th>
<th style="width:1%; vertical-align: middle; text-align: center;">Entry Conditions</th>
<th style="width:5%; vertical-align: middle; text-align: center;">Exit conditions</th>
<th style="width:6%; vertical-align: middle; text-align: center;">Disabled functions</th>
 
</tr>
<tr>
 
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''Main'''''</td>
<td style="vertical-align: middle; text-align: left; min-width: 550px; border-bottom: 3px solid #336699;">
*Configured '''Ignition source''' is off.
*Movement is not detected by the configured '''Movement source'''.
*Device time must be synchronized, as 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.
*No SMS messages are being received.
*No open Data sockets (ignored with enabled permanent link)<br>
*No active FOTA WEB connection progress.
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is deactivated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is deactivated }}
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 150px; border-bottom: 3px solid #336699;">
*Ignition is ON.
*Movement is detected.
{{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN1}} | *DIN1 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN2}} | *DIN2 is activated }} {{#if: {{FTX Pin Support List|model={{{model}}}|pin=DIN3}} | *DIN3 is activated }}
</td>
<td style="vertical-align: middle; horizontal-align: center; min-width: 100px; border-bottom: 3px solid #336699;">
*Modem
*Record sending
*GNSS
*IMU (Inertial Measurement Unit)
*FOTA WEB
*Charger service
*LEDs (Navigation and Status)
*Odometer
*Data acquisition
*SNTP time synchronization
*Overspeeding
*Trip
*Unplug Detection
*Jamming Detection
*Eco Driving
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |--->
*CAN (''does not receive requests, does not read CAN bus messages'')
}}
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}} | *BLE--->
**PIN's are unavailable while BLE module is off.
**Anything connected or enabled by BLE module(1 wire, DIN's, DOUT's, BLE as a peripheral)
}}
</td>
 
</tr>
<tr>
 
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=Manual CAN}} |--->
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">'''''CAN'''''</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*Main module enters power off sleep mode.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px; border-bottom: 3px solid #336699;"">
*Main module wakes up and restarts CAN module.
</td>
<td style="vertical-align: middle; text-align: left; border-bottom: 3px solid #336699;">
*CAN (''does not receive requests, does not read CAN bus messages'')
</td>
}}
 
</tr>
<tr>
<!---
<!---{{#if: {{FTX Pin Support List|model={{{model}}}|pin=BT}} | --->>
<td style="vertical-align: middle; text-align: left;">'''''BLE'''''</td>
<td style="vertical-align: middle; text-align: left;">
*Main module enters power off sleep mode.
</td>
<td style="vertical-align: middle; text-align: left; min-width: 150px;"">
*Main module wakes up and restarts BLE module.
</td>
<td style="vertical-align: middle; text-align: left;">
*PIN's are unavailable while BLE module is off.
*Anything connected or enabled by BLE module(1 wire, DIN's, DOUT's, BLE as a peripheral)
</td>
}}
 
</tr>
</table>

Revision as of 16:10, 11 February 2026

Two-Factor Authentication (2FA) on the 1Global Platform

Overview

Starting February 17, 2026, Two-Factor Authentication (2FA) will become mandatory for all users accessing the 1Global IoT Connectivity platform at https://iot.truphone.com/. This update enhances account protection and aligns the platform with modern security standards.

Description

2FA adds an extra verification step during login. Along with your email and password, you will need to provide a unique code generated by an authentication app. This ensures stronger protection against unauthorized access.

How 2FA Works

To complete the login process, use an authentication app such as:

  • Microsoft Authenticator
  • Google Authenticator

Once two-factor authentication (2FA) becomes mandatory, please follow the login procedure outlined below:

  1. Log in using your email and password.
  2. A QR code will appear on the screen.
  3. Open your chosen authentication app and scan the QR code.
  4. Enter the generated verification code.
  5. Provide a device name for identification.
  6. Select Save to finalize the setup.

Note: If the verification code is entered incorrectly, the system will display an error message and prompt you to try again.

If you have any questions or need assistance enabling and using Two-Factor Authentication, please contact Teltonika support team.

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Test-AC&oldid=111210"