COO5 device with HUABAO protocol, how to get DTC info?
It looks like the JT808 (which should work with the HUABAO protocol) has the DTC fault code info as shown in this doc:
JT T808-2013 OBD2 PROTOCOL.docx:
https://clouddisk.alibaba.com/file/downloadFile.htm?spm=a2706.im-chat.0.0.4f711f8d1qz0ki&appkey=OneChat&id=746248530&parentId=652542651&secOperateAliId=MC1IDX1nJHw40IJswS8gLvBsTITocVyDs_trJNt10n49-aAOk0yi5sF1fCD6gUZZYU_j2ZO
From the above doc:
JT/T 808 standard platform OBD extended protocol
Location information report additional information extension (ID is new additional one after 0x80)
Message ID: 0x0200，0x0201,0x0202,0x0203
0XA0 N fault code information as below table
OBD fault code format
Field
Data type
Description and Requirement
Fault code 1
STRING
Eg：P1001 Each fault code occupies 5 bytes
Delimiter
STRING
One byte, fixed as ‘，’
Fault code 2
STRING
From what I can tell, it's supported in Traccar.
I just got the chance to check and it is connected on port 5015, but is not reporting any faults, like my other Sinotrack 902L does.
It could be that they changed something in the format.
Thanks Anton.
Is there any way for me to try to fix it using the protocol information in the link I posted above?
Should I be seeing any fault info in the logs in the HEX strings?
We can definitely look into it. Would need some samples with fault codes. Send an email to support.
Okay, I can scrub location info and post here, but the https://www.traccar.org/hex-decoder/ seems like it has a bug?
I can decode 31302c3236302c324336352c313746463130432c31368
..but not 31302c3236302c324336352c313746463130432c3136810
..which is only different by the ending '10'. It says "Binary Hex can't be converted to Text".
The other messages for this C005 device also will not decode, but my other device messages will. Maybe this is the bug in the protocol?
BTW, can I decode these messages myself on Linux or using another web tool? I'd like to know how the Hex Decoder works. Is it dependent on the device protocol? Or is converting to ascii the same for every device? Thank you
Why is that a bug? ASCII 0x10 is not a readable character.
Right, that's why I put the question mark..
Makes sense that 10 is not convertible.
Must be the reason the protocol isnt giving fault codes.
How to proceed?
Someone needs to investigate it properly. Look through the documentation, debug your samples etc.
Okay, I'm able to use a Hex to ascii converter.. I assume the non-alphanumeric characters are converted by the protocol.
I'll send an email with the logs before and after the fault code was triggered.
What can be done about the device sending the '10'? This online converter seems to ignore it and convert the rest.. maybe that is a solution in Traccar if I cannot change the device firmware?
The messages seem to contain repeated segments, that arent long enough for fault info (as compared to my Coban devices which convert to an ascii string saying the fault code in plain text). So either it is not being reported (but I know it is somehow for their Android app to show the fault and clear it), or it needs further interpretation of the protocol.
Thanks Anton
By the way, this is the only OBD GPS tracker I know of that is 4G and can clear DTC fault codes. Someone let me know if there is another one I can order. This one is about $40-60, so I would like to get the protocol to work with Traccar.
@Anton apparently Freematics Traccar device "Currently DTC codes are not submitted to traccar server." So, I'm still looking for a 4G device that can report engine DTCs.
Hi all and Anton,
I have a new 4G OBD port gps device that does DTC scans. I have to use an app called Aika GPS, but I want to use it with traccar.
Does anyone know how to get DTC codes with the HUABAO protocol?