For the latest compatibility and driver support information, refer to the Product Compatibility and Download Center.

FactoryTalk Linx recommends the following hardware for applications with typical data acquisition needs:

• Intel® Core™ i5 Standard Power processor
• Total processor cores is recommended to be no less than 4 for virtual machines
• 4 GB of memory

Lower level x86 based CPUs will also work in standalone configurations with reduced data acquisition needs.

For small applications, the following configuration was also evaluated:

• Intel® Atom™ CPU E3845 @ 1.91GHz (4 CPUs)
• 4 GB of memory
• 1500 data points

It is recommended to run performance validation test on the planned computer hardware to ensure the desired capacity and performance can be achieved.

Operating systems

FactoryTalk Linx is tested on operating systems installed from original Microsoft® media only. FactoryTalk Linx runs on the 64-bit versions of the following Windows® operating systems:

• Windows 10 (v2004, v20H2, v21H1, and v21H2)
  FactoryTalk Linx adopts .NET 4.8 which is only supported in Windows 10 v1803 and later.

• Windows 10 IoT Enterprise 2019 Long-Term Servicing Channel (LTSC)
• Windows 10 IoT Enterprise 2021 Long-Term Servicing Channel (LTSC)
• Windows 11
• Windows Server® 2012
• Windows Server 2012 R2
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022

For requirements specific to running FactoryTalk Linx within FactoryTalk View Studio, refer to the System requirements topic in the FactoryTalk View SE and FactoryTalk View ME Release Notes.

FactoryTalk Linx version 6.31.00 has been tested with, and is compatible with, the following Rockwell Automation products:

• Studio 5000 Logix Designer version 35.00.00
• Studio 5000 View Designer version 8.02
• ControlFLASH version 15.07
• ControlFLASH Plus version 5.00
• FactoryTalk Services Platform version 6.31.00
• FactoryTalk Alarms and Events version 6.31.00
• FactoryTalk View version 13.00.00
• FactoryTalk Linx Gateway version 6.31.00
• FactoryTalk Linx OPC UA Connector version 6.31.00
• FactoryTalk Batch version 16.00
• Connected Components Workbench version 21.00.00
• FactoryTalk AssetCentre version 12.00.00
• FactoryTalk Policy Manager version 6.30.00
• FactoryTalk Logix Echo version 2.00.00
• FactoryTalk Updater version 4.00.00
• EDS subsystem version 35.0

To use the ControlNet communication feature with FactoryTalk Linx, the minimum requirements are:

• 1784-PKTCS/B firmware version 4.10.
  The PKTCS cards support I/O and messaging.

• 1784-PCICS/B and 1784-PCIC/B firmware version 4.10.
• 1784-PCICS/A and 1784-PCIC/A firmware version 3.10.

To use the DeviceNet communication feature with FactoryTalk Linx, the minimum requirements are:

• PCID(S) firmware version 3.016. The PCIDS cards support I/O only.

Note: FactoryTalk Linx also supports bridging from Ethernet (1756-ENxxx) to DeviceNet (1756-DNB) across a ControlLogix Chassis.

Windows 10 v1803 or later is the recommended operating system if running this software with a 2K or 4K High Resolution Display with scaling up to 125%.

Rockwell Automation tests software products under a standard configuration of operating systems and antivirus software. For additional information, see the Knowledgebase Document ID: PN24 - Rockwell Software Products and Antivirus Software.

The following web browsers have been tested and are supported for use with this release:

• Google® Chrome™ browser
• Microsoft® Edge™
• Mozilla® Firefox®

To help meet secure system design requirements, review these publications:

• Configure System Security Features User Manual (publication SECURE-UM001)
• System Security Design Guidelines Reference Manual (publication SECURE-RM001)
• Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001)

To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products Application Technique (publication SECURE-AT001).

FactoryTalk Linx version 6.31.00 has the following new features:

• FactoryTalk Linx version 6.31.00 supports adding and configuring unsolicited message shortcuts for PLC-5 and SLC 500 controllers.
• FactoryTalk Linx Network Browser version 6.31.00 supports adding and configuring remote proxy drivers.

Tip: The remote server's IP address, remote server's display name, and driver name are not shown in FactoryTalk Administration Console.

• FactoryTalk Linx Network Browser version 6.31.00 enhances the configurations on the LLDP tab. The neighbor information also shows on the Port Configuration tab.
• FactoryTalk Linx Network Browser version 6.31.00 adds audit messages for device configuration. When configuring controllers, audit messages are logged in FactoryTalk Diagnostics Viewer.

Support for Concurrent Communication Protocol Enhancements

Feature

IMPORTANT:

• If you are using FLEXHA 5000™ I/O modules with ControlLogix® 5580 controllers, do not upgrade any part of your system until all required software versions and component firmware revisions listed below are available.

If you update any part of the system before all versions and revisions are available to be upgraded at the same time, you will get error code 16#0008 Service Request Error: Unsupported service.

For more information, see section Error Codes below.

• Do not attempt to install a Logix SIS Redundancy or GuardLogix 5580 controller application that includes a FLEXHA 5000 I/O system until the FLEXHA 5000 EtherNet/IP adapter and FLEXHA 5000 I/O modules compatible firmware is available. The release of the required compatible firmware revisions is pending.

An attempt to install a Logix SIS Redundancy or GuardLogix 5580 controller application will result in error code 16#008 Service Request Error: Unsupported service. If you see this error with either of these applications, you cannot clear it until the required FLEXHA 5000 EtherNet/IP adapter and FLEXHA 5000 I/O module firmware revisions are available.

• The requirement that all software versions and firmware revisions must be available before starting the system upgrade applies regardless of whether the FLEXHA 5000 I/O modules are in Simplex or Duplex mode.

If you are using Concurrent Communication, your system must meet the following requirements:

• ControlLogix 5580 Redundancy – Required Components

• ControlLogix 5580 – Required Components

• Logix SIS Redundancy – Required Components

IMPORTANT: You are not required to use both FLEX 5000 Safety I/O modules and FLEXHA 5000 I/O modules in Logix SIS Redundancy. The requirements are listed in case you use either or both.

• GuardLogix 5580 – Required Components (Concurrent Communication must be set to Yes in the 1756-EN4TR module configuration for this to apply)

IMPORTANT: You are not required to use both FLEX 5000 Safety I/O modules and FLEXHA 5000 I/O modules in GuardLogix 5580 control systems. The requirements are listed in case you use either or both.

Error Code

If you attempt to upgrade or install a ControlLogix Redundancy System or ControlLogix 5580 controller application and see error code 16#0008 Service Request Error: Unsupported service, you must revert the system to the following software version and firmware revisions.

For more information, see the following:

• ControlLogix EtherNet/IP Network Devices User Manual, publication 1756-UM004
• FLEXHA 5000 I/O System User Manual, publication 5015-UM001
• FLEX 5000 Standard and Safety I/O Modules User Manual, publication 5094-UM001

• After restarting the computer, the RSLinxNG02.EXE service might stop responding. First identified in FactoryTalk Linx version 6.30.00. [Jira 1733073]

Corrected in FactoryTalk Linx version 6.31.00.

• In rare cases, the quantity of ports on the Internet Protocol tab in Device Configuration is incorrect. First identified in FactoryTalk Linx version 6.31.00. [Jira 1708148]

Corrected in FactoryTalk Linx version 6.31.00.

• FactoryTalk Linx Network Browser might be unable to communicate with some alias referenced boolean tags. First identified in FactoryTalk Linx version 6.30.00. [Jira 1595009]

Corrected in FactoryTalk Linx version 6.31.00.

• FactoryTalk Linx Network Browser might be unable to bridge to some controllers if the serial number starts with a letter. First identified in FactoryTalk Linx version 6.21.00. [Jira 1516972]

Corrected in FactoryTalk Linx version 6.31.00.

• After restarting the computer, the client applications that communicate with controllers might stop responding. First identified in FactoryTalk Linx version 6.31.00. [Jira 1745816]

Corrected in FactoryTalk Linx version 6.31.00.

• If you perform the write operation to both Dint and Dint.0 tags at the same time, the RSLinxNG.EXE service might stop responding. First identified in FactoryTalk Linx version 6.31.00. [Jira 1784872]

Corrected in FactoryTalk Linx version 6.31.00.

• After restarting the data server computer, the Nmsphost service might stop responding. First identified in FactoryTalk Linx version 6.31.00. [Jira 1591648]

Corrected in FactoryTalk Linx version 6.31.00.

• After FactoryTalk Linx is configured with CIP Security, FactoryTalk Linx Network Browser might show which means it cannot communicate with the device. First identified in FactoryTalk Linx version 6.31.00. [Jira 1808088]

Corrected in FactoryTalk Linx version 6.31.00.

• When FactoryTalk Linx is configured to communicate with PLC-5 or SLC500 controllers, it uses an INT datatype to deliver Bit/BOOLEAN data. When these Bit/BOOLEAN items are delivered through the FactoryTalk Linx Gateway’s OPC UA interface, an external client like the FactoryTalk Linx OPC UA Connector, may report an error for the items because they were not defined using a BOOL datatype. First identified in FactoryTalk Linx version 6.30.00. [Jira 1442309]

  Corrected in FactoryTalk Linx version 6.40.00.
  

• In the FactoryTalk Linx Network Browser, if the IP address of one device (for example, Device A) is changed to the same address as another device (for example, Device B), Device A may incorrectly show the child nodes from Device B when browsing. First identified in FactoryTalk Linx version 6.21.00. [Jira 1747843]

  To resolve the problem, restart the FactoryTalk Linx Network Browser.

• When adding, editing, or deleting a shortcut in the Communication Setup editor in FactoryTalk Administrator Console, RSLinxShortcutAOA.exe might stop responding. First identified in FactoryTalk Linx version 6.31.00. [Jira 1835623]

  Corrected in FactoryTalk Linx version 6.40.00.
  

• When the device IP address is changed in FactoryTalk Logix Echo, FactoryTalk Linx Network Browser will not detect the new IP address if the current driver is being auto browsed. First identified in FactoryTalk Linx version 6.31.00. [Jira 1916291]

  To resolve this problem, the driver can be refreshed by briefly selecting a different driver and then re-selecting the driver referencing the emulated controller or right-clicking the driver containing the emulated controller and selecting Refresh.

• FactoryTalk Linx does not show the correct information for the IO-Link device on the General tab of the Device Property dialog. First identified in FactoryTalk Linx version 6.31.00. [Jira 2055661]

  Corrected in FactoryTalk Linx version 6.40.00.
  

• If an IO-Link device's EDS files are not registered, FactoryTalk Linx does not show the correct IO-Link device name in the Network Browser. First identified in FactoryTalk Linx version 6.31.00. [Jira 2003122]
  

  Corrected in FactoryTalk Linx version 6.40.00.

• FactoryTalk Linx does not show the correct name for a BFS 26K-GI-L04-S92 device in the Network Browser. First identified in FactoryTalk Linx version 6.31.00. [Jira 2013246]

  Corrected in FactoryTalk Linx version 6.40.00.
  

• A name longer than 100 characters for some IO-Link devices will cause FactoryTalk Linx, Studio 5000 Logix Designer, and ControlFlash Plus to close unexpectedly. First identified in FactoryTalk Linx version 6.31.00. [Jira 2122536]

  Corrected in FactoryTalk Linx version 6.40.00.
  

• The value of the communication module predefine tag, @DevicePath, shows incorrectly on Windows CE system. First identified in RSLinx Enterprise version 5.60.00. [274999]
There is currently no workaround for this anomaly.

• In FactoryTalk Diagnostics Counter Monitor, HMI tag items do not always show under RnaDaSvr[TagSvr.exe]. First identified in RSLinx Enterprise version 2.51.00. [275196]
There is currently no workaround for this anomaly.

• If you rehost a FactoryTalk Linx data server (or an RSLinx Enterprise data server, in RSLinx Enterprise version 5.90.00 and earlier) to a different computer, you may fail to browse the existing device shortcuts in the Tag Browser. First identified in RSLinx Enterprise version 2.70.00. [356075]
To solve the issue, reconfigure the shortcuts in the Communication Setup editor and reboot the FactoryTalk Directory server.

• PanelView terminals cannot show in the Communications Setup editor.
If you use RSLinx Enterprise/FactoryTalk Linx to configure the Serial DF1 driver and specify the baud rate to be 110, 300, or 600, the PanelView terminals cannot show on the communication tree in the Communications Setup editor. First identified in RSLinx Enterprise version 5.60.00. [275151]

To avoid this problem, if your network includes a PanelView terminal that you want to browse, select an alternate baud rate when configuring the Serial DF1 driver.

• FactoryTalk View fails to get the previously reading tag value from a ControlLogix device.
If you use RSLinx Enterprise/FactoryTalk Linx to browse and read tag value of a ControlLogix device, when you manually change the Ethernet module IP address of this device and the IP address of it in RSLinx Enterprise/FactoryTalk Linx device list, FactoryTalk View fails to get the previously reading tag value. First identified in RSLinx Enterprise version 5.60.00. [341516]
There is currently no workaround for this anomaly.

• Installation of a PCICS or PKTX card driver may result in device browse failure.
When installing a PCICS or PKTX card driver on a computer, after the new card driver is installed into system device manager, the device may not show upon browsing. First identified in RSLinx Enterprise version 5.70.00. [346194]

• FactoryTalk Linx cannot browse the 1794 FLEX™ I/O modules under the FLEX I/O adapters in the Network Browser or in the Communication Setup editor. When you browse an online 1794 FLEX I/O adapter with 1794 FLEX I/O modules, the adapter shows in the communication tree, while no downstream port shows. First identified in RSLinx Enterprise version 5.90.00.
To work around this problem, use RSLinx Classic to get a listing of the connected modules and the related downstream port information.

• If you are running FactoryTalk Linx on Windows Server 2012, you cannot browse DH485 driver. First identified in FactoryTalk Linx version 6.00.00. [367931]
Switch to a different operating system and try again.

• A Datalogger error message may show up when using FactoryTalk Linx on FactoryTalk View ME. First identified in FactoryTalk Linx version 6.00.00. [367974]
There is no impact on the terminal or the data log function, and the error message can be ignored.

• If the .mer file user created is version 11.00 or earlier, when checking the unsupported shortcut path (using DHRIO connect to a ControlLogix Controller), the error message cannot be shown as expected. [Jira 488722]
There is currently no workaround for this anomaly.

• On a computer that contains a loopback adapter, after creating an Ethernet driver with Local Broadcast (Discovery Method > Broadcast > Local Broadcast) and Windows Default (Advanced > Interface > Windows Default), the devices cannot be shown when you browse the Ethernet driver. First identified in RSLinx Enterprise version 5.90.00. [Jira 489076]
To avoid this problem, disable the Microsoft Loopback Adapter from Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings or choose another network interface card.

• When a user clicks the SLC/PLC, the icon is changed to the browsing state. [Jira 487435]
There is no workaround for this anomaly, but there is no impact on the shortcut creation.

• After changing the Ethernet driver name, the device path cannot be automatically updated to the latest, so the Device Property page cannot establish connections. First identified in FactoryTalk Linx version 6.21.00. [Jira 354185]
To solve this problem, browse the driver again and make sure the device path is updated to the latest.

• After changing a driver's Interface under Configure Driver > Advanced, the Network Browser may incorrectly show good status for some device that it is unable to communicate with. First identified in FactoryTalk Linx version 6.21.00. [Jira 491731]
To solve this problem, delete the driver and re-create one with new Network Interface Card. Then, the device will display correctly.

• Even though an EDS file is removed or unregistered by the EDS Hardware Installation Tool, the associated device will still appear in the FactoryTalk Linx Network Browser with the proper icon, but some communications to the device may fail. [Jira 749380]
Reinstall an EDS file for the device to recover normal operation.

• For a driver created in the Network Browser as part of ControlFlash or Studio 5000 software, the driver do appear in the FactoryTalk Linx (previously named RSLinx Enterprise prior to version 6.00.00) configuration, but you can only view or change it from within the Network Browser from ControlFlash or Studio 5000. First identified in RSLinx Enterprise version 5.90.00. [363804]
There is currently no workaround for this anomaly.

• FactoryTalk Linx cannot browse the private network through a NAT device from the public side or the second network interface on a CompactLogix controller. [Jira 967248]
To solve this problem, reconnect the workstation to the private network to browse its devices.

• When multiple shortcuts in FactoryTalk Linx are configured to point at the same controller, changes made to one shortcut's "Extended Tag Properties" and "Description pass-through" settings will affect the operation of other shortcuts referencing the same controller on the same FactoryTalk Linx data server. First identified in FactoryTalk Linx version 6.10.00. [150898]
To solve this problem, configure all shortcuts to a device with matching settings.

• Changing the configurations in FactoryTalk Policy Manager and then restarting the FactoryTalk Linx service may cause FactoryTalk Linx to stop responding. First identified in FactoryTalk Linx version 6.10.00. [191818]
To solve this problem, restart the computer that hosts FactoryTalk Linx.

• In an Ethernet driver with a Device List/Range, change the original network interface card to another, the devices from the previous network are not removed. First identified in RSLinx Enterprise version 5.90.00. [Jira 489110]
Manually delete the unwanted device.

• If the user adds a new shortcut or a new server containing a shortcut that has the same name as an existing shortcut, all references to read or write tags from the original shortcut will fail when new items are requested via the original shortcut or when the data server or FactoryTalk software client (For example, FactoryTalk View SE or FactoryTalk Linx Gateway) are restarted. [Jira 857439]
To avoid this problem, verify any new shortcuts do not utilize the same name as existing shortcuts already in use; If a duplicate shortcut name is added, please edit or update all tag references to the original shortcut in order to restore communications.

• On a workstation that is configured with CIP security, disabling the network adapter, restarting the computer, and re-enabling the network adapter will cause FactoryTalk Linx Network Browser to be unable to browse new devices. First identified in FactoryTalk Linx version 6.10.00. [193473]
To solve this problem, restart the computer and try browsing the devices again.

• The Access Rights of CIA message shortcut and symbolic shortcut should be read-only but show as read-write in Tag Browser. First identified in FactoryTalk Linx version 6.21.00. [Jira 890371]
There is currently no workaround for this anomaly.

• If communications to a device is inhibit in FactoryTalk Linx, it will take a long time for FactoryTalk Live Data Test Client to browse tags. First identified in FactoryTalk Linx version 6.21.00. [Jira 978056]
To avoid this problem, set the timeout value by registry key "SOFTWARE\ROCKWELL SOFTWARE\RSLINXNG\LOGIXDP\VALIDATEITEMTIMEOUT". The unit for this value is millisecond, the default timeout value is 5 minutes.

• Online deleting or adding structure member in UDT (User Defined Data Type) is not reflected in the FactoryTalk Linx namespace. As a result, reading from such modified structure will not be possible or may deliver incorrect results. This applies only for UDTs that exists in FactoryTalk Linx namespace (tags of such UDTS were added for reading). [Jira 984705]
To solve the issue, restart the FactoryTalk Linx service.

• On the Runtime (Target) tab in FactoryTalk View ME, it may fail to add PLC or SLC device under a DHRIO device manually because the DHRIO channel A and channel B cannot be displayed. First identified in FactoryTalk Linx version 6.20.00. [Jira 1300592]

  To avoid this problem, copy the DHRIO device from the Design (Local) tab.

• When using the same workgroup user to sign in to different virtual machines with different passwords, some features of FactoryTalk Linx and FactoryTalk Live Data may fail to load. First identified in FactoryTalk Linx version 6.30.00. [Jira 1442619]

  To avoid this problem, use the same password to sign in to different virtual machines.

• When using FactoryTalk Linx to read the unsolicited message of the UDT array data type with multiple elements, if the Number of Elements is greater than 1, it might fail to read the unsolicited message. First identified in FactoryTalk Linx version 6.30.00. [Jira 1390885]

  To read the unsolicited message successfully, set the Number of Elements to 1 in Studio 5000 Logix Designer.

• The FactoryTalk Linx Network Browser is slow to discover and display devices on a bridged or downstream EtherNet/IP network using the default subnet mask discovery method. First identified in FactoryTalk Linx version 6.30.00. [Jira 1435882]

  To improve the detection speed, add individual device IP Addresses to the bridge module’s configuration used to connect to the network.

• When using the FactoryTalk Batch server to communicate Logix controllers and the FactoryTalk Linx Network Browser on the same workstation is browsing the system at the same time, the FactoryTalk Batch server might lose communication. First identified in FactoryTalk Linx version 6.30.00. [Jira 1501398]

  To avoid this problem, don't run FactoryTalk Linx Network Browser from the same workstation that is used to provide FactoryTalk Batch communications.

  To resolve the existing problem, close FactoryTalk Linx Network Browser and restart the FactoryTalk Batch server.

• Extensive online modifications within Studio 5000 Logix Designer, including modifications to extended tag properties, can lead to FactoryTalk Linx clearing cached extended tag properties but not properly reloading them. This could result in FactoryTalk View SE displaying wireframes or default values for a controller's extended tag properties. First identified in FactoryTalk Linx version 6.20.00. [Jira 2398000]

  To address this issue, make online modifications to controllers only when FactoryTalk View SE displays are not required. If the extended tag properties are missing, restart the appropriate FactoryTalk Linx service (RSLinxNG01.exe or RSLinxNG02.exe). Occasionally, it may be necessary to restart the FactoryTalk Linx service once more to restore the correct extended tag properties.

• When browsing for tags from a shortcut whose path bridges through a 1756-DHRIO card to a PLC or SLC controller, the Online folder cannot be expanded to show tags.

  To use the bridge browse function, install Factorytalk Linx version 6.30 or earlier.

The following are the application notes for FactoryTalk Linx version 6.31.00.

The upper limit of the length of C style strings specifier (SC##) supported in FactoryTalk Linx is 400 bytes. The default upper limit value is SC30, and you can increase the upper limit manually.

• When restoring FactoryTalk Linx configuration in FactoryTalk Administration Console, the existing drivers will be removed and new divers will be restored. The running shortcuts will be affected.
To avoid this issue, reconfigure the shortcuts after the restore process completed or use FactoryTalk Linx Configuration Import Export Tool to make a backup in advance.

• If you need to limit connections usage in your application, please refer to Rockwell Automation Knowledgebase Document ID: QA4294 - CIP connections with RSLinx Enterprise (Reducing PanelView Plus connections) for more information on FactoryTalk Linx connection usage.

• On a FactoryTalk Linx workstation where multiple IP addresses exist, only one of them can be configured with CIP security in FactoryTalk Policy Manager.

Rockwell Automation conducts tests using domain-joined computers configured according to CIS Benchmarks to help assure that software products perform as expected on computers that are hardened to industry best practices.

For more information about the guidelines and which products were tested against which CIS Benchmarks, see the Knowledgebase Document ID: QA63609 - Recommended guidelines for hardening software, computer, device, and network systems and infrastructure (CIS Benchmarks).

Note: If a product compliance with the benchmark is less than 100%, a link to a detailed spreadsheet is available. Download the spreadsheet to assist you in determining whether additional compensating controls are necessary.

FactoryTalk Linx version 6.31.00 has been tested on CIS Microsoft Windows 10 Enterprise (Release 21H2) Benchmark v1.12.0, CIS Microsoft Windows Server 2019 MS Benchmark v1.2.1, and CIS Microsoft Windows Server 2022 Benchmark v1.0.0.

Exceptions settings for FactoryTalk Linx version 6.31.00 are listed.

CIS Microsoft Windows 10 Enterprise (Release 21H2) Benchmark v1.12.0

• 19.7.8.5 (L1) Ensure 'Turn off Spotlight collection on Desktop' is set to 'Enabled' - This Group Policy path may not exist by default. It is provided by the Group Policy template CloudContent.admx/adml that is included with the Microsoft Windows 10 Release 21H2 Administrative Templates (or newer). No impact for products.

• Installing FactoryTalk Linx and RSLinx Classic on different drives results in icons displaying as question marks in the Communications Setup editor.
  To avoid this problem, FactoryTalk Linx must be installed on the same drive as RSLinx Classic.

• Attempt to create a run-time application (.mer file) when the Communication Setup editor is open returns the message: Unable to save the project runtime file at default path.
  To avoid this problem, close the Communication Setup editor before creating a run-time application (.mer file).

• Unexpected behavior occurs when browsing a BITSERIES alias with length exceed 32768 bits.
  To avoid this problem, limit the length of a BITSERIES alias to 32768 bits.

• Unexpected behavior occurs for different configurations in RSNetWorx™ and card's I/O map.
  If the configuration specified in RSNetWorx for ControlNet™ or DeviceNet™ does not match what is specified for the card's I/O map in FactoryTalk View ME, results can be unpredictable.
  To avoid this problem, verify the configuration in RSNetWorx matches what is specified for the card's I/O map.

• FactoryTalk Linx may define more I/O than is actually on the interface card.
• When you are entering sequential ControlNet connections, the software incorrectly calculates the maximum free status address.
  To avoid this problem, create a connection at status word 252 prior to reaching the limit condition.

• If you sort by address selection for bit aliases, the results may be out of order.
• Large configurations may take up to several minutes to load.
  This is most likely to happen if there is a large number (more than 500) of initial values of bit arrays.

• Address String field changes may be lost.
  If you make changes to the Address String box in an Alias Properties dialog box and then select a different Alias Data Type, the changes to the Address String box are lost.

• The quality of an output array alias may remain unchanged.
  If you have an output array alias whose data is delivered to two different controllers, the quality of that data is only determined by the health of the connection(s) that cover the first byte of the array. If you have a connection that takes the sixth byte of an array, for example, and that connection goes to a bad status, the quality of the array as a whole will remain unchanged.

• FactoryTalk Linx does not support some of the data types for Micro800™ series controllers, which include Date and Time, Structure and structure elements, Array of array. FactoryTalk Linx does not support array data types with non-zero starting index. Moreover, FactoryTalk Linx cannot read and write DINT bits directly, and it has no access to the User Defined Data Types. Bool Tags Array are not accessible from the Micro800 series controllers.
• FactoryTalk Linx cannot read Safety-class string tags from the GuardLogix controller. If you need to read these tags, copy the data to non-Safety-class tags.
• FactoryTalk Linx does not recognize or honor protected tags in the 1785-L46C15. Attempts to write to any protected tags will succeed.
• Attempts to read or write input or outputs on the MicroLogix™ 1000 Series A controller will result in data read as bad quality.
  To avoid this problem, replace the Series A controller with a Series E controller.

• FactoryTalk Linx cannot browse for tags in PowerMonitor 3000 devices.
• FactoryTalk Linx cannot browse for tags secured by the FactoryTalk® AssetCentre security feature.
• FactoryTalk Linx cannot browse for tags in SLC controllers that have been secured using the FactoryTalk AssetCentre security feature introduced in RSLogix 500® v7.10 (CPR 7).
• FactoryTalk Linx cannot browse, read, or write the RI and PLS data table sections of a MicroLogix 1100 controller.
• FactoryTalk Linx cannot automatically browse the PLC5-80E E/K Device.
• ASCII data cannot be read from SLC integer files.
• In RSLogix 5000 software or Studio 5000 Logix Designer application, if you delete a motion, digital/analog alarm, or message tag on scan, there is no checking mechanism in the controller to prevent the deletion. Further, there is no visual indication in RSLogix 5000 software or Studio 5000 Logix Designer application that these tag types have been deleted from scan; it will appear as if these tags continue to receive data, but that data is invalid. If you have these types of tags on scan, Rockwell Automation recommends that you do not delete them. For more information, see the Knowledgebase Document ID: QA8279 - What tags in a Logix controller can be deleted whilst on scan in an HMI application.
• In Studio 5000 Logix Designer, if you rename a program online, communications to tags using the old name are not initially affected and the tag browser will not initially show the tags under the new program name until the FactoryTalk Linx service is restarted, the controller is restarted or a new application is downloaded into the controller, at which time communications to the tags using the old program name will fail and the tag browser will show tags under the new program name.
  To prevent this problem, avoid renaming a program online. If a program is renamed online, restart the FactoryTalk Linx service or restart the controller, or redownload the controller's application after renaming a program.

• FactoryTalk Linx added EtherNet/IP to DH+ Bridging, it can now read data from PLC5 and SLC-500 controllers connected to DH+.
• When FactoryTalk Linx added EtherNet/IP to DH+ Bridging, the 1756-DHRIO supports up to 32 CIP connections per channel. If more connections are needed, utilize the second channel on the 1756-DHRIO module or install additional 1756-DHRIO modules in the ControlLogix Chassis.
• In FactoryTalk Linx, using DHRIO to connect a controller, the upper limit of connection through this DHRIO module is 32 per channel. For ControlLogix Controllers, each shortcut can create 2-8 connections. For SLC/PLC controllers, each shortcut can create 1-4 connections. If a redundant (secondary) FactoryTalk Linx server is configured, the number of connections through the DHRIO Module will be doubled. FactoryTalk Linx added a user option to limit the number of connections for a shortcut of SLC/PLC controllers, more information can be found in the Shortcut Properties table in the FactoryTalk Linx Help.
• If a PanelView Plus 7 terminal needs to access data from PLC5 and SLC-500 controllers connected to DH+, the upper limit of connection is 2 per shortcut, which is a fixed value and cannot be adjusted.
• FactoryTalk Linx can only utilize solicited communication controllers on DH+ (the unsolicited shortcut type cannot be used).
• FactoryTalk Linx does not support modifying the configuration of the DHRIO module or SLC/PLC controllers under the DHRIO module.
• FactoryTalk Linx does not support Map PLC/SLC Message when user needs to read or write data from the ControlLogix controller connected to DH+ with PCCC protocol. User could use CIP instead to read and write data from the ControlLogix controller.
• FactoryTalk Linx is unable to support Logix controller based alarms or access to Extended Tag properties of controllers connected using DH+. Disable the Enable alarm and event support, Upload all extended tag properties, and Provide pass-through descriptions for tags options.
• For SLC or PLC controllers with the same node on different channels connected to a 1756-DHRIO module, if the Enable Network Path (System > Policies > Product Policies > FactoryTalk Linx > Server Setting > Shortcut Policy) is set to Disable, FactoryTalk Linx will browse the device using the Device Path which does not contain node address information, so FactoryTalk Linx will pick up the wrong device on other channel. If the Enable Network Path is set to Enable, FactoryTalk Linx will browse the device using the Network Path which contains node address information, so different SLC or PLC controllers with the same node address can be distinguished.

• This version of FactoryTalk Linx maintains compliance with the EtherNet/IP standard of Open DeviceNet Vendor Association, Inc. (OVDA).

• FactoryTalk Linx version 6.00.00 cannot be used as the communication software if you are using ControlFLASH version 14.00.00.
  To avoid this problem, upgrade ControlFLASH to version 15.00.00 and try again, or use RSLinx Classic as the communication software.

• If FactoryTalk Linx is uninstalled and then reinstalled, controller-generated alarms will not be shown.
  To avoid this problem, reboot your computer before you reinstall FactoryTalk Linx.

• Duplicate alarms may exist when renaming or deleting a shortcut.
  If a shortcut is renamed or deleted, the previous FactoryTalk Alarms and Events subscription to that shortcut remains until the FactoryTalk Linx service is restarted.
  To prevent the generation of duplicate alarms, restart the FactoryTalk Linx service after you rename or delete a shortcut.

• Special characters in shortcut names may results in unexpected behavior.
  Device Shortcuts are defined in the Communications Setup editor for the FactoryTalk Linx server. Using shortcut names containing special characters (for example, asterisks, pipes) results in unexpected behavior in the FactoryTalk Alarms and Events system.
  To avoid this problem, do not use special characters in the device shortcut name for the FactoryTalk Linx server when using FactoryTalk Alarms and Events to monitor device-based alarms.

• If an analog alarm uses a DINT as the input value, the value may be reported incorrectly in custom messages for very large DINTs (both positive and negative).
  If the DINT value exceeds 24 significant bits, the controller will round it to the nearest REAL value using 24 significant bits. This applies only to the input value and not associated tag values.

• If an alarm changes state ("out of alarm" to "in alarm") while FactoryTalk Linx is disconnected from the network, the last transition message logged to the database is correct but duplicated.
• When rehosting a FactoryTalk Alarms and Events server to a different computer, the prior host computer may fail to unload the running alarm server, and the new host computer may fail to load the alarm server.
  To avoid this problem, restart both the prior and new host computers.

• FactoryTalk Linx does not support the Fast User Switching feature in Windows operating systems.

• In FactoryTalk View Studio, you cannot use the File Transfer Utility to upload/download FactoryTalk View ME (*.mer) files from/to a network location. Although the upload/download appears to complete (via the disappearance of the upload/download progress bar), a follow-up dialog box notifies you that the operation did not complete.
  Uploading/downloading FactoryTalk View ME (*.mer) files from/to your local computer works properly. If you want to download a file, please copy it from the network location to your local hard drive. If you want to upload a file, upload to a local hard drive and then copy it to the network location.

• The operation of the Firmware Upgrade Wizard over the Serial-DF1 port is not supported.
  To avoid this problem, it is strongly recommended that you create a Firmware Upgrade Package on an external compact flash and use this as a means to upgrade your terminal.

• Memory related counters and predefined tags are not displayed correctly for L8x controllers. This information is normally obtained from the controller. However, the Logix L8 (ControlLogix 5580 and CompactLogix 5480) series of controllers do not provide this information because of architectural changes within the controller firmware.

• Diagnostic counters：FreeMem, FreeMem Datatable, FreeMem General, FreeMem IO, FreeMem Security, TotalMem, TotalMem Datatable, TotalMem General, TotalMem IO, TotalMem Security
• Predefined tags: @FreeMem, @FreeMemIO, @FreeMemDT, @FreeMemGM, @FreeMemSC, @TotalMem, @TotalMemIO, @TotalMemDT, @TotalMemGM, @TotalMemSC

Impact of Microsoft deprecating VBScript

• Microsoft announced the phased deprecation of VBScript in 2024. VBScript is now an optional feature beginning in Windows 11 24H2 and Windows Server 2025. Many FactoryTalk software products released before September 1, 2026, use VBScript during installation.
• FactoryTalk Linx versions 6.60.00 and earlier require VBScript for installation. Installation will fail if VBScript is not enabled.
• To mitigate the problem, enable VBScript manually. For more information, see the Knowledgebase Document ID: IN41397 - Impact of Microsoft deprecating VBScript. FactoryTalk software products released after September 1, 2026, no longer rely on VBScript.

In response to Microsoft Distributed Component Object Model (DCOM) Hardening patch (MS KB5004442), the minimum DCOM authentication level used by Rockwell Automation products was raised to Packet Integrity.

Microsoft releases the DCOM Hardening patch in response to CVE-2021-26414. This patch elevates the minimum DCOM authentication level that is required to establish a DCOM connection. DCOM is used by many Rockwell Automation products and may be affected by the change that is made by the Microsoft patch. For additional information about the affected Rockwell Automation products, see the Knowledgebase Document ID: PN1581 - Product Notification 2022-01-001 - Rockwell Automation products unable to establish proper DCOM connection after installing Microsoft DCOM Hardening patch (MS KB5004442).

• The Who Browser is renamed to Network Browser in FactoryTalk Linx version 6.00.00.
• If multiple copies of the Network Browser are open and have the same driver selected, the browser discovery for the selected driver may not work.
  To avoid this problem, close other instances of the browser or have them select a different driver.

• The FactoryTalk Linx driver name are limited to a subset of ASCII characters. The FactoryTalk Linx Network Browser fails to load if double-byte characters, a period (.), backslash (\), left bracket ([), or right bracket (]) are embedded in the name.
  To avoid this problem, follow the naming rule of FactoryTalk Linx drivers.

• In FactoryTalk Linx Network Browser, the computer name should not exceed 15 characters. Otherwise, the workstation name in the Network Browser topology will be truncated to 15 characters. This issue is first found in RSLinx Enterprise version 5.90.00.

• The 1756-DH485 module is not supported as a bridge device in FactoryTalk Linx.
• On occasion, an attempt to download a large .mer file over a DF1 connection to a PanelView terminal fails.
  To avoid this problem:
  • Retry downloading the file.
  • When communicating with PanelView Plus units, be sure to set the error-checking mode to CRC.

• The I/O card does not show up in the tag browser.
  If you are unable to use the SLC I/O in the slot you have selected, the I/O card does not show up in the tag browser.
  To avoid this problem, try to use a different slot.

• Addresses above word 99 in a MicroLogix 1500 input table does not show correctly.
  To avoid this problem, use only addresses 0 to 99 for display purposes.

• When entering item names for a PLC, SLC, or MicroLogix device, FactoryTalk Linx recognizes a slash (/) as a bit qualifier but does not recognize a period (.). For example:
  • O:1/7 is acceptable
  • O:1.7 is not acceptable and generates an error.

• FactoryTalk Linx may take a long time to show the Device Properties dialog box for PKTCS and PCICS cards.
• Devices accessed through a 1440-ACNR module may not be properly identified, and an error message may appear stating that FactoryTalk Linx fails to recognize the bus type.
• In FactoryTalk Linx version 6.20.00, after renaming a driver, any shortcuts pointing to devices referencing the driver may fail to communicate.
  To prevent this problem, avoid renaming drivers. If a driver is renamed and communications through a shortcut fails, either restore the original driver’s name or use the shortcut configuration dialog to update any effected shortcuts to the correct device under the renamed driver.

• If an alias tag is created with its base tag's data type as ALARM_ANALOG and ALARM_DIGITAL, FactoryTalk Linx doesn't provide pass-through descriptions for this alias tag. Manually input descriptions if needed.

• Starting with version 6.10.00, the FactoryTalk Linx "@RedundancyMode" pre-defined tag was removed and is no longer supported. If an application attempts to access the data value for this tag, it will only receive the default value "0" and the reference will show as a wireframe in FactoryTalk View. To avoid this, remove references to this tag from the application.

• Double-right-clicking a node in the I/O tree may show the menu for an unselected item.
• The 1771-SN sub-scanner does not support block transfers for remote I/O.

In a FactoryTalk system, data moves from a source like a controller connected to FactoryTalk Linx to a software client when a data item’s value has changed. Once changes are detected, the data values are transferred between multiple components or services. The services use the subscription rate from the requestor to initiate a processing thread to transfer the data to its next destination in the system. Small processing delays by components, network delivery time, a high number of values changing at once, or a heavily loaded system can cause data to be processed and delivered slower than the requested rate. If the source data value changes faster than twice the subscription rate, a newer data value could likely overwrite a previous data value as it travels between the services.

In some cases, sampling at a rate faster than half of the speed of the value changes can help to ensure that data value changes are detected by the requester. Also, balancing the data subscriptions across multiple computers and services can reduce processing and delivery delays.

• If you create a PLC5 or SLC500 shortcut with a name longer than 135 characters, you are not able to access that PLC or SLC.
  To avoid this problem, limit the PLC or SLC shortcut names to less than 135 characters.

• If you change a FactoryTalk Linx shortcut from one driver type to another, for example, from Ethernet to ControlNet, you may not be able to access data on the newly configured shortcut.
  To restore data access, reboot the FactoryTalk Linx computer.

• If you configure FactoryTalk View SE to run in a distributed environment and disconnect (or power off) the computer functioning as the FactoryTalk Directory server, the Communication Setup editor cannot show any previously configured shortcuts.
  To view your shortcuts, ensure that the computer functioning as the FactoryTalk Directory server is powered on and connected to the network.

• Clients may not re-establish communications to offline device shortcuts after restarting FactoryTalk Linx data server.
  For the shortcuts which are configured to offline devices, clients may fail to communicate to them after the FactoryTalk Linx data server is rebooted.
  To recover communications to offline device shortcuts, click Show All Devices in the Communication Setup editor.

• In a FactoryTalk ME runtime application, if both Processor and CIP-CIA shortcuts point to the same device, after a connection break, the tag value on the terminal will take an extended period of time to recover.
• When FactoryTalk Linx is utilized in a PlantPAX system, or a FactoryTalk View system that utilizes Logix Extended Tag properties or tag-based alarms, tag data delivery times, controller and network loading are negatively impacted if the extended tag property checkboxes (Upload all extended tag properties and Display pass-through values for tag extended properties) for the primary and secondary FactoryTalk Linx data servers are not enabled.
  To ensure the best operation, the extended tag properties checkboxes for the primary and secondary FactoryTalk Linx data servers should be enabled on both servers.

• If a user deletes a shortcut or reconfigures a shortcut to a different device, the related connections are not released.
  To avoid this problem, close and reopen the Live Data Test Client, or restart the FactoryTalk Linx service.

• When a controller is inhibited in a redundant FactoryTalk Linx server configuration, the primary and secondary servers do not synchronize the inhibit state. This could result in the controller having the wrong state after a switch from the active to a standby server.
  To ensure consistent operation, it is recommended to set the Inhibit Data Communications bit for the device on both the active and standby servers. 
  This can be accomplished by one of the following methods:
  • Manually inhibit the device on both the primary and secondary tabs in the FactoryTalk Linx communication setup editor.
  • Set the predefined diagnostic tag @DataCommunicationsInhibit with the ",S1" and ",S2" modifiers, to one, to inhibit the device on the active and standby server (For example, "[ShortcutName]@DataCommunicationsInhibit,S1" and "[ShortcutName]@DataCommunicationsInhibit,S2").

• For information on the security considerations when using Rockwell Automation products, including:

• File extensions created by Rockwell Automation software, firewall rules, and service dependences, see Rockwell Automation Knowledgebase Document ID: PN826 - Security considerations when using Rockwell Automation Software Products.
• TCP/UDP ports used by Rockwell Automation products, see Rockwell Automation Knowledgebase Document ID: BF7490 - TCP/UDP Ports Used by Rockwell Automation Products.
• To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products (publication SECURE-AT001).

• When you design and set up a FactoryTalk system, we recommend using the following guidelines. If you find that your system needs to expand beyond these guidelines, contact your Rockwell Automation sales or distributor representative to discuss your application design.

• The FactoryTalk Live Data server has the following update rate settings:

• 10 ms
• 20 ms
• 50 ms
• 100 ms
• 250 ms
• 500 ms
• 600 ms
• 700 ms
• 800 ms
• 900 ms
• 1000 ms
• A number that is a multiple of 1000 ms

• When a client application sets an update rate different from the FactoryTalk Live Data server settings, the FactoryTalk Live Data server will update the tag using the closest update rate. For example, the client application sets a 70 msc update rate, the FactoryTalk Live Data server will use 50 msc instead. If the client application update rate is configured as 1000 msc or larger, the FactoryTalk Live Data server will use the integer seconds. For example, the client application sets a 1600 msc update rate, the FactoryTalk Live Data server will use 2000 msc instead. Note that if the client update rate is set as 0 msc, the FactoryTalk Live Data server will use 10,000 msc instead.
• There are many factors that can impact the resulting speed that data can be accessed (controller or network communications bandwidth, computer processing capacity, other operations being performed on the computer running FactoryTalk Linx), because of this, requested data values may/will be missed, particularly for the faster rates. Verify the system operation to ensure it handles the resulting effective rate and handles cases where periodic values are not delivered.

Use command-line parameters to perform an unattended or silent installation of the software.

The following table identifies the installation command-line parameters. Command-line parameters are case-insensitive. However, if a specified value includes a space, be sure to enclose the value in quotation marks (for example, "value with spaces").

The following examples show how to use the installation commands.

• To install the software with no user interface using the default settings during the installation process. (Silent install)
  Setup.exe /Q /IAcceptAllLicenseTerms

• To install the software with Chinese displayed during the install process and restart the computer if necessary. (Unattended install)
  Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS

• To install the software with FactoryTalk security policy value specified.
  Setup.exe /Q /IAcceptAllLicenseTerms /ftsp-value=enable

• To perform a restore during the install process.
  Setup.exe /Q /IAcceptAllLicenseTerms /ftsp-bak="C:\aa.bak"

• To specify the FactoryTalk Directory machine.
  Setup.exe /Q /IAcceptAllLicenseTerms /DirectorySever=severname

The following table identifies the error codes that can be returned by an installation.

The following certificates are installed while installing Rockwell Automation software.

• Use Microsoft Management Console (MMC) to view the certificates in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
  • 2016-Rockwell-Driver-SHA1.cer
  • 2016-Rockwell-SHA256.cer
  • DriverCodeSigning2012-1.cer
  • Drivers-10-10-2018.cer
  • Drivers-11-03-2017.cer
  • Drivers-12-06-2016.cer
  • DriversSHA1-10-10-2018.cer
  • Drivers-SHA1-11-27-2017.cer
  • Logix-11-04-2016.cer
  • Rockwell_2013.cer
  • Rockwell_2014.cer
  • Rockwell_2015.cer
  • rockwellcert2010.cer
  • rockwellcert2013.cer
  • VeriSign Class 3 Public Primary Certification Authority -G5 2036.cer

• Use Microsoft Management Console (MMC) to view the certificates in Console Root > Certificates (Local Computer) > Trusted Publishers > Certificates.
  • MicRooCerAut2011_2011_03_22.cer
  • RA - Enterprise Root Certification Authority.cer
  • VeriSign Universal Root Certification Authority.cer