Tuner Pro V5 and OBDII plug-in?

[JP86SS]

In my experience it's much easier to learn new info if you're trying to apply it at the same time as you're learning it.

That's exactly it.
You just have to keep picking at it till something is figured out, then poke at it some more.
I can't seem to get anything to work now so I'll take a step back and get one item to read out, then take everything I've learned up to this point and build up the definition again.
Hopefully it will only take 2-3 more times before it all works out.
Jp

[EagleMark]

May be late to the game here but there is a lot of good info at:
http://obdcon.sourceforge.net/2010/06/obd-ii-pids/

[EagleMark]

Alos found this on Moates site.

[JP86SS]

Got some more info and testing done.
The TP plug-in DOES convert the response from the ELM327 (in Ascii) to hex.
The data is the only thing passed out of the Plug-in.
All of the response definitions must have the following settings:
Body size =1
Payload size =1
Payload offset = 0

Even if this is a 16 bit response, the setting is the same.
The "value" definition will be the place to select if it is 8 bit or 16 bit value.

Got lots of items defined, and have data flowing at 16-18 Hz but that seems to be the total number of command responses you get so you must limit how many items you want to see.
Playing with different sets to get better dashboard display. Feels like your watching 160 baud on an old car though.
Still want to try and increase the speed of the ELM using AT commands but that might not be possible.
Jp

[EagleMark]

Even with EFI Live Scantool the rule of thumb is no more then 24 PIDS at a time. So duplicating ADX commands for fuel, spark, O2. DTCs etc may be the way to go when you find a bunch. Then one for tuner data.

If you need some testing let me know.

[RobertISaar]

i don't think it's the ELM so much as it is the incredibly large overhead the OBD2 PID request requires...

Mark, what kind of update rate do you see with 24 PIDs? does EFILive display an update rate?