P2D33Hybrid/EV Battery Inductive Charger Control Module Processor Performance
- Generic OBD-II code · Powertrain
- How the car detects it
- P2D33 concerns the electronics on the vehicle side of a contactless charging system and states that the processor of the inductive charger module has failed one of its own self-tests, for example a memory checksum, a RAM test or a watchdog. Inductive charging moves energy across a gap between a ground coil and a vehicle coil; GM's EV1 used the Magne Charge paddle to SAE J1773, while SAE J2954 now defines wireless power classes up to 11 kW. No manufacturer documents P2D33 publicly. Its wired counterpart P0E5E shows what such a test covers: Mitsubishi sets it on the 2023 Outlander PHEV for a ROM CRC or RAM read/write error in the charger control. CARB asks for charger faults that stop or slow charging to be detected. Wireless charging is then refused; driving and cable charging normally still work.
- What you may notice
- Wireless charging does not start or stops shortly after starting
- Charging fault message in the instrument cluster or app
- Code returns after clearing even though the vehicle is correctly positioned
- Likely causes
- LikelyInternal fault of the inductive charger control module (memory, processor, watchdog)
- PossibleCorrupted or outdated module software, for example after an interrupted update
- RareUnstable 12 V supply or poor ground at the charger module causing resets
- Repair
- Workshop only · Usually a job for a workshop.Typical cost: €100 – €2,500
- Related codes
Explanation from obdex (CC0), exactly as the app shows it. Guidance only; confirm with a workshop.