castel pt-690
It looks like the protocol is slightly different from what I implemented. Please provide protocol documentation to fix the problem.
Dear Anton,
this is the protocol, provided directly from the manufacturer
http://roscica2.serverlet.com/owncloud/index.php/s/10A94CtG5cu5AJt
Thx
The protocol turned out to be quite different from the original one. Here is a new build with support for this protocol:
https://www.dropbox.com/s/myt68q5u7fiz49r/tracker-server-jar-with-dependencies.jar?dl=0
thanks, it works fine
If you are interested I have another protocol for another device with MTK chipset
Yes, I am interested. What's the device brand and model?
concox model wetrack2, this is the protocol
http://roscica2.serverlet.com/owncloud/index.php/s/1RV6dGtjUwCdags
I tested the pt-690 but after the first time it sends the coordinates. He begins to write debug messages and no longer sends the position.
2015-10-30 12:19:44 DEBUG: [6EC1AA10: 5086 < 5.90.160.93] HEX: 404044000c3631313135303030303935360000000000000000420600011e0a0f0b1312864fcd08c07a13030100640acf000004000a000000000000007ba083a66ad80d0a
Concox protocol is a standard GT06 protocol (port 5023 in Traccar).
As for Castel, those messages are heartbeats. Here is a new build which should send correct response for those messages:
https://www.dropbox.com/s/myt68q5u7fiz49r/tracker-server-jar-with-dependencies.jar?dl=0
Hi,
now you see this in the log.
but the position is not longer detected.
except the first time.
http://roscica2.serverlet.com/owncloud/index.php/s/v6FU9oDQuGRqiut
Update:
if restart the process with 'Service traccar restart' resumes again the position but always only once.
Fixed the problem. Here is a new build:
https://www.dropbox.com/s/myt68q5u7fiz49r/tracker-server-jar-with-dependencies.jar?dl=0
Ok, now it works well, but
traccar not support the position with LBS?
Thanks
Traccar doesn't support LBS at the moment, but it's in plans.
ok thanks, but the strange thing is that the device sends the coordinates.
with wrong date, but sends
5086 < 5.90.141.173] HEX: 40405c000c3631313135303030303935360000000000000000400101010400031ad899ca0886e90b03000000000300000000ff000000000000007ba0a7ca50542d3639305f56312e312e320050542d3639302056312e320028c60d0a 2015-11-04 09:27:01 DEBUG: [AD5F5E24: 5086 > 5.90.141.173] HEX: 40401f000c3631313135303030303935360000000000000000800159560d0a 2015-11-04 09:27:02 INFO: [AD5F5E24] id: 2, time: Thu Jan 01 01:03:26 CET 2004, lat: 40.97094, lon: 14.197868333333334, speed: 0.0, course: 0.0
So that sounds like it's it. xD
Hello,
I have this GPS tracker, Castel pt-690, but it does not work, and this' log me out.
2015-10-28 15:54:28 DEBUG: [240C20E6: 5086 < 5.90.233.168] HEX: 40405c000c363131313530303030393536000000000000000040011c0a0f0e362dca53cd0860831303000000000300000000ff000000000000007ba083a650542d3639305f56312e312e320050542d3639302056312e32008a020d0a
2015-10-28 15:54:28 WARN: [240C20E6] error - Not enough readable bytes - Need 4, maximum is 0 - IndexOutOfBoundsException (... < CastelProtocolDecoder:65 < *:162 < ExtendedObjectDecoder:39 < ...)
2015-10-28 15:54:28 INFO: [240C20E6] disconnected