P2D32: One tuning-valve code covers current and temperature reports

P2D32 can be set through two distinct reports from the intake tuning valve 1 power stage: overcurrent or overtemperature. The shared code does not mean those reports are interchangeable. Knowing which driver status was raised materially changes the evidence to preserve.

Identify the reported protection condition

The overcurrent branch relies on a current-fault report from the power stage. The temperature branch relies on its thermal-fault report. Neither row gives a universal ampere or temperature limit for external testing, so the code alone should not be converted into an assumed measurement specification.

Both branches list a one-second evaluation interval and two-trip reporting. Those reporting details do not establish how much mechanical resistance the valve experienced or prove that it was blocked.

Keep the branch-specific enable information

The current branch shows a battery range bounded above by 17.5 V and below by 9 V. The temperature branch’s lower-voltage entry is not clear enough to apply as the same condition without checking the actual calibration. The article therefore does not invent one common voltage procedure for both paths.

Preserve the power-stage status, valve command and relevant operating conditions. An overtemperature report is not an engine-overheating diagnosis, and an overcurrent report does not identify a particular short or obstruction. The correct service procedure must separate the electrical driver finding from the underlying component cause.

Source and applicability

2025 GM 25OBDG07A Part 1 documented monitor only. Vehicle, engine and calibration applicability must be confirmed from the matching service information; no model fitment is inferred. These criteria explain controller logic, not a complete repair procedure. 25OBDG07A Part 1, PDF page 933.