SparkFun Forums

[sti robot]

Did the recording tonight and I learned several things:

-The 4th position on the 4: line is the oil temp
-There are timing issues/parsing issues with repeatedly resetting the header to default and back to 7E0. An OK gets returned from the chip which includes an \0 or \n character which causes the "dumb" parsing of the return to end reading the buffer. I'll have to make the parsing more intelligent. Skip any OK's and look specifically at the 4: line and not at a specific spacing in the return.

[sti robot]

So, another question/conundrum.

If I want standard obd ii protocol pid stuff i'm good. If I want to get a can pid i'm good. But what if I want to get a CAN pid and then switch back to getting an obd ii pid.

AT D
AT E0

Will switch back to obd ii but it cuts off the CAN messages. I want to datalog some stuff from both protocols and quickly switch between. How do I do this?

[skimask]

Figure out what the "standard" header is before you set it, set it back to that, read the standard stuff, set the header to the "non-standard" header, read the non-standard stuff, wash, lather, rinse, repeat...

[sti robot]

How do i figure out what that is? Echo it out? Thanks for all the help.

[skimask]

Could be the case that doing some logging using "MA" might show you what "standard" header is.

[pstoppani]

Did you figure out the data of pid 2101? I'm trying to decode it myself. Thx, Pete

[sti robot]

Yes. I ended up using this library which was immensely helpful. The link is in here somewhere. So is my code. I think I forked his library and added to it. http://m.instructables.com/id/Custom-OB ... -OEM-Look/

[pat35249]

It works. Thank you very much.