I/O
This tab provides steps that either wait for an I/O signal as input or control an I/O device as output.
On I/O
This trigger step pauses the scenario until a specific signal on a specific I/O device changes to the selected state, either HIGH (active) or LOW (inactive).
| Parameter | Type | Description |
|---|---|---|
| IO device | Mandatory | The I/O device that this step listens to. |
| Aliases | Mandatory | The signal on the I/O device and the state that triggers this step, for example <alias>.HIGH or <alias>.LOW. |
Examples
Example 1: Printing a Pallet Label when the Wrapper or Palletizer Reports a Finished Pallet
When the wrapper or palletizer reports a finished pallet, the On I/O step receives the signal. The Check If Production Running step then verifies whether there is an active production associated with the line linked to this coding scenario. If a production is running, the Send print job to printer step sends the pallet label to the printer. The Create logistic unit from printer log step creates a new logistic unit from the resulting printer log entry, and the Assign aggregation to logistic unit step assigns the pallet layer to it. The Set status to logistic units step then sets the selected status on the newly created pallet.
If no production is running, the scenario terminates at the Check If Production Running step, and no pallet label is printed.

Example 2: Print-and-Apply Triggered by a Product Sensor, Limited to the Order Quantity
When a light barrier detects a product at the labeling station, the On I/O step receives the signal. The Check If Production Running step verifies whether there is an active production on the line. The Evaluate counter step then compares the current value of the selected counter with the configured comparison value, for example whether it is Less than the order quantity. Only if the condition is true does the Send print job to printer step send the label to the printer, and the Increment counter step then increases the counter by the configured increment step.
Once the counter reaches the order quantity, the scenario stops silently at the Evaluate counter step, so no labels are printed beyond the ordered quantity.

Limitations
- The step only reacts to the signal configured in Aliases on the selected I/O device. Only one signal can be selected per step.
- The step triggers when the signal changes to the selected state. A signal that stays in that state does not trigger the scenario again.
- The signal carries no data. Subsequent steps work with the production data of the line, for example the active product or production order.
Set I/O
This action step sets one or more signals on an I/O device to the active (ON) state, optionally for a defined duration. Use it to control devices on the line, for example to trigger a label applicator, a reject pusher, a signal lamp, or a “ready” signal reported to another machine.
| Parameter | Type | Description |
|---|---|---|
| IO device | Mandatory | The I/O device that this step controls. |
| Aliases | Mandatory | The signals to activate on the I/O device. Several signals can be selected. |
| signal-duration (ms) | Optional | The duration in milliseconds for which the signals stay active. When the duration ends, the signals are reset to the inactive state. If not set, the signals remain active until explicitly reset. |
Examples
Example 1: Labeling Different Packaging Types on One Conveyor
Cartons and flat trays run on the same conveyor and are labeled by different applicators: cartons on the side, trays from the top. Two light barriers are mounted at different heights: the low sensor detects every package, the high sensor detects only the taller cartons.
When the low sensor detects a package, the On I/O step receives the signal. The Check I/O step then checks the high sensor: only if it reports the HIGH state, so the package is a carton, does the scenario continue. The Send print job to printer step sends the label to the side printer, and the Set I/O step activates the signal of the side applicator with a signal-duration (ms) of, for example, 500 ms, so the applicator applies the label and the signal is switched off automatically.
The trays are handled by a second coding scenario with the same steps, in which the Check I/O step expects the LOW state of the high sensor, and the Send print job to printer and Set I/O steps use the top printer and the top applicator. Both scenarios start on the same signal, and the Check I/O step decides which of them continues, so each package receives the correct label from the correct applicator.

Example 2: Pushing Out Rejected Products after an Error
When a coding scenario raises an error, for example because a layout is not found, the On exception step triggers the scenario. The Stop Production step stops the production on the line, and the Set I/O step activates the signal of the reject pusher with a signal-duration (ms) of, for example, 200 ms. The pusher removes the product that could not be labeled from the conveyor and retracts when the duration ends, so no unlabeled product travels downstream.

Limitations
- The step always sets the signals configured in Aliases; it cannot select a signal based on production data. To output a value from the master data, for example a packaging type code, use Write binary value to WebIO.
- The scenario does not wait for signal-duration (ms) to end; it continues with the next step immediately.
- If signal-duration (ms) is not set, the signals stay active until a Reset I/O step switches them off.
- If the I/O device cannot be reached or is not found, the signals are not changed, but the scenario still continues and no error is reported. The problem is only recorded in the system logs.
Reset I/O
This action step resets one or more signals on an I/O device to the inactive (OFF) state, optionally for a defined duration. Use it to switch off a signal that was activated by a Set I/O step without a signal duration, for example a signal lamp or a “ready” signal reported to another machine on the line.
| Parameter | Type | Description |
|---|---|---|
| IO device | Mandatory | The I/O device that this step controls. |
| Aliases | Mandatory | The signals to deactivate on the I/O device. Several signals can be selected. |
| signal-duration (ms) | Optional | The duration in milliseconds for which the signals stay inactive. When the duration ends, the signals are set back to the active state. If not set, the signals remain inactive until explicitly set. |
Examples
Example 1: Withdrawing the Ready Signal when Production Stops
The labeler reports a “ready” signal to the upstream machine, for example a filler or case packer, which feeds products to the labeling station only while this signal is active. When a production is stopped on the line, the On production stopped step triggers the scenario. The Reset I/O step switches the “ready” signal off, so the upstream machine stops feeding products and no unlabeled products are sent downstream. The Clear print buffer step then clears the pending print data on the selected printer, so leftover print jobs are not printed when the next production starts.

Example 2: Withdrawing the Ready Signal after an Error
When a coding scenario raises an error, for example because a layout is not found, the On exception step triggers the scenario. The Stop Production step stops the production on the line, and the Reset I/O step switches the “ready” signal off, so the upstream machine immediately stops feeding products to the labeling station.

Limitations
- If signal-duration (ms) is set, the signals are switched on again when the duration ends. Leave it empty if the signals must stay off, as in the examples above; to switch them on again later, use a Set I/O step, for example in a scenario triggered by On production started.
- A signal activated by Set I/O with a signal-duration (ms) is switched off automatically when the duration ends; a Reset I/O step is not required for it.
- The scenario does not wait for signal-duration (ms) to end; it continues with the next step immediately.
- If the I/O device cannot be reached or is not found, the signals are not changed, but the scenario still continues and no error is reported. The problem is only recorded in the system logs.
Check I/O
This action step checks the current state of one or more signals on an I/O device at the moment the step is executed. For each signal, the expected state is selected: HIGH (active) or LOW (inactive). If all signals are in their expected state, the scenario continues with the next step. If not, the scenario ends at this step without an error, and the following steps are skipped. Use this step to make the following steps conditional on the state of the line, for example a sensor, a safety guard, or a machine ready signal.
Unlike the On I/O trigger step, which waits for a signal to start the scenario, this step does not wait: it reads the signal state once, when the scenario reaches it.
| Parameter | Type | Description |
|---|---|---|
| I/O device | Mandatory | The I/O device whose signal is checked. |
| Aliases | Mandatory | The signals to check on the I/O device, each with its expected state, for example <alias>.HIGH or <alias>.LOW. Several signals can be selected; all of them must be in their expected state. |
Examples
Example 1: Checking Line Clearance before a New Production
When a product or production order is assigned to the production line, the Product or order assigned step triggers the scenario. The Check I/O step then checks the signal of the line clearance sensor, which reports that no products from the previous production are left on the conveyor. Only if the signal is in the expected state does the Start Production step start the production on the line, and the Send print job to printer step sends the label to the printer.
If products are still on the line, the scenario ends at the Check I/O step, and the new production is not started.

Example 2: Checking That the Safety Guard Is Closed before Starting Production
A scanner on the production line reads the barcode of a production order, for example from the work order document. The On scan step receives the scanned value, and the Select production order step identifies the matching production order from the master data. The Check I/O step then checks the signal of the safety guard. Only if the signal reports that the guard is closed does the Start Production step start the production on the line.
If the guard is open, for example because the operator is still loading a new label roll, the scenario ends at the Check I/O step, and the production is not started.

Limitations
- This is not a trigger step: it does not wait for the signal, but checks its state once when it is executed. To start a scenario when a signal is received, use On I/O.
- If the signals are not in their expected state, the scenario ends silently: no error is reported, and an On exception scenario is not triggered.
- If a selected signal is not reported by the I/O device, the check fails and the scenario ends at this step.
Write binary value to WebIO
This action step writes a binary value, assembled from a data source, to the individual bits of a WebIO device.
| Parameter | Type | Description |
|---|---|---|
| Data source table | Mandatory | The table that provides the value to write. |
| Data source field | Mandatory | The field that provides the value to write. |
| IO device | Mandatory | The WebIO device to write to. |
| Bit 0 alias | Mandatory | The signal alias mapped to bit 0. |
| Bit 1 alias … Bit N alias | Optional | Additional signal aliases mapped to higher bits. |
Set I/O after no read scan
This action step sets one or more signals on an I/O device when the preceding scan step received a no-read, that is, when the scanner reported the value configured in no-read data instead of a barcode. Use it to signal a failed read on the line, for example with a signal lamp, a horn, a reject pusher, or an input of a PLC.
| Parameter | Type | Description |
|---|---|---|
| IO device | Mandatory | The I/O device that this step controls. |
| Aliases | Mandatory | The signals to activate on the I/O device after a no-read. Several signals can be selected. |
| signal-duration (ms) | Optional | The duration in milliseconds for which the signals stay active. When the duration ends, the signals are reset to the inactive state. If not set, the signals remain active until explicitly reset. |
Examples
Example 1: Reporting a No-Read to the PLC of the Line
A scanner on the conveyor reads the barcode of each product. The On scan step receives the scanned value. If the barcode could not be read, the Set I/O after no read scan step sends a pulse with a signal-duration (ms) of, for example, 500 ms to the “no-read” input of the PLC that controls the conveyor.
The PLC then decides what the machine does, according to its own logic: for example, it stops the conveyor immediately, or only stops the line after three no-reads in a row. The coding scenario detects the problem, and the PLC handles the reaction of the machine.

Limitations
- The stop on no-read option of the preceding scan step (On scan or On any scan) must be disabled. If it is enabled, the scenario stops at the scan step on a no-read, and this step is never executed.
- The step only reacts to the no-read result of a preceding scan step in the same scenario. Without a scan step, the signals are never activated.
- The scenario does not wait for signal-duration (ms) to end.
- If the I/O device cannot be reached or is not found, the signals are not changed, and no error is reported. The problem is only recorded in the system logs.