RuleGo RuleGo
🏠Home
  • Quick Start
  • Rule Chain
  • Standard Components
  • Extension Components
  • Custom Components
  • Visualization
  • RuleGo-Server
  • AOP
  • Trigger
  • Advanced Topics
  • Performance
  • Standard Components
  • Extension Components
  • Custom Components
  • Components Marketplace
  • Overview
  • Quick Start
  • Routing
  • DSL
  • API
  • Options
  • Components
🔥Editor (opens new window)
  • RuleGo Editor (opens new window)
  • RuleGo Server (opens new window)
  • StreamSQL
  • AI Agent Framework
  • TPCLAW Agent Platform (opens new window)
  • Github (opens new window)
  • Gitee (opens new window)
  • Changelog (opens new window)
  • English
  • 简体中文
🏠Home
  • Quick Start
  • Rule Chain
  • Standard Components
  • Extension Components
  • Custom Components
  • Visualization
  • RuleGo-Server
  • AOP
  • Trigger
  • Advanced Topics
  • Performance
  • Standard Components
  • Extension Components
  • Custom Components
  • Components Marketplace
  • Overview
  • Quick Start
  • Routing
  • DSL
  • API
  • Options
  • Components
🔥Editor (opens new window)
  • RuleGo Editor (opens new window)
  • RuleGo Server (opens new window)
  • StreamSQL
  • AI Agent Framework
  • TPCLAW Agent Platform (opens new window)
  • Github (opens new window)
  • Gitee (opens new window)
  • Changelog (opens new window)
  • English
  • 简体中文

广告采用随机轮播方式显示 ❤️成为赞助商
  • Quick Start

  • Rule Chain

  • Standard Components

  • Extension Components

    • Extension Components Overview
    • filter

    • action

    • transform

    • external

    • ai

    • ci

    • IoT

      • IoT Components Overview
      • Input Endpoints

      • Protocol Acquisition

        • OPC_UA Read
          • Configuration
          • Relation Type
          • Execution Result
        • OPC_UA Write
        • Modbus Node
        • Serial Communication
        • S7 Read
        • S7 Write
        • EtherNet/IP Read
        • EtherNet/IP Write
        • SNMP Read
        • SNMP Write
        • Modbus Read Points Node
        • Modbus Write Points Node
        • Universal Acquisition Read
        • IoT Write
        • IEC 104 Read
        • IEC 104 Write
        • FINS Node
        • FINS Read
        • FINS Write
        • MC Node
        • MC Read
        • MC Write
        • DL/T 645 Node
        • DL/T 645 Read
        • DL/T 645 Write
      • Time-Series Database

      • 控制

      • IoT Scenarios
    • Stream Processing

    • Service Discovery

    • file

  • Custom Components

  • Components marketplace

  • Visualization

  • AOP

  • Trigger

  • Advanced Topic

  • Agent Framework

  • RuleGo-Server

  • FAQ

  • Endpoint Module

  • Support

  • StreamSQL

目录

OPC_UA Read

x/opcuaRead Component: v0.28.0+ OPC UA Read component, used to read data from an OPC UA server. It can read data from a single node or multiple nodes.

Additional extension library required: rulego-components-iot (opens new window)

# Configuration

Field Type Description Default
server string OPC UA server address; supports ref:// to reuse a connection within the same chain None
policy string Security policy, options include: None, Basic128Rsa15, Basic256, Basic256Sha256 None
mode string Communication mode, options include: None, Sign, SignAndEncrypt None
auth string Authentication method, options: Anonymous, UserName, Certificate Anonymous
username string Username (required when auth is UserName) None
password string Password (required when auth is UserName) None
certFile string Certificate file path (required when auth is Certificate) None
certKeyFile string Private key file path (required when auth is Certificate) None
points array Point list (standard read method); each item has name/addr/type, addr = OPC UA NodeID None

Point Fields (points array element):

Field Type Description
name string Point name; used as Data.name in output
addr string OPC UA NodeID, e.g. ns=2;s=Temperature
type string Data type, unified enum BOOL/INT16/UINT16/INT32/UINT32/INT64/UINT64/FLOAT32/FLOAT64/STRING

Security Policy (policy) Options Meaning:

  • None: No security policy is used.
  • Basic128Rsa15: Uses basic 128-bit encryption and RSA15 signing.
  • Basic256: Uses basic 256-bit encryption.
  • Basic256Sha256: Uses basic 256-bit encryption and SHA256 signing.

Communication Mode (mode) Options Meaning:

  • None: No mode is used.
  • Sign: Message signing.
  • SignAndEncrypt: Message signing and encryption.

Read Points (Standard Method): specified via the points configuration, where addr is the OPC UA NodeID. Format:

[
  {"name": "temp", "addr": "ns=2;s=Temperature", "type": "FLOAT32"},
  {"name": "humidity", "addr": "ns=2;s=Humidity", "type": "FLOAT32"}
]
1
2
3
4

Legacy Compatibility: you may also pass a NodeID list via the message payload msg.Data (kept for backward compatibility only; points is recommended). Format:

[
  "ns=3;i=1003",
  "ns=3;i=1005"
]
1
2
3
4

# Relation Type

  • Success: Execution is successful, the message is sent to the Success chain.
  • Failure: Execution fails, the message is sent to the Failure chain.

# Execution Result

The query result is reassigned to msg.Data and passed to the next node through the Success chain, format:

[
  {"name": "temp", "value": 25.3, "timestamp": 1721900000000000000, "error": ""}
]
1
2
3
Edit this page on GitHub (opens new window)
Last Updated: 2026/07/29, 07:07:39
Modbus Server Endpoint
OPC_UA Write

← Modbus Server Endpoint OPC_UA Write→

Theme by Vdoing | Copyright © 2023-2026 RuleGo Team | Apache 2.0 License

  • 跟随系统
  • 浅色模式
  • 深色模式
  • 阅读模式