New Here?
Toggle Content
   

Toggle Content User Info
Welcome

Anonymous

Nickname
Password
Register

Membership:
Latest: Stu-mill
New Today: 0
New Yesterday: 0
Overall: 17131

Online Now [54]:
Visitors: 53
Bots: 1
Members: 0
Staff Online Now:

No staff members are online!
Page Views:
Today: 17061
Total: 104904657

Toggle Content Main Menu
 General Info Goodies Search Web Stats Members
 Donations

 

Forums ›

:: Forums ›
fault code 385
-> 206 Problems

#1: fault code 385 Author: orangelight, Location: worcester PostPosted: Fri Jan 28, 2011 12:09 pm
    ----
Hi, I am new to this forum - can anyone help me please. I have a Vreg 206 and the orange ECU light comes on after about 30 mins of driving. The car behaves fine but since we want to be able to do some long distance driving in this car we want to sort the problem. Does anyone know what ECU fault 385 means?

#2: Re: fault code 385 Author: NICKST, Location: Little hulton (worsley) PostPosted: Fri Jan 28, 2011 12:14 pm
    ----
If it's p0385 I think it's the crank shaft sensor/ crankshaft position sensor. But not 100%.

#3: Re: fault code 385 Author: kieron, Location: in the house PostPosted: Fri Jan 28, 2011 1:29 pm
    ----
Crankshaft Position Sensor B Circuit Malfunction
What does that mean?

The crankshaft position sensor (CKP) measures crankshaft location and relays this information to the PCM (Powertrain Control Module). Depending on the vehicle, the PCM uses this crankshaft position information to time the spark properly or on some systems it is only for misfire detection and does not control spark timing. The CKP sensor is stationary and works in harmony with a reluctor ring (or toothed ring) that is attached to the crankshaft. As this reluctor ring passes in front of the CKP sensor, the magnetic field created by the CKP sensor is interrupted and this creates a square wave voltage signal that the PCM interprets as crankshaft position. If the PCM detects that there are no crankshaft pulses or if it sees a problem with the pulses on the output circuit, P0385 will set.

Symptoms

NOTE: If the crank sensor is used only for misfire detection and NOT spark timing (this varies with the vehicle), the vehicle should start and run with MIL (Malfunction indicator lamp) illumination. Also, some vehicles require several key cycles to illuminate the MIL. If this is the case, there may be no MIL illumination until the problem often enough over time. If the crank sensor is used for BOTH misfire detection and spark timing, the vehicle may or may not start. Symptoms may include:

* Vehicle may not start (see above)
* Vehicle may run rough or misfire
* MIL illumination

Causes

A P0385 "check engine light" code could be caused by:

* Damaged CKP sensor connector
* Damaged reluctor ring (missing teeth or not turning due to sheared-off keyway)
* Sensor output open
* Sensor output shorted to ground
* Sensor output shorted to voltage
* Failed crank sensor
* Failed PCM

Possible Solutions

1. Using a scan tool, check if, when engine is running or cranking, that there is an RPM signal.
2. If there is no RPM reading, then visually inspect the crank Sensor Bnd connector for any damage and repair as necessary. If there is no visible damage, and you have access to a scope, you could check the CKP 5 Volt square wave pattern. If you do not, then, obtain a resistance reading of your crank sensor from a repair manual. (There are so many different types of crank sensors that there's no way to put here which resistance reading is correct). Then check the resistance of the CKP sensor by disconnecting the Sensor Bnd measuring resistance of the sensor. (It is best to check resistance readings from the PCM connector. This rules out any wiring problems from the start. But it does require some mechanical skill and shouldn't be performed if you\'re not familiar with automobile electrical systems). Is the sensor within resistance specs?
3. If not, replace the CKP sensor. If so, recheck resistance reading from the PCM connector. Is the reading still okay?
4. If not, repair open or short in the wiring to the crank Sensor Bnd re-check. If the reading is okay, the problem is intermittent or the PCM may be at fault. Try reconnecting and checking for RPM signal again. If there is now an RPM signal, wiggle test the wiring harness to try and induce the fault

#4: Re: fault code 385 Author: gti180boy, Location: Stafford PostPosted: Fri Jan 28, 2011 2:02 pm
    ----
kieron wrote:
Crankshaft Position Sensor B Circuit Malfunction
What does that mean?

The crankshaft position sensor (CKP) measures crankshaft location and relays this information to the PCM (Powertrain Control Module). Depending on the vehicle, the PCM uses this crankshaft position information to time the spark properly or on some systems it is only for misfire detection and does not control spark timing. The CKP sensor is stationary and works in harmony with a reluctor ring (or toothed ring) that is attached to the crankshaft. As this reluctor ring passes in front of the CKP sensor, the magnetic field created by the CKP sensor is interrupted and this creates a square wave voltage signal that the PCM interprets as crankshaft position. If the PCM detects that there are no crankshaft pulses or if it sees a problem with the pulses on the output circuit, P0385 will set.

Symptoms

NOTE: If the crank sensor is used only for misfire detection and NOT spark timing (this varies with the vehicle), the vehicle should start and run with MIL (Malfunction indicator lamp) illumination. Also, some vehicles require several key cycles to illuminate the MIL. If this is the case, there may be no MIL illumination until the problem often enough over time. If the crank sensor is used for BOTH misfire detection and spark timing, the vehicle may or may not start. Symptoms may include:

* Vehicle may not start (see above)
* Vehicle may run rough or misfire
* MIL illumination

Causes

A P0385 "check engine light" code could be caused by:

* Damaged CKP sensor connector
* Damaged reluctor ring (missing teeth or not turning due to sheared-off keyway)
* Sensor output open
* Sensor output shorted to ground
* Sensor output shorted to voltage
* Failed crank sensor
* Failed PCM

Possible Solutions

1. Using a scan tool, check if, when engine is running or cranking, that there is an RPM signal.
2. If there is no RPM reading, then visually inspect the crank Sensor Bnd connector for any damage and repair as necessary. If there is no visible damage, and you have access to a scope, you could check the CKP 5 Volt square wave pattern. If you do not, then, obtain a resistance reading of your crank sensor from a repair manual. (There are so many different types of crank sensors that there's no way to put here which resistance reading is correct). Then check the resistance of the CKP sensor by disconnecting the Sensor Bnd measuring resistance of the sensor. (It is best to check resistance readings from the PCM connector. This rules out any wiring problems from the start. But it does require some mechanical skill and shouldn't be performed if you\'re not familiar with automobile electrical systems). Is the sensor within resistance specs?
3. If not, replace the CKP sensor. If so, recheck resistance reading from the PCM connector. Is the reading still okay?
4. If not, repair open or short in the wiring to the crank Sensor Bnd re-check. If the reading is okay, the problem is intermittent or the PCM may be at fault. Try reconnecting and checking for RPM signal again. If there is now an RPM signal, wiggle test the wiring harness to try and induce the fault

Lol Kieron you copyed that off vivid hehe Smile

lol

#5: Re: fault code 385 Author: qwert, Location: uk PostPosted: Fri Jan 28, 2011 2:12 pm
    ----
or obd-codes.com Laughing

www.obd-codes.com/p0385

#6: Re: fault code 385 Author: orangelight, Location: worcester PostPosted: Fri Jan 28, 2011 2:26 pm
    ----
I think the garage have already replaced that sensor. I will check the connections to it. thanks



-> 206 Problems


Page 1 of 1
 
We are not responsible for comments posted by our users, as they are the property of the poster
Interactive software released under GNU GPL, Code Credits, Privacy Policy