help with trouble shooting
Moderators: Helpinators, Moderators
help with trouble shooting
check engine light came on after driving 80 mph on the freeway (regular cruising, no stomping on the gas, etc.)
got the following codes:
13 - cam angle sensor
23 - air flow sensor
24 air control valve
32 oxygen sensor
45 atmostpheric sensor
where should i start?
i cleared the code and see if it'll go back on. the car has not been driven in a while and just had a turbo installed.
thanks in advance.
got the following codes:
13 - cam angle sensor
23 - air flow sensor
24 air control valve
32 oxygen sensor
45 atmostpheric sensor
where should i start?
i cleared the code and see if it'll go back on. the car has not been driven in a while and just had a turbo installed.
thanks in advance.
That's too many codes. Some of them are probably old codes, maybe caused by mechanics disconnecting things while they work. Clear all the codes and then go for another similar drive. When you get home recheck your codes.
That light can come on for some fairly simple thing like having an almost empty fuel tank with too many fumes in it.
Were there any other symptoms?
That light can come on for some fairly simple thing like having an almost empty fuel tank with too many fumes in it.
Were there any other symptoms?
Re: help with trouble shooting
it's back on.....i do have an td05-18g with stock injectors. running wastegate pressure but i think it's more than 10 psi.chochocho wrote:check engine light came on after driving 80 mph on the freeway (regular cruising, no stomping on the gas, etc.)
got the following codes:
13 - cam angle sensor
23 - air flow sensor
24 air control valve
32 oxygen sensor
45 atmostpheric sensor
where should i start?
i cleared the code and see if it'll go back on. the car has not been driven in a while and just had a turbo installed.
thanks in advance.
can you get these codes when running into fuel cut?
Well if you still have all those codes, those sensors are easy to check with a basic electrical meter.
If you can get it connected to a scanner or laptop the others can be observed in action to ascertain which is faulty.
I'd start with the cam angle sensor. All the others are interdependant and could be triggered by the cam signal being faulty. The other codes wont trigger a cam angle sensor code no matter how bad they get.
I'd check the cam angle sensor first and if it is all right I'd pull the ecu and inspect it inside, using a magnifying glass, looking for, leaking capacitors, burnt transistors, cracked circuit boards or exploded transistors.
If you can get it connected to a scanner or laptop the others can be observed in action to ascertain which is faulty.
I'd start with the cam angle sensor. All the others are interdependant and could be triggered by the cam signal being faulty. The other codes wont trigger a cam angle sensor code no matter how bad they get.
I'd check the cam angle sensor first and if it is all right I'd pull the ecu and inspect it inside, using a magnifying glass, looking for, leaking capacitors, burnt transistors, cracked circuit boards or exploded transistors.
Have you checked the codes again after the CEL came back on?
Josh
surrealmirage.com/subaru
1990 Legacy (AWD, 6MT, & EJ22T Swap)
2020 Outback Limted XT
If you need to get a hold of me please email me rather then pm
surrealmirage.com/subaru
1990 Legacy (AWD, 6MT, & EJ22T Swap)
2020 Outback Limted XT
If you need to get a hold of me please email me rather then pm
There might be an intermittent fault in the cam sensor, the other codes might result from it. It would be strange that it only plays up under load though. Perhaps you have more than one fault.
You need to work through all those sensors confirming they are reading correctly right to the ecu. The subaru code reader can check the cam's signal as revs while it is driving, I'm not sure if it is the same revs a laptop or the rev counter would read though. The rest can be checked fairly simply.
If the cam missed a beat or two it would effect the ecu's idea of what the revs were and cause mixture and ignition problems, which could set all the other codes. If one of the other problems was the cause, that would not make the ecu think the cam wasn't turning.
You need to work through all those sensors confirming they are reading correctly right to the ecu. The subaru code reader can check the cam's signal as revs while it is driving, I'm not sure if it is the same revs a laptop or the rev counter would read though. The rest can be checked fairly simply.
If the cam missed a beat or two it would effect the ecu's idea of what the revs were and cause mixture and ignition problems, which could set all the other codes. If one of the other problems was the cause, that would not make the ecu think the cam wasn't turning.
If you go here... http://cid-4ca3c3459aaa7f7f.skydrive.li ... px/.Public
and have a look at "Diagnostic Aids For", it will perhaps give you some ideas...
and have a look at "Diagnostic Aids For", it will perhaps give you some ideas...