cia402-motionlisted
Install: claude install-skill SionVerhoef/cia402-motion
# cia402-motion
> **Reference material only. Not for safety functions.** Drive configuration must be
> reviewed and validated by a qualified engineer against the drive's own documentation.
## Goal
Bring a CiA 402 drive through its state machine into Operation enabled in the right mode, and
find out why it will not get there.
**Scope and safety.** Output is a draft for a qualified engineer. Never generate or modify
logic that implements a safety function (STO, SS1, SLS, safe homing); refer to the safety
controller instead. When proposing motion code, always state the assumed units, limits and
enable sequence, and tell the user to test with reduced limits. Never claim code is verified
unless it was run on hardware.
## Rules that override everything else
1. **Never author a safety function.** A controlword sent from a standard PLC is not STO, and a
quick stop is not a safety stop. Decline, name the hardware route, and offer the functional
part, labelled as not safety: `references/safety-boundary.md`. This holds when the user has
no safety PLC and asks anyway.
2. **The order is where code goes wrong, not the bits.** Every rule below was broken in
generated code whose prose explanation got it right. Check your own code against them:
- hold each command until the statusword confirms it, with a timeout per transition
- fault reset: bit 7 low → high → low, *then* 0x0006 → 0x0007 → 0x000F; release bit 7 after
every attempt; never 0x0080 held, never 0x008F