Using Traccar with Topin Locator Protocol

s roychowdhury5 years ago

Hi:
I have a set of small GPS devices from a Chinese manufacturer that use the above protocol.
It seems gt06 at port 5023 does not work for this, so can you please tell me which port to test with ?

Log says:

2019-08-13 10:04:56  INFO: [584c23ea] connected
2019-08-13 10:04:56  INFO: [584c23ea: gt06 < 106.206.19.55] HEX: 78780d0103593390754336414d0d0a
2019-08-13 10:04:56  INFO: [584c23ea: gt06 > 106.206.19.55] HEX: 787805014336f0ee0d0a
2019-08-13 10:05:01  INFO: [584c23ea: gt06 < 106.206.19.55] HEX: 78780717190813100440ac84c617fff44474dadaa087bf49b04e26b0918c53608e08744bd156e0cbbc48cb895754b802c577c359ac84c617d93c5e0401942d61f008ec4661f008eb4661f02c3b5061f008ea50000d0a
2019-08-13 10:05:01  INFO: [584c23ea: gt06 > 106.206.19.55] HEX: 787800171908131004400d0a
2019-08-13 10:05:01  INFO: [584c23ea] id: 3593**********1, time: 1970-01-01 00:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2019-08-13 10:05:10  INFO: [584c23ea: gt06 < 106.206.19.55] HEX: 7878151013080d0a050a9701633fa40853d1d20034590389000d0a
2019-08-13 10:05:10  WARN: [584c23ea] error - readerIndex(8) + length(1) exceeds writerIndex(8): PooledSlicedByteBuf(ridx: 8, widx: 8, cap: 8/8, unwrapped: PooledHeapByteBuf(ridx: 8, widx: 27, cap: 512)) - IndexOutOfBoundsException (... < Gt06ProtocolDecoder:213 < *:708 < *:514 < *:1018 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2019-08-13 10:05:10  INFO: [584c23ea] disconnected
Xavier Schreiber5 years ago

Hi
The following packet sent from your tracker

78780717190813100440ac84c617fff44474dadaa087bf49b04e26b0918c53608e08744bd156e0cbbc48cb895754b802c577c359ac84c617d93c5e0401942d61f008ec4661f008eb4661f02c3b5061f008ea50000d0a

Is not a localisation data but a bundle of wifi AP observed by the tracker to be used in a LBS localisation process by the original server (365gps.net)
Try to continue using the tracker in open sky ground to get a GPS fix, and you should see a coordinate on your Traccar instance

You will sadly see that the GT06 protocol doesn't fit exactly to the Topin one

You can look at this thread