Jump to content
  • EN

TachoSync Integrations: Difference between revisions

From Teltonika Telematics Wiki
← Older edit
VisualWikitext
m whoops
No edit summary
 
(9 intermediate revisions by 3 users not shown)
Line 2: Line 2:


This page gives information about the available TachoSync integrations:
This page gives information about the available TachoSync integrations:
* '''[https://api.tacho.teltonika.lt/api-docs/v1#description/overview REST API] - see this link for TachoSync API documentation portal.'''
* '''[[TachoSync_API|API]]'''
* [[TachoSync Integrations#SFTP|SFTP]]
* '''[[TachoSync Integrations#SFTP|SFTP]]'''
Additional integration methods are in development.
Additional integration methods are in development.


Line 55: Line 55:
** New files are processed.
** New files are processed.
** Failed files remain as "Failed" until a successful retry.
** Failed files remain as "Failed" until a successful retry.
** '''The user can try to [[#SFTP Integration Troubleshooting|fix the connection]] and manually retry the connection'''.  
** ''The user can try to [[#SFTP Integration Troubleshooting|fix the connection]] and manually retry the connection''.
* '''Failed''' – integration has failed:
* '''Failed''' – integration has failed:
** One or more file transfers have failed AND no file transfer has been successful:
** One or more file transfers have failed AND no file transfer has been successful:
*** New files are processed.
*** New files are processed nevertheless.
** Alternatively, the integration has failed the connection test.
** Alternatively, the integration has failed the connection test.
*** Integration is skipped when files are queued, no uploads are attempted.
*** Integration is skipped when files are queued, no uploads are attempted.
** '''The user can try to [[#SFTP Integration Troubleshooting|fix the connection]] and manually retry the connection'''.
** ''The user can try to [[#SFTP Integration Troubleshooting|fix the connection]] and manually retry the connection.''
 
===SFTP Server Settings===
===SFTP Server Settings===
[[File:TachoSync Integrations settings.png|thumb|right|alt=TachoSync Integrations settings|TachoSync SFTP integration settings]]
[[File:TachoSync Integrations settings.png|thumb|right|alt=TachoSync Integrations settings|TachoSync SFTP integration settings]]
Line 100: Line 99:


====File Naming Schema====
====File Naming Schema====
* Vehicle files <code>M_YYYYMMDD_HHmm_VEHICLEREGNUMBER_VIN.DDD</code>
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
** M – vehicle (mass memory) data
<tr>
** YYYYMMDD – download date (UTC)
<th style="width:40%; vertical-align: middle; text-align: left;">VEHICLE FILES</th>
** HHmm – download time (UTC)
<th style="width:40%; vertical-align: middle; text-align: left;">DRIVER FILES</th>
** VEHICLEREGNUMBER – vehicle registration number
</tr>
** VIN – vehicle identification number
<tr>
* Driver files
<td style="vertical-align: middle; text-align: left;"><code>M_YYYYMMDD_HHmm_VEHICLEREGNUMBER_VIN.DDD</code></td>
<code>C_YYYYMMDD_HHmm_N_SURNAME_CARDNUMBER.DDD</code>
<td style="vertical-align: middle; text-align: left;"><code>C_YYYYMMDD_HHmm_N_SURNAME_CARDNUMBER.DDD</code></td>
** C – driver card data
</tr>
** YYYYMMDD – download date (UTC)
<tr>
** HHmm – download time (UTC)
<td style="vertical-align: top; text-align: left;">
** N – first letter of driver’s first name
M – vehicle (mass memory) data<br>YYYYMMDD – download date (UTC)<br>HHmm – download time (UTC)<br>VEHICLEREGNUMBER – vehicle registration number<br>VIN – vehicle identification number
** SURNAME – driver’s surname
</td>
** CARDNUMBER – driver card number
<td style="vertical-align: top; text-align: left;">
 
C – driver card data<br>YYYYMMDD – download date (UTC)<br> HHmm – download time (UTC)<br>N – first letter of driver’s first name<br>SURNAME – driver’s surname<br>CARDNUMBER – driver card number
</td>
</tr>
</table>
====Folder Logic====
====Folder Logic====
''Each SFTP integration has a base folder'', configured in the field "Remote directory path".


''Each SFTP integration has a base folder'', configured in the field "Remote directory path". Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.
Inside this base folder, the system always creates folders that reflect your company hierarchy, e.g. <code>base_folder/MainCompany/SubCompany/Department/…</code>.


Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured'''''Italic text'':
Beyond company structure, '''the “Driver file destination“ setting determines how folders are structured:'''
'''* If you choose to store driver files in a separate driver folder (option “Driver folder”):'''
* If you choose to store driver files in a separate driver folder '''(option “Driver folder”) - two separate folders named “Drivers” and “Vehicles” are created.'''
'''** Two separate folders named “Drivers” and “Vehicles” are created.'''
** In these folders, subfolders are created according to driver card and vehicle IMEI/number, respectively.
** In these folders, subfolders are created according to driver card and vehicle IMEI/number, respectively.
** Files are placed accordingly.
** Files are placed accordingly.
'''* If you choose to store driver files in the vehicle folder (option “Vehicle folder”):'''
* If you choose to store driver files in the vehicle folder '''(option “Vehicle folder”) - separate folders are NOT created. Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).
'''** Separate “Drivers” and “Vehicles” folders are NOT created.'''
** Both driver and vehicle files are placed under these specific vehicle folders.
'''** Under the company hierarchy, only specific vehicle folders are created''' (named according to vehicle IMEI/number).
** To correctly place driver files under a vehicle folder, the system determines which vehicle the driver is operating.
** Both driver and vehicle files are placed under these specific vehicle folders. To correctly place driver files under a vehicle folder, the system must determine which vehicle the driver is operating:
*** The system checks vehicle information included in the driver file.
*** If vehicle information is not available in the driver file, the system places that driver file under the last known vehicle folder.
*** If this last known vehicle cannot be determined, the file is not uploaded (upload status set to “Failed”).


====Folder Structure Examples====
====Folder Structure Examples====
Assuming “Vehicles folder naming” = “Vehicle number” and .DDD file format.
Assuming “Vehicles folder naming” = “Vehicle number” and .DDD file format.
 
<table class="nd-othertables_2" style="width:100%; border-collapse: collapse;">
# Driver file destination = Driver folder
<tr>
* /base_folder
<th style="width:50%; vertical-align: middle; text-align: left;">Driver file destination = Driver folder</th>
** /MainCompany
<th style="width:50%; vertical-align: middle; text-align: left;">Driver file destination = Vehicle folder</th>
*** /SubCompany
</tr>
**** /Department
<tr>
***** /Vehicles
<td style="vertical-align: top; text-align: left;">
****** /ABC123 ''← vehicle folder
* /base_folder/MainCompany/SubCompany/Department
******* M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
** /Vehicles
******* …
*** /ABC123 ''← vehicle folder''
***** /Drivers  
**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
****** /1234567890/ ''← driver folder
**** …
******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DD← driver file
** /Drivers  
******* …
*** /1234567890''← driver folder''
 
**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
# Driver file destination = Vehicle folder
**** …
* /base_folder
</td>
** /MainCompany
<td style="vertical-align: top; text-align: left;">
*** /SubCompany
* /base_folder/MainCompany/SubCompany/Department
**** /Department
** /Vehicles
***** /Vehicles
*** /ABC123 ''← vehicle folder
****** /ABC123 ''← vehicle folder
**** M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
******* M_YYYYMMDD_HHmm_ABC123_VIN.DDD ← vehicle file
**** C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DDD← driver file
******* C_YYYYMMDD_HHmm_N_SURNAME_1234567890.DD← driver file
**** …
******* …
</td>
</tr>
</table>


===File Upload Behavior===
===File Upload Behavior===
Line 168: Line 168:


To troubleshoot, see [[TachoSync Integrations#SFTP Integration Troubleshooting|SFTP Integration Troubleshooting]].
To troubleshoot, see [[TachoSync Integrations#SFTP Integration Troubleshooting|SFTP Integration Troubleshooting]].
===SFTP Integration Troubleshooting===
===SFTP Integration Troubleshooting===
If the SFTP integration does not work as expected, verify the following:
If the SFTP integration does not work as expected, verify the following:
* The [[TachoSync Integrations#Prerequisites|prerequisites]] are met.
* The [[TachoSync Integrations#Prerequisites|prerequisites]] are met.
* Your internet connection is stable (there are no repeating time-outs or interruptions).
* SFTP server internet connection is stable (there are no repeating time-outs or interruptions).
* The user has write permissions for the configured directory.
* TachoSync has the neccessary permissions to create folders and upload files in your SFTP server.
* The provided path exists on the server.
* The provided path exists on the server.
If issues persist, collect the “Last event” details from the Integrations page and contact Support.
If issues persist, collect the “Last event” details from the Integrations page and contact Support.


[[Category:TachoSync]]
[[Category:TachoSync]]

Latest revision as of 15:23, 19 May 2026

Main Page > Software & Applications > TachoSync > TachoSync Integrations
Retrieved from "https://wiki.teltonika-gps.com/index.php?title=TachoSync_Integrations&oldid=113574"