Déjà Vu: The P0D94 Fault Code Is Back

I ran a fresh system scan on the Jeep the other day, mostly out of habit at this point, and the result made me laugh in that particular way you laugh when something is more frustrating than funny. Sitting there, stored, was code P0D94-00.

If that code number looks familiar to regular readers, it should. It’s part of the same charging-system fault pair that I thought had been put to rest back in July with two separate software updates. Odometer at the time of the scan: just under 58,000 km. No warning lights on the dash, no drama while driving — just a quiet little entry sitting in the Hybrid Control Processor’s memory, waiting to be found.

What This Code Actually Means

P0D94-00 translates to “Battery Charger Coupler Lock Control Circuit Performance.” In plain terms, it’s flagged by the module that manages charging of the high-voltage traction battery, specifically the part of the system that controls the lock on the charge inlet port. It’s not a code that’s unique to the 4xe, either. A quick look around shows this exact fault family showing up on other plug-in platforms:

Jaguar Land Rover has documented this same pair of codes (P0D94-00 and its companion P0D9E-00) triggering incorrectly depending on the state the vehicle is in when it wakes up — a false alarm baked into how the module handles its startup sequence.
Ford has a service bulletin for a related code cluster on the Mustang Mach-E and F-150 Lightning, but in that case it traces back to a genuinely worn charge port lock actuator — a mechanical explanation rather than a software quirk.

So there are two very different possible explanations sitting behind the same four characters: a software gremlin that flags without cause, or an actual mechanical problem with the lock mechanism on the charge port itself. Both are plausible. What’s not sitting well with me is that this is the same code I was told, back in July, had already been resolved.

Next step is straightforward: get this in front of the garage, have them pull the full trouble code history rather than just what’s stored, and get it logged against the case that’s already open with Jeep Engineering. Whether this turns out to be another chapter of the same throttling story from the Klausenpass, or something new entirely, I’ll update this post once there’s an answer.