How-to
Connecting a Windows mobile HMI panel to ctrlX over OPC UA
Short answer
The panel connects when five things line up: a working network path, the OpcuaItf.cfg client configuration, a Basic256Sha256/SignAndEncrypt self-signed certificate with a matching application URI, a ctrlX user holding permissions for the OPC UA Server and PLC apps, and a GVL named KeTop shared in the symbol configuration. Prove the link by trusting the client certificate on the CORE and watching the Alive variable increment every 1 second.
On this page
- What the setup requires
- Give the panel a reachable address
- Install the OPC UA client on the panel
- Create the client certificate
- Prepare the CORE
- Share the panel variables in the PLC project
- Trust the client certificate on the CORE
- Proving the link on a T15xWL at 192.168.1.101 against a CORE at 192.168.1.1
- When the count never moves
- Questions asked
A KeTop Windows handheld talks to a ctrlX CORE over OPC UA only when five things line up: a network path between the two devices, the prepared OpcuaItf.cfg client configuration on the panel, a self-signed client certificate for Basic256Sha256 with SignAndEncrypt whose application URI matches the client, a ctrlX user holding permissions for the OPC UA Server App and the PLC App, and a GVL named KeTop shared in the PLC's symbol configuration. The link is proven, not assumed: once the CORE trusts the certificate, the Alive variable under plc/app/Application/sym/KeTop/ increments every 1 second. Work the steps in that order — network, client, certificate, server, PLC — because every later step fails silently when an earlier one is wrong.
What the setup requires #
- On the CORE: OPC UA Server App version 1.12.5 with its license, PLC App version 1.12.5 with its license, and ctrlX WORKS PLC Engineering version 1.12.3 on the engineering PC. The how-to pins those app versions and leaves the CORE image version open, so run an image the apps support.
- Wired panel: KeTop T15x Win10 with image 2.7.4, or KeTop T70 Win10 with image 2.7.1, on a CB3xx base station or JB00x junction box cabled to the CORE.
- Wireless panel: KeTop T15x Win10 with image 2.7.4 with a CB4xx base station.
- Address plan: the documented setup runs the CORE at 192.168.1.1 and the panel at 192.168.1.101. Confirm both against the machine's network plan before applying them.
- Server install: Settings > Apps in the CORE's web engineering interface. The server answers on every TCP/IP-capable interface of the ctrlX OS device — XF10 and XF11 on a CORE.
The panel is always the client and the CORE always the server here. When a different job leaves the direction unclear, settle it with HMI OPC UA server vs client: which direction works before you touch certificates, because only the client holds the certificate the server must trust. This procedure is for an external Windows panel; when the client is the controller vendor's own web visualization, the job shrinks to showing PLC variables in WebIQ over OPC UA on a ctrlX CORE.
Give the panel a reachable address #
Wireless T15xWL on a CB4xx base station #
- Start the handheld and hold it within 2 cm of the base station. The device vibrates and a dialog shows the base station's serial number or name; confirm with Yes.
- Verify pairing visually: the base station's LED bar and the emergency-stop illumination on the handheld show the secure connection, and that check is part of the machine's operating concept — do not trust feedback from a handheld whose link you have not seen confirmed.
- Open DeviceConfig from the desktop, then Network > Base station connection > Connection. Set the network address to 192.168.1.101, or DHCP if the site plan says so, and confirm with OK. Write to base station transfers the setting; Cancel leaves without saving.
- Under Network > Base station connection > WLAN, select the channel and the wireless band for the link between base station and handheld; the base station defines the remaining WLAN parameters and shares them with the handheld, which is the recommended setting. Transfer with Write to base station.
- Unpair and pair again after any change, because wireless settings apply on the next pairing. Unpairing is also how the secure connection is released when work is finished.
Wired T15x, with the T70 configured the same way #
- Open DeviceConfig from the desktop, then Network > Ethernet 0.
- Set the address to 192.168.1.101, or DHCP per the plan, and confirm with OK. Configuration works the same way on every Ethernet interface of the device.
Install the OPC UA client on the panel #
- On the panel, open Programs and Features and run WindowsPlatformDriverSetup to install the OPC UA Platform Driver. Run only one interface at a time — a second interface is not a workaround for a failed connection.
- Take the prepared config example that matches your KeTop device and keyboard layout; if the layout is not listed, use the Full template.
- Copy it to
C:\ProgramData\KEBA Automation\keview\system, rename it toOpcuaItf.cfgand replace the existing file. - Where your installation differs from the standard, edit only the values that differ: file path, file name, the CORE's IP address, user and password.
- Restart the panel, or restart the OpcUaItf service in Task Manager, so the client reloads the file.
The client reads the file from that directory only. Credentials edited into any other copy of the file change nothing.
Create the client certificate #
- The CORE's PLC requires a secure session with Basic256Sha256 and SignAndEncrypt, so generate a self-signed certificate and its private key with an external tool such as OpenSSL; the vendor documentation ships a manual and a script for exactly this step.
- Build the application URI as
urn:plus the host name of the machine you generate the certificate on, plus:Keba:OpcuaItf. The documented worked instance isurn:KEBA-PC:Keba:OpcuaItfwith the certificate nameKEBA-Opc. Do not copy the example host when your machine is named differently. - Copy the certificate and the private key to the panel, into the folder and under the file names that
OpcuaItf.cfgreferences. - Expect rejection at first: the certificate sits in the server's store as rejected until you trust it in one of the last steps.
Prepare the CORE #
- Create a user in the CORE's user administration, with a managed password. The documented procedure builds on one example user; any dedicated account works.
- Install the OPC UA Server App through Settings > Apps in the web engineering interface and grant that user permission for the app.
- Install the PLC App and grant the same user permission for it.
- The endpoint the client dials is
opc.tcp://followed by the CORE's address and the port configured in the server app — which is the IP address the config file carries.
Share the panel variables in the PLC project #
- Open the template project, or your own project, in ctrlX WORKS PLC Engineering.
- Copy the declaration code for your keyboard layout into the GVL
KeTop. The GVL must keep exactly that name, because the client's variable mapping depends on it. If your layout is not among the templates, use the declaration from the Full template. - In the symbol configuration, share the variables by selecting the KeTop node; if no KeTop node is listed yet, press Build once and select it.
- Login, download the project to the CORE, and create the boot application so the sharing survives a restart.
Trust the client certificate on the CORE #
- In the CORE's web interface, open Settings > Certificates & Keys > OPC UA Server.
- The client certificate is listed as rejected. Open its "..." menu and choose Trust.
Proving the link on a T15xWL at 192.168.1.101 against a CORE at 192.168.1.1 #
Inputs, each with its source:
- Panel: KeTop T15xWL, Win10 image 2.7.4, paired to a CB4xx base station — the wireless case the documentation works through.
- Addresses: panel 192.168.1.101, CORE 192.168.1.1, both from the documented plan. The first three octets, 192.168.1, are common to both, so the devices share one address range with no router between them.
- Security: certificate
urn:KEBA-PC:Keba:OpcuaItfnamedKEBA-Opc, files placed whereOpcuaItf.cfgreferences them, now trusted under Settings > Certificates & Keys > OPC UA Server. - PLC: project downloaded with GVL
KeTopshared in the symbol configuration and the boot application created.
Rule in words: the shared project increments the variable Alive by 1 every 1 second, and the CORE shows it under Settings > Data Layer at plc/app/Application/sym/KeTop/.
Arithmetic: at 1 count per second, a 30-second watch must show a change of 1 count/s × 30 s = 30 counts. Note the value, wait 30 s, note it again, and subtract: second reading − first reading = 30.
Decision: a difference of 30 — give or take the second you spend reading — proves the session carries data. Press a mapped key and watch its variable change in the same folder; that proves writes as well. A difference of 0 means no session at all, and the four checks below, in that order, find it.
When the count never moves #
- Path: confirm the pairing or the cable link, and that both devices carry the planned addresses without a conflict.
- Config: confirm the edited file is the
OpcuaItf.cfgthe client actually reads, and that the OpcUaItf service restarted after the edit. - Certificate: confirm the application URI matches the client and the server lists the certificate as trusted, not rejected.
- Permissions: confirm the user in the config file holds permission for both the OPC UA Server App and the PLC App.
Questions asked
Can the panel take its address from DHCP instead of 192.168.1.101?
Yes. DeviceConfig offers DHCP or a manual address, and either works as long as the panel can still reach the CORE and the address matches the machine's plan. If you set a fixed address, check the plan for conflicts first. On a wireless panel, remember that network changes only apply on the next pairing, so unpair and pair again after changing them.
Does this work the same for a wired KeTop T70?
Yes. A T70 with Win10 image 2.7.1 on a CB3xx base station or JB00x junction box connects the same way. Set its address in DeviceConfig under Network > Ethernet 0, and in the PLC project paste the declaration code for the T70's keyboard layout into the GVL KeTop, or the Full template's code if that layout is not among the templates.
Why does the CORE list my client certificate as rejected right after setup?
That is the normal state, not a fault. A self-signed client certificate lands in the server's store as rejected and the session is refused until an administrator trusts it. Trust it under Settings > Certificates & Keys > OPC UA Server through the "..." menu, then restart the OpcUaItf service or the panel so the client opens a fresh session against the trusted certificate.
Is a correct password enough for the ctrlX user?
No. The user named in OpcuaItf.cfg also needs explicit permission for the OPC UA Server App and for the PLC App. A right password on a user without those permissions fails exactly like a wrong one, which is why changing credentials is the wrong first move when the panel cannot connect. Check the permission assignments first.