1012 B
1012 B
Event and Alarm Codes v1
Status: draft canonical table for implementation.
Hard-stop faults — reset required
ESTOP_ACTIVATEDFORCE_OVER_LIMITENCODER_LOSTDRIVE_FAULTFT_SENSOR_INVALID
Recoverable pauses / warnings
FORCE_UNDER_LIMITSPINDLE_RPM_DEVIATIONTABLE_RPM_DEVIATIONHOST_COMMS_TIMEOUTARM_GEOMETRY_DIVERGENCE
Refused transitions / blocked starts
GEOMETRY_NOT_VALIDATEDARM_HANDLING_INTERLOCKWRONG_ARTIFACT_TYPESCHEMA_VALIDATION_FAILEDWRONG_MACHINE_IDCONTROLLER_VERSION_MISMATCHUNSUPPORTED_CAPABILITYILLEGAL_TRANSITION
Event fields
Every event should include:
{
"timestamp": "ISO-8601 or host monotonic mapping",
"code": "GEOMETRY_NOT_VALIDATED",
"severity": "info|warning|critical",
"state": "IDLE|MANUAL|...",
"detail": "short machine-readable or operator-readable detail"
}
Do not use free text as the only control signal. Human messages are for UI; codes are for software.