Workflow · 6 steps
Probe, resolve byte order, and finalize a tool pack
Use a selected tool target to collect one raw sample, confirm byte order, then regenerate all selected targets with the confirmed layout.
How it works
Plan Reads
Compile bounded Modbus read blocks
Starts with a reviewed Modbus map. Produces a bounded Modbus read plan.
Build Tool Pack
Build several Modbus tool outputs
Starts with a reviewed Modbus map, a bounded Modbus read plan, one reviewed request for a bounded probe. Produces the selected read-only tool files.
One bounded device read
Run one bounded read against the reviewed endpoint and save the returned raw 16-bit words. Do not scan or write.
Starts with the selected read-only tool files. Produces a bounded raw-word sample.
Confirm byte order from one sample
Evaluate every supported layout from one immutable sample, record one human confirmation, and apply it.
Starts with a reviewed Modbus map, a bounded raw-word sample. Produces a reviewed Modbus map.
Plan Reads
Compile bounded Modbus read blocks
Starts with a reviewed Modbus map. Produces a bounded Modbus read plan.
Build Tool Pack
Build several Modbus tool outputs
Starts with a reviewed Modbus map, a bounded Modbus read plan, the reviewed endpoint and selected final tools. Produces the selected read-only tool files.
When it stops
- No selected target.
- Unresolved route or unit identifier.
- No raw words.
- No human byte-order confirmation.
- Write request detected.
Show machine-readable contracts
modbus-map/v1→modbus-read-plan/v1modbus-map/v1,modbus-read-plan/v1,probe-tool-pack-request/v1→modbus-tool-pack/v1modbus-tool-pack/v1→capture/v1modbus-map/v1,capture/v1→modbus-map/v1modbus-map/v1→modbus-read-plan/v1modbus-map/v1,modbus-read-plan/v1,final-tool-pack-request/v1→modbus-tool-pack/v1