← ClaudeAtlas

cia402-motionlisted

Load before answering any question about a CiA 402 / DS402 (IEC 61800-7) servo, stepper or frequency-inverter (VFD) drive over EtherCAT (CoE) or CANopen: vendors depart from the profile in ways that look standard, and this skill holds the checked facts and a sequence planner. Covers a drive that won't enable or is stuck in Switch on disabled or Fault, statusword and controlword values, fault reset, quick stop and halt, modes (CSP, CSV, CST, PP, PV, VL, homing) and the 0x6060/0x6061 mode switch, homing methods (0x6098), touch probe, user units and gear/feed (0x608F, 0x6091, 0x6092), 0x603F error codes, PDO mapping per mode, CANopen NMT/SYNC/PDO bring-up, and any vendor's drive, with checked pages on where named drive families depart from it. Not for TwinCAT NC axes and MC_ blocks (twincat-motion), CODESYS SoftMotion, servo loop tuning, EtherCAT network faults (ethercat-diagnostics), ESI files (ethercat-esi), SERCOS/SoE drives (AX5000), or safety PLC logic (TwinSAFE); never writes safety functions (STO, SLS).
SionVerhoef/cia402-motion · ★ 0 · Data & Documents · score 72
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