onnected my TK103-2 on Server IP Address: 193.193.165.37
Port: 32329

location is not shown and toolbox show the below error

[02/12/2019 22:17:48] 301: device disconnected (data parsing error (see log details))
{
close_code : 6
duration : 1
error_text : “[chinese-generic.spvm:26:6, input 008c08 11 000001] got more split items than expected”
event_code : 301
event_origin : “gw/devices/281085″
event_text : “196.158.148.74/disconnected”
id : 281085
ident : “359772036696376″
msgs : 0
origin_id : 281085
origin_type : 11
recv : 173
send : 0
source : “196.158.148.74”
timestamp : 1575317868.252407
transport : “tcp”
}

191203050653,+201200000036,GPRMC,210653.000,A,3006.1026,N,03120.5428,E,0.00,0.00,021219,,,A*6F,F,, imei:359772036696376,08,76.8,F:4.10V,1,138,61540,602,02,5533,9360,5.96km

Thanks namo for your prompt support
Device is now pointing to the above port
I configured the device to send location update every 1 minute

MichaelWaheeb
I've checked all possible acks with your device, but it still sends the same message in the loop.
Contact manufacturer's tech support to solve this issue.
You can now switch your device back to GPS Trace ip:port - I don't use it any more.

namo I need to understand the exact issue to investigate, I set a 1 minute time interval for the device to refresh the location
if the device isn't moving it's normal that the device sends the same message every minute.
can you please send me a sample of the duplicate message and what does ACK mean? it is a TCP ACK?

MichaelWaheeb
Here is a packet from your device:
0000000 31 39 31 32 30 33 31 35 33 31 31 32 2C 2B 32 30 191203153112,+20
0000010 31 32 32 34 33 35 35 30 33 36 2C 47 50 52 4D 43 1224355036,GPRMC
0000020 2C 30 37 33 31 31 32 2E 30 30 30 2C 41 2C 33 30 ,073112.000,A,30
0000030 30 31 2E 34 38 38 30 2C 4E 2C 30 33 31 32 37 2E 01.4880,N,03127.
0000040 32 38 32 31 2C 45 2C 37 2E 38 30 2C 32 38 30 2E 2821,E,7.80,280.
0000050 34 33 2C 30 33 31 32 31 39 2C 2C 2C 41 2A 36 41 43,031219,,,A*6A
0000060 2C 4C 2C 2C 20 69 6D 65 69 3A 33 35 39 37 37 32 ,L,,.imei:359772
0000070 30 33 36 36 39 36 33 37 36 2C 30 36 2C 32 38 32 036696376,06,282
0000080 2E 33 2C 46 3A 34 2E 31 30 56 2C 31 2C 31 34 31 .3,F:4.10V,1,141
0000090 2C 34 39 37 30 2C 36 30 32 2C 30 32 2C 37 39 38 ,4970,602,02,798
00000A0 39 2C 33 35 30 32 2C 34 38 2E 37 30 6B 6D 0D 0A 9,3502,48.70km..

Same in text representation:
191203153112,+201224355036,GPRMC,073112.000,A,3001.4880,N,03127.2821,E,7.80,280.43,031219,,,A*6A,L,, imei:359772036696376,06,282.3,F:4.10V,1,141,4970,602,02,7989,3502,48.70km

If it's normal for this device to send the same message every minute when it's not moving - so it's OK. No issue and nothing to investigate.
My concern was the device sends the same message because it's waits for an acknowledgement from server. But actually the device was indifferent to all possible replies for Xexun and Coban protocols.

Thus, the case is closed.

namo Thanks for your awesome support 😀 parsing is working perfectly now.
If possible send me the XEXUN commands as I need to test controlling the device from web
Or if you have any link for the protocol reference and documentation I would be greatfull

MichaelWaheeb
What device id?

namo
#281085

MichaelWaheeb
Your device is stopped and sends the same message in loop again.
To debug the timestamp issue with your device I need it to send real-time messages.
I suggest you to drive your car so that to un-loop the device. Is it possible?

Probably this will happen within 2 hours 😀
Will let u know by then