User Manual

GETTING STARTED


MODULES AND PLATFORM


APPENDIX


TUTORIALS & HELPFUL TRICKS


STRATEGIC PARTNER LINKS

Sepasoft - MES Modules
Cirrus Link - MQTT Modules

RESOURCES

Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples

ALL USER MANUAL VERSIONS

Ignition 8.1
Ignition 7.9
Ignition 7.8

Deprecated Pages

Employees

Sign In

Skip to end of metadata
Go to start of metadata


OPC UA makes connecting to third party OPC servers quick and easy without all the headaches associated with COM. This is a detailed step-by-step guide to connecting to KEPServerEX from Ignition using OPC UA.

Connect to KEPServerEX from Ignition using OPC UA

  1. In the Config section of the Gateway, go to OPC Client > OPC Connections. The OPC Connections page is displayed showing the OPC UA servers your Ignition is connected to.
  2. Click on Create new OPC Connection…
  3. Choose OPC UA as the connection type, and click Next.

  4. On the Server Discovery page,enter the endpoint of the OPC UA server Ignition should connect to. For example:

    Sample FormatLocalhost Example, Default PortRemote Example, Custom Port
    opc.tcp://IpAddress:Portopc.tcp://localhost:49320opc.tcp://10.1.1.10:4444


    Click the Next button to continue.



  5. Select the Server you want and click Next.



  6. A list of available Endpoints with Security Policies and Security Modes options appears.



    Once an endpoint configuration has been selected, click the Next button.

  7. On the Manage Certificate page select Yes for Trust Certificate? and click Next.



  8. Confirm your settings and click Finish




  9. This takes you to the new OPC Connection screen. Fill in the Username and Password if your KEPServer connection requires it.

    Most current installations of KEPServer require a login and will not connect without one. See the No Anonymous Token Policy Found section below.




  10. Click Create New OPC Connection

  11. The connection will appear as Faulted. This is expected because KEPServerEX is denying access to the Ignition OPC UA Client. The next step is to have KEPServerEX trust the Ignition OPC UA Client.

  12. On the computer that KEPServer is installed on, right-click on the KEPServerEX icon on the desktop KEPServerEx is installed on, and from the menu select OPC UA Configuration. The OPC UA Configuration Manager will appear. 



  13. On the OPC UA Configuration Manager window, go to the Trusted Clients tab.

  14. Click on Ignition OPC UA Client, click the Trust button, and click Close. Now the OPC Server Connections page shows the Status of Kepware to be Connected.


  15. Again, right-click on the KEPServerEX icon on the desktop KEPServerEx is installed on, and from the menu select Reinitialize.
     
  16. Go back to the Ignition Gateway Webpage. In the Config section, go to the OPC UA > Security page.

  17. Under the Client Security tab, you will find your new connection listed as Quarantined. Click on the Trust button on the far right.


  18. Go back to the Config section of the Gateway, to OPC Connections > Servers. The Status of your KEPServer connection should be Connected.
  19. To test your tag connections, go to the OPC Connections > Quick Client in the Configure section of the Gateway. Expand the KEPServer object until you find tags.



On this page ...


IULocgo


Connecting to Kepware OPC-UA

Troubleshooting

If Status does not read Connected, click the edit link next to the server connection, scroll down to the bottom of the connection configuration page, and click Save. If Status is still reading something other than Connected, click the OPC Connection Status link at the bottom of the OPC Server Connections page and see if there are any useful messages to help troubleshoot the issue. Also, ensure your firewall is not blocking traffic on the port that KEPServerEX is using to communicate.

Failover

The failover Kepware OPC UA server works the same as the OPC UA server with the exception that you need to have two copies of Kepware setup, preferably on different servers. The failover Kepware OPC UA server will be used in the event the primary Kepware server goes down. To enable failover, check the box to Show advanced properties in the New OPC UA Connection Settings, set the Failover Enabled property to 'true,' and specify the Failover Endpoint.   

The Backup properties should be used when a pair of redundant Ignition Gateways are trying to look at the same Kepware OPC UA server. Both the Backup Discovery URL and Backup Endpoint URL properties need to be configured. 

For additional information on Failover, refer to OPC UA Client Connection Settings.

No Anonymous Token Policy Found

When connecting to KepServer, some versions may not allow anonymous connections by default. This typically means you need to specify user credentials for Ignition to use in the OPC UA server connection. Alternatively, individual Kepware Projects can allow anonymous login. For more information, look into allowing "anonymous login" in KepServer's OPC UA Configuration Manager documentation.

Other UA Servers

While the above example is specific to KEPServerEX, the same concepts apply to connecting to any other third party OPC server that accepts OPC UA client connections. The only difference may be in the way that the certificates are accepted on the server.

The Ignition OPC UA server sends the client certificate to the third party OPC server when it tries to make the connection, however if the OPC server is not designed to expect these certificates then there may not be a straight forward way to accept them. In these cases, you can manually download a client ticket from Ignition and supply it to the OPC server in the appropriate manner.

Download a Client Certificate Manually

  1. Go to Config section in the Gateway Webpage.
     
  2. Select OPC UA > Certificate from the left side of the page. The Manage Certificates page is displayed.
     
  3. In the This Gateway tab, click the download link under Ignition OPC UA Client, and save the certificate somewhere to disk. This certificate is then supplied to your third-party OPC server in a way specific to that server. For more information, check the respective server's documentation.



Related Topics ...


  • No labels