System requirements for Studio 5000 Logix Designer version 28.03

For optimal performance of the Logix Designer application, your personal computer should meet or exceed the following hardware and software requirements.

Hardware Requirements

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

Software Requirements

• Operating system and service pack compatibility:
  • Windows® 10 Professional (64-bit) version 1607
  • Windows 7 Professional (64-bit) with Service Pack 1
  • Windows 8.1 Professional (64-bit) with April 2014 Update Roll-up
  • Windows Server 2008 R2 Standard Edition with Service Pack 1
  • Windows Server 2012 Standard Edition
  • Windows Server 2016

• .NET Framework 4.6

• This version of Logix Designer is expected to operate correctly on all other editions and service packs of the following operating systems but has not been tested:
  • Microsoft Windows 7
  • Microsoft Windows Server 2008 R2
  • Microsoft Windows 8
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2
  • Windows 10
• The following prerequisite software is required with this version of Logix Designer application and will be installed when you install this release:
  • FactoryTalk® Services Platform v2.90.00
  • FactoryTalk® Activation Manager v4.00.02
  • RSLinx Classic v3.90.00
  • RSLinx Enterprise v5.90.00

• On Windows 8 and later, the Adobe® Flash Player ActiveX Control is included with the operating system. On Windows 7, the Adobe® Flash Player ActiveX Control must be downloaded and installed to operate the Logix Designer Start page. The Adobe Flash Player ActiveX Control can be downloaded from Adobe’s website at this URL: http://get.adobe.com/flashplayer/
• FactoryTalk® View Site Edition (SE) software and RSLinx® Enterprise communication software are required in order to fully use alarming capabilities.

• Be sure to check the software requirements for other Rockwell Software® products that you intend to install to be sure that these products are also compatible with the system.

• Logix5000 controllers and ControlLogix Motion modules in your system must contain a revision of firmware that is compatible with this version of the Logix Designer application. 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™.

To check and download the firmware compatible with this version of the Logix Designer application, use the Product Compatibility and Download Center (http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?crumb=112 )

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

New features in this release for Studio 5000 Logix Designer version 28.00

The following new feature and functionality has been added to this release of the Logix Designer application.

Powerflex 755

The Powerflex 755 feature development adds 24-Bit Resolution capability to supported feedback devices and Servo I/O support for Powerflex 755 CIP Motion drives. The 755 CIP Motion drives have also been updated to accept new 11 and 22 Series servo I/O cards that should be placed in slot 7.

SequenceManager

Added in version 28 of the Logix Designer Application, SequenceManager provides the ability to create an Equipment Sequence program to run a single unit batch process within a Logix controller. Used in combination with PhaseManager, SequenceManager follows the ISA-88 methodology for automated batch control. Combining full state model execution, View Site Edition (SE) ActiveX controls, and batch event logging, this product provides flexible and scalable controller base batching solutions to single unit and OEM applications. Note that this functionality will be supported by the 5x80 family of controllers in a future release.

Permission sets and Logical Names

Use permission sets and Logical Names, configured in the FactoryTalk Administration Console, to control access to controller projects. Permission sets and Logical Names identify a set of actions that are allowed or denied for one or more user groups or computer groups. Use permission sets to apply the same permissions to multiple controllers or project components. Use a Logical Name to associate permissions with a specific controller.

Permission sets for project components

You can secure individual tags, routines, and Add-On Instructions with additional or different permissions than those assigned to protect a controller project. For example, you can apply permissions that allow a user to modify some tags, but not others. The security settings that you apply to a specific component override any security policy applied to the overall project.

Permissions for Guest Users

When you configure permission sets and logical names in the FactoryTalk Administration Console, you can also configure permissions for Guest Users. The permissions for Guest Users determine the level of access for users who are not authenticated on the same FactoryTalk directory that the project was secured with.

Secondary security authorities

When a project is protected by a primary security authority, you can configure a secondary security authority. The secondary security authority further restricts Guest Users beyond the permissions granted by the primary security authority. For example, an original equipment manufacturer (OEM) can secure a project with FactoryTalk Services Platform using a primary directory, and an end customer can further secure the project with their own FactoryTalk Services Platform directory.

New Build button on standard Toolbar

For the 5x80 family of controllers, the Build button on the standard Toolbar in Logix Designer application creates binary files compiled from user subroutines and caches them in the project .ACD file. If these binary files are present in the project during a download, then Logix Designer does not have to recompile them, saving time during the download process.

THIS Message to Self addition within Logix Designer

Added the ability to easily perform a message to self by using the word THIS within the communication path of a message instruction.

System Features New features in this release for Studio 5000 Logix Designer version 28

The following new feature and functionality has been added to this release of the Logix Designer application.

Powerflex 755

The Powerflex 755 feature development adds 24-Bit Resolution capability to supported feedback devices and Servo I/O support for Powerflex 755 CIP Motion drives. The 755 CIP Motion drives have also been updated to accept new 11 and 22 Series servo I/O cards that should be placed in slot 7.

SequenceManager

Added in version 28 of the Logix Designer Application, SequenceManager provides the ability to create an Equipment Sequence program to run a single unit batch process within a Logix controller. Used in combination with PhaseManager, SequenceManager follows the ISA-88 methodology for automated batch control. Combining full state model execution, View Site Edition (SE) ActiveX controls, and batch event logging, this product provides flexible and scalable controller base batching solutions to single unit and OEM applications. Note that this functionality will be supported by the 5x80 family of controllers in a future release.

Permission sets and Logical Names

Use permission sets and Logical Names, configured in the FactoryTalk Administration Console, to control access to controller projects. Permission sets and Logical Names identify a set of actions that are allowed or denied for one or more user groups or computer groups. Use permission sets to apply the same permissions to multiple controllers or project components. Use a Logical Name to associate permissions with a specific controller.

Permission sets for project components

You can secure individual tags, routines, and Add-On Instructions with additional or different permissions than those assigned to protect a controller project. For example, you can apply permissions that allow a user to modify some tags, but not others. The security settings that you apply to a specific component override any security policy applied to the overall project.

Permissions for Guest Users

When you configure permission sets and logical names in the FactoryTalk Administration Console, you can also configure permissions for Guest Users. The permissions for Guest Users determine the level of access for users who are not authenticated on the same FactoryTalk directory that the project was secured with.

Secondary security authorities

When a project is protected by a primary security authority, you can configure a secondary security authority. The secondary security authority further restricts Guest Users beyond the permissions granted by the primary security authority. For example, an original equipment manufacturer (OEM) can secure a project with FactoryTalk Services Platform using a primary directory, and an end customer can further secure the project with their own FactoryTalk Services Platform directory.

New Build button on standard Toolbar

For the 5x80 family of controllers, the Build button on the standard Toolbar in Logix Designer application creates binary files compiled from user subroutines and caches them in the project .ACD file. If these binary files are present in the project during a download, then Logix Designer does not have to recompile them, saving time during the download process.

THIS Message to Self addition within Logix Designer

Added the ability to easily perform a message to self by using the word THIS within the communication path of a message instruction.

Rungs missing in routine after online edit with Logix Designer (Lgx00196898, Lgx00200753, Lgx00201030)

Anomaly first identified in Studio 5000 Logix Designer v28

Studio 5000 Logix Designer v28, v29, v30

Corrected Anomaly in Studio 5000 Logix Designer v30.01, v28.03

If online changes are made to a ladder logic routine within a ControlLogix 5580 or CompactLogix 5380 controller and those changes are assembled or tested, and subsequently removed, all rungs within the routine may be removed when the Go Online command in Logix Designer application is used to initiate the edit.

The rungs appear as missing within the Logix Designer editor. Controller projects that have been online edited continue to operate as expected until the Go Online command is used and a subsequent download of the resulting project file is performed.

All of the following conditions must be met for this anomaly to occur:

• The routine must have been created using the Logix Designer ladder logic editor.
• Online edits occurred and edits have been assembled or tested.
• Edits made to a ladder routine have been removed through a cancel operation or re-editing the routine to back out changes that have been made such that the resulting routine has not changed.
• Open a file in Studio 5000 Logix Designer application that does not have the changes and use the Go Online command to connect to the edited controller, forcing correlation of the online version with the offline version.

If these conditions are met, when the affected routine is opened in the Logix Designer ladder logic editor, all rungs within that routine are missing and the number of rungs reported by the Controller Organization within Logix Designer is zero. If the affected routine is opened an empty rung is added and project validation fails. However, if the affected routine is not opened, project validation will pass and allow download of the application to the controller with the affected routine now missing all rungs within the controller.

Important - The rungs appear as missing within the Logix Designer ladder editor, but controller projects that have been online edited continue to operate as expected within the controller until downloaded.

For complete information, see Knowledgebase article 1063358: Product Notice 2017-10-002 Logix Designer Ladder Logic Editor Missing All Rungs in a Routine when Online with Correlation after Online Edits are removed in ControlLogix 5580 and CompactLogix 5380.

Anomalous behavior sometimes occurred when using indirect addressing to a Boolean tag within an Add-On Instruction data type containing an alias parameter.

This anomaly first identified in version 28.03.

Anomalous behavior may occur when using indirect addressing to a Boolean tag within an Add-On Instruction data type containing an alias parameter.

This anomaly first identified in version 28.03.

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

Anomaly First identified in Studio 5000 Logix Designer v24.00

Corrected anomaly with Studio 5000 Logix Designer v28.01

Clearing the Enable Alarm check box does not disable the alarm on the 1794-IF8IHNFXT module when it is configured for 4 to 20 milliamps.

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the "ChxxHAlarmLimit" and "ChxxLAlarmLimit" values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.

Web-based profiles launch as blank or empty windows with multiple instances of Logix Designer running on one PC (5582938)

If a space exists in a Windows username and/or the user shell folder path, and multiple Logix Designer projects are open, web-based user interface profiles will launch as an empty window.

The profiles will launch correctly in a single instance of Logix Designer or in one of the opened projects but trying to launch profiles from additional open projects will display the anomaly.

To work around the anomaly

• Work in one project of Logix Designer at a time.

• Log in as a user with no spaces in the username.

This anomaly will be resolved in an upcoming release of Logix Designer Add-on Profiles.

This anomaly first identified in version 20.00

Filter buttons missing when importing rungs into an AOI (Lgx00156489, Lgx00179907, Lgx00183130, Lgx00183131, Lgx00183132, Lgx00183133)

Anomaly

Studio 5000 Logix Designer v27.00

Corrected Anomaly with Studio 5000 Logix Designer v30.00

When you import rungs into an Add-On Instruction, the following filter options are missing when you click Final Name on the Configure Tag References pane of the Import Configuration dialog box:

• Input

• Output

• InOut

• Local Filter

Only the Show controller tags and Show program tags check boxes are available.  

Find All command fails to find tag names embedded in Structured Text (Lgx00168112)

Anomaly

Studio 5000 Logix Designer v27.00

The Find All command fails to find tag names embedded in Structured Text. (Lgx00168112)

Project containing AOIs fails to download to a safety controller on second attempt (x168232)

Anomaly

Studio 5000 Logix Designer v27.00

A project containing an Add-On Instruction downloads with errors under the following conditions:

• The project is downloaded to a safety controller with the Download Project Documentation and Extended Properties check box unselected.
• The project is uploaded from the controller and the Logix Designer application is taken offline from the controller.
• When offline, the project is downloaded to the safety controller again with the Download Project Documentation and Extended Properties check box unselected, and the following error occurs:

Invalid signature ID. Reseal instruction to resolve. (x168232)

Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger (x168499)

Anomaly

Studio 5000 Logix Designer v27.00

When a project is imported, Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger and the import fails. (Lgx00168499)

Import Configuration Error pane fails to display expected errors and warnings (Lgx00163240)

Anomaly

Studio 5000 Logix Designer v27.00

The Errors and Warnings pane on the Import Configuration dialog box sometimes fails to display expected errors. (Lgx00163240)

Output state user defined value must be 0 when Hold Last State is selected

Studio 5000 Logix Designer v28

A module fault on the 1758-OF8 of: (Code 16#0009) Module Configuration Rejected: Parameter error. Additional Fault Code 16#000e will remain in a fault state after a reset of the slot and when the OK LED is green. As a workaround, the Output State User Defined value must be set to 0 when Hold Last State is selected in the 1756-OF8 module. (Lgx00164117)

Fatal error occurs when deleting uncommitted row in Connection Configuration dialog box

Studio 5000 Logix Designer v28

When working with a program parameter in the Connection Configuration dialog box, if your cursor is in the Name field and you press the Shift +Tab keys to select the entire row and then press the Delete key to delete the row, a fatal error occurs. (Lgx00170925)

Passive hookup tests do not run when Kinetix 6200 drive is in Shutdown state (Lgx00183678)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Removing SD card from controller while flashing firmware can lock up the controller (Lgx00170010)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

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

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Cannot overwrite existing Add-On Instruction when imported and existing AOIs have the same edit date (Lgx00183585)

Corrected Anomaly with Studio 5000 Logix Designer v29.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

RSLogix 5000 Clock Update tool does not work properly on 64-bit Windows 7 (Lgx00124864)

The RSLogix 5000 Clock Update tool does not work properly when it is installed on a 64-bit Windows 7 operating system and executed.

Cannot add 1734-OBV2S modules to I/O configuration (1145619)

When attempting to add a 1734-OBV2S module to the I/O configuration in the Logix Designer application, installed on Windows 10 OS, these errors display:

• "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore the error and attempt to continue.

• "Failed to create model. There was an unspecified failure."

Performing the same workflow in Studio 5000 Logix Designer, installed on Windows 7 OS, does not result in these errors occurring.

Utilizing the application file created on the Windows 7 OS on a Windows 10 OS can still result in errors occurring:

• Module import of Windows 7 OS created file in Windows 10 OS fails when importing module. Error message "Module import failed. No additional information available."
• Fatal error occurs in Studio 5000 Logix Designer when making 1734-OBV2S module configuration changes in Windows 10 OS with file created with Windows 10 OS.

For additional information, refer to this Knowledgebase article: ID: BF26936

This anomaly first identified in version 24.00.

Fatal error can occur accessing an EtherNet/IP Safety device properties in multi-workstation environments of mixed versions of Add-On Profiles (1097239)

RSLogix 5000 Module Profile Core versions earlier than version 26.00 impacts EtherNet/IP Add-On Profile (AOP) device monitoring in Studio 5000 Logix Designer projects versions 24.00 or later.

In a multi-workstation environment where different versions of module AOP exist, it is possible that a mismatch of the version occurs in the ACD file.  When this mismatch is present, a fatal error results when accessing the properties of the Ethernet/IP Safety Device, such as when viewing device properties or copying the device.

To work around this issue, ensure installed device AOP versions match in all multi-workstations.

This anomaly first identified in version 24.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.

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the ChxxHAlarmLimit and ChxxLAlarmLimit values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.  

This anomaly first identified in version 24.00.

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

When an axis gets inhibited, the axis command and actual positions are set = 0.0000. When the axis is uninhibited, the command and actual positions return to their previous values.

This anomaly first identified in version 28.00.

Editing an FBD JSR instruction properties sometimes reverses the order of input and return parameters.

This anomaly first identified in version 26.00.

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.

Major fault in rung calling imported Add-On Instruction (Lgx00230009)

The Logix controller generated a major fault when an Add-On Instruction was imported into the project with an edited import file that was improperly formatted.

This anomaly first identified in version 28.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.

Converting a version 20.00 project that contains an SMC EX250-SEN1 caused numerous errors and missing logic when verifying the project.

This anomaly first identified in version 28.00.

When the Logix Designer application scanned source protection licenses, if licenses were not retrieved, source protected routines were automatically closed.

This anomaly first identified in version 26.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.

Adobe Acrobat Reader DC, used by the Start Pages, causes the Logix Designer application to perform slowly. Version 31.00.00 removed the dependency of requiring Adobe Reader and removed the Start Pages. Access Online Books and Vendor Sample Projects from the Help menu.

This anomaly first identified in version 28.00.

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.

The error Communications request too large for network generates when try to run the trend.

This anomaly first identified in version 28.01.

To work around this issue, remove either the controller scoped tag or one of the local parameters.

With 1756-L8 controllers, when an axis, CIP axis, or Virtual axis is referenced via an InOut Parameter, SSV/GSV commands generate a compiler error, and the routine does not download.

This anomaly first identified in version 28.00.

To work around this issue:

• Remove the connection to the axis.
• Use the controller tag directly in the SSV.

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.

When an axis, a CIP axis, or a virtual axis is referenced using an InOut parameter, motion commands respond as expected. SSV and GSV commands cause the Logix Designer application to return a compiler error.

This anomaly first identified in version 28.00.

When selecting a tag in the Data Context menu in the Add-On Instruction Parameters and Local Tags dialog, the Properties pane displayed the description and project documentation for a tag from the Add-On Instruction Definition Data Context but not from the Add-On Instruction Instance Data Context. Editing the description and properties in this case did not change the description and properties for the selected Data Context tag, but instead changed the description and properties for the Add-On Instruction Instance Definition.

This anomaly first identified in version 28.00.

The Logix Designer application had a compiler error when finalizing online edits or when creating a project offline. This anomaly was only present in ControlLogix 5580, CompactLogix 5480, and CompactLogix 5380 controllers, and Windows 10 workstations that use Microsoft AppLocker.

This anomaly first identified in version 28.00.

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.

When the Logix Designer application scanned licenses on a dongle, when licenses were not retrieved, the application closed the source protection routines.

This anomaly first identified in version 26.00.

Labels are cut off and dislocated in BOOTP-DHCP Server applications (Lgx00152848)

When the font size in Windows 7 is set to 125%, the labels in the Network Settings and DHCP properties of BOOTP-DHCP Server application are cut off, making them unreadable. They are also dislocated, where they do not match with the proper input fields.

This anomaly first identified in version 23.00.

Copy and Paste from one language switching project to another fails to paste project documentation and extended properties (Lgx00162447)

Project documentation, extended properties, and custom properties are not included when you copy and paste project components from one language-switching project to another.

This anomaly first identified in version 26.00. (fixed in 29)

Filter buttons missing when importing rungs into an AOI (Lgx00156489)

When you import rungs into an Add-On Instruction, the following filter options are missing when you click Final Name on the Configure Tag References pane of the Import Configuration dialog box:

• Input
• Output
• InOut
• Local Filter

Only the Show controller tags and Show program tags check boxes are available.

This anomaly first identified in version 23.00.

Find All command fails to find tag names embedded in Structured Text (Lgx00168112)

The Find All command fails to find tag names embedded in Structured Text.

This anomaly first identified in version 26.01.

Project containing AOIs fails to download to a safety controller on second attempt (Lgx00168232)

A project containing an Add-On Instruction downloads with errors under the following conditions:

• The project is downloaded to a safety controller with the Download Project Documentation and Extended Properties check box unselected.
• The project is uploaded from the controller and the Logix Designer application is taken offline from the controller.
• When offline, the project is downloaded to the safety controller again with the Download Project Documentation and Extended Properties check box unselected, and the following error occurs: Invalid signature ID. Reseal instruction to resolve.

This anomaly first identified in version 26.01.

Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger (Lgx00168499)

When a project is imported, Logix Designer fails to set a default value for ProgrammaticallySendEventTrigger and the import fails.

This anomaly first identified in version 27.00. 

Import Configuration Error pane fails to display expected errors and warnings (Lgx00163240)

The Errors and Warnings pane on the Import Configuration dialog box sometimes fails to display expected errors.

This anomaly first identified in version 24.00. 

Logix Designer shuts down when WIBU detects malicious debugger (Lgx00165361)

When WIBU AxProtector detects a potentially malicious debugger application, Logix Designer shuts down. As a workaround, disable debugging applications that are running on your computer and restart Logix Designer.

This anomaly first identified in version 26.00.

Clearing the Enable Alarm check box does not disable the alarm on the 1794-IF8IHNFXT module when it is configured for 4 to 20 milliamps (Lgx00156945, Lgx00158243, Lgx00160986)

When alarm is triggered, clearing the Enable Alarm check box on the Alarm tab does not disable the high and low alarms. The Enable Alarm parameter controls only the Loop/Remote alarms, therefore clearing the Enable Alarm check box disables only the Loop/Remote alarms.

To disable the High and Low alarms, set the "ChxxHAlarmLimit" and "ChxxLAlarmLimit" values in the controller tags to zero, and then clear the Enable Alarm check box on the Alarm tab.

This anomaly first identified in version 24.00. 

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.

L5X file type allows spaces in Alias Tag name (Lgx00155383)

A tag name in an L5X file that contained spaces was imported and opened in a project. A space is not permitted in tag names and spaces cannot be entered in tag names in the Tag Editor.
This anomaly first identified in version 21.03.02.

Module Definition Change button with 1756-L71 (Lgx00167916)

When creating a new project with a 1756-L71 controller on EtherNet/IP, adding a 1756-CNB module, clicking the Change button under Module Definition, and then switching the input or output module, causes the Logix Designer application to lock and lose functionality.
This anomaly first identified in version 23.00.00.

Error changing slot positions for Point I/O module (Lgx00190599)

When adding a module to a Point I/O rack offline, the module is configured for slot 1 by default. When updating the module profile with the correct slot position and downloading the project to the controller, error 16#0205 occurs.
This anomaly first identified in version 28.02.01.

Follow these instructions to work around the issue:

Go offline, remove the module, and add it again in the correct slot.

Converting a generic Ethernet safety module to a later version (Lgx00195596)

If a project containing a generic Ethernet safety module is converted from one version of the Logix Designer application to a later version, changes to the safety configuration signature ID are not deleted. The connection to the safety device keeps running after the safety configuration signature is changed. If the generic Ethernet safety module is deleted and re-added to the project, then the safety configuration signature works as expected.
This anomaly first identified in version 24.00.00.

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.

MCAO default value zero (Lgx00188302)

Axis attribute number 608, Zero Speed, had its default value changed from 0.00 to 1.0% Motor Rated. This change was made to address potential problems in vertical-load applications.
This anomaly first identified in version 28.00.00.

Out of range attribute and ACD file (Lgx00182216)

It is possible for users to push an axis attribute out of range. This is typically done when an SSV is in the controller, and the user saves or uploads the project. Save the file by exporting it as an L5K or L5X file. Upon import of the L5K file, the out of range attribute is corrected and a waning message opens. Upon import of an L5X file, the axis is deleted. This deletion of the L5X file is by design.
This anomaly first identified in version 28.00.00.

Missing rungs of logic (Lgx00196898)

When going online with the controller with an existing project, the uploaded copy of the project has missing rungs of logic. When the project is uploaded to a new project, the rungs of logic show in the project.
This anomaly first identified in version 28.02.00.

Not enough memory (Lgx00190656)

The Logix Designer application runs out of memory when uploading a large amount of tag data at one time.
This anomaly first identified in version 28.02.01.

To work around this issue:

Free up memory before saving. For example, close all routine windows, tag editors, and property pages.

Do not upload tag data values when saving.

Repeatedly load a few records at a time.

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.

Recent projects overridden (Lgx00197976)

When opening a project in Studio 5000 Logix Designer, all Studio 5000 Logix Designer and RSLogix 5000 recent projects are overridden by the most recent saved project.
This anomaly first identified in version 21.03.02.

Fatal error when saving RSNetWorx™ for EtherNetIP project (Lgx00192550)

Studio 5000 Logix Designer has a fatal error when saving a project using an RSNetWorx for EtherNet/IP file that is embedded in a 1756-EN2T in slot 0 and a 1756-L73S in slot 1/2 during the merging connection output step.
This anomaly first identified in version 27.00.01.

Studio 5000 Logix Emulate™ (Lgx00180272)

Studio 5000 Logix Emulate upload fails with Logix 5000 Services

An ACD file uploads successfully from AssetCentre but with the error message Can't open the specified RSLinx driver.
This anomaly first identified in version 24.01.00.

MGSD can cause Group Overlap faults in systems with large number of axes (Lgx00174272)

The Motion Group Shutdown (MGSD) instruction can cause a Motion Group Overlap fault when used in a project that contains a large number of axes and the Coarse Update Rate is set too low.

As a workaround, increase the motion group's coarse update rate.

This anomaly first identified in version 28.00.01. 

When an AOI that was sealed in a project that used a specific documentation language (English, for example) is imported into a project where the documentation language is different (Italian, for example), the project cannot be verified.

Important: As a result of a correction of this anomaly, AOI signatures that were signed in a previous version of RSLogix 5000, or Studio 5000 Logix Designer will break upon import or project conversion into version 29.00 of Studio 5000 Logix Designer. You must un-seal and then re-seal each AOI to get a new signature.

This anomaly first identified in version 28.00.00.

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Find All search limited to Edit Zones produces incorrect results (Lgx00139950)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Find All search limited to Edit Zones produces incorrect results (Lgx00139950)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

GCC Compile Error occurs when project contains ALMA instructions in FBD routine (Lgx00137675)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Go To dialog context varies within FBD Editor (Lgx00143603)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

The Go To dialog context varies within the Function Block Diagram (FBD) Editor.

This anomaly first identified in version 23.00.01.

Remove Alarm Buffer object from GSV/SSV instructions (Lgx00138886)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Remove the Alarm Buffer object from the GSV/SSV instructions. (Lgx00138886)

This anomaly first identified in version 21.00.03.

Enhanced Cam Editor not fully disabled even when Maintain Project permission has been denied (Lgx00029563)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

The Enhanced Cam Editor is not fully disabled even when Maintain Project permission has been denied for the user.

This anomaly first identified in version 11.16.00.

Firmware cannot be updated after licensed connection key has been revoked (Lgx00168994, Lgx00169634, Lgx00156630)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

When the controller contains firmware that has revoked the licensed connection key for older revisions of software, those older revisions of software cannot establish a connection with the controller in order to flash the controller back to a compatible revision of firmware.

This anomaly first identified in version 21.00.03.

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

Logix Designer application does not differentiate between source key names when first five characters of source key names are the same (Lgx00179531)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Empty Action body while editing a Sequential Function Block routine online (Lgx00178412)

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

Commissioning tests stay in testing phase and do not complete (Lgx00177511)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Position Unwind not calculated correctly on Axis Parameter List dialog box (Lgx00179155)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Errors and Warnings pane on Import Configuration dialog box sometimes fails to display errors (Lgx00163240)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Creating alias for Cam, Cam Profile, or Output Cam tag generates error (Lgx00180076)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Logix Designer fails to set default value for ProgrammaticallySendEventTrigger and import fails (Lgx00168499)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Add instruction error code 111, "An Axis With Maximum Acceleration of Zero is Invalid" (Lgx00179479)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Two public parameters aliased to the same local program scoped tag (Lgx00175994)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Using JSR with SBR instruction to pass parameters to routine and RET instruction (Lgx00177196)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Handling of Source Key names is different in v28 project than in a v24 project (Lgx00179531)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

When you lock a safety task and generate a signature, Logix deletes all comments in safety task (Lgx00177873)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Guest Users cannot flash 1756-L7x controller firmware using Autoflash (Lgx00183696)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Position unwind not calculated correctly (Lgx00179155)

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

Removing SD card from controller while flashing firmware can lock up the controller (Lgx00170010)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

Performance problems during various security actions related to Wibu on Windows 7 (Lgx00171830)

Corrected Anomaly with Studio 5000 Logix Designer v29.00

The Logix Designer application crashes after multiple cross references (Lgx00208989)

Logix Designer crashes with the error 0xc0000005 after selecting Go to Cross Reference and then closing the open window more than three times.

This anomaly first identified in version 21.03.

Error when running trend (Lgx00204911)

Running a trend generates a Communication request too large for network error.

This anomaly first identified in 28.01.

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.

Fatal Error 0xe06d7363 Adding Devices to the I/O Configuration (2159635)

This anomaly affects European-based Windows Operating Systems.

An anomaly exists in Add-on Profiles that could cause a fatal error to occur when adding certain devices to the I/O configuration or when opening these device profiles in an existing project.

This anomaly was corrected in the Add-on profiles released with the Logix Designer application v36.00, v35.01, v34.03, v33.03.

This anomaly was first identified with the Add-on profiles that were released with the Logix Designer application v35.00, V34.02, and v33.02. For additional information, please reference ID: QA65946.

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.

• GuardLogix 5570 Family with firmware versions earlier than 30.011
• Compact GuardLogix 5370 family with firmware versions earlier than 30.011
• GuardLogix 5560 family with firmware versions 20.018 or earlier (latest firmware is version 20.018)

• GuardLogix 5580 family SIL2/SIL3, all firmware versions
• Compact GuardLogix 5380 family SIL2/SIL3, all firmware versions

Functional changes in Studio 5000 Logix Designer version 28.03

Studio 5000 Logix Designer version 28.03 has the following changes in functionality since the last release.

Installation wizard

The entire installation has been automated for ease and convenience. The wizard is used to install Logix Designer and supporting applications on your system. After you select the software you want to install, the installer prepares the files needed for that version of software. After the files are prepared you choose from two installation methods:

• Install now - Installs the components available on your system using the recommended settings.
• Customize - You choose which components to install.

Tip: Keep the following considerations in mind before installing the Logix Designer application:

• Some antivirus software blocks or disrupts the Studio 5000 environment installation. If you experience difficulty, try disabling your antivirus software before installation.
• Make sure that you have Administrator privileges on the computer on which you want to install the Studio 5000 environment.

Import/Export

The Import/Export version number for version 28.03 of Logix Designer application is 2.19. The following table lists the Import/Export versions for previous releases.

The following are the application notes for Logix Designer version 28.03.

While the programming software continues to extend its functionality with each new release, the physical controllers that it supports will 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 will, in most cases provide a means to support the older hardware. If you decide to migrate 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 you open a project that is configured for a controller that is no longer supported and the older version of software is not installed, the software will provide an appropriate warning and will automatically provide the option to convert the project to one of the controllers supported by the release.

Installing Studio 5000 Logix Designer version 28.03 automatically installs Microsoft .NET 4.6. However, .NET 4.6 can cause the following issues:

• When previous versions of Logix Designer are installed after versions 28.03 and 30, .NET 4.6 may cause installation to fail for these earlier versions of the Logix Designer application.
• When installed on 32-bit Windows operating systems, .NET 4.6 causes versions 23 and earlier of the Logix Designer application to fail on startup.

Follow one of these steps to work around the issue:

• Do not install version 28.03 of the Logix Designer application on a 32-bit Windows operating system on which you also run version 23 or earlier of the Logix Designer application.
• Contact Rockwell Automation Support for instructions on disabling the Logix Designer Start page on versions 23 or earlier. Disabling the Start page allows the Logix Designer application to start and run.

•   To install the software with no user interface using the default settings during the installation process. (Unattended install)

Setup.exe /Q /IAcceptAllLicenseTerms

•   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. (Silent install)

Setup.exe /QS /IAcceptAllLicenseTerms /AutoRestart /SetupLanguage=CHS /InstallDrive=D:

If you use a Custom RSLogix 5000 Motion Database in RSLogix 5000 software version 12 through 17, you need an updated motion database to work with versions 18 or later. The following table lists the motion database revisions that are used with these application versions.

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