P2135 & P2104/6 Error Codes

[Jmanji]

Had a reoccurring p2135 and limp code yesterday on the way to ace cafe, after resetting it at least 6 times I was just a little fed up, so to make things worse I read this thread and think it's now the ecu that's buggered ,so got home from work and checked all the throttle body connections were tight etc, eml lights went out and after a good blast around the area it seems to have done the trick.

[Reindeer]

@CocoPops

I fully appreciate this was 5 years ago now, so apologies everyone...

But @CocoPops was this ECU change the final solution? Did the problems ever reoccur?

Thank you. Sorry for dragging up old threads.

[CocoPops]

They changed loom and ecu.

My money is on the loom being the issue. They changed ecu first and the issue remained…

[Reindeer]

On 19/06/2015 at 15:22, CocoPops said:

Now I feel sick

 

I was hoping to get an email today saying "Car ready"... but no.. I get an email saying "Loom replaced, issue still exists".

 

They've changed the Engine loom, to the latest spec with additional earthing points etc but the issue still remains.

So they tried my ECU in another Evora and the issue is replicated in the other car. When they try the other cars ECU in my car, the issue is not present.

 

Thus it looks like it needs a new ECU!!

 

Not sure where I stand on costs/bills etc, certainly not wanting to pay anything.

Lotus were picking up the cost of the loom and labour with Silverstone directly, as it was a Lotus decision to change the loom.

Lotus Silverstone have now gone to the warranty firm to see if they will cover cost of ECU (£900 iirc from deRoure prices).

 

Gutted to say the least.

3 weeks now without my Evora (out of 11weeks ownership).

Sorry maybe ive misunderstood the above.........i thought you said issue remained after loom changed...hence they moved on to ECU?

[Peters4]

This weekend, I started the car and immediately it showed engine light and traction control off light.
ODB scan revealed P2104 and P2119.
Cleared the errors and didnt come back (yet).

Could this have been caused by too fast switching the engine on, not waiting for the 'init' phase to complete?
Normally I wait for the dials to 'sweep' and then I start, this time, I turned the key immediately.

 

[Cdm2018]

Could be a sensor glitch ! My car being showing them for last few weeks and I clear them and they come back few days later?

going to get car serviced early and perhaps get new maf sensor or have cleaned and replace brake switch ? 

[Arregueti]

@Peters4I don´t think it has anything to do with how fast you turn the key. I had those codes a number of times recently, too. In my case, a new battery seems to have solved the issue (it is an early MY 12 with what apparently was the original battery).