Release Notes

FactoryTalk Logix Echo Single Node
Version 3.00.00 (released 11/2023)

Catalog Number FactoryTalk Logix Echo Single Node 

These release notes describe version information for FactoryTalk Logix Echo Single Node, version 3.00.00 (released 11/2023).

Requirements

This release has the following requirements.

 
System requirements for FactoryTalk Logix Echo version 3.00.00
FactoryTalk Logix Echo works within the system requirements of all Rockwell Automation software products.

Hardware requirements
FactoryTalk Logix Echo has these minimum hardware requirements:

graphic Tip: Downloading projects simultaneously to many controllers while the system is under heavy load can cause errors. To improve simultaneous download performance, reduce the number of controllers or downloads, or add additional logical cores to the system.

 

Tip: For best performance when using FactoryTalk Logix Echo in a virtual machine, take advantage of Intel® Virtualization Technologies.
graphic


Software requirements
FactoryTalk Logix Echo requires the following software on the host computer:
FactoryTalk Logix Echo is tested on operating systems installed from original Microsoft® media only. FactoryTalk Logix Echo runs on the 64-bit versions of the following Microsoft Windows operating systems:

FactoryTalk Logix Echo is expected to operate correctly on all other editions and service packs of these operating systems but was not tested:

When you install FactoryTalk Logix Echo, these components are installed:

This component is installed if you select it on the installer:

This software is also available to install based on what is installed on the host computer:


System requirements for FactoryTalk Logix Echo version 3.00.01

FactoryTalk Logix Echo works within the system requirements of all Rockwell Automation software products.

Hardware requirements
FactoryTalk Logix Echo has these minimum hardware requirements:

graphic Tip: Downloading projects simultaneously to many controllers while the system is under heavy load can cause errors. To improve simultaneous download performance, reduce the number of controllers or downloads, or add additional logical cores to the system.
  
Tip: For best performance when using FactoryTalk Logix Echo in a virtual machine, take advantage of Intel® Virtualization Technologies.
graphic

Software requirements
FactoryTalk Logix Echo requires the following software on the host computer:
  

NOTE: This release is not intended to run on a 32-bit operating system. All operating systems listed are the 64-bit variant.
  

IMPORTANT: Keep these operating system considerations in mind:
  

FactoryTalk Logix Echo is expected to operate correctly on all other editions and service packs of these operating systems but was not tested. These operating systems are no longer supported by Microsoft and Rockwell Automation does not recommend using them:
When you install FactoryTalk Logix Echo, these components are installed:

This component is installed if you select it on the installer:

This software is also available to install based on what is installed on the host computer:
  

Features

This release includes the following system features.

System features for FactoryTalk Logix Echo version 3.00.00
FactoryTalk Logix Echo version 3.00.00 introduces these features:

Corrected Anomalies in This Release

This release corrects the following anomalies.

Deleting controllers during snapshot save can block creation of snapshots (1693247)
When the FactoryTalk Logix Echo application saves or restores a snapshot, it puts the emulated controllers in the snapshot in co-simulation mode. If you restart or delete emulated controllers during saving or restoration of a snapshot, the controllers in the snapshot are stuck in co-simulation mode, and you cannot create or restore a snapshot using those controllers.
To work around this issue, delete the controllers in the snapshot and re-add them in the FactoryTalk Logix Echo application. This anomaly first identified in the FactoryTalk Logix Echo application, version 2.01.00.
This anomaly corrected in the FactoryTalk Logix Echo application, version 3.00.
API GetDataTypeInfo API method can result in an exception (2098043)
Using API GetDataTypeInfo API method to access tags associated with Input or Output module tags results in an error. This anomaly first identified in the FactoryTalk Logix Echo application, version 2.01.00.
This anomaly corrected in the FactoryTalk Logix Echo application, version 3.00.00.
Download fails when ACD includes 5094-72IS or -IRT8S (2317915)
It is not possible to successfully download an ACD file containing a 5094-G2IS(XT) or 5094-IRT8S(XT) module to a FactoryTalk Logix Echo controller. During the download the Echo controller asserts and becomes non-responsive. To recover the Echo controller to operation it must be turned off and back on.
This anomaly first identified in the FactoryTalk Logix Echo application, version 2.01.00.
This anomaly corrected in the FactoryTalk Logix Echo application, version 3.00.00.


  

Known Anomalies in This Release

This release has the following known anomalies.

Timer structure API set unexpected results in CoSim mode (2253703)
​​Timer accumulate value does not increment from restored value when the timer structure is written to using the API when the Echo controller is in CoSim mode.
Example: Timer ACC = 1000 prior to API write to time r structure with ACC = 500. When the next one second CoSim quantum is completed the timer ACC = 2000 instead of expected 1500.
​To work around this issue, write directly to Timer ACC, which results in expected behavior in CoSim mode quantum execution.
This anomaly first identified in the FactoryTalk Logix Echo application, version 1.00.00.

 

Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

Invalid IP address blocks ability to change properties, turn controller off, or modify SD Card (1894909)

When you create an emulated controller using an ACD file or by restoring or importing a snapshot, and the IP address for the emulated controller is not valid, you cannot apply changes to some controller properties, and you cannot turn the controller off or modify the SD Card. The symptom of this anomaly is that, after you change a controller property on the controller with an invalid IP Address, the Apply button is disabled.

This error appears when you attempt to turn the controller off, attach or detach the SD card from the controller property screen, or toggle the controller on or off from the device status panel:

Modify controller failed. An error occurred when communicating with the FactoryTalk Logix Echo service. If this error occurs often, contact Rockwell Automation technical support.

However, there is no error to indicate that the IP address is not valid.

To work around this issue, enter a valid IP address for the emulated controller.

This anomaly first identified in FactoryTalk Logix Echo v1.00.


Emulated controllers sometimes shut down when program contains a motion axis (1833982)

When the program for an emulated controller contains a motion axis, the emulated controller might shut down suddenly during startup.

To work around this issue, try starting the emulated controller again.

This anomaly first identified in the FactoryTalk Logix Echo application, version 2.01.00.


IP address and network mask are not restored from the SD card (1708087)

When you save an emulated controller configuration to the emulated controller SD card, change the IP address and network mask, and then restore the configuration from the SD card, the IP address and network mask are not restored to the original configuration.

To work around this issue, use a snapshot to restore a configuration.

This anomaly first identified in the FactoryTalk Logix Echo application, version 2.01.00.


Controllers stop responding during snapshot creation (1767371)

One or more controllers might stop responding during Snapshot creation. The message Controller is not responding appears on the Device Status panel in the Dashboard for those controllers.

To work around this issue, turn the controller off and then on again, re-download the project, and attempt snapshot creation again.

This issue first identified in FactoryTalk Logix Echo version 2.01.


Delayed changes fault sometimes occurs for produced and consumed tags (1076648, 1172801)

When the Requested Packet Interval (RPI) is set to 200 ms or less for produced and consumed tags, a fault sometimes occurs that indicates a data change delay.

There is no workaround for this issue.

This anomaly first identified in the FactoryTalk Logix Echo application, version 1.00.00.


Trends display steps instead of a linear line (1093987)

Trends show steps instead of linear line while executing quantums larger than 10ms. Furthermore, some trends use physical time instead of virtual time.

This anomaly first identified in the FactoryTalk Logix Echo application, version 1.00.00.


Controller may assert when associated with a NIC other than None or Loopback address (4008295)
Controllers that have 65 or more devices configured under the emulated Controller’s front ethernet port will likely assert within one minute after a download. Workaround: Configure Echo controllers with devices under the emulated controller’s front ethernet port with a Loopback address 127.0.0.1 or ‘None’.
If communications are required over a network, the workaround configuration is dependent on the controller being emulated:
5580 controllers: Configure another Echo controller with the desired NIC in the same chassis and use it and the backplane to access the controller with the Loopback address or ‘None’.
5380 controllers in dual IP mode: Use the Loopback address or ‘None’ for the ethernet port with ethernet devices and the NIC with network connectivity for the other ethernet port.
5380 controllers in DLR/Linear mode: No workaround exists.
This anomaly first identified in FactoryTalk Logix Echo controllers configured in Logix Designer version 36.011.
  

Functional Changes

This release has the following functional changes from the previous release.


Functional changes for FactoryTalk Logix Echo version 3.00.00
These are the functional changes for FactoryTalk Logix Echo version 3.00.00.


Application Notes

This release has the following application notes.

Application notes for FactoryTalk Logix Echo version 3.00.00
These application notes apply to FactoryTalk® Logix Echo™ version 3.00.00.

Project download sometimes fails when launching a matching emulator from the Logix Designer application
In the Logix Designer application, when you try to download a project to an emulated controller that is not configured in the project, the Logix Designer application displays a dialog that offers to modify the emulated controller to match the project. For example, when you try to download a v35 ACD file to a v34 emulated controller, the Logix Designer application offers to change the v34 emulated controller into a v35 emulated controller. When you try to download a GuardLogix ACD file to a ControlLogix emulated controller, the Logix Designer application offers to change the ControlLogix emulated controller into a GuardLogix emulated controller.
However, when the Logix Designer application changes a ControlLogix emulated controller into a GuardLogix emulated controller, it always changes the emulator into a SIL2 controller without a Safety Partner. If you try to download a SIL3 ACD file to the modified emulated controller, an error message states that the project cannot be downloaded to the controller.
To work around this limitation, in the FactoryTalk Logix Echo application or in the FactoryTalk Logix Echo API, create a GuardLogix emulated controller and select Partner available to add a Safety Partner. Then you can download the SIL3 ACD file to the emulated controller from the Logix Designer application.
Projects containing locked components are not supported
In this release, FactoryTalk Logix Echo does not support projects that contain locked, or encrypted, components. In a locked component, the routine's logic is compiled into executable code and encrypted. The code is decrypted by the controller when it is ready for execution. However, emulated controllers cannot decrypt the logic, so Logix Designer does not allow encrypted components to be downloaded to an emulated controller.
Update permissions for the LogixServices COM service
When you install FactoryTalk Logix Echo on a workstation on which the Logix Designer application is already installed, FactoryTalk Logix Echo updates permissions to allow downloads to an emulated controller using the LogixServices COM service.
However, if you install the Logix Designer application after FactoryTalk Logix Echo is installed, FactoryTalk Logix Echo does not have access to the LogixServices COM service. You need to update the permissions using the LogixEchoSystemConfigurationUtility.ps1 script or the Component Services management tool.

To use the LogixEchoSystemConfigurationUtility.ps1 script to update permissions
  1. Open the Command Prompt in administrator mode.
  2. Enter this command:

PowerShell -File "C:\Program Files (x86)\Rockwell Software\FactoryTalk Logix Echo\Scripts\LogixEchoSystemConfigurationUtility.ps1"

Restart the workstation.

graphic Tip: If you do not have RemoteSigned permission in PowerShell, enter this PowerShell command:


PS C:\Windows\System32> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

Snapshots and crash log data are not protected
The contents of snapshots and crash log data files are not protected and could reveal project information.

Saved and restored snapshot does not execute custom power-up routines and flags
When you restore a snapshot, custom power-up routines and flags that are configured to execute on pre-scan or first scan are not called or set. The controller resumes execution from the point in a routine when the snapshot was created.
Motion Planner does not continue when a snapshot is restored
The in-flight motion system is not fully supported when using snapshots. When you restore a snapshot, the Motion Planner does not resume motion in the same position that was captured in the snapshot. To restart motion after restoring a snapshot, you might need to trigger user application code that resets or restarts motion.
Turn off the Listen on Ethernet/IP encapsulation ports setting in FactoryTalk Linx
Both FactoryTalk Logix Echo and the Listen on Ethernet/IP encapsulation ports setting, enabled by default in FactoryTalk Linx , use port 44818. To prevent a port conflict with FactoryTalk Linx , you must turn off the Listen on Ethernet/IP encapsulation ports setting in FactoryTalk Linx .


IMPORTANT: When you turn off the Listen on Ethernet/IP encapsulation ports setting in FactoryTalk Linx , other applications that rely on FactoryTalk Linx might not work as expected.


To enable or disable the Listen on Ethernet/IP encapsulation ports setting in FactoryTalk Linx , follow these steps for all the listed drivers:
  1. On the Windows Start menu, select Rockwell Software > FactoryTalk Linx Network Browser.
  2. On the FactoryTalk Linx main menu, select Configure Drivers.
  3. On the Configure Drivers dialog box, select a driver from the Configured Drivers list.
  4. Select Edit.
  5. On the Advanced tab, select Listen on Ethernet/IP encapsulation ports to enable the setting. Clear the check box to disable the setting.
  6. Restart the computer.

Reinstalling firmware after it has been uninstalled
If the firmware package for emulated controllers is deleted, you can reinstall it using one of these methods:

Additional time is sometimes required when switching between downloading an .ACD file to physical and emulated controllers
For large .ACD files, the first download can take several minutes longer than subsequent downloads when you switch from downloading to a physical controller to downloading to an emulated controller, or vice versa. Each time the Logix Designer application or FactoryTalk Logix Echo downloads an .ACD file to a different controller type than the previous download operation, the .ACD file must be re-built for the target controller type.
License server can delay creation or startup of an emulated controller

When you start or add emulated controllers when no other controllers are running, you might need to wait several minutes for the license server to respond, especially if the server is busy or you are adding several controllers at once. After at least one controller has acquired a license and is running, subsequent creation or startup operations should complete in a normal time frame.
Delayed changes fault sometimes occurs for produced and consumed tags

When the Requested Packet Interval (RPI) is set to 200 ms or less for produced and consumed tags, a fault sometimes occurs that indicates a data change delay. You can ignore this fault.
Logix Designer can assign IP addresses that are not valid in FactoryTalk Logix Echo
When you use the Logix Designer application to assign an IP address to an emulated controller, the application allows you to assign an IP address that is not valid in FactoryTalk Logix Echo. When you access the emulated controller in FactoryTalk Logix Echo, the address is marked invalid. To correct it, change the IP address back to a valid address in FactoryTalk Logix Echo.
Address Space Layout Randomization (ASLR) sometimes prevents controller initialization
A Microsoft Windows security feature, Address Space Layout Randomization (ASLR), sometimes prevents an emulated controller from aligning memory space. This can prevent the emulated controller from initializing. If this problem occurs, check the FactoryTalk Diagnostics Viewer for additional information. Restarting the computer that runs FactoryTalk Logix Echo should fix the problem. If not, please contact Rockwell Automation Technical Support.
License Validation (LV) instruction partially functional
In this release, the License Validation (LV) instruction is not fully functional. On an emulated controller you can download a project that contains an LV instruction, but the instruction does not validate the provided license number. On the emulated controller, the instruction always returns a true result for both valid and invalid licenses.
Redundancy partially functional
In this release, the Redundancy functionality is not fully functional. On an emulated controller you can download a project with Redundancy selected. Redundancy is the use of two or more controllers, each carrying out the same function, to improve reliability or availability. The high availability (HA) status reports success, but the synchronization with the second controller and support of sync modules is not available. The emulated controller operates only as a primary controller.


NOTE: The emulated scan time will not reflect actual performance of redundancy in physical controllers.


Communication over sockets not supported
In this release, communication using sockets is not supported.

Email functionality not supported
In this release, email functionality is not supported.

CIP Class 3 outgoing communications not supported
In this release, FactoryTalk Logix Echo does not support outgoing CIP Class 3 communication over Ethernet. This restriction prevents FactoryTalk Logix Echo from communicating with physical devices such as controllers, IO devices, and HMI panels. However, the application accepts incoming CIP Class 3 connections.
CIP Class 0/1 communications not supported
In this release, FactoryTalk Logix Echo does not support CIP Class 0/1 communication over Ethernet with physical devices. This restriction prevents FactoryTalk Logix Echo from communicating with physical devices such as controllers, IO devices, and HMI panels. However, the application does support Class 0/1 communication over Ethernet and the emulated backplane between multiple emulated controllers.
FactoryTalk Linx Ethernet speed and duplex settings do not affect emulated controllers
Setting the Ethernet speed and duplex settings in FactoryTalk Linx does not affect the behavior of emulated controllers.

WebServer and WebPage functionality not supported
In this release, FactoryTalk Logix Echo does not support WebServer and WebPage functionality for emulated controllers. If you browse to the IP address of an emulated controller, a WebPage does not appear.
HMIBC instructions are not supported
In this release, FactoryTalk Logix Echo does not support HMI Button Control (HMIBC) instructions.

Module discovery not supported
In this release, FactoryTalk Logix Echo does not support module discovery.

Limited support for Automatic Diagnostics
In this release, emulated controllers gather only controller instance diagnostics and detect connection loss. Diagnostics for modules and external devices are not supported.
Local support for GSV and SSV instructions
FactoryTalk Logix Echo supports Get System Value (GSV) and Set System Value (SSV) instructions for emulated controller instances only. When GSV and SSV instructions target external objects, the instructions return the result for an unconnected device.
Anti-virus software and nats-server.exe
Anti-virus software may quarantine the nats-server.exe file during installation due to false-positive virus detection. Depending on how your anti-virus software operates, you may need to add the following to your anti-virus exception list:
Tip: Replace C: with the correct drive letter if you selected a different drive when you installed FactoryTalk Logix Echo.
graphic

  

Uninstall firmware packages before uninstalling FactoryTalk Logix Echo
Before you uninstall the FactoryTalk Logix Echo application, first uninstall all firmware packages. Uninstalling the FactoryTalk Logix Echo application without uninstalling the firmware packages generates an error.

Unattended or silent install

Unattended or silent install
Use command-line parameters to perform an unattended or silent installation of the software.Installation Command-line parametersThis 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").

 

/?
Displays the usage options for installation parameters.
/Q
Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation using an IT tool or script, and don’t expect any error or restart messages. When using this parameter, check the error codes, and respond as needed. For example, if the installation returns error code
1641, then the IT tool or script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS is not specified.
/QS
Unattended Install, install runs in a quiet simple mode and shows progress through the UI, it does not accept any input but still shows error or restart messages.
When using this parameter, the installation will stop and display a prompt if there are error or restart messages. For example, if an immediate restart is required to complete the install, a restart message will be displayed to confirm the restart. Installation resumes automatically from the point of interruption after restart.
This parameter is required if /Q is not specified.
/IAcceptAllLicenseTerms
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
/AutoRestart
Automatically restarts the computer after the installation is complete. Used when a restart is required to complete the installation.
This parameter is optional. If this parameter is not used silent install (/Q) will return either error code 1641 or 3010 if a restart is required, and unattended install (/QS) will result in a
confirmation prompt that must be agreed to before the installation is completed.
/Record
Records the installation options chosen to a recording file.
This parameter is optional.
/Playback="value"
Plays back a recording file to specify the installation options.
This parameter is optional.
/Repair
Runs a repair operation on the installed products.
This parameter is optional.
/SetupLanguage="value"
Specifies which language is displayed during install process. The value must be the one of these:
  • ENU
  • CHS
  • DEU
 
  • ESP
  • FRA
  • ITA
  • JPN
  • KOR
  • PTB
This parameter is optional. If this parameter is not used, the default language is the current user or operating system user interface language.
/Product="value"
Specifies which sub-products will be installed.
Only required if sub-products are included with the install package.
If the software does not include sub-products this parameter is not available.
/IgnoreWarning
Specifies that the setup ignores warnings and continues.
This parameter is optional. If it is not specified, the setup exits when a warning occurs.
/SerialNumber="value"
Specifies the serial number of the software being installed. This is used to activate the software during installation.
This parameter is optional. If it is not specified the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required this parameter is not
available.
/ProductKey="value"
Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified the software must be activated manually after installation if activation is required.
Some software does not require activation. If activation is not required this parameter is not
available.
/Version="value"
Specifies the version of the software to activate which corresponds to the product version associated with the SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer uses the most recent product version available.
Some software does not require activation. If activation is not required this parameter is not
available.

Examples
These examples show how to use the installation commands.
Setup.exe /Q /IAcceptAllLicenseTerms
Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS

Error codes
This table identifies the error codes that can be returned by an installation.
  
ERROR_SUCCESS
0
The installation completed successfully.

 

ERROR_INVALID_PARAMETER
87
One of the parameters was invalid.
ERROR_INSTALL_USEREXIT
1602
The installation was cancelled by the user.
ERROR_INSTALL_FAILURE
1603
A fatal error occurred during installation.
ERROR_BAD_CONFIGURATION
1610
The configuration data for this product is corrupt. Contact
your support personnel.
ERROR_REBOOT_CONTINUE
1641
A restart is required to continue to installation.
ERROR_SUCCESS_REBOOT_REQUIRED
3010
A restart is required to complete the installation. After restart
the product is successfully installed.
ERROR_REBOOT_PENDING
3012
A restart is pending and is required before the installation can
continue.
ERROR_SUCCESS_NOT_APPLICABLE
3013
The installation cannot proceed because the products are
already installed.


  
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.