A food-processing plant reported that a Hyster J2.0XN 2-ton electric counterbalance forklift had developed a progressive electrical fault over a three-week period. The truck would operate normally for the first hour of a shift, then intermittently shut down for 2 to 5 minutes before restarting - with the cab display showing a "Controller Overtemperature" fault code during each shutdown event. The shutdowns became progressively more frequent as the shift progressed, and by the end of a full 8-hour shift the truck was shutting down every 15 to 20 minutes. The operator reported that the truck's travel performance felt noticeably degraded during the fault events, and that the truck's battery discharge indicator showed faster-than-normal charge depletion during shifts.
The technician first understood the J2.0XN's controller architecture. The truck's drive and hydraulic functions are managed by a "Traction Controller" - a sealed electronic module mounted within the truck's compartment, containing power semiconductor switches (MOSFETs or IGBTs) that deliver current to the traction motor based on operator commands. The controller generates heat during operation, and a dedicated cooling system - typically a passive aluminum heatsink or an air-cooled duct - dissipates this heat to maintain the controller's internal components within safe operating temperatures. A "Temperature Sensor" mounted on the controller's internal heatsink continuously monitors the controller's operating temperature, reporting readings to the controller's microprocessor. When the sensor reports a temperature above the controller's safe limit, the controller derates motor current or shuts down entirely to protect the power semiconductors from thermal damage.
He connected the Hyster diagnostic tool and retrieved the stored fault history. The log showed repeated "Controller Overtemperature Shutdown" codes across the past 120 operating hours, with a clear pattern of increasing frequency as operating hours accumulated. He then retrieved live data during a loaded operational test and observed the controller's reported temperature. After roughly 50 minutes of loaded operation, the controller's reported temperature climbed rapidly from 65°C to 95°C - well above the normal 75°C operating range - triggering the shutdown.
He inspected the controller's cooling system first. The truck's controller is air-cooled through a dedicated cooling duct that draws ambient air across the controller's heatsink fins. The duct's intake was heavily clogged with fine food-processing residue - flour dust, paper fragments, and plastic film - restricting airflow across the controller's heatsink and elevating its operating temperature. He cleaned the cooling duct and heatsink fins with compressed air, restoring airflow.
However, after the cleaning, a subsequent loaded test cycle still showed the controller's temperature climbing above the normal range - though less severely. He then inspected the "Controller Temperature Sensor" - the small thermistor mounted on the controller's heatsink that reports the controller's temperature to the microprocessor. Using the diagnostic tool's live-data function, he compared the sensor's reported temperature with a physical infrared thermometer reading taken directly on the controller's heatsink. The infrared reading showed 72°C; the sensor's reported reading was 91°C - a 19°C discrepancy. He disconnected the sensor and measured its resistance - the reading was significantly out of specification for the expected temperature, indicating the sensor's internal thermistor element had drifted out of calibration.
The root cause was traced to controller temperature sensor drift compounded by cooling-duct blockage. The clogged cooling duct had elevated the controller's actual operating temperature, accelerating the sensor's thermistor degradation. The drifted sensor had then begun reporting spuriously high temperatures - even after the duct had been cleaned - causing the controller to derate and shut down intermittently, producing the progressive performance loss and shutdown frequency the operator described.
The repair involved cleaning the controller's cooling duct and heatsink fins with compressed air, replacing the controller's temperature sensor with a new unit, and verifying the sensor's calibration against a reference infrared thermometer across a range of operating temperatures. The controller's fault history was cleared, and the truck's drive-controller calibration was verified with the diagnostic tool. After reassembly, a full-shift loaded operational test showed the controller's reported temperature tracking accurately with the infrared reference reading, the overtemperature shutdowns eliminated, and battery discharge returning to its normal rate across a full 8-hour shift. Controller cooling duct cleaning was added to the truck's 250-hour preventive maintenance checklist, and controller temperature sensor calibration was added to the annual inspection.
