Plan Reads

Group the points in a checked map into small, read-only Modbus requests for function codes 01–04 before building Node-RED, Modpoll (BETA), or ModScan (BETA) files.

use this skill ↓back to all 20 skills

GROUP 03Plan and run one readGitHub source ↗

WHAT YOU GET

A clear result you can inspect

It writes `read-plan.json`. Each bounded request has a unit ID, register area, start offset, quantity, interval, and the points returned by that block. Every active point must appear in exactly one request.

HOW IT RUNS

01 · GUIDESKILL.mdprocess + safety

02 · EXECUTEscripts/run.pybundled local Python

Groups adjacent points and checks each limit. The planner uses zero unused addresses between points unless you set a different maximum gap. It checks register quantities, target limits, point slices, and the exact map version. Any map change makes the old plan invalid and requires a new plan.

WHERE IT FITS

Used in these workflows

Probe, resolve byte order, and finalize a tool packUse a selected tool to collect one sample, confirm byte order, then rebuild the final tool files.view workflow →Build a multi-target tool packCreate Node-RED, Modpoll (BETA), and ModScan (BETA) files from one validated map and read plan.view workflow →

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.

CODEX$plan-reads

CLAUDE CODE/modbus-skills:plan-reads

CURSOR + OTHER CLIENTSUse the client’s native skill invocation.

$plan-reads

Create a read plan from `reviewed-map.json`. Keep separate points in separate blocks unless they are directly adjacent, and show which points are in each Modbus request.

GitHub source ↗