Description:
Below a list of DCS commands related to tachograph download process. Currently on queue commands can be checked here after connecting to VPN (replace 11111111111 with the IMEI):
PENDING
Download does not start due to following reasons:
Company card not connected : “TachoAuthService card reservation problem: No cards attached”
Company cards by the specified name cannot be found: executionFailure":"{\"error\":{\"code\":2,\"message\":\"TachoAuthService card reservation problem: No available/unreserved card found by company name\"}}
Check if Company card specified in command
\"companyName\":\"companycardnameexample\"}"
is really connected to TT2 or if object is allowed to use it.
Ignition is OFF “Initialization failed (Ignition is required)”
IO 409 and/or IO 5 must be = 1 for the process to start.
Device does not switch to TCP “Tacho download command can't be initiated because switch to TCP is needed”
Records are pending to be delivered {\"error\":{\"code\":13,\"message\":\"Tacho download command can't be initiated when device has pending records\"}}"
Eventually when download starts it fails with following errors from device:
AUTHENTICATED (stucked)
{\"error\":{\"code\":6,\"message\":\"Unexpected subcommand: 9 (ERROR_READING_TACHO_DATA).\"},\"packetStatus\":\"ALL_REPEATS_ARE_EXCEEDED\",\"subcommand\":\"ERROR_READING_TACHO_DATA\"}
UNKNOWN ERROR
{\"error\":{\"code\":6,\"message\":\"Unexpected subcommand: 9 (ERROR_READING_TACHO_DATA).\"},\"packetStatus\":\"ALL_REPEATS_ARE_EXCEEDED\",\"subcommand\":\"ERROR_READING_TACHO_DATA\"}
DEVICE COMMUNICATION ERROR
"error":{"code":6,"message":"Unexpected subcommand: 9 (ERROR_READING_TACHO_DATA)."}
{"code":6,"message":"Tachograph reply. STOP with error: 1 (ACK)."},"packetStatus":"ACK","subcommand":"PROCESS_STOP_RESPONSE"}
executionFailure={"error":{"code":11,"message":"Device responded with ATR and error TASK_ALREADY_IN_PROGRESS"}
{"code":9,"message":"Device responded with ATR and error OTHER_TACHO_DATA_IS_IN_FLASH. Request to delete tacho file was sent"}
Try to upload or reupload the latest FW file or send "delrecords all" to the device.
In some cases, download gets interrupted because channel gets closed (Perhaps due to poor network):
executionFailure={"error":{"code":12,"message":"Channel closed"}}
AUTHORIZATION ERROR
APDU packet not acknowledged. Status: 2 (ERROR)
executionFailure={"error":{"code":3,"message":"Device responded with ATR and error: 2 (ERROR). Tasks available: [TACHOGRAPH_AVAILABLE]."},"packetStatus":"ERROR","subcommand":"ATR_RESPONSE"}
executionFailure":"{\"error\":{\"code\":4,\"message\":\"APDU packet not acknowledged. Status: 7 (SERVER_RESPONSE_TIMEOUT).\"
executionFailure={"error":{"code":11,"message":"Device responded with ATR and error TASK_ALREADY_IN_PROGRESS"}
"error":{"code":15,"message":"TachoAuthService ATR request has failed: Unspecified error"}
executionFailure":"{\"error\":{\"code\":16,\"message\":\"TachoAuthService APDU request has failed: Unspecified error\"}}"
Possible solutions: reset PC, reset device, reset company card rack. https://ruptela.atlassian.net/browse/GUI-29401
Other errors by occurence:
187 Can't read card data from slot 2
120 Device reply timeout
92 Can't read card data from slot 19 Error while saving data (null)
108 APDU packet not acknowledged Status: 7 (SERVER_RESPONSE_TIMEOUT)
64 Device responded with ATR and error TASK_ALREADY_IN_PROGRESS
64 Device responded with ATR and error: 4 (TACHO_RESPONSE_TIMEOUT) Tasks available: []
28 Device responded with ATR and error: 2 (ERROR) Tasks available: [TACHOGRAPH_AVAILABLE, CARD_IN_SLOT1]
28 Device responded with ATR and error: 2 (ERROR) Tasks available: [TACHOGRAPH_AVAILABLE]
12 APDU packet not acknowledged Status: 0 (NACK)
6 APDU packet not acknowledged Status: 2 (ERROR)
3 Unexpected subcommand: 9 (ERROR_READING_TACHO_DATA)
3 Device responded with ATR and error: 0 (NACK) Tasks available: [TACHOGRAPH_AVAILABLE]
2 Device responded with ATR and error OTHER_TACHO_DATA_IS_IN_FLASH Request to delete tacho file was sent
1 Unexpected subcommand: 10 (ERROR_READING_CARD_DATA)
1 Device responded with ATR and error: 2 (ERROR) Tasks available: []
1 Device responded with ATR and error: 0 (NACK) Tasks available: [TACHOGRAPH_AVAILABLE, CARD_IN_SLOT1]
1 APDU packet not acknowledged Status: 3 (TASK_NOT_CREATED)
If APDU is with error, and from device log you see SubID 2 with packet status 6, it means that you need to remove tacho file from device memory, you can do it with "delrecords all" SMS
PS: FW update also removes tacho file from device memory as it resets specific flash memory sectors which includes tacho file and records.
EXPIRED
"{\"error\":{\"code\":902,\"message\":\"Service execution timeout 7200s - tachodownload\"}}"Expired status - will be shown if after authentication there is no answer from the device for 2 hours and all retries from server side was done.
Information got from: