OPC Server Connected, OPC Client Bad Quality

Ignition
,
1

I have my Ignition OPC UA server connected via the loopback 127.0.0.1 and it shows “Connected”

I am connected to a Device (PLC) at address 192.168.100.101 (this is NAT’d from 192.168.1.101 if that matters).

My tags are good quality in the kepware OPC client as connected through Kepserver (as a test) but through the OPC UA Sever, the quality is bad on its OPC client.

Question

Are there any advanced settings I can tweak to get the OPC Client to read Good Quality tags?

2

If you are using Ignition's loopback connection, then you are using Ignition's native drivers. Each driver has its own quirks and requirements as to how the PLC connection needs to work. Especially if there might be local firewalls involved.

Share more details.

3

Under OPC-UA Server > Devices > I am using the native driver for Allen-Bradley Logix Driver v21+ and my PLC is a CompactLogix 5370 (1769-L24ER-QB1B) running v30.011. This seemed to work fine and the device says “Connected”…

As for the OPC UA Client that had bad quality tags (Even though all the tags populated properly in the OPC UA client from the PLC connection) I have tried the following:

  • I disabled the firewall to troubleshoot and still had the same issue.
  • I also removed the NAT and changed the PLC IP temorarily to be on the same subnet as the Ignition server NIC so I could rule out the NAT being an issue.
  • I also temporarily removed certs and encryption/security under OPC Connections > Servers > Ignition OPC-UA Server to rule out that (Endpoint: opc.tcp://127.0.0.1:4096/iaopcua/None)

Follow-up Questions

This Ignition Server PC has multiple NICs for multiple networks, the PLC connection is just one of three. I see in newer versions of ignition you have more settings (bind address, etc.) and have multiple inputs allowed seperated by commas - I guess Im confused about the differences between address settings even after reading help docs (endpoint, etc). I also saw some forum setting the endpoint to 0.0.0.0?

In this case (7.9) the advanced settings available are “Endpoint Host Override” and then some failover and redundancy stuff that Im not sure applies to this?

The last thing Im confused about and migh play in is the OPC-UA Server > Certificates. I can regenerate these but not sure if they are of significance in this instance?

4

When using Ignition's internal drivers, you should never have to manipulate the loopback OPC connection. That part just works, out of the box, for internal drivers. You've probable broken this loopback connection.

You should probably call support for help to unbreak it.