"REV" wireless OBDII for iPhone
Quick question... does the mini ODBII function in all key positions? I mean engine on and engine off with accessories on.
Rev keeps saying "Device not connected to an ODBII device" ...
I tried connecting the Kiwi to a honda and Rev turned green, read engine codes, but would not display speedo or any of the guages properly (not dynamic.. just reported some odd numbers like ECT at 33 degrees and RPM at zero).
Rev keeps saying "Device not connected to an ODBII device" ...
I tried connecting the Kiwi to a honda and Rev turned green, read engine codes, but would not display speedo or any of the guages properly (not dynamic.. just reported some odd numbers like ECT at 33 degrees and RPM at zero).
It takes a minute or so before the lights go green in Rev. I have lost the green lights in Rev. and had to shut down my touch to get everything to resync.
Don
Does that help?
Btw, is your Honda newer than 1996? If not, no worky.
It usually just works, once its set up, but sometimes it goes on strike for no apparant reason. At the weekend I spent about 10 mins trying to get things to connect, but nothing worked. Then it just started working as soon as the engine was turned on. I thought I had the car on (with the fuel petals light up), but it was just the radio on position.
Haven't watched for max boost numbers,* but 12 & 14 are fairly common numbers. I believe I've seen higher, but I usually have my eyes on the road when my foot is in it.

*The ScanGaugeII says they are maximum atmospheric pressure (MAP) which has to be adjusted by altitude to get boost. My house is at about 600 ft. above sea level and most driving is closer to sea level.
If I didn't already have the ScanGuageII, I'd be very tempted. The displays on the iPhone are certainly purdier than the ScanGaugeII.
I wonder how well it works while playing music?
I mount my iPhone with an Apple Universal Dock attached to a platform on a cupholder. This is convenient for the AUX port and cigarette lighter charger (USB not available in 2007), but it is too low for an instrument readout.
okay. just sat in the car for 20+ minutes with the engine running... most of the time all dots are red and the swirling icon just keeps swrling in the top right corner. Once I got the swirl to change into a pulsing green check mark to light up about 15 minutes in. Still, it refuses to go beyond that ... stalls at "reading engine codes". All the other metrics stayed red dot.. "not ready". After that brief moment of green... it all went back to red.
I have to say that for ~200$ this software+hardware is .... not production ready. Forgive me if I sound harsh but I (like some others I know) design multi-million gate microprocessors all day and don't have the patience to "try this, try that" on a system that's touted to be youtube working. It's funny that the programmers have programmed a panic button into the app (tap REV at the top of the app a bunch of times and it will send you to a "data collection" window that sends diagnostics email back to the developers). OKay. Off my soap box.
I have to say that for ~200$ this software+hardware is .... not production ready. Forgive me if I sound harsh but I (like some others I know) design multi-million gate microprocessors all day and don't have the patience to "try this, try that" on a system that's touted to be youtube working. It's funny that the programmers have programmed a panic button into the app (tap REV at the top of the app a bunch of times and it will send you to a "data collection" window that sends diagnostics email back to the developers). OKay. Off my soap box.
uMouse,
I assume that you are using the Rev Ap and not the Rev Lite Ap. (The Lite version does not really do anything with the OBDII Data output).
On your iPhone, when you go to "Settings">"Wi-Fi" (Assuming it is ON)>"Plx Devices", your iPhone is set to DHCP and most likely your iPhone has been given the IP Address of "192.168.0.11"
Is that correct?
From the Rev AP, go to "Settings">"Hardware Setup">Make sure the Device Connectivity is: IP Address = 192.168.0.10 and Port = 35000
If it is not set for that, change it to those settings and it should work!
The OBD Metrics red dots should turn to green and things should start working!
I hope this helps.
Trent
I assume that you are using the Rev Ap and not the Rev Lite Ap. (The Lite version does not really do anything with the OBDII Data output).
On your iPhone, when you go to "Settings">"Wi-Fi" (Assuming it is ON)>"Plx Devices", your iPhone is set to DHCP and most likely your iPhone has been given the IP Address of "192.168.0.11"
Is that correct?
From the Rev AP, go to "Settings">"Hardware Setup">Make sure the Device Connectivity is: IP Address = 192.168.0.10 and Port = 35000
If it is not set for that, change it to those settings and it should work!
The OBD Metrics red dots should turn to green and things should start working!
I hope this helps.
Trent
Yeap and yeap. Rev App v1.7
DHCP, iphone gets assigned 192.168.0.11
I plug in 192.168.0.10 and port 35000 into Rev hardware config (it shows as grayed out if I restart and go back into the config page)
I can wait for half hour with the engine on.. no connection.. little icon just spins forever.
How long does it "typically" take for the red dots to sync up and turn green?
Thanks for the help.
uMouse
DHCP, iphone gets assigned 192.168.0.11
I plug in 192.168.0.10 and port 35000 into Rev hardware config (it shows as grayed out if I restart and go back into the config page)
I can wait for half hour with the engine on.. no connection.. little icon just spins forever.
How long does it "typically" take for the red dots to sync up and turn green?
Thanks for the help.
uMouse
The lights go green within just a few seconds.
Mine does the same.
It sure sounds like you are doing everything correctly. I did have it act goofy at first and did a full power down (2 button hold) of the iPhone and then powered the iPhone back up. That seemed to do the trick. Also I would try unpluging the OBDII with the car running and then plugging it back in with the car still running and see if that does any good. If you know anyone else near you with one you could probably see if its the PLX Wifi, or the iPhone/Rev software.
I think PLX Wifi may have some software (free??) that will work with a PC with WiFi. Maybe that would help diagnose if the PLX device is working correctly.
(it shows as grayed out if I restart and go back into the config page)
It sure sounds like you are doing everything correctly. I did have it act goofy at first and did a full power down (2 button hold) of the iPhone and then powered the iPhone back up. That seemed to do the trick. Also I would try unpluging the OBDII with the car running and then plugging it back in with the car still running and see if that does any good. If you know anyone else near you with one you could probably see if its the PLX Wifi, or the iPhone/Rev software.
I think PLX Wifi may have some software (free??) that will work with a PC with WiFi. Maybe that would help diagnose if the PLX device is working correctly.
Just thought of another trouble shooting ideas.
Although it may not very likely that you may find someone else near you with a PLX Wi-Fi and or a full version of Rev, you probably have a good chance or knowing someone else with an iPhone.
Get them to download the free Rev Lite. With the Rev Lite, the OBD red lights will turn green when you are connected to the PLX WiFi. If your buddy can get the lights to turn green, but you can't, it is something either in your iPhone or the Rev software.
BTW if you touch one of the OBD (like Engine Coolant Temp) with a green light on the Rev Lite version, you won't get to see any information like a virtural guage but you will get a message saying that it is on-line.
On your PLX WiFi, Does the "Link" light turn off and back on at the same time you turn the WiFi of your iPhone off and on? - Is should.
Although it may not very likely that you may find someone else near you with a PLX Wi-Fi and or a full version of Rev, you probably have a good chance or knowing someone else with an iPhone.
Get them to download the free Rev Lite. With the Rev Lite, the OBD red lights will turn green when you are connected to the PLX WiFi. If your buddy can get the lights to turn green, but you can't, it is something either in your iPhone or the Rev software.
BTW if you touch one of the OBD (like Engine Coolant Temp) with a green light on the Rev Lite version, you won't get to see any information like a virtural guage but you will get a message saying that it is on-line.
On your PLX WiFi, Does the "Link" light turn off and back on at the same time you turn the WiFi of your iPhone off and on? - Is should.
I removed Rev and reinstalled it.. no luck.
The green Link does come up and coincides with my iphone's wifi connection.
Sometimes... the green "Link" will flash like it's thinking of doing something.. but then no love, back to steady green with all red dots, and that cursed swirling searching for network swirl in the upper right corner.
Does your PLX get hot? Mine is hot... like a hot laptop bottom. If yes, then it's probably the 12v dc-dc converter in there?
I've tried the standard top button reboot... even did "clear network connections". No Go. Let me try the two button hard reset.
If this fails.. then I'm suspecting a flaky Kiwi.
The green Link does come up and coincides with my iphone's wifi connection.
Sometimes... the green "Link" will flash like it's thinking of doing something.. but then no love, back to steady green with all red dots, and that cursed swirling searching for network swirl in the upper right corner.
Does your PLX get hot? Mine is hot... like a hot laptop bottom. If yes, then it's probably the 12v dc-dc converter in there?
I've tried the standard top button reboot... even did "clear network connections". No Go. Let me try the two button hard reset.
If this fails.. then I'm suspecting a flaky Kiwi.
My kiwi runs hot but I get good link and data. Your issues are odd. I would see if someone has a touch or iphone that you know, just pull rev. from your itunes collection to the new device and see if it works (manual sync).
Let us know what develops.
Let us know what develops.
Hard reset the iphone... no good
Disc/connect negative cable on car batt.... no good
Hot plug odb connector with engine on and Rev swirling... no good
Cycle switch on PLX ... no good
I can get another iphone and try it with that. I'm running out of ideas and seeing stars from all this idling in the garage.
Disc/connect negative cable on car batt.... no good
Hot plug odb connector with engine on and Rev swirling... no good
Cycle switch on PLX ... no good
I can get another iphone and try it with that. I'm running out of ideas and seeing stars from all this idling in the garage.
Awesome info guys, great to hear all the back and forth good or bad. Now I really want to get this combo as soon as I can.
Are any of the people currently running this using Jailbroken iPhones? Mine is Jailbroken because I'm on T-Mobile so if it doesn't work that makes it a definite no go...
Are any of the people currently running this using Jailbroken iPhones? Mine is Jailbroken because I'm on T-Mobile so if it doesn't work that makes it a definite no go...
Does your PLX get hot?
Maybe some more iPhone settings to possibly check
Settings>General>Network>Data Roaming>ON
Fetch New Data>Push>ON>>Manually
Have you tried contacting either support@devtoaster.com or
PLX Devices Inc.
1261 Birchwood Drive
Sunnyvale, CA 95089
(408) 745-7591 (P)
Also you might try PLX Logger 3.0 is free to download
(I have not tried their free software) I believe the software works with a PC using Ad Hoc mode of Wifi. My thoughts were that it would possibly confirm that the PLX KiWi is working properly.
I would see if someone has a touch or iphone that you know, just pull rev. from your itunes collection to the new device and see if it works (manual sync).
The reason why I would not first manually sync the version of Rev you have is that by using the free Rev Lite you rule out any possible corruption issue from your iTunes or your Rev Download. (I know it maybe **** but Trouble shooting being the process of elimination).
Last edited by OkieSnake; Jun 6, 2009 at 07:01 AM.
Yes
Also you might try PLX Logger 3.0 is free to download
(I have not tried their free software) I believe the software works with a PC using Ad Hoc mode of Wifi. My thoughts were that it would possibly confirm that the PLX KiWi is working properly.
Good idea except I would still first have your buddy download the free Rev Lite and see if that works first.
The reason why I would not first manually sync the version of Rev you have is that by using the free Rev Lite you rule out any possible corruption issue from your iTunes or your Rev Download. (I know it maybe **** but Trouble shooting being the process of elimination).
Also you might try PLX Logger 3.0 is free to download
(I have not tried their free software) I believe the software works with a PC using Ad Hoc mode of Wifi. My thoughts were that it would possibly confirm that the PLX KiWi is working properly.
Good idea except I would still first have your buddy download the free Rev Lite and see if that works first.
The reason why I would not first manually sync the version of Rev you have is that by using the free Rev Lite you rule out any possible corruption issue from your iTunes or your Rev Download. (I know it maybe **** but Trouble shooting being the process of elimination).

I agree, try Rev. Lite, then try another device and verify signal with Plx logger. Should give you a hint as to the problem.
Weird.
My son's iphone is unlocked but he is in France, so that is not going to help.
I use the touch, here is an idea, go buy a touch at BB or store of choice, try Rev., if it works, get your iphone fixed/O S software updated. Return or keep the itouch.
I tried the PLX Logger 3.0, it appears I need to get a license to make it run with the PLX Kiwi Wifi.
I sent a question to Plex support, I will see how long they take to reply.
My itouch/plx combo is still working fine.
Don
I sent a question to Plex support, I will see how long they take to reply.
My itouch/plx combo is still working fine.
Don
Okay, I have new news on this issue...
I manages to get REV to "work" on a '97 Honda Prelude, and a late model Honda Accord. Work in that REV would link up with PLX and read batt voltage and engine codes. ALL ODB metric dots remain red BUT some do work (like rpm, temp, etc.) but tapping "i" for more info says that that feature is not supported by this vehicle. hmmm.
How did I get this far? I had to wipe my iphone and reactivate it. YES. Everything sync from anew... not from any iphone backup image. I also had to delete REV from itunes... and "repurchase" it to make it download a clean copy. Then i sync'ed apps to the wiped iphone. Painful, but not so bad since now the iphone even runs slightly faster after I cleaned out all the junk.
And so that leaves me with the mini.... she's still sick. Every attempt to make her talk ODB has failed. I've tried to do a "drive cycle ODB readiness" drive (harder than you think to accomplish) but I don't know if it stuck... i couldn't follow the plan exactly because of traffic and stop lights.
My last ditch effort is to ask you kind folks to run an experiment for me to see if Mini Cooper has changed ODB protocols for '09. The experiment involves launching REV with the car as usual and then tapping the "REV" in the app's title bar in quick tempo... keep tapping... this brings up a REV debug mode that collects the AT commands sent to the PLX on to negotiate an ODB connection with the car. REV will then compose an email of that logfile to send to REV. It won't send since your wifi will currently be connected to the PLX. Just exit the mail app, disconnect wifi link, re-enter mail app and send the logfile to yourself.
From my log... it looks like the mini's ODB chip does not want to talk to PLX ... ERR94 and REV (v1.7 supposed to fix this ODB protocol negotiation) keeps cycling though all protocols with no success.
Thanks all for your help.
Here is my log:
I manages to get REV to "work" on a '97 Honda Prelude, and a late model Honda Accord. Work in that REV would link up with PLX and read batt voltage and engine codes. ALL ODB metric dots remain red BUT some do work (like rpm, temp, etc.) but tapping "i" for more info says that that feature is not supported by this vehicle. hmmm.
How did I get this far? I had to wipe my iphone and reactivate it. YES. Everything sync from anew... not from any iphone backup image. I also had to delete REV from itunes... and "repurchase" it to make it download a clean copy. Then i sync'ed apps to the wiped iphone. Painful, but not so bad since now the iphone even runs slightly faster after I cleaned out all the junk.
And so that leaves me with the mini.... she's still sick. Every attempt to make her talk ODB has failed. I've tried to do a "drive cycle ODB readiness" drive (harder than you think to accomplish) but I don't know if it stuck... i couldn't follow the plan exactly because of traffic and stop lights.
My last ditch effort is to ask you kind folks to run an experiment for me to see if Mini Cooper has changed ODB protocols for '09. The experiment involves launching REV with the car as usual and then tapping the "REV" in the app's title bar in quick tempo... keep tapping... this brings up a REV debug mode that collects the AT commands sent to the PLX on to negotiate an ODB connection with the car. REV will then compose an email of that logfile to send to REV. It won't send since your wifi will currently be connected to the PLX. Just exit the mail app, disconnect wifi link, re-enter mail app and send the logfile to yourself.
From my log... it looks like the mini's ODB chip does not want to talk to PLX ... ERR94 and REV (v1.7 supposed to fix this ODB protocol negotiation) keeps cycling though all protocols with no success.
Thanks all for your help.

Here is my log:
1. raw data:
01 00 BUS INIT: ...ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 4
--------------------------------
1. raw data:
AT SP 4 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 4 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
AT DP
--------------------------------
1. raw data:
AT DP ISO 14230-4 (KWP 5BAUD) >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
AT DP ISO 14230-4 (KWP 5BAUD)
6. response.error:
(null)
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 4 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 00
--------------------------------
1. raw data:
01 00 BUS INIT: ...ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 5
--------------------------------
1. raw data:
AT SP 5 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 5 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 20
--------------------------------
1. raw data:
01 20 BUS INIT: ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 6
--------------------------------
1. raw data:
AT SP 6 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 6 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 7
--------------------------------
1. raw data:
AT SP 7 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 7 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
03
--------------------------------
1. raw data:
03 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 8
--------------------------------
1. raw data:
AT SP 8 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 8 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
07
--------------------------------
1. raw data:
07
ERR94 >
--------------------------------
AT SP 9
--------------------------------
1. raw data:
AT SP 9 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 9 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 33 1
--------------------------------
1. raw data:
01 33 1
ERR94 >
--------------------------------
AT SP A
--------------------------------
1. raw data:
AT SP A OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN A >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 0D 1
--------------------------------
1. raw data:
01 0D 1 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP B
--------------------------------
1. raw data:
AT SP B OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN B >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 0B 1
--------------------------------
1. raw data:
01 0B 1
ERR94 >
--------------------------------
AT SP C
--------------------------------
1. raw data:
AT SP C OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN C >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 10 1
--------------------------------
1. raw data:
01 10 1 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
AT L0
--------------------------------
1. raw data:
AT L0 OK >
--------------------------------
AT E0
--------------------------------
1. raw data:
AT E0 OK >
--------------------------------
AT H1
--------------------------------
1. raw data:
OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
A0 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
01 00 BUS INIT: ...ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 4
--------------------------------
1. raw data:
AT SP 4 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 4 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
AT DP
--------------------------------
1. raw data:
AT DP ISO 14230-4 (KWP 5BAUD) >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
AT DP ISO 14230-4 (KWP 5BAUD)
6. response.error:
(null)
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 4 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 00
--------------------------------
1. raw data:
01 00 BUS INIT: ...ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 5
--------------------------------
1. raw data:
AT SP 5 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 5 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 20
--------------------------------
1. raw data:
01 20 BUS INIT: ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 6
--------------------------------
1. raw data:
AT SP 6 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 6 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 7
--------------------------------
1. raw data:
AT SP 7 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 7 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
03
--------------------------------
1. raw data:
03 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 8
--------------------------------
1. raw data:
AT SP 8 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 8 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
07
--------------------------------
1. raw data:
07
ERR94 >
--------------------------------
AT SP 9
--------------------------------
1. raw data:
AT SP 9 OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN 9 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 33 1
--------------------------------
1. raw data:
01 33 1
ERR94 >
--------------------------------
AT SP A
--------------------------------
1. raw data:
AT SP A OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN A >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 0D 1
--------------------------------
1. raw data:
01 0D 1 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP B
--------------------------------
1. raw data:
AT SP B OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN B >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 0B 1
--------------------------------
1. raw data:
01 0B 1
ERR94 >
--------------------------------
AT SP C
--------------------------------
1. raw data:
AT SP C OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
AT DPN C >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
--------------------------------
01 10 1
--------------------------------
1. raw data:
01 10 1 CAN ERROR >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
01 01
--------------------------------
1. raw data:
01 01 SEARCHING...
ERR94 >
--------------------------------
AT SP 0
--------------------------------
1. raw data:
AT SP 0 OK >
--------------------------------
AT L0
--------------------------------
1. raw data:
AT L0 OK >
--------------------------------
AT E0
--------------------------------
1. raw data:
AT E0 OK >
--------------------------------
AT H1
--------------------------------
1. raw data:
OK >
--------------------------------
AT DPN
--------------------------------
1. raw data:
A0 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
For all the tech types, here is the spec to the OBD interpreter that I THINK is inside the PLX...
http://www.elmelectronics.com/DSheets/ELM327DS.pdf
It's useful to decipher the AT commands and error responses from the logfile.
http://www.elmelectronics.com/DSheets/ELM327DS.pdf
It's useful to decipher the AT commands and error responses from the logfile.
Last edited by uMouse; Jun 11, 2009 at 07:38 AM.
For those running the experiment...
Tell me that your logfiles report Mini is using protocol 3, ISO 9141-2 (5 Baud init). Oddly enough, I just noticed that REV did not try that protocol in my logfile.. hmmm....
Tell me that your logfiles report Mini is using protocol 3, ISO 9141-2 (5 Baud init). Oddly enough, I just noticed that REV did not try that protocol in my logfile.. hmmm....
I tried the experiment on a friend's '06 Mini and it connected without much fuss once the engine was on. All OBD Metrics still show as red dots but do show real time data.
Confirmed that at least the '06 OBD protocol is as suspected: (connects using protocol 3, ISO 9141-2)
Confirmed that at least the '06 OBD protocol is as suspected: (connects using protocol 3, ISO 9141-2)
--------------------------------
09 02
--------------------------------
1. raw data:
NO DATA >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
NO DATA FROM ECU
--------------------------------
AT DP
--------------------------------
1. raw data:
ISO 9141-2 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
ISO 9141-2
6. response.error:
(null)
--------------------------------
AT DPN
--------------------------------
1. raw data:
3 >
2. response.primitiveValue:
3.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
09 02
--------------------------------
1. raw data:
NO DATA >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
NO DATA FROM ECU
--------------------------------
AT DP
--------------------------------
1. raw data:
ISO 9141-2 >
2. response.primitiveValue:
0.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
ISO 9141-2
6. response.error:
(null)
--------------------------------
AT DPN
--------------------------------
1. raw data:
3 >
2. response.primitiveValue:
3.000000
3. response.ecuDataDict:
(null)
4. response.dataArray:
(null)
5. response.stringValue:
(null)
6. response.error:
(null)
Last edited by uMouse; Jun 11, 2009 at 07:39 AM.
How do I check the cable? There isn't anything else in terms of diagnostics for this REV/PLX marriage.
I just pulled the negative from the batt and will let it sit for a bit. Hopefully that will clear up something (I know this trick clears up the aux USB if you happen to be fiddling with your usb/iphone dongle and accidentally short out your usb power.. don't ask how I know).
I just pulled the negative from the batt and will let it sit for a bit. Hopefully that will clear up something (I know this trick clears up the aux USB if you happen to be fiddling with your usb/iphone dongle and accidentally short out your usb power.. don't ask how I know).




