This release has the following requirements.
System requirements for Studio 5000 Logix Designer version 30.xx
For optimal performance of the Logix Designer application, your personal computer should meet or exceed the following hardware and software requirements.
|
Tip:
|
Logix Designer 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.
|
Hardware Requirements
Software Requirements
|
Tip:
|
If the workstation is loaded with the base Windows
Server 2016 operating system, the Studio 5000
Start Page does not open because the base
operating system does not support the Adobe
Flash Player. To restore Start Page functionality,
add the Remote Desktop Session Host role to the
base OS to add support for the Adobe Flash
Player.
|
|
Important:
|
Keep these operating system considerations in mind:
• Universal C Runtime (CRT) is a Windows operating system
component that enables core functionality on the Windows
operating system. It was introduced in Windows 10 and
distributed to most computers running earlier supported operating
systems. On computers that have been kept up-to-date, this
component is present.
When you install the Logix Designer application on computers
that have not been updated, you will be prompted to install
Universal C Runtime or to update the computer to at least the
Microsoft April 2014 update roll-up.
• While the Windows 8.1 operating system runs on many
touch-enabled devices, various features of the Logix Designer
application may not be touch-enabled. Most functions are
expected to work with touch, but the software has only been
tested with a keyboard and mouse.
• Logix Designer was tested with UAC set to the most restrictive
level (Always notify). This version of the Logix Designer
application is also expected to operate correctly when UAC is
configured for any less restrictive setting.
|
|
Important:
|
When you install version 30 of Logix Designer, Microsoft .NET
Framework 4.6 is installed automatically. However, when
installed on 32-bit Windows operating systems, .NET Framework
4.6 causes versions 23 and earlier of the Logix Designer
application to fail on startup. Also, when previous versions of
Logix Designer are installed after version 30, .NET Framework
4.6 may cause these earlier versions of the Logix Designer
application installation to fail. Refer to the Application notes for
more information on this issue.
|
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 )
|
Tip:
|
Most modules use Flash-ROM for the storage of firmware. If a
module requires a firmware change, use the ControlFLASH™
tool to perform the update to the Flash-ROM. It is contained in
the downloaded image or on a DVD-ROM shipped with the
Logix Designer application. You can also automatically update
the firmware 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 .
|
This release corrects the following anomalies.
Redundancy-enabled Projects Sometimes Fail to Upload from The Controller Unless Original Download File Exists (Lgx00191976)
Corrected Anomaly as of Studio 5000 Logix Designer® v30.01.00 and v31.00.00
Known Anomaly first identified in version 30.00.00 of Studio 5000 Logix Designer
When you attempt to upload a redundancy-enabled project from the controller, the upload fails unless your computer contains the same project file that was originally downloaded.
The Studio 5000 Logix Designer application gives an error that the project has redundancy disabled and controller firmware with a minor revision of .49 is required.
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:
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.
These anomalies are from previous releases but are still known in this release.
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)
Trend restarts from the beginning when Pause is clicked (Lgx00184775)
Studio 5000 Logix Designer v29.00
When you click Pause during trending, the trend sometimes starts over from the beginning. (Lgx00184775)
Phase Manager and Sequence Manager sometimes show different phase states (Lgx00183769)
Studio 5000 Logix Designer v29.00
When FactoryTalk Security Modify Logic access is denied, FBD properties are sometimes inaccessible (Lgx00184895)
Studio 5000 Logix Designer v29.00
When Modify Logic access is denied but View Logic access is allowed in FactoryTalk security settings, users sometimes cannot open the Properties dialog box in the Function Block Diagram editor. (Lgx00184895)
As a workaround, select the FBD instruction and press Alt + Enter to open the Properties dialog box.
Low controller memory can prevent connection to the controller (Lgx00179908)
Studio 5000 Logix Designer v29.00
Changing Data Context for AOI does not change metadata context (Lgx00185356)
Studio 5000 Logix Designer v29.00
Error when using Import to overwrite an existing locked component (Lgx00190571)
Anomaly first identified in Studio 5000 Logix Designer v30.00
The Logix Designer application displays a red flag and/or error ("Unable to overwrite [component] while online. The locked routine already exists in project and there are no differences in locked logic") when you attempt to use Import to overwrite an existing locked component with an identical locked component.
Use one of the following steps to work around the issue:
IOT instruction may decompile incorrectly (Lgx00176073, Lgx00188026, Lgx00188027, Lgx00188028)
Anomaly first identified in Studio 5000 Logix Designer v26.00
IOT instruction may decompile incorrectly. If you upload a rung containing, for example, "IOT(MyProduceOrConsumeArrayTag)," it can incorrectly upload or decompile as "IOT(MyProduceOrConsumeArrayTag[0])".
Changing Data Context in Add-On Instructions does not change the description and project documentation in Data Context tab(Lgx00185356, Lgx00185438, Lgx00185439, Lgx00186196)
Anomaly first identified in Studio 5000 Logix Designer v28.00
When you select a tag in the Data Context menu in the Add-On Instruction Parameters and Local Tags dialog box, the Properties pane displays 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 does not change the description and properties for the selected Data Context tag, but instead changes the description and properties for the Add-On Instruction Instance Definition.
Follow these instructions to work around the issue:
Downloading a PointIO project may cause error 16#0205 (Lgx00190599)
Anomaly first identified in Studio 5000 Logix Designer v28.02
When you add a module to a PointIO rack offline, the module is configured for slot 1 by default. When you update the module profile with the correct slot position and download the project to the controller, error 16#0205 occurs.
Follow these instructions to work around the issue:
Tracked State Value for Redundant Controller May Not Be Correct After A Switchover (Lgx00189950, Lgx00190153, Lgx00190152)
Corrected Anomaly in Firmware Revision 31.051
Known Anomaly first identified in version 30.00
Catalog Numbers: ControlLogix® 5570 Redundant Controllers
When you enable redundancy but do not retain test edits of a tracked routine, and switchover occurs with test edits running, the Tracked State value on the redundant controller will show the tracked state value of the controller with test edits, even though the test edits are not running in the redundant controller.
Follow one of these steps to work around the issue:
|
Important:
|
If you retain test edits and the test edits were the cause of the
switchover, the test edits can cause the same fault on the redundant
controller.
|
Routines may not indicate an Overflow Fault setting mismatch (Lgx00190654, Lgx00190708)
Anomaly first identified in version 30.00
If you create a routine and lock it, and then change the Report Overflow Faults setting on the Controller Properties dialog box - Advanced tab, the fault reporting behavior might not match what you expect. For example, if you lock a routine with the Report Overflow Faults setting unselected, but then select the setting and download the project to the controller, no overflow would be reported for that routine. If you lock a routine with the Report Overflow Faults setting selected, but then unselect the setting and download the project to the controller, no overflow would be reported for that routine, but you could still experience the possible decrease in runtime performance and increase in download time.
Logix Designer application Launcher can fail when you click About > Support (Lgx00190760, Lgx00190865)
Anomaly first identified in version 30.00
The Logix Designer application Launcher can fail when you click About > Support. This can happen when the Logix Designer application is installed on the Microsoft Windows 10 operating system, you log into Windows with User Access Control (UAC) disabled, and Microsoft Edge is the default browser.
Use one of these steps to work around the issue:
May not be able to select the correct revision when adding 2715 HMI PanelView 5500 HMI module to Logix Designer (Lgx00191064)
Anomaly first identified in version 30.00
When adding a 2715 HMI PanelView 5500 HMI into the I/O Configuration tree in the Logix Designer application, the Module Definition Revision will be 2.001, even if you are connecting to a V3.xxx PanelView 5500. There is no selection to pick a V3.xxx revision. This will still operate correctly if you choose Compatible Module for the Electronic Keying.
This release has the following functional changes from the previous release.
Functional changes in Studio 5000 Logix Designer version 30.01
Studio 5000 Logix Designer version 30.01 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:
Tip: Keep the following considerations in mind before installing the Logix Designer application:
Import/Export
The Import/Export version number for this version of Logix Designer application is 2.21. The following table lists the Import/Export versions for previous releases.
|
Release Version
|
Import/Export
Version
|
|
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.9
|
|
17.xx
|
2.8
|
|
16.xx
|
2.7
|
|
15.xx
|
2.6
|
|
14.xx
|
2.5
|
|
13.xx
|
2.4
|
|
12.xx
|
2.3
|
|
11.xx
|
2.2
|
|
10.xx
|
2.1
|
|
9.00
|
2.0
|
|
5.02
|
1.2
|
|
2.xx, 6.xx, 7.xx, 8.xx
|
1.1
|
|
1.21, 1.23
|
1.0
|
|
1.10, 1.11
|
0.4
|
This release has the following application notes.
The following are the application notes for Logix Designer version 30.01.
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.
|
|
|
|
Controller Catalog Number
|
Minimum Major
Software Version
|
|
ControlLogix 1756-L71 Series B
|
20
|
|
ControlLogix 1756-L71S Series B
|
20.01
|
|
ControlLogix 1756-L72 Series A
|
19
|
|
ControlLogix 1756-L72 Series B
|
20
|
|
GuardLogix 1756-L72S Series B
|
20
|
|
ControlLogix 1756-L73 Series A
|
18
|
|
ControlLogix 1756-L73 Series B
|
20
|
|
ControlLogix 1756-L73XT Series B
|
20
|
|
GuardLogix 1756-L73S Series B
|
20
|
|
GuardLogix 1756-L73SXT Series B
|
20
|
|
ControlLogix 1756-L74 Series A
|
19
|
|
ControlLogix 1756-L74 Series B
|
20
|
|
ControlLogix 1756-L75 Series A
|
18
|
|
ControlLogix 1756-L75 Series B
|
20
|
|
ControlLogix 1756-L81E Series B
|
29
|
|
ControlLogix 1756-L82E Series B
|
29
|
|
ControlLogix 1756-L83E Series B
|
28
|
|
ControlLogix 1756-L84E Series B
|
29
|
|
ControlLogix 1756-L85E Series B
|
28
|
|
CompactLogix 1769-L16ER-BB1B Series A
|
20
|
|
CompactLogix 1769-L16ER-BB1B Series B
|
20
|
|
CompactLogix 1769-L18ER-BB1B Series A
|
20
|
|
CompactLogix 1769-L18ER-BB1B Series B
|
20
|
|
CompactLogix 1769-L18ERM-BB1B Series A
|
20
|
|
CompactLogix 1769-L18ERM-BB1B Series B
|
20
|
|
CompactLogix 1769-L19ER-BB1B
|
28
|
|
CompactLogix 1769-L24ER-QB1B
|
20
|
|
CompactLogix 1769-L24ER-QBFC1B
|
20
|
|
CompactLogix 1769-L27ERM-QBFC1B
|
20
|
|
CompactLogix 1769-L30ER
|
20
|
|
CompactLogix 1769-L30ER-NSE
|
20
|
|
CompactLogix 1769-L30ERM
|
20
|
|
CompactLogix 1769-L33ER
|
20
|
|
CompactLogix 1769-L33ERM
|
20
|
|
CompactLogix GuardLogix 1769-L30ERMS
|
28
|
|
CompactLogix GuardLogix 1769-L33ERMS
|
28
|
|
CompactLogix GuardLogix 1769-L36ERMS
|
28
|
|
CompactLogix 1769-L36ERM
|
20
|
|
CompactLogix 5069-L306ER
|
29
|
|
CompactLogix 5069-L306ERM
|
29
|
|
CompactLogix 5069-L310ER
|
29
|
|
CompactLogix 5069-L310ERM
|
29
|
|
CompactLogix 5069-L310ERM-NSE
|
29
|
|
CompactLogix 5069-L3100ERM
|
30
|
|
CompactLogix 5069-L320ER
|
28
|
|
CompactLogix 5069-L320ERM
|
29
|
|
CompactLogix 5069-L330ER
|
29
|
|
CompactLogix 5069-L330ERM
|
29
|
|
CompactLogix 5069-L340ER
|
29
|
|
CompactLogix 5069-L340ERM
|
28
|
|
CompactLogix 5069-L350ERM
|
30
|
|
CompactLogix 5069-L37ERMO
|
30
|
|
CompactLogix 5069-L380ERM
|
30
|
|
CompactLogix 5069-L46ERMW
|
30
|
Microsoft .NET 4.6 may cause failure in earlier versions of the Logix Designer application
When you install version 30.01 of Logix Designer, Microsoft .NET 4.6 is installed automatically. However, .NET 4.6 can cause the following issues:
Follow one of these steps to work around the issue:
If the VeriSign Universal Root Certification Authority certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
Microsoft Root Certification Authority certificate
If the Microsoft Root Certificate Authority 2011 certificate does not exist on the local computer, the certificate is installed while installing Rockwell Automation software. Use Microsoft Management Console (MMC) to view the certificate in Console Root > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates.
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.
|
Version of Application
|
Motion Database Revision
|
|
30.00
|
11.6.0 [ Motion.mdb format ]
|
|
29.00
|
11.5.0 [ Motion.mdb format ]
|
|
28.00
|
10.5.0 [ Motion.mdb format ]
|
|
27.00
|
10.3.0 [ Motion.mdb format ]
|
|
26.01
|
10.3.0 [ Motion.mdb format ]
|
|
24.00
|
9.24.0 [ Motion.mdb format ]
|
|
23.00
|
9.22.0 [ Motion.mdb format ]
|
|
21.03
|
9.15.0 [ Motion.mdb format ]
|
|
21.00
|
9.8.0 [ Motion.mdb format ]
|
|
20.01
|
8.12.0 [ Motion.mdb format ]
|
|
20.00
|
8.9.0 [ Motion.mdb format ]
|
|
19.01 / 19.00
|
7.5.0 [ Motion.mdb format ]
|
|
18.02 / 18.01 / 18.00
|
6.9.0 [ Motion.mdb format ]
|
|
17.01 / 17.00
|
5.3.0 [ *Motion.md format ]
|
|
16.04 / 16.03 / 16.00
|
4.2.0 [ *Motion.md format ]
|
|
15.03 / 15.02 / 15.01 / 15.00
|
3.24.0 [ *Motion.md format ]
|
|
14.01 / 14.00
|
3.12.0 [ *Motion.md format ]
|
|
13.04 / 13.03 / 13.02 / 13.01 / 13.00
|
3.12.0 [ *Motion.md format ]
|
|
12.06 / 12.05 / 12.04 / 12.03 / 12.02 / 12.01 /
12.00
|
3.3.0 [ *Motion.md format ]
|
* 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.
Command-line parameters
|
Parameter
|
Description
|
|
/?
|
Displays the usage options for installation parameters.
|
|
/Q
|
Silent Install, install runs in a quiet mode without any user
interface.
This parameter is recommended if you are deploying the
software installation using an IT tool or script, and don’t
expect to see any error or restart messages. When using
this parameter, your IT tool or script should check the error
codes, and respond as needed. For example, if the
installation returns error code 1641, then the IT too or script
should restart the computer and relaunch the installation
after restart.
This parameter is required if /QS is not specified.
|
|
/QS
|
Unattended Install, install runs in a quiet simple mode and
shows progress through the UI, it does not accept any
input but still shows error or restart messages.
When using this parameter, you will not have to check the
error codes, and the installation will stop and display a
prompt if there are error or restart messages. For example,
if an immediate restart is required to complete the install, a
restart message will be displayed for you to confirm the
restart. Installation resumes automatically from the point of
interruption after restart.
This parameter is required if /Q is not specified.
|
|
/IAcceptAllLicenseTerms
|
Acknowledges acceptance of the license terms.
This parameter is required for /Q or /QS parameters.
|
|
/AutoRestart
|
Automatically restarts the computer after the installation is
complete. Used when a restart is required to complete the
installation.
This parameter is optional. If this parameter is not used
silent install (/Q) will return either error code 1641 or 3010 if
a restart is required, and unattended install (/QS) will result
in a confirmation prompt that must be agreed to before the
installation is completed.
|
|
/SetupLanguage=”value”
|
Specifies which language will be displayed during install
process.
The value must be the one of the following:
This parameter is optional. If this parameter is not used,
the default language is the current user or operating
system user interface language.
|
|
/Product=“value”
|
Specifies which sub-products will be installed.
Only required if sub-products are included with the install
package.
If the software does not include sub-products this
parameter is not available.
|
|
/ProductLanguage="value"
|
Specifies the language version of the software being
installed.
The value must be the one of the following:
This parameter is optional. If this parameter is not used,
the default language is the same as the setup language.
If the software does not support multiple languages this
parameter is not available.
|
| /InstallLocation=“value”
Or
/InstallDrive=“value”
|
Specifies the install location or install drive respectively.
This parameter is optional. If this parameter is not used,
the default install location is "C:\Program Files
(x86)\Rockwell Software".
Some software restricts the installer to only change the
drive the software is installed on. Use /? to determine
which parameter is supported.
|
|
/SerialNumber=“value”
|
Specifies the serial number of the software being installed.
This is used to activate the software during installation.
This parameter is optional. If it is not specified the software
must be activated manually after installation if activation is
required.
Some software does not require activation. If activation is
not required this parameter is not available.
|
|
/ProductKey=“value”
|
Specifies the product key used to get activation keys during
installation.
This parameter is optional. If it is not specified the software
must be activated manually after installation if activation is
required.
Some software does not require activation. If activation is
not required this parameter is not available.
|
|
/Version=“value”
|
Specifies the version of the software to activate which
corresponds to the product version associated with the
SerialNumber and ProductKey.
This parameter is optional. If it is not specified the installer
will use the most recent product version available.
Some software does not require activation. If activation is
not required this parameter is not available.
|
• 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:
|
Error Code
|
Value
|
Description
|
|
ERROR_SUCCESS
|
0
|
The installation completed successfully.
|
|
ERROR_INVALID_PARAMETER
|
87
|
One of the parameters was invalid.
|
|
ERROR_INSTALL_USEREXIT
|
1602
|
The installation was cancelled by the user.
|
|
ERROR_INSTALL_FAILURE
|
1603
|
A fatal error occurred during installation.
|
|
ERROR_BAD_CONFIGURATION
|
1610
|
The configuration data for this product is corrupt.
Contact your support personnel.
|
|
ERROR_SUCCESS_REBOOT_INITIATED
|
1641
|
The installer has initiated a restart. After restart
installation will continue.
|
|
ERROR_SUCCESS_REBOOT_REQUIRED
|
3010
|
A restart is required to complete the installation.
After restart the product is successfully installed.
|
|
ERROR_SUCCESS_RELAUNCH_REQUIRED
|
3011
|
Restart of setup needed before installation can
continue.
|