Skip to main content
Version: 3.0 (next)

Siemens S5 Nodes

Read and write Siemens SIMATIC S5 PLCs from pipelines, by S5 address, through an S7 gateway or a CP 1430. Each operation has its own node in the Pipeline Designer: S5 Read and S5 Write.

For connection setup, the addresses and per-function fields, see the Siemens S5 connection guide.

Configuration Quick Reference​

FieldWhat you chooseDetails
ParametersConnection, Function, Function Parameters, Timeout OverrideSelect the S5 connection profile, pick a function, bind parameters with expression support, and optionally override the timeout.
SettingsDescription, Timeout (seconds), Retry on Timeout, Retry on Fail, On ErrorNode description, maximum execution time, retry behaviour on timeout or failure, and error strategy. All execution settings default to pipeline-level values.

S5 Read Node​

Read many named points, each by its S5 address, in the fewest requests. Runs an s5.read function.

Node Configuration​

ParameterTypeRequiredDescription
ConnectionSelectionYesS5 connection profile to use
FunctionSelectionYesAn s5.read function from the selected connection
Function ParametersDynamicVariesThe points list. See Read Points.
Timeout OverrideNumber (seconds)NoOverride the default function timeout

Output Structure​

{
"result": {
"count": 2,
"values": { "speed": 100.0, "pump": true },
"quality": "good",
"totalDataPoints": 2,
"totalReads": 2
},
"_metadata": { "success": true, "functionId": "<function-id>", "durationMs": 7, "timestamp": "2026-10-01T08:30:00Z" }
}
FieldTypeDescription
result.valuesobjectEvery point by its name, typed by its address: a boolean for a bit; a number for a byte, word, double word, KG value, timer (milliseconds) or counter
result.countnumberHow many points were decoded
result.qualitystringgood: a refusal from the S5 fails the node instead of storing a value
result.totalDataPointsnumberHow many points were requested
result.totalReadsnumberHow many reads of the S5's memory the points were grouped into
{{ $node["S5 Read"].result.values.speed }}
How points are grouped

Points are grouped by area (inputs, outputs, flags, timers, counters) and by data block; within a group, neighbours within 32 bytes are read together, up to 255 bytes a read. totalReads shows how many reads the node used.


S5 Write Node​

Write one value to a data block item (DB10.DW4, DB10.DD4:KG, DB10.D4.15), a flag (M10.2, MW10) or an output (A4.0, AW4). Runs an s5.write function.

Inputs, timers and counters are refused: the CPU reads its inputs in every cycle, and timers and counters run in the program. A single bit, or one byte of a data word, is written by reading its byte or word, changing it and writing it back. A write is sent once: the node does not repeat it when the S5 does not answer, and it does not run in a pipeline started by a late (replayed) input.

Node Configuration​

ParameterTypeRequiredDescription
ConnectionSelectionYesS5 connection profile to use
FunctionSelectionYesAn s5.write function from the selected connection
Function ParametersDynamicVariesaddress and value, both of which support ((paramName)) templates. See Write Point.
Timeout OverrideNumber (seconds)NoOverride the default function timeout

Output Structure​

{
"result": {
"address": "DB10.DW4",
"dataType": "WORD",
"value": 750
},
"_metadata": { "success": true, "functionId": "<function-id>", "durationMs": 6, "timestamp": "2026-10-01T08:30:00Z" }
}
FieldTypeDescription
result.addressstringThe S5 address written
result.dataTypestringThe type the address holds: BIT, BYTE, WORD, INT, DWORD, DINT or KG
result.valueanyThe value written

A write to an input, timer or counter, or a value the address cannot hold (70000 for a WORD), fails the node before anything is sent to the S5.

Safety first

Validate values in a Condition node before writing to equipment. A flag or data word the program reads can start a motor or open a valve immediately.


Settings Tab​

Both S5 node types share the same Settings tab:

SettingTypeDefaultDescription
DescriptionText—Optional description displayed on the node
Timeout (seconds)NumberPipeline defaultMaximum time the node may run before timing out
Retry on TimeoutTogglePipeline defaultAutomatically retry the node if it times out
Retry on FailTogglePipeline defaultAutomatically retry the node if it fails
On ErrorSelectionPipeline defaultError strategy: Pipeline Default (the pipeline's Error Handling setting), Stop Pipeline or Continue Execution

When left at their defaults, these settings inherit from the pipeline-level execution configuration.