Fendt 4.1.67 – Transmission Control (A002 or A050): K051 - Relay, active hold function

The relay test was unsuccessful because the relay contacts (Pins 3 and 5) are stuck (welded closed), resulting in the tractor having no active hold/parking function.

• 411 Vario COM III
• 412 Vario COM III
• 413 Vario COM III
• 414 Vario COM III
• 415 Vario COM III
• 712 Vario COM III
• 714 Vario COM III
• 716 Vario COM III
• 718 Vario COM III
• 818 Vario COM III
• 820 Vario COM III
• Fendt 400 Vario (including COM III)
• Fendt 700 Vario (including COM III)
• Fendt 800 Vario (including COM III)
• Fendt 820 Vario greentec (COM III)
• Fendt 900 Vario (including COM III and chassis number 23/3001 and up)

1. 1

   Verify the symptom by confirming that the active hold/parking function is inoperative.

2. 2

   Remove the K051 relay and use a multimeter to check for continuity between Pin 3 and Pin 5 while the relay is unpowered. If there is continuity, the internal contacts are welded shut.

3. 3

   Consult the tractor's specific circuit diagram and check the wiring between the K051 relay and the Y053 (Active hold function solenoid valve) to ensure a short circuit didn't cause the relay to fail.

1. 1

   Locate the Relay

   Access the tractor's main electrical/relay board and locate the relay designated as K051 in your specific model's fuse/relay layout diagram.

2. 2

   Remove and Inspect

   Pull the K051 relay. Inspect the socket terminals for signs of heat damage, melting, or pushed-out pins, which can happen if a relay shorts and sticks.

3. 3

   Replace the Component

   Install a new, equivalent 5-pin relay into the K051 slot.

4. 4

   Clear the Fault Code

   Use the tractor's terminal to clear the stored fault. This is generally done by pressing the confirmation key (pictogram J) to acknowledge the fault, or by pressing and holding the designated key combination on the multiple display to clear the dashboard fault memory.

5. 5

   Functional Test

   Start the tractor and test the active hold/parking function to ensure it engages and disengages properly without throwing the 4.1.67 code again.