1769-RN016 - Rockwell Automation
Contents
1. ArmorPOINT 1 0 modules For more information on using the 1734 AENT or 1738 AENT adapters with Logix controllers that have been upgraded to firmware revision 16 x or later see e POINT 1 0 EtherNet IP Adapter Release Notes publication 1734 RN002 e ArmorPOINT 1 0 Release Notes publication 1738 RN002 System Overhead Time Slice The System Overhead Time Slice SOTS lets you reserve a percentage of the controller processing resources for the handling of communication Prior to this release any unused part of the SOTS was used by the controller to resume the continuous task This firmware revision lets you configure the unused portion of SOTS to either e run the continuous task default legacy mode allowing for faster execution of application code e reserve it for communication providing for more predictable and deterministic continuous task scan time This enhancement allows the full impact of communication on the continuous task to be determined if time reserved for communication were always fully used Rockwell Automation Publication 1769 RNO16F EN E February 2013 6 CompactLogix Controllers Revision 16 Corrected Anomalies These anomalies have been corrected in previous firmware revisions Table 3 Anomalies Corrected in Previous Firmware Revisions Firmware Revision Anomaly 16 22 A Digital Alarm ALMD configured to trigger when the input condition of the alarm is false does not trigger if the alarm2. condition is false when you conduct a download or return to Run mode Description When the Condition parameter of the ALMD instruction is not set that is Input 0 and either the program has recently been downloaded to the controller or the controller has been changed from Run to Program and back to Run mode the alarm is not activated that is the InAlarm bit is not set These behaviors may result depending on your application Programming designed to respond to the activated alarm is not executed Messages designed to be indicated at the operator station in response to the activated alarm are not indicated The alarm s history log does not indicate that the alarm was activated If you choose not to upgrade to this revision you must toggle the Condition parameter from set that is Input 1 to not set that is Input 0 to activate the alarm If and Condition parameter is set then the alarm activates as expected after you download or change the controller mode Lgx000104434 Fault handlers can be defined at the controller and program scope levels These fault handlers are typically used to handle major recoverable faults that can occur during runtime execution of an application due to programming errors A typical example of this would be handling indirect addressing that has gone out of range MyTagl index where index is larger than the size of the array Faults can also be handled by the controller during
3. E 1769 L31 1769 L32C 1769 L32E 16 04 1769 RNO16B 1769 L35 R 1769 L35E 1769 RNO16A 1769 131 1769 L32C 1769 L32E 16 03 1769 L35CR 1769 L35E Compatible Versions of Software To use this controller revision the following minimum software versions are required Software Required Version RSLinx Classic 2 51 RSLinx Enterprise 4 00 RSLogix 5000 16 00 RSNetWorx for ControlNet 8 00 RSNetWorx for DeviceNet RSNetWorx for EtherNet IP 1 Note that firmware revision 16 21 or later is compatible with RSLogix 5000 software version 16 00 However with firmware revisions 16 21 and 16 22 the corrected anomalies and enhancements described in these release notes are available only when RSLogix 5000 software version 16 03 or later is used Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 3 Before You Begin Before you upgrade your firmware please consider the following IMPORTANT Loss of communication or power during a controller firmware upgrade may result in the controller s rejection of the new firmware If the controller firmware upgrade fails due to the conditions described the following corrective actions may be required e Cycle controller power and successfully complete the upgrade e Return the controller for factory repair if a nonrecoverable fault occurs The following preliminary actions are required before upgradi
4. Release Notes Allen Bradley CompactLogix Controllers Revision 16 Catalog Numbers 1769 L31 1769 L32C 1769 L32E 1769 L35 R 1769 L35E About This Publication Topic Page About This Publication 1 Compatible Versions of Software 2 Before You Begin 3 Enhancements 4 Corrected Anomalies 6 Known Anomalies 9 Restrictions 12 Known Issues 13 Hold Last State and User defined Safe State Not Supported 14 Additional Resources 17 IMPORTANT Before updating your controller we strongly recommend that you review information pertinent to previous major firmware revisions For example when updating from revision 15 x to 16 x view information for revision 15 in the CompactLogix Controllers Revision 15 Release Notes publication 1769 RN015 in addition to the content of these release notes Firmware release notes contain material for all minor revisions subsequent to each major revision If your controller for example is at revision 15 3 and not the last minor revision 15 5 you should view all of the information for revision 15 3 15 5 before updating to revision 16 x CompactLogix Controllers Revision 15 Release Notes publication 1769 RN015 are available at http rockwellautomation com literature This publication describes enhancements and anomalies known and corrected for CompactLogix controllers revision 16 Information that has been added or changed since the last revision of this p
5. are Any computer terminals online with the controller indicate that the controller is in Program mode All Periodic and Event based tasks are put into Program mode All 1 0 modules are put into and behave as in Program mode Specifically on output modules output values will not update even though the Continuous Task programming may try to update or change them All motion groups are put into Program mode see the behaviors section below for more information Produced consumed data continues to transfer All out going communication messages are stopped The following anomalous behaviors may result depending on your application The producing controller may not be identified as being in Program mode Unexpected changes in outputs may occur when switched back to Run mode Load Store into nonvolatile memory may not complete successfully Motion instructions may continue to be executed when in Program mode Lgx00080240 Serial DF1 connections may timeout unexpectedly Serial connections made to the controller may timeout Timeouts may be noticed in these situations e Ifthe programming terminal connection is made through the controller serial port the timeout results in a lost connection between RSLogix 5000 software and the controller e If communication is configured by using the DF1 driver in RSLinx software the events log may contain notices of errors in the connection with the controller Message instructions
6. automation 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 1769 RNO16F EN E February 2013 PN 188539 Supersedes Publication 1769 RNO16E EN E February 2010 Copyright 2013 Rockwell Automation Inc All rights reserved Printed in the U S A
7. d The discrepancy in the WALLCLOCKTIME may also result in a MNRF during controller power down or just after controller power has been cycled To avoid this behavior use the DateTime attribute and arithmetic to handle the GMT offset instead of using the LocalDateTime attribute to set the local controllers WALLCLOCKTIME object Lgx00078925 Setting the message timeout bit T0 causes a major nonrecoverable fault MNRF Setting the message timeout bit T0 within the message control structure while the message is active may result in a MNRF of the controller To avoid the MNRF do not manipulate the message timeout bit T0 Instead change the values for the unconnected timeout UnconnectedTimeout and connection rate ConnectionRate in the message control structure Changing the unconnected timeout UnconnectedTimeout and connection rate ConnectionRate values from their defaults to smaller values causes the message instruction to error earlier and avoids the MNRF For more information about changing the values in the message control structure see the Logix5000 Controllers General Instruction Reference Manual publication 1756 RM003 Lgx00098991 Serial port control structure bit RN inaccurately cleared This anomaly occurs when using firmware revision 16 20 or later If the ACL instruction is used to clear instructions from the ASCII queue the serial port control structures RN bit is cleared that is the RN bit is set to
8. dexed tag within an Add On Instruction instance tag is not accepted by the RSLogix 5000 program Description In RSLogix 5000 software version 16 00 if you use an indirectly indexed array in an instance tag of an Add On Instruction anomalous behavior may result For example in the instruction call MyAOI AOIData Index thevalue Index selectsthe AOTData tag element used to call MyAOT Theuse of Index results in anomalous behavior when the program is executed In RSLogix 5000 software version 16 03 and controllers firmware revision 16 20 if an indirectly indexed tag is used in an instance tag the edit is not accepted by the program Instead use a directly indexed instance tag For example instead of using tag MyAOI AOIData Index usetagMyAOI AOIData 2 orsimilarso that the exact element of the array is directly indexed The program accepts directly indexed instance tags You may continue to use indirectly addressed tags in Add On Instruction parameters without anomalous behavior in RSLogix 5000 software versions 16 00 and 16 03 Lgx00077261 Passing a User defined Data Type UDT into an Add On Instruction results in a Major Recoverable Fault or data memory corruption An anomaly occurs when you pass a tag based on a User defined Data Type UDT into an Add On Instruction and certain conditions are met that result in a Major Recoverable Fault or data memory corruption A Major Recoverable Fault or data memory corr
9. e Revisions 16 00 16 023 continued Anomaly When the SFC instruction s Last Scan of Active Steps option is set to Automatic Reset a Major Non Recoverable Fault occurs Description A Major Non Recoverable Fault may occur when these elements are present in the program e Within an SFC a JSR instruction is used to jump to another SFC also know as a nested SFC e One or more of the nested SFC instructions contains Simultaneous Branches e The Last Scan of Active Steps option specified in the SFC Execution tab of the controller Properties dialog is set to Automatic Reset To avoid a Major Non Recoverable Fault when these elements are present set the Last Scan of Active Steps to Don t Scan or to Programmatic Reset Lgx00072702 A function block is initiated either directly or indirectly by an SFC instruction when the parent step becomes active During the first scan of an SFC step the Step FS bit is set In addition the S FS bit is set which allows the logic in any associated actions to easily detect the first scan state This behavior is useful when a subroutine that is called by multiple actions actions that may be connected to other steps is used The first scan state can be detected without programming a reference to the tag of a specific step Many function blocks contain internal data that must be initialized before the block can be used One of the methods a block uses to determine if it should initialize is by evaluati
10. hood of the controller faulting and remove the excessive memory consumption The firmware upgrade eliminates the controller major non recoverable faults caused by this anomaly These RSLinx Enterprise patches are on the Rockwell Automation Knowledgebase http www rockwellautomation com knowledgebase RSLinx Enterprise software version 5 00 CPR9 ID number 65818 RSLinx Enterprise software version 5 17 CPR9 SR1 ID number 65819 RSLinx Enterprise software version 5 20 CPR9 SR2 ID number 65820 Lgx00106378 Lgx0075608 Continuous task continues to be scanned in Program mode After the Logix controller has been placed into Program mode after being in Run mode either by using the key switch or by using the RSLogix 5000 software menus the Continuous Task may continue to be scanned as though it were still in Run mode This issue occurs only when the System Overhead Time Slice is set to Reserve for System Tasks eg Communications This issue is more likely to occur when the System Overhead Time Slice is increased the higher the percentage the more likely the occurrence of the issue When the controller is switched to Program mode and the Continuous Task continues to scan these system behaviors take place The RUN status indicator turns off The Continuous Task continues to be scanned and logic within the Continuous Task is solved This behavior is observable in the logic window for the Continuous Task in RSLogix 5000 softw
11. in a task overlap occurs This task overlap causes the controller to declare a minor fault of Type 6 Task Overlap Code 4 VA task You can use various strategies to resolve minor faults due to task watchdog timeout and or task overlap For more information see RSLogix 5000 Online Help Identifying and Managing Tasks In the case of a minor fault caused by VA task overlap increase the RPI until the overlap no longer occurs e Ifa 1769 I O fault occurs you must cycle power to the CompactLogix controller after clearing the major fault I O communication are not restored until after the power cycle You should never use the fault handling routine to clear local I O faults You should clear local I O faults manually on a per case basis and then the controller should be power cycled e RSLogix 5000 software creates tags for modules when you add them to the I O configuration The 1769 module tags define configuration C data type members that may include attributes for alternate outputs The CompactLogix system does not enable local modules to use the alternate outputs Do not configure the attributes listed below For Digital Output Modules For Analog Output Modules ProgloFaultEn CHxProgToFaultEn ProgMode CHxProgMode ProgValue CHxFaultMode FaultMode Where CHx the channel number FaultValue Any 1769 Compact I O modules used as remote I O modules in a CompactLogix system do support the Hold Last Sta
12. ired conditions exist the fault will occur during prescan Lgx00074725 16 03 Extensive use of UID and UIE If you use extensive amounts of UID and UIE instructions when the controller is put into Run mode a Major Recoverable instructions results in a User Task Watchdog timeout fault Fault type 6 code 1 Task Watchdog Expired may be logged Attempts to clear the fault and return to Run mode are unsuccessful Lgx00050393 Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 9 Table 3 Anomalies Corrected in Previous Firmware Revisions continued Firmware Revision Anomaly Description 16 03 Event Task Overlap Counter If an application that uses event based tasks is downloaded to the controller and then the controller is put into Run registers large values after the mode the overlap counts for event based tasks may exceed 800 000 This value is a false indication of task overlaps and controller is put into Run mode does not affect the execution of event based tasks Lgx00058132 Changes to RPI are not If you are online with one controller from two or more workstations and you alter the RPI setting for an 1 0 connection correlated between all on one workstation the change in RPI does not register on the other workstations The change in RPI registers only if the workstations when multiple altered RPI program is uploaded from the controller by the other works
13. m of the bytes used by the data type of each of the configured associated tags For example an analog alarm moved to V16 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 15 x or earlier Input module A bytes vA Produced tag 12 bytes v Consumed tag 4 bytes vA Task 20 bytes y Program or equipment phase 24 bytes y Routine 4 bytes y Tag that uses COORDINATE_SYSTEM data type 748 bytes y Tag the uses any AXIS data type 800 bytes y Serial port 1120 bytes y Project 4012 bytes vy 14 x or earlier Tag that uses the COORDINATE SYSTEM data type 60 bytes y Tag that uses any AXIS data type 4 bytes y Rockwell Automation Publication 1769 RN016F EN E February 2013 16 CompactLogix Controllers Revision 16 If you have this firmware Then add the following memory requirements to your project Which comes from this type of revision add all that memory appl pply Component Increase Per Instance 1 0 Data and Logic base expansion 13 x or earlier Program 12 bytes y Task 4 bytes vy User defined data type 4 bytes Z 1 0 module 16 bytes y y 8 bytes 8 bytes Produced or consumed tag 8 bytes v 12 x or earlier 1 0 module with a comm format Rack 90 bytes Optimization 1 0 module with a comm format something other 144 bytes than Rack Optimization such as a direct connection CompactLogix 1769 1 0 module 170 by
14. may error and display error codes 16 203 Connected timeout and 16 204 Unconnected timeout Lgx00080320 The Alarms and Events Buffer times out sooner than expected The Alarms and Events Buffer when configured to use values higher than 72 minutes may time out sooner than configured to The early timeout may result in the loss of some Alarm data Lgx00077990 Rockwell Automation Publication 1769 RNO16F EN E February 2013 8 CompactLogix Controllers Revision 16 Table 3 Anomalies Corrected in Previous Firmware Revisions continued Firmware Revision Anomaly Description 16 20 Changing the controller mode When the controller mode is changed from Run to Program and an alarm instruction has a delivery state of In Progress from Run to Program is the controller does not change modes unsuccessful To view the delivery state open the Alarm Properties dialog and click the Messages tab This anomaly may occur even when the controller is not connected to a FactoryTalk Alarm server Lgx00075913 Simultaneous branches ina When executing a simultaneous branch it may take two scans of the routine before all of the simultaneous branches sequential function chart may execute It does not take more than two scans for all simultaneous branches to completely execute not execute at the same time or Lgx00075143 in the same scan During PreScan a Major Each task programmed for a Logix controller has a PreSca
15. n Watchdog of 5 seconds You cannot change this setting in Recoverable Fault Type 6 Code RSLogix 5000 software 1 occurs The fault typically occurs when these elements are present in the program e Add On Instructions that use PreScan mode Alarge program with many tasks and subroutines where a majority of the application memory is used by the application code and not tags Other elements and factors may also cause the fault however those listed are the most common When the fault occurs the PreScan Watchdog has been exceeded With this firmware revision the PreScan Watchdog has been increased to 60 seconds Lgx00077337 16 20 Use of an ACL with other ASCII Ifan ACL instruction is executed while other ASCII instructions are active a Major Non Recoverable Fault may occur Serial Port instructions may Lgx00076857 result in a Major Non Recoverable Fault Add On Instructions yield When calling an Add On Instruction if the data types of the tags passed into or out of the instruction do not match the unexpected results parameter definitions unexpected behavior can result In the logic of an Add On Instruction reading a tag of type INT can also yield incorrect results Lgx00075524 Digital alarms ALMD may The tag InAlarm reports the alarm InAlarm 1 before the time entered in the MinDurationPRE tag expires prematurely report an in alarm Lgx00075889 state 16 04 PanelView Plus operator When the application on the PanelView Plus opera
16. n of a floating point denormalized number 3 And task B completes as task A begins again Lgx00057774 Known Anomalies This table lists known anomalies of controller revisions 16 00 16 023 Table 4 Known Anomalies for Firmware Revisions 16 00 16 023 Anomaly Program is lost after clearing an 1 0 fault Description After clearing a fault due to a missing 1 0 module and cycling power to the CompactLogix controller the program is lost from controller memory and no fault is logged Lgx00082169 An invalid Process Variable PV used by a Proportional Integral Derivative PID instruction results in a control loss of the PV When an invalid Process Variable PV value for example a positive infinity INF or not a number NaN is used by the Proportional Integral Derivative PID instruction the PID instruction becomes stuck and control of the PV is lost To reset the instruction and recover control you have to access the Data array of the PID instruction and clear any values that are invalid The PID instruction would then begin to control the PV Lgx00082890 Use of an FFU instruction in an SFC program results in a major nonrecoverable fault MNRF Use of an FFU instruction in an SFC program results in a major nonrecoverable fault MNRF when the last scan of the SFC is configured to Auto Reset Lgx00096621 Use of FIND instruction results in a major recoverable fault MRF Attempts to use the FIND instructi
17. ng the S FS bit which the function block identifies as the first scan following a prescan Lgx00071558 An SFCR action continues to post scan on the specified action This anomaly occurs only if the SFC Last Scan of Active Steps option is set to Programmatic Reset or Automatic Reset When the default Don t Scan is set the anomaly does not occur The intention of a reset action type R is to terminate the execution of another action that was previously stored When configured as described above the reset action causes logic to execute a final scan The reset action does not check to verify that an action is stored before it completes the final scan As a result each time the reset action is scanned the target logic will be scanned one last time These observable behaviors may result The timer of the stored action will continue to time even though the action is no longer active The logic in the stored action will be executed in the configured mode e At Automatic Reset non retentive outputs are cleared At Programmatic Reset the logic will execute In this situation the action logic checks for the final scan condition action A 1 and action Q 0 and performs some shutdown operations This is the code that will be executed Lgx00069295 A1769 L31 controller firmware upgrade fails if configured at 38 400 bps or higher When upgrading firmware on a 1769 L31 controller if the serial DF1 driver is configured to o
18. ng your controller firmware If Then Your controller is connected Disconnect it from the DH 485 network before you update the firmware of the controller If you update the firmware of a controller while it is to a DH 485 network connected to a DH 485 network communication on the network may stop Your controller is close to its This revision may require more memory than previous revisions limits of memory To see what components of your current project require more memory see page 15 RSLogix 5000 software version 13 0 or later lets you estimate the memory requirements of the controller offline To update to this revision you may have to upgrade to a controller that has more memory You are attempting to We recommend that you complete the following tasks before attempting a controller firmware upgrade upgrade the firmware ona First check the status of the MS module status status indicator next to the Ethernet port If it is flashing red before you begin the upgrade 1769 L32E or 1769 L35E additional action may be required Contact Rockwell Automation Technical Support for more information controller to revision 16 x Modify the Port Configuration for the Ethernet card so that the Network Configuration Type is set to Static and assign a valid IP address If RSWho is actively browsing the controller through an Ethernet or serial connection close the RSWho window to stop the browse If other controllers are messaging t
19. ntative Tech Notes and other resources are available at the Technical Support Knowledgebase http www rockwellautomation com knowledgebase Rockwell Automation Publication 1769 RNO16F EN E February 2013 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 can 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 rockwellautoma
20. o the 1769 L32E or 1769 L35E controller take the other controllers off the network or put them in Program mode If there are controllers consuming tags from the 1769 L32E or 1769 L35E controller remove them from the network e Ifthere are HMI devices connected to the controller disconnect them from the network or shut them down IMPORTANT If you cannot perform the tasks listed above before attempting a controller firmware upgrade Ethernet traffic on the controller s Ethernet port may cause the ControlFlash utility to timeout during the firmware upgrade If the timeout condition is not handled properly you may render the Ethernet port on the controller inoperable requiring you to return the controller to Rockwell Automation for repair In the event that a ControlFlash timeout occurs the software displays an error dialog indicating that the Target Device failed to report the new revision number or that the upgrade Failed to begin update to the target device If the error dialogs display check the MS status indicator If the indicator is flashing red the upgrade is still in progress and should not be interrupted Do not cycle power to the controller while the status indicator is flashing red If the upgrade completes the controller power cycles itself and indicates the upgrade is complete with a solid green MS status indicator The time required to complete the upgrade is dependent on the level of Ethernet traffic If
21. on to search a large string of characters results in a MRF If you attempt to use the ASCII FIND instruction to search a source data string of 32 767 characters or more a major fault Type 4 Code 51 results Lgx00094007 Carry Status flag not set as expected When certain values are converted from a floating point number to an integer the Carry Status flag S C is not set as expected for the value being converted Lgx00074175 Rockwell Automation Publication 1769 RNO16F EN E February 2013 10 CompactLogix Controllers Revision 16 Table 4 Known Anomalies for Firmware Revisions 16 00 16 023 continued Anomaly Using an SSV instruction to set a task priority of 0 results in unexpected execution times Description If you use an SSV instruction to set a task s priority at 0 by using the class name Task attribute Priority abnormal task execution times result This because tasks cannot have a priority of 0 permissible priority values are 1 15 To avoid abnormal task execution times do not use the SSV instruction to set a task s priority at 0 Lgx00076850 Setting the WALLCLOCKTIME object may result in a Major Nonrecoverable Fault MNRF or an incorrect WALLCLOCKTIME value Using an SSV instruction to set the local controller s WALLCLOCKTIME using the LocalDateTime attribute may result in an incorrect WALLCLOCKTIME value upon execution of the program This incorrect time is usually evident in the seconds fiel
22. or non recoverable faults MNRFs Description Causes of this anomaly include e a controller that was or is near its limits in memory doing many online edits tag additions and deletions without downloading again using RSLinx Enterprise software CPR9 When this anomaly occurs the controller generates a major non recoverable fault during an online edit tag additions and deletions 1 0 goes to their configured safe state and the user application is cleared from memory At this point a Code 1 Type 60 or 61 major fault will be logged in the controller This requires you to download the application again When online edits are made to a controller RSLinx Enterprise software CPR9 monitors them When a large number of edits are made to a controller RSLinx Enterprise software CPR9 re optimizes communication to the controller Two anomalies in RSLinx Enterprise software CPR9 are aggravating factors to this controller anomaly e The algorithm used to determine if communication re optimization is needed causes communication re optimization to occur too often e When the communication re optimizations occur the connections to the controller should close However these connections do not close This causes the controller to orphan all information related tags on scan by RSLinx Enterprise software CPR9 You must upgrade your controller firmware and apply RSLinx Enterprise patches The RSLinx Enterprise patches reduce the likeli
23. ot verify and can no longer be downloaded without first editing the modified literal value The edit may be successfully performed either online or offline Note however that when editing online because the rung is in an unverified state the Finalize All Edits in Program will not operate In this case use of the Accept Test Assemble sequence of operations will allow the edit to be completed This condition does not affect the executing image which will continue execution using the unmodified literal value To avoid exposure to this problem replace the literal value with a reference to a tag having the desired value Lgx00077802 Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 13 Known Issues The following are known issues associated with this controller revision e With a 1769 L31 controller you cannot bridge from one serial port to the other You can bridge from either serial port to DeviceNet network via the 1769 SDN scanner e Tasks are the basic scheduling mechanism for executing a program and are created as part of the project and program creation process In addition to other internal tasks the CompactLogix controllers have an internal task to provide communication with the 1769 I O modules This task executes periodically at the Requested Packet Interval RPI selected in the properties of the CompactBus If the task has not completed before it is time to execute aga
24. perate at a baud rate higher than 19 200 bps the upgrade may fail If a flash upgrade fails you must cycle power to the controller reset the baud rate to 19 200 bps and initiate a new flash upgrade Lgx00070538 Attempts to download a program to a controller following a failed firmware upgrade are successful Failure is indicated by the OK status indicator flashing red after the upgrade is complete After a firmware upgrade attempt fails during the upgrade for example the cable is disconnected or communication is interrupted the controller s OK status indicator flashes red and any user attempts to clear the fault by toggling the controller s keyswitch are unsuccessful You can download a program to the controller place the controller in Run mode and run the program the RUN status indicator displays run status The outputs behave as specified by the program However when controller power is cycled the program is lost and the controller properties indicate a firmware revision different from that most recently downloaded to the controller Lgx00071250 Rockwell Automation Publication 1769 RNO16F EN E February 2013 12 CompactLogix Controllers Revision 16 Restrictions These restrictions apply to the use of CompactLogix controllers at any minor revision of firmware revision 16 that is firmware revisions 16 03 16 023 Table 5 Restrictions with Firmware Revision 16 16 023 Restriction Use of an indirectly in
25. pre scan of the controller program on the transition to Run mode Again for example the handling of indirect addressing that has gone out of range There is an anomaly when these methods attempt to handle a fault These are the possible ways the anomaly can manifest itself The controller will experience a major non recoverable fault 1 0 goes to their configured safe state and the user application is cleared from memory At this point a Code 1 Type 60 or 61 major recoverable fault will be logged in the controller This requires you to redownload the application Tag data corruption e Online saving or uploading failures Anomalous program execution For example if a rung is being scanned false and there is an instruction that has false execution the fault handler executes so the remainder of the rung will scan true In the example below the OTE instruction has an index out of range After returning from the fault handler the ADD instruction will execute even though the rung input conditions are false Input_1 oaa Output index J EE ADD Add Source A value 0 Source B 1 Dest value oe Lgx00106481 Lgx00107423 Lgx00100766 Lgx00106478 Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 7 Table 3 Anomalies Corrected in Previous Firmware Revisions continued Firmware Revision 16 21 Anomaly Online edits result in maj
26. r 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 ControlFLASH Firmware Upgrade Kit Quick Start publication 1756 QS105 Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 15 Additional Memory Revision 16 00 or later may require more memory than previous revisions for example 10 x 11 x To estimate the additional memory that your project ma Requirements i aoe Ga pen egy Ca require use this table If you have this firmware Then add the following memory requirements to your project Which comes from this type of revision add all that memory apply Component Increase Per Instance 1 0 Data and Logic base expansion 16 x or earlier Tag that uses ALARM_ANALOG data type 16 bytes s with no associated tag references Tag that uses ALARM_DIGITAL data type 4 bytes v with no associated tag references Tag that uses the COORDINATE_SYSTEM datatype 132 bytes vA Tag that uses ALARM_ANALOG data type 22 bytes v if associated tags are configured for the 9 x the number of configured associated ALARM_ANALOG tag tags 3 x the su
27. ruction is being used in Linear mode this floating point equation is used to calculate the ITerm WldInput WidInput _ K ld p x Wld x z x DeltaT 1ITerm _ 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 Term 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 Lgx00070832 Changes made to a timeout in the alarms system require a new download of the program to controller The Slot Status bit for an 1 0 connection is slow to update if the connection is lost To verify that the timeout change is used by the controller you must download the program to the controller after each change to the timeout variable Lgx00069461 When using 1 0 on an Ethernet network if the connection to the network is lost at the adapter the SlotStatusBit for that connection will not register the disconnect for 9 seconds or more If you require loss of connection data more quickly than the 9 seconds use the GSV instruction to monitor the entry status of the connection as it updates more quickly than the SlotStatusBit Lgx00072697 Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 11 Table 4 Known Anomalies for Firmwar
28. s that use this attribute of the real time clock should not be impacted by this change However the time was also available in its 64 bit form by using the CurrentValue GSV attribute A GSV to CurrentValue of wall clock was changed to the number of microseconds from the new base date Any applications that interpreted the old 1972 64 bit number may now require a change Rockwell Automation Publication 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 5 Table 2 Enhancements Provided with Previous Firmware Revisions Firmware Enhancement Description Revision 16 03 EtherNet IP Reduced Heartbeat The Reduced Heartbeat feature reduces the rate at which heartbeat packets are sent from a device in an 1 0 connection or a Produced Consumed connection This feature preserves bandwidth in EtherNet IP network installations The change is automatic and requires no selection You will notice a reduction in the packets per second used on your EtherNet IP network for several cases including all input modules and Produce Consume tags IMPORTANT If you upgrade your Logix controller s firmware to revision 16 x you must also upgrade these adapters firmware revisions to 2 003 e 1734 AENT POINT I 0 EtherNet IP adapter e 1738 AENT ArmorPOINT 1 0 EtherNet IP adapter Failure to upgrade your EtherNet IP adapter firmware may impact your application if more than one Logix controller is connected to POINT 1 0 or
29. sion 6 x or earlier Base Tag 24 bytes vy Alias Tag 16 bytes us Produced or Data type Bytes per tag Consumed tag DINT 4 12 bytes vA REAL 4 12 bytes v 6 x Routine 68 bytes y 5 x or earlier Routine 116 bytes y 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 Add On Instructions CompactLogix Controllers Revision 15 Release Notes publication 1769 RNO15 Describes anomalies and enhancements related to controller revision 15 Logix5000 Process Control and Drives Instructions Reference Manual publication 1756 RM006 Contains information specific to the PI instruction ControlFlash Firmware Upgrade Kit Quick Start publication 1756 05105 POINT 1 0 EtherNet IP Adapter Release Notes publication 1734 RN002 Contains informations about firmware upgrades installation instructions and error messages Further describes the firmware upgrade to 2 003 ArmorPOINT 1 0 Release Notes publication 1738 RN002 Further describes the firmware upgrade to 2 003 You can view or download Rockwell Automation publications at http www rockwellautomation com literature To order paper copies of technical documentation contact your local Allen Bradley distributor or Rockwell Automation sales represe
30. tations workstations are connected to Lgx00070714 the controller Minor faults logged multiple The same minor faults typically a minor math overflow error may be logged more than once depending on the type of times when certain instructions used in the program For example if in a task the program contained a Multiply instruction that logged a instructions are used math overflow error as a minor fault a GSV instruction in the same program will log the same fault when it should not Instructions affected include Message BTR Message BTW GSV SSV UIE UID STOD STOR STOI PCMD PSC PATT PDET PCLF PPD and PRNP Lgx00028500 Lgx00045361 and Lgx00045365 LimitsInv and SelectLimitinv In the High Low Limit HLL instruction are swapped LimitsInv parameter is set when the SelectLimit is invalid SelectLimitInv parameter is set when the HighLimit and LowLimit parameters are invalid Lgx00055977 Processing of denormalized A denormalized number is any 32 bit floating point value that is less than 1 75494210 x 10 38 or greater than number exceptions causes a 1 75494210 x 10 8 excluding zero Denormalized numbers typically occur when very small real numbers are divided Major Non Recoverable Fault by very large real numbers This anomaly typically occurs when the following sequence takes place 1 The controller is handling an exception of a floating point denormalized number in task A 2 Then task B begins to execute and handles an exceptio
31. te and User defined Safe State features Rockwell Automation Publication 1769 RNO16F EN E February 2013 14 CompactLogix Controllers Revision 16 Hold Last State and User defined Safe State Not Supported Install the Controller Revision When 1769 Compact I O modules are used as local I O modules in a CompactLogix system the local I O modules do not support the Hold Last State or User defined Safe State features even though you can configure these options in the programming software Ifa local I O module fails such that its communication to the controller is lost or if any module is disconnected from the system bus while under power the controller will go into the fault mode All outputs turn off when the system bus or any module faults To install the latest CompactLogix controllers revision go to http www rockwellautomation com support to download your revision Then use the ControlFLASH utility 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 version 16 detects if your controller firmware needs upgraded upon a program download to the controller If a firmware upgrade is necessary AutoFlash will initiate an update After you have completed your firmware upgrade you should complete these steps to verify that the upgrade was successful 1 Cycle powe
32. tes y Bridge module with a comm format None 160 bytes y Bridge module with a comm format Rack 220 bytes y Optimization 11 x or earlier User defined data type 128 bytes v V 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 foran 60 bytes Vv array in an instruction such as an Array_A Tag_B This memory change applies only if the array e 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 10x or earlier Program 12 bytes y Routine 16 bytes y 9 x or earlier Tag that uses the MESSAGE data type 376 bytes y 7 x or earlier Project 1050 bytes v Tag 0 55 bytes 7 Message that transfers more than 500 bytes of data 2000 bytes v and targets a controller in the 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 1769 RNO16F EN E February 2013 CompactLogix Controllers Revision 16 17 If you have this firmware Then add the following memory requirements to your project Which comes from this type of revision add all that memory apply i Component Increase Per Instance 1 0 Data and Logic base expan
33. the controller does not complete the upgrade the MS status indicator continues flashing red In this case contact Rockwell Automation Services and Support Rockwell Automation Publication 1769 RNO16F EN E February 2013 4 CompactLogix Controllers Revision 16 i Enhancements Firmware Revision E 16 023 1769 L32E 1769 L35E This enhancement is provided with revision 16 023 Description Support for Series B controllers These enhancements have been made in previous firmware revisions Table 2 Enhancements Provided with Previous Firmware Revisions Firmware Revision 16 22 16 20 Enhancement False Execution Time of Add On Instructions Improved Radio Modem Protocol Support Description With previous revisions the false execution time of an Add On Instruction was dependent on the number of parameters input output and inout configured for the instruction The more parameters configured the longer the false execution time of the Add On Instruction With this revision the false execution time of an Add On Instruction is now constant if a scan false routine is not created To determine the false execution time of Add On Instructions based on your controller reference the values published in the Logix5000 Controllers Execution Time and Memory Use Reference Manual publication 1756 RM087 Lgx00106477 With this revision the DF1 Radio Modem protocol already supported by SLC 500 and MicroLogi
34. tion com rockwellautomation support overview page or contact your local Rockwell Automation representative New Product Satisfaction Return Rockwell Automation tests all of its products to help 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 local 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 RSLinx RSLogix RSNetWorx Logix5000 ControlFLASH ControlLogix FlexLogix DriveLogix GuardLogix POINT I O ArmorPOINT PanelView SLC MicroLogix FactoryTalk Compact I O and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Rockwell Otomasyon Ticaret A S Kar Plaza Ig Merkezi E Blok Kat 6 34752 erenk y stanbul Tel 90 216 5698400 www rockwell
35. tor terminal begins to initialize communication with the controller terminals utilizing the serial the controller responds with packets that exceed the 500 byte packet size The PanelView Plus operator terminal then port to communicate with the stops attempting communication with the controller When this occurs data is not updated on the PanelView Plus controller will not establish operator terminal communication at startup Lgx00074400 lie cae a T If an Add On Instruction is executed after a FFL or LFL instruction in a given program the internal registers are sare INS MUCHO NSN MS incorrectly written to and the result is a Major Non Recoverable Fault For the fault to occur all of the following must be same program as an Add On true The Add On Instruction an an instruction must be in the same program in a Logix application Instruction may cause the The Add On dFFLandLFLi bein th ina Lodi licati controller to experience a a Bes i ee Major Non Recoverable Fault If the application has two programs defined and the Add On Instruction is in program A and the FFL or LFL are in program B no anomaly will be seen e The FFL LFL instruction must load a scalar type SINT INT DINT or REAL If the source value is a structure no anomaly will be seen e The FFL LFL instruction must be scanned before the Add On Instruction If the Add On Instruction comes first in the code no anomaly will be seen The rung condition does not matter If the requ
36. ublication is indicated by a change bar as shown to the right of this paragraph In addition to information specific to the most recent firmware revision the information from previous minor revisions is retained in these release notes We strongly recommend that you review the information provided regarding previous firmware revisions We recommend that you do so because if you are upgrading your firmware through multiple previous revisions all of the information specific to all of the revisions is applicable Rockwell Allen Bradley Rockwell Software Automation 2 CompactLogix Controllers Revision 16 For example if you need to upgrade your controller from revision 16 03 16 023 all of the information specific to revisions 16 03 16 04 16 20 16 21 16 22 and 16 023 is applicable These release notes 1769 RNO16F are specific to firmware revision 16 023 for all CompactLogix controllers The previous revisions of this publication included the following controllers and firmware revisions The information from previous minor revisions is retained in these release notes Table 1 Previous Publications and Firmware Revisions Publication No 1769 RNO16E Cat No Major and Minor Revision No 1769 131 1769 L32C 1769 L32E 16 22 1769 L35CR 1769 L35E 1769 RNO16D 1769 131 1769 L32C 1769 L32E 16 21 1769 L35CR 1769 L35E 1769 RNO16C 1769 131 1769 L32C 1769 L32E 16 20 1769 L35 R 1769 L35
37. uption may occur in these conditions e Aone dimensional array tag that is based on a UDT is passed into the Add On Instruction The UDT tag contains a member that is a one dimensional array Inside the Add On Instruction an operand address that specifies an immediate member of the UDT tag array and a variable element of the member array for example array 0 memberArray x is used Examples UDT array 0 memberArray x When the size of the UDT array is smaller than that of the memberArray and the x value of the memberArray is larger than the size of the UDT array a Major Recoverable Fault Code 4 Type 20 occurs UDT array 0 memberArray x When the size of the UDT array is bigger than the memberArray and the x value is smaller than the size of the UDT Array but larger than the size of the memberArray the expected fault does not occur and the data is written to a location outside the bounds of the memberArray Lgx00077270 and Lgx00076136 An upload of an Add On Instructions with a literal boolean input parameter modifies offline image When an Add On Instruction containing a literal value for one of it s Boolean input parameters is referenced from a Ladder Diagram routine an upload of the project will modify the display of the literal value by appending a 0 Each time the project is downloaded and re uploaded another 0 is appended so that after the second download upload sequence the project file will n
38. ures Alarms are now embedded in the controller with two new instructions ALMD and ALMA available in RSLogix 5000 software These digital and analog alarm instructions are fully self contained 16 03 Ability to Unicast Producer Consumer Tags on EtherNet IP Networks Revision 16 enables you to use RSLogix 5000 software to set Producer and Consumer tag connections to Unicast Setting the tags to Unicast decreases the network bandwidth and simplifies Ethernet switch configuration Logix Date Base Changed to be January 1 1970 The Logix real time clock operates as a 64 bit binary number that counts microseconds from a fixed date Prior to revision 16 the base date was January 1 1972 Recent developments with the Common Industrial Protocol CIP specification have resulted in the selection of a different base date of January 1 1970 by the Open DeviceNet Vendors Association ODVA With revision 16 the date base that Logix products use has been changed to bring it into alignment with the CIP specification Additionally in support of the changes to the real time clock several other GSV attributes were also added LocalDateTime TimeZoneString ApplyDST daylight savings time and DSTAdjustment Generally the date and time were accessed via the GSV instruction within a Logix program by using the DateTime attribute which breaks down the date and time to its various components usec sec min hour day month year Application
39. x products has been implemented and enabled in the ControlLogix CompactLogix FlexLogix and DriveLogix controllers Legacy and Logix5000 controllers can be mixed and can support both master and slave and store and forward configurations 16 03 Add On Instructions With version 16 of RSLogix 5000 programming software you can design and configure sets of commonly used instructions to increase project consistency Similar to the built in instructions contained in Logix5000 controllers these instructions you create are called Add On Instructions Add On Instructions reuse common control algorithms With Add On Instructions you can e ease maintenance by animating logic for a single instance protect intellectual property with password protected instructions e reduce documentation development time For more information about using Add On Instructions see the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 Logix5000 Firmware Supervisor Use of the Logix5000 Firmware Supervisor with ControlLogix controllers and certain 1 0 modules enables you to program the controller to complete firmware updates by using a GSV or SSV instruction The controller uses a firmware kit loaded on a CompactFlash card and can complete firmware updates in Program and Run modes In GuardLogix controllers this enhancement is available for use with standard 1 0 modules FactoryTalk Alarms and Events Feat
40. zero although it should not be Lgx00081063 Use of revision 16 firmware and the controller serial port results in extended program scan times If you use firmware at revision 16 including revisions 16 03 6 21 and the controller s serial port the program scan time may increase The program scan time increase in revision 16 may be 2 10 times the scan time of the same program with revision 15 This anomaly only occurs when the controller serial port is used and there is no workaround Lgx00077845 Indirectly addressing an instance tag in an Add On Instruction results in a Major Non Recoverable Fault When an indirectly addressed instance tag is used instead of a directly addressed instance tag within an Add On Instruction a Major Non Recoverable Fault occurs Typically the major fault occurs during the prescan of the controller See the Restrictions section on page 12 for more information about this anomaly Lgx00077261 When the nonvolatile restore option is set to load On Corrupt Memory the program may not restore PI function block appears to stop executing as the output does not change and no instruction faults are logged This anomaly typically occurs with new controllers or controllers that register a Major Non Recoverable Fault If the nonvolatile restore option is set to load On Corrupt Memory and a corrupt memory condition is detected the controller program may not be restored Lgx00064843 If the PI inst
Download Pdf Manuals
Related Search