← ClaudeAtlas

twincat-motionlisted

Load before answering, or opening any file, about a Beckhoff TwinCAT 3 NC axis or Tc2_MC2 motion code: NC behaviour hides in axis parameters and look-alike error codes that models get wrong; this skill holds checked facts, an NC error table and an .xti lint and diff tool. Covers an axis that won't enable or move, MC_ blocks (MC_Power, MC_Home, MC_MoveAbsolute, MC_Halt, MC_Stop, MC_Reset) and axis wrappers, NC error codes, homing, scaling and controller parameters, gearing and cam coupling (MC_GearIn, MC_CamIn: a slave that jumps, lags or drops out), touch probe and registration (MC_TouchProbe, MC_PhasingRelative), and reading, linting or diffing any _Config/NC/Axes .xti file, also two versions of one. Not for Structured Text that only mentions an axis (twincat-st), a CiA 402 statusword or 0x6098 on its own (cia402-motion), AL status codes or working counters (ethercat-diagnostics), ESI files (ethercat-esi), TwinCAT CNC, or TwinSAFE design; never writes safety functions such as STO.
SionVerhoef/twincat-motion · ★ 1 · AI & Automation · score 74
Install: claude install-skill SionVerhoef/twincat-motion
# twincat-motion > **Reference material only. Not for safety functions.** Motion configuration must be > reviewed and validated by a qualified engineer before it runs on a machine. ## Goal Get a TwinCAT NC axis configured, enabled, homed and moving correctly, and diagnose why it is not. **Scope and safety.** Output is a draft for a qualified engineer. Never generate or modify logic that implements a safety function; 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, and never work around one.** An NC stop, a software limit or homing is not safety. A missing hardware enable or open STO is diagnosed and named, never bridged, forced or simulated: `references/boundaries.md`. 2. **Never move an axis or change a running system.** Propose motion as code or steps that a person runs, at reduced limits first. No motion commands, no ADS parameter writes, no activating a configuration. 3. **Never edit an `.xti` file without an explicit go-ahead.** Configuration changes go out as a parameter-change table or an Automation Interface script that a person applies. A direct edit only when the user agrees to that change, with XAE closed, the file committed and a diff afterwards: `references/config-changes.md`. 4.