Ah208 problems
Im not sure what has happened but after playing with this for around 4 hrs yesterday and a tone of googling today the device seems to be sending data fine now, the only thing. i did resend the APN details as i wasnt sure that was correct (bad english manuel ) but it started receiving correct details some 22 min after that was set.
further update, tracking going well just missing the ignition detection (acc)
this is what shows in the log for the tracker
DEBUG: [A710E3D3: 5023 < 83.137.1.199] HEX: 78780a130004640001000aedf60d0a 2017-02-20 21:16:41 DEBUG: [A710E3D3: 5023 > 83.137.1.199] HEX: 78780513000a57220d0a 2017-02-20 21:16:42 INFO: [A710E3D3] id: 352887074240593, time: 2017-02-20 19:16:02, lat: 51.32094, lon: -2.95797, speed: 2.7, course: 0.0
i cant seem to translate the hex have i missed something?
Your device is using binary protocol, so it's impossible to translate it into a readable text, if that's what you mean by "translate".
As for ignition, most likely if you don't see it, it means that your device doesn't report it.
Hi Anton. Yes thats what i meant by translate. Re reading the ad it states sos anf fuel cut function. I yet to work out which is which wire to test.
Traccar is a very good bit of software keep up the good work!
Hi Anton,
Can you please tell if this is binary:
2018-11-14 19:12:52 INFO: [c937ed82: 5001 < 106.78.168.91] HEX: 78781f12120b0e152a34c701fe544507ed39c500148f01940027770016e6001634fe0d0a
2018-11-14 19:12:52 INFO: [c937ed82: 5001 > 106.78.168.91] HEX: 4f4e
2018-11-14 19:14:42 INFO: [c937ed82: 5001 < 106.78.168.91] HEX: 78780a13500604020200172baa0d0aWhat should I do if I wish to have this device's location received.
Here https://www.traccar.org/identify-protocol it says that "This instruction does not work for binary protocols."
So is it possible to have this device tracked on traccar?
It's GT06 protocol, port 5023.
Great! Thanks Anton.
You're right - it is GT06, starting from 0x7878
There was initial hiccup after setting the device to forward on port 5023 and it was allowing the port on ufw (ubuntu firewall). Once port was allowed, Traccar immediately showed the position on the map and now the logs look very much like other trackers.
Thanks again.
I have what was sold as ah208 but when opening it to put a sim in it has gt02 v1.2 inside (yes a generic chinese model from amazon)
I have set upa raspberry pi3 as a server at home and port forwarded relivent ports this all seems to work fine as i have 2 andriod phones with clients on updating this. I have set up the tracker to point to my home ip and can see in the server logs that it is connecting. At first i tried 5055 and all i got was hex code that didnt translate to anything. Next i tried 5001, 5002, 5006, 5013 and got the same garbage from the hex code. On 5023 it seems to transmite some hex but i also see the device id which i have added in the manager and can see the device transmiting the problem i have is it says the date is 1970/01/01 and longitude and latitude is 0.000000 so dosnt seem to send where it is. If i txt the device it gives its location so the gps side seems to work.
I have searched the forum for the same issue and cant find anything. Have i missed somthing simple. Could the port still be wrong? I dont have the hex output to hand but can post that up later if that helps.
Kind regards
Max