I have a P1336 - crankshaft position sensor (POS) malfunction code. It all started when i first installed my JWT ECU. I thought it was suppose to trip a different code (O2 sensor or something). Strange thing too is that this is the only code I get, no ghost codes, O2 sensor codes, knock sensor codes...nothin. Anyway, I cannot get my damn car inspected and it has been rejected since august. I thought, ok i will just put the oem ecu back in, clear the code and it should be all set. NOPE!!! It is fine when i run the car without shutting it down, meaning the cel will not illuminate, but no matter how long the drive the ecu will not reset itself. i drove the damn thing 180 miles without turning the car off and as soon as i fire it back up the cel comes back. I dont get why this is happening. the motor does not knock, misfire or feel as though anything is wrong with it. In fact it is running the strongest it ever has. I checked the REF and that sensor and harness are fine. checked the POS and i could not get a voltage when i backprobed so i got a new one ($120 from the dealer, i know i know i got screwed but thats not the point i need it fixed). It still throws the code and i dont know what to do. Please please please help me out. anybody with a similar prob?? do i need to switch some pins??? HHHEEELLLPPP!!!

 

have you talked to JWT about it?

 

Could my Unorthodox Racing Flywheel be throwing a bad crankshaft position sensor code because it is not factory spec??? anyone with UR flywheels HHHEEELLLPPP!!!!

 

So you put the stock ECU back in and the code is still there?

 

that's what I was thinking about. is it possible the JWT damaged something, causing his problem, even with the oem ecu back in?

do you have a UDP? if so, try putting the stock pulley back on. I don't trust the aftermarket timing rings.

i suppose the flywheel is a possibility too. anyone else?

 

If it's never done it before, then something has changed. Done any work to your car involving the wiring harness, flywheel, or CKPS?

P1336 is CKPS POS, reads from the flywheel, so the chance of being a UDP is slim.

Unless his ECU somehow fried a section of the wiring harness, or the sensor itself, it can't really do anything to alter how the stock ECU acts.

 

that's what I was suggesting as a possibility. (since he said it all started after the JWT) but again, not very likely.

 

I seriously doubt that his JWT ECU could've damaged the sensor. Like you said; plausible, but likely? Not really...

 

has anyone ever heard of the UR flywheel doing this?