Welcome to Ultimate Subaru Message Board, my lurker friend!
|Welcome to Ultimate Subaru Message Board, an unparalleled Subaru community full of the greatest Subaru gurus and modders on the planet! We offer technical information and discussion about all things Subaru, the best and most popular all wheel drive vehicles ever created.
We offer all this information for free to everyone, even lurkers like you! All we ask in return is that you sign up and give back some of what you get out - without our awesome registered users none of this would be possible! Plus, you get way more great stuff as a member! Lurk to lose, participate to WIN*!
* The joy of participation and being generally awesome constitutes winning
** Not an actual guarantee, but seriously, you probably won't regret it!
Serving the Subaru Community since May 18th, 1998!
Code Reader Help
Posted 19 April 2004 - 03:59 PM
I recently ordered the cheap $39 OBD II code reader from Harbor Freight, and it just got here today. We have two Subarus, a 98 Forester and a 96 Legacy, both with the Check-Engine light on, so I giddily went out to the car and plugged the reader in.
The code reader is very basic, and is just supposed to pop up with 4 numbers, repeat the numbers 4 times, and then clear the CEL. Unfortunately, this isn't what happened. I inserted the reader, turned the ignition on (also tried in the reverse sequence just in case), and waited for the codes to appear. Instead of getting a code, the reader just read "--- " paused for a second, read " -", and then read "E " (error?). The same exact thing happened on both vehicles.
Am I doing something wrong? The reader's manual makes no mention of what the "E" might mean.
Thanks for any help!!
Posted 19 April 2004 - 04:10 PM
Posted 19 April 2004 - 04:13 PM
So the car is off when you plug the reader in and then you turn the key to on and it does this? Or are you plugging the reader in after you have turned the key to on?
I've tried it both ways... first I tried plugging it in after the car was on (per the instructions that came with the code reader). When this didn't work, I tried turning the car off, plugging the reader in, and then turning the ignition on. Both ways produced the same result.
Posted 20 April 2004 - 07:01 AM
Posted 20 April 2004 - 09:00 AM
Posted 20 April 2004 - 11:17 AM
Posted 20 April 2004 - 11:52 AM
Posted 20 April 2004 - 12:31 PM
Thanks for all the advice.
Posted 30 September 2004 - 11:02 PM
Posted 01 December 2004 - 08:54 PM
My Neighbor had the same results. Returned for replacement...Same....returned for credit. Now he comes to see me and I read his for free using the adapter I purchased 4 yrs ago for $75. Hooks to an old 486 laptop I have. works great on ALL OBDII protocols.
I am resurrecting this thread because I would like to know what else this BR OBD II Interface can do. I just purchased one, and it works great for pulling trouble codes. It will take me some time to learn about the different functions, but how else do you use it?
For example, is it possible to monitor the oxygen sensors and replace them before a check engine light is triggered?
Posted 02 December 2004 - 07:32 AM
Freeze frame data also shows what all the sensors were at when the last code triggered. Very good also.
Yes I did see quite a few slow O2 sensors using monitor mode. But under warrenty, the dealers will usually not replace them unless they trigger a code. I mean GM, Subaru and Toyota to name those I and my neighbors have delt with.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users