Release Notes

CompactLogix L32E controller
Version 17.012 (released 3/2013)

Catalog Number 1769-L32E (series A)

These release notes describe version information for 1769-L32E, version 17.012 (released 3/2013).

Security

This release includes security enhancements as a part of our ongoing efforts to improve security. For information regarding Rockwell Automation's vulnerability disclosure process, please reference the Rockwell Automation Vulnerability Policy.

Access Denied dialog box does not appear when users without FactoryTalk Security access attempt to modify Motion Configuration (Lgx00184951)

Studio 5000 Logix Designer v29.00

Corrected Anomaly with Studio Logix Designer v30.00

When a user without Motion: Modify Configuration security credentials attempts to modify the motion configuration, an Access Denied dialog box does not appear.

Requirements

This release has the following requirements.

Firmware Requirements – 1769 CompactLogix Controllers

Catalog Numbers 1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E

Consider the following before upgrading the firmware on your 1769 CompactLogix controller:

Consideration
Description
Avoid Interrupting the Firmware Upgrade
 
 When upgrading your controller firmware, it is extremely important to allow the upgrade to complete without interruption.
If you interrupt the firmware upgrade either in the software or by disturbing the physical media, you may render the controller inoperable.
During an upgrade of the CompactLogix firmware, the ControlFLASH™ utility displays various progress dialog boxes. The progress dialog boxes contain these status statements:
  • Transmitting block…
  • Polling for power-up…
It is crucial that you do not interrupt the firmware upgrade while these progress statements are displayed. Once the Update Status dialog box indicates that the firmware upgrade is complete, you may adjust your controller’s network connection, make changes using controller-related software, or cycle controller power.
End Cap Needed for Firmware Upgrade
 Attempting a firmware upgrade without the controller end cap attached does not complete.
When upgrading your controller firmware, verify that your end cap is properly attached and locked. If you attempt to upgrade without the end cap attached, your firmware upgrade may not complete successfully.

 

Controller Memory Limits
If your controller is close to its memory limit and this firmware revision requires more project memory, you can upgrade to a controller that has more memory.
Avoid Loss of Communication During Firmware Upgrade
 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 those conditions described, the following corrective actions may be required.
  • Cycle controller power with the battery disconnected for 2…3 minutes, then successfully complete the flash upgrade.
  • If a nonrecoverable fault occurs, contact Rockwell Automation Technical Support for a ticket number and return the controller for factory repair.
Disconnect Controller from DH-485 Network Before Firmware Upgrade
If your controller is connected to a DH-485 network, 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.
Firmware Upgrade on 1769-L32E or 1769-L35E Controller
IMPORTANT: This consideration applies only to 1769-L32E and 1769-L35E controllers.
 We recommend that you complete the following tasks before attempting a firmware upgrade on a 1769-L32E or 1769-L35E:
  1. 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, additional action may be required. Contact Rockwell Automation Technical Support for more information.
  2. Modify the Port Configuration for the Ethernet card so that the Network Configuration Type is set to Static and assign a valid IP address.
  3. If RSWho is actively browsing the controller through an Ethernet or serial connection, close the RSWho window to stop the browse.
  4. If other controllers are messaging to the 1769-L32E or 1769-L35E controller, take the other controllers off the network or put them in Program mode.
  5. If there are controllers consuming tags from the 1769-L32E or 1769-L35E controller, remove them from the network.
  6. If there 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 dialog boxes 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 the controller does not complete the upgrade, the MS status indicator continues flashing red. In this case, contact Rockwell Automation Services and Support.
Use of ControlFLASH software, Version 9 (CPR9 SR3) with Firmware Revision 19
IMPORTANT: This consideration applies only when you are using firmware revision 19.
 Consider the following before you install the ControlFLASH software, version 9:
  • We recommend you install RSLinx communication software, version 2.057, before you install ControlFLASH software, version 9 (CPR9 SR3).
  • If you install RSLinx communication software, version 2.057, before you install ControlFLASH software, version 9, you can enable or disable the FactoryTalk Security platform during ControlFLASH software, version 9, installation. However, to disable the FactoryTalk Security platform, you must first uninstall ControlFLASH software, version 9, then reinstall it.
  • If the FactoryTalk Security platform is enabled during ControlFLASH software, version 9, installation, the software opens with a Select FactoryTalk Directory dialog box. At that dialog box, click the following:
    • Network
    • Local
    • Cancel - If you click Cancel, you must select a directory.
  • ControlFLASH software, version 9, only integrates the FactoryTalk Security platform in the FactoryTalk Services Platform, version 2.030 or later.

 

 

Corrected Anomalies in This Release

This release corrects the following anomalies.

Carry Status Flag Not Set as Expected (Lgx00105710, Lgx00074175)

Corrected as of:

Known Anomaly First Identified as of:

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.


Known Anomalies from Previous Releases

These anomalies are from previous releases but are still known in this release.

FFU Instruction (Lgx00096621, Lgx00105710)

Corrected as of:

Known Anomaly First Identified as of:

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.

With firmware revision 18.011, this anomaly has been corrected.

FIND Instruction Use Results in Fault (Lgx00094007, Lgx00101633)

Corrected as of:

Known Anomaly First Identified as of:

Use of a FIND instruction results in a major recoverable fault (MRF).

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.

With firmware revision 18.011, the FIND instruction can successfully search a source-data string as large as 65,535 characters, the largest number of characters that can be used in a string.

Setting Task Priority via SSV Instruction Causes Unexpected Execution Times

Corrected as of:

Known Anomaly First Identified as of:

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. 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.


PI Function Block Appears to Stop Executing

Known Anomaly First Identified as of:

The PI Function block appears to stop executing as the output does not change and instruction faults are logged.

If the PI instruction is being used in Linear mode, this floating point equation is used to calculate the ITerm.

graphic

Due to the use of the single-precision floating point values, it is possible. This possibility is dependant on 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 ITermn-1.

For more information regarding the PI instruction, see the Logix5000™ Controllers Process Control and Drives Instructions User Manual, publication 1756-RM006.


Corrected

Cat. No.
Corrected As Of
1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E
Firmware Revision 18.011/RSLogix 5000 Software Version 18
1769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
Firmware Revision 18.011/RSLogix 5000 Software Version 18

Program Lost After Clearing IO Fault

Known Anomaly

Cat. No.
Identified As Of
1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E
 Firmware Revision 16.022/RSLogix 5000 Software Version 16
Firmware Revision 17.005/RSLogix 5000 Software Version 17
1769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
Firmware Revision 17.005/RSLogix 5000 Software Version 17

After clearing a fault due to a missing I/O module and cycling power to the CompactLogix controller, the program is lost from controller memory and no fault is logged.

With firmware revision 18.011, cycling power after clearing a fault for missing I/O modules does not result in the program being lost from controller memory.

 

Alarm Systems Timeout Changes Require New Download (00069461)

Known Anomaly First Identified as of:

Changes made to the Buffer Timeout value for FactoryTalk® Alarm subscribers do not take effect until the existing buffer has been deleted.

The FactoryTalk alarm buffer (stored in Logix controller memory) is designed to persist through power cycles. If you change the Buffer Timeout value (via the Communication Setup dialog in FactoryTalk View SE), the controller does not use the new timeout value until the existing buffer is deleted and then recreated. To force recreation of this buffer, you can either:


Corrected

 

Cat. No.
Corrected As Of
1769-L23E-QB1B, 1769-L23E-QBFC1
Firmware Revision 18.011/RSLogix 5000 Software Version 18
1769-L32E, 1769-L35E
Firmware Revision 18.011/RSLogix 5000 Software Version 18


No Memory Buffer (Lgx00087882)

Known Anomaly

Cat. No.
Identified As Of
1769-L23E-QB1B, 1769-L23E-QBFC1
Firmware Revision 17.005, 17.007, 17.012/RSLogix 5000 Software Version 17
1769-L32E, 1769-L35E
Firmware Revision 17.005/RSLogix 5000 Software Version 17

Use of the controller within Ethernet connection limits, but at or near maximum limits, may result in No Buffer Memory, error code 0x301.

If you use your controller at, or very near, the maximum Ethernet connection limits with produced/consumed tags, you may experience over-connection limit errors.

This anomaly is experienced only if your configured RPI rates are not binary multiples of 2 ms. This is because the CompactLogix controllers round the RPI down to the nearest binary multiple to make connections (for example, setting an RPI of 100 ms results in the controller sending data at 64 ms).

If you experience this anomalous behavior, adjust the RPI of controllers consuming data from the CompactLogix controller until the RPI rates are within the capabilities of the packaged controller. In addition, determine which communication module has exceeded the connection limit and adjust its RPI accordingly.

 

Modular Multivariable Control (MMC) Instruction (Lgx00100721, Lgx00091924)

Corrected as of:

Known Anomaly First Identified as of:

The Modular Multivariable Control (MMC) instruction does not always 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 manipulation 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 that is 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.

With firmware revision 18.11, the second and third CVs of the MMC instruction are manipulated, even if the first CV is within the range indicated by CVxHLimit and CVxLLimit.



SSV Instruction WallClockTime (Lgx00097399, Lgx00101632, Lgx00097459, Lgx00078925)

Corrected as of:

Known Anomaly First Identified as of:

Using an SSV instruction to set the WallClockTime causes a fault.

Setting the WallClockTime to an invalid value by using an SSV instruction results in a Major Nonrecoverable Fault (MNRF).

Using an SSV instruction to set the local controller's WALLCLOCKTIME by using the LocalDateTime attribute can result in an incorrect WALLCLOCKTIME value upon execution of the program. This incorrect time is evident in the seconds field.

The discrepancy in the WALLCLOCKTIME can also result in an 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.

With firmware revision 18.011, if a WallClockTime object’s DateTime attribute is invalid, a minor fault results.



Partial Import of Project (Lgx00103562, Lgx00103561, Lgx00102966)

Corrected as of:

Known Anomaly First Identified as of:

Partial import of a project that is developed and run on a SoftLogix™ controller causes fault.

Completing a partial import of a project that is 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:

• Coordinated Control (CC)

• Internal Model Control (IMC)

• Modular Multivariable Control (MMC)

The Major Nonrecoverable Fault occurs after the partial import is completed and the edits to the program are finalized.



SFC Reset (SFR) Step (Lgx00099968, Lgx00099132)

Corrected as of:

Known Anomaly First Identified as of:

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 SFC no longer executes. The SFC remains in the step it was reset to, and attempts to progress via a Transition, Force, or Step Through are unsuccessful. To begin executing the SFC again, you must execute an SFR instruction to the initial step or to a step above the first simultaneous branch.

With firmware revision 18.011, when an SFC is reset to a specified step the transitions occur as expected.




Interrupted Service Communication (Lgx00101330, Lgx00103549, Lgx00098734)

Corrected as of:

Known Anomaly First Identified as of:

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) can result. The connection that is closing could be a connection that is used for I/O, a message instruction, a forward open, and so on.

With firmware revision 18.011, a connection in the process of closing during a service communication interrupt of >300 ms occurs, but does not cause an MNRF.



Deleting Program Tags While Online (Lgx00086136, Lgx00085678)

Corrected as of:

Known Anomaly

Deleting program tags while online is successful, even though they are being referenced by RSLinx® software and must not be deleted.

RSLogix 5000 software and Logix5000™ controller firmware allow deletion of program tags while online with the controller. As a precaution, the firmware checks the tag to verify that it is not in use (that is, the tag is not being scanned or referenced) by RSLinx® Classic or RSLinx® 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. These tag types are always deleted, even if being used by RSLinx software:

• Motion Axis

• Motion Group

• Digital Alarm

• Analog Alarm

• Message

With firmware revision 18.011, tags being used by RSLinx software cannot be deleted while online with the controller



SSV Class Name SerialPort Attribute PendingComDriverID Does Not Set (Lgx00073954)

Corrected as of:

Known Anomaly First Identified as of:

SSV class name SerialPort, attribute PendingComDriverID, does not set.

With firmware revision 18.011, attempts to use an SSV instruction to set the SerialPort class, PendingComDriverID attribute, are successful.


Corrected

Cat. No.
Corrected As Of
11769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
 Firmware Revision 20.011/RSLogix 5000 Software Version 20
 
1769-L31, 1769-L32E, 1769-L32C, 1769-L35E, 1769-L35CR
Firmware Revision 20.011/RSLogix 5000 Software Version 20

VA Task Overlap (Lgx00118179, Lgx00117865, Lgx00135044, Lgx00118176)

Restriction/Known Anomaly

Cat. No.
Identified As Of
11769-L23E-QB1B, 1769-L23E-QBFC1B, 1769-L23-QBFC1B
Firmware Revision 17.005/RSLogix 5000 Software Version 17
1769-L31, 1769-L32E, 1769-L32C, 1769-L35E, 1769-L35CR
Firmware Revision 16.022/RSLogix 5000 Software Version 16

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 again, a task overlap occurs. This task overlap causes the packaged 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.

 

Cycle Power to Clear a Major Fault

Known Anomaly First Identified as of:

If a 1769 I/O fault occurs, you must cycle power to the CompactLogix™ controller after clearing the major fault. I/O communication is not restored until after the power cycle. Never use the fault handling routine to clear local I/O faults. Clear local I/O faults manually on a per case basis, and then the controller must be power cycled.


Echo Mode and Read Write Buffer (Lgx00087052, Lgx00087176)

Corrected as of:

Known Anomaly First Identified as of:

Setting the Read/Write Buffer size parameter before checking 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.

With firmware revision 18.011, you can specify the Read/Write Buffer size and check Echo Mode in any order to achieve a message echo.



RMPS Instruction Does Not Count Down in a Continuous Task (Lgx00100678, Lgx00085036, Lgx00083654)

Corrected as of:

Known Anomaly First Identified as of:

RMPS instruction in a continuous task does not count down.

If an 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 RSEmulate™ 5000 software.

To work around this anomaly, do one of the following.

• Use multiple soaks to achieve your total soak times greater than 1024 minutes.

• Use the RMPS in a periodic task that has a Period of 10 ms or greater.

This anomaly has been resolved with firmware revision 18.011. You can use an RMPS instruction in a continuous task with a Soak Time value greater than 1024 minutes.


MSG Execution in Master Slave Configurations (Lgx00083882, Lgx00082610)

Corrected as of:

Known Anomaly

Unsuccessful MSG execution results in subsequent unsuccessful messages in master/slave controller configurations.

When a DF1 serial connection is used between a master and slave controller, an 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 work around this anomaly, change the master station address of a controller to another value or re-execute the unsuccessful MSG instruction in Master

Transmit mode and use the Between Station Polls parameter.


Corrected

Cat. No.
Corrected As Of
1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E
Firmware Revision 18.011/RSLogix 5000 Software Version 18

IO Bank Power Failure Causes Fault on Controller (00086647)

Known Anomaly

Cat. No.
Identified As Of
1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E
Firmware Revision 17.005/RSLogix 5000 Software Version 17


If you use banks of I/O with your CompactLogix controller and the power supply of the second or third bank is disconnected, the OK, MS, and CompactFlash status indicators turn steady red and the controller transitions into Reset mode.

Once power is restored to the I/O bank, the controller status indicators return to their normal operating states and the controller program begins executing again.

 

Fault/Program States Not Supported by Using the Module Configuration
Dialog Box

Known Anomaly First Identified as of:

This anomaly applies to CompactLogix™ systems as follows:

In this description, the term I/O module refers to 1769 Compact output modules or output points on 1769 Compact combination modules.

RSLogix™ 5000 software does not support Fault/Program state action for I/O modules in CompactLogix systems. The controller cannot trigger the configured Fault/Program state action. You can configure the Fault/Program state action in RSLogix 5000 software, but the configuration does not take effect.

If either of the following conditions exists, outputs turn off, regardless of the Fault/Program state action configuration:

Additionally, RSLogix 5000 software generates configuration tags for any I/O modules in the project. Some of the tags define configuration (C) data type members that include attributes for Fault/Program states, also known as alternate output states.

Because CompactLogix systems do not support Fault/Program state action for I/O modules, do not configure the attribute tags listed in the following table.

Attribute Tags to Avoid

Digital Output Modules
Analog Output Modules
  • ProgToFaultEn
  • ProgMode
  • ProgValue
  • FaultMode
  • FaultValue
  • CHxProgToFaultEn
  • CHxProgMode
  • CHxFaultMode
Where CHx = the channel number

Functional Changes

This release has the following functional changes from the previous release.

V17 Additional Memory Requirements for 1769 CompactLogix Controllers


Functional Change

 

Cat. No.
Initial Firmware Revision/Software Version
1769-L31, 1769-L32C, 1769-L32E, 1769-L35CR, 1769-L35E
Firmware Revision 17.005/RSLogix 5000 Software Version 17



Firmware revision 17.000 or later may require more memory than previous revisions, for example, revision 10.xxx or 11.xxx). To estimate the additional memory that your project may require, use this table.

If you upgrade from revision (add all that apply)
 
 Then add the following memory requirements to your project
 
Which comes from this type of memory
 
Component
Increase/Decrease Per
Instance
I/O
Data and Logic
16.x to 17.x
Task
+ 4 bytes
 
ü
 
Program
+ 4 bytes
 
ü
 
Equipment phase
+ 8 bytes
 
ü
 
LD routine
+ 12 bytes
 
ü
 
FBD routine
- 8 bytes
 
ü
 
SFC routine
+ 28 bytes
 
ü
 
ST routine
+ 4 bytes
 
ü
 
Add-On Instruction
- 12 bytes
 
ü
 
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
 
Produced tag
+ [4 bytes + (4 bytes x number of consumers)
ü
 
 
Consumed tag
+ 8 bytes
ü
 
 
Tag that uses MESSAGE data type
+ 4 bytes
 
ü
 
Tag that uses ALARM_ANALOG data type
- 64 bytes
 
ü
 
Tag that uses ALARM_DIGITAL data type
- 28 bytes
 
ü
 
Tag that uses AXIS_SERVO_DRIVE or AXIS_GENERIC_DRIVE data type
- 34 bytes
(2 bytes x number of output cam execution targets)
 
ü
 
Tag that uses AXIS data type other than AXIS_SERVO_DRIVE or
AXIS_GENERIC_DRIVE
- 52 bytes
(2 bytes x number of output cam execution targets)
 
ü
 
Tag that uses COORDINATE_SYSTEM data type of 2 dimensions with 2 transform dimensions
+ 20 bytes
 
ü
 
Tag that uses COORDINATE_SYSTEM data type of 3 dimensions with 3 transform dimensions
+ 108 bytes
 
ü
15.x to 16.x
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
 
Tag that uses ALARM_ANALOG data type (with no associated tag references)
+ 16 bytes
 
ü
 
Tag that uses ALARM_DIGITAL data type (with no associated tag references)
+ 4 bytes
 
ü
 
Tag that uses ALARM_ANALOG data type (if associated tags are configured for the ALARM_ANALOG tag)
+ 22 bytes
+ (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
 
ü
 
Tag that uses the COORDINATE_SYSTEM data type
+ 132 bytes
 
ü
14.x to 15.x
Input module
+ 4 bytes
ü
 
 
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
 
Produced tag
+ 12 bytes
ü
 
 
Consumed tag
+ 4 bytes
ü
 
 
Tag that uses COORDINATE_SYSTEM data type
+ 748 bytes
 
ü
 
Tag the uses any AXIS data type
+ 800 bytes
 
ü
 
Task
+ 20 bytes
 
ü
 
Program or equipment phase
+ 24 bytes
 
ü
 
Routine
+ 4 bytes
 
ü
 
Serial port
+ 1120 bytes
 
ü
 
Project
+ 4012 bytes
 
ü
13.x to 14.x
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
 
Tag that uses the COORDINATE SYSTEM data type
+ 60 bytes
 
ü
 
Tag that uses any AXIS data type
+ 4 bytes
 
ü
12.x to 13.x
Program
+ 12 bytes
 
ü
 
Task
+ 4 bytes
 
ü
 
User-defined data type
+ 4 bytes
 
ü
 
I/O module
+ 16 bytes
ü
(8 bytes)
ü
(8 bytes)
 
If you use a tag of the types listed below, increase the memory as indicated for each instance:
 
 
 
 
Produced tag
+ 8 bytes
ü
 
 
Consumed tag
+ 8 bytes
ü
 

 

Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these changes.

Copyright © 2026 Rockwell Automation, Inc. All rights reserved.
Rockwell Automation, Allen-Bradley, and FactoryTalk are trademarks of Rockwell Automation, Inc.
To view a complete list of Rockwell Automation trademarks please click here.
Trademarks not belonging to Rockwell Automation are property of their respective companies.