For optimal performance of the Studio 5000 Logix Emulate application, your personal computer should meet or exceed the following hardware and software requirements. Studio 5000 Logix Emulate can be installed on a personal computer that meets the operating system minimum requirements.

• Intel Core i5 Standard Power processor (i5-3xxx)
• 8 GB of RAM memory
• 20 GB free hard disk space

• Operating system and service pack compatibility:

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

• Windows® 11 Enterprise
• Windows 10 Enterprise
• Windows Server 2019 Standard Edition
• Windows Server 2022 Standard Edition

• Microsoft .NET Framework 3.5
• Microsoft .NET Framework 4.8

• This version of the Studio 5000 Logix Emulate application is expected to operate correctly on all other editions and service packs of these operating systems, but has not been tested:

• Windows 8
• Windows Server 2019
• Windows Server 2016

• These prerequisite software applications are required with this version of Logix Designer application and will be installed with this release:

• FactoryTalk® Services Platform v6.40
• FactoryTalk® Activation Manager v5.01
• RSLinx® Classic v4.40, which is shipped with the Logix Designer application, version 36.00
• FactoryTalk® Linx v6.40, which is shipped with the Logix Designer application, version 36.00

• FactoryTalk® View Site Edition (SE) software and FactoryTalk Linx communication software are required to use alarming capabilities fully.
• Check the software requirements for other Rockwell Software® products that will be installed to be sure that these products are also compatible with the system.

In this release of the Studio 5000 Logix Emulate application, product improvements have been made to increase product resiliency to potentially disruptive activities. These enhancements have been verified not to affect product safety, performance, expected life, configuration, or operation of the product. Rockwell Automation recommends that you follow good Industrial Control System (ICS) security practices that include regular product updates. To maintain authenticity, obtain product updates and new releases directly from Rockwell Automation.

Emulate API test sometimes fails on Windows 2022 Server OS (3164278)

The Emulate API test RA_GetTagInfo returns an incorrect error value when attempting to get tag info from a controller that is not present in the virtual rack.  This only occurs for Windows Server 2022.

There is no workaround for this issue.

This anomaly first identified in Studio 5000 Logix Emulate version 36.00.

Anomalies for Studio 5000 Logix Emulate version 33.00

The following list identifies the anomalies corrected in Studio 5000 Logix Emulate version 33.00 and the known anomalies found during testing for this release. Use the identification information provided in the brackets [] to track the anomaly in future releases or contact Customer Support for assistance with a related issue.

• Reopening the chassis monitor or re-adding an emulated controller changes the battery LED to red and loses the controller application. [Lgx00190098]
• Starting the chassis monitor without administrative rights while running Studio 5000 Logix Emulate as an administrator is not supported. By default, Studio 5000 Logix Emulate installs with Run as administrator selected. [Lgx00219241]    
• Operation of binary parameters is not handled properly for the MAG, MAS, and MRP instructions.  These parameters are incorrectly driven by the values of other instruction operands. [Lgx00199947].
• Restoring a snapshot created from the chassis monitor with All Modules > Save Snapshot originally created with versions 31 or 32 would not allow those versions to be selected for Restore. [Lgx00221759]
• The Chassis Monitor becomes unresponsive when saving a snapshot of an Emulate OTS controller. [Lgx00221761]
• Stopping and restarting the chassis monitor when the OTS controller is running causes a battery fault on the associated faceplate. [Lgx00225886]
• Sending values from a user application to an input image in an OTS controller with RA_ExecuteTagGroup() causes the values to be applied inaccurately. [Lgx00194650]
• Restoring a snapshot with All Modules > Restore may trigger a controller red x error. [Lgx00227339]
• No interface is available to programmatically download a project to an OTS controller. [Lgx00179176]
• Emulate controller becomes unresponsive instead of declaring a watchdog fault. [Lgx00228487]
• Certain message instructions would occasionally result in a controller with a red x. [Lgx00229181]
• When using the RA_TriggerRunPulse() programmatic interface to an OTS controller, an incorrect error triggers if the controller is not halted. [Lgx00229372]
• An error occurs when downloading an .acd file to the Emulator controller and the destination operand is a REAL data type for Logical operations. Project verification does not identify the error. [Lgx00217681]
• Using Studio 5000 Logix Emulate operation of binary parameters is not handled properly for the MAG, MAS, and MRP instructions. These parameters are incorrectly driven by the values of other instruction operands. [Lgx00219085]
• Using Studio 5000 Logix Emulate CTU behavior was incorrect for prescan. [Lgx00219605]
• Convert to BCD (TOD) and Convert to Integer (FRD) does not generate correct results when using Studio 5000 Logix Emulate. [Lgx00218808]
• Installing a personalized version of Studio 5000 Logix Emulate triggers a EULA.text is missing error. [Lgx00230711]

• An anomaly exists in Studio 5000 Logix Emulate controllers when using the Jump to Subroutine (JSR) instruction with Return (RET) instruction parameters in the Sequential Function Chart [SFC] programming language. [Lgx00155841] To resolve this issue, avoid using RET with SFC subroutines. Use alternate languages such as Ladder, Structured Text, or Function Block.
  
• The result of the ADD instruction in SFC is different than the other languages. It is also different from a physical controller. [Lgx00156771] To resolve this issue, avoid using ADD instructions with SFC subroutines. Use alternate languages such as Ladder, Structured Text, or Function Block.
• Rockwell Automation recommends not configuring a low Watchdog value for tasks in Emulate because Windows system tasks may preempt user tasks in the Emulate controller. When preemption occurs for a specified duration, a Watchdog fault occurs. Improved watchdog timing does not prevent a watchdog fault for low watchdog values. [Lgx00219641]

These are the functional changes for Studio 5000 Logix Emulate version 36.00.

• None in this release.

The following are the application notes for Studio 5000 Logix Emulate version 36.00.

• While the Windows 10 operating systems run on many touch-enabled devices, various features of the Studio 5000 Logix Emulate application might not be touch-enabled. Most functions are expected to work with touch, but the software is tested only with a keyboard and a mouse.
• Running Studio 5000 Logix Emulate in conjunction with Fast-User Switching is not supported. Running Studio 5000 Logix Emulate software in Safe mode is not supported. Accessing Studio 5000 Logix Emulate through Remote Desktop on remote machines is not tested.
• Licensed-Based Source Protection is not supported. License-Based Source Protection controls permissions (Use, View, Edit, Copy, Export, and Protect) on license-protected Add-On Instructions and routines.

• Do not depend on the emulated controller to match the performance or operation of the physical controller. Some instructions are interpreted differently in an emulated controller than in a physical controller. Execution times for instructions and program files may be significantly different in an emulated controller than in a physical controller.

• For maximum portability across platforms, avoid mixed operand types between the destination and its inputs. To get identical results for similar operations across languages, perform floating point operations. Floating point operations can affect performance. Verify that operands are compatible with the I/O.
• There are instruction differences across programming languages and Logix platforms. The following examples use the operation i = n / m where all the operands are integers. Ladder DIV instructions perform an integer divide operation and store the immediate result in the destination. For ‘n’ = 800 and ‘m’ = 1000, ‘i’ is equal to 0. The DIV function block instructions only does floating point operation. The Function Block instruction converts the inputs to reals, if necessary, and converts the result from a real to the destination type, if necessary. In this example, ‘n’ is converted to 800.0 and ‘m’ is converted to 1000.0. The result of the operation is 0.8. That result gets converted to an integer where rounding rules apply and the final destination value is 1. This difference between Ladder and Function Block instructions applies to all Logix platforms. Function Block instructions only perform floating point operations.
• If a Studio 5000 Logix Emulate controller experiences repeated minor faults, a red X appears. This occurs in systems whenever load in the controller prevents it from responding to communications in a timely manner, including when minor faults are repeatedly generated on each program scan. To avoid this, correct any programs that may cause repeated minor faults.

Studio 5000 Logix Emulate requires an upgrade to RSLinx Classic Gateway version 4.20 or later. If RSLinx Classic Lite is installed, uninstall RSLinx Classic Lite and install RSLinx Classic Gateway version 4.20 or later. Remote connections are disabled when both FactoryTalk Linx and RSLinx Classic version 4.20 or later are installed. Beginning with Studio 5000 Logix Emulate version 35.00, you can also create remote connections with FactoryTalk Linx version 6.31 or later.

To enable remote connections when using RSLinx Classic version 4.20 or later:

1. Ensure that FactoryTalk Linx is not running. If FactoryTalk Linx is running as a service, stop the service and mark the service for manual startup.
2. In RSLinx Classic Gateway, select View > Options and select Accept UDP messages on Ethernet port.
3. Restart RSLinx Classic.
4. Under Communications, verify that Configure Gateway… is selected.
5. Restart RSLinx Classic.

Tip: After configuring RSLinx Classic, FactoryTalk Linx may be enabled. RSLinx Classic will enable remote connections.

6. In Logix Designer, select Communications > Communications Software > RSLinx Classic.

To enable remote connections when using FactoryTalk Linx version 6.31 or later on the server side:

7. Install FactoryTalk Gateway Server OPC UA and DA on the server side of the connection.

8. Open FactoryTalk Linx Gateway Configuration. Select Remote Proxy Service. Make sure Enable Remote Proxy Server is selected. Make sure all NIC cards are enabled on which the proxy service should listen.
9. Open FTLinx Network Browser and configure the driver to listen to Ethernet/IP encapsulation ports on the intended interface. Verify that Configure Driver > Ethernet > Advanced > Listen on Ethernet/IP encapsulation ports is selected.
10. Make sure RSLinx Classic is not running.

To enable remote connections when using FactoryTalk Linx version 6.31 or later on the client side:

11. Open FTLinx Network Browser. Make sure that Advanced Settings > General > Enable Communications to Remote Proxy is selected.

12. Add a new Remote Device via Proxy Server driver, specifying the IP address of the server and the name of the remote driver.
13. In the Logix Designer application, select Communications > Communications Software > FactoryTalk Linx.