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

FactoryTalk Logix Echo has these minimum hardware requirements:

• 2.2-GHz Intel® Core i3 or faster processor:

• At least one logical core for the operating system
• At least two logical cores for the base FactoryTalk Logix Echo application
• At least one logical core per emulated controller instance; for best performance, two logical cores per emulated controller instance
• Additional logical cores dependent on additional software installed on the same workstation, server, or virtual machine

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.

• 8 GB of available memory:

• 2 GB for software applications
• 256 MB for each started emulated controller instance (up to 1 GB)

• 4 GB of available storage space
• 1-GB network adapter

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

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

• Operating system

• Windows® 10 Professional and Enterprise
• Windows 10 Enterprise 2021 LTSC (v21H2)
• Windows 11 Professional and Enterprise
• Windows Server 2022 Standard and Datacenter Editions

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

• FactoryTalk Logix Echo Service version 2.00.00
• Firmware packages
• Dashboard version 2.00.00

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

• SDK version 2.00.00

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

• FactoryTalk® Services Platform v6.31.00
• FactoryTalk® Activation v5.00.11
• FactoryTalk® Diagnostics
• FactoryTalk® Alarms and Events v6.31.00
• FactoryTalk® Linx v6.31.00

FactoryTalk® Logix Echo™ version 2.00.00 introduces these features:

• Create, modify, and delete GuardLogix 5580 emulated controllers as well as ControlLogix 5580 emulated controllers.
• Add multiple chassis to emulate multi-chassis environments.
• The FactoryTalk Logix Echo application programming interface (API)  supports 32-bit and 64-bit applications.

Project minor version changes unexpectedly when export or save the project as .L5X after uploading from an emulated controller (1048997)

When you import a project in the Logix Designer application, download the project to an emulated controller, go offline, upload the project, and save is as an .L5X file, the minor version on the project changes.

There is no workaround for this issue.

This anomaly first identified in the Logix Designer application, version 33.00.00.

Logix Designer application sometimes shuts down after a download timeout error (1166356)

When a download timeout error occurs in the Logix Designer application when downloading a project to an emulated controller, the Logix Designer application sometimes shuts down when you close the error dialog box.

This anomaly first identified in the Logix Designer application, version 33.00.00.

Download triggered through FactoryTalk Logix Echo errors with Access Denied message (1102472, 1012868)

When you install the Logix Designer application after FactoryTalk Logix Echo is installed, FactoryTalk Logix Echo does not have access to the LogixServices COM service, and the FactoryTalk Logix Echo dashboard cannot download projects to emulated controllers.

To work around this problem, follow these steps:

1. Open the Command Prompt in administrator mode.
2. Enter this command:

Tip: Replace C: with the correct drive letter if you selected a different drive when you installed FactoryTalk Logix Echo.

3. Restart the workstation.

Tip: If you do not have RemoteSigned permission in PowerShell, enter this PowerShell command: PS C:\Windows\System32> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

This anomaly first identified in the Logix Designer application, version 33.00.00.

Shutdown occurs when you cancel an upload to an emulated controller in the Logix Designer application (1094102)

In the Logix Designer application, when you begin an upload to an emulated controller and then cancel the upload, the Logix Designer application shuts down.

There is no workaround for this issue.

This anomaly first identified in the Logix Designer application, version 33.00.00.

Logix Designer application sometimes fails to download a project to an emulated controller (1151759)

In the Logix Designer application, downloading a project to an emulated controller fails when you:

Import a Sequential Function Chart (SFC) routine into a project.

Go offline and run the Build command.

To work around this problem, download the project to the emulated controller without running the Build command.

This anomaly first identified in the Logix Designer application, version 33.00.00.

Messages do not reappear when you reopen the Output pane during downloads (1162611)

When you start downloading a project, close the Output pane, and reopen it, status messages do not reappear in the pane even though the download continues and completes.

There is no workaround for this issue.

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

Error message dialog boxes sometimes appear in the wrong size (1110505)

Error message dialog boxes are sometimes sized incorrectly when the error title is long.

To work around this problem, use the scroll bar to see the complete text for the message.

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

Emulated controllers sometimes lose connection to each other (986224)

Over time, produce/consume messages between emulated controllers will have intermittent or temporary connection faults.

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

Consumed axis module faults sometimes occur between emulated controllers (971966)

Consumed axis module faults sometimes occur between emulated controllers, and the end positions of some or all axes in the base controller are not correct. When the failure occurs, the time and position camming (TCAM and PCAM) stops, and the position cams and gears stop when the consumed axis faults.

To work around this problem, make sure the workstation running the FactoryTalk Logix Echo application meets the recommended hardware requirements on page 1.

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

Virtual axes stop functioning and cause errors on various motion instructions while the emulated controller is in co-simulation mode (commanded through the API) (1246444)

In projects that produce and consume axes between a base controller and a remote controller, the virtual axes stop functioning and cause errors on various motion instructions when only one of the controllers is in co-simulation mode.

To work around this problem, re-download the project to the emulated controller.

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

Deleting an emulated controller sometimes fails when the SD card folder is open (1228345)

When you right-click an emulated controller and select View SD card, a File Explorer window opens. If you leave the window open and attempt to delete the emulated controller, an error sometimes appears, and the controller is not deleted.

To work around this problem, close the File Explorer window and then delete the emulated controller.

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

Clearing a major fault sometimes causes loss of communication with emulated controller (1209255)

When a major fault occurs on an emulated controller, you sometimes lose communication with the controller after you clear the fault.

To work around this issue, restart the controller to resume communication.

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

Major fault sometimes causes emulated controller to stop responding (1237651)

A major non-recoverable fault sometimes causes an emulated controller to stop responding.

To work around this issue, delete the controller and re-create it.

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

Emulated controller sometimes fails to respond to the Logix Designer application (1231468)

An emulated controller sometimes appears to be running normally in the FactoryTalk Logix Echo application but fails to communicate with the Logix Designer application.

To work around this issue, restart the controller to resume communication.

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

The word Explorer is not localized in Ladder Logic programming languages in the FactoryTalk Logix Echo application (1226736)

The word Explorer is not localized for the ladder logic programming language for the PTB, FRA, ITA, DEU, ESP, CHS, JPN, and KOR languages.

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

Some error messages are not translated on the Add Controller dialog box (1118671)

When you enter an invalid character or too many characters for the controller name on the Add Controller dialog box, some error messages are not translated, and only appear in English. For example, if you enter a controller name containing spaces, the error message Name must not contain spaces is not translated.

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

The FactoryTalk Logix Echo application experiences a fatal error after canceling an upload (1006799)

If you select Cancel on the upload progress dialog box, the FactoryTalk Logix Echo experiences a fatal error.

This anomaly first identified in the Logix Designer application, version 33.00.00.

CIP Error when downloading project after selecting Build Controller option (1005224)

After importing a project, selecting the Build Controller option and downloading the project to an emulated controller, the FactoryTalk Logix Echo application experiences a CIP error and the download fails.

This anomaly first identified in the Logix Designer application, version 33.00.00.

Multiple controllers sometimes lose configuration after reboot (1525297)

When you add multiple controllers to the FactoryTalk Logix Echo configuration, the controllers sometimes lose their configuration, or program, following a reboot of the host machine, or the controllers display an error: Processor not responding.

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.

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.

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.

These are the functional changes for FactoryTalk® Logix Echo™ version 2.00.00.

• Add multiple chassis to emulate multi-chassis environments.
• You can start a project download to additional controllers before the ongoing download is complete. Multiple downloads are logged into the same console log tab.
• The Firmware Packages pane lists the installed firmware packages. To install additional firmware, download it from the Rockwell Automation Product Compatibility and Download Center (PCDC) and install it using the Microsoft Windows installer.
• The Restore snapshot dialog now offers four options when you restore a snapshot:

• Restore only. This option restores the snapshot using only the chassis and controllers in the current configuration.
• Create only. This option adds new chassis and controllers without adjusting the current configuration.
• Restore and create. This option adds new chassis and controllers if necessary. The current configuration might be overwritten.
• Delete all and create. This option deletes the current configuration and creates the controllers and chassis in the snapshot.

These application notes apply to FactoryTalk® Logix Echo™ version 2.00.00.

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.

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.

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.

1. Open the Command Prompt in administrator mode.
2. Enter this command:

3. Restart the workstation.

Tip: If you do not have RemoteSigned permission in PowerShell, enter this PowerShell command: PS C:\Windows\System32> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

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

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.

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.

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.

To enable or disable the Listen on Ethernet/IP encapsulation ports setting in FactoryTalk Linx, follow these steps for all the listed drivers:

4. On the Windows Start menu, select Rockwell Software > FactoryTalk Linx Network Browser.

5. On the FactoryTalk Linx main menu, select Configure Drivers .
6. On the Configure Drivers dialog box, select a driver from the Configured Drivers list.
7. Select Edit.
8. On the Advanced tab, select Listen on Ethernet/IP encapsulation ports to enable the setting. Clear the check box to disable the setting.
9. Restart the computer.

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

• Re-run the FactoryTalk Logix Echo installer and make sure all the firmware versions are selected, or
• Download firmware from the Rockwell Automation Product Compatibility and Download Center (PCDC) and install it using the Microsoft Windows installer.

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.

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.

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.

In this release, the License Validation (LV) instruction is not fully functional. On an emulated controller you can load 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.

In this release, the Redundancy functionality is not fully functional. On an emulated controller you can load 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.

In this release, communication using sockets is not supported.

In this release, email functionality is 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.

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.

Setting the Ethernet speed and duplex settings in FactoryTalk Linx does not affect the behavior of emulated controllers.

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.

In this release, FactoryTalk Logix Echo does not support HMI Button Control (HMIBC) instructions.

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

In this release, emulated controllers gather only controller instance diagnostics and detect connection loss. Diagnostics for modules and external devices are not supported.

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 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:

• Directories used by FactoryTalk Logix Echo:

• C:\Program Files (x86)\Rockwell Software\FactoryTalk Logix Echo

Tip: Replace C: with the correct drive letter if you selected a different drive when you installed FactoryTalk Logix Echo.

• Processes used by FactoryTalk Logix Echo:

• EmulateController5580.exe
• EmulateControlLogix5580.exe
• EmulateGuardLogix5580.exe
• EmuDashboardBackend
• EmulateService

• Services used by FactoryTalk Logix Echo:

• FactoryTalk Logix Echo Message Broker
• FactoryTalk Logix Echo Service

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.

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

This 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").

These 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)

• To install the Chinese language version of the software on the D: drive and display the progress, error, or complete messages during installation and restart the computer if necessary. (Unattended install)

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