|Name||A name used to identify this connection.|
|Description||Short description of this connection.|
|Read-only||Puts the connection into read-only mode. All writes sent to this server will fail.|
|Enabled||Disable the connection to the OPC server.|
|Username and Password||If a username and password are specified, they are used as a user identity token when connecting to the specified OPC-UA server.|
The internal OPC-UA server provided by the OPC-UA module uses an Ignition security profile to govern who can connect to it. This can be configured in the OPC-UA Server > Settings section.
|Change Password?||Enable this property to change the configured password.|
|Password||Re-type password for verification.|
|Host Override||When specified, if the endpoint address returned by the OPC server has a different IP address or hostname than the discovered endpoint, the overridden value will be used. Expects just an IP address or hostname. Example: 192.168.1.10|
|Max Per Operation||Specify the maximum number of nodes to read, write, subscribe, or unsubscribe to in any given UA server request.|
|Request Timeout||Maximum amount of time, in milliseconds, to wait for the response to a request. (default: 120,000)|
|Secure Channel Re-authentication Enabled||(default: true)|
|Backup Discovery URL||The discovery URL for the backup server's OPC-UA server. Expects the following format: opc.tcp://hostname:port|
|Backup Endpoint URL||The full endpoint URL for the backup Gateway, e.g. opc.tcp://10.20.1.100:4096/ia/opcua or opc.tcp://192.168.1.10:49320|
|Failover Enabled||When enabled, if this OPC-UA server connection is faulted, requests will be sent to a failover OPC-UA server.|
|Failover Endpoint||The endpoint of the failover server. |
|Failover Host Override||When specified, if the endpoint address returned by the failover OPC server has a different IP address or hostname than the discovered endpoint, the overridden value will be used. Expects just an IP address or hostname. Example: 192.168.1.10|
|Failover Threshold||The number of retry attempts before the failover connection is used. The default is 5.|
How do I determine the Endpoint for my backup?
See step 5 in the Connecting to a OPC-UA Server guide above. Clicking the Discover button will show a list of available endpoints to connect to.
The Failover properties should be used when a single Ignition Gateway needs to connect to a pair of redundant OPC-UA servers. The failover OPC-UA server will be used in the event the primary OPC server goes down. To enable failover, set the Failover Enabled property to true, and specify the Failover Endpoint. The Failover Threshold can be adjusted if desired. Note: Failover events are "sticky." That means once control has moved to a backup OPC-UA server, it stays there until that server fails.
The Backup properties should be used when a pair of redundant Ignition Gateways are trying to look at the same OPC-server. Both the Backup Discovery URL and Backup Endpoint URL properties need to be configured.
You can access the OPC Quick Client from under the OPC Connections section of the Ignition Gateway Configure section. It allows for quick, simple testing of any devices connected to the server.
You can browse by expanding tree nodes and read/write to Tags by clicking on the [r] and [w] buttons next to those Tags.
Subscriptions can be made by clicking on the [s] button. For each individual subscription, you can click on the SET button and it will automatically refresh subscriptions and show live value changes (if there are any).
You can see the following OPC-UA Server Settings by going to the Configure section of the Gateway, and then choosing OPC-UA Server > Settings.
|Authentication Profile||The User Source that the OPC-UA module will use to authenticate incoming connections against. By default, this is set to the opcua-module User Source. This profile is included in the default installation and has the following as its default settings:|
|Allowed Roles||Roles within the given User Source that are allowed to connect to the server. Multiple roles should be separated by a comma, for example, |
|Allow Anonymous Access||Allows users to connect whether or not they possess authentication credentials. Not checked by default.|
|Server Port||The port on the local machine of the OPC-UA server runs on. Requires a module restart to take effect.|
This is the local address that the Ignition UA server will bind to. It is also the address that will be used in a GetEndpointResponse, so it is important that this be an address reachable by any clients that wish to connect. Requires a module restart to take effect. This is useful if the server machine has a VPN connection or multiple adapters and is returning the wrong address.
|Backup Endpoint Address||This is the local address that the Ignition UA server will bind to *on the redundancy backup*. Leave blank if not using redundancy.|
|Minimum Sampling Interval||The fastest rate (in milliseconds) that the server will use to sample its underlying data sources. Requires a module restart to take effect. The default is 100.|
Expose Configured Tags
|Expose Tag Providers||If enabled, Ignition Tag providers will be exposed through the OPC-UA server, allowing third party clients to access the Tags configured in the system. By default, the check box is not selected or False.|
|Auditing Enabled||Enables an Audit profile for OPC-UA server. (default: false)|
|Audit Profile||If enabled, writes to exposed Tags will be audited to the selected profile.|
|Stale Threshold||The multiplier by which the server determines that updates from a driver have become stale. This period will be calculated as the fastest sampling rate for that node multiplied by this settings value. Default is |
|Auto-cast Writes|| Attempt to auto-cast incoming writes to the correct DataType before rejecting them with a |
|Read Only When Inactive||Operate in read-only mode when this node is the inactive node of a redundant pair.|
Getting data from your PLC into Ignition is a two step process:
It requires you to touch both the Ignition Gateway and the Ignition Designer. There are also some limitations as to what kind of devices you can connect to Ignition and these are explained throughout the user manual, however, included below is an overview of what you can expect when it comes to compatibility.
Most commonly you will be adding a device that is supported by one of the built-in device drivers. The first step is connecting your device to Ignition. This is done through the Ignition Gateway Configuration section under the OPC-UA -> Devices page.
As long as all the device information you entered was correct you should see your device in a "Connected" state. The only exception to this is if you chose to add a Siemens or Modbus device. Since these devices don't support the browsing of Tags, you will have to create and address some Tags in the Ignition Designer before the device will stop cycling from a connected to disconnected state.
If you need to address your Tags for your Siemens or Modbus device, you'll want to read about adding Tags in the Ignition Designer as well as how addressing works for the different protocols. You will have to first add a Tag in the Ignition Designer and then edit the OPC Item Path of the Tag using the appropriate addressing scheme.
If your device does not have an Ignition driver, you can use a 3rd party OPC server to connect to your device and then have Ignition connect to the server as a client. If the OPC server talks OPC-UA, you can add a new OPC-UA server connection in the Ignition Gateway. Configuration will be different depending on what OPC server you are using, but the following is an example of a popular solution, connecting to KEPServer via OPC-UA, see Connecting to Kepware OPC-UA.
The following section provides a detailed walk-through on how to connect to an OPC server using the OPC-COM module. If Ignition doesn't have a driver for your device and you don't have an OPC server that talks OPC-UA, you have to connect using the OPC-COM module, see Connecting to OPC Classic (COM).
Tags are how Ignition represents your PLC Tags. You create Tags in the Ignition Designer and then you can use these Tags to store history or display PLC data in your projects.
For the most part, Allen Bradley devices support browsing of Tags in the PLC. There are a few exceptions, like the MicroLogix 1200/1500 for which you have to manually address your Tags. For now, we will focus on creating Tags from devices that support browsing.