Factorytalk Logix Echo Getting Results Guide
Factorytalk Logix Echo Getting Results Guide
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.
Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash
will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and
for Personal Protective Equipment (PPE).
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.
Chapter 1
Overview FactoryTalk Logix Echo ............................................................................... 7
Emulated controllers ............................................................................. 7
Differences between emulated controllers and physical controllers 8
Navigate FactoryTalk Logix Echo panes.............................................10
Controller pane settings ................................................................10
Device Status pane settings .......................................................... 11
Security considerations ....................................................................... 11
Chapter 2
Use an emulated controller Turn off the Listen on Ethernet/IP encapsulation ports setting in
FactoryTalk Linx..........................................................................................13
Add an emulated controller ....................................................................... 13
Delete a controller ...................................................................................... 15
Modify a controller ..................................................................................... 15
Download .acd files to emulated controllers ............................................ 16
IP Addresses for emulated controllers...................................................... 17
Add and manage multiple chassis............................................................. 18
Add a chassis......................................................................................... 18
Delete a chassis..................................................................................... 18
Modify a chassis ................................................................................... 18
Use SD Cards in emulated controllers ...................................................... 19
Attach an SD Card to a controller ....................................................... 19
Manage emulated controller firmware.................................................... 20
Communicating with emulated controllers ............................................ 20
Communication considerations ........................................................ 22
Virtual time on emulated controllers........................................................23
Export the results of an operation ........................................................... 24
Use the API ................................................................................................. 24
Chapter 3
Use controller snapshots Use controller snapshots ........................................................................... 27
Add a snapshot ..................................................................................... 27
Edit a snapshot .................................................................................... 28
Restore a snapshot .............................................................................. 28
Export a snapshot ............................................................................... 29
Import a snapshot ............................................................................... 29
Chapter 4
Troubleshooting emulated Troubleshooting emulated controllers ......................................................31
controllers Generate data files using the problem-report-collector script ..........31
Change port numbers to correct a port conflict ................................ 32
Change the port number for a WebSocket connection ..............32
Change the port number for a GraphQL connection .................. 33
Change the service API port number ........................................... 34
Update permissions for the LogixServices COM service ............ 35
Appendix A
FactoryTalk Logix Echo SDK SDK Documentation kit and NuGet package .......................................... 37
API functions.............................................................................................. 37
Legal Notices Rockwell Automation publishes legal notices, such as privacy policies, license
agreements, trademark disclosures, and other terms and conditions on the
Legal Notices page of the Rockwell Automation website.
Overview
FactoryTalk Logix Echo FactoryTalk® Logix Echo™ is a software application that emulates the behavior
of ControlLogix® 5580 and GuardLogix® 5580 controllers. Use FactoryTalk
Logix Echo to test, debug and optimize application code without physical
hardware. Additionally, connect to HMI and other simulation software to
create a comprehensive digital twin of your process or machine.
Emulated controllers To emulate ControlLogix 5580 controllers, including process controllers and
all PlantPAx® built-in instructions, use FactoryTalk Logix Echo to help create
an emulated instance of the controller, versions 33 or later. To emulate
GuardLogix 5580 controllers, use FactoryTalk Logix Echo to help create an
emulated instance of the controller, versions 35 or later. You can continue to
use Studio 5000 Logix Emulate software to emulate the ControlLogix 5570
family of controllers.
The Studio 5000® Logix Designer project file can be downloaded directly to
the emulated controller over the emulated controller Ethernet port when a
compatible version of the Logix Designer application is installed on the same
PC. In the Logix Designer application, the dialog box title bars display
[Emulator] when connected to an emulated controller.
ControlLogix and GuardLogix 5580 emulated controllers are compatible with
project files belonging to the same family of controllers. For example, you can
download a 1756-L85E project file to a 5580 emulated controller. To use the
5580 emulated controller, create projects in the Logix Designer application for
ControlLogix 5580 controllers.
IMPORTANT Do not use FactoryTalk Logix Echo to control physical machines, devices, or
processes. The application blocks outgoing CIP Class 3 communication and Class 0/1
communications through the Ethernet port to help prevent control of physical
devices.
See also
Differences between emulated controllers and physical controllers on
page 8
Differences between Some functionality of emulated controllers differs from the functionality of
physical controllers.
emulated controllers and
IMPORTANT Do not depend on the emulated controller to match the performance or operation of
physical controllers the physical controller. Execution times for instructions and programs might be
different in an emulated controller compared to a physical controller.
See also
Security considerations on page 11
Communication considerations on page 22
Virtual time on emulated controllers on page 23
Navigate FactoryTalk Logix Use the FactoryTalk Logix Echo panes to view and configure emulated
controllers.
Echo panes
• The Devices pane provides controls to create emulated controllers and
lists the emulated controllers configured in your system.
• The Controller pane displays settings for the selected controller.
• The Device Status pane displays the status for each emulated
controller and provides controls to modify the keyswitch position and
turn the controller instance on or off.
See also
Controller pane settings on page 10
Device Status pane settings on page 11
Controller pane settings Use the Controller pane to view controller attributes and edit controller
settings. This table describes the attributes and settings on the Controller
pane.
Setting Description
Vendor The manufacturer of the emulated controller. For most controllers, the
vendor is Rockwell Automation/Allen Bradley. This setting is applied when
the controller is added and cannot be changed.
Type The emulated controller type, such as a ControlLogix 5580. This setting is
applied when the controller is added and cannot be changed.
Revision The firmware revision for the emulated controller. This setting is applied
when the controller is added and cannot be changed.
Name The emulated controller name. Contains up to 40 characters and must
begin with a letter or an underscore.
Description A brief description of the emulated controller.
IP Address The IP address assigned to the emulated controller.
ACD Path The project path for the emulated controller's .acd files. An ACD path might
look like this: C:\Users\jsmith\Documents\Studio5000\Projects\Emulated
Chassis The name of the chassis that contains the emulated controller.
Slot The slot number for the emulated controller. Not displayed for controllers
that are not chassis-based.
Controller Instance Turns the emulated controller on or off. When a controller is On, the
emulated controller executable is launched and is running. When a
controller is in the Off state, the controller configuration is saved but the
emulated controller executable is not launched.
Tip: To restart an emulated controller, turn off the controller and then turn
it on.
SD Card Indicates whether an SD card is attached to the emulated controller.
See also
Add an emulated controller on page 13
Device Status pane settings Select Device Status to display the Device Status pane.
This table describes the status settings.
Setting Description
Controller name and on-off switch Use the on-off switch beside the controller name to
enable or disable the controller.
Mode Select Run, Remote, or Program for the controller mode.
Status The Run and OK status lights are green when the
controller is in Run mode and is not in a faulted state. The
OK light is red when there is a controller fault.
Fault messages When a controller fault occurs, an error message appears
under the Status lights.
See also
Navigate FactoryTalk Logix Echo panes on page 10
Security considerations Keep these security considerations in mind when using FactoryTalk Logix
Echo.
IMPORTANT FactoryTalk Logix Echo supports a subset of the security features that are available
in physical controllers to help protect intellectual property in controller projects.
Rockwell Automation recommends you review account access to limit the risk of
exposing sensitive information in your projects.
See also
Differences between emulated controllers and physical controllers on
page 8
Communication considerations on page 22
Turn off the Listen on Both FactoryTalk Logix Echo and the Listen on Ethernet/IP encapsulation
ports setting, enabled by default in FactoryTalk® Linx, use port 44818. To
Ethernet/IP encapsulation prevent a port conflict with FactoryTalk Linx, you must turn off the Listen on
ports setting in FactoryTalk Ethernet/IP encapsulation ports setting in FactoryTalk Linx.
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.
Add an emulated controller Add a controller to create an emulated controller in FactoryTalk Logix Echo.
Configure the settings for an emulated controller when adding it. Modify the
controller settings at any time.
You can add a controller by entering controller settings, or you can select an
existing .acd file to automatically populate the controller settings.
To add a controller
1. In Devices, right-click the chassis where you want to add the
controller.
2. Select Add Controller.
To add a controller from an existing .acd file, select Add controller
from ACD. When you add a controller from an .acd file, the controller
properties are read-only.
3. In the Add Controller dialog box, configure these controller settings.
The settings are populated if you added the controller using an .acd
file.
See also
Delete a controller on page 15
Modify a controller on page 15
IP addresses for emulated controllers on page 17
To delete a controller
1. Complete one of these actions to delete a controller:
• From the Devices explorer, right-click the controller and select
Delete.
• From the Devices explorer, double-click the controller. In the
General view for the controller, select Delete.
2. When prompted, select Yes to delete the controller permanently.
See also
Add a controller on page 13
Modify a controller on page 15
Modify a controller Modify an emulated controller in the Controller pane. Modifications made to
the Controller Instance or SD Card properties take immediate effect.
Tip: You can configure the revision number for the emulated controller only when you add a
controller.
To modify a controller
1. In the Devices pane, double-click the controller.
The controller settings appear in the Controller pane.
2. Modify these properties:
• Name. The name can contain up to 40 characters.
• ACD Path. Defines the location of the .acd project file. Select
Browse to add or modify the project file associated with the
emulated controller.
• Description. An optional description of the emulated controller. The
description can contain up to 10,240 characters.
• Chassis Name. The emulated chassis that hosts the controller.
• IP Address. The IP address used to communicate with the emulated
controller. Select an address from the list of available IP addresses.
Tip: Use the General Properties pane of the emulated controller to change the IP
address to any of the supported loopback addresses (127.x.x.x).
• Slot. The chassis slot in which the controller resides. Each controller
in FactoryTalk Logix Echo must have a unique slot number.
• Controller Instance. Determines whether the emulated controller is
in the On or Off state. When the emulated controller is in the On
state, FactoryTalk Logix Echo emulates running the controller code.
See also
Add a controller on page 13
Delete a controller on page 15
IP addresses for emulated controllers on page 17
Download .acd files to Use the Download pane to download an .acd project file to an emulated
controller or to multiple emulated controllers.
emulated controllers
Note: To download an .acd file to an emulated controller, the Logix Designer application must be
installed on the same computer as FactoryTalk Logix Echo.
See also
Navigate FactoryTalk Logix Echo panes on page 10
IP Addresses for emulated You assign an IP address to an emulated controller when you add it in a
chassis. The IP address menu lists available addresses from these sources:
controllers
• The loopback address, reserved in Windows for testing. By default,
FactoryTalk Logix Echo allows you to assign 127.0.0.1 from the IP
address menu. Use the General Properties pane of the controller to
change the IP address to any of the supported loopback addresses
(127.x.x.x).
The main limitation of the loopback address is that the Logix Designer
application does not allow communication to loopback IP addresses.
For example, other controllers cannot share produce-and-consume
data with an emulated controller that uses a loopback address.
• IP addresses configured in Windows. If you have administrator
privileges on your workstation, you can add IP addresses to your
workstation's Ethernet card using the Advanced TCP/IP dialog box in
Windows. The Logix Designer application allows communication to
these addresses across a network, allowing program downloads from
other workstations and produce-and-consume data sharing with other
controllers.
Keep these considerations in mind when assigning IP addresses for emulated
controllers:
• You can configure an emulated controller with no IP address.
Workstations can download programs to the controller across the
emulated backplane through another controller with a valid IP
address.
Note: One emulated controller on each chassis must have an IP address. If none of the
controllers has an IP address, the controllers on that chassis can be online but cannot
receive project downloads and cannot carry out Logix Designer operations.
• You can assign the same IP address to more than one emulated
controller. Use duplicate IP addresses on multiple emulated controllers
to test a project on a variety of controllers and configurations without
re-configuring an IP address for each test. The emulated controller
that you start first can communicate over IP; other emulated
controllers with the same IP address cannot communicate.
• The Ethernet port on an emulated controller is always enabled, even if
it has been disabled in the Logix Designer application.
• Emulated controllers do not support the Quality of Service (QoS)
protocol.
See also
Add an emulated controller on page 13
Modify a controller on page 15
Communication considerations on page 22
Add and manage multiple Add chassis to the FactoryTalk Logix Echo configuration to emulate a
multi-chassis system.
chassis
One chassis, named Chassis, is included in the configuration by default. Each
chassis that you add must have a unique name. There is no set limit to the
number of chassis you can add.
To add a chassis
1. Right-click in Devices and select Add chassis.
2. In Add Chassis, enter a name for the chassis by using up to 40 valid
characters. The name must be different from the names of existing
chassis.
3. (Optional) Enter a chassis description by using up to 10,240 characters.
4. Select Add. The new chassis appears in Devices.
To delete a chassis
• In Devices, right-click the chassis and select Delete.
If controllers are associated with the chassis, a dialog box states that
the associated controllers will be deleted with the chassis.
Modify a chassis Edit the name and description of a chassis.
To modify a chassis
1. In Devices, right-click the chassis.
The chassis properties appear in Edit Chassis.
2. Modify these properties:
• Name. The name can contain up to 40 characters and must be
unique.
• Description. An optional description of the chassis. The description
can contain up to 10,240 characters.
Use SD Cards in emulated Attach a virtual Secure Digital (SD) card to an emulated controller to simulate
the use of an SD card. A folder on your computer functions as the SD card
controllers repository. You can create, write, delete, or modify files in the virtual SD card
directory just as you would with a physical SD card.
To view the virtual SD card contents, right-click the controller in the Devices
pane and select View SD card. Browse to the simulated location of the SD
card.
Tip: The time required to communicate with the virtual SD card might vary from the
communication time required for physical SD cards.
See also
Attach an SD card to a controller on page 19
Manage emulated controller Firmware for emulated controllers is installed when you install FactoryTalk
firmware Logix Echo. Rockwell Automation recommends that you install all the
supported firmware versions in case you need them.
In FactoryTalk Logix Echo, the Firmware Packages pane lists the installed
firmware packages. To install additional firmware, follow one of these steps:
• 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.
See also
Use the API on page 24
Communicating with Emulated controllers communicate over Ethernet and across the emulated
backplane. You can connect with an emulated controller locally or remotely.
emulated controllers Emulated controllers communicate with the Logix Designer application, with
other emulated controllers, and with HMI and CIP-based applications.
See also
Communication considerations on page 22
See also
Differences between emulated controllers and physical controllers on
page 8
Security considerations on page 11
Use the API on page 24
Virtual time on emulated FactoryTalk Logix Echo relies on a virtual clock to indicate the passage of time
on emulated controllers. Virtual time on an emulated controller runs in two
controllers modes:
• Free-running mode, which is a close approximation to the time on
your workstation. In this mode, FactoryTalk Logix Echo compares the
virtual time to the Windows time available on your computer and
adjusts to match the Windows clock within a few milliseconds. When
an emulated controller is on, its time elapses in free-running mode by
default.
• Co-simulation mode, which you control through the FactoryTalk Logix
Echo API on page 24. In this mode, you control the virtual time:
• Control the flow of virtual time.
• Adjust the fidelity of continuous tasks.
• Synchronize emulated controllers.
Keep these virtual time considerations in mind:
• On emulated controllers, the synchronization settings on the
Controller Properties dialog box - Date/Time tab and on the
Controller Properties - Advanced Time Sync dialog box have no effect.
In free-running mode, FactoryTalk Logix Echo considers all emulated
controllers to be synchronized based on the workstation's Windows
clock. In co-simulation mode, you control the synchronization of
emulated controllers.
Synchronized emulated controllers should all rely on the same time
mode. For example, to be synchronized, two emulated controllers in
co-simulation mode must rely on the same time leader.
Tip: Set up the time configuration on your workstation before you run a synchronized
system of emulated controllers. Changing the workstation time after a synchronized system
starts running can lead to inaccuracies or non-synchronized results.
• Motion virtual axis produce/consume tags do not report faults, but
they might not work as precisely as on a physical controller.
• Displayed scan times will probably vary from project to project and will
differ from scan times on physical controllers.
See also
Use the API on page 24
Differences between emulated controllers and physical controllers on
page 8
Export the results of an Export the results of an operation as a CSV or Microsoft Excel file.
operation
To export the results of an operation
1. In the list of operations in the Output pane, select an operation.
If the Output pane is hidden, select the Output icon to display it.
2. In the Operations list, select an operation to export.
3. Right-click anywhere in the list of results and select an export option:
• Export > CSV Export
• Export > Excel Export (.xlsx)
• Export > Excel Export (.xml)
Tip: You can also copy and then paste results into a spreadsheet or document:
• Right-click anywhere in the results table.
• Select Copy or Copy with headers.
• Paste the results into a document or spreadsheet.
See also
Controller pane settings on page 10
Use the API The FactoryTalk Logix Echo Application Programming Interface (API)
provides programmatic access for third-party applications to manage an
emulated environment and interact with simulation systems. The
functionality of FactoryTalk Logix Echo is accessible through the API.
IMPORTANT To access the full functionality of the API, install the Logix Designer application,
version 33.00 or later, on the same workstation as FactoryTalk Logix Echo. Some API
functionality is not available unless the Logix Designer application is installed.
See also
Communication considerations on page 22
Virtual time on emulated controllers on page 23
Use controller snapshots Use snapshots to capture the settings and state of a controller or of multiple
controllers. Restore a snapshot to apply the saved settings to the controllers.
In a classroom system, you can save the settings of a group of controllers at
specific points of a project and restore the snapshots so trainees can observe
and run those scenarios again.
These emulated controller settings and data are saved in a snapshot:
• IP address
• Firmware package ID
• Slot number
• Persistency data
• Virtual SD card content, excluding fault dumps
• Time values
See also
Add a snapshot on page 27
Restore a snapshot on page 28
Export a snapshot on page 29
Import a snapshot on page 29
Add a snapshot Add a snapshot to capture and save the settings of a controller or group of
controllers.
To add a snapshot
1. In the Tools menu, select Snapshots.
2. Select Add to open the Add Snapshot dialog box.
3. In the Name box, enter a name for the snapshot. The name can contain
up to 40 characters.
4. (optional) In the Description box, enter a description for the snapshot.
5. Select the controllers to include in the snapshot.
6. Select Add.
See also
Restore a snapshot on page 28
To edit a snapshot
1. In the Tools menu, select Snapshots.
2. In the Snapshot pane, right-click a snapshot and select Edit.
3. Update the snapshot name or description.
4. Select Apply.
See also
Add a snapshot on page 27
Restore a snapshot Restore a snapshot to apply the controller settings saved in the snapshot.
IMPORTANT Message instructions executing when you saved the snapshot might generate an
error when you restore the snapshot.
IMPORTANT When you restore a snapshot, the WallClockTime (WCT) of the emulated controller
changes to the WCT at the time the snapshot was taken. The Enable Time
Synchronization setting on the Logix Designer Controller Properties dialog box does
not affect the WCT.
Tip: Restoring a snapshot purges all existing user projects from the controllers.
To restore a snapshot
1. In the Tools menu, select Snapshots.
2. Select the snapshot to restore.
3. Check the Inconsistencies box for any inconsistencies that exist
between the current setup and the snapshot. If errors appear, correct
them before restoring the snapshot.
4. Select Restore.
5. Select a Restore option:
• 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 controller without
adjusting the current configuration.
See also
Add a snapshot on page 27
To export a snapshot
1. In the Tools menu, select Snapshots.
2. In the Snapshot pane, right-click a snapshot and select Export.
3. Select a destination folder for the exported snapshot.
4. Enter a file name for the snapshot and then select Save.
The snapshot file appears in the destination folder as
filename.echo-snap.
See also
Add a snapshot on page 27
To import a snapshot
1. In the Tools menu, select Snapshots.
2. Select Import to open a File Explorer dialog box.
3. Browse to the location of the snapshot and select it.
4. Select Open. The snapshot is added to the snapshot list.
Troubleshooting emulated Use these resources to troubleshoot emulated controllers and the FactoryTalk
Logix Echo application.
controllers
• Check information in the FactoryTalk® Diagnostics Viewer. To open
the Viewer, open the FactoryTalk® Administration Console and select
Tools > FactoryTalk Diagnostics > Viewer.
Use the information, warning, and error messages in the FactoryTalk
Diagnostics Viewer to monitor FactoryTalk Logix Echo status, keep a
record of completed actions, and resolve issues in FactoryTalk Logix
Echo.
For more information on setting up and using FactoryTalk
Diagnostics, see the FactoryTalk View Site Edition User's Guide.
• Generate data files using the problem-report-collector.ps1 script.
• Change port numbers to correct a port conflict.
See also
Change port numbers to correct a port conflict on page 32
Generate data files using If you need help from Rockwell Automation technical support, a technician
might request data generated by the problem-report-collector script. The
the script gathers data from FactoryTalk Logix Echo that can help the technician
problem-report-collector identify a problem with the application or with an emulated controller.
script
To generate data files by using the problem-report-collector script
1. Open Windows PowerShell ISE (x86) in administrator mode.
2. Open this folder:
C:\Program Files (x86)\Rockwell Software\FactoryTalk Logix
Echo\Dashboard
3. Run the problem-report-collector.ps1 script. The script collects log files
and controller memory data and compresses it in two zip files:
• FTLogixEchoProblemReportIP.zip
• FTLogixEchoProblemReport.zip
The zip files appear in this folder:
C:\Users\username\AppData\Local\Temp\GUID
Change port numbers to If a port conflict occurs with another application after you install FactoryTalk
Logix Echo, you can change the port numbers used for the WebSocket,
correct a port conflict GraphQL, and service API connections.
See also
Change the port number for a WebSocket connection on page 32
Change the port number for Typically, the WebSocket protocol uses port 80. Follow these steps to change
the port number for a WebSocket connection.
a WebSocket connection
"ws://localhost:WEBSOCKET_PORT_HERE/emulate-dashboa
rd-backend"
],
}
]
},
...
}
See also
Change the port number for a GraphQL connection on page 33
Change the port number for Follow these steps to change the port number for a GraphQL connection.
a GraphQL connection
To change the port number for a GraphQL connection
1. Navigate to this folder on your workstation:
C:\Program Files (x86)\Rockwell Software\FactoryTalk Logix
Echo\Dashboard\resources\app\dist\app-backend\config
Tip: On 32-bit Windows workstations, navigate to this folder:
C:\Program Files\Rockwell Software\FactoryTalk Logix
Echo\Dashboard\resources\app\dist\app-backend\config
2. In a text editor, open the default.json file.
3. Enter the new port number for the apolloPort and routes.graphql
properties in the file. Enter the same port number for both properties.
{
...
"apolloPort": GRAPHQL_PORT_HERE,
"routes": {
"graphql":
"http://localhost:GRAPHQL_PORT_HERE/graphql"
},
...
}
4. Save and then close the default.json file.
5. In a text editor, open the graphql-service.js file.
6. Enter the new port number for the apolloPort property. Enter the
same port number that you entered in the default.json file.
...
module.exports = {
...
apolloPort: GRAPHQL_PORT_HERE,
...
};
7. Save and then close the graphql-service.js file.
8. Close FactoryTalk Logix Echo and then reopen it.
See also
Change the port number for a WebSocket connection on page 32
Change the service API port Follow these steps to change the service API port number for the FactoryTalk
Logix Echo interface.
number
"ws://localhost:46540/emulate-dashboard-backend",
SERVICE_API_PORT
],
}
]
},
...
}
4. Save and then close the default.json file.
5. Navigate to this folder on your workstation:
C:\Program Files (x86)\Rockwell Software\FactoryTalk Logix
Echo\Service
Tip: On 32-bit Windows workstations, navigate to this folder:
C:\Program Files\Rockwell Software\FactoryTalk Logix Echo\Service
6. In a text editor, open the EmulateService.exe.config file.
7. Replace SERVICE_API_PORT with a valid port number. The default is
46520.
<RockwellAutomation.Emulate.Service.Properties.Sett
ings>
<setting name="ServiceApiPort"
serializeAs="String">
<value>SERVICE_API_PORT</value>
</setting>
...
</RockwellAutomation.Emulate.Service.Properties.Set
tings>
</applicationSettings>
</configuration>
8. Save and then close the EmulateService.exe.config file.
9. In the Windows search bar, search for the Services application and
then open it.
10. In the list of services, right-click FactoryTalk Logix Echo Service and
then select Restart. The port number is updated when the service
restarts.
Update permissions for the When you install FactoryTalk Logix Echo on a workstation on which the Logix
Designer application is already installed, FactoryTalk Logix Echo updates
LogixServices COM service 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.
SDK Documentation kit and The FactoryTalk Logix Echo SDK and API provide a way to integrate all the
FactoryTalk Logix Echo functionality into your own software applications.
NuGet package Use the SDK and API to build applications to connect directly to controllers
for simulation and data analysis.
The SDK Documentation kit is installed as an option with FactoryTalk Logix
Echo. To find the SDK documentation:
• On the Windows Start menu, expand Rockwell Software.
• Select FactoryTalk Logix Echo SDK Documentation.
Tip: If the SDK Documentation kit does not appear on the Windows Start menu, run the
FactoryTalk Logix Echo installer again and select the SDK installation option.
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Get help determining how products interact, check features and capabilities, and rok.auto/pcdc
(PCDC) find associated firmware.
Documentation feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at
rok.auto/docfeedback.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.
Allen-Bradley, expanding human possibility, Logix, Rockwell Automation, and Rockwell Software are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomayson Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenkÖy, İstanbul, Tel: +90 (216) 5698400 EEE YÖnetmeliğine Uygundur