Jump to content

TEST-T: Difference between revisions

From Teltonika Telematics Wiki
No edit summary
No edit summary
 
(118 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
[[File:Tachosync_dashboard.png|300px|TachoSync|right|frameless]]
<tr>
[https://tacho.teltonika.lt '''TachoSync'''] is a cloud-based SaaS (Software-as-a-Service) solution that streamlines remote download and management of tachograph data, ensuring effortless compliance and operational efficiency.
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER NAME</th>
<br><br>
<th style="width:1%; vertical-align: middle; text-align: center;">PARAMETER ID (RELATED AVL ID)</th>
As we developed TachoSync, we focused on providing an exceptional user experience while listening to our customers and learning from the journey with our previous product [[WEB Tacho]]. We’ve taken valuable feedback, improved upon long-standing requests, addressed known issues, and—importantly—kept intact the features and functionality that worked best. Our mission has always been to make tachograph data retrieval effortless, and we hope you’ll feel that in every interaction with our product.
<th style="width:5%; vertical-align: middle; text-align: center;">DESCRIPTION</th>
== Platform Structure ==
<th style="width:6%; vertical-align: middle; text-align: center;">VALUES</th>
* '''[[TachoSync/01. Dashboard & System Overview|01. Dashboard & System Overview]]''' — General UI navigation, global settings, platform billing credits, and system release notes.
</tr>
* '''[[TachoSync/02. Vehicles|02. Vehicles]]''' — Configuration for automated remote download (RDL) schedules, device pairing (IMEI/VRN), and tracking hardware compatibility.
<tr>
* '''[[TachoSync/03. Drivers|03. Drivers]]''' — Driver profile management and driver tachograph card download configurations.
<td style="vertical-align: middle; text-align: center;">Scenario Settings</td>
* '''[[TachoSync/04. Files|04. Files]]''' — Technical documentation regarding secure DDD file ingestion, parsing logic, and storage data retention.
<td style="vertical-align: middle; text-align: center;">11200 <br> (251)</td>
* '''[[TachoSync/05. Companies|05. Companies]]''' — Multi-tenancy fleet structures, background Company Card Authenticator (CCA) setup, and card reader configurations.
<td style="vertical-align: middle; text-align: center;">Sets the scenario priority level.</td>
* '''[[TachoSync/06. Users|06. Users]]''' — User profile creation and Role-Based Access Control (RBAC) permission matrices.
<td style="vertical-align: middle; text-align: left;">
* '''[[TachoSync/07. Integrations|07. Integrations]]''' — Developer resources, including REST API endpoints, webhooks, and automated outbound SFTP file synchronization.
'''0 = Disable''' Disable scenario.<br>
 
'''1 = Low priority''' Device makes an additional record with indication of event cause. <br>
[[Category:Software & Applications]]
'''2 = High priority''' Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. <br>
'''3 = Panic priority''' Triggers the same actions as high priority, but if GPRS fails, the device sends an AVL packet via SMS (if enabled in SMS settings).
</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Eventual Records</td>
<td style="vertical-align: middle; text-align: center;">11203</td>
<td style="vertical-align: middle; text-align: center;">Toggle appending scenario status to eventual records.</td>
<td style="vertical-align: middle; text-align: left;">'''0 = Disable''' When enabled, scenario status will be appended only to eventual records.<br> '''1 = Enable'''When disabled, scenario status will be appended in each AVL record. </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Delay To Enter Idle (s)</td>
<td style="vertical-align: middle; text-align: center;">11205</td>
<td style="vertical-align: middle; text-align: center;">Delay before entering the excessive idling state. Defines how long a vehicle with Ignition ON (configured in System>Ignition settings) should not move to enter the excessive idling state.</td>
<td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
Maximum value '''= 3600''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Delay To Exit Idle (s)</td>
<td style="vertical-align: middle; text-align: center;">11206</td>
<td style="vertical-align: middle; text-align: center;">Delay before exiting the excessive idling state. Defines how long a vehicle should be moving with Ignition ON (configured in System>Ignition settings) to exit the excessive idling state.</td>
<td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
Maximum value '''= 3600''' </td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Output Control</td>
<td style="vertical-align: middle; text-align: center;">11024</td>
<td style="vertical-align: middle; text-align: center;">Configures the digital output to be activated when this scenario is entered.</td>
<td style="vertical-align: middle; text-align: left;">'''0 = None''' DOUTs are disabled in this scenario.
'''1 = DOUT1''' DOUT1 is enabled in this scenario.<br>
'''2 = DOUT2''' DOUT2 is enabled in this scenario.<br>
'''3 = DOUT3''' DOUT3 is enabled in this scenario.<br>
</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">DOUT ON Duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">11201</td>
<td style="vertical-align: middle; text-align: center;">Duration for which the selected DOUT signal is ON when the device enters this scenario. Value in milliseconds.
Works together with "DOUT OFF Duration" (for most parameters) - after one duration elapses, the other starts, until the scenario is exited.
</td>
<td style="vertical-align: middle; text-align: left;"> Minimum value '''= 100''' <br>
Maximum value '''= 5000'''</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">DOUT OFF Duration (ms)</td>
<td style="vertical-align: middle; text-align: center;">11202</td>
<td style="vertical-align: middle; text-align: center;">Duration for which the selected DOUT signal is OFF when the device enters this scenario. Value in milliseconds.
Works together with "DOUT ON Duration" - after one duration elapses, the other starts, until the scenario is exited.
</td>
<td style="vertical-align: middle; text-align: left;">Minimum value '''= 0''' <br>
Maximum value '''= 5000'''</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Buzzer</td>
<td style="vertical-align: middle; text-align: center;">11209</td>
<td style="vertical-align: middle; text-align: center;">Toggles use of buzzer for event indication.<br>
This parameter is available only for devices with integrated buzzer. In such cases, it replaces the “Output control” and related parameters.
</td>
<td style="vertical-align: middle; text-align: left;">'''0 = None''' Buzzer is disabled for this scenario.<br>
'''1 = Buzzer''' Buzzer is enabled for this scenario.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">Send SMS to</td>
<td style="vertical-align: middle; text-align: center;">7037</td>
<td style="vertical-align: middle; text-align: center;">Sets the GSM number of SMS event recipient.</td>
<td style="vertical-align: middle; text-align: left;">Number selected from “GSM Predefined Numbers” list in menu “SMS / Call Settings”.</td>
</tr>
<tr>
<td style="vertical-align: middle; text-align: center;">SMS Text</td>
<td style="vertical-align: middle; text-align: center;">8037</td>
<td style="vertical-align: middle; text-align: center;">Sets the SMS text that will be sent to SMS recipient when the event is triggered.</td>
<td style="vertical-align: middle; text-align: left;">Maximum text length = '''160 symbols'''</td>
</tr>
</table>

Latest revision as of 10:02, 19 June 2026

Main Page > Software & Applications > TEST-T
TachoSync
TachoSync

TachoSync is a cloud-based SaaS (Software-as-a-Service) solution that streamlines remote download and management of tachograph data, ensuring effortless compliance and operational efficiency.

As we developed TachoSync, we focused on providing an exceptional user experience while listening to our customers and learning from the journey with our previous product WEB Tacho. We’ve taken valuable feedback, improved upon long-standing requests, addressed known issues, and—importantly—kept intact the features and functionality that worked best. Our mission has always been to make tachograph data retrieval effortless, and we hope you’ll feel that in every interaction with our product.

Platform Structure

  • 01. Dashboard & System Overview — General UI navigation, global settings, platform billing credits, and system release notes.
  • 02. Vehicles — Configuration for automated remote download (RDL) schedules, device pairing (IMEI/VRN), and tracking hardware compatibility.
  • 03. Drivers — Driver profile management and driver tachograph card download configurations.
  • 04. Files — Technical documentation regarding secure DDD file ingestion, parsing logic, and storage data retention.
  • 05. Companies — Multi-tenancy fleet structures, background Company Card Authenticator (CCA) setup, and card reader configurations.
  • 06. Users — User profile creation and Role-Based Access Control (RBAC) permission matrices.
  • 07. Integrations — Developer resources, including REST API endpoints, webhooks, and automated outbound SFTP file synchronization.