Allen-Bradley ControlLogix 1756 Reference Manual

Allen-Bradley ControlLogix 1756 Reference Manual

Controllers design considerations
Hide thumbs Also See for ControlLogix 1756:
Table of Contents

Advertisement

Reference Manual
Logix5000 Controllers Design Considerations
Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 CompactLogix, 1768 Compact GuardLogix, 1769 CompactLogix,
1789 SoftLogix, CompactLogix 5370
AB Drives

Advertisement

Table of Contents
loading

Summary of Contents for Allen-Bradley ControlLogix 1756

  • Page 1 Reference Manual Logix5000 Controllers Design Considerations Catalog Numbers 1756 ControlLogix, 1756 GuardLogix, 1768 CompactLogix, 1768 Compact GuardLogix, 1769 CompactLogix, 1789 SoftLogix, CompactLogix 5370 AB Drives...
  • Page 2 Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE). Allen-Bradley, CompactBlock Guard I/O, CompactLogix, ControlFLASH, ControlLogix, DH+, FactoryTalk, FLEX, GuardLogix, Kinetix, Logix5000, MicroLogix, PanelBuilder, PanelView, PhaseManager, PLC-2, PLC-3, PLC-5, POINT I/O, POINT Guard I/O, Rockwell Automation, Rockwell Software, RSBizWare, RSFieldbus, RSLinx, RSLogix 5000, RSNetWorx, RSView, SLC, SoftLogix, Stratix, Stratix 2000, Stratix 5700, Stratix 6000, Stratix 8000, Stratix 8300, Studio 5000, Studio 5000 Logix Designer, SynchLink, and Ultra are trademarks of Rockwell Automation, Inc.
  • Page 3 Logix5000 Controller Comparison - CompactLogix, ControlLogix, GuardLogix Table 1 - CompactLogix, ControlLogix, and GuardLogix Characteristics Characteristic CompactLogix™ CompactLogix CompactLogix ControlLogix® 1769-L30ER, 1769-L24ER-BB1B, 1769-L16ER-BB1B, 1756-L71, 1756-L72, 1756-L73, 1769-L30ER-NSE, 1769-L24ER-QBFC1B, 1769-L18ER-BB1B, 1756-L74, 1756-L75, 1756-L73XT 1769-L30ERM, 1769-L27ERM-QBFC1B 1769-L18ERM-BB1B 1769-L33ER, GuardLogix® 1769-L33ERM, 1756-L72S, 1756-L73S, 1756-L73SXT 1769-L36ERM Controller tasks: •...
  • Page 4 Chapter 1 Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 5: Rockwell Automation Publication 1756-Rm094I-En-P - September 2015

    Summary of Changes This manual contains new and updated information. Changes throughout this revision are marked by change bars, as shown to the right of this paragraph. Topic Page Logix5000™ Controller Comparison Table: • Removed 1756-L6x, 1769-L23x, 1769-L3x, and 1769-L4x because they are no longer supported. •...
  • Page 6 Summary of Changes Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 7: Table Of Contents

    Table of Contents Preface Additional Resources ..........11 Websites .
  • Page 8 Table of Contents Guidelines to for Subroutines ........45 Guidelines for User-defined Data Types .
  • Page 9 Table of Contents More Information ..........75 Guidelines to Manage I/O Connections .
  • Page 10 Table of Contents Chapter 10 Optimize an Application for Use with HMI Implementation Option........111 Compare FactoryTalk View Site Edition and RSView32 Software .
  • Page 11: Preface

    IASIMP-QS010 • SoftLogix System User Manual, 1789-UM002 SoftLogix Controllers You can view or download publications at http://www.rockwellautomation.com/literature/. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative. Websites Resource Description http://www.ab.com/logix/ Logix Product Information http://www.ab.com/networks/...
  • Page 12 Preface Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 13: Logix5000 Controller Resources

    Chapter Logix5000 Controller Resources Topic Page Estimate Memory Use Controller Connections Determine Total Connection Requirements CIP Sync Controller Mode 1756-L7x ControlLogix controllers - Memory is separated into isolated sections. Project Documentation Memory Logic and Data Memory I/O Memory Comment descriptions Program source code I/O data Logix...
  • Page 14 Chapter 1 Logix5000 Controller Resources CompactLogix 5370 controllers - Memory is separated into isolated segments. Project Documentation Memory Logic and Data Memory I/O Memory Comment descriptions Program source code I/O data Logix Alarm log Tag data I/O force tables Message buffers Extended tag properties RSLinx tag group lists Produced/consumed tags...
  • Page 15 Logix5000 Controller Resources Chapter 1 SoftLogix controllers - Memory is in one, contiguous section. Project Documentation Memory Logic, Data, and I/O Memory Program source code I/O data Comment descriptions Windows Logix operating I/O force tables Alarm log Tag data system Message buffers Extended tag properties RSLinx tag group lists...
  • Page 16: Estimate Memory Use

    Chapter 1 Logix5000 Controller Resources Estimate Memory Use The equations provide an estimate of the memory that is needed for a controller. If you configure controllers for redundancy, you must double the memory IMPORTANT resources that are required for a non-redundant application. Controller tasks _____ * 4,000...
  • Page 17: Compare Plc/Slc Memory

    Logix5000 Controller Resources Chapter 1 Compare PLC/SLC MEMORY The Logix5000 controllers use compiled instructions to provide faster execution times than PLC or SLC™ processors. The compiled instructions use more memory when compared to the instructions in PLC and SLC processors. If you have a PLC/SLC program, you can estimate the number of bytes it takes in a Logix5000 controller by the following equation: number PLC/SLC words ...
  • Page 18: Determine Total Connection Requirements

    Chapter 1 Logix5000 Controller Resources The limit of connections can ultimately reside in the communication module you use for the connection. If a message path routes through a communication module, the connection that is related to the message also counts toward the connection limit of that communication module.
  • Page 19 Logix5000 Controller Resources Chapter 1 The ControlLogix and SoftLogix controllers support more communication modules than the other controllers, so you must tally local connections to make sure that you stay within the connection limit. Use this table to tally local connections. Connection Type Device Quantity Connections per Module...
  • Page 20: Cip Sync

    Chapter 1 Logix5000 Controller Resources CIP Sync CIP Sync is a time synchronization implementation that incorporates IEEE-1588 standards on the EtherNet/IP protocol. CIP Sync provides the control system access to synchronization information and transport and routing of a system clock on standard CIP networks. CIP Sync offers the following features: •...
  • Page 21: Controller Mode

    Logix5000 Controller Resources Chapter 1 Controller Mode The controller mode switch provides a mechanical means to enhance controller and control system security. You must physically move the switch to change the operating mode from RUN to REM or to PROG. Remote lets you change the operational mode to REM RUN or REM PROG via RSLogix 5000 software.
  • Page 22 Chapter 1 Logix5000 Controller Resources Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 23: Logic Execution

    Chapter Logic Execution Topic Page Decide When to Use Tasks, Programs, and Routines Specify Task Priorities Manage User Tasks Considerations that Affect Task Execution Configure a Continuous Task Configure a Periodic Task Configure an Event Task Select a System Overhead Percentage Manage the System Overhead Timeslice Percentage Access the Module Object Develop Application Code in Routines...
  • Page 24: Decide When To Use Tasks, Programs, And Routines

    Chapter 2 Logic Execution Routines contain the executable code. Each program has a main routine that is Routines to encapsulate the first routine to execute within a program. Use logic, such as the Jump to executable code that is written in one programming language Subroutine ( JSR) instruction, to call other routines.
  • Page 25: Specify Task Priorities

    Logic Execution Chapter 2 Specify Task Priorities Each task in the controller has a priority level. A higher priority task (such as 1) interrupts any lower priority task (such as 15). The continuous task has the lowest priority; periodic or event tasks always interrupt continuous tasks. Logix5000 Controller User Tasks Supported Available Priority Levels...
  • Page 26: Manage User Tasks

    Chapter 2 Logic Execution Manage User Tasks You can configure these user tasks. If you want logic to execute Use this task Description All of the time Continuous task The continuous task runs in the background. Any CPU time that is not allocated to other operations or tasks is used to execute the continuous task.
  • Page 27: Considerations That Affect Task Execution

    Logic Execution Chapter 2 Considerations that Affect Task Execution Consideration Description Motion planner The motion planner interrupts all other tasks, regardless of their priority. • The number of axes and coarse update period for the motion group affect how long and how often the motion planner executes.
  • Page 28 Chapter 2 Logic Execution This example depicts the execution of a project with these tasks. Task Priority Period Execution Time Duration Motion planner 8 ms (course update rate) 1 ms 1 ms  Event task 1 1 ms 2 ms ...
  • Page 29: Configure A Continuous Task

    Logic Execution Chapter 2 Configure a Continuous Task The continuous task is created automatically when you open an RSLogix 5000® software project. A continuous task is similar to how logic executes on PLC-5® and SLC™ 500 processors. A Logix5000 controller supports one continuous task, but a continuous task is not required.
  • Page 30: Configure An Event Task

    Chapter 2 Logic Execution Configure an Event Task An event task executes automatically based on a trigger event occurring or if a trigger event does not occur in a specific time interval. You configure whether the task updates output modules at the end of the task. After the task executes, it does not execute again until the event occurs again.
  • Page 31: Select A System Overhead Percentage

    Logic Execution Chapter 2 Select a System Overhead The system overhead timeslice specifies the percentage of continuous task execution time that is devoted to communication and background redundancy Percentage functions. System overhead functions include the following: • Communicating with programming and HMI devices (such as RSLogix 5000 software) •...
  • Page 32: Manage The System Overhead Timeslice Percentage

    Chapter 2 Logic Execution Manage the System As the system overhead timeslice percentage increases, time that is allocated to executing the continuous task decreases. If there is no communication for the Overhead Timeslice controller to manage, the controller uses the communication time to execute the Percentage continuous task.
  • Page 33: Access The Module Object

    Logic Execution Chapter 2 Access the Module Object The MODULE object provides status information about a module. To select a particular module object, set the Object Name operand of the GSV/SSV instruction to the module name. The specified module must be present in the I/O Configuration section of the controller organizer and must have a device name.
  • Page 34: Develop Application Code In Routines

    Chapter 2 Logic Execution Develop Application Code in Each routine contains logic in one programming language. Choose a programming language that is based on the application. Routines Section of Code Represents Language to Use Continuous or parallel execution of multiple operations (not sequenced) Relay ladder logic (LD) Boolean or bit-based operations Complex logical operations...
  • Page 35: Programming Methods

    Logic Execution Chapter 2 Programming Methods The capabilities of the Logix5000 controllers make different programming methods possible. There are trade-offs to consider when selecting a programming method. Inline Duplication Write multiple copies of the code with different tag references. Benefits •...
  • Page 36: Buffered Routine

    Chapter 2 Logic Execution Buffered Routine Copy the values of an array into tags to directly reference these buffer tags. Benefits • One copy operation can occur faster than multiple index offsets • Eliminates the need to calculate array offsets at run time •...
  • Page 37: Add-On Instruction Prescan Logic

    Logic Execution Chapter 2 Add-On Instruction Prescan Logic An Add-On Instruction prescan logic executes after the main logic executes in Prescan mode. Use the prescan logic to initialize tag values before execution. For example, set a PID instruction to Manual mode with a 0% output before its first execution.
  • Page 38: Timer Execution

    Chapter 2 Logic Execution Timer Execution Timers in the PLC, SLC, and Logix5000 controllers all store off a portion of the real-time clock each time they are scanned. The next time through, they compare this stored value against the current clock and then adjust the ACC value by the difference.
  • Page 39: Edit An Sfc Online

    Logic Execution Chapter 2 Edit an SFC Online Firmware revision 13 adds support for editing SFCs online. When you edit an SFC online, the software initially makes the changes in the offline project. When you accept the changes, they are downloaded to the controller. If you transition the controller to test or untest edits, the controller resets the SFC and starts execution at the initial step.
  • Page 40 Chapter 2 Logic Execution Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 41: Modular Programming Techniques

    Chapter Modular Programming Techniques Modular programming guidelines support the delivery of standardized programming structures, conventions, configurations, and strategies. The goal of modular programming is to provide consistency. • Faster and easier development of application software • Faster and easier testing of application software •...
  • Page 42: Naming Conventions

    Chapter 3 Modular Programming Techniques Naming Conventions The following conventions are guidelines to help make an engineering library more reusable by other developers. These guidelines also help the resulting applications have a more consistent look and feel. • Names that are meaningful (and readable) to people who use the application as a later date are most effective.
  • Page 43 Modular Programming Techniques Chapter 3 Component Name Recommendations I/O or communication module Controller name, underscore, abbreviation of rack location (L=local, R=remote), underscore, the letter S, 2-digit slot number, underscore, abbreviation of function Example Functions: Analog input Analog output Discrete input Discrete output Analog input/output combination Discrete input/output combination...
  • Page 44: Parameter Name Prefixes

    Chapter 3 Modular Programming Techniques Parameter Name Prefixes Programming structures, such as Add-On Instructions and programs support parameters for passing values. The convention for prefixes is to abbreviate the function of the parameter to three letters and an underscore, followed by additional text to clarify the specific function.
  • Page 45: Guidelines To For Subroutines

    Modular Programming Techniques Chapter 3 Parameter Function Prefix Description Parameter Par_ Variables that are received from an external source that can be internal or external to the program. Examples: • Par_MachineSpeed: Provides a machine's running speed • Par_TargetFillLevel: Provides a tank's target fill level Set point Set_ Variables received from an operator or HMI and are not part of an external source.
  • Page 46: Guidelines For User-Defined Data Types

    Chapter 3 Modular Programming Techniques Guidelines for User-defined A UDT lets you organize or group data logically, so that all of the data associated with a device (such as a pressure transmitter or variable frequency drive) can be Data Types grouped together.
  • Page 47 Modular Programming Techniques Chapter 3 In the following example, the UDT on the left, UDT_Tank, has members arranged by function without regard for memory usage. This makes sense in the context of implementation, because members toward the top are ordinarily used in the software code.
  • Page 48: Guidelines For Add-On Instructions

    Chapter 3 Modular Programming Techniques Guidelines for Add-On An Add-On Instruction encapsulates commonly used functions or device controls. It is not intended for use as a high-level hierarchical design tool. Once Instructions an Add-On Instruction is defined in a project, it behaves similarly to the built-in instructions that are already available in the programming software.
  • Page 49: Add-On Instruction Design Concepts

    Modular Programming Techniques Chapter 3 Add-On Instruction Design Concepts To be sure that specific data is passed into or out of the add-on instruction, use a required parameter. A required parameter must be passed as an argument in order for a call to the instruction for verification. To pass a required parameter in ladder diagrams and in structured text, specify an argument tag for the parameter.
  • Page 50: Comparison Of Partial Import/Export And Add-On Instructions

    Chapter 3 Modular Programming Techniques Comparison Subroutine Add-On Instructions Memory use Compact • Call requires more memory • All references need additional memory Both code and data can be modified offline and online in a running Code modifications are limited to offline in the project file and require Edit controller a new download...
  • Page 51: Guidelines For Program Parameters

    Modular Programming Techniques Chapter 3 Guidelines for Program Program parameters define a data interface for programs to facilitate data sharing. Data sharing between programs can be achieved either through pre-defined Parameters connections between parameters or directly through a special notation. Unlike local tags, all program parameters are publicly accessible outside of the program.
  • Page 52: Comparison Of Program Parameters And Add-On Instructions

    Chapter 3 Modular Programming Techniques Comparison of Program Parameters and Add-On Instructions Comparison Program Parameters Add-On Instructions Accessibility Within program (multiple copies) Anywhere in controller (single copy) Parameters Input / Output (pass by value), InOut (pass by reference), Public (pass Input / Output (pass by value), InOut (pass by reference) by value) Numeric parameters...
  • Page 53: Address Data

    Chapter Address Data Logix5000 controllers support IEC 61131-3 atomic data types, such as BOOL, SINT, INT, DINT, LINT, and REAL. The controllers also support compound data types, such as arrays, predefined structures (such as counters and timers), and user-defined structures. Data Type Description Atomic data type...
  • Page 54: Guidelines For Data Types

    Chapter 4 Address Data The Logix CPU reads and manipulates 32-bit data values. The minimum memory allocation for data in a tag is 4 bytes. When you create a standalone tag that stores data that is less than 4 bytes, the controller allocates 4 bytes, but the data only fills the part that it needs.
  • Page 55: Arrays

    Address Data Chapter 4 Arrays An array allocates a contiguous block of memory to store a specific data type as a table of values. • Tags support arrays in one, two, or three dimensions. • User-defined structures can contain a single-dimension array as a member of the structure.
  • Page 56: Guidelines For Arrays

    Chapter 4 Address Data Guidelines for Arrays Guideline Description You can create arrays of most data types, except for A subscript identifies an individual element within the array. A subscript starts at 0 and extends to the number of ALARM, AXIS, COORDINATE_SYSTEM, MOTION_GROUP, elements minus 1 (zero based).
  • Page 57: Guidelines For Array Indexes

    Address Data Chapter 4 You can also use an expression to specify the index value. For example: MyArray[10 + MyIndex]. • An expression uses operators to calculate a value. • The controller computes the result of the expression and uses it as the index.
  • Page 58: Guidelines For User-Defined Structures

    Chapter 4 Address Data Guidelines for User-defined Structures Table 1 - UDT Guidelines Guideline Description Group members of the same data type within a structure. You can create members of most data types, except for ALARM, AXIS, COORDINATE_SYSTEM, MOTION_GROUP, and MESSAGE data types.
  • Page 59: Select A Data Type For Bit Tags

    Address Data Chapter 4 Select a Data Type for Bits in a Logix5000 controller can exist as: BOOL tags, bits in a BOOL array, bits in elements of a SINT, INT, DINT array, members of a user-defined Bit Tags structure, or as bits in a SINT, INT, DINT member of a user-defined structure. Tag Type Description BOOL tag...
  • Page 60: Serial Bit Addresses

    Chapter 4 Address Data Serial Bit Addresses The BOOL B data table in the PLC-5 and SLC 500 processors supports two address modes that can address the same bit. Address Mode Description Serial bit Serial bit addressing references all bits as a contiguous list (array) of bits. For example, if you want to reference the third bit in the second word of a B file, specify B3/18.
  • Page 61: Guidelines For String Data Types

    Address Data Chapter 4 Guidelines for String String data types are structures that hold ASCII characters. The first member of the structure defines the length of the string; the second member is an array that Data Types holds the actual ASCII characters. Guideline Description You can create a string data type that is longer or shorter...
  • Page 62: Configure Tags

    Chapter 4 Address Data Configure Tags A tag is a text-based name for an area of the controller’s memory where data is stored. Tags are the basic mechanism to allocate memory, reference data from logic, and monitor data. If you want the tag to Then choose this type Store a value for use by logic within the project Base...
  • Page 63: Create Alias Tags

    Address Data Chapter 4 Table 2 - Base Tag Guidelines Guideline Description Take advantage of program-scoped tags. If you want multiple tags with the same name, define each tag at the program scope (program tags) for a different program. This lets you reuse both logic and tag names in multiple programs. Avoid using the same name for both a controller tag and a program tag.
  • Page 64: Guidelines For Data Scope

    Chapter 4 Address Data Guidelines for Data Scope Data scope defines where you can access tags. Controller-scoped tags are accessible by all programs. Program-scoped tags are accessible only by the code within a specific program; phase-scoped tags are accessible only by the code Controller scope within a specific equipment phase.
  • Page 65: Guidelines For Extended Tag Properties

    Address Data Chapter 4 Guidelines for Extended Tag Use the following guidelines for extended tag properties. Properties Guideline Description Use extended tag properties to define additional You can define extended tag properties for these components: information, such as limits, engineering units, or state •...
  • Page 66: Tag Descriptions

    Chapter 4 Address Data Tag Descriptions RSLogix 5000 software searches a tag’s origin to locate the first available description. This reduces the number of descriptions you need to enter. This also verifies that tag references display associated descriptions. Guideline Description Tag descriptions display in RSLogix 5000 software according to the tag’s origin.
  • Page 67: Produced And Consumed Data

    Chapter Produced and Consumed Data Logix5000 controllers support the ability to produce (broadcast) and consume (receive) system-shared tags. For two controllers to share produced or consumed tags, both controllers must be in the same backplane or attached to the same control network. You cannot bridge produced and consumed tags over two networks.
  • Page 68: Guidelines To Specify An Rpi Rate For Produced And Consumed Tags

    Chapter 5 Produced and Consumed Data Guideline Description Use one of these data types: To share data types other than DINT or REAL, create a user-defined structure to contain the required data. • DINT Use the same data type for the produced tag and the corresponding consumed tag or tags. •...
  • Page 69: Guidelines To Manage Connections For Produced And Consumed Tags

    Produced and Consumed Data Chapter 5 Guidelines to Manage Connections for Produced and Consumed Tags Guideline Description Minimize the use of produced and consumed tags. To reduce network traffic, minimize the size of produced and consumed tags. Also, minimize the use of produced and consumed tags to high-speed, deterministic data, such as interlocks.
  • Page 70: Compare Messages And Produced/Consumed Tags

    Chapter 5 Produced and Consumed Data Compare Messages and Produced/Consumed Tags Method Benefits Considerations Read/Write Message • Programmatically initiated • Delay can occur if resources are not available when needed • Communication and network resources that are only used when •...
  • Page 71: Communicate With I/O

    Chapter Communicate with I/O In Logix5000 controllers, I/O values update at a period, requested packet interval (RPI), which you configure via Module Property dialog in the I/O configuration folder of the project. The values update asynchronously to the execution of logic. The module sends input values to the controller at the specified RPI.
  • Page 72: Guidelines To Specify An Rpi Rate For I/O Modules

    Chapter 6 Communicate with I/O Guidelines to Specify an RPI Configure an RPI rate per module (ControlLogix and SoftLogix) or an RPI rate per controller (CompactLogix). The RPI value is the rate at which the controller Rate for I/O Modules attempts to communicate with the module.
  • Page 73: Communication Formats For I/O Modules

    Communicate with I/O Chapter 6 Communication Formats for The communication format determines whether the controller connects to the I/O module via a direct or a rack-optimized connection. The communication I/O Modules format also determines the type and quantity of information that the module provides or uses.
  • Page 74 Chapter 6 Communicate with I/O Output modules let peer ownership of input modules to consume input data to Peer control directly control outputs without requiring controller processing. The 1756- IB16IF and 1756-IB16IFC modules can be listened to presuming the output module knows the input data layout and connection information.
  • Page 75: Electronic Keying

    Communicate with I/O Chapter 6 Electronic Keying Electronic Keying reduces the possibility that you use the wrong device in a control system. It compares the device that is defined in your project to the installed device. If keying fails, a fault occurs. These attributes are compared. Attribute Description Vendor...
  • Page 76: Guidelines To Manage I/O Connections

    Chapter 6 Communicate with I/O Guidelines to Manage I/O Connections Use the following guidelines to administer your I/O modules. Table 3 - I/O Connection Guidelines Guideline Description The type of I/O module can determine the type of Analog modules always use direct connections, except for 1771 analog modules that use messaging. connection.
  • Page 77: Control 1771 I/O Modules

    Communicate with I/O Chapter 6 Control 1771 I/O Modules The Logix5000 controllers support the following: • Remote I/O communication to 1771 digital and analog I/O modules • ControlNet communication to 1771 digital I/O modules • Block transfer message instructions via a remote I/O or ControlNet network to 1771 analog and intelligent I/O modules Guideline Description...
  • Page 78: Communicate With Hart Devices

    Chapter 6 Communicate with I/O Communicate with HART HART (Highway Addressable Remote Transmitter) is an open protocol that is designed to connect analog devices in industrial process-measurement Devices applications. The protocol uses the standard 4…20 mA current loop that is widely used for such measurements.
  • Page 79: Communicate With Foundation Fieldbus Devices

    Communicate with I/O Chapter 6 Communicate with FOUNDATION Fieldbus is a communication network that is created by the Fieldbus Foundation. It is a protocol that is designed for distributed control of FOUNDATION Fieldbus process control applications. Devices If your application bridges from Select Description EtherNet/IP...
  • Page 80 Chapter 6 Communicate with I/O Table 4 - Linking Device Guidelines Guideline Description Use either the EtherNet/IP linking device or the Rockwell Automation does not support 1757-FFLDC and 1757-FFLD linking devices communicating with the same HSE ControlNet linking device with an HSE server. server in the same RSFieldbus project.
  • Page 81: Create Tags For I/O Data

    Communicate with I/O Chapter 6 Create Tags for I/O Data Each I/O tag is automatically created when you configure the I/O module through the programming software. Each tag name follows this format: Location:SlotNumber:Type.MemberName.SubMemberName.Bit This address variable Location Identifies network location LOCAL = local chassis or DIN rail ADAPTER_NAME = identifies remote adapter or bridge SlotNumber...
  • Page 82: Controller Ownership

    Chapter 6 Communicate with I/O Controller Ownership When you choose a communication format, you have to choose whether to establish an owner or listen-only relationship with the module. Mode Description Owner The owner controller writes configuration data and can establish a connection to the module. Listen-only A controller that uses a listen-only connection only monitors the module.
  • Page 83: Runtime/Online Addition Of Modules

    Communicate with I/O Chapter 6 Runtime/Online Addition of You can add modules when the controller is in Run mode. Modules RSLogix 5000 Software Support for Online Addition of Modules Version 15 and later Add 1756 I/O modules to the local chassis, remotely via the unscheduled portion of a ControlNet network, and remotely via an EtherNet/IP network.
  • Page 84: Add Modules At Runtime/Online

    Chapter 6 Communicate with I/O Add Modules at Runtime/Online Module Type and In Local Chassis Remote via a ControlNet Network Remote via an Configure Hold Last Connection Method EtherNet/IP Network Output State Offline Runtime Offline Runtime Offline Runtime Offline only Scheduled Unscheduled Scheduled Unscheduled Motion - direct Digital - direct...
  • Page 85: Design Considerations For Runtime/Online Addition

    Communicate with I/O Chapter 6 Design Considerations for Runtime/Online Addition of Modules When you design your network, address these considerations to add modules at runtime. Design Issue Considerations I/O modules When planning to add 1756 I/O modules at runtime, leave space in the local chassis, remote chassis on a ControlNet network, or remote chassis on an EtherNet/IP network for the I/O modules you want to add.
  • Page 86 Chapter 6 Communicate with I/O Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 87: Determine The Appropriate Network

    Chapter Determine the Appropriate Network EtherNet/IP™, ControlNet™, and DeviceNet™ networks share a universal set of communication services. These are the recommended networks for Logix control systems. Comparison EtherNet/IP Network ControlNet Network DeviceNet Network Function Plant management system tie-in Supports transmission of time critical Connects low-level devices directly to (material handling);...
  • Page 88: Ethernet/Ip Network Topology

    Chapter 7 Determine the Appropriate Network EtherNet/IP Network Topology EtherNet/IP Network Topology • An EtherNet/IP network supports messaging, produced and consumed tags, and distributed I/O Star • An EtherNet/IP network supports half-duplex/full-duplex, 10 Mbps or 100 Mbps operation • An EtherNet/IP network requires no network scheduling •...
  • Page 89: Guidelines For Ethernet/Ip Networks

    Determine the Appropriate Network Chapter 7 Guidelines for EtherNet/IP Networks Guideline Description Use these publications. • EtherNet/IP Network Configuration User Manual, publication ENET-UM001 • EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005 • EtherNet/IP Design Considerations Reference Manual, publication ENET-RM002 Make sure that the switch has the required features.
  • Page 90: Guidelines For Switches In Ethernet/Ip Systems

    Chapter 7 Determine the Appropriate Network Guidelines for Switches in EtherNet/IP Systems Use a Managed Switch Use an Unmanaged Switch • The EtherNet/IP control system is directly connected to the business system via a In I/O Systems—Only in These Cases switch or router.
  • Page 91: Stratix Industrial Switches

    • Optimized for the plant floor • Engineer friendly – Logix-based configuration, Logix-based tags, and FactoryTalk View faceplates Embedded technology • Two Ethernet ports that are embedded in Allen-Bradley products • Enables high-speed ring and linear topologies • No configuration required •...
  • Page 92: Guidelines For Controlnet Networks

    Chapter 7 Determine the Appropriate Network Guidelines for ControlNet Networks Guideline Description Use these publications. • ControlNet Coax Media Planning and Installation Guide, publication CNET-IN002 • ControlNet Fiber Media Planning and Installation Guide, publication CNET-IN001 • ControlNet Network Configuration User Manual, publication CNET-UM001 Adjust the default RSNetWorx for ControlNet settings.
  • Page 93: Guidelines For Unscheduled Controlnet Networks

    Determine the Appropriate Network Chapter 7 Guidelines for Unscheduled ControlNet Networks Guideline Description You can run an entire ControlNet network as unscheduled. An unscheduled ControlNet network: • provides for easier network configuration. • is useful if your I/O updates needs are slower. •...
  • Page 94: Compare Scheduled And Unscheduled Controlnet Communication

    Chapter 7 Determine the Appropriate Network Compare Scheduled and Unscheduled ControlNet Communication Scheduled ControlNet Communication Unscheduled ControlNet Communication Deterministic Less deterministic than scheduled communication Provides simpler ControlNet installations when scheduled networks are not required To add scheduled I/O on the ControlNet network, you must: Can be changed online without impacting the schedule •...
  • Page 95: Guidelines For Devicenet Networks

    Determine the Appropriate Network Chapter 7 Guidelines for DeviceNet Networks Guideline Description Use these publications. • DeviceNet Cable System Manual, publication DNET-UM072 • DeviceNet Network Configuration User Manual, publication DNET-UM004 Use the DeviceNet Tag Generator tool. The Logix Designer application includes a DeviceNet tag generator tool that creates device-specific structured tags and logic based on the network configuration in RSNetWorx for DeviceNet software.
  • Page 96 Chapter 7 Determine the Appropriate Network Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 97: Communicate With Other Devices

    Chapter Communicate with Other Devices The MSG instruction asynchronously reads or writes a block of data to another device. If the target device is a Select one of these message types Logix5000 controller CIP Data Table Read CIP Data Table Write I/O module that you configure with the Logix Designer Module Reconfigure application...
  • Page 98: Cache Messages

    Chapter 8 Communicate with Other Devices Cache Messages Some types of messages use a connection to send or receive data. Some also give you the option to either leave the connection open (cache) or close the connection when the message is done transmitting. This table shows messages that use a connection and whether you can cache the connection.
  • Page 99: Outgoing Unconnected Buffers

    Communicate with Other Devices Chapter 8 Table 5 - Message Buffer Guidelines Buffer Description Ten outgoing unconnected buffers The outgoing unconnected buffers are for: (20 on 1756-L7x controllers) • Establishing I/O connections to local I/O modules and remote devices on ControlNet, EtherNet/IP, and remote I/O networks.
  • Page 100: Guidelines For Messages

    Chapter 8 Communicate with Other Devices Guidelines for Messages Guideline Description Message tags must exist as controller-scoped, base tags. The operating system accesses the information in a message tag asynchronously to the program scan. Along with the visible fields within the message tag, there are hidden attributes that are only referenced by the background operating system.
  • Page 101: Guidelines For Block Transfer Messages

    Communicate with Other Devices Chapter 8 Guidelines for Block Transfer Messages Guideline Description Distribute 1771 analog modules across multiple chassis. Distributing 1771 analog modules across multiple chassis reduces the number of block transfers that one 1771-ACN or 1771-ASB module manages. Isolate different 1771 chassis on different networks.
  • Page 102 Chapter 8 Communicate with Other Devices Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 103: Factorytalk Alarms And Events System

    Chapter FactoryTalk Alarms and Events System The FactoryTalk® Alarms and Events system integrates alarming between FactoryTalk View SE applications and Logix5000 controllers by embedding an alarming engine in Logix5000 controllers. You need the following tools: • Logix Designer application, version 21 or later (or RSLogix 5000 software, version 16 or later) •...
  • Page 104: Changes In Logic

    Chapter 9 FactoryTalk Alarms and Events System Guideline Description In relay ladder, how you define the alarm values on the When you create an alarm instruction, you also create an alarm data type for that alarm. For example, MyDigitalAlarm of instruction determines whether you can access those data type DigitalAlarm.
  • Page 105: Configure Logix-Based Alarm Instructions

    FactoryTalk Alarms and Events System Chapter 9 Configure Logix-based Alarm Instructions Option Description Message string The message string (maximum of 255 characters, including embedded text) contains the information to display to the operator regarding the alarm. Besides entering text, you can also embed variable information. In the alarm message editor, select the variable that you want and add it anywhere in the message string.
  • Page 106: Multiple Language Versions Of Alarm Messages

    Chapter 9 FactoryTalk Alarms and Events System Multiple Language Versions of Alarm Messages You can maintain alarm messages in multiple languages. Either enter the different languages in the associated language versions of the Logix Designer application or in an import/export (.CSV or .TXT) file. You can access alarm message text from an import/export (.CSV or .TXT) file and add additional lines for translated versions of the original message string.
  • Page 107: Alarm Process

    FactoryTalk Alarms and Events System Chapter 9 Alarm Process At powerup of the alarm system, the alarm uses this process to establish its initial connection to the controller. 1. The RSLinx Enterprise server initiates a subscription to the alarm log. One subscription to the alarm log consumes 2 KB of controller memory.
  • Page 108: Alarm Log

    Chapter 9 FactoryTalk Alarms and Events System Alarm Log The alarm log holds 10,000 alarm state transitions in a circular log. This replaces the alarm buffer in controllers with firmware earlier than revision 21. The original 100 KB alarm buffer is now a 2 KB subscription service with no timeouts.
  • Page 109: Shelve, Suppress, Or Disable Alarms

    FactoryTalk Alarms and Events System Chapter 9 To perform global alarm operations, access the alarm elements via the relay ladder instructions. For example, assign a BOOL tag DisableToolA to all the ProgDisable fields on the alarm relay ladder faceplates in ToolA. Then use the DisableToolA tag to disable the operation of all the alarms that use this tag.
  • Page 110 Chapter 9 FactoryTalk Alarms and Events System Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 111: Hmi Implementation Option

    Chapter Optimize an Application for Use with HMI Rockwell Automation offers these HMI (human machine interface) platforms. Platform Description PanelView™ Plus terminal Dedicated, machine-level HMI running FactoryTalk View Machine Edition software FactoryTalk View software Product family that consists of: • FactoryTalk View ME (Machine Edition) software for an open, machine-level HMI; also runs on PanelView Plus terminals •...
  • Page 112: Compare Factorytalk View Site Edition And Rsview32 Software

    Chapter 10 Optimize an Application for Use with HMI Compare FactoryTalk View Site Edition and RSView32 Software HMI Product Benefits Considerations FactoryTalk View Site Edition • Supports Windows 2000, Windows XP, Windows 2003. Windows • Does not support Windows NT operating system Vista, and Windows 2008 operating systems •...
  • Page 113: How Rslinx Software Communicates With Logix5000 Controllers

    Optimize an Application for Use with HMI Chapter 10 How RSLinx Software RSLinx software acts as a data server to optimize communication to HMI applications. RSLinx software groups data items into one network packet to Communicates with reduce: Logix5000 Controllers •...
  • Page 114: Compare Rslinx Classic And Rslinx Enterprise Software

    Chapter 10 Optimize an Application for Use with HMI Compare RSLinx Classic and RSLinx Enterprise Software Comparison RSLinx Classic (RSLinx 2.x) Software RSLinx Enterprise Software Supported platforms • Windows 2000 • Windows CE • Windows XP • Windows 2000 • Windows Server 2003 •...
  • Page 115: Guidelines To Configure Controller Tags

    Optimize an Application for Use with HMI Chapter 10 Guidelines to Configure Controller Tags Guideline Description Use INT data types with third-party products. Most third-party operator interface products do not support DINT (32-bit) data types. However, there are additional performance and memory-use considerations when you use INT data types. See Guidelines for Data Types on page FactoryTalk View software supports native Logix5000 data types (including BOOL, SINT, INT, DINT, and REAL), structures, and arrays.
  • Page 116 Chapter 10 Optimize an Application for Use with HMI Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 117: Guidelines For Equipment Phases

    Chapter Develop Equipment Phases The PhaseManager™ option of the Logix Designer application gives you a state model for your equipment. It includes the following components: • Phase to run the state model • Equipment phase instructions for programming the phase •...
  • Page 118: Equipment Phase Instructions

    Chapter 11 Develop Equipment Phases Equipment Phase The equipment phase instructions are available in relay ladder and structured text programming languages. You can use them in relay ladder routines, structured Instructions text routines, and SFC actions. If you want to Use this instruction Signal a phase that the state routine is complete so go to the next state Phase State Complete (PSC)
  • Page 119: Guidelines To Manage Controller Firmware

    Chapter Manage Firmware The Logix controllers, I/O modules, and other devices use firmware that you can update on your own. You choose the firmware revision level and decide when to update the firmware. Guidelines to Manage Controller Firmware Guideline Description Maintain software versions and firmware revisions at the At release, a specific version of software supports the features and functions in a specific revision of firmware.
  • Page 120: Compare Firmware Options

    Chapter 12 Manage Firmware Compare Firmware Options Controllers ship with basic firmware that supports only updating the controller firmware to the required revision. You must update the firmware to a revision that is compatible with your version of the Logix Designer application. ControlFLASH Software AutoFlash Function Controller-based Firmware Supervisor...
  • Page 121 Manage Firmware Chapter 12 Guideline Description The firmware supervisor can update any Rockwell The firmware supervisor works on local I/O modules and distributed modules via EtherNet/IP, SERCOS, and ControlNet Automation device that: networks. On DeviceNet networks, the firmware supervisor supports local devices only, such as scanners and linking •...
  • Page 122: Access Firmware

    Chapter 12 Manage Firmware Guideline Description You can monitor the status of automatic firmware Monitor the status of automatic firmware updates on the Nonvolatile Memory tab on the controller properties. updates. To monitor the status of automatic firmware updates for a specific module, use GSV instructions. This example shows that the firmware supervisor encountered the wrong hardware revision for 1756-OB16D module.
  • Page 123: Rockwell Automation Publication 1756-Rm094I-En-P - September

    Glossary The following terms and abbreviations are used throughout this manual. For definitions of terms that are not listed here, refer to the Allen-Bradley Industrial Automation Glossary, publication AG-7.1. Add-On Instruction An Add-On Instruction is a user-defined instruction that encapsulates executable logic and data.
  • Page 124 Glossary controller scope Data accessible anywhere in the controller. The controller contains a collection of tags that can be referenced by the routines and alias tags in any program, as well as other aliases in the controller scope. program scope. direct connection A direct connection is a real-time, data transfer link between the controller and an I/O module.
  • Page 125 Glossary index A reference used to specify an element within an array. local connection A connection to a module in a local chassis, extended-local chassis, or any of the I/O banks configured for the controller. Communication occurs across the backplane or virtual backplane and does not require an additional communication module or adapter.
  • Page 126 Glossary product-defined data type A structure data type that is automatically defined by the software and controller. By configuring an I/O module, you add the product-defined data type for that module. program A set of related routines and tags. Each program contains program tags, a main executable routine, other routines, and an optional fault routine.
  • Page 127 Glossary software version The product ID label of a software products identifies the software version. This version denotes the functional version of the software. The software version is usually two numbers separated by a period. For example, in software version 10.02, the first number (10) defines the major revision and the second number (02) defines the minor revision.
  • Page 128 Glossary user-defined data type (UDT) A UDT is a data structure you define. A user-defined data type groups different types of data into a single named entity. You define the members of the user- defined data type. Like tags, the members have a name and data type. virtual communication relationship A VCR is a channel that provides for the transfer of data between (VCR)
  • Page 129 Index comparison HMI software 112 access import/export, add-on instructions 50 firmware 122 program parameters, add-on instructions 52 module object 33 programming languages 34 Access the Module Object 33 scheduled and unscheduled ControlNet 94 add-on instruction subroutines, add-on instructions 49 compound data types 53 guidelines 48 postscan logic 37 configuration...
  • Page 130 Index estimate logic controller memory 16 routine application code 34 EtherNet/IP network Logix5000 controller guidelines 89 resources 14 switches 90 Logix-based topology 88 alarm event configuration 105 task 26 instruction guidelines 103 configuration 30 considerations 30 consumed tag 69 guidelines 30 manage executable code firmware updates 119...
  • Page 131 Index priority level system overhead task 25 manage timeslice 32 produced and consumed timeslice 31 RPI 68 tag guidelines 67 tags 67 program table considerations 24 mapping 101 languages comparison 34 methods 35 configuration 62 routines, tags 23 controller-scoped 113 -scoped tags 113 descriptions 66 project...
  • Page 132 Index Notes: Rockwell Automation Publication 1756-RM094I-EN-P - September 2015...
  • Page 133 AB Drives...
  • Page 134 Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. http://www.rockwellautomation.com/support you can find technical and application notes, sample code, and links to software service packs. You can also visit our Support Center at https://rockwellautomation.custhelp.com/ for software updates, support chats and forums, technical information, FAQs, and to sign up for product notification updates.

Table of Contents