This is a Micodus MV720 that has presented some odd behavior. I noticed some times routes or travels have some missing poins/markers on map, so I went to watch the log and found this.
Between 17h:11m:55s and 17h:13m:05s It seems there's some data missing, but I don't know how to diagnose it. ¿May be device not reporting whole data or maybe server didn't "understood it"
(map image below)
2021-10-25 17:11:46 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20114625102134482414040561542622032119fffffbffff00079a0000005702ec0100000000009217
2021-10-25 17:11:46 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:11:46, lat: -34.80402, lon: -56.25710, speed: 32.0, course: 119.0
2021-10-25 17:11:50 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20114925102134482547040561539792032119fffffbffff000d9a0000005702ec0100000000009218
2021-10-25 17:11:50 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:11:49, lat: -34.80425, lon: -56.25663, speed: 32.0, course: 119.0
2021-10-25 17:11:53 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20115225102134482679040561536972032119fffffbffff000d9a0000005702ec0100000000009219
2021-10-25 17:11:53 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:11:52, lat: -34.80447, lon: -56.25616, speed: 32.0, course: 119.0
2021-10-25 17:11:55 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20115525102134482810040561534092032118fffffbffff000d9a0000005802ec010000000000921a
2021-10-25 17:11:55 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:11:55, lat: -34.80468, lon: -56.25568, speed: 32.0, course: 118.0
2021-10-25 17:11:59 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20115825102134482940040561531272032118fffffbffff00109a0000005802ec010000000000921b
2021-10-25 17:12:02 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20120125102134483060040561528652028118fffffbffff00109a0000005802ec010000000000921c
2021-10-25 17:12:05 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20120425102134483167040561526222026120fffffbffff00109a0000005802ec010000000000901d
2021-10-25 17:12:08 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20120725102134483260040561524182021118fffffbffff00109a0000005802ec010000000000901e
2021-10-25 17:12:11 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20121025102134483315040561522882010116fffffbffff00129a0000005802ec010000000000901f
2021-10-25 17:12:14 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20121325102134483334040561522342004085fffffbffff0012990000005802ec0100000000008f20
2021-10-25 17:12:17 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20121625102134483333040561522242003074fffffbffff00129a0000005802ec0100000000008f21
2021-10-25 17:12:19 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20121925102134483333040561522242003074fffffbffff00129a0000005802ec0100000000009022
2021-10-25 17:12:23 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20122225102134483328040561522242005045fffffbffff00129a0000005802ec0100000000009023
2021-10-25 17:12:24 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20122425102134483287040561522092011000fffffbffff00129a0000005802ec0100000000009224
2021-10-25 17:12:29 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20122825102134483119040561522622019337fffffbffff00109a0000005802ec0100000000009225
2021-10-25 17:12:31 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20123125102134482952040561523452023338fffffbffff00109a0000005802ec0100000000009226
2021-10-25 17:12:35 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20123425102134482779040561524292021336fffffbffff00109a0000005802ec0100000000009227
2021-10-25 17:12:38 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20123725102134482632040561525042017336fffffbffff00109a0000005802ec0100000000009228
2021-10-25 17:12:41 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20124025102134482522040561525572011337fffffbffff00139a0000005802ec0100000000009329
2021-10-25 17:12:43 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20124325102134482432040561525992012339fffffbffff00139a0000005802ec010000000000932a
2021-10-25 17:12:47 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20124625102134482347040561526342010342fffffbffff00139a0000005802ec010000000000932b
2021-10-25 17:12:50 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20124925102134482323040561526432009342fffffbffff00159a0000005802ec010000000000902c
2021-10-25 17:12:53 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20125225102134482226040561526802006342fffffbffff00159a0000005802ec010000000000902d
2021-10-25 17:12:55 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20125525102134482168040561527042008340fffffbffff00159a0000005802ec010000000000932e
2021-10-25 17:12:59 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20125825102134482109040561527312007340fffffbffff00159a0000005802ec010000000000922f
2021-10-25 17:13:02 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20130125102134482057040561527522007346fffffbffff00159a0000005802ec0100000000009230
2021-10-25 17:13:04 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 2a48512c373230313133363237352c56312c3230313330332c412c333434382e323031362c532c30353631352e323736382c572c3030372e39302c3334332c32
2021-10-25 17:13:04 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 35313032312c46464646464246462c3734382c30312c302c302c3423
2021-10-25 17:13:05 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20130425102134481996040561527752008339fffffbffff00159a0000005802ec0100000000009331
2021-10-25 17:13:05 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:13:04, lat: -34.80333, lon: -56.25463, speed: 8.0, course: 339.0
¿May be this due to slow movement speed?
https://i.imgur.com/tMHxRRY.png
Assuming you haven't stripped some important information from the log, it looks like some data is not decoded for some reason. Do you have any external services configured in Traccar (geocoding/geolocation/forwarding etc)?
I stripped only before and after this segment and edited inside what I think may be sensitive data, everything else is as server shows. (not even other devices data mixed in the middle)
I have reverse geocoding to solve addresses enabled but only works upon user request. (click dot on map or line on report, and "show address") And I'm the one that uses it the most often... But I was the one driving when this happened, so it was not being used.
I'm currently handling around 12 devices live all time on 1GB RAM, 1 core server running bare debian. (no graphical interface, nothing else than traccar) As far as I could find CPU seems to be always almost idle (0.00 load average) and memory is never over 800MB no matter the load.
Only 2 protocols enabled.
¿Is there any way that I can force decrypting or recover that data somehow?
GPS has the ability to save data on an internal memory in case there's no internet and then upload it in bulk, but this behavior is the first time I have seen. Other times devices uploaded up to 10 hours of data and everything went fine.
Now I tried to decode one data line and traccar hex converter tells me "Binary Hex can't be converted to Text"
It's a binary format, so hex decoder won't help you here.
The problem is likely with frame decoding. There was a long thread about it somewhere on the forum. TLDR is you need to configure h02.messageLength to match your binary message lengths.
Yes. The value has to match your message length though.
Ok, great. Understood, but how I find the correct length, trial and error?
I find 94 chars line 128 chars line 56, 184... (2/bit) It's quite messy.
Since the closest one to a correctly decoded data line (last) is 94 chars should I go with 47 bits? (trying that now actually)
2021-10-25 17:13:02 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20130125102134482057040561527522007346fffffbffff00159a0000005802ec0100000000009230
2021-10-25 17:13:04 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 2a48512c373230313133363237352c56312c3230313330332c412c333434382e323031362c532c30353631352e323736382c572c3030372e39302c3334332c32
2021-10-25 17:13:04 INFO: [ba569993: h02 < ip.of.my.gps] HEX:
35313032312c46464646464246462c3734382c30312c302c302c3423
2021-10-25 17:13:05 INFO: [ba569993: h02 < ip.of.my.gps] HEX: 24MYDEVICEID20130425102134481996040561527752008339fffffbffff00159a0000005802ec0100000000009331
2021-10-25 17:13:05 INFO: [ba569993] id: MYDEVICEID, time: 2021-10-25 17:13:04, lat: -34.80333, lon: -56.25463, speed: 8.0, course: 339.0
You need to look at the length of binary messages, which looks like 94, so 47 is the answer. Not bits, but bytes.
yes, and I just realised there are arrows in two directions so I assume one is for server to GPS and other is for GPS to server messages....
Server to GPS are 94 but GPS to server are 72, so I guess it should be 36 actually
Arrows are directions, but I think you mixed them up. You need the one with arrow pointing to the IP address of your device (right).
I assumed:
h02 > deviceip
meant server to gps while
h02 < deviceip
meant device to server // and this being the one needed to handle. This is the 94 chars line and 72 is the other one
maybe the sign is not meant as an arrow and i'm completely messing it up... :) ... sorry.
Correct. That's the opposite from what you said earlier.
yes, i just messed up, it seems too much information for my brain to process currently...
Thanks a lot. (still don't know if solved))
This is a Micodus MV720 that has presented some odd behavior. I noticed some times routes or travels have some missing poins/markers on map, so I went to watch the log and found this.
Between 17h:11m:55s and 17h:13m:05s It seems there's some data missing, but I don't know how to diagnose it. ¿May be device not reporting whole data or maybe server didn't "understood it"
(map image below)
¿May be this due to slow movement speed?
https://i.imgur.com/tMHxRRY.png