$analyze-capture
Analyze Capture
Check a saved set of Modbus samples for communication, timing, stale-value, range, rate, and byte-order problems.
GROUP 05Analyze read dataGitHub source ↗
WHAT YOU GET
A clear result you can inspect
It writes `analysis.json` from a limited JSON or CSV capture. The report shows planned reads that never ran, missing or duplicate samples, timing gaps, flat values, range or rate problems, and raw-word patterns that can point to byte order.
HOW IT RUNS
Runs each selected check over the saved samples
SKILL.mdprocess + safetyscripts/run.pybundled local PythonRuns each selected check over the saved samples. The script separates communication findings from signal findings. The report states the sample period, thresholds, checks it skipped, and any missing metadata. It reports evidence and possible relationships, but it does not claim a root cause.
SYNTHETIC ANALYSIS
Separate connection problems from signal problems
The report describes what the capture shows. It does not claim a root cause.
WHERE IT FITS
Used in these workflows
EXAMPLE REQUEST
Ask for the result in your own words.
Use this example as a starting point. Replace the file names and details with your own.
$analyze-capture Analyze `pump-run-2026-08-08.csv`. Check for missed reads, timing gaps, repeated values, values outside the limits in `analysis-options.json`, and sudden changes. Keep communication and signal findings separate.