WebIQ OPC client not able to read OPC Server

[Open0]

Hi Community,

My WebIQ is connected to ctrlX OPC Server successfully, but is not able to read data.

My ctrlX apps version:

WebIQ connect to ctrlX OPC Server app successfully:

Widget Gauge map to OPC Server PLC datalayer node

Mapping variable into Gauge

Value in Datalayer

Value in OPC Client

Please help.

Warmest regards,

[webiq-sk]

To diagnose server issues the connect.log is required which you can download from the Runtime Manager.

Can you please show a screenshot of the "Items" tab showing all fields of the corresponding item?

[HmiGuide · Accepted solution]

Two common hints from my side:

• Even it is possible to use blanks in an item name in WebIQ, you should not do that. Best solution is to keep the original PLC variable name. My experiance is: blanks in variable name creates unexpected problems.
• When your WebIQ server is running on a ctrlX you should always use 127.0.0.1 (=localhost) as IP address instead of 192.168.2.212, because 192.168.2.212 is not available when no network cable is plugged in. This means when you want to do e.g. a trend recording while the HMI is switched off, no data is recorded. 

[webiq-sk]

@HmiGuide If you experience any issues with spaces inside item names can you please forward a demo HMI to us so we can look into this? There shouldn't be an issue - you can even use emojis like 🤷‍ as an item name if you like, actually.

[HmiGuide]

Like I said, it is a common experiance - nothing special for WebIQ. An because of the fact that it is not allowed in most programming languages, it is confusing that it is possible in WebIQ.

[webiq-sk]

What I actually find more weird is things like this with some PLCs: "Extruder"."Heatzone"."7".... 😉 All those quotation marks....

[Open0]

Thank you everyone for your reply, I solved it by not changing the item name in WebIQ keeping the original PLC variable name. 

[webiq-sk]

Thanks for the info. WebIQ only uses the PLC item name internally and never in the HMI and the alias only in the HMI and never with the server. As you unfortunately did not provide connect.log as request we cannot analyze this issue any further to fix a possible bug.