FactoryTalk Linx Gateway gives external applications access to control data collected by FactoryTalk Linx. Third-party software can use data from Logix5000 and other supported Allen-Bradley controllers alongside existing FactoryTalk applications.
For a plant upgrade in India, this allows a new monitoring, MES or reporting application to use data from the existing Rockwell control system.
FactoryTalk Linx Gateway adds OPC DA and OPC UA interfaces for external clients. A third-party HMI or data collection application with a compatible client interface can access the information collected by FactoryTalk Linx while the plant continues to use its FactoryTalk software.
OPC UA connects upper-level applications through a client/server interface. MQTT exchanges data through a broker. The destination application's interface and required transfer direction determine which connection to use.
MQTT capabilities vary by Gateway version. Publishing, receiving data and buffering outgoing messages were introduced in different releases, as outlined below.
Excel RTD and DDE interfaces let engineers inspect control values in workbooks during startup or troubleshooting. This provides a way to check data before connecting the final application.
The Ordering Guide limits DDE and Excel RTD to software running on the same computer.
FactoryTalk Linx Gateway addresses projects where Rockwell control data is already available through FactoryTalk Linx and another application needs access. An Indian plant could retain its existing HMI while adding a separate reporting or monitoring system.
In a mixed-vendor plant, each controller still needs a supported communication path into the system. Equipment outside the existing connection scope may require additional communication software.
The OPC NEXUS directory lists OPC server vendors and their connection capabilities.
| Supported Interfaces: | OPC DA / OPC UA / MQTT / DDE / Excel RTD. Functions and capacities depend on the software version, activation and deployment configuration. |
|---|---|
| Pricing Guide and Fee Structure: | Edition-based licensing with subscription and perpetual options described in the Ordering Guide. Contact Rockwell Automation or its distributor for current pricing and support terms in India. |
FactoryTalk Linx communicates with supported Rockwell Automation control equipment. Gateway publishes that data to external clients.
FactoryTalk Linx OPC UA Connector handles the opposite direction: it brings information from third-party OPC UA servers into FactoryTalk applications. FactoryTalk Linx Data Bridge transfers data between FactoryTalk data sources. The source and destination determine whether a project needs these components alongside Gateway.
Gateway can organise published data into custom OPC UA namespace folders. Other functions depend on the release:
The MQTT publisher cache buffers outgoing data during temporary disconnections. Its capacity and overflow policy need to account for the expected interruption and data rate.
The Ordering Guide lists Basic, Standard, Extended, Distributed and Professional editions. Basic through Extended cover local or station configurations; Distributed and Professional support broader distributed configurations.
Tag limits differ by interface. An OPC UA capacity does not automatically apply to MQTT, OPC DA or Excel RTD, so the selected edition must cover the required interface as well as the tag count.
Before installation, check Windows and FactoryTalk component compatibility through Rockwell Automation's Product Compatibility and Download Center. Gateway also requires configured data-source shortcuts and appropriate FactoryTalk Security permissions.
The documented architecture connects existing control data to an external OPC UA client through FactoryTalk Linx and Gateway. This is a configuration example, rather than a reported customer deployment.
Data passes from the controller through FactoryTalk Linx to Gateway's OPC UA service, then to the external client. The application scope and data-source shortcuts identify the tags to expose.
During commissioning, establish the UA connection and verify values in the receiving application. Before enabling writes in production, test both the permissions and the resulting equipment behaviour.
A tag list defines the first test: which application needs each value, how often it must update, and whether it needs write access. Add the expected behaviour when a controller or network connection fails. The integrator can then verify one connection before extending it to other production areas.
The version 6.60 guide describes a seven-day grace period at the Professional activation level when no valid activation is found. Clients cannot connect to Gateway after that period expires.
Confirm installer access and the activation procedure with Rockwell Automation or its distributor before scheduling the evaluation. Allow enough time to test the connection and its recovery behaviour within the grace period.
Rockwell Automation supplies industrial automation and information products, including the Allen-Bradley and FactoryTalk portfolios. Its India website provides sales enquiries, distributor search and technical support contacts. The page identifies which technical support services require TechConnect access.
| Company Name | Rockwell Automation, Inc. |
|---|---|
| Product | FactoryTalk Linx Gateway |
| Sales and Support in India | Use Rockwell Automation's India contact page for sales assistance or distributor search. Product support depends on the purchased entitlement. |
| Official Website | https://www.rockwellautomation.com/en-in.html |
| India Contact | https://www.rockwellautomation.com/en-in/company/about-us/contact-us.html |
Advertiser Disclosure:
We receive compensation from some of the companies listed below.This compensation may affect which companies are included and the order in which they appear.
Communication parameters can be changed dynamically while the server keeps running, so adding a device or revising a setting does not interrupt data collection. Drivers cover 400+ device series from 100+ manufacturers, including Siemens, Rockwell Automation, Mitsubishi Electric and Omron, so most equipment changes are handled as a setting change rather than a rebuild.
Every site publishes data through OPC UA, or sends it to AWS, Azure and other cloud services over MQTT or HTTP*, so upper systems see the same interface wherever the data originates. A cloud-side OPC UA client can initiate the connection, so no inbound ports need to be opened at the site. Calculation, conditional branching and recipe handling are configured on the server itself at no additional cost, keeping that work off the SCADA or MES side.
Packaged licensing* for large-scale standardization reduces the need to procure licenses when adding new sites or manage updates site by site. This supports scaling while maintaining the management framework.
With add-on options, OPC servers running at different sites can be centrally managed from the main site.
Collects oil and gas drilling data via OPC. Secure transmission across firewalls and redundancy help maintain an audit-ready data foundation over time.
All servers include diagnostic logging with log-level settings and filtering. The logs can also serve as a foundation for audit trails.