FactoryTalk Logix Echo is Rockwell Automation software that emulates Logix controllers on a PC, so a Logix Designer project can be run and debugged without the controller hardware. It is a good place to find logic and HMI mistakes before the factory acceptance test (FAT), but the emulated controller is not the real one: I/O, timing, redundancy, the network and safety behave differently. This article follows Rockwell's FactoryTalk Logix Echo Getting Results Guide, publication
1. What FactoryTalk Logix Echo emulates
Logix Echo emulates the behaviour of five controller families, each from a minimum Logix Designer version (p. 6):
| Controller | Logix Designer version |
|---|---|
| ControlLogix 5590, including process controllers and the PlantPAx built-in instructions | 38 and later |
| ControlLogix 5580, including process controllers and the PlantPAx built-in instructions | 33 and later |
| GuardLogix 5580 | 35 and later |
| CompactLogix 5380 | 36 and later |
| Compact GuardLogix 5380 | 36 and later |
An emulated controller accepts project files of the same family: the guide's example is a
Rockwell's first warning is that Logix Echo must not control physical machines, devices or processes. To help prevent it, the software blocks outgoing CIP Class 3 and Class 0/1 communication through the Ethernet port (p. 6, p. 22).
2. Getting a project onto an emulated controller
A project from Logix Designer version 33.00 or later needs no change to run on a 5580 or 5380 emulated controller: there is no need to use Change Controller, and the controller organizer, including the I/O configuration, is kept (p. 6). When Logix Designer is connected to an emulated controller, its dialog title bars show [Emulator] (p. 6).
- Adding a controller. A controller is added by entering its settings or from an existing .acd file, which fills the settings in (p. 13). Type, chassis, slot, IP address and firmware revision are chosen when it is added; the revision cannot be changed later (p. 14–15).
- Firmware. Firmware for emulated controllers is installed with Logix Echo, and Rockwell recommends installing every supported version. More can be added by running the installer again or from the Product Compatibility and Download Center (PCDC) (p. 20). Updating a real controller is a separate task: ControlLogix and CompactLogix firmware update.
- Downloading. The project downloads over the emulated Ethernet port. Downloading through Logix Echo's own Download pane, which can send one .acd file to several controllers, needs Logix Designer on the same computer (p. 6, p. 16).
- IP addresses. A controller can use a loopback address (127.0.0.1 by default) or an address configured on the PC's network card. With a loopback address, other controllers cannot exchange produced and consumed data with it; addresses configured in Windows allow downloads from other workstations and produce/consume with other controllers. One controller on each chassis must have an IP address (p. 17).
- Several chassis. Chassis can be added for ControlLogix 5580, GuardLogix 5580 and ControlLogix 5590 controllers, with no set limit on their number (p. 18).
3. Connecting the HMI
Emulated controllers talk to HMI and other CIP-based applications with Class 3 (message) communication over EtherNet/IP, or through a controller-to-controller bridge over the emulated backplane to EtherNet/IP (p. 20). The HMI can run on the same PC or on another computer on the network (p. 20–21). Emulated controllers talk to each other by produce/consume or by messages (p. 21), and controller messaging works only to local emulated controllers (p. 22).
Two points from the guide come up on every HMI test:
- Port 44818. Logix Echo and the FactoryTalk Linx setting Listen on EtherNet/IP encapsulation ports both use port 44818. To avoid the conflict, that setting must be turned off in FactoryTalk Linx, and Rockwell warns that other applications that rely on FactoryTalk Linx might then not work as expected (p. 13). When the HMI does not see the controller, the general checks are in RSLinx or FactoryTalk Linx cannot see the controller.
- HMIBC. HMI Button Control instructions are not supported on an emulated controller (p. 9).
In our practice, the HMI tests that make sense on Logix Echo are screen navigation, faceplates and popups, alarms raised by logic conditions, and the binding of every display object to the right tag. Which HMI product fits a project: FactoryTalk View SE, ME and Optix.
4. Simulating I/O and time
An emulated controller cannot control physical I/O or connect to a physical device (p. 7). When a project runs, most I/O modules in the I/O configuration tree are faulted; only produce/consume tag connections between emulated controllers work as expected (p. 9). Module discovery is not supported, and serial number matching is ignored (p. 9). Diagnostics are limited to the controller instance and connection loss, with none for modules or external devices (p. 8). The I/O fault codes a real system shows are covered in ControlLogix I/O module fault 16#0204, 16#0203.
Input and output values are simulated through the Logix Echo API, and they can be overwritten (p. 22). Logix Echo 4.0 and later supports C# and Python for the API, which works fully only with Logix Designer 33.00 or later on the same computer (p. 24). The Controller API reads and writes single or multiple tags, and its co-simulation mode controls time execution (p. 33).
Time is virtual. In free-running mode, the default, the virtual clock follows the Windows clock within a few milliseconds; in co-simulation mode the API controls the flow of time, the fidelity of continuous tasks and the synchronisation of emulated controllers (p. 23). Trend time stamps use virtual time, and time scaling is supported through the API (p. 9). Motion instructions run on virtual axes (Logix Designer 33.00 and later) and on CIP axes in Axis Test Mode (Logix Designer 35.00 and later with Logix Echo 2.01 and later) (p. 7).
Snapshots save the settings of one or more controllers and can be restored, exported to an .echo-snap file and imported on another workstation (p. 25–27). Restoring purges the user projects from the controllers, sets the controller wall clock time to the snapshot time, and can make messages that were executing return an error (p. 25).
5. What Logix Echo can check and what waits for FAT
The guide is explicit that an emulated controller must not be relied on to match the performance or operation of a physical one: instruction and program execution times can differ (p. 7), and displayed scan times will differ from those on physical controllers (p. 23).
| Item | On FactoryTalk Logix Echo | Needs the real hardware |
|---|---|---|
| Logic and sequences | Runs the project unchanged (p. 6) | Final run on the real controller and firmware |
| I/O | Values simulated or overwritten through the API; most I/O modules faulted (p. 9, p. 22) | I/O modules, field wiring, module and device diagnostics (p. 8) |
| Timing | Execution and scan times differ (p. 7, p. 23) | Scan and execution time measured on the controller |
| Redundancy | Runs only as primary; the high availability (HA) status reports success but there is no synchronisation with a second controller and no sync modules; scan time does not reflect redundancy (p. 9) | Every switchover test on two real chassis: ControlLogix redundancy pre-FAT checklist |
| DLR ring | Not supported; the Linear/DLR setting on a 5380 only puts both ports on one network as a single node (p. 10–11) | Ring tests on the real switches and adapters: DLR or PRP |
| Other network functions | OPC UA, the socket interface, QoS, SNMP, controller web pages and email not supported; the Ethernet port is always enabled (p. 8–9, p. 18, p. 22) | Tested on the real controller and network |
| GuardLogix safety | The safety partner's presence is emulated but it is not operational; no cross checks or cross loading; safety I/O tags are not put in the Safe State when inhibited or faulted and can be overwritten (p. 8) | All safety functions on the real controller, safety partner and safety I/O: GuardLogix safety program |
| Motion | Virtual axes and CIP axes in Axis Test Mode only (p. 7–8) | Real drives and axes |
For a GuardLogix project, Logix Echo can generate an imitated safety signature that is used only for the emulation and cannot be used on a physical controller (p. 7). Logix Echo therefore does not validate a safety function; it lets the safety routines run against simulated safety I/O values (p. 8) before the real hardware is available.
6. Security and intellectual property
Logix Echo supports only a subset of the security features of a physical controller, and Rockwell recommends reviewing account access (p. 12):
- License-Based Source Protection is not supported; it must be removed from the project to emulate the controller (p. 7, p. 12).
- The License Validation (LV) instruction does not validate the licence number and always returns true (p. 12).
- Snapshots and crash log files are not protected and might reveal project information; project content on the virtual SD card is not encrypted or digitally signed (p. 12). Fault dumps are stored in the virtual SD card folder even when the card is detached (p. 9, p. 19).
A PC running Logix Echo, and every snapshot file, should therefore be handled like the project files themselves. FactoryTalk Logix Echo is also among the products listed in Rockwell security advisory SD1707: see the Rockwell CVE tracker. Securing the real controllers: CIP Security.
What we check first
This is TDL's practice, not a Rockwell Automation requirement.
- On current Rockwell Logix projects, we run the logic on FactoryTalk Logix Echo before FAT, and connect the HMI to the emulated controllers when the project has one.
- That the project's controller type and Logix Designer version match an emulated type in the table in section 1; if they do not, the logic waits for the real controller.
- That License-Based Source Protection is removed from the test copy only, never from the delivered project.
- An I/O simulation list agreed before the test: which inputs are driven through the API, and from which values.
- That every item in the table in section 5 is written into the FAT procedure for the real hardware.
- That the tested project version is stored with its Logix Designer and firmware revisions: Logix version control and backup.
How TDL approaches it
TDL Industrial Automation is a System Integrator in the Rockwell Automation PartnerNetwork. Programming and the FAT are steps 6 and 7 of how a TDL control system project runs. More: Rockwell Automation system integrator in Vietnam.
Frequently asked questions
Which controllers can FactoryTalk Logix Echo emulate?
ControlLogix 5590 from Logix Designer 38, ControlLogix 5580 from 33, GuardLogix 5580 from 35, and CompactLogix 5380 and Compact GuardLogix 5380 from 36, according to Rockwell's guide
Can an HMI connect to FactoryTalk Logix Echo?
Yes. Emulated controllers communicate with HMI and CIP-based applications using Class 3 messages over EtherNet/IP, locally or from another computer. The FactoryTalk Linx setting that listens on EtherNet/IP encapsulation ports must be turned off to avoid a conflict on port 44818, and HMIBC instructions are not supported.
Can Logix Echo test ControlLogix redundancy?
No. The emulated controller runs only as a primary. The high availability status reports success, but there is no synchronisation with a second controller and no sync modules, and the scan time does not reflect redundancy. Switchover tests need the two real chassis.
Can Logix Echo validate a GuardLogix safety program?
No. The safety partner's presence is emulated but it is not operational, cross checks are not supported, and safety I/O tags are not put in the Safe State. The imitated safety signature is only for emulation. Safety functions are tested on the real controller and safety I/O.
Does Logix Echo support License-Based Source Protection?
No. Rockwell's guide says source protection by licence must be removed from the project to emulate the controller, and the License Validation instruction always returns true on an emulated controller. Snapshots and crash logs are not protected, so they should be stored like project files.
Sources
- Rockwell Automation,
9310-GR001D-EN-P , FactoryTalk Logix Echo Getting Results Guide, 10/2025 — pp. 6–27, 33
Read 22 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system. Links open the latest edition in Rockwell's literature library; page numbers refer to the edition cited.