Corrected anomalies in this release

This list identifies the anomalies that are corrected in the Logix Designer application version 37.00. Use the identification information provided in parentheses to track the anomaly in future releases or for reference when receiving assistance from Customer Support with a related issue.

When you attempt to upload a project from a controller running Logix Designer versions 34, 35, or 36, the upload sometimes fails.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

The Logix Designer application can become unresponsive or shut down when you use the

Toggle Inline Value Display

setting while these conditions are true:

You are viewing the logic of an AOI that references at least one Logix tag-based alarm.
The AOI logic is in a structured text routine.

The error can occur when you are either offline or online with the controller.

This anomaly corrected in version 37.00.

This anomaly first identified in version 31.00.

Logix Designer does not prevent you from including HMIBC type tags in Redundant applications, which can lead to controller Primary, Secondary or simultaneous Primary and Secondary assert and errors when you attempt to upload from the controller into an existing or new application when no assert has occurred.

This anomaly corrected in version 37.00.

This anomaly first identified in Logix Designer version 33.00.

A compiler error,

Complier Error(0x0A), Call technical support

, appears when trying to lock a license-based source protected routine, where at least one InOut parameter is missing a required connection and that InOut parameter is used in the routine that is being source protected and locked.

To work around this anomaly, perform a

Controller Verify

or

Build

of the project to determine if any InOut Parameter are missing required connections.

This anomaly corrected in version 37.00.

This anomaly first identified in Logix Designer version 32.00.

If an application was generated in an XML editor and a move instruction (MOV/MOVE) was created with an empty/missing operand, a Fatal Error occurs on import of the L5X file.Example of text that would cause the Fatal Error on import:

<![CDATA[MOV(TagA);]]>

Example of text that would not cause the Fatal Error on import:

<![CDATA[MOV(TagA,TagB);]]>
<![CDATA[MOV(TagA,?);]]>

NOTE: The fatal error does not occur when importing L5X created with Logix Designer because the software inserts a “?” in place of the missing operand.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

When you open a project in the Logix Designer application, select

Go to Cross Reference

for a tag, and then close the project, the Logix Designer application asks you to save changes even though the project has not changed.

There is no workaround for this issue.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

When you attempt to search and replace a tag name used in multiple programs, the Logix Designer application sometimes displays an error that states "Not enough graphic resources" and sometimes becomes unresponsive.

To work around this anomaly, intermittently close out tag editor windows during the Search and Replace action to free graphic resources.

This anomaly corrected in version 37.00.

This anomaly first identified in version 31.00.

The Logix Designer application sometimes locks up when you create a new data type and select for one of the properties.

To work around this issue, hover your cursor over the application icon in the taskbar and close the empty dialog.

This anomaly corrected in version 37.00.

This anomaly first identified in version 36.00.

The Logix Designer application sometimes fails to create an alarm when you do a partial import for an Add-On Instruction (AOI) that contains the alarm.

To work around this issue, export and then import the affected project.

This anomaly corrected in version 37.00.

This anomaly first identified in version 33.00.

You can expand and display the bit members for tags using the DT and LDT data types, but you cannot change the values for the bit members. This is expected behavior.

This anomaly corrected in version 37.00.

This anomaly first identified in version 36.00.

The verification error, “Invalid signature ID. Reseal instruction to resolve.” is reported for a Structured Text Add-on Instruction (AOI) that contains a signature and a nested, unsigned AOI. The error appears after edits are made to the unsigned, nested AOI.

To get past the verification error, the signature must be removed and re-added to the AOI with the reported error.

This anomaly corrected in version 37.00.

This anomaly first identified in version 28.00.

By default, hidden members within a User-defined Data Type (UDT) are defined with a decimal radix. This can be changed in the L5X export of a UDT to another supported radix type.

On project upload, the hidden member tag’s radix would change back to the default decimal style format. This does not affect UDT tag data but could be flagged as a difference when comparing copies of the project file using text comparison tools.

This anomaly corrected in version 37.00.

This anomaly first identified in version 20.00.

The Fatal Error occurs on upload if there previously was an Add-on Instruction (AOI) that matched the naming convention from the IEC 61131-3 standard, and that AOI was removed from the project prior to downloading.

To prevent the anomaly, avoid creating AOI mnemonics matching the naming convention from the IEC 61131-3 standard.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

The following could occur for EDS AOP devices that use a one-dimensional array, with only one element for the input or output tag in their configuration:

When updating an EDS AOP module’s configuration, it appears that the data type has changed on the module properties, but the update is not present in the tag browser.
When creating, copying/pasting, or importing/exporting the device, the module-defined timestamps increment for each device created.

This anomaly has been corrected in the Add-on profile Core released with Logix Designer version 37.00.

This anomaly first identified in version 31.00.

A Fatal Error could occur when you select the

Upgrade Data Types…

button for certain EDS AOP device configurations. The

Upgrade Data Types…

button is present on the device’s profile if the project environment has been upgraded to support unsigned datatypes. This support was added with the release of Studio 5000 Logix Designer version 36.00.

To work around this anomaly, remove and re-add the EDS AOP device to the I/O configuration, which will upgrade the datatype.

This anomaly corrected in version 37.00.

This anomaly first identified in version 34.00.

When you create a new device in the I/O configuration, the module tags in the Controller Tag browser do not reflect the defined module definition.

This can also affect Logix Designer applications with EDS AOP devices that are upgraded to Logix Designer versions 34.00 and later, if Logix Designer version 36.00 or later is installed.

This anomaly is related to the EDS Subsystem installed with Logix Designer version 36.00.

This issue only affects EDS AOP devices in 5380/5480/5580 controller applications.

This anomaly corrected in version 37.00.

See technote

BF30248

for additional information.

When you add certain third-party devices to a 5032 I-O Link Master application, Logix Designer could display a Fatal Error or an Invalid Name error, preventing the device from being added to the configuration.

This anomaly corrected in version 37.00.

This anomaly first identified in version 35.00.

When a Guardlink EIP Scanner 432ES AOP version 1.00.34 is already installed on your Logix Designer workstation and you attempt to install version 36, installation errors occur and the installer fails to install AOP core files.

To work around this issue, uninstall the GuardLink EIP Scanner AOP from your Logix Designer application before installing version 36.00. For more information, see

this Knowledgebase article

.

This anomaly corrected in version 37.00.

This anomaly first identified in version 36.00.

When you open the device configuration page with a 5032 IO-Link Master running with a 42AF IO-Link device at default settings, the

Clear Log

button on the Event Log page is sometimes grayed out.

This anomaly corrected in version 37.00.

This anomaly first identified in version 36.00.

In 5380, 5480, and 5580 controller applications, the Host Words in a tag configuration could be excluded from an EDS AOP device’s Input, Output, and/or Configuration tags. The individual programming bits are still visible.

This anomaly has been corrected in the Add-on profile Core released with Logix Designer version 37.00.

This anomaly first identified in version 34.00.