P07E4: Park is requested but the actual range does not agree

P07E4 can describe different Park-engagement strategies across controllers. This article covers the 25OBDG04B GM range-supervision row: the commanded transmission range is Park, but the actual arbitrated range fails to become or remain Park within the expected time.

What is compared

Actual-range information must have good status. When it is valid but differs from Park, the monitor increments a failure timer. Qualification occurs when that timer reaches the expected shift time. No fixed numerical timeout is provided on this page.

That distinction is useful because a range-data validity fault and a valid range that refuses to follow the command are different findings. The “remain” wording also allows disagreement after an initially successful Park selection, rather than limiting the diagnostic to the first engagement attempt.

Conditions and confirmation

Code clearing and manufacturing mode must be inactive. The power-state description allows Run/Crank or accessory/wakeup operation and an internal interval that ends after actual Park and loss of accessory/wakeup. The listed reporting is Type B over two trips.

For verification, the relevant evidence is commanded Park, valid actual range and agreement across the required interval. A selector display alone is insufficient. Because Park retention affects unintended vehicle movement, apply the vehicle's controlled service procedure rather than relying on this summary as a holding test.

This row supplies no mechanical root cause or repair instruction. The range comparison should not be expanded into an unsupported physical locking test. Identify the installed system and use its specific diagnostic procedure before interpreting engagement or retention.

Source: GM monitor, PDF page 653.