HEART Embedded Systems logoHEART

HEART system.main-function-lost H-01001

Main function lost. The system cannot do its main job. Every HEART MUST be able to detect this.

CodeHEART system.main-function-lost; inside a message "code": "system.main-function-lost"
H-numberH-01001: area 01, code 001
Areasystem: The whole system
Typical severitycritical. A product may set another for its own case.
Applies toEvery product with a HEART

Likely causes

How to fix or prevent it

  1. Read the alert's explanation and cause: they say which part stopped and why, often with a second fault code.
  2. If a safety device tripped, find the reason before you reset it. Never bypass a cut-out to get the job running again.
  3. Refill or replace what ran out (filament, water, paper, card), then resume the job.
  4. Check power and fuses to the working part, and look for messages from the product's own controller or display.
  5. Restart the product only if its manual says that is safe. If the job stops again, stop and call service.
  6. To prevent it: follow the maintenance schedule, and act on earlier warnings such as system.main-function-degraded, power.battery-low or storage.nearly-full.

What the HEART does by itself

Every HEART must notice this (Autonomy Level A1). It raises a critical alert, sets its status to failing, and tells a person through the owner's escalation route at once. A Playbook may try one safe step that the product allows, such as restarting a stuck software worker, but a HEART never resets a safety device or works around an interlock. The alert resolves by itself when the main job works again.

When to call service

At once if a safety device tripped (a thermal cut-out, an earth-leak trip, a welded contactor), if anything smells hot or looks damaged, or if the job stops again after one restart. For medical or life-safety products, follow the product's own emergency instructions first.


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)