SOFTWARE SUPPORT / NODE-RED

Node reference

Find the purpose, example nodes and configuration checks for each category.

CORE

Common nodes

Trigger a message, inspect its contents and observe errors or state changes.

InjectDebugCatchStatusCompleteLinkComment

Start with Inject and Debug. Configure Catch for errors reported by nodes, and inspect Status separately.

PACKAGED / MODEL DEPENDENT

Hardware nodes

Connect the flow to supported serial ports and hardware interfaces.

Serial inSerial outSerial requestGPIO

Match wiring and serial settings. One physical serial port has one owner; GPIO availability and pin mapping depend on the hardware.

CORE

Function nodes

Transform values, route messages and control when information is emitted.

FunctionChangeSwitchRangeDelayTriggerRBETemplate

Validate types before scaling. Rate limits and delays are not a persistent offline message queue.

CORE

Network nodes

Exchange messages with a broker, service or application.

MQTT inMQTT outHTTP inHTTP responseHTTP requestWebSocketTCPUDP

Configure the endpoint, credentials and required TLS settings. Confirm the result at the receiver, not only in Debug.

CORE

Sequence nodes

Split, collect, order and group related messages.

SplitJoinSortBatch

Preserve sequence metadata and define the completion condition. Bound batch size and waiting time.

CORE

Parser nodes

Convert structured text into message properties and back.

JSONCSVXMLYAML

Check the actual payload type and encoding. A format parser does not interpret an undocumented industrial protocol.

CORE / PROJECT CONFIGURATION

Storage nodes

Read files, write records and retain selected application state.

FileFile inContext

Choose the permitted storage path, capacity and retention policy. Memory context is not durable storage.

PACKAGE DEPENDENT

Advanced nodes

Add industrial acquisition and management with compatible packages.

Modbus ReadModbus GetterModbus WriteSNMP

Modbus and SNMP integrations are available in the documented runtime. Confirm installed versions, device roles, point types and write authorization.

INTEGRATION PATH

PLC nodes & integration

Bring verified PLC readings into a flow for processing and reporting.

PLC acquisitionMQTT inPayload mapping

Use the delivered PLC acquisition service or a verified compatible node. Confirm the PLC model and driver; Modbus support is not universal PLC support.

PROJECT ADAPTATION

CNC integration

Connect machine data through an agreed controller interface.

CNC controllerProtocol adapterNode-RED flow

Provide the machine and controller model, API or protocol, data list and permissions. CNC connectivity is assessed as a project integration.

INTEGRATION PATH

IEC104 integration

Reuse a confirmed IEC104 data path in a local application.

IEC104 serviceMessage mappingNode-RED flow

Agree the master or slave role, point addressing and command feedback with the delivered service. A gateway IEC104 function does not by itself provide a Node-RED node.

PROJECT ADAPTATION

BACnet integration

Plan a building-equipment data path around the actual BACnet interface.

BACnet equipmentProtocol adapterNode-RED flow

Confirm BACnet/IP or MS/TP, objects, instances and read/write scope. BACnet connectivity is assessed as a project integration.

PACKAGED / DELIVERY CHECK

OPC UA nodes

Work with OPC UA endpoints, nodes and application data.

OpcUa-ItemOpcUa-ClientOpcUa-BrowserOpcUa-Server

OPC UA integration is available in the documented runtime. Check endpoint security, certificates, NodeIds and installed node help on the delivered unit.

PROJECT CONFIGURATION

History & trends

Turn readings into time-stamped records and useful trends.

TimestampFileDashboard

Define timestamps, retention, restart behavior and storage limits. A chart, context store and historical database serve different purposes.

Modbus to MQTTEnlarge diagram +
Modbus to MQTTNative Node-RED 3.0.2 editor. Isolated examples use simulated inputs; hardware commissioning is separate.
OPC UA nodesEnlarge diagram +
OPC UA nodesNative Node-RED 3.0.2 editor. Isolated examples use simulated inputs; hardware commissioning is separate.
Hardware nodesEnlarge diagram +
Hardware nodesNative Node-RED 3.0.2 editor. Isolated examples use simulated inputs; hardware commissioning is separate.
WhatsApp