eusonlito / GPS-Tracker

GPS Tracker platform for Sinotrack, Coban, Teltonika, Concox, Jimilab, OsmAnd and Queclink devices built with Laravel 11 + PHP 8.2 and MySQL 8. Plataforma GPS Tracker para dispositivos Sinotrack Sinotrack, Coban, Teltonika, Concox, Jimilab, OsmAnd y Queclink creada con Laravel 11 + PHP 8.2 y MySQL 8.
https://tracker-demo.lito.com.es/
MIT License
137 stars 62 forks source link

Problem with coban protocol #35

Closed sajjadintel closed 6 months ago

sajjadintel commented 6 months ago

Hi, Thanks for your hard work.

Coban devices sometimes send multiple data together. I don't know why but sometimes it happens and only the first one is considered and result is jump in location on the map.

Only one data is sent:

[2024-01-06T11:13:20+00:00] imei:868166056076334,001,240106144319,,F,111319.000,A,3530.66277,N,04610.23361,E,17.52,204.23,,1,1,0.00%,,;

Multiple data is sent:

[2024-01-06T11:09:07+00:00] ##,imei:868166056076334,A;imei:868166056076334,001,240106143749,,F,110749.000,A,3531.00191,N,04610.22611,E,9.91,188.51,,1,1,0.00%,,;imei:868166056076334,001,240106143759,,F,110759.000,A,3530.97760,N,04610.22360,E,8.37,180.87,,1,1,0.00%,,;imei:868166056076334,001,240106143809,,F,110809.000,A,3530.95149,N,04610.22457,E,8.21,173.89,,1,1,0.00%,,;imei:868166056076334,001,240106143819,,F,110819.000,A,3530.92937,N,04610.22475,E,9.13,186.42,,1,1,0.00%,,;imei:868166056076334,001,240106143829,,F,110829.000,A,3530.90256,N,04610.22213,E,10.71,189.00,,1,1,0.00%,,;imei:868166056076334,001,240106143839,,F,110839.000,A,3530.87432,N,04610.21685,E,9.33,184.25,,1,1,0.00%,,;imei:868166056076334,001,240106143849,,F,110849.000,A,3530.84773,N,04610.21385,E,10.30,186.39,,1,1,0.00%,,;imei:868166056076334,acc off,240106143858,,F,110858.000,A,3530.83202,N,04610.21109,E,0.00,200.63,,0,1,0.00%,,;imei:868166056076334,001,240106143859,,F,110859.000,A,3530.83196,N,04610.21114,E,0.00,200.63,,0,1,0.00%,,;
[2024-01-06T11:07:06+00:00] ##,imei:868166056076334,A;imei:868166056076334,acc on,240106143539,,F,110539.000,A,3531.17871,N,04610.08326,E,0.00,111.86,,1,1,0.00%,,;imei:868166056076334,001,240106143539,,F,110539.000,A,3531.17871,N,04610.08326,E,0.00,111.86,,1,1,0.00%,,;imei:868166056076334,001,240106143549,,F,110549.000,A,3531.17935,N,04610.08511,E,2.70,72.30,,1,1,0.00%,,;imei:868166056076334,001,240106143549,,F,110549.000,A,3531.17935,N,04610.08511,E,2.70,72.30,,1,1,0.00%,,;imei:868166056076334,001,240106143559,,F,110559.000,A,3531.17765,N,04610.11152,E,10.30,98.63,,1,1,0.00%,,;imei:868166056076334,001,240106143609,,F,110609.000,A,3531.17297,N,04610.14989,E,12.26,99.44,,1,1,0.00%,,;imei:868166056076334,001,240106143619,,F,110619.000,A,3531.16713,N,04610.19253,E,12.92,102.61,,1,1,0.00%,,;imei:868166056076334,001,240106143629,,F,110629.000,A,3531.16211,N,04610.23589,E,11.80,98.17,,1,1,0.00%,,;imei:868166056076334,001,240106143634,,F,110634.000,A,3531.15897,N,04610.24923,E,5.47,134.39,,1,1,0.00%,,;imei:868166056076334,001,240106143636,,F,110636.000,A,3531.15629,N,04610.25175,E,7.35,158.41,,1,1,0.00%,,;imei:868166056076334,001,240106143639,,F,110639.000,A,3531.15047,N,04610.25191,E,7.38,188.68,,1,1,0.00%,,;imei:868166056076334,001,240106143649,,F,110649.000,A,3531.13199,N,04610.24797,E,6.54,188.91,,1,1,0.00%,,;imei:868166056076334,001,240106143659,,F,110659.000,A,3531.11248,N,04610.24535,E,6.99,186.17,,1,1,0.00%,,;
image
eusonlito commented 6 months ago

Okey, let me see :)

eusonlito commented 6 months ago

Can you send me the full day log by mail? To recreate the full trip.

eusonlito commented 6 months ago

Ok, I have checked the logs and I have seen that the device has not sent anything in those missing intervals, for example it has reported position at 2024-01-06 12:40:44 (240106124044) (always UTC time):

[2024-01-06T09:10:46+00:00] imei:868166056076334,001,240106124044,,F,091044.000,A,3530.80415,N,04610.21698,E,5.53,1.57,,1,1,0.00%,,;

then it has reported position at 2024-01-06 12:40:47 (240106124047) (three seconds later that is not recorded because there is not enough movement):

[2024-01-06T09:10:49+00:00] imei:868166056076334,001,240106124047,,F,091047.000,A,3530.80939,N,04610.21710,E,6.33,0.51,,1,1,0.00%,,;

and the next report is at 2024-01-06 12:42:27 (240106124227):

[2024-01-06T09:12:29+00:00] imei:868166056076334,001,240106124227,,F,091227.000,A,3530.99770,N,04610.13982,E,11.36,276.33,,1,1,0.00%,,;

And the same for the following jumps:

[2024-01-06T09:12:49+00:00] imei:868166056076334,001,240106124247,,F,091247.000,A,3531.00986,N,04610.05360,E,11.34,282.91,,1,1,0.00%,,;
[2024-01-06T09:12:56+00:00] imei:868166056076334,001,240106124254,,F,091254.000,A,3531.02322,N,04610.03713,E,11.21,3.52,,1,1,0.00%,,;
[2024-01-06T09:14:26+00:00] imei:868166056076334,001,240106124414,,F,091414.000,A,3531.35855,N,04610.14962,E,9.12,46.27,,1,1,0.00%,,;
eusonlito commented 6 months ago

Also I have checked the multiple points sent in a single communication, and they are registering correctly.

eusonlito commented 6 months ago

I think it is solved. There was a problem in how the server managed connections and under certain circumstances it generated a block that did not allow incoming connections for 2 minutes. Now it should always work correctly. Thank you very much for the report.

sajjadintel commented 6 months ago

Cool. Thanks for your support and hard work. appreciate it.