A 2011 Peugeot 508 was scanned in a Swedish workshop, revealing a solitary P1712 fault code. This code indicates a plausibility or communication fault in the torque reduction request signal between the transmission control unit and the engine control unit. As a founder of the diagnostic platform we build, I review thousands of shop sessions, and this specific interaction between control units is a frequent bottleneck for technicians.
Decoding the torque reduction request
The P1712 code is highly specific to the interaction between the engine and the dual clutch transmission. During a gear shift, the transmission control unit must request a momentary reduction in engine torque from the engine control unit to ensure a smooth engagement. When this request signal fails to arrive, arrives corrupted, or does not match expected parameters, the system logs P1712.
Our diagnostic engine analyzed this specific vehicle and ranked the possible root causes based on historical repair data. The results point away from internal transmission failure and directly toward signal integrity.
The physical layer and CAN-bus integrity
The engine ranked a CAN-bus communication error or wiring harness failure as the most likely cause, assigning it a 90 percent probability with high severity. On this generation of Peugeot, fatigue in the wiring harness is common, particularly where it routes around the transmission housing. Corrosion or broken wires here will intermittently interrupt the torque reduction request.
To prove this out, the suggested diagnostic path begins with a visual inspection of the wiring harness and connectors. From there, the technician must measure the CAN-bus network resistance and verify the voltage drop across the relevant ground points. Real-time monitoring of the CAN-bus communication using a diagnostic tool is the final step to catch intermittent dropouts.
Conflicting data from the gear selector
If the CAN-bus physical layer is intact, the platform ranked a faulty gear lever sensor or microswitch as the second most likely cause at 70 percent. The logic here involves plausibility. If the transmission control unit receives incorrect information about the physical gear position, it will flag a fault. For example, if the microswitch indicates the vehicle is in Park but the wheels are turning, the system generates a conflict.
The tests required for this cause are straightforward. The technician needs to monitor the gear position sensor in real time while cycling the selector. A manual function test of the microswitches and a visual inspection of the gear selector module itself will confirm if liquid intrusion or wear has compromised the contacts.
Speed sensors and base voltage
Ranked at 50 percent, a faulty transmission output speed sensor is another viable cause. OEM data for P1712 includes a sub-definition regarding high vehicle speed in Park. If an output speed sensor provides erratic data, the transmission control unit incorrectly interprets the vehicle speed relative to the selected gear. The diagnostic path requires real-time monitoring of these speed sensors and resistance measurements of the sensor circuits.
We also cannot ignore the electrical foundation. The system ranked insufficient power supply or battery failure at 60 percent. Control units are highly sensitive to voltage drops. A failing alternator or corroded battery terminals can cause the engine control unit to drop communication packets, triggering a plausibility fault even when the dedicated network wiring is fine. A full battery load test and a charging system check are necessary prerequisites before condemning any control modules.
Applying this approach
Chasing communication codes by replacing modules is a fast way to ruin a bay's profitability. Testing the physical wiring harness and verifying the plausibility of the gear selector inputs provides a clear path to a verified repair. Do you typically start with harness continuity checks when you see torque reduction codes on this platform?