Protocol PST

Hello Anton, I am testing the new protocol included in version 4.7 - PST.
I have a problem, the device sends the positions and the system is translating with a different latitude and longitude than the one captured by the device. presenting a difference of 3 kilometers of distance.

could you verify?
following line sent by the equipment:

2020-01-21 17:37:48  INFO: [33102dc1] connected
2020-01-21 17:37:48  INFO: [33102dc1: pst < 200.186.114.173] HEX: 282faf982768060000002c05506b4969c8090b04000000080c09b500b4f9e52f18e0de0d01fd0f04506b49661014506b4968824913e7889622dd0046010c0000000f110300db01130400000d4c1404b58000001502300db3fe29
2020-01-21 17:37:48  INFO: [33102dc1] id: 800036904, time: 2020-01-21 17:37:40, lat: -9.75085, lon: -36.63482, course: 140.0
2020-01-21 17:38:06  INFO: [33102dc1: pst < 200.186.114.173] HEX: 282faf982768060000002c05506b4969c8090b04000000080c09b500b4f9e52f18e0de0d01fd0f04506b49661014506b4968824913e7889622dd0046010c0000000f110300db01130400000d4c1404b58000001502300db3fe29
2020-01-21 17:38:06  INFO: [33102dc1] id: 800036904, time: 2020-01-21 17:37:40, lat: -9.75085, lon: -36.63482, course: 140.0
2020-01-21 17:38:27  INFO: [33102dc1: pst < 200.186.114.173] HEX: 282faf982768060000002c05506b4969c8090b04000000080c09b500b4f9e52f18e0de0d01fd0f04506b49661014506b4968824913e7889622dd0046010c0000000f110300db01130400000d4c1404b58000001502300db3fe29
2020-01-21 17:38:27  INFO: [33102dc1] id: 800036904, time: 2020-01-21 17:37:40, lat: -9.75085, lon: -36.63482, course: 140.0
2020-01-21 17:38:50  INFO: [33102dc1: pst < 200.186.114.173] HEX: 282faf982768060000002c05506b4969c8090b04000000080c09b500b4f9e52f18e0de0d01fd0f04506b49661014506b4968824913e7889622dd0046010c0000000f110300db01130400000d4c1404b58000001502300db3fe29
2020-01-21 17:38:50  INFO: [33102dc1] id: 800036904, time: 2020-01-21 17:37:40, lat: -9.75085, lon: -36.63482, course: 140.0
2020-01-21 17:39:06  INFO: [33102dc1: pst < 200.186.114.173] HEX: 282faf982768060000002c05506b4969c8090b04000000080c09b500b4f9e52f18e0de0d01fd0f04506b49661014506b4968824913e7889622dd0046010c0000000f110300db01130400000d4c1404b58000001502300db3fe29
2020-01-21 17:39:06  INFO: [33102dc1] id: 800036904, time: 2020-01-21 17:37:40, lat: -9.75085, lon: -36.63482, course: 140.0

Are you using official version 4.7?

Yes, I received this log:

2020-01-21 18:01:46  INFO: [2e9b74a2] connected
2020-01-21 18:01:46  INFO: [2e9b74a2: pst < 200.186.114.173] HEX: 282faf982768060000003505506b5004c8090b040000004a0c09b500b4f9e52f18e0e60d010a0f04506b4efa1014506b5002824913b0889623020044010b000000111103008501130400000d4c1404b580000015023280d15529
2020-01-21 18:01:46  WARN: [2e9b74a2] error - readerIndex(39) + length(80) exceeds writerIndex(87): UnpooledByteBufAllocator$InstrumentedUnpooledHeapByteBuf(ridx: 39, widx: 87, cap: 88) - IndexOutOfBoundsException (... < PstProtocolDecoder:105 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)
2020-01-21 18:01:46  INFO: [2e9b74a2] disconnected
2020-01-21 18:03:42  INFO: [c21d5466] connected
2020-01-21 18:03:42  INFO: [c21d5466: pst < 200.186.114.173] HEX: 282faf982768060000003505506b5004c8090b040000004a0c09b500b4f9e52f18e0e60d010a0f04506b4efa1014506b5002824913b0889623020044010b000000111103008501130400000d4c1404b580000015023280d15529
2020-01-21 18:03:42  WARN: [c21d5466] error - readerIndex(39) + length(80) exceeds writerIndex(87): UnpooledByteBufAllocator$InstrumentedUnpooledHeapByteBuf(ridx: 39, widx: 87, cap: 88) - IndexOutOfBoundsException (... < PstProtocolDecoder:105 < ExtendedObjectDecoder:51 < ... < WrapperContext:102 < ...)

is on a test server:
Link Server
User: admin
password: admin

Link to real-time verification of the system tracker-server.log

where the device is

Log shows that the data is not even decoded, so I'm not sure how the two things are connected.

check the log link above

Link to real-time verification of the system tracker-server.log

where the device is

the route is divergent.
the red cetas was the route I took
the system is decoding something wrong, the PST configuration software log displays the correct latitude and logintude.
I don't know why it is showing divergence, but the equipment is capturing the correct position.

good night, Anton Tananaev, I also have the same problem, the device of the one differs immensely in relation to the correct coordinate ,.
I performed the test on another system that has the protocol for this device, and it presented correct positioning, if you wish, I can provide you with the complete protocol of the device
whatsapp [removed]