twincat-motionlisted
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.