JT701 on Traccar
Please provide logs starting from "connect" message. Also, what version of Traccar are you using?
Not sure what happened but I just received an online message via email. So the devices seems to be connected now.
Version 3.11
Here are the logs in any case:
2017-11-15 10:01:24 INFO: [B108AA74] connected
2017-11-15 10:01:24 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c404a5429
2017-11-15 10:01:26 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c404a5429
2017-11-15 10:01:28 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681713002701010000000100000000000000000e000000000000000000000000a05a0000000000000f0f0f002475609215681712002701010000000300000000000000000e000000000000000000000010205a0000000000000f0f0f002475609215681712002701010000002200000000000000000e00000000000000000000006020550000000000000f0f0f002475609215681712002701010000002700000000000000000e00000000000000000000006020550000000000000f0f0f012475609215681712002701010000003800000000000000000e000000000000000000000030e0550000000000000f0f0f022475609215681712002701010000004700000000000000000e000000000000000000000030e0550000000000000f0f0f032475609215681713002701010000005700000000000000000e000000000000000000000020e0550000000000000f0f0f002475609215681713002701010000000100000000000000000e000000000000000000000020e05a0000000000000f0f0f002475609215681712002701010000000300000000000000000e000000000000000000000060205a0000000000000f0f0f002475609215681712002701010000001200000000000000000e00000000000000000000006060550000000000000f0f0f00
2017-11-15 10:01:29 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c5034352c3031303130302c3030303031382c302e3030303030302c4e2c302e3030303030302c452c562c302e30302c302c352c302c303030303030303030302c302c302c3029
2017-11-15 10:01:59 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710025146125990006087823e000000000000000000000020c1551b5e0aa71b000f0f0f14
2017-11-15 10:02:23 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710032246126608006088124e000000000000000000000020c15512850dcf0d000f0f0f15
2017-11-15 10:02:36 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681712002701010000002200000000000000000e00000000000000000000006020550000000000000f0f0f012475609215681713002701010000000100000000000000000e000000000000000000000000a05a0000000000000f0f0f002475609215681712002701010000000300000000000000000e00000000000000000000001020ff0000000000000f0f0f002475609215681712002701010000000400000000000000000e00000000000000000000004020ff0000000000000f0f0f012475609215681713002701010000003200000000000000000e000000000000000000000000a0ff0000000000000f0f0f002475609215681712002701010000003400000000000000000e00000000000000000000001020ff0000000000000f0f0f002475609215681712002721081709093400000000000000000e000000000000000000000001205f0000000000000f0f0f012475609215681712002721081709093522348560113550287f000000000000050000000010205f0000000000000f0f0f022475609215681712002721081709094822348594113550252f000000000000050000000030605a0000000000000f0f0f032475609215681712002721081709094922348592113550255f000000000000050000000040205a0000000000000f0f0f04
2017-11-15 10:02:37 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c5034352c3031303130302c3030303032312c302e3030303030302c4e2c302e3030303030302c452c562c302e30302c302c312c312c303030383934373834382c302c302c3129
2017-11-15 10:02:53 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710035246126608006088124e000000000000000000000020c15512850dcf0e000f0f0f16
2017-11-15 10:03:23 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710042146126608006088124e000000000000000000000020c15512850dcf0e000f0f0f17
2017-11-15 10:03:45 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681712002721081709095122348585113550259f000000000000050000000030205a0000000000000f0f0f002475609215681713002701010000000100000000000000000e000000000000000000000000a05a0000000000000f0f0f002475609215681712002701010000000300000000000000000e000000000000000000000010205a0000000000000f0f0f002475609215681712002701010000000400000000000000000e000000000000000000000040205a0000000000000f0f0f012475609215681713002701010000000100000000000000000e000000000000000000000000a0550000000000000f0f0f002475609215681712002701010000000300000000000000000e00000000000000000000003020ff0000000000000f0f0f002475609215681712002701010000000600000000000000000e00000000000000000000001020ff0000000000000f0f0f012475609215681712002701010000002900000000000000000e00000000000000000000001020ff0000000000000f0f0f022475609215681712002701010000003900000000000000000e00000000000000000000001020ff0000000000000f0f0f032475609215681712002701010000005300000000000000000e00000000000000000000001020ff0000000000000f0f0f04
2017-11-15 10:03:46 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c5034352c3031303130302c3030303032342c302e3030303030302c4e2c302e3030303030302c452c562c302e30302c302c352c302c303030303030303030302c302c302c3229
2017-11-15 10:03:53 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710045246126608006088124e000000000000000000000020c15512850dcf0e000f0f0f18
2017-11-15 10:04:23 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710052246126608006088124e000000000000000000000020c15512850dcf0f000f0f0f19
2017-11-15 10:04:53 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710055246126608006088124e000000000000000000000020c15512850dcf0e000f0f0f1a
2017-11-15 10:04:56 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681712002701010000010100000000000000000e000000000000000000000010205a0000000000000f0f0f052475609215681713002701010000010200000000000000000e000000000000000000000020205a0000000000000f0f0f012475609215681712002701010000010300000000000000000e000000000000000000000030205a0000000000000f0f0f062475609215681712002701010000011300000000000000000e00000000000000000000001060550000000000000f0f0f072475609215681712002701010000011400000000000000000e00000000000000000000004020550000000000000f0f0f082475609215681713002701010000000100000000000000000e000000000000000000000000e0550000000000000f0f0f002475609215681712002701010000000300000000000000000e000000000000000000000010e0550000000000000f0f0f002475609215681712002701010000004000000000000000000e000000000000000000000010e0550000000000000f0f0f012475609215681713002701010000000100000000000000000e00000000000000000000000020550000000000000f0f0f002475609215681712002701010000000300000000000000000e000000000000000000000010e0550000000000000f0f0f00
2017-11-15 10:04:56 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 28373536303932313536382c5034352c3031303130302c3030303032362c302e3030303030302c4e2c302e3030303030302c452c562c302e30302c302c312c312c303030383934373834382c302c302c3329
2017-11-15 10:05:23 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710062146126608006088124e000000000000000000000020c15512850dcf0e000f0f0f1b
2017-11-15 10:05:53 DEBUG: [B108AA74: 5014 < 178.197.227.74] HEX: 2475609215681711002715111710065246126608006088124e000000000000000000000020c15512850dcf0d000f0f0f1c
2017-11-15 10:06:36 INFO: [DFA0CCA9] connected
2017-11-15 10:06:36 DEBUG: [DFA0CCA9: 5014 < 178.197.234.72] HEX: 28373536303932313536382c404a5429
2017-11-15 10:06:38 DEBUG: [DFA0CCA9: 5014 < 178.197.234.72] HEX: 28373536303932313536382c404a5429
@ @
"tracker-server.log" 162L, 58820CYou should upgrade first and see if it solves the issue.
Hi,
We're having similar issues with our JT701 device / traccar server (3.14). We cannot seem to get it to work... the device is appearing as offline and Last Update field is blank. We've tried both the device IMEI and device ID.
We're willing to configure our device to one of you dev servers if it helps with the troubleshooting.
Device protocol documentation can be downloaded from here:
Wireshark trace can be downloaded from here:
Below are the logs:
2017-12-04 17:50:30 INFO: [E09B31A5] connected
2017-12-04 17:50:30 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:50:31 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:50:33 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:50:34 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701713002701010000000100000000000000000e00000000000f00000000000020640000000000000f0f0f002475609213701712002701010000000300000000000000000e00000000000f000000000010e0640000000000000f0f0f002475609213701712002701010000001700000000000000000e00000000000f000000000010e0640000000000000f0f0f01
2017-12-04 17:50:36 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701711002701010000010200000000000000000e00000000000f000000000000c064cd7b00d519000f0f0f01
2017-12-04 17:51:31 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:51:32 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701711002701010000020200000000000000000e00000000000f000000000020c164cd7b00d516000f0f0f02
2017-12-04 17:52:30 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:52:31 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701711002704121716523335535174014273342e00000000000f000000000020c064cd7b00d513000f0f0f03
2017-12-04 17:53:11 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c5034352c3034313231372c3136353331312c33352e3839323234362c4e2c31342e3435383430312c452c412c302e31362c302c312c312c303030303530383030342c302c302c3029
2017-12-04 17:53:13 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701712002704121716531435535347014275036f01000000000f0400000000203064cd7b00d512000f0f0f02
2017-12-04 17:53:30 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-04 17:53:33 DEBUG: [E09B31A5: 5014 < 46.11.240.113] HEX: 2475609213701711002704121716533335535323014275062f02000000000f040000000020c064cd7b00d515000f0f0f04Thanks
Some new fields were added to the protocol. I have updated decoder:
https://github.com/tananaev/traccar/commit/9ec8be4360ad3088af66d9fd432d9a85cd0ee074
Hi Anton, appreciate the protocol update.
I'm using the updated protocol, which shows a significant improvement. Hex values are being read into traccar now.
The only issues that I have is detecting certain events with the device, for example lock / unlock events. The device itself is a padlock / tracking device.
The positions table in traccar shows no attributes related to these events when the device is locked / unlocked. Should I be looking in a different table? I skimmed through most of them and could not find anything.
From the protocol documentation it seems this can be extracted from the 00F0 hex value,Byte2.BIT0.
These are the logs from an unlock event:
2017-12-12 17:41:19 DEBUG: [EE30864D: 5014 < 46.11.240.113] HEX: 28373536303932313337302c404a5429
2017-12-12 17:41:26 DEBUG: [EE30864D: 5014 < 46.11.240.113] HEX: 2475609213701711002701010000280235535174014273342e00000000000f030000000020415fcd7b00d515000f0f0f0d
2017-12-12 17:41:26 INFO: [EE30864D] id: 7560921370, time: 2000-01-01 01:28:02, lat: 35.89196, lon: 14.45557, speed: 0.0, course: 0.0
2017-12-12 17:41:39 DEBUG: [EE30864D: 5014 < 46.11.240.113] HEX: 2475609213701713002704121718494335535572014275012e00000000000f030000000020e064cd7b00d51a000f0f0f132475609213701713002704121718503635535572014275012e00000000000f040000000020e064cd7b00d51a000f0f0f142475609213701713002704121718513635535572014275012e00000000000f000000000020e064cd7b00d515000f0f0f152475609213701713002704121718523635535572014275012e00000000000f000000000020e064cd7b00d51a000f0f0f162475609213701713002704121718533635535572014275012e00000000000f000000000020e064cd7b00d515000f0f0f172475609213701713002704121718543635535572014275012e00000000000f000000000020e064cd7b00d500000f0f0f182475609213701713002704121718553635535572014275012e00000000000f000000000020e064cd7b00d51a000f0f0f192475609213701713002704121719304735535572014275012e00000000000f030000000020e064cd7b00d51a000f0f0f1a2475609213701713002704121719314235535347014275016e00000000000f000000000020e064cd7b00d51a000f0f0f1b2475609213701713002704121719324135535340014275012e00000000000f000000000020e064cd7b00d51a000f0f0f1c
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:49:43, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:50:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:51:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:52:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:53:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:54:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 19:55:36, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 20:30:47, lat: 35.89262, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 20:31:42, lat: 35.89225, lon: 14.45836, speed: 0.0, course: 0.0
2017-12-12 17:41:39 INFO: [EE30864D] id: 7560921370, time: 2017-12-04 20:32:41, lat: 35.89223, lon: 14.45835, speed: 0.0, course: 0.0
2017-12-12 17:41:40 DEBUG: [EE30864D: 5014 < 46.11.240.113] HEX: 28373536303932313337302c5034352c3034313231372c3136353331392c33352e3839323233312c4e2c31342e3435383430362c452c412c302e38342c302c352c302c303030303030303030302c302c302c3129Thanks.
If you are talking about status flag, it's already decoded. You can use computed attributes to extract bits if you want.
Something doesn't seem right about the status flag. The value always remains 8416 even when locking / unlocking the device... so it could be related to something else.
Below is a sample of extracted data from traccar during which I unlocked and locked the device:
390 2017-12-05 04:02:03 2017-12-14 10:52:29 2017-12-05 04:02:03 {"odometer":15000,"sat":6,"status":8416,"batteryLevel":95,"distance":6.19,"totalDistance":4267898.63,"motion":false}
389 2017-12-05 04:01:09 2017-12-14 10:52:29 2017-12-05 04:01:09 {"odometer":15000,"sat":6,"status":8416,"batteryLevel":95,"distance":6.1,"totalDistance":4267898.54,"motion":false}
...
356 2017-12-05 00:04:24 2017-12-14 10:49:01 2017-12-05 00:04:24 {"odometer":15000,"sat":3,"status":8416,"batteryLevel":95,"distance":24.36,"totalDistance":4267899.47,"motion":false}
355 2017-12-05 00:03:23 2017-12-14 10:49:01 2017-12-05 00:03:23 {"odometer":15000,"sat":0,"status":8416,"batteryLevel":95,"distance":24.36,"totalDistance":4267899.47,"motion":false}Thanks
I guess you should contact device vendor about it.
Hello
I also have a problem with the JT701 GPS. it refuses to communicate with the platform, when I enter the code to apply the modification in the link above (https://github.com/tananaev/traccar/commit/9ec8be4360ad3088af66d9fd432d9a85cd0ee074) I realize that the code has changed and the structure is no longer the same
please help me
Hi,
I have setup a JT701 device to report to my server. I can see that the device is connected through the log entries in tracer_server.log but i dont seem able to see it in the actual platform.
Some example entries are:
and for the device in the platform I've tried using the 10 digit device ID as you can see from the hex in the examples above but this doesn't seem to have any impact and then also I tried the IMEI.
What am I doing wrong?
Thanks,
Mike