Issue with Teltonika and queued commands

Norm5 years ago

I have a Teltonika FM3612. When I send it an engine stop command while offline. The device doesn't comply when it comes online. Is there a way to delay the queued commands for a certain time period (5 or 10 seconds)? Have you seen behavior from devices like this before?

Teltonika is sent an Engine Stop command. It is queued as device is not online.

2019-03-03 21:56:33  INFO: [8d08fd3b] connected
2019-03-03 21:56:34  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000f383637303630303335373634353834
2019-03-03 21:56:34  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 01
2019-03-03 21:56:34  INFO: [8d08fd3b] id: 867060035764584, command type: custom sent
2019-03-03 21:56:34  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000000000000160c01050000000e7365746469676f75742031310d0a010000e258
2019-03-03 21:56:36  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000002b080100000169458ed75801c77e4689170dc0eb013c00000f0000ef0402b300ef01024234da43104e0000010000a8fa
2019-03-03 21:56:36  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:56:36  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:56:23, lat: 38.77773, lon: -94.90257, course: 0.0
2019-03-03 21:56:39  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000002b080100000169458ecf8800c77e4689170dc0eb013c00000f0000000402b300ef00024234d843104e0000010000c25e
2019-03-03 21:56:39  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:56:39  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:56:21, lat: 38.77773, lon: -94.90257, course: 0.0

Teltonika is sent an Engine Stop command. Works fine as device is already online.

2019-03-03 21:57:13  INFO: [8d08fd3b] id: 867060035764584, command type: custom sent
2019-03-03 21:57:13  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000000000000160c01050000000e7365746469676f75742031310d0a010000e258
2019-03-03 21:57:14  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000003a0c0106000000324469676974616c204f757470757473206172652073657420746f3a2031312e2054696d656f757473206172653a203020302e0100005030
2019-03-03 21:57:14  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:57:15  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:56:23, lat: 38.77773, lon: -94.90257, course: 0.0, result: Digital Outputs are set to: 11. Timeouts are: 0 0.
2019-03-03 21:57:17  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000002b080100000169458fa27801c77e4689170dc0eb013c00000d0000b30402b301ef01024234c143104d0000010000edb7
2019-03-03 21:57:17  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:57:18  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:57:15, lat: 38.77773, lon: -94.90257, course: 0.0

Teltonika is sent an Engine Start command Works fine as device is already online.

2019-03-03 21:57:36  INFO: [8d08fd3b] id: 867060035764584, command type: custom sent
2019-03-03 21:57:36  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000000000000160c01050000000e7365746469676f75742030300d0a010000de64
2019-03-03 21:57:37  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000003a0c0106000000324469676974616c204f757470757473206172652073657420746f3a2030302e2054696d656f757473206172653a203020302e010000002d
2019-03-03 21:57:37  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:57:37  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:57:15, lat: 38.77773, lon: -94.90257, course: 0.0, result: Digital Outputs are set to: 00. Timeouts are: 0 0.
2019-03-03 21:57:41  INFO: [8d08fd3b: 5027 < 208.54.80.235] HEX: 000000000000002b080100000169458ffc5001c77e4689170dc0eb013d0000110000b30402b300ef01024234bf43104d0000010000e92c
2019-03-03 21:57:41  INFO: [8d08fd3b: 5027 > 208.54.80.235] HEX: 00000001
2019-03-03 21:57:41  INFO: [8d08fd3b] id: 867060035764584, time: 2019-03-03 21:57:38, lat: 38.77773, lon: -94.90257, course: 0.0
Anton Tananaev5 years ago

Seems like device issue. Currently there is no way to delay the command.