← ClaudeAtlas

twincat-scopelisted

Records and analyses TwinCAT 3 Scope measurements. Use when the user works with TwinCAT Scope, Scope View, TE1300, TF3300, Scope Server, .svdx, .tcscopex, .svd, .tcmproj, a scope project, a trace, a recording, a measurement, an oscilloscope view of PLC data, channels, sample rate, oversampling, a scope trigger, or exporting scope data to CSV/TDMS. Also use when diagnosing machine behaviour from recorded data: following error, position lag, torque spikes, velocity saturation, jitter, cycle-time overruns, axis oscillation, drive tuning, 'what happened at 12 seconds', or any request to scan, summarise or find events in a large measurement file, and when a directory contains .tcscopex or .svdx files even if the user does not say TwinCAT. Do NOT use for WRITING or REVIEWING Structured Text or PLC code - this skill is for measurement and diagnosis, not authoring. Do NOT use for Siemens or Rockwell trace tools.
SionVerhoef/twincat-scope · ★ 1 · AI & Automation · score 74
Install: claude install-skill SionVerhoef/twincat-scope
# twincat-scope — measure a machine, then actually read the measurement > **Reference material only. Not for safety functions.** Every scope configuration, recording > plan and diagnosis you produce must be reviewed and validated by a qualified engineer > against the drive and platform documentation before anyone acts on it. Recording is the easy half. Ten minutes of twenty channels at 1 kHz is twelve million samples — far too large to read, and the thing you are looking for is usually three samples wide. So this skill never hands back samples: it hands back summaries, events and pictures, and only returns real rows once a time range is known. **Not for authoring code.** This skill measures and diagnoses. Once the data has named a fault, writing the PLC fix is a different job. Load the companion skill `twincat-st` for it if it is installed; otherwise hand off to whatever covers ST authoring in this project. ## The four rules 1. **No safety logic.** This skill writes no code, safety code least of all; reading, explaining and recording safety signals is fine. 2. **Never write to or activate a live machine.** Reading measurements is safe. Writing a variable, activating a configuration, or switching Run/Config mode is a human gesture — propose the command, do not run it. 3. **Never claim something is verified that you have not verified.** There may be no TwinCAT installation on this machine. What has and has not been seen working in TwinCAT is under *Status* b