Modern hot runner controllers display alarm codes to indicate thermocouple and system faults. Understanding these codes and knowing the corrective actions is essential for quick response. This article provides a comprehensive guide to common alarm codes and troubleshooting steps.
Open Circuit (E02, TC.OP, or similar). This indicates the controller cannot detect the thermocouple signal-the circuit is broken. Causes: broken wire, loose connector, or failed sensor. Corrective action: Check the connector first (most common). If okay, use a multimeter to check resistance at the mold junction box. Infinite resistance confirms an open circuit. Replace the thermocouple or repair the wiring.
Reversed Polarity (E03, TC.St, or similar). The positive and negative leads are swapped. The controller may show a negative temperature or a reading that decreases with heating. Corrective action: Verify polarity using color codes (Type K: red = positive, black = negative; Type J: white = positive, red = negative). Swap the leads at the connector or terminal block. Confirm reading changes correctly.
Short Circuit (E09, SHRT, or similar). The thermocouple leads or the sheath are shorted. Causes: moisture ingress, insulation breakdown, or damaged cable. Corrective action: Check insulation resistance with a megohmmeter. If <1 MΩ, replace the thermocouple. Also check for plastic leakage that may be bridging contacts.
Temperature Too High (Over-Temperature Alarm). The thermocouple reading exceeds the high-temperature limit set in the controller. Causes: heater runaway, controller triac stuck, or thermocouple drift (reading low causing controller to overheat). Corrective action: Immediately reduce power or shut down the zone. Check heater current-if it remains high when setpoint is low, the triac may be shorted. Also verify the thermocouple reading with a reference probe.
Temperature Too Low (Under-Temperature Alarm). The temperature is below the low limit. Causes: heater failure, open circuit, or thermocouple drift (reading high). Corrective action: Check heater resistance (should be a few ohms). If open, replace heater. If heater is good, check power supply and controller output.
Rate-of-Change Alarm (Fast Rise or Fall). The temperature changes faster than the set limit (e.g., >5°C/second). Causes: thermocouple intermittent contact, heater short, or sudden melt flow. Corrective action: Check connectors for tightness. If the alarm occurs during injection, it may be normal-adjust the rate limit higher.
Sensor Drift Alarm (some advanced controllers). The controller detects that the thermocouple has drifted beyond a set tolerance (e.g., 2°C). Causes: aging, oxidation, or contamination. Corrective action: Calibrate the sensor with a reference. If drift exceeds the sensor's specification, replace it. This alarm is preventive-don't ignore it.
Power Output Alarm. The controller reports that power output has been at 100% for too long (e.g., >10 minutes). Causes: heater failure, poor thermocouple contact (reading low), or excessive heat loss. Corrective action: Check heater current. Also check thermocouple insertion depth and thermal grease. If the mold is cold, this may be normal during startup.
General Troubleshooting Flowchart. (1) Note the alarm code and zone. (2) Check the controller display for temperature and power. (3) Visually inspect the connector and cable. (4) Measure resistance at the mold connector. (5) If resistance is normal, test the controller input with a simulator. (6) If the controller passes, the sensor is faulty-replace it. (7) If the controller fails, the input module may be damaged-contact the controller supplier.
Simulator Testing. A thermocouple simulator generates a known millivolt signal. Connect it to the controller input (disconnecting the sensor). Set the simulator to a temperature (e.g., 280°C). If the controller reads within ±1°C, the controller is good and the sensor/wiring is at fault. This isolates the problem quickly.
Documentation. Keep a log of alarms and corrective actions. If a zone alarms repeatedly, investigate the root cause (e.g., vibration, corrosion, installation). Patterns reveal systemic issues.
Training. Train operators on basic alarm interpretation: red light = stop, yellow = check. Provide a laminated quick-reference card with common alarm codes and actions. Empower them to reset non-critical alarms after checking safety.
Preventive Measures. Most alarms can be prevented by regular maintenance: visual inspections, resistance checks, and calibration. Set the rate-of-change limit appropriately-too low causes nuisance alarms, too high delays detection.
Case Study: Frequent Over-Temperature Alarms. A plant had repeated over-temp alarms on one zone. The thermocouple was reading 20°C low due to a loose connector. The controller overheated the zone. After tightening the connector and recalibrating, the alarms stopped.
Controller Documentation. Keep the controller manual accessible. Alarm codes vary by manufacturer (e.g., Husky, Yudo, Milacron). Ensure your reference matches your controller type.
Emergency Contacts. Post emergency contact numbers for after-hours support from your controller and thermocouple suppliers. Quick phone support can resolve issues without a site visit.
Review and Improve. After each alarm event, review the response time. Was the alarm resolved within the target (e.g., 30 minutes)? If not, improve the procedure. Continuous improvement reduces downtime over time.
