Before disassembling any hardware, eliminate temporary software glitches.
Service technicians generally follow two paths to resolve this "tiller ghost":
The throttle sensor (potentiometer) within the tiller head may be worn, dirty, or misaligned, sending an incorrect signal to the truck controller. 2. Neutral Zone Issues
Code 4372 typically indicates a . In plain terms: The truck’s travel controller sends a command to move, but the encoder or Hall sensor feedback from the drive motor doesn’t match what the controller expects. jungheinrich eje 120 error code 4372 work
Is the pallet jack an , or has it had a recent parts replacement ?
Marta tells Tom: “Park on level ground, turn the key off, remove the emergency stop, wait 30 seconds, restart. If the error returns, don’t force the lift – you could damage the pump.”
Inspect the cable harness running from the tiller head down the handle to the main truck chassis. Look for pinch points or exposed wiring, particularly at the pivot point of the tiller. Step 4: Check for Firmware Updates Neutral Zone Issues Code 4372 typically indicates a
Essentially, the truck’s controller is receiving a signal from the tiller handle that does not match its expected operating parameters—usually meaning it cannot determine the exact position of the throttle (neutralzone) or the steering tiller sensor is faulty, resulting in a tiller head sensor analogue implausible error. Common Symptoms The truck cuts out or refuses to drive.
The truck may experience intermittent operation, require constant restarts, or completely disable travel and lift controls.
To help narrow down the specific fix for your machine, please provide a few additional details: Is the error code or intermittent ? Marta tells Tom: “Park on level ground, turn
Access the service menu using your standard technician pin code.
If the wiring looks perfect and a firmware patch is unavailable, the internal analogue sensor board requires physical replacement.
Industry documentation and community service forums like Forklift Action identify three distinct root causes for this specific code: 1. Narrow Neutral Zone Calibration (Factory Firmware Issue)