Mode $06 On A Tibby
07-04-2010, 11:15 AM
#1
Moderator
Thread Starter
Manufacturer speciffic diagnostics are very important to figuring out problems. Hyundai does not have any support from any OBD programs to my knowledge. I'm reseaching mode $06 and any help would be appreciated.
Keep in mind that this is part of a much much larger project. So for mode $06 data what I've done is create a program which establishes bluetooth communications with my ELM327 OBD reader and then injected hexidecimal codes into the reader which are called "requests". These requests are done in Hexadecimal, which are integers that count up to 16. So instead of 0-9 digits, you have 0-F digits. Collection of this data took around 10 hours to perform FFFF (65535 in base 10) requests at a time of aproximately 400ms per request.
After collecting the data, I sorted through 198287(decimal) lines of data to bring this to you:
<div class='codetop'>CODE</div><div class='codemain'>>0600
Hex data received:
46 00 FF 88 00 00 00
Binary bits broken down:
1:11111111 2:10001000 3:00000000 4:00000000 5:00000000
>0601
Hex data received:
46 01 01 00 00 00 00
Binary bits broken down:
1.00000001 2.00000001 3.00000000 4.00000000 5.00000000
>0605
Hex data received:
46 05 03 00 00 00 80
Binary bits broken down:
1.00000011 2.00000000 3.00000000 4.00000000 5.10000000
>0601CA
Hex data received:
46 01 01 00 00 00 00
Binary bits broken down:
1.00000001 2.00000001 3.00000000 4.00000000 5.00000000
>0605CE
Hex data received:
46 05 03 00 00 00 80
Binary bits broken down:
1.00000011 2.00000000 3.00000000 4.00000000 5.10000000</div>
This data is still raw, but at least it has been processed. It just needs to be cooked into something we humans can injest.
Keep in mind that this is part of a much much larger project. So for mode $06 data what I've done is create a program which establishes bluetooth communications with my ELM327 OBD reader and then injected hexidecimal codes into the reader which are called "requests". These requests are done in Hexadecimal, which are integers that count up to 16. So instead of 0-9 digits, you have 0-F digits. Collection of this data took around 10 hours to perform FFFF (65535 in base 10) requests at a time of aproximately 400ms per request.
After collecting the data, I sorted through 198287(decimal) lines of data to bring this to you:
<div class='codetop'>CODE</div><div class='codemain'>>0600
Hex data received:
46 00 FF 88 00 00 00
Binary bits broken down:
1:11111111 2:10001000 3:00000000 4:00000000 5:00000000
>0601
Hex data received:
46 01 01 00 00 00 00
Binary bits broken down:
1.00000001 2.00000001 3.00000000 4.00000000 5.00000000
>0605
Hex data received:
46 05 03 00 00 00 80
Binary bits broken down:
1.00000011 2.00000000 3.00000000 4.00000000 5.10000000
>0601CA
Hex data received:
46 01 01 00 00 00 00
Binary bits broken down:
1.00000001 2.00000001 3.00000000 4.00000000 5.00000000
>0605CE
Hex data received:
46 05 03 00 00 00 80
Binary bits broken down:
1.00000011 2.00000000 3.00000000 4.00000000 5.10000000</div>
This data is still raw, but at least it has been processed. It just needs to be cooked into something we humans can injest.
07-04-2010, 03:58 PM
#2
Super Moderator
at hyundaitechinfo.com, in the OBD-II section, there is some $06 information on the Siemens 662 and 663 systems and some serial communication protocol stuff. I'm not sure if it will help, but there it is.
07-04-2010, 04:10 PM
#3
Moderator
Thread Starter
I have been looking at that stuff all day and have not been able to figure it out.
Oh. I was looking at hmaservice. I will check that out too.
Oh. I was looking at hmaservice. I will check that out too.