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

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

• Windows Server® 2025 Standard (Recommended OS)**
• Windows Server 2022 Standard (Recommended OS)**
• Windows Server 2019 Standard**
• Windows Server 2016 Standard**
• Windows® 11 Professional (Recommended OS)
• Windows 11 Enterprise (Recommended OS)
• Windows 11 IoT Enterprise 2024 LTSC 64-bit (v24H2)***
• Windows 11 Enterprise 2024 LTSC 64-bit (v24H2)
• Windows 10 Enterprise 64-bit
• Windows 10 Professional 64-bit
• Windows 10 Enterprise 2021 LTSC 64-bit (v21H2) (Recommended OS)
• Windows 10 IoT Enterprise 2021 LTSC 64-bit (v21H2)***
• Windows 10 Enterprise 2019 LTSC 64-bit (v1809)

• ControlFLASH version 15.09.00
• ControlFLASH Plus version 6.01.00
• EDS subsystem version 38.0
• FactoryTalk Action Manager version 1.02.00
• FactoryTalk Alarms and Events version 6.60.00
• FactoryTalk AssetCentre version 16.00.00
• FactoryTalk Batch version 18.00.00
• FactoryTalk Linx Data Bridge version 6.60.00
• FactoryTalk Linx Gateway version 6.60.00
• FactoryTalk Linx OPC UA Connector version 6.60.00
• FactoryTalk Logix Echo version 3.00.01
• FactoryTalk Policy Manager version 6.60.00
• FactoryTalk Services Platform version 6.60.00
• FactoryTalk Updater version 4.30.00
• FactoryTalk View version 16.00.00
• KEPServer Enterprise version 16.00.00
• Studio 5000 Logix Designer version 38.00.00
• Studio 5000 View Designer version 11.00.00

• 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.

• PCID(S) firmware revision 3.016. The PCIDS cards support I/O only.
Tip: FactoryTalk Linx also supports bridging from Ethernet (1756-ENxxx) to DeviceNet (1756-DNB) across a ControlLogix Chassis.

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

• Configuring Firewalls for FactoryTalk Services Platform (publication FTSP-RM001) shows the ports, services, and firewall rules necessary for FactoryTalk® Services Platform components to function properly.
• Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001) is built on, and adds to, design guidelines from the Cisco Ethernet-to-the-Factory (EttF) solution and the Rockwell Automation Integrated Architecture™.

• FactoryTalk Security Application Technique (publication SECURE-AT002) explains how to use FactoryTalk Security to implement authentication and authorization in your industrial automation system and how to enforce product-specific security for applications like Studio 5000 Logix Designer, FactoryTalk View, and FactoryTalk AssetCentre.

• System Security Design Guidelines Reference Manual (publication SECURE-RM001) provides guidelines for how to use Rockwell Automation products to improve the security of your industrial automation system.
• Configure System Security Features User Manual (publication SECURE-UM001) describes the system-level configuration requirements to use a controller that has achieved IEC 62443-4-2:2019 certification.
• CIP Security with Rockwell Automation Products Application Technique (publication SECURE-AT001) explains how to implement the Common Industrial Protocol (CIP) Security standard in your industrial automation control system (IACS).

• Support EtherNet/IP In-cabinet Solution.
• Support 1756 ControlLogix® 5590 Controllers.
• Support Stratix™ 4100 EtherNet/IP Test Access Point (ETAP).
• Support tags from FactoryTalk Design Studio® .
• Add new predefined tags (@AlarmClass and @AlarmGroup) to show the value of alarm class and alarm group from a Logix controller.
• Support a new FactoryTalk Linx extended tag property @Shortcut.

• FactoryTalk Directory clients are losing communication with the FactoryTalk Directory Server which disrupts other Rockwell Automation software products that rely on the FactoryTalk Directory, such as Studio 5000 Logix Designer or FactoryTalk View Site Edition. The root cause is an anomaly with leap year handling in a FactoryTalk Alarms and Events service causing high CPU and memory usage when the system date is February 28 in non-leap years. For more information, see Product Notice 2025-03-001 – FactoryTalk® Alarms and Events anomaly causes High CPU and Memory usage preventing a FactoryTalk® Directory Client from communicating with the FactoryTalk® Directory Server. First identified in FactoryTalk Services Platform version 6.40.00. [Jira 4180731]
Corrected in FactoryTalk Services Platform version 6.60.00.

• FactoryTalk Linx Configuration Import Export Tool is unable to import driver configurations from CSV files created in version 6.40.00 or earlier. First identified in FactoryTalk Linx version 6.50.00. [Jira 4076958]
• FactoryTalk Linx may fail to communicate with a Logix controller using CIP Security if the computer’s Network Interface Card (NIC) configuration or IP address has been changed. First identified in FactoryTalk Linx version 6.40.00. [Jira 3159425]
• While online with Studio 5000 Logix Designer, creating a Logix tag-based alarm, where the input is configured to a program-scoped tag defined as an output parameter, can cause FactoryTalk Linx to clear the 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 program-scoped extended tag properties. First identified in FactoryTalk Linx version 6.30.00. [Jira 3269352]
• When FactoryTalk Linx connects to controller using CIP Security, the certificate Subject Alternative Name (SAN) check accepts a valid certificate but does not properly verify the controller's IP address. First identified in FactoryTalk Linx version 6.50.00. [Jira 3894454]
• FactoryTalk Linx continues to log diagnostics for write attempts to inhibited controllers. First identified in FactoryTalk Linx version 6.30.00. [Jira 4166317]
• FactoryTalk Linx may unexpectedly stop during certain write operations, which may also affect FactoryTalk Linx Gateway when it relies on FactoryTalk Linx as a data server. First identified in FactoryTalk Linx version 6.50.00. [Jira 3991472]
• FactoryTalk Linx is unable to deliver @AlarmClass or @AlarmGroup properties when the shortcut is configured to upload all extended tag properties. First identified in FactoryTalk Linx version 6.50.00. [Jira 4034822]
• FactoryTalk Linx may shut down unexpectedly when uploading a Device Description file (previously EDS file) that contains UTF‑8 Unicode characters. First identified in FactoryTalk Linx version 6.50.00. [Jira 4037301]
• FactoryTalk Linx Network Browser may show incorrect IP addresses for Ethernet/IP In-cabinet devices and does not alert users when LLDP data is read incorrectly. First identified in FactoryTalk Linx version 6.50.00. [Jira 4175443]
• FactoryTalk Linx Network Browser shows incomplete support for the 1834‑AENTR gateway, including missing network details, EDS upload restrictions, UI inconsistencies, and lack of progress indicators. First identified in FactoryTalk Linx version 6.50.00. [Jira 4007834]
• FactoryTalk Linx presents tags differently than FactoryTalk Design Studio. First identified in FactoryTalk Linx version 6.50.00. [Jira 4035022]
• FactoryTalk Linx incorrectly allows data server name and server type properties to be modified after initial creation in the FactoryTalk Administration Console, which can result in communication problems. First identified in FactoryTalk Linx version 6.50.00. [Jira 3962887]
• FactoryTalk Linx web-based Network Browser may become unresponsive and report a timeout when a driver includes more than 25 IP addresses. First identified in FactoryTalk Linx version 6.50.00. [Jira 3925915]
• FactoryTalk Linx Network Browser network driver nodes may disappear because redundancy validation in the  netbrowser.dll library removes devices from other subnets. First identified in FactoryTalk Linx version 6.50.00. [Jira 3794255]
• FactoryTalk PharmaSuite read requests through FactoryTalk Live Data may fail to return updated values due to improper sequencing in the FactoryTalk Linx service. First identified in FactoryTalk Linx version 6.21.00. [Jira 3751171]
• When FactoryTalk Transaction Manager performs a high number of tag writes in a short duration, some tag value changes detected by FactoryTalk Linx may not be delivered to FactoryTalk Transaction Manager through FactoryTalk Live Data. First identified in FactoryTalk Linx version 6.30.00. [Jira 4945457]
• The FactoryTalk Live Data  CommandCliServ.exe service may shut down unexpectedly due to excessive memory usage when numerous FactoryTalk Batch event macros call FactoryTalk Live Data. First identified in FactoryTalk Linx version 6.31.00. [Jira 3984425]
• The FactoryTalk Live Data Tag Browser may display wrapped tooltips that are hard to read when the zoom ratio is set below 100%. First identified in FactoryTalk Linx version 6.40.00. [Jira 3978887]
• FactoryTalk View ME version 14.00.00 displays an “Unsupported device detected” warning from FactoryTalk Linx when creating a version 13.00.00 MER file. First identified in FactoryTalk Linx version 6.40.00. [Jira 3159461]
• Messages associated with Process Tags in P controllers do not update properly in FactoryTalk Alarms and Events until the FactoryTalk Linx service is restarted. First identified in FactoryTalk Linx version 6.40.00. [Jira 3836611]

• When 5015-U8IHFTXT I/O modules are configured as duplex or redundant, connected HART field devices do not appear in the FactoryTalk Linx Network Browser. This prevents FactoryTalk Linx CommDTM from detecting HART devices and hinders FDT-based asset management software from managing connected HART devices. For more information, see Knowledgebase Document ID: BF31975 - FactoryTalk Linx Fails to Browse HART Devices Through a 5015-U8IHFTXT Module. First identified in FactoryTalk Linx version 6.31.00. [Jira 4181852]
While there is currently no workaround for this anomaly, you can pre-configure the HART device by connecting it first to a different singular HART module, then moving the device to a duplex or redundant 5015-U8IHFTXT I/O module once configured.

• FactoryTalk Linx Network Browser is unable to discover devices if you import an Excel-saved CSV file that contains IP addresses with descriptions.
This problem occurs when you export driver configurations from FactoryTalk Linx Configuration Import Export Tool into a CSV file, and then save it in Excel. Excel adds additional quotation marks to the IP addresses that include descriptions in the "Device" column. This change makes the IP formatting invalid. First identified in FactoryTalk Linx version 6.40.00. [Jira 5031074]
To avoid this problem, open the Excel-saved CSV file with a plain text editor, such as Notepad, replace all instances of two double quotes ("") with a single double quote ("), remove the single double quotes (") at the start and end of each affected data string, and then save the file.
Example:
• Incorrect format: "10.0.0.1 ""des1"";10.0.0.2 ""des2"""
• Corrected format: 10.0.0.1 "des1";10.0.0.2 "des2"

• After installing FactoryTalk Linx, the FactoryTalk Linx CIP Security Service may fail to start due to a malformed configuration file, cip_security.xml. This problem occurs when FactoryTalk Linx fails to generate a valid file containing the required elements. First identified in FactoryTalk Linx version 6.10.00. [Jira 4974457]
To avoid this problem, go to C:\ProgramData\Rockwell\RSLinx Enterprise, delete cip_security.xml, and then restart the FactoryTalk Linx CIP Security Service in Windows Services.

• FactoryTalk Linx Network Browser does not display DF1 devices under the Serial-DF1 driver node. First identified in FactoryTalk Linx version 6.60.00. [Jira 5079449]
There is currently no workaround for this anomaly.

• FactoryTalk Linx Gateway MQTT subscriber is unable to write to ULINT and LINT bit tags beyond bit 31 (.32 through .63) due to incorrect handling of 64-bit bit addressing. First identified in FactoryTalk Linx version 6.60.00. [Jira 5101046]
There is currently no workaround for this anomaly.

• When the Enable alarm and event support checkbox is selected in the FactoryTalk Linx Server, the server and the Communication Setup editor may stop responding if the processor shortcut’s IP address points to a Windows computer with FactoryTalk Linx version 6.60.00 installed or a PanelView device. First identified in FactoryTalk Linx version 6.60.00. [Jira 5214872]
To resolve this problem, do the following:
1. In the FactoryTalk Linx Server properties, clear the Enable alarm and event support checkbox.
2. In the Communication Setup editor, specify the processor shortcut to connect to a Logix controller.
3. Restart the FactoryTalk Linx Server.
4. In the FactoryTalk Linx Server properties, select the Enable alarm and event support checkbox.

• In a redundant HMI system, if the secondary HMI server is disconnected, downloading a recipe with HMI tags in RecipePro+, and then performing subsequent operations such as refresh, download, or upload will cause RecipePro+ to stop responding. First identified in FactoryTalk Linx version 6.50.00. [Jira 5070999]
To resolve this problem, restart the HMI client computer and connect the secondary HMI server to the network.

• Downloading a large number of sizable ACD project files, such as twenty 40 MB projects, in parallel to multiple controllers using Logix Designer SDK may cause FactoryTalk View SE HMI clients to stop responding. First identified in FactoryTalk Linx version 6.60.00. [Jira 5214276]
To resolve this problem, restart the HMI server computer or disconnect the computer from the network and then reconnect.
To avoid this problem, do one of the following:
1. Reduce the number of controllers that are concurrently updated.
2. On the FactoryTalk Directory server computer, open FactoryTalk Administration Console, and then expand the application node that contains the HMI server before downloading the projects.

• FactoryTalk Live Data Test Client is unable to load tags from a remote OPC DA connection. The issue arises when multiple channel node names within KEPServer Enterprise or KEPserverEX are identical, or when multiple topic names within RSLinx Classic servers are identical. First identified in FactoryTalk Linx version 6.40.00. [Jira 1640452]

  To avoid this problem, create different channel node names for KEPServer Enterprise or KEPserverEX, and different topic names for RSLinx Classic servers.

• FactoryTalk Linx Network Browser is unable to discover the 1756-ENET module. First identified in FactoryTalk Linx version 6.40.00. [Jira 1728249]

  To work around this issue, add the 1756-ENET module as an offline device in FactoryTalk Administration Console. This will enable the FactoryTalk Linx Network Browser to communicate with the module and support bridging through it. However, RSLinx Classic must be used to change the module’s configuration. Since the 1756-ENET module was discontinued in June 2010, it is recommended to replace it with a newer generation module.

• FactoryTalk Linx Network Browser is unable to update the network topology and will report errors if you attempt to interact with a device. The issue arises when RSLinxNG.exe, the FactoryTalk Linx service, is not running or has been restarted in the Task Manager. First identified in FactoryTalk Linx version 6.40.00. [Jira 3077256]

  To restore normal operation, close the FactoryTalk Linx Network Browser from the Windows system tray and then restart it.

• The Tag Browser is unable to browse the HMI tags when the HMI server is rehosted after being restored to another computer. First identified in FactoryTalk Linx version 6.40.00. [Jira 2398016]

  To restore normal operation, restart the Nmsphost service in the Task Manager or restart the computer that the FactoryTalk Directory server is running on.

• Studio 5000 Logix Designer is unable to go online with a controller with CIP Security enabled. First identified in FactoryTalk Linx 6.40.00. [Jira 3055457]

  To avoid this issue, ensure the FactoryTalk Linx driver used to find the controller uses the correct network interface card (NIC). The selected NIC must match the IP address FactoryTalk Policy Manager uses to deploy CIP Security to the device. Note it is best to avoid using the Windows default if there are multiple NICs on the computer.

• 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.

• FactoryTalk Linx Network Browser may appear as a black window the first time it is launched after the computer is started. First identified in FactoryTalk Linx version 6.40.00. [Jira 3182692]

  To restore normal operation, click the FactoryTalk Linx Network Browser icon in the Windows system tray or the Start menu.

• 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.

• 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.

• 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.

• 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.

• When adding invalid numbers or strings between an array element and the L modifier in FactoryTalk Live Data Test Client, FactoryTalk Linx delivers a null value with good quality but should report the item as invalid with bad quality. First identified in FactoryTalk Linx version 6.50.00. [Jira 3798104]
  There is currently no workaround for this anomaly.

• FactoryTalk Linx Network Browser Port Configuration tab for the EtherNet/IP in-cabinet gateway shows incorrect link status for the 10BASE-T1S side of the gateway. First identified in FactoryTalk Linx version 6.50.00. [Jira 3239884]
  There is currently no workaround for this anomaly.

• FactoryTalk Linx Network Browser Port Configuration tab for the EtherNet/IP in-cabinet gateway does not shade the configuration settings when the 10BASE-T1S port is selected. First identified in FactoryTalk Linx version 6.50.00. [Jira 2315233]
  There is currently no workaround for this anomaly.

• FactoryTalk Linx Network Browser Device Locator tab for the EtherNet/IP in-cabinet gateway blocks the LED blink button and the seconds input box. First identified in FactoryTalk Linx version 6.50.00. [Jira 3230575]
  There is currently no workaround for this anomaly.

• FactoryTalk Linx does not correctly show the LLDP configuration for the Stratix 8000 devices. First identified in FactoryTalk Linx version 6.50.00. [Jira 3699322]
  To avoid this problem, review the configuration using the Stratix 8000's built-in webpage.

• FactoryTalk Linx Network Browser might stop responding if the Ethernet driver’s name is changed. First identified in FactoryTalk Linx version 6.50.00. [Jira 3699612]
  To avoid this problem, restart FactoryTalk Linx Network Browser.

• FactoryTalk Linx Network Browser permits the configuration of the LLDP transmit interval from 3601 through 32768 seconds, but these values are rejected by the device. First identified in FactoryTalk Linx version 6.50.00. [Jira 3690220]
  There is currently no workaround for this anomaly.

• FactoryTalk Linx might not detect the modification after the shortcut has changed and still gets data from the old shortcut. First identified in FactoryTalk Linx version 6.50.00. [Jira 3377218]
  To avoid this problem, restart the service or restart the computer.

• FactoryTalk Linx might incorrectly report a successful IP configuration change even though the device is unresponsive. First identified in FactoryTalk Linx version 6.50.00. [Jira 3836260]
  To avoid this problem, reconfigure the IP address when the device is online.

• The Tag Browser is unable to browse the HMI tags if the tags were browsed before enabling redundancy, followed by switching the active HMI server to another computer. First identified in FactoryTalk Linx version 6.30.00. [Jira 3837996]
  To avoid this problem, restart the computer hosting the redundant pair, and restart the computer hosting the FactoryTalk Network Directory Server.

• When accessing the FactoryTalk Linx Server Properties dialog for a previously configured server in FactoryTalk Administration Console, the “name” and “server type” settings can be modified, but the changes will be rejected or partially accepted, impacting data delivery. First identified in FactoryTalk Linx version 6.50.00. [Jira 3855757]
  To avoid this problem, do not modify the name or server type of a previously configured FactoryTalk Linx Server. If these settings need to be changed, delete the existing service and readd it and its associated shortcuts to the FactoryTalk application.

• FactoryTalk Linx is unable to receive security policies from FactoryTalk Policy Manager on Windows Server 2016. First identified in FactoryTalk Linx version 6.50.00. [Jira 3865059]
  To avoid this problem, use one of the recommended operating systems listed in the System requirements.

• 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.
  It 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 connections 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 must 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.
• When a shortcut is configured to pass through a FactoryTalk Linx Gateway Proxy Server to PLC-5 or SLC-500 controllers directly connected to Ethernet, the controller’s tags cannot be browsed, read, or written. However, tags can be accessed if the path to the PLC-5 and SLC 500 controllers is routed from EtherNet/IP across a ControlLogix chassis through a 1756-DHRIO module.
• Logix controllers support a limited number of USB CIP connections. Only one FactoryTalk Linx shortcut will be able to browse, read, or write tags from a USB-connected controller. Communications from other shortcuts to the controller will fail.
• The following array formats are not supported for ControlLogix controllers.
  • ARR[#].[#]
  • ARR.#
  • ARR.[#]
  • ARR.[#].#
  • ARR.[#].[#]
  [#] is used to reference a single item from an array. The # sign is replaced with a number indicating the array element to be accessed (note [0] is the first element).
• FactoryTalk Linx communicates with Logix controllers by storing lists of desired tags within the controller. When Studio 5000 Logix Designer is used to edit tag definitions in the controller, FactoryTalk Linx must recreate its tag list. A high number of changes can interrupt and impact FactoryTalk Linx communication performance.

• 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 must 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 must 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 that 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 that contains node address information, so different SLC or PLC controllers with the same node address can be distinguished.

• 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. It 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.

• 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.

• 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 name or use the shortcut configuration dialog to update any effected shortcuts to the correct device under the renamed driver.

• 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.

• File extensions created by Rockwell Automation software, firewall rules, and service dependences, see Rockwell Automation Knowledgebase Document ID: IN40928 - Security Software Considerations to Prevent or Mitigate Impacts to 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).

• 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 oNine device shortcuts after restarting FactoryTalk Linx data server.
  For the shortcuts which are configured to oNine devices, clients may fail to communicate to them after the FactoryTalk Linx data server is rebooted.
  To recover communications to oNine 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 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. It 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. It 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").

• To install the FactoryTalk Services Server with no user interface using the default settings during the installation process. (Silent install)
  Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Server"
• To install the FactoryTalk Services Server with English displayed during the install process and restart the computer if necessary. (Unattended install)
  Setup.exe /QS /IAcceptAllLicenseTerms /Product="FactoryTalk Services Server" /AutoRestart / SetupLanguage=ENU
• To install the FactoryTalk Services Server with FactoryTalk security policy value specified.
  Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Server" /ftsp- value="enable"
• To perform a restore of FactoryTalk Services Server during the install process.
  Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Server" /ftsp- s="global" /ftsp-bak="C:\aa.bak" /ftsp-pp="password"
• To specify the use of FactoryTalk Directory Server Services during the install process.
  Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Custom Installation" /FTSPWebAuth="Yes" /FTSPWebEventServer="Yes"
  Tip: The FactoryTalk Web Authentication Server, FactoryTalk Web Event Server, and FactoryTalk Reverse Proxy will be installed, because the FactoryTalk Reverse Proxy will be installed by default with the FactoryTalk Web Authentication Server or FactoryTalk Web Event Server.
OR
Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Custom Installation" / ReverseProxy="Yes"
Tip: The FactoryTalk Reverse Proxy will be installed.
• To specify the FactoryTalk Directory machine for FactoryTalk Services Client.
  Setup.exe /Q /IAcceptAllLicenseTerms /Product="FactoryTalk Services Client" / DirectorySever="servername"

Error codes

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

• 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