Documente Academic
Documente Profesional
Documente Cultură
ControlLogix Controllers
Version 24.012 (released 3/2015)
Catalog Number 1756-L71 (series A)
These release notes describe version information for 1756-L71, version 24.012 (released 3/2015).
Corrected Anomalies
This release corrects the following anomalies.
Failure to Update Time Offset Corrections in Drives (Lgx00161389, Lgx00161400)
CORRECTED in:
1756 ControlLogix® L7 Firmware Revision 24.012
1756 GuardLogix® L7 Firmware Revision 24.012
5370 CompactLogix™ L1, L2, L3 Firmware Revision 24.013
Studio 5000 Logix Designer, version 26.01
Known Anomaly First Identified as of Firmware Revision 24.011
Catalog Numbers:
1756 ControlLogix L7
1756 GuardLogix L7
5370 CompactLogix L1 (1769-L18ERM-BB1B only)
5370 CompactLogix L2 (1769-L27ERM-QBFC1B only)
5370 CompactLogix L3 (1769-L30ERM, 1769-L33ERM, 1769-L36ERM only)
This anomaly can occur when you use Motion Group Multiplexing in Studio 5000 Logix Designer™ application, version 24.00.00, projects.
Alternate 1 or Alternate 2 Motion Grouped axes can miss passing along time offset corrections to their drives. The result of this anomaly occurring ranges
from minor degradation in motion quality to faulting due to large Command Position disturbances.
For more information on this anomaly, see Knowledgebase article #635683, V24 Motion Group Multiplexing feature can cause a divergence in axis position.
The article is accessible from the Rockwell Automation® Technical Support Center at: http://www.rockwellautomation.com/support/overview.page (Login
required)
Motion Coordinate Linear Move Merge All Generates Error (Lgx00162301)
CORRECTED Anomaly with Firmware Revision 24.012
Catalog Numbers
1756 ControlLogix® L7
1756 GuardLogix® L7
The controller can experience Error 63: AXIS_IN_TRANSFORM_MOVE, when using the MCLM instruction. When the MCLM instruction with Merge All is
executed on the target coordinate system while a MCT instruction is enabled to cancel all the currently active moves on all axes in the source coordinate
system and transition to a point-to-point (Joint) move on target coordinate system or vice versa.
The error occurs even though the Process Complete bit was set to indicate that the first move was complete.
ControlLogix and GuardLogix are trademarks of Rockwell Automation, Inc.
Known Anomalies
This release has the following known anomalies.
Applications with PowerFlex drives in the I/O configuration can experience a major non-recoverable fault (MNRF) (00200734, 00200735,
00200600, 00200599)
Corrected Anomaly as of Firmware Revision 31.011 and 30.014 for these catalog numbers:
CompactLogix™ 5370 Controllers
Compact GuardLogix® 5370 Controllers
Corrected Anomaly as of Firmware Revision 31.011 and 30.013 for these catalog numbers:
ControlLogix® 5580 Controllers
ControlLogix 5570 Controllers
GuardLogix 5570 Controllers
Known Anomaly First Identified as of Firmware Revision 28.011 for these catalog numbers:
ControlLogix 5580 Controllers
CompactLogix 5380 Controllers
Compact GuardLogix 5370 Controllers
Known Anomaly First Identified as of Firmware Revision 20.011 for these catalog numbers:
ControlLogix 5570 Controllers
GuardLogix 5570 Controllers
ControlLogix 5570 (Redundancy) Controllers
ControlLogix 5560 Controllers
GuardLogix 5560 Controllers
ControlLogix 5560 (Redundancy) Controllers
CompactLogix 5370 Controllers
1769 CompactLogix Controllers
1768 CompactLogix Controllers
If a controller already has an application loaded into it that contains PowerFlex drives in the I/O configuration, a MNRF (Major Non-Recoverable Fault) can
occur when any of the following occurs:
A download of a project is performed to the controller.
A PowerFlex drive is deleted while online.
A firmware flash update of the controller is performed.
For more information and workarounds, see Knowledgebase document 1067997.
Functional Changes
This release has the following functional changes from the previous release.
Motion Coordinated Linear Move Instruction Change to Merge All
Functional Change First Identified As Of Firmware Revision 24.012
Catalog Numbers
1756 ControlLogix® L7
1756 GuardLogix® L7
If the Motion Coordinated Transform (MCT) instruction is executing and the source side is moving, you cannot also execute a motion instruction to move the
target axis or Error 63, AXIS_IN_TRANSFORM_MOVE, occurs. The same is true if the target side is moving and you attempt to execute a Motion instruction
on the source axis.
With FW revision 24.012 and later, if the MCLM instruction with Merge All is executed while an MCT instruction is active between the source and target
coordinate system, you can blend smoothly from a continuous-path linear move to a point-to-point move or from a point-to-point move to a continuous-path
linear move without waiting for the first move to complete, without Error 63 occurring.
ControlLogix and GuardLogix are trademarks of Rockwell Automation, Inc.
V24 Additional Memory Requirements for Logix5000 Controllers
Functional Change First Identified As Of Firmware Revision 24.011
Catalog Numbers
1756 ControlLogix® L7
1756 GuardLogix® L7
5370 CompactLogix™ L1
5370 CompactLogix L2
5370 CompactLogix L3
This revision of Logix5000™ controllers may require more memory than earlier revisions. To estimate additional memory requirements for your application,
you can either use the memory estimation tool provided with Logix Designer application or the tables provided in these release notes.
If you do not have the desired version of Logix Designer application, use the following table to estimate the additional memory that your project may require.
If you upgrade Component Increase per instance
from revision
(add all that
apply)
Tag that uses CIP_DRIVE data 140 bytes
type
Module input connection 8 bytes
Module output connection 8 bytes
Standard Produced tag 6 bytes
Standard Consumed tag 8 bytes
Safety input connection 8 bytes
consuming I/O
Safety input connection -8 bytes
consuming data
Safety input connection -8 bytes
consuming safety
Safety output connection 8 bytes
consuming I/O
Safety output connection 8 bytes
consuming data
Safety output connection 8 bytes
consuming safety
Safety Produced tag 8 bytes
Safety Consumed tag 8 bytes
Tag that uses ALARM_ANALOG 64 bytes
data type
Tag that uses ALARM_DIGITAL 16 bytes
data type
Motion Group -128 bytes
Tag that uses 152 bytes
COORDINATE_SYSTEM data
type with no transform
dimensions
Tag that uses 184 bytes
COORDINATE_SYSTEM data
type with transform dimensions
Safety Controller 112 bytes
Data Driven Controller 72 bytes
Program 24 bytes
SFC Routine 8 bytes
21.x to 2.x <no change>
20.x to 21.x Tag that uses AXIS_GENERIC 32 bytes
data type
Tag that uses 512 bytes
AXIS_OUTPUT_CAM data type
Tag that uses -8 bytes
AXIS_SERVO_DRIVE data type
Tag that uses AXIS_CIP_DRIVE 4 bytes
data type
Produce tag 2 bytes
Tag that uses ALARM_DIGITAL 64 bytes
data type
Tag that uses ALARM_ANALOG 436 bytes
data type
Motion Group -8 bytes
Program 8 bytes
Add-On Instruction 12 bytes
SFC Routine 8 bytes
Controller (> 1K bytes change)
1769-L1y-BB1B 6600 bytes
1769-L1y-BB1B (I/O Memory) 376 bytes
1769-L2y-QB1 13588 bytes
1769-L2y-QB1B (I/O Memory) 1392 bytes
1769-L2y-QBFC1B 13564 bytes
1769-L2y-QBFC1B (I/O 1392 bytes
Memory)
1769-L3y 14984 bytes
1769-L3y (I/O Memory) 24 bytes
1756-L7xS 24720 bytes
1756-L7xS (Safety Memory) 48 bytes
1756-L7x 24720 bytes
1756-L7x (I/O Memory) 16 bytes
SoftLogix 5860 (I/O Memory) 76196 bytes
19.x to 20.x Task 1312 bytes
Program 16 bytes
Equipment Phase 8 bytes
Routine 24 bytes
Add-On Instruction 32 bytes
Project with any tags that use -76 bytes
ALARM_ANALOG or
ALARM_DIGITAL data type
Tag that uses ALARM_ANALOG 4 bytes
data type
Tag that uses ALARM_DIGITAL 24 bytes
data type
Tag that uses MOTION_GROUP 56 bytes
data type
Tag that uses 940 bytes
COORDINATE_SYSTEM data
type
Tag that uses AXIS_CIP_DRIVE 676 bytes
data type
Tag that uses AXIS data type 672 bytes
other than AXIS_CIP_DRIVE
Standard Produced tag 4 bytes + (4 bytes x number
of consumers)
Standard Consumed tag 12 bytes
Safety Produced tag 4 bytes
Safety Consumed tag 4 bytes
I/O Module 8 bytes
Module input connection 4 bytes
Module output connection 4 bytes
Controller (> 1K bytes change)
1756-L6x 1264 bytes
1756-L6x (I/O Memory) 1268 bytes
1756-L6xS 1264 bytes
1756-L6xS (I/O Memory) 1316 bytes
1756-L6xS (Safety Memory) 1312 bytes
1756-L7x 5588 bytes
1756-L7x (I/O Memory) 1296 bytes
1768-L4x, -L4xS 1212 bytes
1768-L4x (I/O Memory) 1292 bytes
1768-L4xS (I/O Memory) 1340 bytes
1768-L4xS (Safety Memory) 1312 bytes
1769-L23 (I/O Memory) 2488 bytes
1769-L31 (I/O Memory) 2492 bytes
1769-L32C, -L35CR (I/O 2812 bytes
Memory)
1769-L32E, -L35E (I/O Memory) 2496 bytes
18.x to 19.x <no change>
Application Notes
This release has the following application notes.
Out of I/O Memory Error Reported on Download (Lgx00148858, Lgx00143901)
Application Note First Identified as of Firmware Revision 24.011
Catalog Numbers:
1756 ControlLogix L7
1756 GuardLogix L7
5370 CompactLogix L1
5370 CompactLogix L2
5370 CompactLogix L3
A project download can result in an Out of I/O or Data and Logic Memory error being reported. Typically, the application includes significant HMI
communication.
When this anomaly occurs, the Estimated I/O or Data and Logic Memory tool in the controller properties indicates enough remaining memory to
accommodate the project download.
To work around this anomaly, cycle power to the controller and download the project again. If the anomaly persists after cycling power and downloading the
project again, disconnect existing HMI, RSLinx Enterprise, and FactoryTalk Alarms and Events servers, and redownload the project.
Copyright © 2020 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and Rockwell Software are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.