aCayenneFan

Why are you getting concerned? If your car has the issue, it seems like a solution is near at hand. If your car spends some time in the shop, then negotiate a price reduction. Not many alternative choices with the same combination of performance and function features.

daveo4porsche

Car should be returned to us next week - and Porsche North America has stepped up with a generous consideration given our time and trouble.

It's not the absence of problems, it's how you handle them - Porsche in my experience has always been really really good. YMMV

My wife is looking forward to driving her car next week.

donutcritic

Our MY21 TSEH was delivered in March and now has 350 miles. The CEL has come on and cleared 2x, but is now persisting. I sure hope it's not this serious issue - is there anyway of figuring out the situation without an OBD reader?

daveo4porsche

not that I’ve found - if your CEL is clearing on it’s own it’s not the same CEL code that my car is experiencing.

I’m told this is gravitating towards a known issue - they replaced some parts on my vehicle with newer parts and more importantly newer firmware on the new parts and Porsche germany believes this will address the issue.

I expect the vehicle back end of next week and hope we can put this issue behind us.

I recomend letting your porsche service department chase the issue and make sure you get a good loaner while yours is in the shop.

radctt1

Donutcritic

Check this thread and specifically last post. Had very similar CEL as you described. Took local dealer awhile to get it fixed. No more CEL on my 20 TSEH.

Dave not trying to hijack thread but might be helpful to donut.

https://rennlist.com/forums/cayenne-...-e-hybrid.html

daveo4porsche

got the car back so far so good…but less than 24 hours so far - Porsche has asked me to charge the car exclusively with the porsche charger it came with for the first month. "Fix" was a new charging component from the factory to avoid "conflicts" in communication between various computers in the vehicle - Porsche is confident the issue will be resolved by the new component but wants to rule out any charger incompatibility for the first month.

I'm keeping detailed logs.

Ryan Day

Seems like Deja vu. My 2021 turbo s e- hybrid has had the check engine light come on for the second time. I have less than 600 miles as well. Goodnews I guess is that I am in CA.
I'll run the scanner to see what's codes are showing up. Stay tuned.

donutcritic

Uh oh... I had my MY21 TSEH scanned at a local shop today when the CEL refused to clear.

I got the fateful "Lost connection with vehicle dynamics control module - U0122" message from their reader. Sadly my nearest dealer is 3+ hours away so am in a pickle.

icemang

I'd put it on a flatbed and send Porsche the bill. Curious where you live though.

daveo4porsche

let porsche haul it to the closest dealer.

daveo4porsche

sadly after 133 miles and 6 charging sessions - the CEL is back - I will be returning the vehicle to porsche service tomorrow for further diagnostics and hopefully resolution…

Ryan Day

What a bummer! Mines getting looked at and running diagnostics. If they can't solve I'll lemon it and go for the turbo instead assuming it doesn't have the same issues.

aCayenneFan

Ugh. Something tells me the root cause of the problem is not the software in the charging module...

daveo4porsche

same diagnostic codes we’ve been dealing with this entire time - local service shop is left wondering about next steps - they have escalated to field/national service for next steps so that Porsche North America can scratch their heads and shrug their shoulders cause no one knows what to do…I smell a hard to reproduce software fault and everyone is clueless as to what to do next…

citrus juice is my next step - but then I’m left with the problem of replacing a vehicle during a world wide crisis in automative production - mild inquires indicate I might be able to get a new car of the same class as the Turbo Cayenne sometime during the 2nd biden administration if I ordered one today (well not really that long but might as well be).

aCayenneFan

Yup - random, unrelated error codes are almost the original example of software failure going all the way back to COBOL days. Maybe even assembler code, but I am dating myself.

The magnitude of the failure would seem to be a compelling argument for putting your allocation at the front of the line. However, there is no guarantee at this point that you won't get a replacement with the same failure - if they can't isolate the root cause of the failure, they can't remedy the cause and it remains ready to rear it's ugly head. This is starting to sound like BMW's experience with high pressure fuel pump failures in the #35 cars that used the twin turbo motor - it took something like 3 years before they were able to find the root cause of the failure (and countless lemon law repurchases along the journey).

Sorry to hear about your misfortune.