FMB640 and Tachograph Solution: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
==Supported tachographs and formats== | ==Supported tachographs and formats== | ||
The solution supports not only the standard DDD file extension but also Spanish TGD and French V1B, C1B file formats. You simply set required one in Web Tacho user settings.<br /> | |||
'''NOTE:''' To | '''NOTE:''' To check whether VDO tachograph is supported or not, Teltonika [https://tacholookup.teltonika.lt/ Tachograph Lookup] can be used. | ||
Supported devices are: Siemens VDO Digital Tachograph – DTCO 1381 (release 1.3a, 1.4 | Supported devices are: Siemens VDO Digital Tachograph – DTCO 1381 (release 1.3a, 1.4 | ||
or later) and Stoneridge Tachograph – SE5000 (release 7.1 or later). | or later) and Stoneridge Tachograph – SE5000 (release 7.1 or later). The version can be checked on | ||
tachograph or in cheque as shown in pictures below: | tachograph or in cheque as shown in pictures below: | ||
Line 41: | Line 41: | ||
[[Image:Wires.PNG|800px|center]] | [[Image:Wires.PNG|800px|center]] | ||
*CAN | *CAN wire need to be installed as far as possible from GSM antenna.<br /> | ||
Below is wiring diagram of Tachograph and FM6400/FMB640 device:<br /> | Below is a wiring diagram of Tachograph and FM6400/FMB640 device:<br /> | ||
[[Image:Wiring_diagram.PNG|800px|center]] | [[Image:Wiring_diagram.PNG|800px|center]] | ||
Line 49: | Line 49: | ||
==Checking connection (Tachocheck SMS)== | ==Checking connection (Tachocheck SMS)== | ||
After successful connection ''tachocheck'' SMS message can be sent to device for checking if | After successful connection ''tachocheck'' SMS message can be sent to the device for checking if | ||
data presented on connected lines, by | data presented on connected lines, by other words if connections were done correctly. It is | ||
used for getting status information. SMS response is of such structure: | used for getting status information. SMS response is of such structure: | ||
CAN_2:[TRC],[ABCD], K-Line:[K]<br /> | CAN_2:[TRC],[ABCD], K-Line:[K]<br /> | ||
[T] – Tachograph presence on bus: | [T] – Tachograph presence on the bus: | ||
*0 – Tachograph doesn’t respond on bus; | *0 – Tachograph doesn’t respond on the bus; | ||
*1 – Tachograph responds on bus.<br /> | *1 – Tachograph responds on bus.<br /> | ||
Line 67: | Line 67: | ||
[C] – Response to Close Last Authentication Session validity check: | [C] – Response to Close Last Authentication Session validity check: | ||
*0 – Wrong or unknown response (failed to close last authentication session); | *0 – Wrong or unknown response (failed to close last authentication session); | ||
*1 – Last authentication session closed successfully, device is ready to open new authentication session.<br /> | *1 – Last authentication session closed successfully, the device is ready to open new authentication session.<br /> | ||
[K] – K-Line data presence on bus: | [K] – K-Line data presence on the bus: | ||
*0 – K-Line data not present on bus; | *0 – K-Line data not present on the bus; | ||
*1 – K-Line data present on bus.<br /> | *1 – K-Line data present on bus.<br /> | ||
[ABCD] – FMS data presence on bus: | [ABCD] – FMS data presence on the bus: | ||
*0000 – FMS data not present on bus; | *0000 – FMS data not present on the bus; | ||
*Non-zero – FMS data detected on bus.<br /> | *Non-zero – FMS data detected on bus.<br /> | ||