Got a new toy!!
I got the PLX KWI wifi interface, and the Palmer performance DashCommand.
http://www.palmerperformance.com/pro...hone/index.php
http://www.plxkiwi.com/kiwiwifi/hardware.html
http://www.palmerperformance.com/pro...hone/index.php
http://www.plxkiwi.com/kiwiwifi/hardware.html
Have a look to see if you can define your own PIDs (they may call them commands or custom display values or some such). Some of the OBD tools (ScanGauge, XGauge, I think) can. If so, you can probably monitor things like EOT (engine oil temp) and IAT2 (air temp after the SC) by creating your own PIDs.
Have a look to see if you can define your own PIDs (they may call them commands or custom display values or some such). Some of the OBD tools (ScanGauge, XGauge, I think) can. If so, you can probably monitor things like EOT (engine oil temp) and IAT2 (air temp after the SC) by creating your own PIDs.
yes I can Im currently building a theme to monitor IAT1, IAT2, Coolant, temp, rpm, speed, vaccum/boost, oil pressure/temp, Tranny fluid temp, gear selection status.
Any other suggestions?
Does it know how to do IAT2, EOT & TFT (tranny fluid temp) out of the box? (They're not generic OBD nor are they the same PIDs as Ford or GM use.)
You might like to know fuelling at WOT but firstly you're not at WOT for long and secondly you'd need to use non-generic stuff for sure (avos has mentioned various issues with WOT).
Anyway - for now just play
You might like to know fuelling at WOT but firstly you're not at WOT for long and secondly you'd need to use non-generic stuff for sure (avos has mentioned various issues with WOT).
Anyway - for now just play
hmm, have you checked that you get readings for those non-generic sensors and that they're plausible readings?
If the AFR values are read using "mode 1" (as usual), I think you'll find they aren't reported correctly during WOT (I think they're some of the ones avos mentioned).
If the AFR values are read using "mode 1" (as usual), I think you'll find they aren't reported correctly during WOT (I think they're some of the ones avos mentioned).
Im still tinkering with it, since the PLX does use a ELM compatible output I think I can use it with different software and get more in depth, I have a list of all the PIDS,
so I am able to see the raw hex values. from all the sensors.
so I am able to see the raw hex values. from all the sensors.
Trending Topics
hex! lucky you LOL
If they're "mode 1" PIDs (as normal), you'll hit up against the issues avos pointed out.
Just about all ELM-based software is generic ("mode 1") PIDs only (when reading sensors). And of the stuff that does more than just generic I don't know if any does Jags. Have fun
If your list includes "mode 22" you may get further. PM me if you need help, by all means.
You can check IAT2 for plausibility by watching it as the car warms up.
If they're "mode 1" PIDs (as normal), you'll hit up against the issues avos pointed out.
Just about all ELM-based software is generic ("mode 1") PIDs only (when reading sensors). And of the stuff that does more than just generic I don't know if any does Jags. Have fun

If your list includes "mode 22" you may get further. PM me if you need help, by all means.
You can check IAT2 for plausibility by watching it as the car warms up.
Awesome! Well I'm trying to work Palmer performance to see what all modes thier software will support I doesn't do me any good to just read the data streams without a means to translate the data. I really do like the wifi interface
Please tell me if I understood correctly that with PLX Kiwi wifi interface you can read IAT2?
Mafiosio and your messages in the beginning of the thread. Mafiosio told "I have a list of all the PIDS" so I thought he has configured the custom PID successfully.
Thread
Thread Starter
Forum
Replies
Last Post
JimC64
X-Type ( X400 )
4
Oct 11, 2015 09:04 PM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)









