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:

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

• Windows® 10 Professional and Enterprise
• Windows 10 Enterprise 2021 LTSC (v21H2)
• Windows 11 Professional and Enterprise
• Windows Server 2022 Standard and Datacenter Editions

• 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 8
• Windows Server 2019
• Windows Server 2016

• This is a list of the prerequisite software installed with this version of the Logix Designer application:

• FactoryTalk® Services Platform v6.31
• FactoryTalk® Activation Manager v5.0
• FactoryTalk® Linx v6.31

• RSLinx Classic v4.3x is shipped with the Logix Designer application version 35.00.

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

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

• Windows 10 Professional
• Windows Server 2019 Standard

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

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 v35.00 has this new feature.

• Axis Test Mode

• FLEXHA 5000^TM I/O

• Equipment Sequence Unit ID

• Equipment Sequence controller support

• Equipment Phase External Request (PXRQ) error codes

• New instructions added to the Logix Designer instruction set

• Two-Argument Arctangent (ATAN2). The ATAN2 instruction takes the two-argument arc tangent of the Source values and stores the result in the Destination (in radians). The ATAN2 operator/function computes the arc tangent of the Source and returns the FLOAT result. The resulting value in the Destination is greater than or equal to -p and less than or equal to p (where p = 3.141593).
• Process Discrete 2-, 3-, or 4-State Device (PD4SD). The Process Discrete 2-, 3-, or 4-State Device (PD4SD) instruction controls and monitors feedback from a discrete 2-state, 3-state, or 4-state device in a variety of modes, monitoring for fault conditions. These devices include multiple-speed motors or multiple-position valves.
• Process n-Position Device (PNPOS). The Process n-Position Device (PNPOS) instruction controls and monitors feedback from a circular or linear discrete device with up to 30 positions. The PNPOS instruction provides outputs to select an individual position and outputs to move toward increasing positions (clockwise for a circular device) or decreasing positions (counterclockwise for a circular device).
• Process Mix Proof Valve (PVLVMP). The Process Mix Proof Valve (PVLVMP) instruction controls and monitors feedback from a mix-proof valve in various modes and states, monitoring for fault conditions. This instruction supports mix-proof valves with or without additional connections for cleaning (CIP, clean-in-place) or steaming (SIP, sanitize in place).

• Controller Change Detection expanded support

• Updated device profiles

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?).

Delete option enabled in safety and standard connections (1522174)

In safety and standard connections to PowerFlex 755T drives, the Delete option is enabled but selecting it does not remove the device from the project.

This anomaly first identified in version 33.01.

Ethernet module parent property does not respond (1653397)

When offline with an Ethernet module with redundancy enabled, the parent module does not respond to property updates.

This anomaly first identified in version 34.00.

1756 Ethernet Bridge Module Profile delays or stops responding (1653397)

An anomaly in the RSLogix 5000 Module Profile core for Studio 5000 v34.00 and v34.01 results in delays when opening 1756 Ethernet Bridge Module Add-On Profiles. The anomaly will occur when 193-ECM-ETR E300 modules are configured beneath the 1756 Bridge Module in the I/O configuration.

This anomaly first identified in version 34.00.

Online module discovery for redundant chassis pair enabled and concurrent configured 1756-EN4TR (1569080)

When 1756-EN4TRs are configured as redundant chassis pair enabled and a concurrent connection is configured, when creating the 1756-EN4TR via online discovery, the RcpGatewayAddress1 and RcpGatewayAddress2 should be given the default value. For RcpGatewayAddress1, its default value is the found IP address; while the RcpGatewayAddress2, its default value is the partner IP address. For AOP core, the ModuleBrowseInfo and SelectModuleTypeDialog components will be updated.

This anomaly first identified in version 35.00.

PLLS instruction motor/pump demand does not align with running motors (1767531)

The PLLS instruction does not properly set its Demand value on the first scan to align with the motors that are running. The instruction will then begin sequencing the motors off.

This anomaly first identified in version 34.00.

PAI instruction Alarm values mismatch (1647896, 1647893, 1647446, 1641560)

The PAI instruction Alarm values show these mismatches:

• The user assistance states that the Low Deviation value Limit must be set to a negative value. The tool tip in the Alarms dialog box states that the Limit value can be a positive value.
• The user assistance states that the High Deviation value Limit value must be a positive value. The tool tip in the Alarms dialog box states that the High Deviation value High Limit can be a negative value.
• The Limit field on the Alarms tab accepts a Low Deviation positive Limit value, which causes the Deadband value to set incorrectly to a negative value.

This anomaly first identified in version 33.00.

PAH instruction HART input values should be unavailable (1624291)

The Advanced tab of the PAH dialog box Object has HART inputs options for PV, SV, TV, and QV values are enabled when the options are not available to the variable. 

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.

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.

Message datatype cannot compile after upload from controller (1785828, 1789626)

The Logix Designer application cannot compile the ACD file after uploading a program-scoped MSG backing\control tag that is used as an InOut parameter in an Add On Instruction (AOI) to a new ACD file.

This anomaly corrected in versions 33.02, 35.00, and 36.00.

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

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.

Input controller tag value after cable break varies (1494865, 1494862, 1494859)

The input controller tag values after a cable break varies based on the channel value at the last inhibition and uninhibition action.

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

Editing Operand Description sometimes results in unexpected display behavior (1354684)

When the same tag description exists on many branches that span an area that extends beyond what is visible on a display and the tag description is edited, the content on the display sometimes jumps upon acceptance of the tag description edit. 

Using the left or right arrow keys causes the screen to focus on the tag description that was just edited.

The anomaly does not occur when the tag description is edited for the rung where the contacts are unique because the tag description only exists in one location.

This anomaly first identified in version 20.00.

Storing Firmware Supervisor files from PowerFlex 755T causes the <ST5LD>  application to stop responding (1518416)

Attempting to store Firmware Supervision files for PowerFlex 755T devices causes the <ST5LD> application to stop responding. The application must be closed using Task Manager.

This anomaly was first identified in version 33.00.

This anomaly first identified in version 20.00.

DataExchange fails AML and RDF imports and exports due to incorrect catalog number (1427806)

DataExchange AML and RDF imports and exports fail because the catalog number 5059-HSC2xOB4 is incorrectly listed as 5059-HSC2XOB4 in ModuleType and CatalogServices.

This anomaly corrected in version 36.00.

This anomaly first identified in version 34.00.

Trends display steps instead of linear line (1093987)

Trends show steps instead of linear line while executing quantums larger than 10ms. Part of trends use physical time instead of virtual time.

This anomaly first identified in version 33.00.

Unable to upload project from PLC (1489327)

The Logix Designer application stops performing with attempting to upload a project from the controller on a sequence diagram.

For details about this issue, see Tech Note BF28540.

This anomaly first identified in version 34.00.

Can create safety I/O module successfully when Safety Modify Component set to deny (1787414)

You can successfully create an Add-On Profile based safety I/O module without errors when FactoryTalk Security user privileges's Safety Modify Component is set to Deny.

This anomaly first identified in version 35.00.

Can create a 5015-AENFTXT under the 1756-EN2TSC I/O configuration (1882887)

When creating a module under 1756-EN2TSC, 5015-AENFTXT is listed in available modules and can be created successfully. 5015-AENFTXT should only appear under adapters that support concurrent connections, such as 1756-EN4TR major revision 4. Communication between 1756-EN2TSC and 5015-AENFTXT is not supported and will not function.

First reported in version 35.00 and AOP version 28.04. 

PFO Advanced dialog box Clamping limits input range (1585324)

The PFO instruction Advanced dialog box Clamping limits do not update to match the Minimum and Maximum values.

This anomaly only applies to projects using the CompactLogix 5380P and ControlLogix 5580P controllers.

This anomaly corrected in version 36.00.

This anomaly first identified in version 33.00.

Logix Designer application Tag-based Alarm extended properties do not auto-populate completely (1957929)

The Logix Designer application tag-based alarm extended property @Alarms does not auto-populate completely in Sequential Function Chart (SFC) or Structured Text (ST) routines. You must manually type out the text in its entirety to access all extended properties.

For example, if your alarm is named MyAlarm, and the input tag is named AlarmInput, you must type:

AlarmInput.@Alarms.MyAlarm.

When you enter the last period, you can select from the list of available extended properties in a dialog box.

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

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

Some Catalog numbers not displaying correctly in Module Discovery (2001084)

After creating a new L85E v35 project with a 5032 I/O-Link bridge device connected to the Ethernet bus and enabling at least one channel for the I/O-Link, connect Siemens-K20-4DI IO-Link device with the 5032 I/O-Link bridge module, and download the project. Launching Module Discovery from the I/O-Link bus shows some Catalog numbers do not display correctly.

This anomaly first identified in version 35.00.

I/O-Link Module Discovery displays 17.00 (100,1.1001) (1848106)

When creating an L85E project and adding a 5032-Master, after configuring some channels to I/O-Link and downloading the project, launch Module Discovery from the I/O-Link bus. The Revision column shows 17.000 for the I/O-Link devices instead of the expected 1.1 or 1.0.

This anomaly first identified in version 35.00.

L5K file with I/O Device cannot be imported (2047005)

When creating an L85E project using a 5032 master profile on the Ethernet bus and adding the I/O-Link device 42AF-R1MAB1-xx[209] with default setting on the I/O-Link bus, the error Unexpected end of file encountered occurs and the import is not successful.

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

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.

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.

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

• The safety signature in the GuardLogix 5380, and GuardLogix 5580 controllers does not store the Safety tags data. Safety tag values no longer impact the safety signature.
• Preservation of online tag values during download includes the Safety tags.
• It is now possible to clear some of the safety faults and continue working on the project without downloading the project again.

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

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.