PlcConsole

Batch Operations

Batch Operations is the reusable PLC workflow page. It is where you build, save, export, import and execute recurring command sequences.

Manual Home
Batch Workflow Builder and Presets PLC Operation Rows Timing Rows Preset State Import and Export Batch Operations Batch Chaining Preset Management

Batch Workflow

The batch screen edits a working copy first, not the saved preset. Review row order, register family, values and timing before saving a repeatable sequence.

Add PLC Operation for a read, write or discrete control command. Add Delay to wait locally for a duration or Wait Until to pause until the selected time of day. Delay and Wait Until do not send PLC traffic. Arrange rows with the explicit move controls, then run only after the screen reports valid configuration.

Execution is sequential and cancellable. Stop Batch cancels the active sequence, including long delays and time waits. While running, editing, reordering, adding and removing rows is disabled so the displayed plan cannot diverge from the sequence being executed.

A named preset is a saved copy of the current working batch. Switching away from modified work asks whether to save, discard or cancel. Imported presets are validated and never execute automatically; when an imported identifier already exists, choose Replace, Keep Both or Cancel.

PLC Operation rows: choose Read, Write or Control. Reads retain returned values in the completed row. Writes accept decimal, 0x-prefixed hexadecimal or 0b-prefixed binary values. Control rows apply the selected discrete action. A batch needs an active PLC profile only when it contains one or more PLC Operation rows.

Timing rows: Delay waits for its configured duration. Wait Until uses hour, minute and second pickers for a time today. If that time has already passed when the row is reached, it completes immediately. Both timing rows remain cancellable and send no PLC traffic.

Batch Builder and Presets

Batch Operations

Batch Operations screen with row editing and execution controls

Description

This is the main editing surface for a batch preset. It keeps the working row list visible, shows the register family and operation type for each PLC row and exposes the execution controls that start the currently loaded batch only after validation passes.

Execution header: The execution header shows progress, the current action and the selected preset while the batch is running.

Execution safety: Operation rows are disabled from reordering during execution so the running order cannot drift under the command queue.

Working copy: The screen’s working copy makes it safe to experiment before saving a repeatable sequence.

Batch Chaining

Batch Operations screen showing chained command rows and execution flow

Description

Chaining is the reason batch operations exist. A read row can feed later write or control rows, a delay can be inserted to let the PLC settle and a wait-until row can pause the batch until a specific time of day.

Row types: Read, write, control, delay and wait-until rows are all part of the same batch flow.

Pacing tools: Local delay and time-wait rows do not send PLC traffic, which means they are safe pacing tools rather than device commands.

Action editors: The model stores row type separately from the operation details, so the screen can switch between action-specific editors without losing the preset structure.

Preset Management

Batch Operations screen with preset management menu open

Description

The overflow menu is the preset manager. It is where the working batch turns into a named preset, where existing presets are edited or duplicated and where JSON import/export lives so the configuration can be backed up or shared.

Preset state: Unsaved Batch means the working rows have never been saved. Modified means a loaded preset has changed. Loading an unchanged saved preset intentionally shows no extra status label.

Edit preset: Edit Batch Preset changes its Name and Description. Editing operation rows is separate and marks the working batch Modified until it is saved.

Import and export: JSON contains reusable configuration only, never execution progress, read results, errors or last-run state. Imported presets are validated and never execute automatically.

Destructive action: Delete All Presets removes every saved preset, but the current working batch stays open and unsaved.

Separation: The menu keeps destructive actions separate from the editing surface, which reduces accidental taps during normal batch construction.