1756-RN017 - Rockwell Automation
Contents
1. 1756 ControlLogix Controllers Revision 17 3 IMPORTANT Firmware revisions 17 02 ControlLogix controllers and 17 06 GuardLogix controllers are no longer available for download from the Rockwell Automation Technical Support website due to an issue with the firmware revisions For more information about the issue see Technical Support Knowledgebase ID 62845 Firmware revisions 17 03 ControlLogix controllers and 17 07 GuardLogix controllers are available from the Technical Support website and include all of the enhancements and corrected anomalies provided with firmware revisions 17 02 and 17 06 in addition to those indicated for 17 03 and 17 07 as described in these release notes Compatible Versions of To use firmware revision 17 these minimum software versions are Software required Software Required Version RSLinx Classic 2 54 CPR 9 SR 1 RSLinx Enterprise 5 17 CPR 9 SR 1 RSLogix 5000 17 00 CPR 9 SR 1 RSNetWorx for ControlNet 9 00 CPR 9 SR 1 RSNetWorx for DeviceNet RSNetWorx for EtherNet IP Before You Begin Before you upgrade your firmware please consider the following IMPORTANT Loss of communication or power during a controller firmware flash 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 successf2. Publication 1756 RNO17C EN E February 2010 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 Corrected Anomalies with Previous Revisions 1756 ControlLogix Controllers Revision 17 17 Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Acknowledging an analog or digital If an alarm has an active status InAlarm tag is true and is 1756 L62 alarm does not clear the alarm s unacknowledged InAlarmUnack is true acknowledging the alarm 1756 L63 unacknowledged InAlarmUnack does not reset the alarm s unacknowledged tag that is even after 1756 L64 tag being acknowledged the InAlarmUnack continues to be true 1756 L61S 17 06 a 1756 L62S This anomalous behavior occurs with both digital ALMD and analog 1756 L63S ALMA alarms Lgx00081999 1756 L61 17 02 Writing 483 SINT values to another If you attempt to write 483 SINT values to another controller by using a 1756 L62 controll
3. SPCascade is set even when the setpoint 1756 L61S 17 06 SPCascade multiplied by the ratio value is below SP limits 1756 L62S 1756 1635 Lgx00065664 1756 L61 17 02 Setting the WALLCLOCKTIME Using an SSV instruction to set the local controller s WALLCLOCKTIME 1756 L62 object may result in a Major using the LocalDateTime attribute may result in an incorrect 1756 L63 Nonrecoverable Fault MNRF or an WALLCLOCKTIME value upon execution of the program This incorrect 1756 L64 incorrect WALLCLOCKTIME value time is usually evident in the seconds field 1756 L61S 17 06 1756 L62S The discrepancy in the WALLCLOCKTIME may also result in a MNRF 1756 L63S 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 1756 L61 17 02 Totalizer TOT instruction may Setting the ProgValueReset input puts the Totalizer into Program Mode 1756 L62 continually remain in Program The ProgOper output continues to indicate the mode requested that is 1756 L63 Mode Operator mode however only ProgStartReg ProgStopReq and 1756 L64 ProgResetReg are recognized 1756 L61S 17 06 1756 L62S Lgx00077908 1756 L63S Publication 1756 RNO17C EN E February 2010 Corrected Anomalies with Previous Revisions 1756 ControlLogix Con
4. 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 e has only one dimension such as UDT_1 5 10 x or earlier Program 12 bytes YA Routine 16 bytes y 9 x or earlier Tag that uses the MESSAGE data type 376 bytes Ya Publication 1756 RN017C EN E February 2010 1756 ControlLogix Controllers Revision 17 33 If you have this Then add the following memory requirements to your project Which comes from this firmware revision type of memory add all that apply Component Increase Decrease 1 0 Data and Logic Per Instance 7 X or earlier Project 1050 bytes M Tag 0 55 bytes Pa Message that transfers more than 500 bytes of data and 2000 bytes v 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 6 x or earlier Base tag 24 bytes Y Alias tag 16 bytes VA Produced or Data type Bytes per tag consumed tag DINT 4 12 bytes v REAL 4 12 bytes M 6 x Routine 68 bytes Y 5 X Or earlier Routine 116 bytes s Publication 1756 RN017C EN E February 2010 Additional Resources www rockwellautomation com These documents contain additional information concerning related Rockwell Automation p
5. February 2010 1756 ControlLogix Controllers Revision 17 9 Anomalies Corrected with Revisions 17 04 and 17 08 Cat No 1756 L55Mxx 1756 L61 1756 L62 1756 L63 and 1756 L64 Firmware Revision 17 04 1756 L615S 1756 L62S 1756 L63S 17 08 Description Online edits result in major non recoverable faults MNRFs Causes of this anomaly include e a controller that was or is near its limits in memory e doing many online edits tag additions and deletions without downloading again e 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 I O 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
6. e Motion Group e Digital Alarm e Analog Alarm e Message Lgx00086136 Lgx00085678 Attempting to use an SSV instruction to set the SerialPort class PendingComDriverlD attribute is unsuccessful Lgx00073954 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 PI function block appears to stop executing as the output does not change and no instruction faults are logged If the PI instruction is being used in Linear mode this floating point equation is used to calculate the ITerm WidInput WldInput _ Kp x Wld x 7 x DeltaT ITerm _ 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 1 For more information regarding the PI instruction see the Logix5000 Controllers Process Control and Drives Instructions User Manual publication 1756 RMO06 Lgx00070832 Changes made to a timeout in the alarms system require a new download of the program to controller 7C EN E February 2010 To verify that the timeout change is used by the controller
7. occurs when using firmware revision 16 20 or later 1756 L62 inaccurately cleared 1756 L63 If the ACL instruction is used to clear instructions from the ASCII 1756 L64 queue the serial port control structures RN bit is cleared that is the 1756 L61S 17 06 RN bit is set to zero although it should not be 1756 L62S 1756 L63S Lgx00081063 1756 L61 17 02 Use of revision 16 firmware and If you use firmware at revision 16 including revisions 16 02 16 21 1756 L62 the controller serial port results in and the controller s serial port the program scan time may increase 1756 L63 extended program scan times The program scan time increase in revision 16 may be 2 10 times the 1756 L64 scan time of the same program with revision 15 1756 L61S 17 06 i 1756 L62S With revision 17 program scan times have been reduced from 2 10 1756 L63S_ times to 1 5 6 times the scan time of the same program executed in revision 15 Lgx00077845 1756 L61 17 02 Indirectly addressing an instance When an indirectly addressed instance tag is used instead of a 1756 L62 tag in an Add On Instruction results directly addressed instance tag within an Add On Instruction a Major 1756 L63 ina Major Non Recoverable Fault Non Recoverable Fault occurs Typically the major fault occurs during 1756 L64 the prescan of the controller 1756 L61S 17 06 1756 L62S Lgx00077261 Lgx00076136 1756 L63S 1756 L61 17 02 Serial messages broadcast from a When two c
8. possible 1756 L64 combination 1756 L61S 17 06 Command Tolerance 1756 L62S Movel TT2 y 1756 L63S Move2 TT4 Move 1 blends 2 outside the command Move3 TTx tolerance radius Lgx00088549 1756 L615 17 06 Tag element names for safety When using the RSLinx tag browser function online the tag element 1756 L62S instructions in RSLinx Classic and names for GuardLogix safety application instructions such as ESTOP 1756 L63S RSLinx Enterprise software don t and ROUT are different from the tag element names RSLogix 5000 match RSLogix 5000 tag element software displays for the same tag names Lgx00072573 1756 L61S 17 06 Button and instruction faults occur If a dummy plug is used with a Two Handed Run Station THRS 1756 L62S with THRS dummy plug use instruction instruction and button faults occur 1756 L63S Publication 1756 RNO17C EN E February 2010 The GuardLogix controller has added an enhanced Two hand Run Station instruction THRSe in version 17 that should be used instead Refer to publication GuardLogix Safety Application Instruction Set Safety Reference Manual publication 1756 RM095 for more information about this enhanced instruction Lgx00076851 1756 ControlLogix Controllers Revision 17 23 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61S 17 06 GSV and SSV instructions unable to The Get System Value GSV and Set System Value S
9. 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 likelihood 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 e RSLinx Enterprise software version 5 00 CPR9 ID number 65818 e RSLinx Enterprise software version 5 17 CPR9 SR1 ID number 65819 e RSLinx Enterprise software version 5 20 CPR9 SR2 ID number 65820 Lgx00096513 Publication 1756 RNO17C EN E February 2010 10 1756 ControlLogix Controllers Revision 17 Anomalies Corrected with Revisions 17 04 and 17 08 Cat No 1756 L55Mxx 1756 L61 1756 L62 1756 L63 and 1756 L64 Firmware Revision 17 04 1756 L615S 1756 L62S 1756 L63S 17 08 Description 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 gon
10. unexpected 1756 L62 Non Recoverable Fault on combination of initial conditions when velocity 0 and acceleration lt gt 1756 L63 Controller 0 The only way to achieve this combination of initial conditions is to 1756 L64 stop the axis with an MAS instruction Speed 0 or an MCD 1756 L61S 17 06 instruction Speed 0 and to start the motion exactly one iteration 1756 L62S before the MAS instruction or MCD instruction is complete 1756 L63S Lgx00082075 1756 L61 17 02 An armed MAOC will remain armed If an MAOC instruction is armed when a system power cycle occurs 1756 L62 during a system power cycle the MAOC will remain armed at power up 1756 L63 1756 L64 The MAOC instruction may become disarmed if a physical axis fault is 1756 L61S 17 06 detected Additionally the MAOC instruction may cause a group 1756 L62S overlap fault if a physical axis reports a large delta position during 1756 L63S power up Lgx00085513 1756 L61 17 02 Execution time change for some With controller firmware revision 17 02 there is a change in the 1756 L62 motion instructions instruction execution times for numerous motion instructions 1756 L63 1756 L64 For more information on execution times see the Logix5000 Controllers 1756 L61S 17 06 Execution Time and Memory Use Reference Manual publication 1756 L62S 1756 RM087 1756 L63S Lgx00085687 1756 L61 17 02 Axis experiences unwanted motion You may experience unwanted motion if your application has
11. you must download the program to the controller after each change to the timeout variable Lgx00069461 1756 ControlLogix Controllers Revision 17 27 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No 1756 1756 1756 1756 1756 1756 1756 1756 L61 L62 L63 L64 L61S L62S L63S L63XT Anomaly Possible Velocity Spike When a MCCD Instruction is Executed Description Under certain application conditions you may see a velocity spike if you are using termination type 4 or 5 with coordinated moves and you execute an MMD instruction on the last iteration of a move For more information about this anomaly see the Technical Note titled Possible Velocity Spike When a Motion Coordinated Change Dynamics MCCD Instruction is Executed 53928 in the Technical Support Knowledgebase available at http www rockwellautomation com knowledgebase Lgx00088802 Setting the Read Write Buffer size parameter before enabling the Echo Mode does not result in a message echo In the User Protocol tab of the Controller Properties dialog box if the Read Write Buffer size is specified before Echo Mode is checked the message echo does not execute For the message echo to execute first check Echo Mode then specify the Read Write Buffer size Lgx00087052 Lgx00087176 Unsuccessful MSG execution results in subsequent unsuccessful messages in master slave controller configu
12. 095 Version 17 provides support for the Kinetix6000 SERCOS S1 Advanced Safety based family of drives The safety status can be directly accessed by the user s application via two new SERCOS Axis attributes GuardStatus and GuardFaults in the Axis_Servo_Drive data type The configuration of the S1 Drive s safety parameters is done via an Ethernet WEB based interface and downloaded to the Kinetix6000 drive via this Ethernet connection Version 17 provides support for the Kinetix6000 SERCOS SO Enhanced Safety based family of drives The safety status can be directly accessed by the user s application via a bit attribute SafeOff in the Axis_Servo_Drive data type Pause Management for Step Timer ACC The Logix5000 timers store a portion of the wall clock with each scan and compare this to the value from the last scan The timer s ACC value is updated by the difference Previous to version 17 when a Sequential Function Chart SFC routine was paused and then released all of the step timers jumped forward by the length of the pause time Version 17 now provides an option to control how the step timers will treat the pause ignore it or count the pause time Reading SFC Chart Paused State via GSV Instruction The paused state of a Sequential Function Chart can be determined programmatically using the Get System Variable GSV instruction Reading Safety Signature via GSV Instruction You can directly read the safety signature o
13. 17 06 1756 1625 Lgx00068281 1756 L63S Publication 1756 RNO17C EN E February 2010 14 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Duration Cam Latch and Unlatch Duration cams enable an application to turn an output on at a specific 1756 L62 Delays position and off after the configured Duration time Latch and unlatch 1756 L63 delays adjust the point at which an output turns on and off regardless 1756 L64 of axis speed 1756 L61S 17 06 nA LO 1756 L62S A positive latch delay time should extended your Duration time but 1756 L63S_ instead shortens it Additionally a positive unlatch delay time should shorten your Duration time but instead extends it The converse is also true A negative latch delay time should shorten your Duration time but instead extends it Additionally a negative unlatch delay time should extend your Duration time but instead shortens it If you execute a latch and unlatch delay for the identical value no anomaly occurs and the output remains on for the configured Duration time Lgx00068599 1756 L61 17 02 The Slot Status bit for an 1 0 When using 1 0 on an Ethernet network if the connection to the 1756 L62 connection is slow to update if the network is lost at the adapter the SlotStatusBit for that connection will 796 L63 connection is lost not register the dis
14. DRIVE 2 bytes x number of output cam execution targets Tag that uses COORDINATE_SYSTEM data type of 2 20 bytes v dimensions with 2 transform dimensions Tag that uses COORDINATE_SYSTEM data type of 3 108 bytes M dimensions with 3 transform dimensions Publication 1756 RN017C EN E February 2010 1756 ControlLogix Controllers Revision 17 31 If you have this Then add the following memory requirements to your project Which comes from this firmware revision type of memory add all that apply Component Increase Decrease 1 0 Data and Logic Per Instance 16 x or earlier Tag that uses ALARM_ANALOG data type 16 bytes v with no associated tag references Tag that uses ALARM_DIGITAL data type 4 bytes v with no associated tag references Tag that uses ALARM_ANALOG data type 22 bytes M if associated tags are configured for the ALARM_ANALOG tag 9 x the number of configured associated tags 3 x the sum 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 16 x or earlier Tag that uses the COORDINATE_SYSTEM data type 132 bytes v 15 x or earlier Input module 4 bytes M Produced tag 12 bytes v Consumed tag 4 bytes v Task 20 bytes VA Program or equipment phase 24 bytes Y Routine 4 b
15. Move Type Incremental 1756 L61S 17 06 or 1796 L62S e a Circle Type Center Incremental and any Move Type 1756 L63S Whether the occurred error was a function of the parameters of the circle and the merge point of the circle Lgx00079059 Publication 1756 RNO17C EN E February 2010 22 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 MCT not configured with a 1 to 1 You may experience a loss of position or an axis jump after coordinate 1756 L62 Ratio can cause loss of position or transform is activated via a MCT instruction The problem occurs if any 1756 L63 axis jump axes motion are programmed and the Coordination Units Conversion 1756 L64 Ratios of the Source and or Target Coordinate Systems and the axes 1756 L61S 17 06 contained therein are not configured with a 1 to 1 conversion ratio and 1756 L62S Coordinate Transforms are activated that is an MCT instruction has 1756 L63S_ been programmed The problem only occurred if the system had not been configured properly Lgx00078679 1756 L61 17 02 Combination of Termination Types You may have missed hitting the end point of a move with Termination 1756 L62 may cause you to miss the target Type 4 or 5 TT4 5 when it was preceded by another move with 1756 L63 position Termination Type 2 or 3 TT2 3 See figure below as one
16. OD instruction in revision 17 Lgx00102980 Use of an FFU instruction in an SFC program results in a major nonrecoverable fault MNRF Publication 1756 RNO17C EN E February 2010 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 1756 ControlLogix Controllers Revision 17 25 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No 1756 L61 1756 L62 1756 L63 1756 L64 1756 L61S 1756 L62S 1756 L63S 1756 L63XT Anomaly Partial import of a project developed and run ona SoftLogix controller causes fault Using an SFC Reset SFR to a step that is not the initial step cause the program to stay at the reset step Description Completing a partial import of a project developed and run on a SoftLogix controller causes a Major Nonrecoverable Fault if certain instructions are used in the program A Major Nonrecoverable Fault occurs on the controller when a program is developed and run on a SoftLogix controller and then a partial import online is completed to a Logix5000 controller while the Logix5000 controller is in Run mode online A Major Nonrecoverable Fault occurs if the imported project contains these instructions e Coordinated Control CC e Internal Model Control IMC e Modular Multivariable Control MMC The Major Nonrecoverable Fault occurs after the part
17. Release Notes 1756 ControlLogix Controllers Revision 17 ControlLogix Controller Catalog Numbers 1756 L61 1756 L62 1756 L63 1756 L64 1756 L65 ControlLogix XT Controller Catalog Number 1756 L63XT GuardLogix Controller Catalog Numbers 1756 L61S 1756 L62S 1756 L63S 1756 LSP Topic Page About This Publication 2 Compatible Versions of Software 3 Before You Begin 3 Enhancements 4 Corrected Anomalies 8 Known Anomalies 23 Restrictions 28 Additional Memory Requirements 30 Additional Resources 34 IMPORTANT Before updating your controller we strongly recommend that you review information pertinent to previous major firmware revisions For example when updating from revision 16 x to 17 x view information for revision 16 in the ControlLogix Controllers Revision 16 Release Notes publication 1756 RNO16 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 16 03 and not the last minor revision 16 21 you should view all of the information for revision 16 03 16 21 before updating to revision 17 x ControlLogix Controllers Revision 16 Release Notes publication 1756 RNO16 are available at http www rockwellautomation com literature Rockwell ALLEN BRADLEY e ROCKWELL SOFTWARE Automation 2 1756 ControlLogix Controllers Revision 17 About This Public
18. SV instructions 1756 L62S identify a safety task were unable to verify if an executing task was a safety task While this 1756 L63S inability did not hinder GSV and SSV functionality in safety applications the correction of this anomaly provides greater recognition of safety tasks and greater control over executable code Lgx00083100 Known Anomalies This table lists known anomalies of ControlLogix and GuardLogix controllers at all minor revisions of major revision 17 For more information about controller revisions and firmware revisions see the tables on page 2 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No Anomaly Description 1756 L61S Safety 1 0 configurations When the RSLogix 5000 software version 14 xx 16 xx or 17 xx is online with the 1756 L62S displayed may not be GuardLogix controller the Safety 1 0 module configurations displayed may not be those 1756 L63S those used by the used by the controller controller This issue is specific to the use of these 1 0 products e 1791DS All CIP Safety I O on the DeviceNet network e 1732DS All CIP Safety 1 0 on the DeviceNet network e 1791ES All CIP Safety 1 0 on EtherNet network e 1734 xxxS All POINT Guard CIP Safety 1 0 IMPORTANT You are not affected by this issue if these tasks are completed e Always perform a download after making offline edits e Make only online edits e Follow the Confirm the Project proc
19. ScanTime then a GSV instruction 1756 L63 is executed The average scan time jumps to an incorrect value The 1756 L64 larger the Coarse Update Period the larger the jump will be For 1756 L61S 17 06 example with a Coarse Update Period of 26 ms the average scan time 1756 L62S value can increase to over 300 ms 1756 L63S Lgx00071520 1756 L61 17 02 Axis ActualAcceleration tag is not For the virtual axis the Axis_tag ActualAcceleration does not update 1756 L62 updated for virtual axes but the Axis_tag CommandedAcceleration does The actual 1756 L63 acceleration is now updated for a virtual axis 1756 L64 1756 L61S 17 06 Lgx00073829 1756 L62S 1756 L63S 1756 L61 17 02 MCT error 61 with extended error You will get Error 61 with Extended Error 10 if you execute an MCT 1756 L62 10 for zero length moves instruction on the same interaction as the PC bit for a Motion 1756 L63 Coordinated Linear Move MCLM or Motion Coordinated Circular 1756 L64 Move MCCM is set for a zero length move indicating that axes are 1756 L61S 17 06 moving or locked by some other operation 1756 L62S 1756 L63S Lgx00075286 1756 L61 17 02 Setting invalid home sequence Attempting to program an SSV instruction to set the home sequence to 1756 L62 value via SSV instruction Torque or Torque Marker on a non SERCOS drive produced a minor 1756 L63 controller fault on any subsequent attempt to program this attribute via 1756 L64 an SSV instruction 1756 L61S
20. ailable with previous firmware revisions 17 02 ControlLogix controllers and 17 06 GuardLogix controllers Enhancements with Revisions 17 02 and 17 06 Enhancement Description Runtime Detection of Controller Online changes to programs and data in a 1756 L6x ControlLogix controller can be tracked Modifications via an internal log with change counters The log includes the type of change and the personal computer identity Windows login of the user who made the change The change log can be stored on the controller s CompactFlash card for offline review Changes may also be monitored programmatically by reading the change log counter using a Get System Variable GSV instruction Advanced Process Control Instructions Three new instructions targeted for process applications have been added The new instructions are e Internal Model Control IMC Compares actual process error against error calculated by an internal first order lag plus deadtime model e Coordinated Control CC Controls a single process variable by manipulating as many as three different control variables e Modular Multivariable Control MMC Controls two process variables to their setpoints using up to three control variables Instructions need to be purchased separately and licensed per use The catalog numbers and associated use types are 9324 RLDAPCENE provides a license to use the instructions in RSLogix 5000 and provides a license to use
21. an on the specified action 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 1756 ControlLogix Controllers Revision 17 15 Description 7 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 e The timer of the stored action will continue to time even though the action is no longer active e The logic in the stored action will be executed in the configured mode e At Automatic Reset non retentive outputs are cleared e 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 After a firmware upgrade attempt fails during the u
22. at is a one dimensional array e 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 1756 L61 17 02 An upload of an Add On Instruction When an Add On Instruction containing a literal value for one of its 1756 L62 with a literal Boolean input Boolean input parameters is referenced from a Ladder Diagram routine 1756 L63 parameter modifies offline image an upload of the project will modify the display of the literal value by 1756 L64 appending a 0 Each time the project is downloaded and 1756 L61S 17 06 re uploaded another 0 is appended so that after the second 1756 L62S download upload sequence the project file will not verify and can no 1756 163 longer be downloaded without first editing the modified literal value
23. ation Publication 1756 RNO17C EN E February 2010 This publication describes enhancements and anomalies known and corrected for ControlLogix controllers revision 17 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 For example if you need to upgrade your 1756 L61 controller from revision 16 07 to 17 04 all of the information specific to revisions 16 07 16 09 16 20 16 21 17 02 17 03 and 17 04 is applicable About Publication 1756 RN017 This revision of the firmware release notes 1756 RNO17C provides updated information specific to firmware revision 17 04 for all ControlLogix controllers The previous revisions of this publication and the associated firmware revisions are listed in this table Firmware Revisions Identified in Publication 1756 RN017 Pub Revision Catalog No Major and Minor Revision Nos 1756 RNO17A 1756 L61 1756 L62 1756 L63 17 02 1756 L64 1756 L65 1756 L61S 1756 L62S 17 06 1756 L63S 1756 LSP 1756 RNO17B 1756 L61 1756 L62 1756 L63 17 03 1756 L64 1756 L65 1756 L61S 1756 L62S 17 07 1756 L63S 1756 LSP 1756 RNO17C 1756 L61 1756 L62 1756 L63 17 04 1756 L64 1756 L65 1756 L61S 1756 L62S 17 08 1756 L63S 1756 LSP NVU
24. connect for 9 seconds or more 1756 L64 1756 L61S 17 06 If you require loss of connection data more quickly than the 9 seconds 1756 L62S use the GSV instruction to monitor the entry status of the connection 1756 L63S as it updates more quickly than the SlotStatusBit Lgx00072696 1756 L61 17 02 When the SFC instruction s Last A Major Non Recoverable Fault may occur when these elements are 1756 L62 Scan of Active Steps option is set present in the program 1756 L63 to Automatic Reset a Major 1756 L64 Non Recoverable Fault occurs e Within an SFC a JSR instruction is used to jump to another SFC 1756 161S 17 06 also know as a nested SFC 1756 L62S e One or more of the nested SFC instructions contains Simultaneous 1756 L63S Branches Publication 1756 RNO17C EN E February 2010 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 Corrected Anomalies with Previous Revisions Cat No 1756 L61 1756 L62 1756 L63 1756 L64 Firmware Revision 17 02 1756 L61S 1756 L62S 1756 L63S 1756 L61 1756 L62 1756 L63 1756 L64 17 06 17 02 1756 L61S 1756 L62S 1756 L63S 17 06 Anomaly An SFC R action continues to post sc
25. cted Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 03 Outputs remotely located via a When a controller changes from RUN mode to a non RUN mode state 1756 L62 network may not go to their that is to PROGRAM mode or a recoverable faulted state the 1756 L63 predefined PROGRAM mode state controller s outputs may not transition to their predefined PROGRAM 1756 L64 ona change out of RUN mode mode state 1756 L65 1756 L61S 17 07 Any of the following transitions from RUN mode to a non RUN mode 1756 L62S may cause this anomaly to occur 1756 L63S e The key switch on the controller is turned from RUN mode to PROGRAM mode e A remote command is sent to the controller to change from RUN mode to PROGRAM mode e The controller detects a major recoverable fault that causes an operating mode change from RUN mode to a faulted mode If your experience a major non recoverable fault on your controller the controller s outputs will transition to their predefined fault mode state Lgx00099405 1756 L61 17 03 The When using Produced Consumed tags with CONNECTION_STATUS 1756 L62 CONNECTION_STATUS RunMode the CONECTION_STATUS RunMode indication in the producing 1756 L63 indication in a Produced tag may controller may not indicate correctly if it is not in RUN mode The 1756 L64 not indicate correctly CONNECTION_STATUS RunMode indication in the Consuming 1756 L65 controller will i
26. e more memory see page 30 e 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 use a controller with a larger amount of memory 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 connected to a DH 485 network communication on the network may stop This enhancement is provided with firmware revisions 17 04 ControlLogix controllers and 17 08 GuardLogix controllers Enhancements with Revisions 17 04 and 17 08 Enhancement False Execution Time of Add On Instructions Improved Publication 1756 RNO17C EN E February 2010 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 Lgx00091647 1756 ControlLogix Controllers Revision 17 5 These enhancements were made av
27. e out of range MyTag i ndex where index is larger than the size of the array Faults can also be handled by the controller during 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 e The controller will experience a major non recoverable fault I O 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 e Tag data corruption e Online saving or uploading failures e 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 Output index ADD Add Source A value 0 Source B 1 Dest Lgx00106482 Lgx00100765 Lgx00097014 Publication 1756 RNO17C EN E February 2010 1756 ControlLogix Controllers Revision 17 11 This table lists anomalies corrected with previous revisions Corre
28. ecoverable Fault MNRF chassis as the GuardLogix controller a MNRF occurs Attempts to clear the Publication 1756 RNO17C EN E February 2010 major fault are unsuccessful and the controller loses its application program To avoid the MNRF we recommend not using a 1756 EN2T module as a CST master in GuardLogix controller applications However you can still use the 1756 EN2T modules in GuardLogix applications if it is not used as a CST master Lgx00079148 Lgx00080945 Install the Controller Revision 1756 ControlLogix Controllers Revision 17 29 To install the latest ControlLogix 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 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 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 If the controll
29. edure when commissioning the GuardLogix safety system as described in the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 In this confirmation procedure located in the Safety Application Development chapter you compare the online and original instance of your project For complete information about this anomaly see the Product Safety Advisory ID 62572 posted on the Rockwell Automation Knowledgebase available at http Awww rockwellautomation com knowledgebase Publication 1756 RNO17C EN E February 2010 24 1756 ControlLogix Controllers Revision 17 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No 1756 1756 1756 1756 1756 1756 1756 1756 L61 L62 L63 L64 L615 L62S L63S L63XT Anomaly Carry Status flag not set as expected Description 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 The Modular Multivariable Control MMC instruction may not use the second or third control variable CV The Modular Multivariable Control MMC instruction may not use the second or third control variable CV parameters to achieve the process variable PV setpoint when certain limits are specified for the CV In applications where the MMC function block is used to control one PV through manipulatio
30. er 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 Publication 1756 RNO17C EN E February 2010 30 1756 ControlLogix Controllers Revision 17 Additional Memory Requirements If you have this firmware revision add all that apply 17 x or earlier This firmware revision may require more memory than previous revisions for example 10 x 11 x To estimate the additional memory that your project may require use this table Then add the following memory requirements to your project Which comes from this type of memory Component Increase Decrease 1 0 Data and Logic Per Instance Task 4 bytes v Program 4 bytes v Equipment Phase 8 bytes v LD Routine 12 bytes v FBD Routine 8 bytes v SFC Routine 28 bytes M ST Routine 4 bytes v Add On Instruction 12 bytes M Produced Tag 4 bytes 4 bytes x W number of consumers Consumed Tag 8 bytes v Tag that uses MESSAGE data type 4 bytes M Tag that uses ALARM_ANALOG data type 64 bytes v Tag that uses ALARM_DIGITAL data type 28 bytes v Tag that uses AXIS_SERVO_DRIVE or 34 bytes v AXIS_GENERIC_DRIVE data type 2 bytes x number of output cam execution targets Tag that uses AXIS data type other than 52 bytes M AXIS_SERVO_DRIVE or AXIS_GENERIC_
31. er using a MSG instruction MSG instruction an error occurs This anomalous behavior does not 1756 L63 Causes an error occur with any other amount of SINT values for example attempting 1756 L64 to write 482 or 484 SINT values to the other local controller does not 1756 161S 17 06 cause this anomaly 1756 L62S 1756 1635 Lgx00057515 1756 L61 17 02 Message errors may occur when If you perform a CIP data table read or write message to another 1756 L62 using a CIP data table read or write controller with User defined Data Types UDTs the message 1756 L63 message instructions may error with code 16 001F extended error code 1756 L64 16 203 1756 L61S 17 06 1756 L62S Lgx00083193 1756 L63S 1756 L61 17 02 Attempts to rename Alias tags for If your HMI references any bit of a DINT and you try to rename Alias 1756 L62 bits within ina DINT referenced by tags for bits 0 7 within that DINT the new alias name fails to be set 1756 L63 an HMI are unsuccessful Attempting to rename Alias tags for bits 8 and higher is successful 1756 L64 1756 1618 17 06 Lgx00079805 1756 L62S 1756 L63S 1756 L61 17 02 Use of certain Function Block The use of these Function Block instructions may result in various 1756 L62 instructions causes various minor minor faults when your program executes 1756 L63 faults 1756 L64 BAND BOR BNOT BXOR CTUD D2SD D3SD DFF JKFF OSFI OSRI 1756 L62S 1756 L63S The minor faults result because the Ov
32. erflow status flag S V is set each time an instruction listed above is carried out Lgx00045364 Lgx00028500 Publication 1756 RNO17C EN E February 2010 18 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Nested SFCs when configured to Normally if in an SFC where the configuration of the last scan is set to 1756 L62 Automatic Reset are prescanned Automatic Rest the code of associated actions are executed a final 1756 L63 rather than postscanned time and the scan mode is set to postscan Postscan execution is a 1756 L64 system defined mode similar but not the same as prescan 1756 L61S 17 06 aaa ae 1756 1625 With this anomaly if an action in the SFC contains a JSR to another 1756 L63S_ SFC the suburoutine is prescanned rather than postscanned that is the incorrect scan mode is set Many instructions especially motion instructions remain inactive during a postscan but re initialize during a prescan Lgx00086725 1756 L61 17 02 The SPCascadelnv value of a PIDE When the AllowCasRat and UseRatio tags are set the SPCascadelnv 1756 L62 instruction is set any time should be set only if SPCascade multiplied by the ratio value exceeds 1756 L63 SPCascade exceeds the SP limits the SP limits However the SPCascadelnv is set any time SPCascade 1756 L64 exceeds the SP limits
33. f a GuardLogix controller using the Get System Variable GSV instruction Produced Consumed Tag Structures Status Firmware support for 1756 L65 and 1756 L63S controllers Status information can be included with produced and consumed tags In order to take advantage of this enhancement the Produced Consumed tag will need to be a User Defined Type UDT with the first member being of data type CONNECTION_STATUS Note that RSNetWorx software version 9 00 00 or later is required when scheduling a ControlNet network that has Produced Consumed tags with status This firmware revision supports two new controllers the ControlLogix 1756 L65 and the GuardLogix 1756 L63S controllers For more information about the capabilities of these controllers see ControlLogix Controllers Selection Guide publication 1756 SG001 Added Extended Error Codes for MAOC Cam amp Compensation array errors Publication 1756 RNO17C EN E February 2010 For Error Codes 36 and 37 new Extended Error Codes are available for Output Cam array and Output Compensation array errors The Extended Error Codes describe errors that may occur because the element is incorrectly configured or the value of one of its members is out of range 1756 ControlLogix Controllers Revision 17 7 Enhancements with Revisions 17 02 and 17 06 Enhancement Description Support of Programmable Jerk for Support for programmable jerk has been extended to the multi axis move instruc
34. ial import is completed and the edits to the program are finalized Lgx00103562 When an SFC Reset SFR instruction that is executed specifies a target step that is not the initial step and the step is anywhere below but outside a simultaneous branch the chart will no longer execute The chart will remain in the step it was reset to and attempts to progress via a Transition Force or Step Through are unsuccessful To begin executing the chart again you must execute an SFR instruction to the initial step or to a step above the first simultaneous branch Lgx00099805 Interrupted service communication during a connection closure causes a fault Depending on the structure of your program if your service communication is interrupted for longer than 300 ms as determined by the System Overhead Time Slice setting and a connection is in the process of closing a major nonrecoverable fault MNRF may result The connection that is closing could be a connection used for I O a message instruction a forward open and so on Lgx00101330 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 instr
35. n of up to three CVs only the first CV is manipulated by the instruction if the CVxEUMax CVEUMin CVxHLimit and CVxLLimit input parameters for the first CV are set at conflicting values These input parameters conflict when the CVxHLimit or CVxLLimit keeps the CV clamped at a value inside the range specified with the CVxEUMax and CVxEUMin parameters If the CV does not extend outside the CVxEUMax and CVxEUMin parameters the second and third CVs of the MMC instruction are not used to manipulate the PV Lgx00091924 Using an SSV instruction to set the WallClockTime causes a fault Use of a FIND instruction results in a major recoverable fault MRF Setting the WallClockTime to an invalid value by using an SSV instruction results in a Major Nonrecoverable Fault MNRF Lgx00097399 Attempts to use the FIND instruction 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 Use of STOD instruction when upgrading from revision 16 cause a scan time increase Use of an STOD instruction and a program upgrade from revision 16 to revision 17 results in the program scan time increasing When an STOD is used in an application that has been upgraded from revision 16 to revision 17 the program scan time dramatically increases due to an anomaly correction made to the ST
36. ndicate correctly 1756 L61S 17 07 1756 L63S 1756 L61 17 02 Setting the message timeout bit Setting a message timeout bit TO in the message control structure 1756 L62 TO causes a major while the message is active may result in a MNRF on the controller 1756 L63 nonrecoverable fault MNRF 1756 L64 To avoid causing a MNRF do not change the message timeout bit T0 1756 L61S 17 06 Instead change the values for the unconnected timeout 1756 L62S UnconnectedTimeout and connection rate ConnectionRate in the 1756 L63S_ message control structure For more information about changing the values in the message control structure see the Logix5000 Controllers General Instruction Reference Manual publication 1756 RM003 Lgx00098991 Publication 1756 RNO17C EN E February 2010 12 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Firmware upgrades using the If you have stored your program on a CompactFlash card then remove 1756 L62 ControlFlash utility are the CompactFlash card while power is off without replacing it 1756 L63 unsuccessful if the CompactFlash attempts to upgrade the controller firmware are unsuccessful 1756 L64 card is removed Re inserting the CompactFlash card restores the ability to upgrade firmware Lgx00073863 1756 L61 17 02 Serial port control structure bit RN This anomaly
37. of whether feedback is on or off Lgx00076298 Publication 1756 RNO17C EN E February 2010 28 1756 ControlLogix Controllers Revision 17 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No Anomaly Description 1756 L61 Axis Stopping Status bit If you execute a MAS of Type ALL on motion that started with an MCLM instruction the 1756 L62 is incorrect for MAS AIl Axis StoppingStatus bit briefly transitions to true but then transitions back to false and 1756 L63 Instruction with remains in that state until the axis comes to a complete stop 1756 L64 Coordinated Motion 1756 L61S Lgx00085033 1796 L62S Multiple Absolute MAM Overshoot may occur with MAM instruction with Merge Enabled if there is not enough 1796 L63S Instructions with S curve distance until the end of the move for the programmed dynamic jerk parameters that is 796 L63XT and Merge Enabled can decel jerk and axis decel in the merged move overshoot target position Overshoot may be avoided by increasing the decel jerk or not using the merge Lgx00078822 Restrictions These restrictions apply to the use of ControlLogix controllers at all Restrictions for Firmware Revision 17 Cat No 1756 1756 1756 L61S L62S L63S Restriction minor revisions of major firmware revision 17 Description Use of two CST masters causes a Major If two CST masters for example two 1756 EN2T modules are in the same Nonr
38. on com literature To order paper copies of technical documentation contact your local Rockwell Automation distributor or sales representative Tech Notes and other resources are available at the Technical Support Knowledgebase http www rockwellautomation com knowledgebase Allen Bradley Rockwell Automation RSLinx Classic RSLinx Enterprise RSNetWorx for ControlNet RSNetWorx for DeviceNet RSNetWorx for EtherNet IP SoftLogix and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies 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 Vorstlaan Boulevard du Souverain 36 1170 Brussels 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 RNO17C EN E February 2010 Supersedes Publication 1756 RN0O17B EN E July 2009 PN 66516 Copyright 2010 Rockwell Automation Inc All rights reserved Printed in the U S A
39. ontrollers are used in a master slave configuration and the 1756 L62 master controller to station address message to the broadcast station address 255 is executed that 1756 L63 255 results in other messages message errors Some messages occurring after the message 1756 L64 failing addressed to address 255 also error with the same error code 1756 L61S 17 06 1756 L62S Lgx00079116 1756 L63S Publication 1756 RNO17C EN E February 2010 Corrected Anomalies with Previous Revisions 1756 ControlLogix Controllers Revision 17 13 Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Motion Redefine Position MRP You may get the error Parameter out of Range if the MRP is executed 1756 L62 Error 13 for Positions within the when 1756 L63 range 1756 L64 Current Position MRP Position gt 231 Axis Conversion Constant 1756 L61S 17 06 Or 1756 L62S Current Position MRP Position lt 231 Axis Conversion Constant 1756 L63S For example assume that the e axis conversion constant 120 000 0 feedback counts 1 0 unit e current command position 17 893 0 units If you MRP with a position of five units which exceeds 231 Axis Conversion Constant the MRP will error Lgx00073719 1756 L61 17 02 SSV of MotionGroup Average Scan If an SSV instruction with a value of zero is executed against the 1756 L62 Time causes a jump in scan time MotionGroup attribute TaskAverage
40. pgrade 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 unsuccesstul 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 Publication 1756 RNO17C EN E February 2010 16 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Passing a User defined Data Type An anomaly occurs when you pass a tag based on a User defined Data 1756 L62 UDT into an Add On Instruction Type UDT into an Add On Instruction and certain conditions are met 1756 L63 results in a Major Recoverable that result in a Major Recoverable Fault or memory corruption 1756 L64 Fault or data memory corruption 1756 L61S 17 06 These conditions are required for Major Recoverable Fault or data 1756 L62S memory corruption 1756 L63S i e A one dimensional array tag that is based on a UDT that is passed into the Add On Instruction e The UDT tag contains a member th
41. rations RMPS instruction in a continuous task does not countdown When a DF 1 serial connection is used between a master and slave controller a MSG instruction is not successfully executed and an in polling sequence error occurs if the master station address is not listed in the poll node list However with this anomaly after the in polling sequence error subsequent MSG instructions are also unsuccessful To workaround this anomaly change the master controller s station address to a different value or re execute the unsuccessful MSG instruction in Master Transmit mode and use the Between Station Polls parameter Lgx00083882 If a RMPS instruction is used in a continuous task and a Soak Time value greater than 1024 minutes is specified the countdown SoakTimeLeft does not countdown and the RMPS instruction appears to stop executing This anomaly does not occur if the RMPS is used in a periodic task or the continuous task program is run in SoftLogix 5800 or Emulator 5000 software To workaround this anomaly either e Use multiple soaks to achieve your total soak times greater than 1024 minutes e Use the RMPS in periodic task that has a Period on 10 ms or greater Lgx00085036 Lgx00083654 If you issue an Absolute Feedback Offset it results in a Feedback Fault 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
42. roducts Resource Logix5000 Controllers Common Procedures Reference Manual publication 1756 PMO001 Description Contains information specific to the use of Add On Instructions and other procedures related to programming your controller ControlLogix Controllers Revision 16 Release Notes publication 1756 RNO16 Describes anomalies and enhancements related to controller revision 16 Motion Planner Version 16 03 Application Solution publication RA AP031 Describes Motion Planner enhancements made with RSLogix 5000 software version 16 03 ControlLogix Combination Controller and SERCOS Interface Card Revision 17 Release Notes publication 1756 RN655 Describes anomalies and enhancements specific to the 1756 L60MO03SE Combination Controller and Sercos Interface Module Logix5000 Controllers Process Control and Drives Instructions Reference Manual publication 1756 RMO006 Contains information specific to the PI instruction ControlFlash Firmware Upgrade Kit Quick Start publication 1756 05105 Contains informations about firmware upgrades installation instructions and error messages Possible Velocity Spike When a Motion Coordinated Change Dynamics MCCD Instruction is Executed ID 53928 Further describes the Velocity Spike anomaly described in the Restrictions section of these release notes You can view or download Rockwell Automation publications at http www rockwellautomati
43. sions 17 04 ControlLogix controllers and 17 08 GuardLogix controllers Anomalies Corrected with Revisions 17 04 and 17 08 Cat No 1756 L55Mxx 1756 L61 1756 L62 1756 L63 and 1756 L64 1756 L61S 1756 L62S 1756 L63S Firmware Revision 17 04 17 08 Description A Digital Alarm ALMD configured to trigger when the input condition of the alarm is false does not trigger if the alarm condition is false when you conduct a download or return to Run mode 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 e Programming designed to respond to the activated alarm is not executed e Messages designed to be indicated at the operator station in response to the activated alarm are not indicated e 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 your Condition parameter is set then the alarm activates as expected after you download or change the controller mode Lgx000104435 Publication 1756 RNO17C EN E
44. stead continues moving to the programmed end point in the direction of the MAM instruction You may also experience similar issue for a non merged move if a MAM Instruction with Move Type Rotary Positive or Rotary Negative is followed by a MAM instruction with a rotary move in the opposite direction while the move is in progress The axis doesn t reverse the direction but instead continues moving to the programmed end point in the direction of the first MAM Lgx00080848 Lgx00081561 1756 L61 17 02 An MCD Instruction on Rotary Your controller occasionally experiences a non recoverable fault if the 1756 L62 Unidirectional moves with reduced following sequence of events occurs 1756 L63 deceleration may cause a 1756 L64 Non Recoverable Fault e A rotary axis is programmed to move in either a positive or negative 1756 L61S 17 06 only mode in an MAM instruction 1756 L62S e The rotary axis is currently decelerating 1756 L63S e An MCD instruction is issued to stop such an axis by a programmed speed of 0 A slight overshoot may result when the axis finally comes to a stop When this axis is restarted again by another MCD the non recoverable fault may occur Lgx00080762 1756 L61 17 02 An Incremental MCCM Move with Your controller occasionally sees a Circular R1 R2 Mismatch error on a 1756 L62 Merge Enabled May Cause merge of a MCCM instruction with 1756 L63 Error 46 Circular R1 R2 Mismatch 1756 L64 Error e Circle Type Center and
45. the 1756 L62 on rotary axis following conditions 1756 L63 1756 L64 e The axis is a rotary axis 1756 L61S 17 06 e The axis position was less than 1 2 drive count away from unwind 1796 L62S e An MPP instruction was executed with a commanded position of 1756 L63S zs Lgx00078215 1756 L61 17 02 Base Offset X1b with a negative For a 2 amp 3 axes Delta robot you can now use both negative and 1756 L62 value in Delta gives MCT Error 61 positive values for the X1 Base Offset 1756 L63 Exerr 15 1756 L64 For both of these 2 Delta robot geometries an error is now forced if 1756 L61S 17 06 1756 L62S L1 X1b x1e gt L2 1756 L63S Publication 1756 RN017C EN E February 2010 Lgx00083890 Corrected Anomalies with Previous Revisions 1756 ControlLogix Controllers Revision 17 21 Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Axis may move in opposite An axis may move in the opposite direction specified in a MAM 1756 L62 direction for Rotary Positive or instruction if the following events occur at the same time 1756 L63 Rotary Negative moves 1756 L64 e The servo loop for an axis is closed by an MSO instruction 1756 L61S 17 06 and 1796 L62S e A MAM instruction with a Move Type of Rotary Positive or Rotary 756 L63S Negative is configured with Merge Enabled and is executed in the same iteration as the MSO instruction The axis doesn t reverse the direction but in
46. them in a single Logix controller 9324 RLDAPCCLENE provides a license to use the instructions in an additional controller pay to deploy Runtime Partial Import You can now import programs equipment phases routines rungs and new Add On Instructions into a running system You can add these new components as well as replace existing programs equipment phases and routines while the system is running New tags and User Defined Types will be created as needed with values initialized from the import file Data values of existing tags will be maintained Publication 1756 RNO17C EN E February 2010 6 1756 ControlLogix Controllers Revision 17 Enhancements with Revisions 17 02 and 17 06 Enhancement Added GuardLogix Safety Instructions Kinetix6000 Advanced Safety Drive S1 Support Kinetix6000 Enhanced Safe Torque off Drive SO Support Description Several new safety instructions are available with the use of RSLogix 5000 software version 17 and GuardLogix controller firmware revision 17 New instructions include e Nine Metal Forming Instructions e Three Muting Instructions for Light Curtains e Six Dual Channel Instructions e A Safety Mat Instruction e A Configurable Redundant Output Instruction e A Two Hand Run Station Enhanced Instruction For more information about these and other safety instructions see the GuardLogix Safety Application Instruction Set Safety Reference Manual publication 1756 RMO
47. tions that Multi Axis Coordinated Move Instructions is MCCM MCLM MCCD and MCS You are now able to specify acceleration and deceleration jerk rates for the multi axis coordinated moves directly via operands in the instruction faceplate for S Curve profile motion for these instructions The configurable maximum jerk rates are also accessible programmatically via the Get System Variable GSV and the Set System Variable SSV instructions For project conversions the new Jerk Operands are pre populated in the MCLM MCCM MCCD and MCS instructions with default values for Jerk rate as 100 of time Support for Programmable Jerk for The MCD instruction is used to Change the Speed Acceleration and Deceleration of a Single Axis Change Dynamics Instruction running Single Axis Motion MCD Now with the Programmable Jerk you can specify the Accel and Decel Jerk for S Curve Profiles Added ability to apply change dynamics to A new enumeration that is Active and Pending Motion has been added to the Scope Active and Pending Motion variable of the MCCD instruction Choosing Active and Pending Motion specifies that the changes affect the motion dynamics of the active coordinated motion instruction and any pending coordinated motion instruction in the queue Publication 1756 RNO17C EN E February 2010 8 1756 ControlLogix Controllers Revision 17 Corrected Anomalies These anomalies have been corrected in controller firmware revi
48. troller experiences this issue 1756 L64 only if the Program Stop Action configured in the axis properties is set 1756 L61S 17 06 to Hard Disable 1756 L62S PESES N 1756 L63S With the corrected behavior in this release the transition to the program mode is immediate Lgx00077357 1756 L61 17 02 Prevent execution of Motion Previously if certain Motion Instructions overlapped while Motion Stop 1756 L62 Instructions while an MGS Instructions were active your application experiences unexpected 1756 L63 MAS ALL or MCS AII instruction is behavior When an instruction is actively stopping and a second 1756 L64 executing instruction is initiated that overlaps the active instruction you see this 1756 L61S 17 06 mmama 1756 L62S ee l 1756 L63S With firmware revision 17 02 if certain Motion Instructions overlapped while Motion Stop Instructions are active you see Error Code 78 For more information about Error Code 78 and the affected Motion Instructions see the Error Codes for Motion Instructions Appendix of the Logix5000 Controllers Motion Instructions Reference Manual publication 1756 RM007 Lgx00083819 Publication 1756 RN017C EN E February 2010 20 1756 ControlLogix Controllers Revision 17 Corrected Anomalies with Previous Revisions Cat No Firmware Anomaly Description Revision 1756 L61 17 02 Parameter Combination Caused A non recoverable fault is caused by a very unlikely and
49. trollers Revision 17 19 Cat No Firmware Anomaly Description Revision 1756 L61 17 02 An MAOC in conjunction with an An MAOC instruction used in conjunction with an 1756 0B16IS 1756 L62 1756 OB16IS Scheduled Output Scheduled Output Module can overwrite memory if 1756 OB16IS 1756 L63 Module can overwrite memory module is not configured with the default communications format 1756 L64 Scheduled Output Data per Point If the format is changed to either 1756 L61S 17 06 Listen Only Output Data or Output Data the memory allocated 1756 L62S for the schedule data used by the MAOC instruction is not present 1756 L63S Lgx00082622 1756 L61 17 02 Jerk parameters of master offset The Master Offset Moves are used to offset the Position cams 1756 L62 move are incorrectly computed 1756 L63 The Jerk parameters of the Master offset Move using a MAM 1756 L64 instruction are incorrectly applied if the conversion constant of the 1756 L61S 17 06 master and the slave are different The slave axis conversion constant 1756 L62S is applied instead of the master axis conversion constant for master p 756 163S offset move Lgx00081390 1756 L61 17 02 Motion Stop issues if Program Stop If MCLM or MCCM instructions are in process and the controller 1756 L62 Action is Hard disable for a transitions to Program Mode the system s transition takes longer than 1756 L63 Virtual Axis expected for the axes to stop Your con
50. uction 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 Publication 1756 RNO17C EN E February 2010 26 1756 ControlLogix Controllers Revision 17 Known Anomalies with All Minor Revisions of Major Revision 17 Cat No 1756 L61 1756 L62 1756 L63 1756 L64 1756 L61S 1756 L62S 1756 L63S 1756 L63XT Publication 1756 RNO1 Anomaly Deleting program tags while online is successful even though they are being referenced by RSLinx software and should not be deleted SSV class name SerialPort attribute PendingComDriverlD does not set Using an SSV instruction to set a task priority of 0 results in unexpected execution times Description RSLogix 5000 software and Logix5000 controller firmware provide the ability to delete program tags while online with the controller As a precaution the software checks the tag to verify that is not in use that is the tag is not being scanned or referenced by RSLinx Classic or Enterprise software If the tag is being used by RSLinx software the deletion is not allowed and an error dialog box indicates Failed to delete tag However with certain tags the deletion is always allowed even if the tag is being used by RSLinx software Tag types that are always deleted even if being used by RSLinx software include e Motion Axis
51. ully complete the flash upgrade e f anonrecoverable fault occurs then return the controller for factory repair Publication 1756 RNO17C EN E February 2010 4 1756 ControlLogix Controllers Revision 17 lf Your controller is at revision 11 firmware or earlier The following preliminary actions are required before upgrading your controller firmware Then You must first upgrade to revision 12 or 13 before attempting to upgrade to revision 17 x Once you have your controller upgraded to revision 12 or 13 then you can upgrade the controller to revision 17 x Your controller meets both of these conditions e t has nonvolatile memory e t is currently at revision 11 x or earlier Remove the CompactFlash card from the controller or check the Load Image option of the CompactFlash card If it is set to On Power Up or On Corrupt Memory first store the project with the Load Image option set to User Initiated Otherwise you may get a major fault when you update the firmware of the controller This occurs because the On Power Up or On Corrupt Memory options cause the controller to load the project from nonvolatile memory The firmware mismatch after the load then causes a major fault Your controller is close to its limits of memory Your controller is connected to a DH 485 network Enhancements This revision may require more memory than previous revisions e To see what components of your current project requir
52. ytes VA Tag that uses COORDINATE_SYSTEM data type 748 bytes v Tag the uses any AXIS data type 800 bytes Z Serial port 1120 bytes VA Project 4012 bytes vA Publication 1756 RN017C EN E February 2010 32 1756 ControlLogix Controllers Revision 17 If you have this Then add the following memory requirements to your project Which comes from this firmware revision type of memory add all that apply Component Increase Decrease 1 0 Data and Logic Per Instance 14 x or earlier Tag that uses the COORDINATE SYSTEM data type 60 bytes vA Tag that uses any AXIS data type 4 bytes WA 13 x or earlier Program 12 bytes Y Task 4 bytes Y4 User defined data type 4 bytes WA 1 0 module 16 bytes VA VA 8 bytes 8 bytes Produced or consumed tag 8 bytes v 12 x or earlier 1 0 module with a comm format Rack Optimization 90 bytes VA 1 0 module with a comm format something other than 144 bytes Sf Rack Optimization such as a direct connection CompactLogix 1769 1 0 module 170 bytes VA Bridge module with a comm format None 160 bytes Sf Bridge module with a comm format Rack Optimization 220 bytes v 11 x or earlier User defined data type 128 bytes VA e Number of user defined data types in the controller organizer gt Data Types folder gt User Defined folder e Not the use of that data type in tags Indirect address using a tag as the subscript for an array 60 bytes vA
Download Pdf Manuals
Related Search