Siemens LOGO! Nodes

Read and write Siemens LOGO! 8 logic modules from pipelines, by LOGO! address. Each operation has its own node in the Pipeline Designer: LOGO! Read and LOGO! Write.

For connection setup, the address map and per-function fields, see the Siemens LOGO! connection guide.

Configuration Quick Reference

Field	What you choose	Details
Parameters	Connection, Function, Function Parameters, Timeout Override	Select the LOGO! connection profile, pick a function, bind parameters with expression support, and optionally override the timeout.
Settings	Description, Timeout (seconds), Retry on Timeout, Retry on Fail, On Error	Node description, maximum execution time, retry behaviour on timeout or failure, and error strategy. All execution settings default to pipeline-level values.

---

LOGO! Read Node

Read many named points, each by its LOGO! address, in the fewest requests. Runs a logo.read function.

Node Configuration

Parameter	Type	Required	Description
Connection	Selection	Yes	LOGO! connection profile to use
Function	Selection	Yes	A logo.read function from the selected connection
Function Parameters	Dynamic	Varies	The points list. See Read Points.
Timeout Override	Number (seconds)	No	Override the default function timeout

Output Structure

{
  "result": {
    "count": 2,
    "values": { "pump": true, "level": 512 },
    "quality": "good",
    "totalDataPoints": 2,
    "totalReads": 1
  },
  "_metadata": { "success": true, "functionId": "<function-id>", "durationMs": 6, "timestamp": "2026-10-01T08:30:00Z" }
}

Field	Type	Description
result.values	object	Every point by its name, typed by its address: a boolean for I, Q, M, NI, NQ and V bits; a number for AI, AQ, AM, NAI, NAQ, VB, VW and VD
result.count	number	How many points were decoded
result.quality	string	good: a refusal from the LOGO! fails the node instead of storing a value
result.totalDataPoints	number	How many points were requested
result.totalReads	number	How many reads of the LOGO!'s memory the points were grouped into

{{ $node["LOGO! Read"].result.values.level }}

How points are grouped

Every LOGO! area is a slice of one memory, so points close to each other share a read: the points are sorted by their place in memory, and neighbours within 32 bytes are read together, up to 255 bytes a read. totalReads shows how many reads the node used.

---

LOGO! Write Node

Write one value to a network input (NI, NAI) or a V memory address (V10.3, VB10, VW10, VD10). Runs a logo.write function.

The LOGO! program rewrites its inputs, outputs, flags and analog values every cycle, so those addresses are refused: to command a LOGO!, write a network input or a V address the program reads. A single bit is written by reading its byte, setting the bit and writing the byte back. A write is sent once: the node does not repeat it when the LOGO! does not answer, and it does not run in a pipeline started by a late (replayed) input.

Node Configuration

Parameter	Type	Required	Description
Connection	Selection	Yes	LOGO! connection profile to use
Function	Selection	Yes	A logo.write function from the selected connection
Function Parameters	Dynamic	Varies	address and value, both of which support ((paramName)) templates. See Write Point.
Timeout Override	Number (seconds)	No	Override the default function timeout

Output Structure

{
  "result": {
    "address": "NI5",
    "dataType": "BIT",
    "value": true
  },
  "_metadata": { "success": true, "functionId": "<function-id>", "durationMs": 5, "timestamp": "2026-10-01T08:30:00Z" }
}

Field	Type	Description
result.address	string	The LOGO! address written
result.dataType	string	The type the address holds: BIT, BYTE, INT or DINT
result.value	any	The value written

A write to an address the program owns, or a value the address cannot hold (70000 for a VW), fails the node before anything is sent to the LOGO!.

Safety first

Validate values in a Condition node before writing to equipment. A network input can start a motor or open a valve through the LOGO! program immediately.

---

Settings Tab

Both LOGO! node types share the same Settings tab:

Setting	Type	Default	Description
Description	Text	—	Optional description displayed on the node
Timeout (seconds)	Number	Pipeline default	Maximum time the node may run before timing out
Retry on Timeout	Toggle	Pipeline default	Automatically retry the node if it times out
Retry on Fail	Toggle	Pipeline default	Automatically retry the node if it fails
On Error	Selection	Pipeline default	Error 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.