OPC-UA - Knowledge Base
Overview of OPC-UA (Open Platform Communications Unified Architecture) for building automation — nodes, security, gateway limitations, and common integration pitfalls.
What OPC-UA Is
OPC-UA (Open Platform Communications Unified Architecture) is a platform-independent industrial interoperability standard that replaces legacy OPC-DA. It provides secure, structured data exchange between automation systems, SCADA platforms, historians, and cloud services. In building automation, OPC-UA sources are typically converted to BACnet or Modbus via a protocol gateway.
Core Concepts
| Concept | Description |
|---|
| Node | The fundamental OPC-UA element — variables, objects, methods, and views are all nodes |
| Namespace | Hierarchical organization of nodes within a server’s address space |
| NodeID | Unique identifier for each node (numeric, string, GUID, or opaque format) |
| Security Mode | Certificate-based authentication and encryption built into the protocol |
| Subscription | Event-driven data delivery via monitored items (gateway may use polling instead) |
| Product Key | Per-unit firmware activation key required for OPC-UA driver on QuickServer |
Gateway Capabilities
| Capability | QuickServer Support |
|---|
| OPC-UA Client (read) | ✅ Supported |
| OPC-UA Client (write) | ❌ Not supported — requires custom development (~3 days) |
| OPC-UA Server | ❌ Not supported |
| Polling mode | Sequential polling (not subscription-based) |
[!CAUTION] QuickServer’s OPC-UA client is read-only. If the integration requires writing setpoints or commands to the OPC-UA server, confirm this at pre-sales. Write capability requires custom firmware development.
Integration Prerequisites
- OPC-UA server IP address — must be a routable IP (not
localhost or 127.0.0.1).
- NodeID / namespace export — list of nodes to read.
- Read vs. write requirements — clarify before quoting.
- Security certificates — if the server requires certificate-based authentication.
- OPC-UA product key — required per QuickServer unit for firmware activation.
Common Problems
- Read-only assumption — customers expect bidirectional control; discovering the write limitation mid-project causes escalation.
- Recovery mode “FORBIDDEN” error — a malformed configuration can remove the OPC-UA firmware. Recovery requires reloading firmware via the QuickServer recovery procedure.
- Localhost IP constraint —
127.0.0.1 is not routable from the gateway. The server must be on an accessible network IP.
- Certificate misconfiguration — authentication or encryption failures when certificates are missing, expired, or in the wrong format.
- Missing product key — OPC-UA firmware requires a per-unit product key for activation.
| Tool | Type | Description |
|---|
| UaExpert | Client | Free OPC-UA client — node browsing, data access, certificate management. Most popular free OPC-UA client in the industry. |
| Prosys OPC UA Browser | Client | Free OPC-UA client for node browsing and value reading. Lightweight alternative to UaExpert. |
| Prosys OPC UA Simulation Server | Simulator | Free OPC-UA server simulator with configurable nodes for development and testing. |
Related Pages
Related content
Overview of DNP3 (Distributed Network Protocol) for utility and SCADA integration — protocol levels, master/outstation architecture, and common configuration pitfalls.
Overview of Johnson Controls Metasys N2 protocol for building automation — variants, point counts, device addressing, and common integration pitfalls.
Overview of MQTT (Message Queuing Telemetry Transport) for building automation — publish/subscribe model, TLS security, broker configuration, and cloud integration.
Need more help?
If this page does not resolve the issue, contact Chipkin support with the product model,
protocol details, and any diagnostics you have already captured.
Open Chipkin Support
