2005 Chrysler Neon Camshaft Sensor

  • 130,000 MILES
A couple of months ago my engin light came on and the car started to stutter while driving and did not want to accelerate. I went to the repair shop and they put it on the computer to check what was wrong (also had difficulty starting the car sometimes, but not always). It said that the camshaft sensor was faulty and would probably have to be replaced. They reset the computer and the light went out and the car drove fine for a day or two at which point the light went on a again and acceleration halted when revving too high. Took it back and ordered the camshaft sensor to be replaced. It has been replaced and the same problem is persisting. The repair shop puts it on the computer with old sensor error reads it is the camshaft sensor, puts in the new sensor and give completely different error (not sure what it was). Not knowing what was wrong they resert the computer again and drove around with the car to see if the light came on again, but it did not. But when I drove the car this morning, it happened again. What can cause this and how should I approach the repair shop to assist as I am not mechanically savvy.
Do you
have the same problem?
Tuesday, June 4th, 2013 AT 11:51 PM

1 Reply

First of all, diagnostic fault codes never say to replace parts or that parts are defective. They only indicate the circuit or system that needs further diagnosis. About half the time there is something else wrong like corroded or stretched electrical connector terminals, bare wires, corroded splices, etc.

Second, there are a lot of codes related to each sensor and they mean vastly different things. Some get very specific, and some are not real descriptive. We need to know the exact code number to have a better idea of where to start.

Also, you should understand that the computers on the car detect problems by comparing sensor readings at different times to different things. As an example, the Engine Computer knows that when the engine has been off for a specific amount of time, the coolant temperature sensor and the intake air temperature sensor had better be reading the same temperature. If one of them sends an unacceptable voltage signal that results in setting a fault code, the computer knows it can't use that one as a reference for the second one, so even if the second sensor develops a problem, no code will be set because no tests will be run on it. It's not until after the first problem is fixed that the computer can resume running all the tests, and that's when it will detect the second problem. That could be why you are seeing the Check Engine light again. You have to start over by reading the codes again to see if it's the same one that is setting. If it's the same code, the sensor wasn't the cause and the circuit must be tested further. If there's a new code now, the computer wasn't able to detect it while the first problem existed.
Was this
Wednesday, June 5th, 2013 AT 12:22 AM

Please login or register to post a reply.

Sponsored links