Allen-Bradley 1756-L61 ControlLogix 5561 User Manual

40 Rockwell Automation Publication 1756-PM004D-EN-P - September 2012
Chapter 2 Organizing Tags
Guidelines for User-defined Data Types
When you create a user-defined data type, use these guidelines:
· If you include members that represent I/O devices, you must use logic to
copy the data between the members in the structure and the corresponding
I/O tags. Refer to “Address I/O Data”
on page 19.
· If you include an array as a member, limit the array to a single dimension.
Multi-dimension arrays are not permitted in a user-defined data type.
EXAMPLE
User-defined data type that stores the data that is required to run a machine.
Because several drill stations require the following mix of data, use a user-defined data type.
ATTENTION: An array that is based on this data type looks like this example.
Name (of data type): DRILL_STATION
Member Name Data Type
Part_advance BOOL
Hole_sequence CONTROL
Type DINT
Hole_position REAL
Depth REAL
Total_depth REAL
42583
Array of Drills
First Drill
This array contains four
elements of the
DRILL_STATION
data type.
Data for the Drill

Allen-Bradley 1756-L61 ControlLogix 5561 Specifications

General

Series	ControlLogix
Controller redundancy	Yes
Battery Life	5 years
Relative Humidity	5 to 95% non-condensing
Shock	30 g
Vibration	2 g
I/O Capacity	128, 000 I/O
I/O Capacity (digital)	128, 000 I/O
Communication Ports	ControlNet, DeviceNet
Approx. shipping weight	2.5 kg
Operating Temperature	0 to 60 °C (32 to 140 °F)
Certifications	CE, UL, cUL, C-Tick

Summary

Chapter 1 Communicate with I/O Modules

Requested Packet Interval

Defines RPI and how it affects I/O data updates, updating asynchronously to logic.

Electronic Keying

Compares expected module to physical module before communication, preventing mismatches.

Chapter 2 Organizing Tags

Scope

Defines tags as controller (global) or program (local) scoped for data organization.

Creating a User-defined Data Type

User-defined data types (structures) allow custom data organization matching machine or process needs.

Alias Tags

Chapter 3 Force I/O

Precautions

Emphasizes safety risks of forcing, like unexpected machine motion, and personnel safety.

Enable Forces

Add an I/O Force

Remove or Disable Forces

Chapter 4 Data Access Control

External Access

Controls how external applications (HMIs, software) access tags (Read/Write, Read Only, None).

Configure External Access

Constant Value Tags

Designating tags as constants to protect them from programmatic changes.

Configure Constant Tags