OBD TK 306

Hi there

My English is not really good, so sorry for using google translater.

I have the TK306 OBD2 tacker that does not send correctly and does not send any OBD data!

Already have all the ports that were read here and should be tried!
The tracker does not even recognize the ignition ACC can. someone help me there?

I have already added the code

<entry key = 'processing.computedAttributes.enable'> true </entry>
<entry key = 'processing.engineHours.enable'> true </entry>
<entry key = 'processing.copyAttributes.enable'> true </entry>
<entry key = 'processing.copyAttributes'> power, ignition, battery, hours </ent>

in traccar.xml, nothing really helps!

---

Deutsch
Hallo

Mein Englisch ist nicht wirklich gut deshalb verzeiht das ich google translater nutze.

Ich habe den Tacker TK306 OBD2 der Sendet nicht richtig und sendet keine OBD Daten!

Habe schon alle Ports durch die hier zu lesen waren und man versuchen sollte!
Der Tracker erkennt nicht mal die Zündung ACC Kann. mir da einer weiter helfen ?

Habe auch schon in der traccar.xml den Code (oben) hinzugefügt nichts hilf wirklich !

Can you provide HEX samples and protocol documentation for your device?

is that enough ???

2021-01-23 02:04:50  INFO: [f4f2de01: gt06 < 37.82.142.14] HEX: 78780d010352672102402237000d54a20d0a
2021-01-23 02:04:50  INFO: [f4f2de01: gt06 > 37.82.142.14] HEX: 78780501000d13b00d0a

My database is mysql

have now turned off mysql and activated the normal database now it is in the log

2021-01-23 20:13:36  INFO: [e64d334c: gt06 < 37.80.164.246] HEX: 78780a130406010001004b5ebc0d0a
2021-01-23 20:13:36  INFO: [e64d334c: gt06 > 37.80.164.246] HEX: 78780513004b04af0d0a

Do you have protocol documentation? Have you checked the samples against the documentation?

What do you think ?
the whole * .log file?

Unfortunately I'm not yet a Linux professional, always read a lot!

I saved the old * .log! If you think so ?

That would be the newest

2021-01-24 00:02:41  INFO: [f83317f3: osmand > 5.XXX.XXX.XXX] HEX: 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2021-01-24 00:02:41  INFO: [f83317f3] id: 0000000, time: 2021-01-24 00:02:41, lat: 51.36820, lon: 8.57094, course: 0.0, accuracy: 65.0
2021-01-24 00:02:43  INFO: [1e796881: gt06 < 37.83.XX.XXX] HEX: 78780a134406010001007cdc860d0a
2021-01-24 00:02:43  INFO: [1e796881: gt06 > 37.83.XX.XXX] HEX: 78780513007c41930d0a
2021-01-24 00:02:43  INFO: [1e796881] id: 3526721XXXXXXXXXX, time: 2021-01-23 20:25:49, lat: 51.36828, lon: 8.57117, course: 0.0
2021-01-24 00:02:43  INFO: [2dab3f9e: osmand < 5.XXX.XXX.XXX] HEX: 504f5354202f3f69643d3437343437342674696d657374616d703d31363131343432393633266c61743d35312e333638323032266c6f6e3d382e3537303934302673706565643d302662656172696e673d3026616c7469747564653d3533382e393930393031393437303231352661636375726163793d363526626174743d31303020485454502f312e310d0a486f73743a20352e3134372e3130312e34323a353035350d0a436f6e6e656374696f6e3a206b6565702d616c6976650d0a4163636570743a202a2f2a0d0a557365722d4167656e743a2054726163636172436c69656e742f35362043464e6574776f726b2f313230392044617277696e2f32302e322e300d0a4163636570742d4c616e67756167653a2064652d64650d0a436f6e74656e742d4c656e6774683a20300d0a4163636570742d456e636f64696e673a20677a69702c206465666c6174650d0a0d0a

Seems like you are ignoring my questions.

no definitely not! Then I do not understand your question or I do not understand it incorrectly

Do you have protocol documentation?

I think I have if you could tell me where to find it

Your device vendor should provide it.

Got this tracker!
The seller himself has a Tracker Service Traccar

I have already written to him but no answer yet!

Tracker

the site from the seller of the tracker

The instructions from the tracker