How To
Summary
This document explains how to verify real‑time OPC DA data using Matrikon OPC Explorer.
OPC DA (OLE for Process Control – Data Access) is a Windows‑based industrial communication protocol that relies on COM/DCOM technology. Due to these dependencies, OPC DA operates only on Windows systems and requires appropriate DCOM configuration, firewall permissions, and authentication settings.
To successfully establish a connection to an OPC DA server, the following details are required:
Program ID (Server ID) of the OPC DA server
Machine Name (Server Name / Hostname) where the OPC DA server is hosted
Objective
The objective of this document is to provide customers with a clear and detailed procedure to:
- Connect to an OPC DA server using Program ID and Machine Name
- Browse and load OPC DA tags
- Read live values using Matrikon OPC Explorer
- Understand the technical requirements needed for successful OPC DA communication
Environment
Operating System
OPC DA requires:
- Microsoft Windows (any version with COM/DCOM support)
OPC DA does not run natively on Linux, macOS, or embedded systems.
Required Information for Connection
To connect Matrikon OPC Explorer to an OPC DA server, you must have:
| Information Required | Description |
| Program ID (Server ID) | The COM class identifier for the OPC DA server. Example: Matrikon.OPC.Simulation.1 |
| Machine Name (Server Name) | The Hostname or IP address of the machine running the OPC DA server. Example: PROD-SERVER01 |
These values are mandatory for establishing a successful OPC DA connection.
Software Components
- Matrikon OPC Explorer installed on the client machine. ( This is one of the third‑party tools used to verify OPC data connectivity; alternative third‑party tools may also be used if preferred )
- OPC DA server installed on the target system
- DCOM Runtime enabled
- RPC services running
Network Requirements (For Remote Connections)
Component | Requirement |
RPC Endpoint Mapper | TCP Port 135 must be open |
DCOM High Ports | Dynamic ports 49152–65535 must be allowed |
Windows Authentication | Must support NTLM or Kerberos authentication |
Firewall | DCOM communication must be allowed on client and serve |
If any of these ports are blocked, browsing and data updates will fail.
DCOM Security Requirements
DCOM configuration settings must grant the client:
- Access Permissions
- Launch Permissions
- Activation Permissions
Identity must be correctly configured (common choice: This User or Interactive User).
Steps
How to Check OPC DA Data Using Matrikon OPC Explorer
Step 1 — Open Matrikon OPC Explorer
- Launch the application using Run as Administrator to ensure full DCOM access.
Step 2 — Connect Using Program ID and Machine Name
- In Matrikon OPC Explorer, go to Server → Connect
- Select Custom Connect (if available)
- Enter the following:
- Program ID (Server ID) → e.g., Vendor.OPCServer.1
- Machine Name (Server Name) → e.g., PLANT-SERVER01
- Click OK to initiate connection
Note:
If Matrikon OPC Explorer lists the server automatically, you can select it from the list.
However, manual entry using Program ID + Machine Name is required in secure or restricted environments.
Step 3 — Browse the OPC DA Namespace
Once connected:
- Expand the server tree in the left pane
- Navigate through folders (branches)
- Identify the tags you want to monitor
If browsing fails:
- DCOM access or firewall rules are likely blocking communication
Step 4 — Add Tags to a Monitoring Group
- Select the tags
- Right-click → Add Item
- Choose Add to Group
- Tags appear in the right pane with real-time data fields
Step 5 — Observe Real-Time Values
The following fields will update automatically:
- Value
- Quality (GOOD / BAD / UNCERTAIN)
- Timestamp
A stable OPC DA connection will show:
- Quality = GOOD
- Timestamp updating with data changes
If values do not update:
- Reverse DCOM callback may be blocked
- Client firewall may be blocking incoming DCOM traffic
Additional Information
Note: Matrikon OPC Explorer is a widely used OPC diagnostic utility for connecting to OPC DA servers, browsing the address space, and monitoring real‑time data values along with associated quality codes and timestamps. Although any compatible third‑party OPC client may be utilized, This tool is commonly installed and used by clients on their systems
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
30 March 2026
UID
ibm17263395