For optimal performance of the RSLogix 5000 software, the personal computer should meet or exceed these hardware and software requirements.

Tip: The RSLogix 5000 software can be installed on a personal computer that meets the operating system minimum requirements, but may not meet performance expectations when used in a production system.

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

• Windows® 10 Professional (64-bit) version 1703
• Windows Server 2012 R2 Standard Edition
• Windows Server 2016

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

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

• Windows 10 (versions 1607, 1709)
• Windows 8
• Windows Server 2012

• These prerequisite software is required with this version of RSLogix 5000 software and will be installed with this release:

• FactoryTalk® Services Platform v6.30
• FactoryTalk® Activation Manager v4.06.13
• RSLinx Classic v4.30

• FactoryTalk® View Site Edition (SE) software and FLEX Ex 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.

Note: The RSLogix 5000 software version 20.06 does not support SoftLogix.

• Logix 5000 controllers and ControlLogix Motion modules must contain a revision of firmware that is compatible with this version of the RSLogix 5000 software. The firmware images for most of the supported modules are contained on a DVD-ROM shipped with Rockwell Software Studio 5000 Automation Engineering & Design Environment™ or can be downloaded from the PCDC.

• The firmware associated with this release version of the programming software does not support redundancy. Redundancy firmware revisions are released later than the standard revisions and are available for download from the Product Compatibility and Download Center.

Tip: Most modules use Flash-ROM for the storage of firmware. If a module requires a firmware change, use the ControlFLASH™ tool to perform the update to the Flash-ROM. It is contained in the downloaded image or on a DVD-ROM shipped with the RSLogix 5000 software. Another option is to update the firmware automatically as part of the project download. For additional information and assistance in performing a Flash-ROM update, review the ControlFLASH Firmware Upgrade Software User Manual, publication 1756-UM105.

RSLogix 5000 software version v20.06 has no new features.

AssetCentre Backup and Compare tasks (942415, 981951, 981960, 1600636, 1170050, Lgx00225888)

AssetCentre Backup and Compare tasks run from one to several days without errors but will then start to receive the error *** RETRY *** - Event (0001) Done - State:256 Status: Logix 5000 Error: Failed to open file <file_name>. ExtErr" Could not CoCreate RSLogix5000Services. Please re-install Logix5000.

This anomaly first identified in version 20.01.

Fatal error can occur when editing an RLL rung using ASCII Editor offline (1244059)

Attempting to delete a rung when online without accepting the edits and then going offline and attempting to accept the edits, puts the rung in an error state but does not delete the rung. Attempting to delete the rung code causes the RSLogix 5000 application to crash.

This anomaly first identified in version 32.04.

Tag does not reference valid reference or target (1241943)

When editing the Type and Data Type values in the Tag Properties dialog in a safety project, applying the changes causes an error Failed to modify the properties of the <project_name>. Tag doesn't reference valid object or target.

This anomaly first identified in version 32.00.

Unexplained motion (1090045, 1090058)

Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.

This anomaly first identified in version 12.00.

FactoryTalk Activation component causing incompatibility with Stratus (990492)

FactoryTalk Activation component delivered with RSLogix 5000 application v20.05 is incompatible with Stratus solutions. 

This anomaly first identified in version 20.00.

Brand name error on Installation Summary page (1811984)

The Installation Summary page for v20.06 inaccurately states the product name as Studio 5000. It should state the product name as RSLogix 5000.

This anomaly first identified in version 20.06.

Inaccurate size reported for install (1557642, 1822740)

Installing the <rslx5kt> software on a disk other than the C drive causes an inaccurate reporting of the estimated gigabytes required to install the application and the used gigabytes after the installation is complete. The installation fails if there is not enough free space on the C drive, but a warning message does not display to inform you that the installation failed.

This anomaly first identified in version 20.06.

GDI Object Leaks, Child Windows (x66929)

Anomaly

First identified in RSLogix 5000 Software 16.x

Repeatedly opening and closing child windows may cause the number of graphics device interface (GDI) objects to increase when running RSLogix 5000 on Windows XP SP2 or on Windows Server 2003 with the Themes service started. Example child windows include, but are not limited to: the Controller Properties dialog, the Ladder Routine window, and the SFC Routine window. The leaks are minor in nature, but it is possible that unpredictable behavior can occur if the number GDI objects gets excessively high. This issue is documented in the Microsoft Knowledgebase article http://support.microsoft.com/?kbid=319740, which also provides instructions for obtaining a supported hotfix from Microsoft. A temporary work-around is to set the display properties to Windows Classic Theme.

Corrected

Blank Primary Window (Lgx0039239)

Anomaly

RSLogix 5000 Software 16.x

If you have a primary help window displayed and you open a help topic which displays a secondary window, the primary window may become blank. This is the result of a problem with the Windows Help compiler. To display the original topic, click Help Topics and re-select the original topic.

Unicode Characters, Does Not Display (Lgx00063773)

Anomaly

RSLogix 5000 Software 16.x

When the description of a task, program, routine, module, trend, etc. is edited, any audit records displayed using RSMACC Audit will not properly display Unicode characters.

Inserting Unicode Characters (Lgx00059649, Lgx00059650, Lgx00059825)

Anomaly

RSLogix 5000 Software 16.x

RSLogix 5000 employs a feature which allows the user to position the caret on an edit control and, without explicitly opening the edit control, to begin entering character data from the keyboard. This action will cause RSLogix 5000 to automatically open that edit control as character data entry continues. For many of the edit controls in RSLogix 5000, using this auto-open feature when inputting Unicode characters using an Input Method Editor (IME) will result in unexpected behavior or in a Fatal Error. 

To avoid this Fatal Error when entering Unicode characters, the edit control should be explicitly opened before beginning to enter character data from the keyboard. In most cases, pressing [Enter] on the keyboard will open the edit control which has the caret. In other cases, a single click or double click of the mouse is required. 

When using an IME to input Unicode characters, if the small IME character input dialog appears in the upper left corner of the display, then you have started to input a Unicode character string with no edit control opened. When this occurs, you can press [Esc] on the keyboard to cancel the input and then open the desired edit control before entering the Unicode character string.

User-Defined Data Type Size Limits (x03090, x06296)

Anomaly

RSLogix 5000 Software 16.x

You may not create a data type with more than 512 members either by editing in the Data Type Editor or by importing from an .L5K file. An individual UDT member may be an array with more than 512 elements.

Associated Tag, Non-Recoverable  (x77626)

Anomaly

RSLogix 5000 Software 16.x

In RSLogix 5000 V16.03, the ability to edit the Associated Tag configuration for analog and digital alarm tags has been enabled. If an alarm tag is referenced in executing logic, any attempt while online to remove an Associated Tag for that alarm tag may result in a Major Non-Recoverable Fault in the controller.

Module: Modify Properties (Lgx00072088)

Anomaly

RSLogix 5000 Software 16.x

With the security action “Motion: Modify Configuration” granted, you should be allowed to modify the motion configuration. You are allowed to change the axis association to a module from the Axis Properties dialog but are erroneously prevented from making this change from the Module Properties dialog. To allow the axis association to be configured on the Module Properties dialog, grant access for the security action “Module: Modify Properties”. This will enable all of the tabs of the Module Properties dialog, including the Axis Association tab.

Hardware Overtravel Fault (x66998)

Anomaly

RSLogix 5000 Software 16.x

For Kinetix 6000 axes configured in RSLogix 5000, if you have both Soft Overtravel and Hardware Overtravel Limits enabled, and you configure the Soft Overtravel Fault Action as "Status Only", be aware that a Hardware Overtravel Fault Action configured for "Stop Motion" may not "Stop Motion" due to the two faults existing together and the first fault action being set to "Status Only". For more information refer to Technical Note: ID=36709 "2094 Kinetix 6000; Soft Overtravel triggers first then sequential hard overtravel does not stop motion", and Technical Note: ID=21500 "How do I get off a Soft Overtravel?"

SERCOS Ring Phase Up (x43750, x43870, x44775)

Anomaly

RSLogix 5000 Software 16.x

If a motion Axis_Servo_Drive axis is configured with a Loop Configuration using auxiliary feedback, there are 3 choices for the units for Drive Counts per: Aux Rev, Aux Inch, Aux Millimeter. Only the default Aux Rev is valid for RA SERCOS Drives. Selecting Aux Inch or Aux Millimeter will cause a SERCOS Ring phase up fault at Phase 3. The SERCOS Fault reported will be “Position Data Scaling – Invalid attribute value”. To workaround the problem, select Aux Rev as the units when configuring a Loop Configuration using Dual/Auxiliary feedback.

Windows Vista Operating System (x81660)

Anomaly

RSLogix 5000 Software 17.x

There are a number of issues related to compatibility of RSLogix 5000 software with the Windows Vista operating system. The most significant of these includes the following:

0. Although RSLogix 5000 software versions earlier than version 17 can be installed, they are not supported on Windows Vista operating systems.
1. Although RSLogix 5000 software version 18 is supported with User Account Control (UAC) turned on, RSLogix 5000 software version 17 is supported only with UAC turned off.
2. On some properties dialog boxes, there is no indicator shown when a control has focus. A workaround to display focus indicators is to select the Windows Vista setting to ‘Underline keyboard shortcuts and access keys’. Access this setting by using Personalize>Ease of Access>Make the keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
3. The 1784-PCIC(S) driver must be at version 4.06.01 or later. This driver is installed when RSLinx software is installed.

Operands Missing V17 (x80000)

Anomaly

First identified in RSLogix 5000 Software 17.x

Emulated Controller, Select Slot 0(x79666)

Anomaly

RSLogix 5000 Software 17.x

RSLogix 5000 software does not support selection of slot 0 for an RSLogix Emulate 5000 Controller. If you need to emulate a controller in slot 0, you can perform the following steps:

1. With your emulator project open in RSLogix 5000 software, from the File menu choose Save As to export the project to an .L5K file.

2. Launch a text editor (for example, Notepad), and open the .L5K file.

3. Scroll through the content of the .L5K file until you find the MODULE Local section for the Emulator.

4. Locate the Slot entry, and change the value from its current slot value to slot 0 and save the file.

5. In RSLogix 5000 software, import the edited .L5K file.

You can now configure a controller in slot 0 in RSLogix Emulate 5000 software and then download your Emulator project.

Note that this workaround requires that RSLinx Classic software version 2.54.00 or later be used.

Unable to Enable Security (x107466)

Anomaly

RSLogix 5000 18.x

The SetSecKeys tool included with RSLogix 5000 software version 17 and earlier do not work with User Account Control (UAC) turned on. When a SetSecKeys tool earlier than file version 18.0.0.0 is executed with UAC turned on, security appears to be enabled, yet security remains disabled in RSLogix 5000 software. If a version of SetSecKeys earlier than file version 18.0.0.0 is used inadvertently, SetSecKeys file versions 18.0.0.0 and later can still be used to enable security. (Note that depending on the operating system, the file version of SetSecKeys.exe can be viewed on either the Details tab or the Version tab of the File Properties dialog box.)

Slow Launch Times (x125369)

Anomaly

RSLogix 5000 Software 20.x

When RSLogix 5000 software is launched for the first time after restarting your personal computer, it may take 1 to 3 minutes for RSLogix 5000 software to be available for use. This behavior is also exhibited when launching FactoryTalk Administration Console or any other product that uses FactoryTalk Services Platform. Note that subsequent launches of these applications will not experience this behavior. This is only observed on the first launch of the application after a restart of the personal computer. If you experience launch times significantly longer than 3 minutes, refer to the firewall configuration settings in Tech Note #29402

Windows 7 Operating Systems (x111504, x113166, v124864)

Anomaly

RSLogix 5000 19.x

There are a number of issues related to compatibility of RSLogix 5000 software with the Windows 7 operating system. The most significant of these includes the following:

• Although RSLogix 5000 software versions earlier than version 19 can be installed, they are not supported on Windows 7 operating systems. Also note that some applications and tools cannot be installed on a 64-bit Windows 7 operating system. Most notably, RSLogix 5000 software version 12 and earlier cannot be installed on a 64-bit Windows 7 operating system.
• On some properties dialog boxes, there is no indicator shown when a control has focus. A workaround to display focus indicators is to select the Windows 7 setting to 'Underline keyboard shortcuts and access keys'. Access this setting by using Personalize>Ease of Access Center>Make the keyboard easier to use>Underline keyboard shortcuts and access keys. (x113166)
• The RSLogix 5000 Clock Update tool does not work properly when it is installed on a 64-bit Windows 7 operating system and executed. (x124864)

New EDS File Not Displayed (Lgx00124959)

Anomaly

RSLogix 5000 20.x

When a new EDS file is registered from outside RSLogix 5000 software, when RSLogix 5000 software is not running and RSLinx Classic software is running as an application (as opposed to as a service), then the newly registered device will not be available in the Select Module Type dialog box. Note that there is no problem with display of the device when registered outside of RSLogix 5000 software, provided that you first exit the RSLogix 5000 application and shut down the RSLinx Classic application. There is also no problem with display of the device when registered from within the RSLogix 5000 application (such as when using the “ Tools>EDS Hardware Installation Tool” menu). So, if the registered module is not displayed, you can use the “ Tools>EDS Hardware Installation Tool” menu to register the device again.

XML Full Project (x114197)

Anomaly

RSLogix 5000 20.x

Unable to Open Full Project XML Format File (.L5X) for Project File of Later Version of RSLogix 5000 Software than is Being Executed.

When attempting to open a full project xml format file (.L5X), an error may be reported indicating "Controller Revision not supported". This will occur when the major revision of the xml format file being opened is later than the revision of RSLogix 5000 software being executed.

For example, when executing RSLogix 5000 software version 19, an attempt to open an xml format file for version 20 will report the error. However, when executing RSLogix 5000 software version 20, an attempt to open an xml format file for version 19 will not exhibit the problem. When this error is observed, first switch to the RSLogix 5000 software version for the xml format file, and then open the file. This problem does not affect L5K or ACD files. (x114197)

"Log On to FactoryTalk" Displayed (Lgx00124955)

Corrected Anomaly with Studio 5000 Logix Designer 24.01

Known Anomaly First Identified as of  RSLogix 5000 20.x

When launching RSLogix 5000 software, the "Log On to FactoryTalk" dialog box may be displayed.

This dialog box may be seen when you do not have Administrator privileges on the personal computer and the current user does not exist in the FactoryTalk directory. If this dialog box is cancelled, the RSLogix 5000 software will not be launched. When the dialog box is displayed, entering the credentials for a user that exists in the FactoryTalk Directory will allow RSLogix 5000 software to be launched. Administrator accounts are included in the FactoryTalk Directory by default.

To avoid seeing this dialog box, you can add the current user or user group to the FactoryTalk directory. Follow these steps to add a user or user group to the FactoryTalk directory:

• Launch the FactoryTalk Administration Console (available from the Start menu).
• Select the Network directory when prompted. (You may need to provide credentials for a user with Administrator privileges in order to continue.)
• To allow access for a particular user, navigate to "Network\System\Users and Groups\Users", right-click the Users folder, and choose "New>Windows Linked User". Then click Add and provide the domain\logon name for the desired user. (You can click Check Names to verify that the name was found.)
• To allow access for all authenticated users, navigate to "Network\System\Users and Groups\User Groups", right-click the User Groups folder, and choose "New>Windows Linked User Group". Then click Add and type the name of the user group "authenticated users".

The "Log On to FactoryTalk" dialog bax may also be displayed when using Remote Desktop to connect to the personal computer that is running RSLogix 5000 software. This is due to FactoryTalk Security not recognizing the computer name. To enable access through Remote Desktop for a specific computer, you should add the name of the computer that is initiating the Remote Desktop connection to the "Network\System\Computers and Groups\Computers" folder in the FactoryTalk Administration Console. To allow remote computers to connect using the name of the host computer, open the FactoryTalk Administration Console and log in to the Network directory using your domain credentials. Then navigate to "Network\System\Policies\Security Policy". In the "Computer Policy Settings" section, set "Identify terminal server clients using the name of" to "Server Computer". To allow all computers to connect, set the value of "Require Computer accounts for all client machines" to disabled.

Note that if "Use single sign-on" is set to "disable" in FactoryTalk software, then the "Log on to FactoryTalk" dialog box will be displayed each time RSLogix 5000 software is launched and proper user credentials must be entered in order to continue. (By default, "Use single sign-on" is set to "enable".)

RSNetWorx Software Cannot Download to Controller (Lgx00124236)

Anomaly

RSLogix 5000 Software 20.x

When attempting to download a project using RSNetWorx software, if the controller firmware is at revision 20 and the controller is in Remote Run mode, then RSNetWorx software will not be able to change the controller mode in order to download. In this case, the controller mode must be changed either by using the keyswitch or by using RSLogix 5000 software version 20.

RSLogix 5000 Software Unresponsive (x129306)

Anomaly

RSLogix 5000 Software 20.x

When the server hosting the FactoryTalk Directory is restarted, RSLogix 5000 software may become unresponsive for about 3-5 minutes. When FactoryTalk Services then become available, RSLogix 5000 software will resume normal operation. 

CIP Path Displayed Using AutoFLASH (x124629, x124918)

Anomaly

RSLogix 5000 20.x

When using AutoFLASH to update firmware, a progress dialog box is presented to you during the update. This progress dialog box shows the communication path as ASCII values for the CIP path instead of displaying it in the typical display format such as "AB_ETH-1\10.20.30.40\Backplane\3". This path format is also shown in Audit log messages.

Long Timeout (x125029, x125045)

Anomaly

First identified in RSLogix 5000 20.x

When a PowerFlex 755 drive loses power during a firmware supervisor update, it can take over 10 minutes for RSLogix 5000 software to report the time out. Once the connection to the powered-up PowerFlex 755 drive has been restored, the firmware supervisor will then successfully update the drive's firmware.

References In Program Logic Will Not Update (x125220)

Anomaly

RSLogix 5000 20.x

If a project for a CompactLogix controller that is no longer supported is imported as a controller that has expansion I/O, any expansion I/O modules from the original controller are properly moved to the correct expansion slot; however, the references in program logic will not be correspondingly updated. This does not necessarily result in the program failing to verify. Instead, the logic may now be referencing the embedded modules for this controller. This is a problem only when opening a L5K or L5X project file. The references are properly adjusted when opening an ACD file.

Miscellaneous Known Anomalies V20

• Import of a Project to Controller with Expansion I/O May Not Update Logic that References that I/O
• RSLogix 5000 Software No Longer Functioning after Inhibit of Module in Unlocked Instance
• Operands Missing After Copy and Paste or Drag and Drop of MDSC Related Motion Instructions to Version 20
• Partial Import Online of S-Curve Function Block May Execute with Uninitialized Values
• Major Non-Recoverable Fault Removing Alarm Message Tag Association While Online
• Failure to Modify the RPI of a Consumed Tag
• Instances of Going Online for the First Time Failing

Corrected Anomaly with Studio 5000 Logix Designer 24.01

On CIP-axis:

• Motor Source=NamePlate
• Motor_Feedback: select [Hiperface]

the associated Feedback attributes, (in Offline Configuration of Feedback Device) are:   

• Cycle Resolution:       [          ]
• Cycle Interpolation:   [          ]
• Calculate'd Effective Resolution: [          ]

You can edit or enter these attributes in Offline Configuration of Feedback Device:

Revision |    values     |    Res      *    Interp     | =  effective
V18.00   | Defaults     |   1024     *    2048       |=  2097152          StartUp=[Incremental]
V18.00    | by hand     |   1024     *   2097152  | = 2147483648  
V18.00    | by hand     |   131072 *   10000000 | = 10240000000   (7 0's)

Revision  |    values     |    Res      *    Interp     | =  effective
V19.01    | Defaults     |   1024     *    2048       |=  2097152          StartUp=[Absolute]
V19.01    | by hand     |   1024     *   2097152   | = -2147483648    
V19.00    | by hand     |   131072 *   10000000 | = -2071986176   (7 0's)

Direct Add-on-Profile-to-Device Communication Could Result in Time Out Errors or Communication Routing to the Wrong Device (1927272)

Direct Add-on-Profile-to-device communication could result in time out errors or routing the communication to the wrong device in circumstances where all of the following conditions are met:

• I/O must exist on a different subnet from the controller.
• Layer 3 switches used to separate and manage the routing of communication from the controller network to the network with the I/O.

This applies to configuration data that goes through unconnected communication to the target I/O device (for instance, uploading/downloading device parameters).

This does not apply to I/O data.

This does not apply to commands from the controller (for instance, inhibiting/uninhibiting a device).

Please see technote BF28941 for additional details.

This anomaly first identified in version 20.00.

Mismatching display resolution and scaling may result in overlapping SFC elements (2122642)

Editing a Sequential Function Chart (SFC)) using a display with a given resolution (for example, 1920 x 1200) and Windows scale setting (for example, 100%), closing the ACD, and then opening the same ACD in another resolution (for example, 3840 x 2160) and Windows scale setting (for example, 150%) may result in overlapping SFC elements.

Errors logged in the Logix Compare Tool and FTAC when running a compare (1170050, Lgx00225888)

When running the Logix Designer Compare Tool or FactoryTalk AssetCentre, the following errors can be logged:

• Object reference not set to an instance of an object.
• Component of the RSLogix 5000 Application has stopped working.

This anomaly is caused by a component of Logix Designer, RSLogix5000Services.exe.

Note this anomaly will only occur with V20.05.00 of the Logix Designer application.

Refer to Knowledgebase document 1129863 for more information.

Unexplained motion possibly caused by the application not recognizing the motion database which could cause the motion configuration to change.

Some PlantPAx P_PIDE Add-On Instruction instance values were set to denormalized low REAL values upon import of a P_PIDE 4.00.00 Add-On Instruction into a project that contained a P_PIDE 3.5.xx Add-On Instruction.

This anomaly first identified in version 18.00.

FactoryTalk AssetCentre error caused by the Logix Designer application (961951, Lgx00225888)

The following error will appear in FactoryTalk AssetCentre: "ExtErr: Could not CoCreate RSLogix5000Services. Please re-install Logix5000." 

This anomaly is caused by a component of the Logix Designer application, RSLogix5000Services.exe, experiencing a fatal error during the compare operation. (View this error in the Windows Event Logs).

While the error in FactoryTalk AssetCentre can affect all asset versions, the version of software causing the error will be apparent in the Windows Event Logs.

This anomaly first identified in version 20.04.

Please refer to Knowledgebase document 1129799 for more information.

Disable Download Project Documentation and Extended Properties features

To include or exclude project documentation and extended properties from a downloaded project, select or clear the

Fatal Error 0xe0434352 when creating, opening, or interacting with a module’s properties after installing a later version of the Studio 5000 Logix Designer application or after installing a new Add-on Profile (3219935)

Fatal Error 0xe0434352 occurs on creating, opening, or viewing of profiles updated with a web-based interface, including 1756 Ethernet modules, 5069 Ethernet Adapters, 5094 Ethernet adapters, 1734 Ethernet Adapters, and 1756 I/O.

This fatal error could occur after an installation of the Studio 5000 Logix Designer application or a stand-alone Add-On Profile (AOP), which causes an upgrade to all module profiles.

The fix for this anomaly is available in the Add-on Profiles update for the 1756 Analog Modules, v40.14.70. The Add-on Profiles can be downloaded from the Product Compatibility and Download Center. For more information on this anomaly and the solution, please see technote ID BF30201. 

This anomaly first identified in v20.05.

Output data remains high for inhibited modules during testing (Lgx00177604)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Fatal error can occur when an RLL rung is edited using ASCII Editor offline (1244044)

When the ASCII Editor is used to edit a rung where previously an online pending delete rung edit was accepted offline for the same rung, a fatal error occurs.

This anomaly first identified in version 20.00.

After an Add-On Instruction was downloaded, uploading the project caused one of the Add-On Instruction's multi-dimensioned array parameter tag to become invalid. The Logix Designer application generated the error: USER_CONTROL, op errand 1: Invalid size of array. Argument must match number of dimensions.

This anomaly first identified in version 20.04.

After changing a BOOL tag value to Decimal, and then saving, closing, and reopening the project file, the value had reset to Float. A BOOL tag reset to Float disabled manual changing of the value between 0 and 1.

This anomaly first identified in version 20.00.

Trying to upgrade the project in the Controller Properties dialog box, from v20.00.00 to v30.00.00, maintaining the same controller, causes a fatal error.

This anomaly first identified in v20.01.

Attempting to import some Add-On Instructions into an existing project generates the error message: Failed to import <file name>. Unable to parse the L5X content.

This anomaly first identified in version 17.00.

To work around this issue, export the Add-On Instruction, modify the file description to remove dashes. Or, open the L5X file in a plain text editor and modify the description to remove dashes. Import the Add-On Instruction.

The Logix Designer application has been upgraded to a version of MSXML that is supported by Microsoft.

This anomaly first identified in version 20.01.

This sequence of events can result in unexpected tag values:

1. An Add-On Instruction contains an alias parameter that points to a member of a local tag.

2. The alias parameter is changed to a base tag, either by editing the AOI definition directly or by importing a modified Add-On Instruction that overwrites the existing Add-On Instruction.

3. The instance values for the previously aliased parameters now contains unexpected values.

This anomaly first identified in version 18.00.

Follow one of these steps to work around the issue:

• To replace all values in all instances of the modified Add-On Instruction with the default values, double-click the Parameters and Local Tags folder for the modified Add-On Instruction, then click Copy default values in the Monitor Tags window.  This replaces all existing values for tags of this Add-On Instruction type with their default values.
• To replace the values for only the previously aliased parameters, in the Tag Monitor window, select each Add-On Instruction instance from the Data Context menu and then modify the values for the desired parameters.

After installing version 30.00 or the version 30.00 AOP Bundle, adding an ENBT, ENT2T or EN2TR module causes a fatal error.

This anomaly first identified in version 20.00.

Attempting to search a tag’s cross-reference multiple times may cause the software to crash.

This anomaly first identified in version 20.04.

After performing multiple cross reference tasks and closing the window after tasks, the Logix Designer application stopped performing with error 0xc0000005.

This anomaly first identified in version 20.01.

Adding a new case selection in a Structured Text routine (Lgx00166840)

Adding a new case selection in a Structured Text routine can cause the Logix Designer application to shut down.

This anomaly first identified in version 20.03.

Output Cam editor with UDT alias causes a crash when you click Apply (Lgx00161890)

When using the Output CAM Editor to make changes to an Output CAM that contains an Alias Tag, you will get a fatal error when you click Apply within the editor. The work around is to use the direct address for the Output CAM operand of the MAOC rather than the alias tag.

This anomaly first identified in version 20.01.

Unicode Characters, Does Not Display (Lgx00063773)

Slow Launch Times (Lgx00125369)

Long Timeout (Lgx00125029, Lgx00125045)

Once the connection to the powered-up PowerFlex 755 drive has been restored, the firmware supervisor will then successfully update the drive's firmware.

This anomaly first identified in version 20.00.

References In Program Logic Will Not Update (Lgx00125220)

Undefined Tag error (Lgx00190787)

Undefined Tag error displays when spaces are used between commas in the Ladder Editor. Spaces between commas are no longer needed.

This anomaly first identified in version 20.04.02.

Failed to create module library, not registered (Lgx00203463)

Failed to create module library in a project that uses the 1768-L45 controller. The 1768-L45 controller is no longer a supported controller.
This anomaly first identified in version 20.04.02.

Vendor specific error code (Lgx00137897)

When the controller attempts to open a connection with a 3rd-party device on EtherNet/IP, it causes the device to return a vendor specific error (0x01, 0x320). This error code is interpreted incorrectly in the Logix Designer application Module Properties dialog box, Connection tab.
This anomaly first identified in version 20.01.02.

Allow Unicast Consumer Connections check box (Lgx00159102)

When offline in the Logix Designer application, the Allow Unicast Consumer Connections check box clears or resets itself when changing the Max Consumers value of a safety product tag for the 1756-L73S/A controller, firmware version 20.01.00. This does not occur when modifying a standard product tag.
This anomaly first identified in version 20.01.02.

L1 Controller embedded I/O module firmware (Lgx00127607)

For the L1 controller, the controller’s embedded I/O module firmware may not be updated due to a corrupt embedded I/O module firmware image. For more information, see Rockwell Automation Knowledgebase document 498109.

This anomaly first identified in version 20.01.02.

Drive run at small coarse update period (Lgx00132326)

When the drive is running at small coarse update period such that late or lost Drive-to-Controller (D2C) updates are being seen, the Logix controller extrapolates the actual position during the lost D2C updates. The extrapolation algorithm computed the actual position incorrectly that resulted in incorrect velocity. If the actual velocity is plotted, you will see velocity spikes during lost D2C updates.

This anomaly first identified in version 20.01.02.

L1 Controller remove or insert local expansion POINT I/O modules (Lgx00131054)

For the L1 controller, if you remove or insert local expansion POINT I/O modules while under power, you can cause the controller to experience a Major Non-recoverable fault.

This anomaly first identified in version 20.05.00.

RUN LED on controller shows wrong state (Lgx00133064)

RUN LED on controller shows wrong state if you overload the system with very fast RPI limits on a CompactLogix controller that is communicating with SDN modules. It may cause the Run LED to incorrectly report Run mode when the controller has not finished its transition to the new mode. If this happens, cycle power to the controller and switch to Program mode when power is applied. 

This anomaly first identified in version 20.00.03.

RSLogix 5000 reports fatal error in Ladder instruction (Lgx00125908)

RSLogix 5000 reports a Fatal Error while typing in the tag operand field of a Ladder instruction.

This anomaly first identified in version 19.01.00. 

Fatal error on rung edited online (Lgx00127957)

A Fatal Error is reported when performing a copy and paste operation on a rung that is being edited while online.

This anomaly first identified in version 17.01.01.

Imported routine fatal error (Lgx00128439)

After configuring the import of a routine, if a tag is renamed and the Show differences only Data Comparison option is selected, a Fatal Error could be reported when the routine is imported.

This anomaly first identified in version 20.00.03.

Component tag deletion causes fatal error (Lgx00129693)

When attempting to delete a component of a tag, such as an array element or a structure member, a dialog box is displayed asking users if they wish to delete the entire tag. Clicking No results in a Fatal Error.

This anomaly first identified in version 20.00.03.

Fatal error searching for forces (Lgx00133070)

A Fatal Error can be reported when searching for forces in logic.

This anomaly first identified in version 19.01.00.

Safety modules fail to instantiate after installation of Ethernet module AOP profile 10.00.3664 (Lgx00170167)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Tool tip for undefined tag in Ladder Editor needs improvement (Lgx00176367)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Tool tip for Dest FAL instruction indicates an undefined tag (Lgx00176367)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Safety Lock LED sometimes fails to show correct status after you restore project from SD card (Lgx00178417)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

RSLogix 5000 version 20.06 has this change in functionality since the last release.

These security privileges are not supported in RSLogix 5000 version 20.06.

• Add-On Instruction: Export
• Add-On Instruction: View Logic
• Alarm Definition: Create
• Alarm Definition: Delete
• Alarm Definition: Modify Properties
• Alarm Definition: Modify Required Use
• Alarm: Clear Alarm Log
• Alarm: Configure Direct Command
• Alarm: Create
• Alarm: Delete
• Alarm: Modify Properties
• Alarm: Modify Use
• Routine: Export
• Routine: View Logic
• Sequence: Create
• Sequence: Delete
• Sequence: Manual Control
• Sequence: Modify Properties

For additional information on FactoryTalk Security product policies, see Appendix A of the Logix 5000 Controllers Security Programming manual, publication 1756-PM016.

The Import/Export version number for this version of RSLogix 5000 software is 2.11. This table lists the Import/Export versions for previous releases.

These are the application notes for RSLogix 5000 version 20.06.

Supported Logix Controllers

While the programming software continues to extend its functionality with each new release, the physical controllers that it supports vary. New controllers are added, and in some cases, support for existing controllers may be removed. While a specific controller may not be supported by the current release, the side-by-side installation of multiple versions of the software provide, in most cases, a means to support the older hardware. If migrating from one controller to another, a project created for one controller can be easily converted to another controller using the Controller Properties configuration dialog box within the software.

If opening a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software provides an appropriate warning and automatically provides the option to convert the project to one of the controllers supported by the release.

The table provides a breakdown of the various Logix 5000 controllers and the initial or minimum version of RSLogix 5000 application required to support the controller.

¹ Excludes RSLogix 5000 software version 15.

² Excludes GuardLogix software version 14.

When installing version 20.05 of RSLogix 5000, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:

• When previous versions of the software are installed after version 20.05, 24.02, 28.03, 30.00, and later, .NET Framework 4.6 may cause installation to fail for these earlier versions of the software.
• When installed on 32-bit Windows operating systems, .NET Framework 4.6 causes versions 23.00 and earlier of the software to fail on startup.

• Do not install version 20.05 of the RSLogix 5000 software on a 32-bit Windows operating system on which version 23.00 or earlier of the software is installed.
• Contact Rockwell Automation Support for instructions on disabling the Start page on versions 23.00 or earlier. Disabling the Start page allows the software to start and run.

When installing RSLogix 5000 version 20.06, the installation fails with the message "A higher upgrade is already installed" when FactoryTalk® Linx™ 6.0 software is installed on the computer. The installation fails on RSLinx Enterprise 5.90.

To avoid this problem, do one of these options.

• Restart the Studio 5000 installation and click Custom.

• If the RSLinx Enterprise appears shaded and the check box cannot be cleared:

1. Uninstall FactoryTalk Linx 6.0 from Control Panel > Programs and Features. 
2. Restart the Studio 5000 installation to install the software.
3. When the installation is complete, reinstall FactoryTalk Linx 6.00 on the computer.

For more information, refer to Rockwell Automation Knowledgebase Answer ID 1072383.

When updating the firmware as part of the project download, the Update Module Firmware dialog box may display an error that it cannot find the location of the updated firmware files.

The installation of ControlFLASH version 15.01 moves the DMK files located in the ControlFLASH installation folder (C:\Program Files (x86)\ControlFLASH for 64-bit operating systems or C:\Program Files\ControlFLASH for 32-bit operating systems) to a new folder located in C:\Users\Public\Documents\Rockwell Automation\Firmware Kits.

Older versions of ControlFLASH and Logix Designer place DMK flash files in previous ControlFLASH file locations.

The work around if ControlFLASH cannot find the location of the DMK files:

1. In the Choose Firmware Revision dialog box, click Browse.

2. Depending on the operating system, browse to the location of the DMK files.

• For 64-bit operating systems, browse to C:\Program Files (x86)\ControlFLASH.
• For 32-bit operating systems, browse to C:\Program Files\ControlFLASH

For more information, refer to Rockwell Automation Knowledgebase Answer ID 1071313.

When attempting to go online with a controller that is set up to only allow communications through trusted slots, a failed to go online with the controller error message appears if the communication module is not located in a trusted slot.

Clicking OK to close the error message causes the error message to appear again. Click OK again to close error message.  

When a Flex I/O module is attached to a 1794-AENT adapter, on the General tab in the classic profile, select either Compatible Module or Disable Keying as the Electronic Keying option. Even though Exact Match is available as an Electronic Keying option, Flex modules do not use the Exact Match keying option. Electronic keying is based on an external Flex ID value which does not depend on the module's minor revision.

When using a Custom RSLogix 5000 Motion Database in RSLogix 5000 software versions 12.00 through 17.00, update the motion database to work with versions 18.00 or later. The table lists the motion database revisions used with these application versions.

* Before a Custom Motor can be used in version 18.00 or later, any Custom Motor currently in a motion database file at revision 5.00 or earlier (Motion.db format) must be converted to the newer Motion.mdb format.

To initiate the process of getting the database updated, please email the request to raeptechsupport@ra.rockwell.com. Please include any prior tech support case number if the current database includes non-Rockwell motors.

This version of the software does not install or use MSXML 4.0. MSXML 4.0 has security risks associated with it and is no longer supported by Microsoft. For more information about MSXML and its availability, see the MSXML Roadmap. When installing products or components made by other vendors that use MSXML 4.0, contact the vendor for questions about the security risk associated with MSXML 4.0.

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.

1756 Analog I/O Profile Not Retaining Engineering Units (1486580)

1756 Analog I/O Add-on Profiles allow users to set custom Engineering Units per channel, and these are stored as extended properties in the Studio 5000 Logix Designer application, versions 21 and later.

RSLogix 5000, versions 20 and earlier, does not support extended properties. When you use a 1756 Analog I/O Add-on Profile in RSLogix 5000, versions 20 and earlier, custom Engineering Units are not stored in the profile.