Trying to understand decode of message with two different speed outputs of 64.8 and 0 at same log file time stamp

visiondrive7 years ago

Anton - I have a problem with a Teltonika device model FM3622 reporting high speeds (incorrectly) when the device is not moving. I am providing advice to Teltonika but I noticed this below where the incorrect speed and correct speed are displayed with the exact same server time stamp.

Earlier messages and only one before the one below.

2017-09-21 16:48:04  INFO: [D14A0EB6] connected
2017-09-21 16:48:06 DEBUG: [D14A0EB6: 5027 < 1.144.97.68] HEX: 000f333531353830303531353132333936
2017-09-21 16:48:06 DEBUG: [D14A0EB6: 5027 > 1.144.97.68] HEX: 01
2017-09-21 16:48:07 DEBUG: [D14A0EB6: 5027 < 1.144.97.68] HEX: 000000000000002908010000015ea3310f580056736c13e9a52e340000000000000018030101000242641918000500000100005725
2017-09-21 16:48:07 DEBUG: [D14A0EB6: 5027 > 1.144.97.68] HEX: 00000001
2017-09-21 16:48:07  INFO: [D14A0EB6] id: 351580051512396, time: 2017-09-21 16:47:35, lat: -37.50507, lon: 145.04049, speed: 0.0, course: 0.0

Next message:

2017-09-21 16:52:34  INFO: [901F36E2] connected
2017-09-21 16:52:36 DEBUG: [901F36E2: 5027 < 1.144.97.68] HEX: 000f333531353830303531353132333936
2017-09-21 16:52:36 DEBUG: [901F36E2: 5027 > 1.144.97.68] HEX: 01
2017-09-21 16:52:37 DEBUG: [901F36E2: 5027 < 1.144.97.68] HEX: 000000000000004f08020000015ea33555180056649906e995f6d400da004a09000018030101000242648e18000500000000015ea33539c0005664b3fae995f5ea012000520400780003010100024264a21800430000020000b26b
2017-09-21 16:52:37 DEBUG: [901F36E2: 5027 > 1.144.97.68] HEX: 00000002

2017-09-21 16:52:38 DEBUG: SMS submitted, message id: F93E949F-A04F-4480-8D50-8D9AD5FE0540

2017-09-21 16:52:38  INFO: [901F36E2] id: 351580051512396, time: 2017-09-21 16:52:08, lat: -37.60482, lon: 144.94403, speed: 64.8, course: 82.0

2017-09-21 16:52:38  INFO: [901F36E2] id: 351580051512396, time: 2017-09-21 16:52:15, lat: -37.60479, lon: 144.94334, speed: 0.0, course: 74.0
Anton Tananaev7 years ago

It looks like device issue.

visiondrive7 years ago

In discussion with Teltonika we have enabled Static Navigation Filtering so that artificial jumps in location when not moving are not sent to the server.