SV660N Keypad Panel Status Codes

Quick reference for the 5‑digit LED keypad on Inovance SV660N (MS1 / EtherCAT), as used on this stacker.

All digit layout and blink timings below are from the SV660N Advanced User Guide (status indication / Figure 8‑2), not from guesswork. The panel ↔ EtherCAT error map is maintained from the SV660N Troubleshooting Guide (fault tables → objects 0x603F / 0x203F) plus desk observations with IgH ethercat.

• How to read _28ry (official digit map)
• Terminology
  • AL ladder
• Official AL digit blink rules
  • Matches observed on this machine
• Servo status (4th–5th LEDs)
• Control mode (3rd LED)
• Ports CN3 / CN4
• Fault blink (different from AL blink)
  • How to read panel fault glyphs
• Panel ↔ EtherCAT common error map
  • Objects / CLI to read (common set)
  • Normal status (not faults)
  • EtherCAT / network faults
  • Drive / motor thermal & overload
• Everyday combinations on this machine
• References

How to read _28ry (official digit map)

The five LEDs show several fields at once (fixed positions). They do not time‑share / alternate full screens between 2 and ry.

  LED:   [ 1st ] [ 2nd ] [ 3rd ] [ 4th ] [ 5th ]
  field:  link    AL     mode    ---- servo ----
  ex.:     _       2       8       r       y

So what looks like _28ry is one composite readout:

Official spelling is ry (ready). On 7‑seg it is easy to misread as rdy.

Cross-check on the PC:

ethercat slaves -v    # State: INIT / PREOP / SAFEOP / OP

Terminology

AL ladder

cable / power-up
    →  INIT (1)     solid on panel
    →  PREOP (2)    blinks 400 ms   ← Idle master + cable in
    →  SAFEOP (4)   slow blink pattern
    →  OP (8)       solid           ← motion app target

Servo status (ry / rn) is independent of AL: the drive can show ry already in PREOP; it becomes rn after S‑ON / CiA402 enable (usually with AL in OP for bus control).

Official AL digit blink rules

From Advanced User Guide — Communication status (2nd LED):

Matches observed on this machine

So the blink is how PREOP (and SAFEOP) are drawn, not a separate “bus activity” metaphor and not a full-screen carousel.

Servo status (4th–5th LEDs)

When motor speed ≠ 0 RPM, the manual says the trailing letter can blink:

• In PREOP/SAFEOP: y / n blink at the same rate as AL digit 2 / 4
• In Init/OP: y / n blink at 2 Hz

(At standstill ready/ry, you typically only notice the AL digit blink in PREOP.)

Also listed in §4.2.3: reset / nr / ry / rn for general status display.

Control mode (3rd LED)

Stacker bring-up: CSP (8) via mode:=csp (default); CSV (9) via mode:=csv. Panel 3rd digit tracks 0x6060 / 0x6061.

Ports CN3 / CN4

Link may also be shown via 1st-LED - segments (PORT0 / PORT1) as in the digit map.

Fault blink (different from AL blink)

Do not confuse with PREOP’s single 2 blinking at 400 ms (normal).

How to read panel fault glyphs

The 7‑seg dot is tiny (especially when all five digits blink). What you actually read is a compact string:

Tables below put Panel (as read) first so you can look up what your eye saw without hunting for the dot.

Panel ↔ EtherCAT common error map

Use the keypad for the glyph you see, and IgH CoE / AL for the machine-readable view. Maintain this table when new faults show up on the stacker desk.

Objects / CLI to read (common set)

Healthy OP example (this machine): ethercat slaves → OP +; 0x6041=0x1637 (Operation enabled); 0x603F=0; 0x203F=0.

Encoding tip: for EtherCAT group faults, Troubleshooting Guide maps:

So panel EE083 = manual EE08.3 ⇒ 0x603F = 0x0E08, 0x203F = 0x3E080E08.

SDO upload needs a reachable mailbox (usually PREOP+). In OP it often still works; if upload fails, drop to PREOP or read after the fault is latched and link is back.

Normal status (not faults)

EtherCAT / network faults

Values for 0x603F / 0x203F are from SV660N Troubleshooting Guide. “Desk hint” = what we see on the PC.

Drive / motor thermal & overload

AL-only failures (panel may still show _28ry / drop toward _18ry without an E… code):

When filling a new row: record panel as read (no dot) → manual form → 0x6041 / 0x603F / 0x203F → one desk note.

Everyday combinations on this machine

| You see (panel) | Decode | Expected? | |—|—|—| | _18ry solid | AL Init + CSP + ready | Yes with RJ45 unplugged | | _28ry (2 blinks ~400 ms) | AL PREOP + CSP + ready | Yes with cable in, Idle master | | _48ry (4 slow blink) | AL SAFEOP + mode + ready | During app activate | | _88ry / _88rn (AL solid) | AL OP + CSP + ready/run | Target when CSP app is live (mode:=csp) | | _89ry / _89rn | AL OP + CSV + ready/run | Target when CSV app is live (mode:=csv); 3rd digit 9, not 8 | | nr | Not ready | Check main power, STO1/STO2 = 24 V | | All 5 flash + E… | Fault | Bad — see error map | | EE083 | EE08.3 cable / link | Reseat CN3 | | E6400 ↔ _88rn ~3 s | E640.0 + auto fault reset | Stop launch; cool; d03 | | E6200 blink | E620.0 motor overload | Wait ≥30 s; slower demos; d04 | | E6200 again ~5 s after ROS reset | Latch cleared, I²t/re-enable still overloaded | Stop launch; cool longer; d05 | | Shaft jumps after reset_fault pulse | CSP catch-up (target ≠ actual) | Not a move cmd; see d06 + docs/cia402_csp.md |

References

1. SV660N Series Servo Drive Advanced User Guide
   • Mirror: eec.by download
   • Digit map + blink timings: status indication / Figure 8‑2 (communication connection status, communication status, servo mode, servo status)
   • Also §4.2.3 Status Display (reset / nr / ry / rn, modes 1–A, AL 1/2/4/8)
2. SV660N Commissioning Guide (keypad overview; fault = all five LEDs blink)
   • Mirror: servotechnica.ru
3. SV660N Troubleshooting Guide (fault/warning codes, reset; Error Code 603Fh / Aux. Code 203Fh tables)
   • Example: mrosupply.com
   • H0b.34 fault log encoding; EE08 / EE10 families used in the error map
4. Inovance portal: inovance.com

Hardware on this project: SV660NS2R8I + MS1H4-40B30CBA334R, EtherCAT.