ControlLogix Controllers, Revision 21 Release Notes
Contents
1. Table 6 Restrictions with Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L71S 1756 L72S 1756 1738 1756 L73XT 1756 L73SXT Description IMPORTANT The following restrictions apply to enabling or disabling the Download Project Documentation and Extended Properties feature and should be considered collectively Any or none of these restrictions might apply to your application Restriction 1 Storing your project comments and tag descriptions in the controller can increase upload download times Be aware of the following e Ifyou click the Cancel dialog box during the Finalize portion of the download process the download process continues to successful completion and you may not be able to access the controller for long as 10 minutes e Ifthe Finalizing portion of the download process takes longer than 10 minutes the controller can generate a Major Non recoverable fault MNRF To work around this restriction clear the Download Project Documentation and Extended Properties checkbox when downloading the project Restriction 2 IMPORTANT This restriction exists only in environments that use multi workstation development Ifyou are using multi workstation development we strongly recommend that you configure the Logix Designer project to include all project documentation and extended properties when downloading a project to the controller This configuration setting is the default s2. CORRECTED Under certain conditions the presence absence or insertion of a SD card can cause the controller to generate a Major Non Recoverable fault For more information see Rockwell Automation Knowledgebase document 495063 You can access the Rockwell Automation Knowledgebase at http www rockwellautomation com rockwellautomation support overview page 00130075 CORRECTED This anomaly occurs only in applications that use Integrated Motion on the EtherNet IP network When the drive is running at a tight coarse update period such that last and or lost Drive to Controller D2C updates are being seen the controller extrapolates the actual position during the lost D2C updates The extrapolation algorithm computed the actual position incorrectly which resulted in incorrect velocity If the actual velocity is plotted you would see velocity spikes during lost D2C updates With the correction the actual position is computed correctly resulting in correct velocity 00133577 CORRECTED This anomaly occurs in applications that use any Motion type An autotune does not take the Motion Polarity bit into consideration properly The Motion Polarity bit is currently used by the controller when it generates motion commands to the drive but when the autotune is done by the drive it does not use the bit This could have caused unexpected motion 00133875 Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix C
3. 1756 L728 1756 1738 1756 L73XT 1756 L73SXT Description PI function block appears to stop executing as the output does not change and no instruction faults are logged If the Pl instruction is being used in Linear mode this floating point equation is used to calculate the ITerm WldInput WldInput KP x Wid x x DeltaT ITerm 2 n 1 Due to the use of the single precision floating point values it may be possible depending on the values of WLD and KP for the ITerm value to be small enough less than 0 0000001 to be lost when adding to the ITerm For more information regarding the PI instruction see the Logix5000 Controllers Process Control and Drives Instructions User Manual publication 1756 RM006 00070832 This anomaly occurs in applications that use only SERCOS Motion If you issue an Absolute Feedback Offset via an SSV instruction on the 1756 M02AS module the result is a feedback fault The feedback fault occurs regardless of whether feedback is on or off 00076298 This anomaly occurs in applications that use any Motion type Under some rare occurrences if a Motion Axis Move MAM instruction with Merge Enabled is activated during the deceleration segment of an active MAM instruction then the new MAM instruction may overshoot its programmed endpoint The occurrence of the overshoot depends on the following factors The original MAM instruction s remaining travel distance at the time of the m
4. 5000 software version 13 00 00 or later lets you estimate the memory requirements of the controller offline To upgrade to this revision you may need to use a controller with a larger amount of memory Rockwell Automation Publication 1756 RN210A EN P December 2012 4 ControlLogix Controllers Revision 21 Enhancements These enhancements are available when you use ControlLogix and GuardLogix controllers firmware revision 21 011 with the Studio 5000 Logix Designer application version 21 00 00 Table 3 Enhancements with Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L73XT 1756 1718 1756 L728 1756 1738 1756 L7SP 1756 L73SXT 1756 L7SPXT Description Pre scan of Add On Instruction Behavior The Pre scan behavior of Add On Instructions has been enhanced This enhancement can affect Pre scan behavior of Add On Instructions when indirect addressing is used This enhancement can improve the Add On Instruction initialization behavior when indirect addressing is used For more information see Rockwell Automation Knowledgebase document 481124 You can access the Rockwell Automation Knowledgebase at http www rockwellautomation com rockwellautomation support overview page HMI Connectivity and Performance Improvements HMI communication drivers can perform Rockwell Automation approved symbolic data reads Symbolic reads improve the read performance and eliminate errors being r
5. Sync time synchronization feature if one of the EtherNet IP modules listed below is used in the chassis with the controller then we recommend that you update the firmware of all your EtherNet IP modules in the chassis to major revision 3 x or later EtherNet IP modules that this restriction applies to include the following 1756 EN2T 1756 EN2TF e 1756 EN2TR e 1756 EN3TR If the EtherNet IP modules in the chassis with the controller are not all at major revision 3 x then the system may change the time master and or reductions in synchronization accuracy and system performance may result The Logix CPU security tool does not work with version21 controllers The Totalizer TOT instruction may not function properly when a converted project is downloaded to a ControlLogix controller catalog numbers 1756 L7x revision 21 This anomaly may occur under these conditions e An RSLogix 5000 project is running on a ControlLogix controller catalog numbers 1756 L7x revision 18 with the TOT instruction in Run mode The project is uploaded and saved to a new file The new file is changed to use a ControlLogix controller catalog numbers 1756 L7x revision 21 and is downloaded to a new controller of the same catalog number The project transitions to Run mode When transitioned to Run mode the TOT instruction s output value is different from the last value generated when the same project was running on the first controller To re
6. troubleshoot your ControlLogix application Provides information necessary to program operate and troubleshoot you GuardLogix application GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 Provides information specific to the use of GuardLogix controllers and safety program elements Logix5000 Controllers Execution Time and Memory Use Reference Manual publication 1756 RM087 Provides calculations of execution times and memory use for Logix5000 controllers ControlFLASH Firmware Upgrade Kit Quick Start publication 1756 05105 Contains informations about upgrading firmware and related error messages You can view or download publications at http www rockwellautomation com literature To order paper copies of technical documentation contact your local Allen Bradley distributor or Rockwell Automation sales representative Tech Notes and other resources are available at the Technical Support Knowledgebase http www rockwellautomation com knowledgebase Rockwell Automation Publication 1756 RN210A EN P December 2012 Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products At http www rockwellautomation com support you can find technical manuals technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools You c
7. 1 1756 L72 1756 L73 1756 L74 1756 L75 1756 L73XT 1756 L71S 1756 L72S 1756 1738 1756 L7SP 1756 L73SXT 1756 L7SPXT Description CORRECTED This anomaly occurs in applications that use any Motion axis type An axis can move in the wrong direction in the following conditions The Motion Axis Jog MAJ instruction faceplate of an axis is being merged is configured so that Merge Enabled and Merge Speed Current The MAJ instruction is configured in one of the following manners Profile Type Trapezoidal In this case the direction on the faceplate is set to forward Profile Type S curve In this case the sign of the current axis velocity of the axis being merged via the MAJ instruction and the sign of the velocity specified by the combination of the Direction parameter and Speed parameter on the faceplate are inconsistent You can complete the following tasks to work around this anomaly e For Profile Type Trapezoidal set the direction on the faceplate to Reverse For Profile Type S curve set the direction on the faceplate to correspond to the sign of the current axis velocity Always set the Speed parameter to 1 0 If the current axis velocity is unknown use a GSV instruction to obtain it 00136317 Known Anomalies These anomalies have been identified with firmware revision 21 011 Table 5 Known Anomalies for Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 1718
8. 48 bytes v 1756 L7xS 24720 bytes v 1756 L7x 16 bytes v 1756 L7x 24720 bytes v 1789 L10 1789 L30 1789 L60 76196 v Rockwell Automation Publication 1756 RN210A EN P December 2012 16 ControlLogix Controllers Revision 21 Table 7 Additional Memory Requirements per Application Component ae Component aa Per 1 0 Data and Logic Safety apply 19 x to 20 x Task 1312 bytes v Program 16 bytes v Equipment Phase 8 bytes v Routine 24 bytes v Add On Instruction 32 bytes v Project with any tags that use ALARM_ANALOG or ALARM_DIGITAL data type 76 bytes 4 Tag that uses ALARM_ANALOG data type 4 bytes v Tag that uses ALARM_DIGITAL data type 24 bytes v Tag that uses MOTION_GROUP data type 56 bytes v Tag that uses COORDINATE_SYSTEM data type 940 bytes v Tag that uses AXIS_CIP_DRIVE data type 676 bytes w Tag that uses AXIS data type other than AXIS_CIP_DRIVE 672 bytes S Standard Produced Tag 4 bytes 4 bytes x v number of consumers Standard Consumed Tag 12 bytes v Safety Produced Tag 4 bytes v Safety Consumed Tag 4 bytes v 1 0 Module 8 bytes v Module input connection 4 bytes v Module output connection 4 bytes v For each controller gt 1K bytes change 1756 L6x 1264 bytes v 1756 L6x 1268 bytes v 1756 L6xS 1264 bytes S 1756 L6xS 1316 bytes v 1756 L6xS 1312 bytes v 1756 L7x 5588 bytes v R
9. All instruction is executed when the coordinate motion instruction is accelerating decelerating or blending with another instruction The duration of the acceleration or deceleration is very short for example 10 coarse update periods or fewer The configured maximum deceleration of any axis in the coordinate system is significantly lower for example 50 or less than programmed maximum deceleration of the MCS instruction 00133646 Even though controllers that use firmware revision 21 011 can use ALMA and ALMD instructions FactoryTalk View Studio SE software versions 6 and 7 cannot connect to a Logix Designer application that uses firmware revision 21 011 and that use ALMA or ALMD instructions IMPORTANT This anomaly applies to the use of ALMA and ALMD instructions only Tag based alarming systems that use FactoryTalk Alarms and Events functionality work as expected Rockwell Automation Publication 1756 RN210A EN P December 2012 12 ControlLogix Controllers Revision 21 Table 6 Restrictions with Firmware Revision 21 011 Cat No Description 1756 L71 Your Logix Designer application project will not download in the following conditions 1756 L72 e The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared 1756 173 The controller s programming code uses minimum or maximum extended properties in code elements 1756 L74 tag name MIN or tag name MAX 1756
10. G data type 64 bytes v Tag that uses ALARM_DIGITAL data type 28 bytes v Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type 34 bytes v 2 bytes x number of output cam execution targets Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or 52 bytes v AXIS_GENERIC_DRIVE 2 bytes x number of output cam execution targets Tag that uses COORDINATE_SYSTEM data type of 2 dimensions with 2 20 bytes v transform dimensions Tag that uses COORDINATE_SYSTEM data type of 3 dimensions with 3 108 bytes v transform dimensions Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 19 Table 7 Additional Memory Requirements per Application Component Ifyou upgrade Then add the following memory requirements to your project Which comes from this type of memory from revision z add alll that Component pepe a Per 1 0 Data and Logic Safety apply 15 x to 16 x If you use a tag of the types listed below increase the memory as indicated for each instance Tag that uses ALARM_ANALOG data type with no associated tag references 16 bytes lt S Tag that uses ALARM_DIGITAL data type with no associated tag references 4 bytes v Tag that uses ALARM_ANALOG data type if associated tags are configured for 22 bytes v the ALARM_ANALOG tag 9x the numbe
11. INATE_SYSTEM data type with no transform dimensions 40 bytes v Tag that uses COORDINATE_SYSTEM data type with transform dimensions 100 bytes v Module input connection 20 bytes v Module output connection 24 bytes S Safety controller 8 bytes v Safety partner 8 bytes v Rockwell Automation Publication 1756 RN210A EN P December 2012 18 ControlLogix Controllers Revision 21 Table 7 Additional Memory Requirements per Application Component If youupgrade Then add the following memory requirements to your project Which comes from this type of memory from revision z add all that Component ea Per 1 0 Data and Logic Safety apply 17 x to 18 x For each controller gt 1k bytes change 1756 L6x 1756 L6xS 1756 L63XT 16728 bytes v 1768 L4x 1768 L4xS 14448 bytes WA 1769 L2x 35084 bytes v 1769 L31 14740 bytes v 1769 L32C 1756 L35CR 35400 bytes v 1769 L32E 1756 L35E 35036 bytes v 1789 L10 1789 L30 1789 L60 4992 v 16 x to 17 x Task 4 bytes v Program 4 bytes v Equipment phase 8 bytes v LD routine 12 bytes S FBD routine 8 bytes v SFC routine 28 bytes v ST routine 4 bytes v Add On Instruction 12 bytes v If you use a tag of the types listed below increase the memory as indicated for each instance Produced tag 4bytes 4bytes v number of consumers Consumed tag 8 bytes v Tag that uses MESSAGE data type 4 bytes v Tag that uses ALARM_ANALO
12. L75 To work around this restriction check the Download Project Documentation and Extended Properties checkbox when configuring the project 1756 L71S You cannot connect FactoryTalk View Studio SE software version 6 to a Logix Designer application that uses ALMA or ALMD instructions You must upgrade 1756 L72S your FactoryTalk View Studio SE software to version 7 to connect that application to a Logix Designer application that uses the ALMA or ALMD instructions 1756 L73S IMPORTANT This anomaly applies to the use of ALMA and ALMD instruction only Tag based alarming systems that use FactoryTalk Alarms and Events 1756 L73XT functionality work as expected with FactoryTalk View Studio SE software version 6 1756 L73SXT 1756 L71S With earlier revisions of GuardLogix controller firmware we recommended that you set the GuardLogix controller as the Coordinated System Time CST 1756 L725 master to avoid nonrecoverable safety faults 1756 L735 If you are using the CIP Sync enhancement with RSLogix 5000 software and a GuardLogix controller we recommend that you configure the GuardLogix controller so that it becomes the CST master To do so select Enable Time Synchronization on the Date Time tab of the Controller Properties dialog box If you do not configure the GuardLogix controller to become the CST master and your project uses safety tags that are produced 1 0 faults can occur when the project is downloaded For more information about enabling the Guard
13. Logix controller to become the CST master see the GuardLogix Controllers User Manual publication 1756 UM020 00104194 The use of a safety tag with several multicast consuming controllers at varying firmware revisions can result in a connection timeout If your application is configured with GuardLogix controllers consuming safety tags produced by a GuardLogix controller at revision 18 x and the consuming controllers of one safety tag are at varying firmware revisions you may experience a connection timeout with error code 0x203 In the event of a connection timeout all of the consuming controllers appear to connect to the tag and run for some time but then the connection timeout occurs If you use a single consumer of a safety tag that consumer will connect and remain connected To workaround this anomaly set the revision of the producing controller to the same revision as the lowest revision of the consumers connecting to the safety tag For example if you have consuming GuardLogix controllers at revisions 17 x and 18 x set the producing controller to revision 17 x to match the lowest revision of the consumers 00104877 If an application requires produce consume communication between GuardLogix controllers the 1 0 status indicator can blink giving the indication that an 1 0 fault is present even though the system is functioning properly This status indicator behavior occurs when the following conditions exist e A GuardLogix control
14. Release Notes amp Allen Bradley ControlLogix Controllers Revision 21 ControlLogix Controllers Catalog Numbers 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 ControlLogix XT Controller Catalog Numbers 1756 L73XT GuardLogix Controllers Catalog Numbers 1756 L71S 1756 L72S 1756 L73S 1756 L7SP GuardLogix XT Controller Catalog Numbers 1756 L73SXT 1756 L7SPXT Topic Page Compatible Software Versions 2 Before You Begin 3 Enhancements 4 Corrected Anomalies 5 Known Anomalies 8 Restrictions 10 Install the Controller Revision 13 Additional Memory Requirements 14 Additional Resources 21 Rockwell Allen Bradley Rockwell Software Automation 2 ControlLogix Controllers Revision 21 IMPORTANT Consider the following before upgrading the firmware on your controller e Firmware release notes contain material for all minor revisions subsequent to each major revision If your controller for example is at revision 19 011 and not the last minor revision 19 015 you should view all of the information for revisions 19 011 19 015 before updating to revision 21 xxx Before updating your controller we strongly recommend that you review information pertinent to previous major firmware revisions For example when updating from revision 19 xxx to 21 xxx view information in the following publications ControlLogix Controllers 1756 L7x controllers Revision 20 Release Notes publication 1756 RN220 Co
15. an also visit our Knowledgebase at http www rockwellautomation com knowledgebase for FAQs technical information support chat and forums software updates and to sign up for product notification updates For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect support programs For more information contact your local distributor or Rockwell Automation representative or visit http www rockwellautomation com support Installation Assistance If you experience a problem within the first 24 hours of installation review the information that is contained in this manual You can contact Customer Support for initial help in getting your product up and running United States or Canada 1 440 646 3434 Outside United States or Canada Use the Worldwide Locator at http www rockwellautomation com support americas phone_en html or contact your local Rockwell Automation representative New Product Satisfaction Return Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned follow these procedures United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor to complete the return process Outside United States Please contact your l
16. ation Consequently when a restore from removable media that is an SD card is performed the value is restored to its default value In Logix Designer application version 21 and later the Audit Mask Value is saved with the user application 00135562 CORRECTED This anomaly occurs in applications that use any Motion axis type When you restore a project from removable media that is an SD card you can restore an axis home bit and the Absolute Position Recovery APR fault bit The axis cannot be homed and experience an APR fault This anomaly can occur if the project has one or more axes experiencing an APR fault and the project is saved to the SD card If you clear the APR fault rehome the axes and restore the project from the SD card again the axis home bit and APR fault bit are restored 00135973 CORRECTED Second download fails In the following application conditions the initial project download is successful but the second download fails e PowerFlex 750 drives use a firmware revision that supports drives automatic device configuration ADC Drive Peripherals are configured to Fail Drive Connection on Peripheral Error When the second download fails the controller experiences a Major Non recoverable Fault MNRF 00135986 Rockwell Automation Publication 1756 RN210A EN P December 2012 8 ControlLogix Controllers Revision 21 Table 4 Corrected Anomalies with Firmware Revision 21 011 Cat No 1756 L7
17. ed double integer but they are treated as UDINT unsigned double integer by Logix firmware This causes negative values of the tag members to be handled as large positive numbers when they should be handled as zero 119996 CORRECTED In SFCs when using time limited actions in steps if the program stays on a given step for greater than 24 days 2 32 ms the timer s accumulator ACC will roll over and the action body starts to execute again The time limited action initializes its timer when it starts step is first scanned On subsequent scans it compares the timers PRE and ACC value If ACC lt PRE the action body will execute If ACC gt PRE it is not executed When the rollover occurs the ACC PRE and action body will execute again when it should not 00124697 CORRECTED The controller supports only three active reconfigure messages at a time If more than three are triggered at a time they will complete DN bit will go high but not all the modules will be reconfigured For example if you send five reconfiguration messages at the same time three reconfigure messages will truly complete DN bit will go high and the 1 0 modules will be reconfigured The other two reconfigure messages will indicate complete DN bit will go high but the 1 0 modules will not be reconfigured In this case the last two should have errored ER bit but do not 00125204 CORRECTED This anomaly occurs in applications that use any Motion ty
18. erge and the new MAM instruction remaining travel distance The relationship of the decel jerk of the new MAM instruction to the decel jerk of the original MAM instruction e Ifthe original MAM instruction is decelerating Typically the overshoot does not occur If either of the following conditions exist you will avoid the overshoot The new MAM instruction is programmed with Merge Disabled If there is no other motion active at the time of the merge then the Merge Disable results in the same operation as the Merge Enable The new MAM instruction has a slightly higher jerk in units seconds than the original MAM instruction You should note though lower value of jerk in of time results in higher value of jerk in units seconds 00078822 Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 9 Table 5 Known Anomalies for Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L71S 1756 L72S 1756 L73S 1756 L73XT 1756 L73SXT Description This anomaly occurs in applications that use any Motion type If a Motion Group Shutdown Reset MGSR instruction is executed while a Motion Group Shutdown MGSD is still executing motion error 7 that is Shutdown State Error results The purpose of an MGSR instruction is to bring an axis group out of the shutdown state However when the scenario described in the previous paragraph exi
19. etting A Logix Designer project can lose content from the text boxes for routines written in either Function Block Diagram FBD or Sequential Function Chart SFC programming languages when both of the following conditions exist e Multiple workstations are online with the controller The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared When project edits are made at one workstation the content in the text boxes of edited routines are deleted from all of the other workstations in the environment To work around this restriction configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is checked IMPORTANT Consider the following This anomaly does not apply if your Logix Designer project uses Ladder Logic LL or Structured Text ST programming languages Arestriction applies to when you check the Download Project Documentation and Extended Properties checkbox Restriction 3 IMPORTANT This restriction exists only in environments that use multi workstation development Ifyou are using multi workstation development we strongly recommend that you configure the Logix Designer project to include all project documentation and extended properties when downloading a project to the controller A Logix Designer project can temporarily lose content in the Rung Comments sections when all of the following conditions exist e M
20. eturned when the HMI attempts to collect data For more information see the LogixS000 Data Access Programming Manual publication 1756 PM020 Introducing the Studio 5000 Logix Designer Application The version 21 release re brands RSLogix 5000 software to Logix Designer application and embeds the application as a key component of the Studio 5000 environment The Studio 5000 environment is the new launch point for components of the Integrated Architecture The Studio 5000 environment provides the infrastructure to accomplish the following between traditionally independent automation development tasks Share data Share design time components Share runtime components Extended Tag Properties You can use Extended Properties to define additional information about a tag or structure of tags The Logix Designer application version 21 or later provides the option to specify Engineering Units and Min Max Values for numeric tags Engineering Units and state information for Boolean tags Extended properties are also available for user defined data types arrays or other complex data structures Project Documentation Stored in Controller The Logix Designer application version 21 provides the option to store all of your project documentation including comments tag descriptions and other key descriptors of the project in the controller Other project descriptions can be stored online such as routine descriptions and task descrip
21. ion ADC feature the Logix controller owns the configuration in the drive Do not use the HMI or other external tools such as DriveExplorer software to change drive parameters Doing so may cause a sequence of events to occur that results in the connection between the controller and the drive to be dropped and causes the controller to be unable to re establish the connection Consider using the Write Mask function drive Parameter 888 Write Mask Cfg to prevent tools connected to ports other than the Embedded EtherNet IP port from writing to the drive This anomaly was addressed with Drive firmware revision 4 001 00129165 CORRECTED Changes made to the Buffer Timeout value for FactoryTalk Alarms and Events subscribers do not take effect until the existing buffer is deleted The FactoryTalk alarm buffer stored in Logix controller memory is designed to persist through power cycles If you change the Buffer Timeout value via the Communication Setup dialog box in FactoryTalk View SE software the controller does not use the new timeout value until the existing buffer is deleted and then recreated To force recreation of this buffer do one of the following e Redownload the project to the controller Disconnect the FactoryTalk Alarms and Events subscriber and leave it disconnected until the existing timeout expires 00069461 CORRECTED The MinDurationPRE and MinDurationACC members of ALMD and ALMA tags are defined as DINT sign
22. le if you are upgrading from revision 16 x to revision 20 x total your application components for revisions 16 x to 17 x 17 x to 18 x 18 x to 19 x 19x to 20x and 20 x to 21 x Table 7 Additional Memory Requirements per Application Component If you upgrade from revision add all that apply 20 x to 21 x Then add the following memory requirements to your project Which comes from this type of memory Component Increase Decrease Per 1 0 Data and Logic Safety Instance PROGRAM 8 bytes v Add On Instruction 12 bytes v SFC Routine 8 bytes v Tag that uses AXIS_GENERIC data type 32 bytes v Tag that uses OUTPUT_CAM data type 512 bytes 4 Tag that uses AXIS_SERVO_DRIVE data type 8 bytes v Tag that uses CIP_DRIVE data type 4 bytes v PRODUCE_TAG 2 bytes v Tag that uses ALARM_DIGITAL data type 64 bytes v Tag that uses ALARM_ANALOG data type 436 bytes v Tag that uses MOTION_GROUP data type 8 bytes S For each controller CompactLogix 5370 L1 376 bytes v CompactLogix 5370 L1 6600 bytes v CompactLogix 5370 L2 1769 L24ER QB1B 1392 bytes v CompactLogix 5370 L2 1769 L24ER QB1B 13588 bytes S CompactLogix 5370 L2 1769 L24ER QBFC1B or 1769 L27ERM QBFC1B 1392 bytes WA CompactLogix 5370 L2 1769 L24ER QBFC1B or 1769 L27ERM QBFC1B 13564 bytes v CompactLogix 5370 L3 24 bytes v CompactLogix 5370 L3 14984 bytes v 1756 L7XS
23. ler is configured to consume data from another GuardLogix controller of a later firmware revision The consuming GuardLogix controller is a 1756 L6xS controller that uses firmware revision 19 or earlier e The producing GuardLogix controller is a 1756 L7xS controller IMPORTANT In the conditions described previously you must have two controller applications one for the 1756 L6xS controller that is the consumer and one for the 1756 L7xS controller that is the producer You cannot add a 1756 L7xS controller to a 1756 L6xS controller s RSLogix 5000 software project if the project is version 19 or earlier To work around this anomaly complete one of the following tasks Upgrade the consuming controller to use RSLogix 5000 software version 20 and firmware revision 20 xxx e Inthe consuming controller s application add a 1756 L6xS controller to the 1 0 configuration tree as the producing controller and configure it exactly as you would configure the 1756 L7xS controller This workaround causes the 1 0 status indicator to blink Despite the blinking status indicator there is no 1 0 fault 00135976 Rockwell Automation Publication 1756 RN210A EN P December 2012 Install the Controller Revision ControlLogix Controllers Revision 21 13 To download the latest ControlLogix or GuardLogix controllers firmware revision go to http www rockwellautomation com support downloads and select your desired revision Then use the ControlFLASH u
24. mber 2012 ControlLogix Controllers Revision 21 3 Before You Begin Table 2 Before You Begin If You are updating a 1756 L7x controller Before you upgrade your firmware consider the following IMPORTANT Loss of communication or power during a controller firmware upgrade may result in the controller rejecting the new firmware If the controller firmware upgrade fails due to the conditions described these corrective actions may be required e Cycle controller power and successfully complete the upgrade e Ifa nonrecoverable fault occurs then return the controller for factory repair The preliminary actions are required before upgrading your controller firmware Then Before you begin updating your controller check the status of your Secure Digital SD card If your SD card is Then Unlocked You can successfully upgrade the firmware to the intended revision Locked and the Load You should unlock the SD card before beginning the upgrade If the card is locked when Image option is settoOn you attempt to upgrade the firmware the upgrade fails and the controller reverts to the Power Up firmware revision already stored on the SD card Figure 1 SD card Unlocked and Locked Unlocked t Locked i Your controller is close to its limits of memory This revision may require more memory than previous revisions To see what components of your current project require more memory see page 14 RSLogix
25. n the 2000 bytes v same chassis This memory is allocated only when the MSG instruction is enabled To estimate count the number of these messages that are enabled and or cached at one time Rockwell Automation Publication 1756 RN210A EN P December 2012 Table 7 Additional Memory Requirements per Application Component ControlLogix Controllers Revision 21 21 If youupgrade Then add the following memory requirements to your project Which comes from this type of memory from revision z add all that Component e E Per 1 0 Dataand Logic Safety apply 6 x to 7 x If you use a tag of the types listed below increase the memory as indicated for each instance Base tag 24 bytes y Alias tag 16 bytes y Produced tag DINT 4 12 bytes v REAL 4 12 bytes v Consumed tag DINT 4 12 bytes REAL 4 12 bytes Routine 68 bytes ff 5 x to 6 x Routine 116 bytes if Additional Resources These documents contain additional information concerning related products from Rockwell Automation Resource Logix5000 Controllers Common Procedures Reference Manual publication 1756 PM001 Description Contains information specific to procedures related to programming your controller ControlLogix Systems User Manual publication 1756 UM001 GuardLogix Controllers Systems User Manual publication 1756 UM020 Provides information necessary to program operate and
26. ntrolLogix Controllers 1756 L7x controllers Revision 19 Release Notes publication 1756 RN019 Release notes are available at http www rockwellautomation com literature e After upgrading the firmware on your module we strongly recommend that you retest and or validate your application offline before going online Compatible Software Versions To use firmware revision 21 011 these minimum software versions are required Table 1 Compatible Software Versions Comparetol as sssti lt i id SS ControlFLASH 12 00 00 FactoryTalk AssetCentre 4 00 00 CPR 9 SR3 FactoryTalk Services Platform 2 50 00 CPR 9 SR5 1 FactoryTalk Activation 3 51 00 CPR 9 SR5 1 RSLinx Classic 3 51 00 CPR 9 SR5 1 RSLinx Enterprise 5 51 00 CPR 9 SR5 1 Studio 5000 Logix Designer 21 00 00 CPR9 SR5 1 RSNetWorx for ControlNet 21 00 00 CPR 9 SR5 1 RSNetWorx for DeviceNet RSNetWorx for EtherNet IP Operating system and service pack compatibility are as follows e Microsoft Windows 7 Professional 64 bit with Service Pack 1 e Microsoft Windows 7 Home Premium 64 bit with Service Pack 1 e Microsoft Windows 7 Home Premium 32 bit with Service Pack 1 e Microsoft Windows Server 2008 R2 Standard Edition with Service Pack 1 For hardware requirements go to http www rockwellautomation com rockwellsoftware design rslogix5000 sys req html Rockwell Automation Publication 1756 RN210A EN P Dece
27. o Run mode the application is not executing and the outputs are not being updated For more information see Rockwell Automation Knowledgebase document 493802 You can access the Rockwell Automation Knowledgebase at http www rockwellautomation com rockwellautomation support overview page 00134308 CORRECTED This anomaly occurs in applications that use any Motion axis type If single axis or multi axis move instructions are initiated while a Motion Redefine Position MRP instruction is in process the controller experiences Motion Error 85 This anomaly occurs when the MRP instruction is configured to use an Absolute or Relative operation With the anomaly correction motion initiated while an MRP instruction using an Absolute operation only is in process causes the controller to experience Motion Error 85 00134471 CORRECTED This anomaly occurs in applications that use any Motion type Previous to RSLogix 5000 software version 19 you could perform either an absolute immediate SERCOS only or a passive home with the drive in a safe off state In RSLogix 5000 software version 20 attempts to perform either home action with the drive in a safe off state are blocked and the controller experiences the error 16 0028 You are trying to run a motion command when the drive is locally disabled 00134717 CORRECTED In RSLogix 5000 software version 20 and earlier the Audit Mask Value is not saved as part of the user applic
28. ocal Rockwell Automation representative for the return procedure Documentation Feedback Your comments will help us serve your documentation needs better If you have any suggestions on how to improve this document complete this form publication RA DU002 available at http www rockwellautomation com literature Allen Bradley Rockwell Software Rockwell Automation CompactLogix ControlLogix ControlLogix XT DriveExplorer GuardLogix GuardLogix XT Logix5000 RSLinx RSLogix RSNetWorx ControlFLASH FactoryTalk Kinetix PowerFlex Integrated Architecture and TechConnect ate trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Rockwell Otomasyon Ticaret A S Kar Plaza Merkezi E Blok Kat 6 34752 erenk y stanbul Tel 90 216 5698400 www rockwellautomation com Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation NV Pegasus Park De Kleetlaan 12a 1831 Diegem Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 RN210A EN P December 2012 PN 172673 Copyright 2012 Rockwell Automation Inc All rights reser
29. ockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 17 Table 7 Additional Memory Requirements per Application Component Ifyou upgrade Then add the following memory requirements to your project Which comes from this type of memory from revision z add all that Component anea aa Per 1 0 Data and Logic Safety apply 19 x to 20 x 1756 L7x 1296 bytes v 1768 L4x 1768 L4xS 1212 bytes v 1768 L4x 1292 bytes v 1768 L4xS 1340 bytes v 1768 L4xS 1312 bytes v 1769 L23 2488 bytes v 1769 L31 2492 bytes v 1769 L32C 1769 L35CR 2812 bytes v 1769 L32E 1769 L35E 2496 bytes v 18 x to 19 x lt no change gt 17 x to 18 x Program 8 bytes v Equipment phase 20 bytes WA Add On Instruction 12 bytes v Each tag 4 bytes v In addition if you use a tag of the types listed below increase the memory as indicated for each instance Produced tag 36 bytes 24 bytes WY number of consumers Consumed tag 24 bytes v Data access control 4 bytes per symbol v Tag that uses ALARM_ANALOG data type 20 bytes v Tag that uses ALARM_DIGITAL data type 28 bytes v Tag that uses MOTION_GROUP data type 76 v Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type 786 bytes v Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or 818 bytes v AXIS_GENERIC_DRIVE Tag that uses COORD
30. ontrollers Revision 21 7 Table 4 Corrected Anomalies with Firmware Revision 21 011 Cat No Description 1756 L71 CORRECTED This anomaly occurs only in applications that use Integrated Motion on the EtherNet IP network 1756 L72 1756 L73 1756 L74 1756 L75 1756 L73XT 1756 L71S 1756 L72S 1756 L73S 1756 L7SP 1756 L73SXT 1756 L7SPXT An axis position register can roll back one motor revolution at powerup in the following conditions The axis uses a rotary feedback device The axis is configured for Cyclic Travel mode The axis windup point configuration is greater than the rotary feedback device s hardware rollover point Either of the following events occurs Scenario 1 The following events a The axis stops close to the feedback device s hardware rollover point b The axis is powered down c The axis moves across the hardware rollover point while powered down d The axis is powered up again Scenario 2 The axis moves beyond the cyclic windup point and power is cycled to the axis An axis that uses a linear feedback device can also lose its absolute position if the axis is beyond half of the travel range of the feedback device and a power cycle occurred on the axis 00134238 CORRECTED When using PowerFlex 750 series drives with firmware that supports Drives Automatic Device Configuration ADC on powerup the controller can become stuck in the transition to Run mode When stuck in the transition t
31. ork axis the default value for Mechanical Brake Delay 0 If you are using a motor with a brake on this axis and do not change the Mechanical Brake Delay value the motor will not work properly when you attempt to execute motion To work around this anomaly make sure that you set the Mechanical Brake Delay to the appropriate value before executing motion 00113541 This anomaly occurs in applications that use only Integrated Motion on the EtherNet IP network Every time there is a Motion Servo Off MSF instruction Motion Servo On MSO instruction cycle the Position Trim value is added to the axis position This change in axis position causes the axis to move unexpectedly by a distance equal to the Position Trim value 00113540 1756 L71S 1756 L72S 1756 L73S A 1756 GuardLogix controller can experience a Type 14 Code 8 major fault when you apply power to it in the following conditions e The controller resides in the same chassis as multiple 1756 ENxTR ControlLogix EtherNet IP communication modules The controller and the communication modules reside on the same subnet To work around this anomaly raise the Priority 1 that is the Master Override setting in the Controller Properties dialog box gt Date Time tab gt Advanced dialog box 00134930 Rockwell Automation Publication 1756 RN210A EN P December 2012 10 ControlLogix Controllers Revision 21 Restrictions These restrictions exist for firmware revision 21 011
32. ow these steps to add a user or user group to the FactoryTalk directory 1 Launch the FactoryTalk Administration Console available from the Start menu 2 Select the Network directory when prompted You may need to provide credentials for a user with Administrator privileges in order to continue 3 To allow access for a particular user navigate to Network System Users and Groups Users right click the Users folder and choose New gt Windows Linked User 4 Click Add and provide the domain logon name for the desired user You can click Check Names to verify that the name was found 5 To allow access for all authenticated users navigate to Network System Users and Groups User Groups right click the User Groups folder and choose New gt Windows Linked User Group 6 Click Add and type the name of the user group Authenticated Users The Log On to FactoryTalk dialog box may also display when using Remote Desktop to connect to the personal computer running RSLogix 5000 software This is due to FactoryTalk Security not recognizing the computer name To enable access through Remote Desktop for a specific computer you should add the name of the computer initiating the Remote Desktop connection to the Network System Computers and Groups Computers folder in the FactoryTalk Administration Console To allow all computers to connect follow these steps 1 Open the FactoryTalk Administration Console and log in to the Network directory using your domain c
33. pe Aslave axis is likely to experience jitter in the following conditions The slave axis is geared to a master axis via a Motion Axis Gear MAG instruction The gear ratio of the MAG instruction is a binary fraction for example 1 5 e The master axis is idle The last command to the master was not an integer multiple of the feedback units When this anomaly occurs the jitter is a single count 00133576 Rockwell Automation Publication 1756 RN210A EN P December 2012 6 ControlLogix Controllers Revision 21 Table 4 Corrected Anomalies with Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L73XT 1756 L71S 1756 L72S 1756 1738 1756 L7SP 1756 L73SXT 1756 L7SPXT Description CORRECTED Log On to FactoryTalk Dialog Box Displays When Launching RSLogix 5000 Software When launching RSLogix 5000 software the Log On to FactoryTalk dialog box may be displayed This dialog box may be seen when you do not have Administrator privileges on the personal computer and the current user does not exist in the FactoryTalk directory If this dialog box is cancelled the RSLogix 5000 software will not be launched When the dialog box is displayed entering the credentials for a user that has Administrator privileges on the personal computer will then allow RSLogix 5000 software to be launched To avoid seeing this dialog box you can add the current user or user group to the FactoryTalk directory Foll
34. r of configured associated tags 3x the sum of the bytes used by the data type of each of the configured associated tags For example an analog alarm moved to 16 03 with two Associated Tags one DINT 4 bytes and one STRING 88 bytes would need to add 22 9 2 3 92 316 bytes Tag that uses the COORDINATE_SYSTEM data type 132 bytes v 14 x to 15 x Input module 4 bytes v If you use a tag of the types listed below increase the memory as indicated for each instance Produced tag 12 bytes v Consumed tag 4 bytes v Tag that uses COORDINATE_SYSTEM data type 748 bytes J Tag the uses any AXIS data type 800 bytes y Task 20 bytes y Program or equipment phase 24 bytes y Routine 4 bytes y Serial port 1120 bytes 7 Project 4012 bytes A Rockwell Automation Publication 1756 RN210A EN P December 2012 20 ControlLogix Controllers Revision 21 Table 7 Additional Memory Requirements per Application Component If youupgrade Then add the following memory requirements to your project Which comes from this type of memory from revision add all that Component ea Per 1 0 Data and Logic Safety apply 13 x to 14 x If you use a tag of the types listed below increase the memory as indicated for each instance Tag that uses the COORDINATE SYSTEM data type 60 bytes y Tag that uses any AXIS data type 4 bytes y 12 xto 13 x Program 12 b
35. redentials 2 Navigate to Network System Security Policy In the Computer Policy Settings section set Identify terminal server clients using the name of to Server Computer Important If Use Single Sign on is set to disable in FactoryTalk software then the Log On to FactoryTalk dialog box will be displayed each time RSLogix 5000 software is launched and proper user credentials must be entered in order to continue By default Use Single Sign on is set to enable 00124955 CORRECTED The RSLogix 5000 Clock Update tool does not support Windows 7 or Windows Server 2008 operating system CORRECTED This anomaly occurs only in applications that use Integrated Motion on the EtherNet IP network Changes have been made to make recovery from a Soft Overtravel SOT condition on an Axis CIP Drive easier ASOT fault is currently defined such that the following conditions cause the fault The commanded position is on or beyond the SOT position The commanded motion is in the direction of the overtravel Complete the following tasks to recover from the SOT fault 1 Reset the SOT fault 2 Enable the drive if it is disabled 3 Command motion in the opposite direction of the SOT position The following conditions are a result of this anomaly correction The SOT fault will not immediately recur if the drive is enabled outside the SOT position range No SOT exceptions will be generated when the axis is in the Stopped state 00129650
36. ry estimation tool provided with RSLogix 5000 software or Logix Designer application or the tables provided in these release notes Use the Estimate Tool To estimate the amount of memory required by your application convert the project to the controller revision desired and use the Estimate tool available in the Memory tab of the Controller Properties Controller Properties App_001 E jol x General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced SFC Execution File Redundancy Nonvolatile Memory Memory Memory Option 1756 L75 v Estimated I O Memory Estimated Data and Logic Memory i Total 505 856 bytes F Total 8 388 608 bytes 3 L Free 488 352 bytes j _ Free 8 372 496 bytes E Used 17 504 bytes E Used 16 112 bytes F 4 Max Used 17 504 bytes s Max Used 16 112 bytes Largest Block Free 488 352 bytes Largest Block Free 8 372 496 bytes Estimate Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 15 Estimate Based on Application Components If you do not have the desired version of RSLogix 5000 software or Logix Designer application use this table to estimate the additional memory that your project may require If you are upgrading your system through multiple firmware revisions add all components your application uses for each of the revisions you upgrade through For examp
37. set an invalid Totalizer value set the ProgResetReq or OperResetReq to move the value of the instruction s Reset input parameter to the instruction s Total output parameter Repeat this task once more to move the invalid value out of the instruction s OldTotal output parameter 00114767 IMPORTANT This restriction applies to SERCOS Motion applications that use only Kinetix SERCOS drives and linear motors Under certain conditions it is possible that the Real Time Axis attribute VelocityFeedback contains an incorrect value The inaccuracy is the result of incorrect scaling of that attribute Your program will have an incorrect value for the VelocityFeedback attribute if you do the following 1 While offline you write your RSLogix 5000 program and as part of that program the VelocityFeedback attribute is selected 2 You save the program and download it to the controller 3 You go online The VelocityFeedback attribute value is incorrect because that attribute was enabled before the program was saved downloaded and put online To work around this anomaly do not enable the VelocityFeedback attribute until the RSLogix 5000 program is online 00107793 This restriction applies to applications that use any Motion type In the Logix Designer application version 21 stopping coordinated motion by using a Motion Coordinated Stop MCS All instruction could take longer than expected if the following conditions existed e The MCS
38. sts the MGSR instruction is not executed because the shutdown procedure initiated by the MGSD instruction has precedence Thus the MGSR instruction generates motion error 7 because the shutdown procedure has not completed The shutdown procedure must complete before any attempt to reset the shutdown 00095484 This anomaly occurs in applications that use only Integrated Motion on the EtherNet IP network With any coordinated move in a system that uses two or more Integrated Motion on the EtherNet IP network axes if one axis is disabled using a Motion Servo Off MSF instruction any remaining Integrated Motion on the EtherNet IP network axes will generate an Excessive Velocity Error that is Drive Error 55 00105595 When you accept edits in LD ST and FBD the controller will log an Online Edit entry in the controller log Accepting edits in a SFC routine is done by performing a partial import resulting in a Transaction Commit entry in the controller log This is confusing because you can select to mask both entries separately Selecting only Online edits would cause the Audit Value to change when only FBD ST and LD edits are made SFC online edits would change the Audit Value if only the Partial Import Online Transaction Completed bit was set 00122622 This anomaly occurs in applications that use only Integrated Motion on the EtherNet IP network When you create a new Integrated Motion on the EtherNet IP netw
39. tility to upgrade your controller Alternatively if you have installed RSLogix 5000 software version 16 and related firmware you may not need to complete the tasks described The AutoFlash feature of RSLogix 5000 software detects if your controller firmware needs to be upgraded upon a program download to the controller If a firmware upgrade is necessary AutoFlash will initiate an upgrade After you have completed your firmware upgrade complete these steps to verify that the upgrade was successful 1 Cycle power to the controller 2 Go online with the controller and view controller properties 3 Verify that the firmware revision listed matches the firmware to which you intended to upgrade 4 Ifthe controller s firmware is not correct initiate another firmware upgrade For more information about errors when completing a ControlFLASH upgrade see the ControlIFLASH Firmware Upgrade Kit Quick Start publication 1756 QS105 Rockwell Automation Publication 1756 RN210A EN P December 2012 14 ControlLogix Controllers Revision 21 is firmware revision may require more memory than previous revisions for itional Memory This fi ision may requi y than previ isions fi Requirements example if you are upgrading from a 1756 L6x controller running version q 16 00 00 software to a 1756 L7x controller running version 21 00 00 software To estimate additional memory requirements for your application you can either use the memo
40. tions Uploading a project now restores all of the original project documentation without having to find the original ACD file Motion Axis Output Cam Expansion This enhancement applies to applications that use any Motion type The Motion Axis Output Cam MAOC instruction now supports additional devices for scheduling Up to 16 scheduled outputs are now supported Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 5 Corrected Anomalies These anomalies have been corrected with this firmware revision Table 4 Corrected Anomalies with Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L73XT 1756 L71S 1756 L72S 1756 L73S 1756 L7SP 1756 L73SXT 1756 L7SPXT Description CORRECTED This anomaly occurs only in applications that use SERCOS Motion In Axis Servo Drive data types SERCOS the axis is not allowing execution of motor feedback or marker test while the axis safe off input is open This operated correctly in version 19 00 00 but does not operate correctly in version 20 00 00 00128300 CORRECTED This anomaly occurs only in applications that use Integrated Motion on the EtherNet IP network In Axis CIP Drive data types the axis is not allowing execution of motor feedback or market test while the CIP Axis State is in start inhibited or precharge 00128828 CORRECTED When using the Automatic Device Configurat
41. ultiple workstations are online with the controller The project is configured such that the Download Project Documentation and Extended Properties checkbox is cleared The Logix Designer project uses the Ladder Logic programming language When project edits are made at one workstation the content in the Rung Comments sections for the project rungs is briefly hidden in all of the other workstations in the environment When rung edits are finalized on the workstation that is making edits the content in the Rung Comments sections for the project rungs reappears in the in all of the other workstations in the environment To work around this anomaly configure the Logix Designer project so that the Download Project Documentation and Extended Properties checkbox is checked 00135928 Rockwell Automation Publication 1756 RN210A EN P December 2012 ControlLogix Controllers Revision 21 11 Table 6 Restrictions with Firmware Revision 21 011 Cat No 1756 L71 1756 L72 1756 L73 1756 L74 1756 L75 1756 L71S 1756 L72S 1756 L73S 1756 L73XT 1756 L73SXT Description Arithmetic State flags anomalies 1 When dealing with Floating point numbers the controller does not truncate denormalized values or 0 0 0 0 2 For an integer divide when the denominator is 0 the S N and S Z are not set 3 For the MOD instruction the S V is not set if an overflow occurred during the calculation 00122480 With the use of the CIP
42. ved Printed in the U S A
43. ytes y Task 4 bytes y User defined data type 4 bytes y 1 0 module 16 bytes Z Iz 8 8 bytes bytes If you use a tag of the types listed below increase the memory as indicated for each instance Produced tag 8 bytes v Consumed tag 8 bytes v 11 xto 12x 1 0 module with a comm format Rack Optimization 90 bytes y 1 0 module with a comm format something other than Rack Optimization such 144 bytes y as a direct connection CompactLogix 1769 1 0 module 170 bytes v Bridge module with a comm format None 160 bytes y Bridge module with a comm format Rack Optimization 220 bytes v4 10 xto 11 x User defined data type 128 bytes y Number of user defined data types in the controller organizer gt Data Types folder gt User Defined folder Not the use of that data type in tags Indirect address using a tag as the subscript for an array in an instruction such as 60 bytes S an Array_A Tag_B This memory change applies only if the array Uses a structure as its data type Does not use one of these data types CONTROL COUNTER PID or TIMER Has only one dimension such as UDT_1 5 9 x to 10 x Program 12 bytes Z Routine 16 bytes y 8 x to 9 x If you use a tag of the types listed below increase the memory as indicated for each instance Tag that uses the MESSAGE data type 376 bytes y 7 x to 8 x Project 1050 bytes v Tag 0 55 bytes y Message that transfers more than 500 bytes of data and targets a controller i
Download Pdf Manuals
Related Search