Allen-Bradley 1756-L61 ControlLogix 5561 Programming Manual
  1. Manuals
  2. Brands
  3. Allen-Bradley Manuals
  4. Controller
  5. controllogix 1756-L61
  6. Programming manual

Allen-Bradley 1756-L61 ControlLogix 5561 Programming Manual

Logix5000 series
Hide thumbs Also See for 1756-L61 ControlLogix 5561:
Table of Contents

Advertisement

Quick Links

See also: User Manual
Programming Manual
Logix5000 Controllers I/O and Tag Data
Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 Compact GuardLogix, 1769 CompactLogix, 1789 SoftLogix, PowerFlex
with DriveLogix

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 1756-L61 ControlLogix 5561 and is the answer not in the manual?

Questions and answers

Related Manuals for Allen-Bradley 1756-L61 ControlLogix 5561

Summary of Contents for Allen-Bradley 1756-L61 ControlLogix 5561

  • Page 1 Programming Manual Logix5000 Controllers I/O and Tag Data Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 Compact GuardLogix, 1769 CompactLogix, 1789 SoftLogix, PowerFlex with DriveLogix...
  • Page 2 IMPORTANT Identifies information that is critical for successful application and understanding of the product. Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.2012...
  • Page 3 Summary of Changes This manual contains new and updated information. RSLogix 5000 programming software is now known as Studio 5000 Logix IMPORTANT Designer application, a component of the Studio 5000 Engineering and Design Environment. The following controllers are no longer supported in Logix Designer application, version 21.
  • Page 4 Summary of Changes Notes: Rockwell Automation Publication 1756-PM004D-EN-P - September 2012...

  • Page 5: Table Of Contents

    Table of Contents Preface Studio 5000 Engineering and Design Environment and Logix Designer Application ......... 5 Purpose of This Manual .
  • Page 6 Table of Contents Chapter 3 Force I/O Introduction ........... . . 57 Precautions .

  • Page 7: Preface

    Preface Studio 5000 Engineering and The Studio 5000™ Engineering and Design Environment combines engineering and design elements into a common environment. The first element in the Design Environment and Studio 5000 environment is the Logix Designer application. The Logix Designer Logix Designer Application application is the rebranding of RSLogix™...
  • Page 8 Preface Notes: Rockwell Automation Publication 1756-PM004D-EN-P - September 2012...

  • Page 9: Communicate With I/O Modules

    Chapter Communicate with I/O Modules Introduction To communicate with an I/O module in your system, you add the module to the I/O Configuration folder of the controller. Add I/O modules here. When you add the module, you also define a specific configuration for the module.

  • Page 10: Requested Packet Interval

    Chapter 1 Communicate with I/O Modules Requested Packet Interval The Logix5000 controller uses connections to transmit I/O data. Term Definition Connection A communication link between two devices, such as between a controller and an I/O module, PanelView terminal, or another controller. Connections are allocations of resources that provide more reliable communications between devices than unconnected messages.

  • Page 11: Direct Or Rack-Optimized Connection

    Communicate with I/O Modules Chapter 1 Direct or Rack-Optimized Connection The Logix5000 controller uses connections to transmit I/O data. These connections can be direct connections or rack-optimized connections. Term Definition Direct connection A direct connection is a real-time, data transfer link between the controller and an I/O module. The controller maintains and monitors the connection with the I/O module.
  • Page 12 Chapter 1 Communicate with I/O Modules When you choose a communication format, you have to choose whether to establish an owner or listen-only relationship with the module. Owner controller The controller that creates the primary configuration and communication connection to a module. The owner controller writes configuration data and can establish a connection to the module.
  • Page 13 Communicate with I/O Modules Chapter 1 Table 2 - Control Input and Output Modules Controlling This Ownership Description Input modules Owner An input module is configured by a controller that establishes a connection as an owner. This configuring controller is the first controller to establish an owner connection. Once an input module has been configured (and owned by a controller), other controllers can establish owner connections to that module.

  • Page 14: Electronic Keying

    When a Logix5000 controller begins communicating with a module, this set of keying attributes is considered. Attribute Description Vendor The manufacturer of the module, for example, Rockwell Automation/Allen-Bradley. Product Type The general type of the module, for example, communication adapter, AC drive, or digital I/O. Catalog Number The specific type of module, generally represented by its catalog number, for example, 1756-IB16I.

  • Page 15: Exact Match

    The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the Minor Revision of the module does not match precisely. Module Configuration Vendor = Allen-Bradley Product Type = Digital Input Module Catalog Number = 1756-IB16D...

  • Page 16: Compatible Module

    Chapter 1 Communicate with I/O Modules Compatible Module Compatible Module indicates that the module determines whether to accept or reject communication. Different module families, communication adapters, and module types implement the compatibility check differently based on the family capabilities and on prior knowledge of compatible products. Compatible Module is the default setting.
  • Page 17 The physical module is a 1756-IB16D module with module revision 3.2. In this case, communication is prevented because the minor revision of the module is lower than expected and may not be compatible with 3.3. Module Configuration Vendor = Allen-Bradley Product Type = Digital Input Module Catalog Number = 1756-IB16D...
  • Page 18 Module Configuration Vendor = Allen-Bradley Product Type = Digital Input Module Catalog Number = 1756-IB16D...
  • Page 19 The physical module is a 1756-IF16 analog input module. In this case, communication is prevented because the analog module rejects the data formats that the digital module configuration requests. Module Configuration Vendor = Allen-Bradley Product Type = Digital Input Module Catalog Number = 1756-IA16...
  • Page 20 The module configuration is for a 1756-IA16 digital input module. The physical module is a 1756-IB16 digital input module. In this case, communication is allowed because the two digital modules share common data formats. Module Configuration Vendor = Allen-Bradley Product Type = Digital Input Module Catalog Number = 1756-IA16...

  • Page 21: Address I/O Data

    Communicate with I/O Modules Chapter 1 Address I/O Data I/O information is presented as a set of tags. Each tag uses a structure of data. The structure depends on the specific features of the I/O module. The name of the tag is based on the location of the I/O module in the system.

  • Page 22: Buffer I/O

    Chapter 1 Communicate with I/O Modules Buffer I/O Buffering is a technique that logic does not directly reference or manipulate the tags of real I/O devices. Instead, the logic uses a copy of the I/O data. Buffer I/O in the following situations: To prevent an input or output value from changing during the execution of a program.
  • Page 23 Communicate with I/O Modules Chapter 1 This example copies inputs and outputs to the tags of a structure for a drill machine. EXAMPLE Buffer I/O The main routine of the program executes the following subroutines in this sequence. Jump to Subroutine Jump to Subroutine Jump to Subroutine Routine name map_inputs...
  • Page 24 Chapter 1 Communicate with I/O Modules This example uses the CPS instruction to copy an array of data that represent the input devices of a DeviceNet network. EXAMPLE Buffer I/O Local:0:I.Data stores the input data for the DeviceNet network that is connected to the 1756-DNB module in slot 0. To synchronize the inputs with the application, the CPS instruction copies the input data to input_buffer.

  • Page 25: Organizing Tags

    Chapter Organizing Tags Introduction With a Logix5000controller, you use a tag (alphanumeric name) to address data (variables). Term Definition A text-based name for an area of the controller’ s memory where data is stored. ·Tags are the basic mechanism for allocating memory, referencing data from logic, and monitoring data.

  • Page 26: Tag Type

    Chapter 2 Organizing Tags Tags EXAMPLE Analog I/O Device Integer Value Storage Bit Counter Timer Digital I/O Device Tag Type The tag type defines how the tag operates within your project. If you want the tag to Then choose this type Store a value or values for use by logic within the project Base Represent another tag...

  • Page 27: Data Type

    Organizing Tags Chapter 2 Data Type Term Definition Data type The data type defines the type of data that a tag stores, such as a bit, integer, floating-point value, string, and so forth. Structure A data type that is a combination of other data types. ·A structure is formatted to create a unique data type that matches a specific need.
  • Page 28 Chapter 2 Organizing Tags The minimum memory allocation for a tag is four bytes. When you create a tag that stores data that requires less than four bytes, the controller allocates four bytes, but the data only fills the part it needs. Data type Bits BOOL...

  • Page 29: Scope

    Organizing Tags Chapter 2 Scope When you create a tag, you define it as either a controller tag (global data) or a program tag for a specific program (local data). Project Controller tags I/O data (Global data) System-shared data Task Program Program tags (Local data)
  • Page 30 Chapter 2 Organizing Tags Avoid using the same name for both a controller tag and a program tag. Within a program, you cannot reference a controller tag if a tag of the same name exists as a program tag for that program. Certain tags must be controller scope (controller tag).

  • Page 31: Guidelines For Tags

    Organizing Tags Chapter 2 Guidelines for Tags Use the following guidelines to create tags for a Logix5000 project. Table 4 - Tag Guidelines Table 5 - Guideline Details Create user-defined data types User-defined data types (structures) let you organize data to match your machine or process. A user-defined data type provides these advantages: ·One tag contains all the data related to a specific aspect of your system.
  • Page 32 Chapter 2 Organizing Tags Table 4 - Tag Guidelines Table 5 - Guideline Details Limit a tag name to 40 characters Here are the rules for a tag name: ·Only alphabetic characters (A-Z or a-z), numeric characters (0…9), and underscores (_) ·Must start with an alphabetic character or an underscore ·No more than 40 characters ·No consecutive or trailing underscore characters (_)
  • Page 33 Organizing Tags Chapter 2 Table 4 - Tag Guidelines Table 5 - Guideline Details Using extended properties in logic (continued) In the Function Block Editor, you can access extended properties in logic by wiring an Input Reference to a block’s input pins.
  • Page 34 Chapter 2 Organizing Tags Table 4 - Tag Guidelines Table 5 - Guideline Details Using extended properties in logic (continued) ·Array Tags are constrained A constraint on array tags apply if the array tag uses indirect addressing to access limit extended properties. If an array tag is using indirect addressing to access limit extended properties in logic, the following conditions apply.

  • Page 35: Create A Tag

    Organizing Tags Chapter 2 Create a Tag The Tag Editor window lets you create and edit tags by using a spreadsheet-style view of the tags. The Logix Designer application also automatically creates tags when you: IMPORTANT – Add an element to a sequential function chart (SFC). –...
  • Page 36 Chapter 2 Organizing Tags The entries in the list depend on the tag’s data type. You can check more than one property. For data type You can add the following extended property Array and string Engineering Unit Bool State0 State1 Engineering Unit DINT, INT, LINT, SINT, and REAL and corresponding array member...

  • Page 37: Create An Array

    Organizing Tags Chapter 2 Create an Array Logix5000 controllers also let you use arrays to organize data. Term Definition Array A tag that contains a block of multiple pieces of data. ·An array is similar to a file. ·Within an array, each individual piece of data is called an element. ·Each element uses the same data type.
  • Page 38 Chapter 2 Organizing Tags Single-dimension array EXAMPLE In this example, a single timer instruction times the duration of several steps. Each step requires a different preset value. Because all the values are the same data type (DINTs) an array is used. To expand an array and display its elements, click the + sign.
  • Page 39 Organizing Tags Chapter 2 Two-dimension array EXAMPLE ATTENTION: A drill machine can drill one…five holes in a book. The machine requires a value for the position of each hole from the leading edge of the book. To organize the values into configurations, a two-dimension array is used. The first subscript indicates the hole that the value corresponds and the second subscript indications how many holes will be drilled (one…five).

  • Page 40: Configuring An Array

    Chapter 2 Organizing Tags Configuring an Array To create an array, you create a tag and assign dimensions to the data type. 1. On the Controller Organizer, right-click Controller Tags and choose Edit Tags. The Tag Editor window appears. 42350 2.

  • Page 41: Creating A User-Defined Data Type

    Organizing Tags Chapter 2 Creating a User-defined User-defined data types (structures) let you organize your data to match your machine or process. Data Type User-defined data type that stores a recipe. EXAMPLE ATTENTION: In a system of several tanks, each tank can run a variety of recipes. Because the recipe requires a mix of data types (REAL, DINT, BOOL, so forth), a user-defined data type is used.

  • Page 42: Guidelines For User-Defined Data Types

    Chapter 2 Organizing Tags User-defined data type that stores the data that is required to run a machine. EXAMPLE Because several drill stations require the following mix of data, use a user-defined data type. Name (of data type): DRILL_STATION Member Name Data Type Part_advance BOOL...

  • Page 43: Creating A User-Defined Data Type

    Organizing Tags Chapter 2 When you use the BOOL, SINT, or INT data types, place members that use the same data type in sequence. More Efficient Less Efficient BOOL BOOL BOOL DINT BOOL BOOL DINT DINT DINT BOOL Creating a User-defined Data Type 1.
  • Page 44 Chapter 2 Organizing Tags 3. Type a name and description for the user-defined data type. A description is optional. 4. For each member of the user-defined data type, type a name, data type, style, and description. 5. Click the External Access column, and choose an attribute. 42196 Limit any arrays to a single dimension.

  • Page 45: Adding Extended Properties To A User-Defined Data Type

    Organizing Tags Chapter 2 Adding Extended Properties to a User-Defined Data Type You can add Min, Max, Engineering Units, State 0, and State 1 properties to a data type or its member. When these properties are added, their values are made available for use by some Rockwell Automation HMIs.

  • Page 46: Describing A User-Defined Data Type

    Chapter 2 Organizing Tags Describing a User-defined The Logix Designer application lets you automatically build descriptions out of the descriptions in your user-defined data types. This greatly reduces the amount Data Type of time you have to spend documenting your project. Version 13.0 or later of the application.

  • Page 47: Activate Pass-Through And Append Descriptions

    Organizing Tags Chapter 2 Activate Pass-Through and Append Descriptions Follow these steps to use pass-through descriptions and append to base tag descriptions. 1. In the Logix Designer application, from the Tools menu choose Options. The Work Station Options screen appears. 2.

  • Page 48: Paste A Pass-Through Description

    Chapter 2 Organizing Tags Paste a Pass-Through Description Choose this command to paste a pass-through value of an item into the Description, Engineering Unit, State 0, or State 1 field of another item. Follow these steps to use a pass-through description as the starting point for a more specific description.

  • Page 49: Address Tag Data

    Organizing Tags Chapter 2 Address Tag Data A tag name follows this format. Name [Element] .Member [Element] .Bit .[Index] = Optional Where Name Name that identifies this specific tag. Element Subscript or subscripts that point to a specific element within an array. ·Use the element identifier only if the tag or member is an array.

  • Page 50: Alias Tags

    Chapter 2 Organizing Tags Alias Tags An alias tag lets you create one tag that represents another tag. Both tags share the same value. When the value of one of the tags changes, the other tag reflects the change as well. Use aliases in the following situations: Program logic in advance of wiring diagrams.

  • Page 51: Display Alias Information

    Organizing Tags Chapter 2 The following logic was initially programmed by using descriptive tag names, such as stop and conveyor_on. Later, the tags were converted to aliases for the corresponding I/O devices. stop start stop is an alias for Local:2:I.Data.1 (the <Local:2:I.Data.1>...

  • Page 52: Assign An Alias

    Chapter 2 Organizing Tags Assign an Alias Follow these steps to assign a tag as an alias tag for another tag. 1. On the Controller Organizer, right-click Controller Tags and choose Edit Tags. The Tag Editor window appears. 42360 2. Select the scope of the tag. 3.

  • Page 53: Assign An Indirect Address

    Organizing Tags Chapter 2 Assign an Indirect Address If you want an instruction to access different elements in an array, use a tag in the subscript of the array (an indirect address). By changing the value of the tag, you change the element of the array that your logic references.

  • Page 54: Expressions

    Chapter 2 Organizing Tags The following example loads a series of preset values into a timer, one value (array element) at a time. EXAMPLE Step through an array. The timer_presets array stores a series of preset values for the timer in the next rung. The north_tank.step tag points to which element of the array to use. For example, when north_tank.step equals 0, the instruction loads timer_presets[0] into the timer (60,000 ms).
  • Page 55 Organizing Tags Chapter 2 You can use these operators to specify the subscript of an array. Operator Description Operator Description Modulo Subtract/negate Complement Multiply Divide Square root Absolute value Integer to BCD Truncate BCD to integer Exclusive OR Format your expressions as follows. Table 7 - Format Expressions If the operator requires Use this format...

  • Page 56: Array Subscript Out Of Range

    Chapter 2 Organizing Tags Array Subscript Out of Range Every instruction generates a major fault if the array subscript is out of range. Transitional instructions also generate a major fault even if the rung is false. The controller checks the array subscript in these instructions even if the rung is false. EXAMPLE For more information on handling major faults, refer to the Logix5000 Controllers Major and Minor Faults Programming Manual,...

  • Page 57: Tag Documentation

    Organizing Tags Chapter 2 Tag Documentation The table outlines the four types of tags that can be created and the descriptions that you can document for each one. The Logix Designer application automatically assigns what are called pass-through IMPORTANT descriptions of the tags you have created. You may or may not want to use these descriptions.
  • Page 58 Chapter 2 Organizing Tags Enter the localized descriptions in your Logix Designer project, either when programming in that language or by using the import/export utility to translate the documentation off-line and then import it back into the project. Once you enable documentation languages in the Logix Designer application, you can dynamically switch between languages as you use the application.

  • Page 59: Introduction

    Chapter Force I/O Introduction Use a force to override data that your logic either uses or produces. For example, use forces to: test and debug your logic. check wiring to an output device. temporarily keep your process functioning when an input device has failed. Use forces only as a temporary measure.

  • Page 60: Disable Or Remove A Force

    Chapter 3 Force I/O When forces are in effect (enabled), a appears next to the forced element. state to which the element is forced Disable or Remove a Force To stop the effect of a force and let your project execute as programmed, disable or remove the force.

  • Page 61: Force Status Indicator

    Force I/O Chapter 3 The Online toolbar shows the status of forces. It shows the status of I/O forces and SFC forces separately. Forces tab This Means Enabled ·If the project contains any forces of this type, they are overriding your logic. ·If you add a force of this type, the new force immediately takes effect Disabled Forces of this type are inactive.

  • Page 62: When To Use I/O Force

    Chapter 3 Force I/O where: Force_Status is a DINT tag. To determine if Examine this bit For this value Forces are installed No forces are installed Forces are enabled Forces are disabled When to Use I/O Force Use an I/O force to: override an input value from another controller (that is, a consumed tag).

  • Page 63: Force An Input Value

    Force I/O Chapter 3 If a produced tag is forced, you cannot make it Constant. Force an Input Value Forcing an input or consumed tag: overrides the value regardless of the value of the physical device or produced tag. does not affect the value received by other controllers monitoring that input or produced tag.

  • Page 64: Remove Or Disable Forces

    Chapter 3 Force I/O 4. Install the force value. To force a Do this BOOL value Right-click tag and choose Force On or Force Off. Non-BOOL value In the Force Mask column for the tag, type the value that you want to force the tag.

  • Page 65: Disable All I/O Forces

    Force I/O Chapter 3 3. Right-click a tag that has the force and choose Monitor. If necessary, expand the tag to show the value that is forced, for example, BOOL value of a DINT tag. 4. Right-click a tag or element that has the force and choose Remove Force. Disable All I/O Forces To disable, choose Logic>I/O Forcing>Disable All I/O Forces.
  • Page 66 Chapter 3 Force I/O Notes: Rockwell Automation Publication 1756-PM004D-EN-P - September 2012...

  • Page 67: Introduction

    Chapter Data Access Control In the Logix platform, version 18 or later of the application, there are two tag Introduction attributes that allow you to control access to tag data. These attributes are: External Access Constant The External Access attribute controls how external applications, such as HMIs, can access tags.

  • Page 68: Configure External Access

    Chapter 4 Data Access Control Configure External Access You configure external access from a menu when you create a new tag or data type. You can also modify that value just like other tag attributes. These changes can be made throughout the application. For example, they can be made in the User-defined Data Type Editor, New Tag Dialog, and the Tag Properties Dialog.

  • Page 69: Configure External Access In The New Tag Dialog Box

    Data Access Control Chapter 4 For Alias type, the External Access box is disabled. You are not allowed to change IMPORTANT the external access of an alias tag. However, the External Access box will update its value to be the same as the external access of the base target. “‘Go To’...
  • Page 70 Chapter 4 Data Access Control The New Tag Dialog Box appears. 2. From the Type menu, choose a tag type. 3. From the External Access menu, choose an external access option. 4. Click OK. As shown in the example below, the External Access box is dimmed for an alias tag.

  • Page 71: Set Up External Access In The Tag Properties Dialog Box

    Data Access Control Chapter 4 For other tag considerations, see “External Access Availability” on page The Connection button (next to the Type box) becomes active when either a produced or consumed tag type is selected. The button accesses a dialog box for setting up produced/consumed tag connections.

  • Page 72: View And Select External Access Status On The Tag Editor Window

    Chapter 4 Data Access Control The External Access box is dimmed for an alias tag. If a tag is a module tag, the only external access option is Read/Write. “External Access Availability” page 72 for other considerations. 4. Click OK. View and Select External Access Status on the Tag Editor Window You can view the external access status of a tag in the Tag Editor window.

  • Page 73: Go To' Search Menu

    Data Access Control Chapter 4 “External Access Availability” page 72 for considerations when the External Access column is disabled. ‘Go To’ Search Menu The external access setting of an alias tag can only be changed through its base tag. The ‘Go To’ option on the Search menu of the Logix Designer application is a convenient way to find the base tag among all the cross-reference records.

  • Page 74: External Access Availability

    Chapter 4 Data Access Control External Access Availability The following table describes the conditions in which the External Access box is disabled. The External Access box is always disabled for any tag whose data type is Alarm IMPORTANT Analog or Alarm Digital. The external access status is always Read/Write for these data types.

  • Page 75: User-Defined Type Considerations

    Data Access Control Chapter 4 User-defined Type The three external access options—Read/Write (default), Read Only, None—are chosen from the External Access column on the Data Type Considerations dialog box. Three external access rules apply for members of User-defined data types. You can only set external access for the top members of that User-defined data type.
  • Page 76 Chapter 4 Data Access Control The table below describes the External Access options for various Add-On Instruction parameters and tags. Add-0n Instruction Parameters and Tags External Access Options Local tag Read/Write Input parameter Read Only None Output parameter EnableIn parameter Read Only EnableOut parameter InOut parameter...
  • Page 77 Data Access Control Chapter 4 Dialog Box/Window Considerations Parameters/Local Tab No change is applied to the External Access box if you switch the usage among Input Properties parameter, Output parameter or Local tag, except when the usage is a Local tag, the box is disabled.

  • Page 78: Tag Mapping Considerations

    Chapter 4 Data Access Control Tag Mapping Considerations Only tags with external access settings of Read/Write or Read Only can be mapped to a PLC-2 controller and PLC-5/SLC controllers. Dialog Box/Window Considerations PLC-2, PLC-5/SLC Mapping To map a tag: • Type a file number. •...

  • Page 79: Constant Value Tags

    Data Access Control Chapter 4 Constant Value Tags Version 18 and later of the application, you can designate tags as constants to protect them from being changed programatically via: the controller programming application. logic in the controller. Tags that cannot be designated as constants are User-defined type members, Add-On Instruction input and output parameters, and local tags.

  • Page 80: Configure Constant Tags

    Chapter 4 Data Access Control Configure Constant Tags This section describes the various ways a constant attribute can be configured. Set Up a Constant in the New Tag Dialog Box Follow these steps to configure a tag as a constant on the New Tag dialog box. 1.
  • Page 81 Data Access Control Chapter 4 1. On the Tag Editor window, right-click a tag and choose Edit (tag name) Properties. The Tag Properties dialog box appears. 2. From the Type menu, choose a tag type. 3. Check Constant. 4. Click OK. “Constant Checkbox Availability”...

  • Page 82: Designate A Constant In The Tag Editor

    Chapter 4 Data Access Control Designate a Constant in the Tag Editor The Constant column on the Tag Editor window lets you designate tags that cannot be modified in the Logix Designer program. The Constant property applies to an entire tag; all members of the tag take on the same setting. The Constant column cells are blank for members of the constant tag.

  • Page 83: Constant Checkbox Availability

    Data Access Control Chapter 4 Constant Checkbox Availability The state of the Constant checkbox depends on a number of conditions. Dialog Box/Window Considerations New Tag The Constant box is disabled if: • the tag is an alias tag. • the Factory Talk Security action is not enabled for changing constant value property of a tag.

  • Page 84: Add-On Instructions Constant Value Considerations

    Chapter 4 Data Access Control Add-On Instructions Constant The Constant attribute applies only to InOut parameters. The default setting of the property will be not a Constant Value. Value Considerations The Constant attribute will not apply to Input, Output, EnableIn and EnableOut Add-On Instruction parameters.

  • Page 85: Rockwell Automation Publication 1756-Pm004D-En-P - September

    Index tag properties 78 value configuration 78 access value tags 77 external 65 controller add extended properties to a tag 33 tags 27 add extended properties to user-defined data type 43 use of 27 create Add-On Instruction alias 50 constant value considerations 82 tag 33 external access variables 74 user-defined data type 41...
  • Page 86 Index file name ?See array guidelines for tag 29 force reuse of tag name 27 disable 58 enable 57 options 60 remove 58 ownership safety precautions 57 I/O module 9 tag 60 function block diagram force a value 57 pass-through description 44 program tags 27 global data...
  • Page 87 Index force 60 guidelines 29 user-defined data type I/O 19 create 41 mapping external access variables 73 considerations 76 guidelines 40 memory allocation 25 overview 39 name 27 organize 29 overview 23 properties external access 69 variables reuse of name 27 constant value 81 scope 27 external access 72...
  • Page 88 Index Rockwell Automation Publication 1756-PM004D-EN-P - September 2012...
  • Page 90 Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.

This manual is also suitable for:

1756-l61s controllogix 5561s1756-l63 controllogix 55631756-l63s controllogix 5563s1756-l64 controllogix 55641756-l65 controllogix 55651756-l62 controllogix 5562 ... Show all

Table of Contents

Save PDF