Joined
·
20,380 Posts
A few notes raised by your description:
If a problem is detected by the OBD system and the CEL is turned on, after which the problem disappears, the CEL will remain on for 3 consecutive driving cycles without any problem being detected and then will go out automatically. Also, even if the CEL goes out automatically, the code or codes that caused the light to be turned on will be stored in memory for up to 40 driving cycles.
Your experience with the light going out on it's own seems to be consistent with this. In addition, the three codes that were found could actually be one code that triggered the CEL that was on at that time, but also two codes that were registered some time earlier but aren't an actual problem at the present time. Thus the importance of reading the codes whenever the light comes on -- best to know what it was, even if the light goes out.
This leads to the question -- if the codes were manually cleared using the code reader it's likely they were also erased from memory. If the CEL came on immediately after, were the codes read again to see which one or ones caused the immediate re-appearance of the CEL? That might have helped narrow down the possibilities. (Code readers are relatively inexpensive -- recently there was a basic one on e-Bay for less than $20. Also, you can identify the codes without a separate code reader following the procedure in this thread: http://www.subaruoutback.org/forums...9-how-read-diagnostic-trouble-codes-dtcs.html
The P0463 can be caused by a bad connection to the fuel level sensors in the tank, but if that were to happen, I would think the fuel gauge would also malfunction. Was there any evidence of this, e.g., gauge at full or empty end when it shouldn't be, or the Low Fuel light being on?
The fuel level sensors, fuel tank pressure solenoid and vent solenoid do seem to share a common harness connector (R46), so your focus on that connector (under the seat) is logical. But the likelihood of it being faulty (loose, intermittent connection) seems, to me, to be low unless that area of the car was worked on at some time, e.g. body work, or detailing/cleaning in the rear seat area.
Interesting combination of codes that I don't recall reading about at the same time before. Fortunately, as far as I know, none causes the car to shut down or go into a failsafe condition that will prevent it from being driven normally, although emissions might suffer, and as noted, the fuel gauge might be strange.
Not sure if this helps. Hope you will keep us informed.
If a problem is detected by the OBD system and the CEL is turned on, after which the problem disappears, the CEL will remain on for 3 consecutive driving cycles without any problem being detected and then will go out automatically. Also, even if the CEL goes out automatically, the code or codes that caused the light to be turned on will be stored in memory for up to 40 driving cycles.
Your experience with the light going out on it's own seems to be consistent with this. In addition, the three codes that were found could actually be one code that triggered the CEL that was on at that time, but also two codes that were registered some time earlier but aren't an actual problem at the present time. Thus the importance of reading the codes whenever the light comes on -- best to know what it was, even if the light goes out.
This leads to the question -- if the codes were manually cleared using the code reader it's likely they were also erased from memory. If the CEL came on immediately after, were the codes read again to see which one or ones caused the immediate re-appearance of the CEL? That might have helped narrow down the possibilities. (Code readers are relatively inexpensive -- recently there was a basic one on e-Bay for less than $20. Also, you can identify the codes without a separate code reader following the procedure in this thread: http://www.subaruoutback.org/forums...9-how-read-diagnostic-trouble-codes-dtcs.html
The P0463 can be caused by a bad connection to the fuel level sensors in the tank, but if that were to happen, I would think the fuel gauge would also malfunction. Was there any evidence of this, e.g., gauge at full or empty end when it shouldn't be, or the Low Fuel light being on?
The fuel level sensors, fuel tank pressure solenoid and vent solenoid do seem to share a common harness connector (R46), so your focus on that connector (under the seat) is logical. But the likelihood of it being faulty (loose, intermittent connection) seems, to me, to be low unless that area of the car was worked on at some time, e.g. body work, or detailing/cleaning in the rear seat area.
Interesting combination of codes that I don't recall reading about at the same time before. Fortunately, as far as I know, none causes the car to shut down or go into a failsafe condition that will prevent it from being driven normally, although emissions might suffer, and as noted, the fuel gauge might be strange.
Not sure if this helps. Hope you will keep us informed.
