HEART performance.overshoot H-05006

Overshoot. A controlled value goes past its target by more than the system's stated limit, such as a room getting colder than its setpoint.

Likely causes

• A controller tuned too aggressively, such as a PID on a 3D printer's hotend.
• Outside heat or cold the controller does not see: sun through a window, a door left open.
• A sensor in the wrong place, or reading late.
• A valve or heater that does not shut off fully.

How to fix or prevent it

1. Check the readings: how far past the target, and for how long.
2. Check the sensor's place and reading against another thermometer or gauge.
3. Re-tune the controller, or use the product's auto-tune.
4. Check that the valve or heater really switches off.

What the HEART does by itself

It raises a warning when the value goes past its target by more than the product's stated limit, such as 1.5 °C. It does not retune the controller by itself. It resolves when the value is back near the target.

When to call service

If it continues after tuning, or the value overshoots in a way that could do harm (too hot, too high a pressure).

Related codes

• sensors.drift H-08005: Sensor drift
• actuators.position-mismatch H-09002: Position mismatch
• actuators.short-cycling H-09004: Short-cycling

Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written HEART storage.full. Things that simply happen, such as system.started, are event types, not faults. The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7. All of it, as data: fault-codes.json.

All fault codes, by area · All fault codes, by H-number · Problem types (API errors)