IMDTouchKnowledge BaseShop main store

How-to

Show PLC Variables in WebIQ Over OPC UA on ctrlX CORE

HMI and touchscreens Published 6 min read

Short answer

Live PLC data reaches a WebIQ HMI on ctrlX CORE when four layers line up: a PLC Symbol Configuration exposes the variables, the SMART HMI certificates are trusted, an OPC UA IO Handler points at the controller endpoint, and an HMI variable created by browsing is linked to a widget Item. Open the running project at port 10123 and prove the path by changing the PLC value and watching the widget follow.

On this page
  1. Install the minimum app set
  2. Publish the PLC variables in a Symbol Configuration
  3. Trust the SMART HMI certificates on the controller
  4. Create the OPC UA IO Handler in the IO Manager
  5. Create the HMI variable by browsing
  6. Link the variable to a widget
  7. Publish, start and open the project
  8. End-to-end check: one variable from the PLC to port 10123
  9. Read the blank-widget pattern
  10. Questions asked

Live PLC data appears in a WebIQ HMI on ctrlX CORE only when four layers line up: the PLC app publishes a Symbol Configuration that lists the variables, the SMART HMI certificates are trusted on the controller, an OPC UA IO Handler in WebIQ Designer points at the controller's endpoint, and an HMI variable created by browsing is linked to a widget Item. Work the sections in order, because each layer feeds the next: there is nothing to browse until the Symbol Configuration is downloaded and running, and no session at all until the certificate is trusted. The running project opens in a browser on port 10123, and you prove the whole path by changing the PLC value and watching the widget follow it.

Install the minimum app set #

The minimum set is three apps: the PLC app, the OPC-UA Server app and the WebIQ Runtime app. The controller also offers an OPC UA client app, but on this data path WebIQ itself is the client, so the server app is the one that has to run. Open the app list on the ctrlX CORE and confirm all three are installed and running before you configure anything in WebIQ, because each missing app has its own symptom:

  • No PLC app: nothing to browse, because the variables never exist.
  • No OPC-UA Server app: the IO Handler cannot connect and every widget stays blank.
  • No WebIQ Runtime app: the project has nowhere to publish to and serves no page.

Publish the PLC variables in a Symbol Configuration #

WebIQ reads PLC data through OPC UA, and the server only exposes what the PLC application lists in its Symbol Configuration. That configuration is the whole PLC-side contract with the HMI:

  1. Add a Symbol Configuration to the PLC app.
  2. Tick every variable the HMI must read or write; anything not ticked never reaches the browse dialog later.
  3. Login and run the application so the configuration is downloaded and active.

Two symptoms point straight back here. A variable missing from Browse was either not ticked, or the application was not downloaded and running after the change. A variable present but frozen means the PLC is stopped, so log in and start it. Every variable you add to the PLC later needs the Symbol Configuration edited and the application downloaded again before WebIQ can browse it.

Trust the SMART HMI certificates on the controller #

This step decides whether the IO Handler can be created at all. OPC UA secure channels refuse a client whose certificate is untrusted, so with the WebIQ certificate untrusted the handler creation throws an error no matter how correct the endpoint fields are.

  1. Open certificate management on the ctrlX CORE.
  2. Find the SMART HMI certificates for WebIQ.
  3. Mark them trusted.
  4. Go back to WebIQ Designer and create the IO Handler again.

Certificate trust is the same gate for any OPC UA client; reading OPC UA tags once the client certificate is trusted shows the identical rule from a Java client talking to a Kepware server. A different failure, rejection of a SHA1-signed certificate, is its own fault with its own procedure in fixing OPC UA SHA1 signed certificates that are not trusted.

Create the OPC UA IO Handler in the IO Manager #

  1. Create a new project in WebIQ Designer.
  2. Open the IO Manager.
  3. Select Create Entry and add an IO Handler of the OPC UA type.
  4. Fill the highlighted fields with the endpoint and authentication values of your own controller; they are per-device values, not constants you can copy from another installation. On ctrlX CORE virtual, the reported working combination required the OPC UA namespace copied exactly.

If creation still fails with the certificates trusted, the fault has moved into these fields, meaning the endpoint, port or authentication, not into security.

Create the HMI variable by browsing #

  1. Open the Process Data Manager and select the Variables section.
  2. Use Browse to walk the OPC UA address space; arrays and structures are reached the same way as single variables.
  3. Select the PLC variable and confirm that the HMI variable is created.

Browse listing your variables proves the handler and the certificates. If Browse is empty, go back to the Symbol Configuration and certificate sections; if Browse works and a widget still shows nothing, the fault is in the widget link.

  1. Open the Layout Manager.
  2. Select the widget that will display the value.
  3. Link the HMI variable to the widget Item.

Publish, start and open the project #

  1. Save the project.
  2. Click Publish to transfer it to the WebIQ runtime.
  3. Go to Home, find the project in the Project List and Start it; a published project that was never started serves no page at all.
  4. Open a browser at yourIPaddress:10123/projectname/, with your controller address and project name in place of the two words, and enter the username and password configured for the project.

If the station has to come back up on its own after a controller restart instead of someone starting it from the list, starting a published WebIQ HMI project without Runtime Manager covers that setup. A login prompt that rejects you is a project-credential problem, not a PLC problem; once the page loads, only the data path is left.

End-to-end check: one variable from the PLC to port 10123 #

Inputs, each taken from the procedure above: one variable ticked in the Symbol Configuration with the application logged in and running; one OPC UA IO Handler whose endpoint and authentication come from your own controller; one HMI variable created with Browse and linked to one widget Item; an app set of 3 required and 3 running; the WebIQ runtime port, 10123; and the project name exactly as saved before publishing.

Rule in words: the path is live only when the value shown in the browser equals the value in the PLC after each side changes it once, and the count of blank widgets tells you which layer broke if it does not.

Arithmetic:

  • App check: 3 required minus 3 running leaves 0 missing, so the controller side is complete and any fault is downstream.
  • URL: controller address, then a colon, then 10123, then a slash, then the project name, then a slash, giving yourIPaddress:10123/projectname/.
  • Traffic check: 1 change at the PLC must appear as 1 change on the widget, and 1 write from the HMI must appear as 1 new value in the PLC.

Do the write test on a variable that cannot command motion, or with the machine in a safe state.

Result: the pass condition is the widget following one change in each direction. Decision: if it passes, the path is proven end to end and you commission the remaining tags the same way without touching the handler; if the widget misses even one change, the path is down, so stop and read the pattern below before changing anything else.

Read the blank-widget pattern #

The blank widgets split the four layers into shared and per-tag, and that split gives you the decision before you open a single tool:

What you see Broken layer Fix
Every widget blank Shared: untrusted certificate, IO Handler not connected, wrong endpoint, or Symbol Configuration never downloaded Work the certificate and IO Handler sections first
One widget blank, the rest live That tag: variable not ticked, HMI variable not created by Browse, or widget Item not linked Re-tick and download, re-browse, or re-link that one tag
Values shown but never change PLC stopped Log in and run the application

All blank is a binding fault: work the certificate and IO Handler sections and leave the tags alone. One blank is a tag fault: work that single variable from the Symbol Configuration to the widget Item and leave the handler alone.

Questions asked

Why does creating the IO Handler fail even though the endpoint is correct?

The ctrlX CORE is rejecting the WebIQ client certificate, and OPC UA refuses an untrusted client at session setup. Work the certificate section first, then create the handler again. Only when that still fails should you recheck the handler fields themselves, the endpoint, port or authentication.

Does this data path work on ctrlX CORE virtual, or only on the hardware controller?

Yes, it works on the virtual controller. Reported working setups needed two things exactly right: the OPC UA namespace copied exactly as shown, and the client certificate trusted. Treat those two as the critical items when you commission the data path against a virtual controller before the hardware exists.

A variable I added to the PLC does not appear in Browse. What did I miss?

The Symbol Configuration is a static list, not a live view of the application. Every variable the HMI needs must be ticked in it, and the application must be logged in and running again before the OPC UA server exposes the new variable to Browse.

The login works but every widget is blank. Is that a password problem?

No. Credentials only decide whether the page opens at all. Once you are in, every widget blank is a binding fault in the shared layer: an untrusted certificate, an IO Handler that never connected, a wrong endpoint, or a Symbol Configuration that was never downloaded. Fix that layer before touching individual tags.

Do I need the OPC UA client app on the ctrlX CORE for this?

No. The controller offers both an OPC UA server app and a client app, but on this data path WebIQ itself is the client and connects to the server app. Install the app set listed in the first section and skip the client app.

Keep reading

  • How-to

    Connecting Operator Terminal Expert to a Third-Party PLC

    Operator Terminal Expert connects to a third-party PLC through a protocol both ends document — typically Modbus TCP or RTU, or OPC UA with the HMI as client and the PLC as server. Select the driver for your exact terminal target, match the driver's address notation to the PLC's register references, and prove one read and one controlled write on the deployed terminal before mapping the rest.

    HMI and touchscreens

  • Explainer

    HMI OPC UA Server vs Client: Which Direction Works

    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.

    HMI and touchscreens

  • Troubleshooting

    Displaying a PLC Real Value Over Modbus on an HMI

    An INTEGER display that reads the register proves the link, station and address, so a blank REAL display is a 32-bit mapping fault. Declare the HMI variable as a 32-bit float on the register pair (40064/40065), set the device double-word order to Low Word First to match the PLC, and give the numeric field six integer digits for 628402.0.

    HMI and touchscreens