TK103 - Ignition/ACC not working

Hi I am trying to see when my car is idling with this OBD II device that I bought from eBay. It says it's a TK103 and I am getting consistent data except for the ACC/ignition. On Traccar "ignition" always remains on (while my other hardwired devices give me notifications for whether the vehicle is on or off). Is there a fix to this? My decoded hexadecimal is below. I tried going through the protocol, however, I just do not understand it at all.

Does anyone know if I can maybe modify the protocol/code as well? It has a micro usb slot.

*HQ,358xxxxx8437,V1,000337,A,xxxx.xxxx,N,xxxx.xxxx,W,34.15,289,310517,FFFFFFFF#

Last value in the message is the status mask. Does it change when you switch ignition on/off?

@Anton

Here is my log:

2017-05-31 01:38:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313539384e30383034382e30333838573030302e393031333834383030302e303031313030303030304c303030343530414229
2017-05-31 01:38:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:38:48, lat: 35.30266, lon: -80.80065, speed: 0.5, course: 0.0
2017-05-31 01:39:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313634344e30383034382e30323736573030302e333031333934383030302e303031313030303030304c303030343530414229
2017-05-31 01:39:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:39:48, lat: 35.30274, lon: -80.80046, speed: 0.2, course: 0.0
2017-05-31 01:40:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313733364e30383034382e30303339573030302e313031343034383030302e303031313030303030304c303030343530414229

2017-05-31 01:38:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313539384e30383034382e30333838573030302e393031333834383030302e303031313030303030304c303030343530414229
2017-05-31 01:38:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:38:48, lat: 35.30266, lon: -80.80065, speed: 0.5, course: 0.0
2017-05-31 01:39:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313634344e30383034382e30323736573030302e333031333934383030302e303031313030303030304c303030343530414229
2017-05-31 01:39:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:39:48, lat: 35.30274, lon: -80.80046, speed: 0.2, course: 0.0
2017-05-31 01:40:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313733364e30383034382e30303339573030302e313031343034383030302e303031313030303030304c303030343530414229

if its easier to see without quotes. and also I had car off, then ignition on, then drove, then off, but log may not represent all the events I am trying to figure it out still.

Larger Log if it helps:
I see a very long hex then short ones - when its short its split up into two parts

2017-05-31 01:32:50 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313735394e30383034372e39393538573030302e353031333234383030302e303031313030303030304c303030343530414229
2017-05-31 01:32:50  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:32:48, lat: 35.30293, lon: -80.79993, speed: 0.3, course: 0.0
2017-05-31 01:33:50 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313733394e30383034382e30303331573030302e313031333334383030302e303031313030303030304c303030343530414229
2017-05-31 01:33:50  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:33:48, lat: 35.30290, lon: -80.80005, speed: 0.1, course: 0.0
2017-05-31 01:34:21 DEBUG: [738A4FF6: 5013 < 77.218.246.220] HEX: 2a48512c3335383531313032303031383433372c48544254230d0a
2017-05-31 01:35:43 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384250303033353238383730373431393838353848534f3031383729
2017-05-31 01:35:43 DEBUG: [F40D209D: 5002 > 77.218.252.2] HEX: 283038373037343139383835384150303148534f29
2017-05-31 01:36:21 DEBUG: [738A4FF6: 5013 < 77.218.246.220] HEX: 2a48512c3335383531313032303031383433372c48544254230d0a
2017-05-31 01:38:22 DEBUG: [738A4FF6: 5013 < 77.218.246.220] HEX: 2a48512c3335383531313032303031383433372c48544254230d0a
2017-05-31 01:38:44 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384250303033353238383730373431393838353848534f3031383629
2017-05-31 01:38:44 DEBUG: [F40D209D: 5002 > 77.218.252.2] HEX: 283038373037343139383835384150303148534f29
2017-05-31 01:38:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313539384e30383034382e30333838573030302e393031333834383030302e303031313030303030304c303030343530414229
2017-05-31 01:38:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:38:48, lat: 35.30266, lon: -80.80065, speed: 0.5, course: 0.0
2017-05-31 01:39:51 DEBUG: [F40D209D: 5002 < 77.218.252.2] HEX: 283038373037343139383835384252303031373035333141333531382e313634344e30383034382e30323736573030302e333031333934383030302e303031313030303030304c303030343530414229
2017-05-31 01:39:51  INFO: [F40D209D] id: 352887074198858, time: 2017-05-31 01:39:48, lat: 35.30274, lon: -80.80046, speed: 0.2, course: 0.0

Okay so I did a little more digging. I found these specific lines in my log:

283038373037343139383835384250303033353238383730373431393838353848534f3031383<strong>6</strong>29

283038373037343139383835384250303033353238383730373431393838353848534f3031383<strong>7</strong>29

Which translates to:

(087074198858BP00352887074198858HSO0186)

(087074198858BP00352887074198858HSO0187)

And I still cant figure out what the last part means. HSO018x

My first post quote is from another one of my devices(Disregard that line) - these last 2 posts are the best to go off of.

How is your original comment related to other ones? The protocol is completely different!!!

Yeah I messed up by accident haha. That is for my hardwired tracker which is working perfectly fine. The rest of my replies are what I am struggling with my TK206OBD II (tk103) device.

Sorry about that, my friend helping me with this sent me the wrong Hex Code at first. I tried editing my post, but after some time I couldn't.

Traccar supports ignition for TK103 protocol as well. It uses status mask in the location message.

Yes I understand, but for some reason I am not getting notifications/change in ignition on Traccar and I can't debug whether my device is the issue or not. I don't know if the hex is changing based on ignition. I'll do some more thorough testing tomorrow morning, but if you can figure out the change from my logs above, it would be really appreciated.

If you look at a regular message with coordinates the status is 8 digits before letter "L". That's what you should check.

8 Digits before the L is:

0011000000L

Not sure if its the 1 or the 0 in this case. I can't seem to figure this out with the protocol documentation either.

(087074198858BR00170531A3518.1598N08048.0388W000.9013848000.0011000000L000450AB)

I would need protocol documentation with this information if you want it to be implemented in Traccar.