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

Tip: The Logix Designer application 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 1803, 1809, 1903, and 2004
• Windows Server 2012 R2 Standard Edition
• Windows Server 2016 Standard Edition
• Windows Server 2019 Standard Edition

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

• This version of the Logix Designer application 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, 1703, 1709, 1809)
• Windows 7
• Windows Server 2008 R2
• Windows 8
• Windows Server 2012

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

• FactoryTalk® Services Platform v6.21
• FactoryTalk® Activation Manager v4.04 (v4.05 is acceptable to use with v33.00 of the Logix Designer application)
• FactoryTalk® Linx™ v6.21
• RSLinx Classic v4.21

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

Preferred operating systems are prioritized for support, testing, and post-release patch qualifications. These operating systems are preferred for this release:

• Windows 10 Professional (64-bit)
• Windows Server 2016 Standard (64-bit)
• Windows Server 2012 R2 Standard (64-bit)

Windows 10 v1703 / Windows Server 2016 or later is the recommended operating system if running this software with a 2K or 4K High Resolution Display with scaling up to 125%.

Acceptable results can also be expected with:

• Logix Designer v31.00 or later
• Windows 8.1 / Server 2012 R2 minimum

Windows 7 / Windows Server 2008 is not recommended for display scaling greater than 125%.

Install one or more functionalities for FactoryTalk Updater:

FactoryTalk Updater Agent collects information and activation license data from the Rockwell Automation software installed on the computer. Install the FactoryTalk Updater Agent on each computer that requires data collection. This is the default functionality installed with most Rockwell Automation software.

FactoryTalk Updater Server:

• Communicates with online FactoryTalk Updater Agents to receive collected data.
• Connects to the Product Compatibility and Download Center to retrieve the latest software information.
• Responds to requests from the FactoryTalk Updater Client.
• Supports ~100 online Agents.

Tip: To avoid issues, limit FactoryTalk Updater Server installations to one instance per intranet.

FactoryTalk Updater Client is the user interface that displays information collected by the FactoryTalk Updater Server. Install FactoryTalk Updater Client to display information from the intranet.

• 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).
• Logix 5000 controllers and ControlLogix Motion modules 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™.

Tip: Most modules use Flash-ROM for the storage of firmware. If a module requires a firmware change, use the ControlFLASH™ tool or the ControlFLASH Plus™ tool to perform the update to the Flash-ROM. These tools are contained in the downloaded image or on a DVD-ROM shipped with the Logix Designer application. 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, or the ControlFLASH Plus Quick Start Guide, publication CFP-QS001.

Rockwell Automation tests software products under a standard configuration of operating systems and antivirus software. For additional information, see the Knowledgebase Document ID: PN24 - Rockwell Software Products and Antivirus Software.

Logix Designer application version v33.01 has the same new and enhanced features and new supported hardware as v33.00.

• P-controllers

• Instruction usage

• Tasking model

• HART digital data

• HART Dynamic Variables (PV, SV, TV and QV) values with engineering units and variable status, and the digital value of the device’s analog loop current (in milliamps DC).
• Analog range (min, at 4 mA, and max, at 20 mA).
• Analog units of measure.
• Device information such as Tag and Description text.
• Additional device status (HART “Command 48 additional status” bit array).
• Lookup of diagnostic message and severity based on the Command 48 bits that are set (for the first three diagnostics found in the array).
• Additional status information received from the device via HART, such as Field Device Status bits.

• Redundancy support in new ControlLogix 5580 standard controllers

• Automatic Diagnostics

• Controller web page

• Adding extended properties to alarm messages and Add-On Instructions

• Sorting alarms by state while online

• Navigating to cross references for alarm input and target tags

• Navigating to first and next destructive references for a tag

• Additional Function Block Functions and 64-bit data type instruction support

• Controller and Logical Organizers

• Exporting files

• Logix Emulate

This table lists new hardware supported in this release.

The version of FactoryTalk Linx software provided with this version of the Logix Designer application includes an updated set of electronic data sheet (EDS) files for Rockwell Automation products. Installing this software ensures that FactoryTalk Linx software and RSNetWorx software will be able to work with the new revisions of firmware. To download and install the latest EDS file, access the Rockwell Automation Services & Support website (http://www.rockwellautomation.com/global/support/downloads.page?).

Error: 1746-HSCE Failed to modify properties. Connection failure. (1685002)

Error Failed to modify properties. Connection failure. occurs when changing the configuration of a 1746-HSCE module connected to a 1747-AENTR while online.

The same error occurs with the 1746-HSCE2 module after the above-described error occurs with the 1746-HSCE module. Following a controller download, no configuration errors occur when changing the configuration of a 1746-HSCE2 module until an error occurs while attempting to change the configuration of a 1746-HSCE module connected to a 1747-AENTR while online.

To work around this issue, consider:

• Using a version of the Studio 5000 Logix Designer application other than v32.xx.
• When using v32.xx of the Studio 5000 Logix Designer application, make changes to the 1746-HSCE module offline and download those changes to avoid the anomaly, which prevents online property modification.

This anomaly first identified in version 32.00.

Warnings about unable to set attributes for map connection will be observed while importing an L5K project file that contains any of the following modules: 1794-IE8HB, 1794-IF8IH, 1794-OE8HB and 1794-OF8IH. Use and L5X project export or delete the modules before exporting to L5K.  

This anomaly first identified in version 30.00.

PAO/PPID instruction issue (1045247)

Shed value (Cfg_CVIntlk) is limited to less than 100% when it should be less than or equal to 100%.

As a work around, enter Cfg_CVIntlk = 99.999 %

This anomaly first identified in v33.00.

Upload rejects tag suffix greater than three characters (1218803)

The Logix Designer application verifies and downloads an I/O tag suffix with three or more characters, but does not allow the upload of the tag.

This anomaly first identified in version 33.00.

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

When attempting to upload modules from the controller, the Logix Designer application generates these errors:

• Error: Couldn't be found
• Error: Failed to upload modules

This anomaly first identified in version 32.00.

Using the shortcut combination Alt, plus, and dash did not close routine windows and caused the Logix Designer application to become unresponsive. This effects versions 31.00 and later.

This anomaly first identified in version 31.00.

Importing a CSV file of tags into the Logix Designer application requires more time than in prior releases to complete.

This anomaly first identified in version 33.00.

License Source Protection and locked content not compatible (925976, Lgx00229625, Lgx00229626)

When importing, cutting, copying, or pasting License Source Protected and locked routines and Add-On Instructions that contain GSV or SSV instructions, an error message states that Licensed Source Control content is newer and not compatible. Licensed Source Protected and locked routines and Add-On Instructions that do not contain GSV or SSV import, cut, copy, and paste without an error message.

This anomaly first identified in version 31.00.

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.

Incorrect calculation of Motion Counters per Unwind Cycle (1108548)

The Logix Designer application calculated an incorrect number of Motion Counts/Unwind Cycle value.

This anomaly first identified in version 32.00.

A comment in an imported routine in a Structured Text Add-On Instruction loses the closing parenthesis upon import forcing the user to add the closing parenthesis to successfully download the file.

This anomaly first identified in version 32.03.

To work around this issue, add a space before the forward slash (* /*).

The Logix Designer application stopped responding with the error 0xc0000005 after switching SFC routines while online in edit mode.

This anomaly first identified in version 33.00.

For the ControlLogix 5380 and 5580 controllers, a Boolean InOut parameter in an Add-On Instruction when referencing the .31 bit of a DINT on the outside of the Add-On Instruction, sets the 22nd bit, not the 32nd bit, of that DINT.

This anomaly first identified in version 30.00.

Axis Properties do not reflect SSV changes to bit attributes (00234015, 1063469)

After executing an SSV instruction on a motion axis, the instruction correctly sets the attribute value, but the axis properties does not reflect the change.  See technote BF27663 for additional details.

This anomaly first identified in version 31.00.

Changing the Major Revision Keying of a Kinetix Drive sometimes affects Axis Parameters (1010610, 1010618)

Changing the firmware Major Revision Keying in the properties of a Kinetix drive could affect the scaling (Load Type parameter), as well as other axis parameters, of the associated CIP Motion Axis. This sometimes causes motor performance changes, different from their original configuration. See technote BF27045 for additional details.

This anomaly first identified in version 32.00.

Upload failure (1024944)

When attempting to upload a project, the Logix Designer application generates these errors and the upload fails:

• Error code: 731-0

• Error: [Routine Name]: Logic reconstruction data may be corrupted (displays in Error pane).

To work around this issue, remove long names from the project.

This anomaly first identified in version 32.00.

Tag based alarm does not create on import (1093641)

If Logix based alarms are not verified or created when importing a User-defined Data Type (UDT) that references them, users will experience a controller major non-recoverable fault (MNRF) after download.

This anomaly first identified in version 33.00.

The Logix Designer stops responding when copying motion axes (1170662)

When copying and pasting motion axes between motion groups, the Logix Designer stops responding.

This anomaly first identified in version 32.00.

Safety I/O Add-On Profile Automatic Diagnostic online setting edits makes Add-On Profile unstable (1172072)

For 5094 Safety Discrete I/O Automatic Diagnostic Add-on Profile build v2.2.2, Automatic Diagnostic is enabled by default. If users disable Automatic Diagnostics while the Add-On Profile is online, after applying the change, the Logix Designer application generates a Failed to modify properties error message and the Add-On Profile stops responding.

To work around this issues, go offline, delete the module, and add it again.

This anomaly first identified in version 33.00.

Not enough graphics resources to perform the operation requested. Closing windows will free graphic resources (1623620)

Closing SFC routines online in run mode causes a Windows GDI object memory leak. When this occurs, this window’s operating system dialog box may appear.

When the anomaly occurs, the online project can be saved but opening any other windows results in the dialog box appearing.

The workaround is to close the Logix Designer application session and start a new Logix Designer application session.

This anomaly first identified in version 31.00.

Displayed alarm fields may not update when modified programmatically (1541337)

Alarm behavior functions properly with the programmatically modified value; however, the Alarm List and Alarm Properties dialogs box might display values that existed before the programmatic modification.

Saving the file, uploading tags, and reopening the dialogs updates the Alarm List and Alarm Properties to the current value.

This anomaly first identified in version 32.03.

This anomaly corrected in version 36.00.

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.

Removed KNOptimassMfc400 profile (2106380)

The KN profile no longer has a license in the Logix Designer application.

This anomaly first identified in version 32.02.

Motion Coordinated Linear Move (MCLM) Instruction Show ??'s for V_X, V_Y, V_Z Axes Positions (2069950)

In the Motion Coordinated Linear Move (MCLM) instruction, if the Position operand is defined with an array tag and the array pointer is set at element 1 or greater, axes V_X, V_Y, V_Z appear as question marks “??” instead of their respective positions.

This anomaly only occurs with direct array references. This will not occur with indirect addressing of the array tag.

This is a display anomaly that does not affect the instruction’s functionality.

This anomaly corrected in version 36.00.

This anomaly first identified in version 33.00.

Using specific set of characters in structured text outlining comment, will cause an upload failure into a blank project ACD file (2207451)

Using the ** set of characters with a single-line comment (//) (that is, //**) in a structured text outlining comment (#region\#endregion) causes an upload error into a blank ACD file. The ** characters are used for multi-line comments and using the ** characters with a single-line comment causes this anomaly to occur. 

To work around this issue, put double quotes around the ** characters, such as “**”.

This anomaly first identified in version 31.00.

Defined alarm members of UDTs can be lost in editing process (2339160)

Editing an existing UDT that contains alarms and involves UDT nesting can result in a different UDT losing defined alarm members.

This anomaly first identified in version 31.00.

This anomaly corrected in version 36.00.

Dialogs undocked, split, or set to auto-hide provide unpredictable results for F4 key (2335181)

When dialogs in the Logix Designer application are undocked, split, or set to auto-hide, the F4 key produces unexpected results.

This anomaly first identified in version 31.00.

This anomaly corrected in version 36.00.

Failed to import file occurs during AOI import (2239485)

When an Add On Instruction (AOI) with the same name and one or more matching signature entries is imported with Overwrite option an error occurs. NOTE: The error occurs with signed and unsigned AOIs.

Error message in popup window:  Failed to import file ‘C:\….L5x.’ The import was canceled due to errors.  No changes were made to the project.  See Output Window Errors tab for details.

Error message in Output Window Errors tab:  Error:  Unable to import “AOI name here”, The Import was cancelled due to a name collision (Name=' ').

Workarounds:

Unsigned AOIs: clear the signature history on the AOI that already exists in the ACD file.

Signed AOIs: remove the signature from the AOI that already exists in the ACD file.

This anomaly first identified in version 32.00.

This anomaly corrected in version 36.00 and 36.01.

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.

For more information on this anomaly and workarounds, please see technote ID BF30201.

This anomaly first identified in v20.05.

When importing and exporting programs or routines with Public program parameters between projects, the program or routine causes the parameter to appear undefined. 

This anomaly first identified in version 24.00

The Tag Browser may disappear behind the Watch view preventing the user from selecting a tag. This can happen when the Watch view is in Auto Hide mode, the user opens the Tag Browser from the Watch view, and the Tag Browser appears outside the Watch view.

This anomaly first identified in version 32.00.

Use one of these steps to work around the issue:

• Dock the Watch view by selecting in the Watch title bar.
• Float the Watch view by selecting in the Watch title bar and selecting Float.

Size the Watch view so the Tag Browser fits inside the Watch view.

Some browsers (particularly the Microsoft Edge browser) may not launch the hyperlinks in the Sample Projects.pdf file when the hyperlinks are configured to open PDF files.   

This anomaly first identified in version 32.00

To work around this issue, open the PDF file with Adobe Acrobat Reader:

• Right-click the Vendor Sample Projects.pdf file and select Open with Adobe Acrobat Reader.

The Accelerate 3D Graphics setting in VMware sometimes causes the Logix Designer application to run out of memory.

This anomaly first identified in version 32.00.

Use one of these steps to work around this issue:

• In VMware, turn off the Accelerate 3D Graphics setting.
• Modify VMware Tools and remove the offending VMware SVGA 3D. This causes the display adapter to revert to Microsoft Basic Display Adapter mode.
• Upgrade VMware Workstation to version 15, which uses VMware SVGA 3D driver v8.16.1.1.

In the Tag Editor with Show: Consumed tags displayed, selecting all the consumed tags can cause the Logic Designer application to freeze.

This anomaly first identified in version 32.00.

• To work around this issue, press Esc. When an error message window appears that asks Do you want to abort the operation, select Yes.

Leaving multiple routines open for over two days while online with the controller can cause the Logix Designer application to crash.

This anomaly first identified in version 32.00.

Subroutine called by locked routine through JSR instruction might not show energized power rail (Lgx00218331)

When a locked routine uses a JSR instruction to call a subroutine, Logix Designer sometimes fails to display the power rails in the subroutine as energized. The problem is limited to the incorrect display; the execution flow in the controller is still correct.

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

Source protected routine or Add-On Instruction not executing after download (1312820, Lgx00233725)

Licensed-based Source Protected routines or Add-On Instructions in a Logix Designer application stop executing after a download, when a routine or Add-On Instruction is locked online and previously compiled data was deleted during the Compact operation.  See technote 1132965 for additional details.

This anomaly first identified in version 30.00.

Error in the content of Studio 5000 Logix Designer application generated reports (1421415)

"ACD filename - Label does not exist" appears at the top of the page instead of "ACD filename - Controller Organizer Listing" when using the Generate Report menu option. 

This anomaly first identified in version 33.00.

Error when attempting to run a trend (1435208)

The Logix Designer application is unable to run a trend in v29 or earlier after switching communication software from RSLinx Classic to FactoryTalk Linx in another instance of the Logix Designer application v31 and later on the same workstation.

Once a trend is run in the Logix Designer application v31 and later, using FactoryTalk Linx as the communication software, you will receive this error message if you then attempt to run a trend in the Logix Designer application v29 or earlier on the same workstation:

Error: <trend name> - : Can’t open the specified RSLinx driver.

For more information, refer to the technical note BF23206.

This anomaly first identified in version 20.00.

Module Info B tab empty (1815893)

An anomaly in the AOP core (v26.32.51.0) installed with v34.00 Studio5000 Logix Designer prevents redundant 1715-AENTR and 1715 IO modules Module Info B tab from displaying information while online. 

Consider these work arounds:

• Use an MSG instruction as documented in AID 55301 and AID 55305
• Reference the backing tags of the 1715 adapter :S tags and 1715 IO :I tags

This anomaly first identified in version 20.05.

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.

Studio 5000 Logix Designer Ladder Diagram routines may stop execution after download (2047296)

Studio 5000 Logix Designer ladder diagram routines may stop execution after download to ControlLogix 5580, GuardLogix 5580, CompactLogix 5380, 5480 and Compact GuardLogix 5380 controllers. See Product Notice ID: PN1620 for the specific sequence of events to experience this anomaly.

This anomaly first identified in version 31.00.

Fatal Error 0x80042001 when creating an Add-On Defined output parameter in a routine (1731323)

Fatal error 0x80042001 could occur when creating a new control tag for an Add-On Instruction (AOI) and setting the control tag as an output program parameter.

This fatal error will occur when the tag is created directly from the instruction within the routine. 

This fatal error will not occur if the tag is created from the tag data tables.  

Reference technote BF29394 for additional information.

This anomaly first identified in version 31.00.

Upload error: Logic reconstruction data may be corrupted (2180963)

Converting a file to a newer revision that includes structured text application code in a routine or Add-On Instruction with #Region defining the beginning of a collapsible outline segment but omitting the #EndRegion defining the ending results in the verified and downloaded file generating the error Logic reconstruction data may be corrupted during upload.

Issues within the application code can be identified by:

1. Exporting the file as L5K or L5X.
2. Importing the file.
3. Building the file after the import identifies the missing #EndRegion instances with errors.

This anomaly first identified in version 33.00.

This anomaly corrected in version 36.00.

SSV attribute must be uploaded (1721849)

When working with the Get System Value (GSV) and Set System Value (SSV) instructions in standard and safety tasks, the SSV attributes must be uploaded to be saved to the project.

This anomaly first identified in v32.00.

Logix Designer version 33.01 has these changes in functionality since the last release.

These features are not supported after redundancy is enabled:

• License Source Control
• Controller Ethernet port
• Event tasks
• Inhibited tasks
• Motion groups, axes, and coordinate systems
• Unicast connections

For additional information about redundancy restrictions and functionality, refer to these user manuals:

• ControlLogix Redundancy User Manual, publication no. 1756-UM535.
• ControlLogix 5580 Redundant Controller User Manual, publication no. 1756-UM015.

In Logix Designer releases v32.00 and earlier, string comparison instructions (EQU, for example) do not reflect an error in rung condition output when the LEN member of a string is invalid (larger than the number of characters the buffer can hold). In v33.00, the instruction generates a minor fault and sets the rung to false. After you update to v33.00 software and firmware, projects that contain an invalid string error behave differently: rungs that were true now become false.

Rockwell Automation recommends testing conversion of projects that contain locked routines or locked Add-On Instructions before distribution. Some projects require unlocking of routines and Add-On Instructions before the project can successfully convert to this version of the Logix Designer application. (Lgx00221920)

Starting with version 33.00, the AutoTune license is removed from Full and Professional editions of the Logix Designer application. AutoTune is available as an Add-On to all editions.

Starting with Logix Designer application version 33.00, the default communication software is FactoryTalk Linx. If another version of the Logix Designer application has not been installed on the machine, then FactoryTalk Linx is the default communication software. If a previous version of the Logix Designer software was installed on the machine, then the previously chosen communication software will be used. FactoryTalk Linx communication software must be used to support CIP Security communication with controllers. To change the communication software:

1. Open Logix Designer.

2. Close any open projects.
3. Select Communications > Select Communication Software.
4. In Select Communication Software, choose FactoryTalk Linx, then select OK.
5. A verification message appears with information about some controllers not being supported by FactoryTalk Linx. Select OK.

When you upload through FactoryTalk Linx, if the project uses motion, a large connection size (4,000 bytes) is not used to reduce motion jitter.

The Import/Export version number for this version of Logix Designer application is 2.24. The table lists the Import/Export versions for previous releases.

These are the application notes for Logix Designer version 33.01.

When going online with the controller with the Download Project Documentation and Extended Properties option cleared, online edits did not save after making online edits to Ladder Logic routines, saving and copying the project, going offline, and then going online with the copied project. (Lgx00230263, Lgx00230366, Lgx00230369, Product Safety Advisory 2017-10-002)

To help meet secure system design requirements, review these publications:

• Configure System Security Features User Manual (publication SECURE-UM001)
• System Security Design Guidelines (publication SECURE-RM001)
• Converged Plantwide Ethernet (CPwE) Design and Implementation Guide (publication ENET-TD001)

To learn about implementing CIP Security, see CIP Security with Rockwell Automation Products (publication SECURE-AT001).

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 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 will provide an appropriate warning and will automatically provide 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 Logix Designer application that is required to support the controller.

One method to restore or reset Workstation Options is to hold Ctrl + Shift, launch the Logix Designer application, and continue to hold Ctrl + Shift until the application is fully launched.

However, when this restore method is used and the Windows User Account Control (UAC) setting is set at a level higher than Never notify, a UAC dialog box sometimes appears containing the following message:

Do you want to allow this app to make changes to your device?

Clicking Yes on the dialog box while continuing to hold Ctrl + Shift, the Workstation Options are not reset.

To reset Workstation Options, use one of these workarounds:

• Temporarily set UAC to Never notify.
• Release Ctrl + Shift, click Yes on the dialog box, and then immediately hold down Ctrl + Shift.
• Open the Logix Designer application, click Tools > Options to open the Workstation Options dialog box, and for each Workstation Option category, click Reset Category.

Some device properties, online functions, communication drivers, and FactoryTalk Security authentication with Studio 5000 Logix Designer are not supported with FactoryTalk Linx. Use the following table as a guide for the recommended communication software to use with select modules.

Starting with version 31.00 of Logix Designer application, the default font type size for the Structured Text Editor changed from Courier New size 8 to Consolas size 10. Since the Sequential Function Chart (SFC) Action uses structured text to execute assignments and instructions, this change makes the SFC Action larger causing the overlap of the SFC elements in projects converted from version 30.00 and earlier to version 31.00 and later. 

To get the same SFC layout as in v30.00 and earlier:

Select Tools > Options.
In the Workstation Option, select Structured Text Editor > Font/Color.
In Font, choose Courier New.
In Size, choose 10. 

To convert a project with a Function Block Diagram routine with text boxes from version 11.00 of RSLogix 5000 software to version 21.00 and later, use one of these steps:

• Export the version 11.00 project file to an .L5K file, and then import the .L5K project file into version 21.00 and later.
• Convert the project from version 11.00 to version 12.00 through version 20.00 before converting the project to version 21.00 and later. 

The Logix Designer application may exceed memory when multiple large routines are opened and resized to fit the full window using the View>Zoom>Fit to Window command. To work around this issue, use the View>Zoom>Fit to Width command to set the zoom of the selected routines so that the entire width of the routine fits within the routine windows. 

When versions 30.00 and 31.00 of the Logix Designer application are both installed on the same computer, and trending has never been run in the version 31.00.00 Logix Designer application, trending fails to run in the version 30.00 Logix Designer application. RSLinx Classic is the default communication software for Trend Server, which causes this behavior. After switching between FactoryTalk Linx and RSLinx Classic, the trend will not work for version 30.00. (Lgx00203589)

Starting with version 24.00 of the Logix Designer application, modules can be accessed via module references. Because of this, program-scoped tags with the same names as modules ignore those modules in terms of logic references. For version 24.00.00 and later, when attempting to access modules via module reference from within the Logix Designer application, a warning message opens. If converting from a version earlier than version 24.00, the application returns a verification error.

If uninstalling the CodeMeter kit, which is installed with the FactoryTalk® Activation Manager, the Logix Designer application fails to uninstall. To restore the CodeMeter kit, uninstall the FactoryTalk Activation Manager and then reinstall it.

The SequenceManager feature is not available for Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580 controllers in this release of the Logix Designer application.

When editing existing standard STRINGs or entering a new STRING, if there is a non-alphanumeric character in the STRING, such as a space, period or apostrophe, add an escape carriage.

For installations of version 32.00 of Logix Designer, Microsoft .NET Framework 4.6 is installed automatically. However, .NET Framework 4.6 can cause these issues:

• When previous versions of Logix Designer are installed after version 30.00, .NET Framework 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 Framework 4.6 causes versions 23.00 and earlier of the Logix Designer application to fail on startup.

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

When using version 29.00 or later to open a project from a release earlier than version 29.00, the signature breaks for any Add-On Instruction included in the project. In the same way, when importing an Add-On Instruction from a project created in a release earlier than version 29.00, the signature breaks for that Add-On Instruction. Un-seal and then re-seal each Add-On Instruction to get a new signature.

The Requested Packet Interval (RPI) setting for the Kinetix Encoder Emulator must match the Motion Group Base Update period. If the RPI setting and the Motion Group Base Update period do not match, output can fail from the Encoder Emulator.

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.

Some Boolean members of the AxisSafetyFaults attribute were renamed and some were added to support the drive safety instructions. If a member of the AxisSafetyFaults is used in logic, the logic will not compile until the old axis Boolean attribute is replaced with the new name.

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 following table lists the motion database revisions that are 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.

When using version 32.00 to open a project from a release earlier than version 32.00, any routines that are locked in the project will not download to a controller. Before downloading the project, open the project in version 32.00, unlock the routines, and then re-lock them. Download the project with the re-locked routines to the controller.

This version of Studio 5000 Logix Designer application 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.

The following 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").

The following 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)

The following table identifies the error codes that can be returned by an installation.

The Module Info tab within Module Properties will not return module information when utilizing FactoryTalk Linx

Viewing the Module Info tab of any device in the I/O configuration results in the following error:

Internal direct communications error. Call Technical Support.

This error will occur even when the module is connected and successfully communicating with the controller. The error will only occur when utilizing FactoryTalk Linx as the communication software package for Logix Designer.

This is not an anomaly in Logix Designer.

This anomaly in FactoryTalk Linx was addressed in a Patch Update for FactoryTalk Linx. See technote BF28781 for additional details.