Safety in Selmo does not arise from add-on modules, but from the way the system is structured:
Every action has feedback.
Every state knows its active zones.
Every interlock automatically stops the release.
Every conflict (PairCheck) is detected.
Every manual command (MXIC) is secured.
As a result, the behavior is not only logically correct but also verifiable from a safety perspective.
Last updated 4 months ago
Was this helpful?