What the S# alarm means

The safety subsystem reports a fault with a numeric code; safety-related stops or enable failures result until cleared. We see this alarm constantly when servicing Omron SmartController (ACE / Viper / Cobra) systems, and the first on-site pass usually pins down the cause.

Most common causes

  • Safety interlock input (XSLV/XSYS) open
  • Safety circuit wiring fault
  • Faulty safety relay or I/O
  • Mismatch between safety settings and hardware
Field note: Based on our handling experience the first cause is the most frequent — use it as your starting point.

Step-by-step field fix

  1. Read the specific safety code on the status panel or in the ACE diagnostics
  2. Check the XSLV safety interlock and XSYS cables between robot and controller
  3. Verify all safety inputs match the configuration
  4. Inspect safety relays and I/O modules
  5. Correct the fault and re-enable; do not jumper safety inputs
Safety first: For OMRON s, this alarm is the safety circuit itself: jumpering a door switch or forcing a contactor removes the protection entirely - no protective action when something happens, and no defensible account of responsibility. The self-serviceable action is Read the specific safety code on the status panel or in the ACE diagnostics; anything past that falls under the e-stop chain and safety circuit and needs a certified engineer.

How we diagnose safety-chain faults on site

OMRON s belongs to the safety chain & e-stop family. On OMRON s the failing stage is e-stop chain plus safety inputs on the OMRON robot controllers (including SCARA and cobot companions) - continuity of one series loop: e-stop buttons, door switches, light curtains, safety relays and the enabling device. We start reading OMRON s at controller status indicators and the software error list (letter prefixes RC / SW / V / M / D / A / E).

The chain involved in OMRON s runs: e-stop / door / curtain -> safety relay (dual channel) -> controller safety input -> motor-off and brake apply.

OMRON s is sometimes designed behaviour, not a fault - Releasing the enabling device (three-position switch) in manual mode triggers a protective stop by design, yet plenty of sites report it as an alarm. The switch enables only in the middle position; fully released or pushed through both open - and pushing through is the instinctive panic reaction, which is exactly what the designers used. Knowing that clears a good share of mysterious protective stops. The real fault is worn contacts inside the switch, showing up as poor contact in the middle position.

Field notes on this page cover OMRON s (Safety System Fault (Code N)); written by the Henghuan repair team, updated 2026-10-01.

Still unresolved? Our engineers are standing by

Just tell us the alarm code, the robot model and which program was running, and our engineers will help you narrow it down — phone and video remote diagnosis are both free.

Get a Free Remote Diagnosis See Repair Services

Hotline: +86-20-39029800 · WhatsApp: +86-188-1886-2860

Related Safety Chain & E-Stop alarms

ES — E-Stop Active
Same family: this code belongs to the Safety chain & e-stop alarms family - the page collects all Safety chain & e-stop-family codes we have handled, with the common inspection order and spares.
Other brands: we also keep field-fix libraries for ESTUN · INOVANCE · EFORT and more — see the complete alarm code hub.

Frequently asked questions

QWhat does the OMRON s alarm mean?

The safety subsystem reports a fault with a numeric code; safety-related stops or enable failures result until cleared. We see this alarm constantly when servicing Omron SmartController (ACE / Viper / Cobra) systems, and the first on-site pass usually pins down the cause. OMRON s sits in the safety chain & e-stop family; on our work orders the highest-frequency trigger for this code is "Safety interlock input (XSLV/XSYS) open".

QCan I clear a OMRON s alarm myself?

Whether OMRON s clears on its own depends on the outcome of "Read the specific safety code on the status panel or in the ACE diagnostics". Finish the flow with "Correct the fault and re-enable; do not jumper safety inputs" to confirm OMRON s - do not skip it. If that step is clean, the second most frequent cause on OMRON s is "Safety circuit wiring fault". Two attempts and still there means stop: OMRON s involves the e-stop chain and safety circuit, and running OMRON s on can turn a repairable fault into a replacement.

QA safety-chain fault like OMRON s stops the line - how fast can you be here?

The commonest causes we see on OMRON s are "Safety interlock input (XSLV/XSYS) open, Safety circuit wiring fault, Faulty safety relay or I/O", so we stock the van against those. For OMRON s specifically, we stock along the loop: safety relays, common door switches, e-stop buttons, light-curtain pairs and terminal blocks. For OMRON s, a safety-chain fault stops the whole line, so we rank it top priority and pre-triage by phone: door switch, e-stop or relay. Before we roll, tell us what OMRON s shows on controller status indicators and the software error list (letter prefixes RC / SW / V / M / D / A / E) and what the machine was doing - phone or video triage is free.

The notes on OMRON s were summarized by the Henghuan Robotics repair team from on-site service. The alarm interpretation is our empirical summary for troubleshooting reference and may vary by controller and software version — please check Omron documentation or contact us with questions. Henghuan is an independent service provider, not affiliated with or endorsed by Omron.