Line 134: |
Line 134: |
| }} | | }} |
| |} | | |} |
− |
| |
− | ===DOUT Overcurrent protection===
| |
− |
| |
| | | |
| {| | | {| |
Line 145: |
Line 142: |
| *Codec 8 supports up to 255 AVL ID; | | *Codec 8 supports up to 255 AVL ID; |
| *Codec 8 Extended supports up and above 255 AVL ID. | | *Codec 8 Extended supports up and above 255 AVL ID. |
− |
| |
− | Protocol version for data sending to server.
| |
− | Codec 8 supports up to 255 AVL ID.
| |
− | Codec 8 Extended supports up and above 255 AVL ID.
| |
− |
| |
− | [[Image:Screenshot 2024-03-01 at 14-16-56 5.2. System - Mobility documentation.png]]
| |
| | | |
| }} | | }} |
Line 345: |
Line 336: |
| |[[Image:Time_synchronization.PNG|right]] | | |[[Image:Time_synchronization.PNG|right]] |
| User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time. | | User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time. |
| + | |
| + | Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time. |
| + | [[Image:Screenshot 2024-03-01 at 14-19-44 5.2. System - Mobility documentation.png]] |
| + | {| class="wikitable" style="width: 80%;" |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID''' |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name''' |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type''' |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min''' |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max''' |
| + | ! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default''' |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903 |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2 |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0 |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55 |
| + | |- |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0 |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt |
| + | | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org |
| + | |} |
| + | Time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. If the firmware acquires the fix, it starts working in the syncing by GNSS state. This state checks the difference of RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a procedure by GNSS. |
| + | |
| + | After that, the the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization. This is done to prevent false GNSS timestamps (such as year 2080 and etc.). If there’s no time difference found, the difference is expected to persist again for a period of 5 seconds later on when calculating. In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to state of syncing by NTP. |
| + | |
| + | Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP resynchronization time is reached. If the NTP resynchronization time is set to 0, no periodical resynchronization is done in this state. Time synchronization by NITZ can occur any time. |
| + | |
| + | [[File:Time sync chart.png|thumb]] |
| + | |
| + | |
| + | |
| + | |
| |} | | |} |
| | | |