Explainer
HMI OPC UA Server vs Client: Which Direction Works
Short answer
OPC UA support on an HMI spec sheet almost always means the panel runs a server that serves its tags to external clients. Reading PLC symbols by name needs an OPC UA client driver, a separate capability you verify in the driver list for your exact software release, target and license.
On this page
- The two directions are two different drivers
- What a compliance listing actually tells you
- The HMI as OPC UA server
- The HMI as OPC UA client: the capability often missing
- The name-based paths that are not OPC UA
- Working the direction check: EOTE 3.1 SP1A reading symbols from an M251
- Verifying direction before you commit code
- Questions asked
OPC UA support on an HMI datasheet almost always describes one direction: the panel running a server that hands its own tags to outside clients. Reading controller symbols by name is the opposite direction, and it needs an OPC UA client driver in the panel, a separate implementation the server listing says nothing about. Before you restructure PLC code or map a single register, write down which way the data has to flow and check the driver list for that direction, for your exact software release, panel target and license tier.
The two directions are two different drivers #
In OPC UA, the server owns the data and its address space; clients connect to it to read, write and subscribe. An HMI can fill either role, but as two separate functions with separate configuration.
As a server, the panel publishes its own tags on an endpoint, and SCADA, historian or MES clients connect in. As a client, the panel opens an outgoing connection to a server running on the controller or on a gateway, and browses the symbol configuration there. A client never reaches controller hardware directly; it gets everything by requesting it from a server.
| Data path you need | Panel role | What gets configured | Proven by an OPC UA line on the datasheet? |
|---|---|---|---|
| SCADA, historian or MES reads panel tags | Server | An endpoint on the panel that clients connect to | Yes, when the listing covers the server |
| Panel reads controller symbols by name | Client | An outgoing connection to the controller's server, then a browse of its symbols | No, that is a separate driver |
What a compliance listing actually tells you #
Certification entries name one product and the part of the specification it was certified against. Most HMI entries cover the server, so the logo proves the panel can expose data. In the case this article grew out of, the listing offered as proof belonged to a different product in the same vendor's range, which is the trap in its purest form: a certificate for product A says nothing about client capability in product B. Read the entry, not the logo, and read it for the product you hold.
The HMI as OPC UA server #
Serving outward is the common implementation. In EcoStruxure Operator Terminal Expert it was available in the 3.1 SP1A era, in both the EOTE form and the Pro-face BLUE form, under documented conditions: the release must be one whose documentation retains the function, the panel target must support it (HMISTO7 did not), and the license must be Professional (Basic did not).
None of that touches PLC-facing reads. A panel serving tags to a historian and a panel browsing controller symbols are different capabilities, and only the first is what the spec sheet means.
The HMI as OPC UA client: the capability often missing #
Client duty needs three things in the panel project: an OPC UA client driver, the controller server's endpoint with its security policy and credentials, and a browse of the symbol configuration. CoDeSys-based controllers such as the M251 and M262 can publish a symbol configuration fit for name-based addressing, so the hard part is not on the controller side. It is whether the panel software ships the client that consumes it.
For Operator Terminal Expert at 3.1 SP1A, no PLC-facing OPC UA client driver was documented. The documented controller-facing paths were the SoMachine symbol link and Modbus. Compare that with a panel that talks to a controller over its native driver, where direction questions barely arise: see Connecting an HMI Panel to an S7-1500 PLC for that setup end to end.
The name-based paths that are not OPC UA #
The SoMachine symbol link gave name-based access without OPC UA, and it broke in the field: the cybersecurity changes in Machine Expert 1.2 were not matched by a simultaneous HMI-side release, because the two products were maintained by separate teams with a release gap between them. The only workaround reported at the time was disabling the controller password. That strips an authentication control from the controller, so use it as a commissioning diagnostic and restore the password afterwards, never as a production configuration. A fix was announced for a coming release with no confirmed number, so confirm it in the release notes for the exact pair you run.
The address-based fallback is Modbus: locate the variables in registers, then translate the controller's Modbus addressing into the panel's address format. It works, but every variable is mapped by hand, and code organized in DUTs gets flattened toward located variables. Once running, refresh behaves like any polled Modbus link, and the failure modes in Why HMI Indicators Stay Off Over Modbus RTU Polling apply.
Working the direction check: EOTE 3.1 SP1A reading symbols from an M251 #
Inputs:
- Paths required by the project: 1, the panel reads M251 controller symbols by name (the requirement that started this article).
- Panel software: EcoStruxure Operator Terminal Expert 3.1 SP1A.
- Documented capability lines at that release: 3, the OPC UA server (subject to release, target and license: HMISTO7 excluded, Professional required), the SoMachine symbol link (name-based, controller-facing), and Modbus (address-based, controller-facing).
- Controller-side engineering software in the pair: Machine Expert, whose 1.2 cybersecurity change broke the symbol link pending the HMI-side fix.
Rule in words: match every required path against a documented driver line for the exact release, target and license, and count only lines that serve the direction you need.
The arithmetic:
- Required: 1 path.
- Available documented lines: 3.
- The OPC UA server serves the outward direction, a direction mismatch, so it matches 0 of the 1 required path.
- The symbol link serves the right direction but fails the version-pair test against Machine Expert 1.2 unless the controller password is disabled.
- Modbus serves the right direction and works.
- Matching lines: 1 of 1, and it is Modbus. Name-based OPC UA access: 0 of 1.
Decision: short by even one driver line, stop restructuring code and change the path instead of forcing the software. Commission over Modbus with located variables and a mapped address table, prove each data type read and write before handover, and keep the password workaround out of the delivered machine. If name-based OPC UA access is a hard requirement, this software pair fails selection: move the client role to a gateway that subscribes to the controller and republishes, or step up to the advanced-panel software the vendor positioned for targets like the G3U, which at the time was Vijeo Designer.
Verifying direction before you commit code #
- Write the arrow first: external client to panel server, or panel client to controller server.
- In the panel project, look where communication settings live: if OPC UA appears only as a server or remote-access setting and never in the controller connection list, the client role does not exist in that release.
- Read the driver matrix for the exact software pair, panel target and license tier, not the family brochure.
- Test against a live controller or a simulation with authentication enabled, and record the versions that passed.
Questions asked
Can I turn the HMI's OPC UA server into a client by changing settings?
No. The server and the client are separate implementations. The server publishes the panel's own tags on an endpoint and waits for connections; a client opens an outgoing session to someone else's server, browses its address space and subscribes. Endpoint settings on the panel, such as port and security policy, change how outsiders reach the panel, never what the panel can reach. If the client driver is absent from the release, no server setting creates it.
If the PLC runs an OPC UA server with symbol configuration, doesn't any OPC UA device work with it?
Not by itself. A controller-side server with symbol configuration publishes the variables, but something must still connect as a client to browse and subscribe to them. That client can be the HMI, a SCADA node or a gateway, and the security settings, meaning policy and authentication, must match on both ends before any data moves.
Is a gateway a workable substitute for a missing client driver in the panel?
Yes, and it is the usual fix. A PC or server node runs the OPC UA client, subscribes to the controller's server and republishes the data to the systems that need it, including older OPC DA clients. You add one box, one failure point and some latency, so it suits plant-level data delivery better than fast panel interaction.
Does an OPC Foundation certified listing cover both directions?
Usually not. A certification entry names the product and the part of the specification it was certified against, and most HMI entries cover the server. Read the profile named in the listing before treating the logo as client support, and remember the entry describes the listed product only, not other products in the same range.