N18 Camshaft Problem? Code P1339

Hi! my car (Cooper S N18) threw the CEL this morning with an alarming knocking/rattling noise that increases as the revs go up. However, as the revs go above 2000rpm, the rattling/knocking noise goes away. Even if the car is warm the knocking/rattling still persists, even at idle...which has never happened before. Certainly not normal. oh and also starting the car up is really hard, it cranks and cranks before finally starting up.

Can this be a timing chain tensioner problem?

I've done my search and havent found much other than this

P1339 - Camshaft Position Sensor Rationality Check (Inlet - Outlet)
P1339 - Exhaust Camshaft: Angular offset to crankshaft is outside tolerance range

 

Sounds like it's jumped time. I would have it towed to your mechanic, and be prepared to write a big check.

If the car is still under warranty, have Motoring Assistance drag it to your dealer.

 

Please check the oil in your engine. Too often overlooked!

 

I've been experiencing the same issue with error code P1339.
I don't have a BMW scan tool so I only know the generic error code meaning : "Crankshaft Pos./Engine Speed Sensor Cross Connected".

Is it even possible that the ESS is cross connected? I had an issue with the HPFP in the past and replaced it along with ALL coil packs and plugs (6months ago). This error message was coming up during that time as well and still seems to come up randomly. An engine restart seems to reset it and clears engine "limp mode", but a cold start seems to trigger the error code and put the engine into reduced power again. I am not noticing a lack of power or rough idle, so there really aren't any noticeable symptoms as far as I can tell.

Any thoughts on how to look further into this issue?
Thanks!

 

how many miles have you got on the odo? For me, I had 80,000miles on the clock. I believe it was the replacement of engine suspension mounts and transmission suspension mounts that solved the code for me. You should look into that and also the battery/alternators. Best of luck to you!


I also replaced the high pressure fuel pump, the aux fuel pump, ignition coils, spark plugs, all the intake/intercooler hoses to forge silicone pipes, water pump, alternator, battery. But I believe it was the engine/transmission suspension mount that did the magic.

 

I have 65k on the OD. Thanks for the info. Any ideas why the mounts would cause a timing error? How much were the engine mounts and how easy are they to get to? I repaced the battery after the HPFP as well as the intake hoses. I do have a slight "rattle" noise on acceleration sometimes and someone told me it might be an engine mount. I'm not sure where they are located.

 

I think you should take it to the dealer. I don't think it's an easy or diy job. How is your car doing now?

 

I'm having a similar issue one code reader says 2DA2
other p1339
curious as to why the mount would cause this code?

 

Double check code AD2A. I didn't find it here.

 

Your right its 2DA2 I checked everything Related to exhaust cam vanos solenoid camshaft sensors timing,,,,

The p1339 says it is crank shaft sensor cross wired...

Also the code only comes up while the car is driving if i clear codes and sit idle and even rev the engine the code doesn't come up...

 

Did you check the mechanical timing by installing the cam tool?

 

yes we did that

 

How many miles does the current timing chain have on it? Is the code linked to some recent repairs?

 

timing chain is new.. what is most interesting is the code only come up if the car is in driving sitting idle rev the engine no code will come up..

 

Was the same code present before replacing the timing chain?
Low engine oil level?
Did you reset DME VANOS adaptations after replacing the timing chain?
If you swap the two VANOS solenoids, does the fault code change to the intake camshaft?
If those are fine, you may want to consider a faulty exhaust VANOS unit.

 

we put in a new vanos and we did swap the solenoids it does stay....

we did not do the adaptations but have read that it is not necesary but we do reset the codes..

 

Was code 2DA2 present before replacing the timing chain or only after?

I would recommend resetting all adaptations related to the VANOS and engine timing and then go from there.

 

ok does a autel obd reader do it or does it have to be something like ista?

 

A basic code reader won't have advanced functions like reading live data and resetting adaptations. I paid ~$120 for a Launch scan tool having these functions and many others, though ISTA would definitely do the job and even more.

 

Resetting VANOS adaptations is not mentioned in the TIS instructions for changing the timing chain and/or VANOS gears. I did nevertheless reset them using ISTA+ after changing the timing chain and both VANOS gears in my N16 a couple months ago.

Regarding codes and other symptoms:
About 15K miles prior to changing the timing chain and the gears, a chain wear tool had already indicated that the chain is near or at its wear limits. About 3K miles prior to changing the timing chain, the DME threw the 2845 code for the first time (and a second time a few hundred miles later). At about the same time, chain rattle appeared when starting cold. All of the old chain gliders were fully intact (no broken/chipped off parts).

After changing the chain and the gears, no codes were thrown (both prior and after resetting VANOS adaptions) when idling or reving. I only drove the car after resetting the VANOS adaptations and to this day, no code appeared.

Side note: the timing seemed to be off and both cam shafts needed to be turned in order to position the cam lock tool (the intake shaft more so than the exhaust shaft). This was the first time the timing assembly was released so the timing was either off from factory (?) and/or somehow chain wear (??) caused it. The engine runs noticeably smoother now than before.

 

If I remember correctly, I used my Launch scan tool to perform three functions after replacing the N16 timing chain...

• Learn Valvetronic Limit Positions
• Delete VANOS Adaptations
• VANOS Adaptation

 

hi did you ever fix this? I am having this same issue and it’s driving me insane.