This release has the following requirements.
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.
|
|
|
This release is not intended to run on a 32-bit operating system. All
operating systems listed are the 64-bit variant.
|
|
IMPORTANT
|
Keep these operating system considerations in mind:
When installing the Logix Designer application on
computers that have not been updated, a prompt
displays to install Universal C Runtime or to update the
computer to at least the Microsoft April 2014 update
roll-up.
|
Preferred operating systems are prioritized for support, testing, and post-release patch qualifications. These operating systems are preferred for this release:
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:
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:
|
|
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.
|
|
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.
This release includes the following system features.
Logix Designer application version v35.00 has this new feature.
This table lists new hardware supported in this release.
|
Catalog Number
|
Description
|
Vendor Name
|
|
AirLINE_8652
|
Burkert 8652 Valve Island
|
Burkert
|
|
SPC
|
SPC Compact High Precision Weight Sensor
|
METTER TOLEDO
|
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?).
This release corrects the following anomalies.
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.
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:
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.
This release has the following known anomalies.
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.
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.
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.
These anomalies are from previous releases but are still known in this release.
Upload failure (1024944)
When attempting to upload a project, the Logix Designer application generates these errors and the upload fails:
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:
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:
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 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.
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.
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.
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.
This release has the following functional changes from the previous release.
Logix Designer version 35.00 has these changes in functionality since the last release.
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.
|
Release Version
|
Import/Export Version
|
|
34.xx
|
2.25
|
|
33.xx
|
2.24
|
|
32.xx
|
2.23
|
|
31.xx
|
2.22
|
|
30.xx
|
2.21
|
|
29.xx
|
2.20
|
|
28.xx
|
2.19
|
|
27.xx
|
2.18
|
|
26.xx
|
2.17
|
|
24.xx
|
2.15
|
|
23.xx
|
2.14
|
|
21.xx
|
2.12
|
|
20.xx
|
2.11
|
|
19.xx
|
2.10
|
|
18.xx
|
2.09
|
|
17.xx
|
2.08
|
|
16.xx
|
2.07
|
|
15.xx
|
2.06
|
|
14.xx
|
2.05
|
|
13.xx
|
2.04
|
|
12.xx
|
2.03
|
|
11.xx
|
2.02
|
|
10.xx
|
2.01
|
|
9.00
|
2.00
|
|
5.02
|
1.02
|
|
2.xx, 6.xx, 7.xx, 8.xx
|
1.01
|
|
1.21, 1.23
|
1.00
|
|
1.10, 1.11
|
0.04
|