Home › Technical articles

Đọc bằng tiếng Việt

FactoryTalk Linx Gateway as OPC UA server: endpoints, security policies, certificates for third-party clients

TDL Industrial Automation · Last updated:

From FactoryTalk Linx Gateway Help 6.60 and Getting Results Guide FTLG-GR001I-EN-E: the Gateway as the OPC UA and OPC DA server for third-party software, the FactoryTalk application and standalone data sources, endpoint port 4990, security policies and modes, anonymous or FactoryTalk Security logon, certificates on both sides, three namespace modes, activation, and the messages when a client cannot connect.

FactoryTalk Linx is the Rockwell data server that FactoryTalk software uses to read Logix controllers. A third-party SCADA, historian or MES reaches the same data through FactoryTalk Linx Gateway, which adds an OPC UA server, an OPC DA server and a few other interfaces. Below is what Rockwell documents for that OPC UA server: data sources, endpoints, security, certificates, namespace, activation and connection faults.

From Logix controllers to OPC UA clients through Linx GatewayFrom top to bottom: Logix 5000 controllers on EtherNet/IP; the Gateway's two data sources, A the FactoryTalk Application (FactoryTalk Linx servers and shortcuts, three namespace modes, CIP Security and redundant sources) and B the Standalone Data Service (Logix version 18 and later, Processor shortcut, Custom namespace only, no CIP Security); FactoryTalk Linx Gateway with its OPC UA server: endpoint port 4990, the security policies not marked deprecated, the modes, Anonymous or FactoryTalk Security User logon, client certificates in Rejected until trusted, plus OPC DA, MQTT, DDE and Excel RTD; at the bottom three OPC UA clients: Ignition, AVEVA, a historian or MES. Based on FactoryTalk Linx Gateway Help 6.60 and FTLG-GR001I-EN-E.From Logix controllers to OPC UA clients through Linx GatewayLogix 5000 controllersEtherNet/IPA · FactoryTalk ApplicationFactoryTalk Linx servers and shortcutsFolders, Tag list or Custom namespaceCIP Security, redundant sourcesB · Standalone Data ServiceLogix version 18 and later, Processor shortcutCustom namespace only for OPC UANo CIP SecurityFactoryTalk Linx GatewayOPC UA ServerEndpoint: Address, Port 4990, plus one per further endpointSecurity Policy: Basic256Sha256, Aes128Sha256RsaOaep,Aes256Sha256RsaPssSecurity Mode: Sign or Sign & EncryptLogon: Anonymous (default) or FactoryTalk Security UserClient certificate stays in Rejected until trustedSame GatewayOPC DA over DCOM,MQTT, DDE, Excel RTDOPC UAOPC UAIgnitionOPC UA clientAVEVAOPC UA clientHistorian, MESother OPC UA clientsEach client: the endpoint URL, the same security policy and mode, trust in the Gateway certificate, aFactoryTalk Security user when the endpoint asks for one.Based on Rockwell Automation, FactoryTalk Linx Gateway Help 6.60 and FTLG-GR001I-EN-E (read15 November 2026). Figure: drawn by TDL.
Figure 1: From Logix controllers to OPC UA clients through Linx Gateway. On a phone, swipe sideways to see the whole figure.

1. What was read

FactoryTalk Linx Gateway Help 6.60 and Getting Results Guide FTLG-GR001I-EN-E (version 6.60.00); the FactoryTalk Linx Getting Results Guide 6.50.00 (LNXENT-GR001Z-EN-E, new number FTLINX-GR001); one page each from the FactoryTalk Services Platform 6.60 and Logix Designer 37.00 help. When FactoryTalk Linx itself cannot see a controller, see RSLinx Classic or FactoryTalk Linx cannot see the controller.

2. FactoryTalk Linx and FactoryTalk Linx Gateway

FactoryTalk Linx delivers data from Allen-Bradley controllers to FactoryTalk software and Studio 5000, optimised for Logix 5000 over EtherNet/IP. Standard OPC connectivity for third-party products comes with FactoryTalk Linx Gateway. The Gateway includes an OPC UA service for up to 100 clients, an OPC DA service for up to 20 clients, and MQTT, DDE and Excel RTD interfaces; real OPC UA capacity depends on the computer and the data requested.

OPC UA arrived in version 6.00.00 with a non-secured endpoint, and secured endpoints with signing and encryption in 6.10.00. Version 6.60.00 added certificate management through FactoryTalk Policy Manager and opened the standalone data service to OPC UA clients.

3. Two data sources: FactoryTalk application or standalone

The Data Source setting under Global Settings chooses where the Gateway takes its tags from.

Point FactoryTalk Application Standalone Data Service
Where tags come from FactoryTalk Linx servers in a FactoryTalk application, with shortcuts made in FactoryTalk View Studio or FactoryTalk Administration Console Logix 5000 controllers read directly, no FactoryTalk application, on the same computer
Controllers and shortcuts All FactoryTalk Linx shortcut types Logix controllers version 18 and later, Processor shortcut only
OPC UA namespace Folders with scalar data, Tag list, or Custom namespace Custom namespace only
CIP Security Yes No
Server high availability Redundant FactoryTalk Linx servers, OPC UA Connectors and OPC UA servers No
Controller connection Shared with other FactoryTalk software Its own connection
Scale in the Help One to ten servers, dozens to hundreds of controllers One computer, a few dozen controllers

The standalone service uses the RSLinx Classic tag reference format, with the shortcut name as the topic.

4. Endpoints, security policies and logon

Endpoints are set under OPC UA Server > EndPoints in FactoryTalk Linx Gateway Configuration:

  • Name: unique; it appears in the OPC UA namespace and in the full path of every node.
  • Address and Port: host name or IP address; the port defaults to 4990 and goes up by one for each further endpoint. It must be unique, and the firewall must allow incoming connections on it.
  • URL: the network path the client needs, with a Copy button.
  • Security Policy: None, Basic128Rsa15, Basic256, Basic256Sha256, Aes128Sha256RsaOaep or Aes256Sha256RsaPss. Basic128Rsa15 and Basic256 are marked deprecated by the OPC UA specification and not recommended.
  • Security Mode: Sign, Sign & Encrypt, or Sign + Sign & Encrypt (either).
  • Reverse connect: the server opens the connection to the client, up to 20 client URLs per endpoint.

Anonymous logon is the default and gives full browse, read and write access; it can be limited to read-only. FactoryTalk Security User makes the client log on with a FactoryTalk user, whose permissions are set under Product Policies > FactoryTalk Linx Gateway > Feature Security; it cannot be used with the policy None. Maximum anonymous connections (Advanced Settings) defaults to 50, which keeps connections free for secured clients out of the 100. Each endpoint can also log every client write to the FactoryTalk Audit or Diagnostics log; this is off by default.

5. Certificates, on both sides

At installation the Gateway creates a self-signed certificate under C:\ProgramData\Rockwell\FactoryTalk Linx Gateway\PKI\own. To replace it, create a certificate signing request (CSR) in the Gateway, have an external authority sign it and import it; Regenerate renews the validity period.

A new client's certificate is validated and put in the rejected list, and the Diagnostics log says it is not trusted. An administrator selects it under Certificate Management > Incoming Certificate and clicks Trust. The client must also trust the Gateway's certificate, which each client does in its own way. Since 6.30.00 only administrators, or users they approve, manage certificates.

With "Enable certificate management by FactoryTalk Policy Manager", Policy Manager 6.60.00 or later deploys the certificates. This needs an endpoint with Basic256Sha256 and Sign & Encrypt and FactoryTalk Security User logon; anonymous connections are then not allowed, and the OPC UA Server must be restarted after a deployment. CIP Security between FactoryTalk Linx and the controllers is a separate subject: CIP Security.

6. What the client sees

The Namespace setting has three modes:

  • Folders with scalar data: every tag from the FactoryTalk application's sources, as single values in folders.
  • Tag list and structures/array access: only tags in tag groups of the UA Tag List are visible, granted per FactoryTalk Security user. Needed when a client must see Logix UDTs as structures.
  • Custom namespace: user-defined structures and tags mapped to controller data, for naming rules such as OPC UA companion models.

From 6.20.00 the namespace index defaults to 2; 6.21.00 added a choice of 2 or 3. The OPC UA Access property of a tag in Logix Designer (None, Read Only, Read/Write) applies only to a controller's embedded OPC UA server, not to tags served by the Gateway, where the UA Tag List limits access.

7. Activation, as a mechanism

The activation type sets how many tags each interface may serve, counted separately for OPC UA, MQTT, OPC DA, RTD and DDE, and summed over clients: five clients subscribing to 1,000 tags use 5,000. "Automatic Selection" picks the available activation with the most capacity. Without a valid activation the Gateway runs a seven-day grace period at Professional level; after it, no client of any interface can connect.

8. OPC DA on the same Gateway

The OPC DA server uses DCOM. Its Access setting is "Only local DA clients" or "Local or remote DA clients"; the Help warns that the service runs as Local System and that remote DA access carries a security risk. Version 6.30.00 raised the default DCOM authentication level to Packet Integrity. Existing DA links: OPC DA and DCOM errors.

9. High availability

The Help describes two Gateway services with the same configuration on two computers, with the client managing the switch: use one and move to the other when it drops (slow recovery), connect to both with one active, or take data from both. Behind the Gateway, FactoryTalk Linx servers, OPC UA Connectors and UA servers, and Logix controllers can be redundant.

10. Connecting Ignition, AVEVA and other clients

The Gateway Help asks the client to use the endpoint's security policy, trust the Gateway certificate and, when that logon is set, enter the FactoryTalk Security user name and password. Where each platform sets up its OPC UA client: our driver comparison. Ignition and AVEVA can also read ControlLogix with their own drivers: Ignition Logix driver, AVEVA ABCIP.

The opposite direction, OPC UA servers into a FactoryTalk application, is the FactoryTalk Linx OPC UA Connector. It presents their data as tags, takes endpoints in the form opc.tcp://hostname:port/Endpoint/Name, and runs once per computer.

11. When a client cannot connect

What the Gateway reports What the Help points to
Failed to enable endpoint Port used by another endpoint or blocked by the firewall
Client failed to connect from an endpoint The message names the security mode, policy and reason
Client certificate is not trusted Trust it under Incoming Certificate
Server has reached its limit of connections Connection limit of the OPC UA server
Not in the Local Discovery Service Endpoint or service off, activation expired, registration off, LDS certificate not trusted

What we check first

This is TDL's practice, not a Rockwell Automation requirement.

  • We note the Gateway version, activation and data source in Global Settings.
  • We list each client with its endpoint, policy and mode, avoid None and the two deprecated policies, and agree with the plant whether anonymous logon stays on.
  • We trust certificates on both sides and note who manages them and when the Gateway certificate expires.
  • We agree the namespace mode with the client team: a Tag list for UDTs or read-only groups, and the namespace index their node IDs expect.
  • We open only the endpoint port between client and Gateway, as in our firewall article, with zones as in IEC 62443.
  • We count tags per client against the activation and test a reconnect after a Gateway restart.

How TDL approaches it

TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. Our pages cover connecting existing equipment to SCADA, with interfaces to third-party systems over Modbus and OPC UA, and a package to connect one machine or line to a historian or OPC UA, where the data path (Rockwell driver, OPC UA or gateway) is chosen after a survey.

Frequently asked questions

Does FactoryTalk Linx on its own serve OPC UA to third-party clients?

The FactoryTalk Linx guide says standard OPC connectivity for third-party products comes together with FactoryTalk Linx Gateway. The OPC UA and OPC DA servers are part of the Gateway.

What port does the Linx Gateway OPC UA endpoint use?

The first endpoint defaults to port 4990, and each further endpoint takes the next number. Each port must be unique and open for incoming connections in the firewall.

Why can the client not connect after the endpoint was set up?

One documented cause is the certificate: a new client certificate goes to the rejected list until an administrator trusts it, and the client must trust the Gateway certificate too. The OPC UA diagnostics message for a failed connection names the security mode, policy and reason.

Can a client see Logix UDTs as structures?

Yes, with the namespace mode "Tag list and structures/array access". Only tags in UA Tag List groups are then visible, by FactoryTalk Security user. With the standalone data service the OPC UA server offers only the custom namespace.

Does the Gateway need a FactoryTalk application?

No. The standalone data service reads Logix controllers from version 18 directly, with Processor shortcuts. It has no CIP Security and no server high availability.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Rockwell Automation (Allen-Bradley) Connecting existing equipment to SCADA