Edmunds.com | Inside Line | Auto Observer Your Account | Help | Directory
You are here:
![[F]](http://a332.g.akamai.net/f/332/936/12h/www.edmunds.com/media/townhall/webxicons/site.gif){kind=small}
Forums
Wagons Subaru Crew Subaru Legacy & Outback OBD II Code Reader for Outback
16 messages, Last post on Apr 17, 2009 at 8:55 AM
You are in the Subaru Legacy & Outback Forum. Your Host is kcram
| Have an 05 Outback and saw an Actron code reader on sale (model 9175) Question, will this work on my sube and my 04 F-350, V 10. Also, where do you order oil filters on line for the Sube--Thanks, Mel | |
|
Replying to: catmandu (Jan 05, 2007 3:43 pm) You can check - look in the driver footwell of your Subaru, you will see the plug. Then look at your truck, see if they are the same type of plug. -juice |
|
|
Replying to: catmandu (Jan 05, 2007 3:43 pm) Steve (fibber2) wrote up a nice post quite a while ago about his research into scanners... on one of these threads (probably the P&S). I saved it as a Word document and will try to find it at lunch time tomorrow. Lots of good info!
|
|
|
Replying to: catmandu (Jan 05, 2007 3:43 pm) Otherwise, I mail order from 1stsubaruparts.com. They are a dealer located in Washington state and will accept Subaru Bucks. I'm not sure who the East coast folks order from.
|
|
|
Replying to: jfl (Jan 11, 2007 11:23 pm) -juice
|
|
|
Replying to: xwesx (Jan 11, 2007 8:51 pm) "Well, my need for an OBDII scanner was short lived. I had kind of settled in on either the Actron CP9135 or the Equus 3100 (both around $125) and locally available when the code cleared itself. There are also interesting products out there like CarChip and various PC and PDA adaptors that can be used for continuous monitoring. Perhaps all of this is worth explaining, as I learned some interesting stuff reading the .pdf owners manuals from the respective sites in my quest to understand exactly what I was getting into. While OBDII came into being in the mid '90's, it isn't completely universal in how it is executed. How the data is logged, and how it is read out and interpreted is referred to as the protocol. Manufacturers have a lot of leeway here, and the systems continue to evolve with new protocols being introduced and adopted. Most of the tools support OBDII protocols commonly used in US vehicles prior to 2004: VPW (General Motors), PWM (Ford), ISO9141 (Chrysler, Asian, and European), and ISO 14230 (also called Keyword 2000). The newest system, CAN (controlled area network) looks like it will be a major problem for most of the consumer grade tools. Ford/Mazda/Volvo are already using it, as are many of the new or revamped models introduced in '04/'05 from Toyota, GM, Chryco, Audi & Saab. I am sure that SoA will be headed there as well, so consider many of today's sub $200 tools as having a dead end unless they can be upgraded in the field (maybe downloadable ROM code change). There is a standard set of DTC's (Diagnostic Trouble Code), or "P0" codes, but just as many (or more, depending on the mfgr), proprietary codes. Reading them out is step one, finding exactly what the P1/P2/P3 codes might mean could take some work. My Subi shop manual lists them, and some of the sites list some of the mfgrs proprietary codes as well. Error codes can be stored that don't trigger the CEL (Check Engine Light), more properly called the MIL (Malfunction Indicator Lamp). These 'pending' or 'monitor' situation codes occur when something is out of spec, but not yet serious enough to warrant service. But they will probably cause you to fail an emissions test that requires reading out the stored data. DTC's that cause the MIL to illuminate show the more serious situations - 'static on' when a fault code is stored that meets a certain criteria, or flashing to indicate impending doom, like an overheating catalytic. A stored code (whether or not it illuminates the MIL) will stay forever if the fault remains, or immediately return if you attempt to clear it using the tool, or disconnect the battery. But a one time event will often clear itself, if it was a low level problem, after a certain number of start & warm-up cycles. The minimum number is three, but some situations will hang around for as much as 40. Mine was gone on the 4th trip - occurred after an abrupt maneuver on Tuesday evening, gone on Thursday. It may have backfired after a quick on/off/on throttle situation, triggering the light. So yes, I would like to own one, but I will probably wait for CAN compliance to become part of the package to insure the most useful life from my investment. -Steve"
|
|
|
Replying to: ateixeira (Jan 12, 2007 8:23 am) Jim |
|
|
Replying to: xwesx (Jan 12, 2007 10:34 am) For the member who posted the question: Beware, that while the generic 16 pin OBD-II connector may look the same, the pinout will be different depending on which of the protocols are used. I don't think you will harm anything as Gnd & +12 are typically in the same place and only the signal lines change, but best to be sure before trying.... I ended up with the Auto Enginuity tool that runs on a laptop. AutoTap is also another big player in the PC based market. They allow you to monitor a number of sensors realtime, much like the shops have. Realize that the error codes are only a best guess based on what the computer thinks is going wrong. Many times that is correct, but sometimes it can send you down an expensive wrong path. Watching an error occur, seeing what all the other sensors see, and knowing what the driving conditions were and how the car reacted at the time of the event is the key to a correct diagnosis. Steve |
|
|
Replying to: fibber2 (Jan 17, 2007 12:20 pm)  ), you write quality posts with useful information. I figure that rather than replicate the research you have already done, why not benefit from it to focus my own inquiries? Keeping a copy is a lot more handy than trying to remember when, where, etc. I have a handful of posts by various members to which I refer on occasion. Looking at the Auto Enginuity tool, the price (for what it does) seems reasonable. More expensive than the handhelds available, but also far more useful as you discussed. I would really like it to have the expanded capabilities offered for other makes like Ford, GM, Toyota, etc. Will you confirm, then, that you are limited to engine/emission diagnostics? Oh, and I confirmed on Saturday that my little Innova handheld is not compatible with the '07. Ah, well, I guess I will have to find a buyer for it so I can get some sort of salvage value out of it. In case anyone is wondering, the diagnostics interface port is now located under the dash, facing straight down (no cover), just "behind" the area of the hood release latch.
|
|
|
Replying to: fibber2 (Jan 17, 2007 12:20 pm)
|
|
You are here:
Forums
Wagons Subaru Crew Subaru Legacy & Outback OBD II Code Reader for Outback
New? Join Now!
Forum Tools
Search Forums
Browse by Vehicle
2010 Subaru Outback
Browse by Board
Browse by Topic
Today's Chats
