Supported ODB GPS trackers
It's H02 protocol. Port 5013 in Traccar.
hi Anton
I am usinq gps306 (or tk306) obd tracker from Coban for a while, on gps103 protocol. it retrieves fuel level in position but that's all. many obd informations are missing
Please find more accurate infos about gps306 from coban here : https://drive.google.com/drive/folders/0BzkifR8eVspfS0RMblMxaWdNaDg?usp=sharing
hope it helsp, and thanks for your awesome job
Hello,
All these devices are compatible with Traccar.
ODO function?
Regards,
https://www.traccar.org/ports-for-tk-gt-and-other-gps-devices/ "so it’s impossible to identify correct port for those devices just by a model name"
the named port here, i guess you mean TCP port? on device or server? Or another port? Is it an idea (specially for newbies like me) to explain on the page https://www.traccar.org/ports-for-tk-gt-and-other-gps-devices/ ?
cheers
It's TCP or UDP port on the server.
Hi, do you have experience with the ODBII devices of the company BAANOOL? I am looking at this device (http://www.ebay.com/itm/222514308867?ul_noapp=true) and I want to be sure of its compatibility with Traccar.
You have to request protocol documentation from them to confirm if it's supported.
Thanks Anton for your answer, i have documentation about the product. The protocols section is as fallows:
(GPS306A B-user manual)
The product supports existing OBD protocol:
SAE J1850 PWM
SAE J1850 VPW
ISO 9141-2
ISO 14230-4 (KWP2000_5BPS)
ISO 14230-4 (KWP2000_FAST)
ISO 15765-4 (CAN500_11BIT)
ISO 15765-4 (CAN500_29BIT)
ISO 15765-4 (CAN250_11BIT)
ISO 15765-4 (CAN250_29BIT)
But i can´t tell if is compatible. Perhaps you can tell me in the Traccar documentation where i can go into the matter.
tks!
That's not it. I need protocol documentation for the device, not for OBD standards that it supports.
Ok, this is the manual. I'm not sure what to look for http://drivers.amazplus.com/download/BT792_Manual.rar
Tks!
I need protocol documentation, not user manual.
hi Anton strange for GPS306 the fuel sensor used to be decoded in former version (io3) but no more on 3.11 (protocol gps103 port 5001)
please find an example of message:
imei:353451044508750,001,0809231929,13554900601,F,055403.000,A,2233.1870,N,11354.3067,E,0.00,30.1,65.43,1,0,10.5%,0.0%,28;
and the content specifications according to coban protocol documentation :
Content specification
Content after the first comma is: keywords
Content after the second comma is: year, month, day, hour, second
Content after the third comma is: the number of sim card in the tracker
Content after the fourth comma is: whether the signal of GPS is ok.
F means gps data is valid, L means no gps signal. In the old version, it is 5 comma when L, the following field is null. It stand for LBS in the new version, LAC is instead of latitude, Cellid is instead of longitude.
imei:359586015829802,help me,000000000,13554900601,L,,,22820,,10320,,,,;
Content after the fifth comma is: hour, minute, second of zero time zone
Content after the sixth comma is: Be corresponding to the content after the fourth comma, A=F，V=L；
Content after the seventh comma is: Latitude
Content after the eighth comma is: N is north latitude, S is south latitude
Content after the ninth comma is: Longitude
Content after the tenth comma is: E is east longitude, W is west longitude
Content after the eleventh comma is: speed
Content after the twelfth comma is: 1 stand for address request, non-1 stand for direction ( Direction will be sure with a decimal point )
Content after the thirteenth comma is: altitude
Content after the fourteenth comma is: The current state of the vehicle ACC; 1 is on, 0 is off
Content after the fifteenth comma is: The current state of the vehicle door; 1 is open the door, 0 is close the door
Content after the sixteenth comma is: the remaining Oil percentage in the fuel tank 1
Content after the seventeenth comma is: the remaining oil percentage in the fuel tank 2
Content after the eighteenth comma is: The current temperature sensor indicated
End with a semicolon after the nineteenth comma.
this shoud be ok for all tk103-105 devices
the device 306 sends OBD messages (currently under debug status in traccar logs)
example:
imei:868683027810526,OBD,170629185557,7235,,,794,129,64.71%,92,29.80%,2483,14.81,,,,;
meaning according to 306 Doc :
keywords (OBD), Time, Accumulative mile,Instant fuel Average, Fuel Driving time, Speed, Power load, Water temperatu,Throttle percentage, Engine speed, battery voltage, diagnostic troubl1,diagnostic troubl2,diagnostic troubl3,Diagnostic troubl4
hope that helps...
Can you please be more specific on what doesn't work. Message sample, what you see, and what's expected.
Hi Anton thanks for your answer problem was i didn't get fuel level infos but tried another car and it works; was a problem of avability of fuel datas from WW Fabia.
Sorry about that
have a wonderful day !
Here's an update on the Neelam TR209. I hadn't been able to find much info on this device until now so in case anyone else finds themselves viewing this thread for info on it...
It is manufactured by Huizhou Great-Will Industrial CO.,Ltd. Their website has zero information but I was able to match it up with a Heacent 908 device. They actually provide some decent info and the commands match up exactly on everything I've tried. Here is a link to the Owner's Manual which is much better written than the one I received with the device.
http://www.heacent.com/download/Heacent%20gps%20munual%28908%29.pdf
The Heacent website also has the following protocol document available.
http://www.heacent.com/download%5CGPS%20protocol%28Heacent%29.pdf
It doesn't mention any particular model and I've not had time to look into it. Maybe someone here can look at it and let me know if it's what is needed to implement a new protocol if one doesn't already exist.
Hope this helps someone.
Thanks,
~ TMiddleton