Rockwell Automation 1794-L34 User Manual

FlexLogix Controller System User Manual

1794-L34

Firmware Revision 16

User Manual

Important User Information

Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

) describes some important

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

WARNING

Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

IMPORTANT

Identifies information that is critical for successful application and understanding of the product.

ATTENTION

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you to identify a hazard, avoid a hazard, and recognize the consequences.

SHOCK HAZARD

Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD

Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may be dangerous temperatures.

Allen-Bradley, FlexLogix, Logix5000, RSLogix, RSLogix 5000, Rockwell Automation, RSNetWorx, and RSLinx are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

Summary of Changes

Developing FlexLogix Controller Systems

Where to Start

Directly Connect to the Controller via the Serial Port

Important User Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Updated Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preface

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Install Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Connect the Controller via the Serial Port. . . . . . . . . . . . . . . 15

Configure the Serial Driver . . . . . . . . . . . . . . . . . . . . . . . . . 18

Select the Controller Path . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Communicate over Networks

Manage Controller Communications

Chapter 3

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

EtherNet/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Connections over EtherNet/IP . . . . . . . . . . . . . . . . . . . . 24

ControlNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Connections over ControlNet . . . . . . . . . . . . . . . . . . . . . 26

DeviceNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Define Data Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Communicate with DF1 devices . . . . . . . . . . . . . . . . . . . 33

Communicate with ASCII devices . . . . . . . . . . . . . . . . . . 35

Modbus support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

DH-485. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Third Party . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Communication Format . . . . . . . . . . . . . . . . . . . . . . . . . 42

Connection Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 42

Chapter 4

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Produce and Consume (Interlock) Data . . . . . . . . . . . . . . . . 45

Send and Receive Messages. . . . . . . . . . . . . . . . . . . . . . . . . 47

Determine whether to cache message connections . . . . . 47

Connection Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Calculate Connection Use . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Connections Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3 Publication 1794-UM001G-EN-P - January 2007

4 Table of Contents

Place, Configure, and Monitor I/O

Chapter 5

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Select I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Place Local I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Selecting a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . 54

Configure I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

I/O connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Configure Distributed I/O on EtherNet/IP . . . . . . . . . . . . . . 59

Configure Distributed I/O on ControlNet . . . . . . . . . . . . . . . 60

Configure Distributed I/O on DeviceNet . . . . . . . . . . . . . . . 61

Address I/O Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Determine When Data Is Updated . . . . . . . . . . . . . . . . . . . . 63

Monitor I/O Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Displaying fault data . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Monitor a rack-optimized connection . . . . . . . . . . . . . . . 65

Reconfigure an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . 66

Reconfigure a module via RSLogix 5000 software . . . . . . 66

Reconfigure a module via a MSG instruction . . . . . . . . . . 67

Develop Applications

Chapter 6

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Manage Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Develop Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Defining tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Defining programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Defining routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Sample controller projects . . . . . . . . . . . . . . . . . . . . . . . 74

Organize Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Select a Programming Language . . . . . . . . . . . . . . . . . . . . . 76

Add-On Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Monitor Controller Status. . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Monitor Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Determine if communication has timed out with any device

Determine if communication has timed out with a specific

I/O module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Interrupt the execution of logic and execute the fault handler

Select a System Overhead Percentage . . . . . . . . . . . . . . . . . 82

Use the Event Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Prioritizing Periodic and Event Tasks . . . . . . . . . . . . . . . 85

Triggering the Event Task. . . . . . . . . . . . . . . . . . . . . . . . 86

Programmatically Determine if an EVENT Instruction

Triggered a Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Checklist for an EVENT Instruction Task . . . . . . . . . . . . . 87

Publication 1794-UM001G-EN-P - January 2007

Configure PhaseManager

Maintain the Battery

FlexLogix System Status Indicators

FlexLogix Back-Up on DeviceNet

Table of Contents 5

Chapter 7

Use This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

PhaseManager Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

How equipment changes states . . . . . . . . . . . . . . . . . . . 92

Manually change states . . . . . . . . . . . . . . . . . . . . . . . . . 94

Compare PhaseManager to Other State Models. . . . . . . . . . . 94

Minimum System Requirements . . . . . . . . . . . . . . . . . . . . . . 94

Equipment Phase Instructions . . . . . . . . . . . . . . . . . . . . . . . 95

Chapter 8

Using this Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Storing Replacement Batteries . . . . . . . . . . . . . . . . . . . . . . . 97

Estimating Battery Life. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Replacing a Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Appendix A

Controller LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Appendix B

Using This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

How the Back-up Works . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Requirements of the Back-Up. . . . . . . . . . . . . . . . . . . . 105

Power-Up and System Start-up . . . . . . . . . . . . . . . . . . . . . 106

Developing the FlexLogix Back-Up Application . . . . . . . . . 108

Back-up Heartbeat Configuration Rungs . . . . . . . . . . . . 108

Reading Back-up State Rung. . . . . . . . . . . . . . . . . . . . . 112

Reading Back-up Status . . . . . . . . . . . . . . . . . . . . . . . . 114

Using Indicators to Check Status . . . . . . . . . . . . . . . . . . . . 115

Development and Debugging Tips. . . . . . . . . . . . . . . . . . . 115

Instruction Locator Index

Appendix C

Where to Find an Instruction . . . . . . . . . . . . . . . . . . . . . . . 117

Publication 1794-UM001G-EN-P - January 2007

6 Table of Contents

Publication 1794-UM001G-EN-P - January 2007

Summary of Changes

Introduction

Updated Information

This release of this document contains new and updated information. To find new and updated information, look for change bars, as shown next to this paragraph.

The document contains these changes.

Topic Page

DF1 radio modem 31

Add-On Instructions 77

Where to Find an Instruction 117

7 Publication 1794-UM001G-EN-P - January 2007

8 Summary of Changes

Notes:

Publication 1794-UM001G-EN-P - January 2007

Preface

Developing FlexLogix Controller Systems

Introduction

Use this manual to become familiar with the FlexLogix controller and its features. This version of the manual corresponds to controller firmware revision 16.

This manual describes the necessary tasks to install, configure, program, and operate a FlexLogix system. In some cases, this manual includes references to additional documentation that provides the more comprehensive details.

Use This Chapter

1794 I/O modules connected to the FlexLogix controller

The FlexLogix controller offers state-of-art control, communications, and I/O elements in a distributed control package..

FlexLogix controller

For a more flexible system, use:

• multiple controllers joined across networks

• I/O from multiple platforms that is distributed in many locations

and connected over multiple I/O links

network communication cards installed in the controller

EtherNet/IP link

1794 I/O modules connected to the FlexLogix controller

remote I/O modules

drives

}

ControlNet link

EtherNet/IP link

ControlNet link

DeviceNet

computers

other controllers

11 Publication 1794-UM001G-EN-P - January 2007

12 Where to Start

The FlexLogix controller, part of the Logix family of controllers, provides a small, powerful, cost-effective system built on the following components:

• 1794-L34 FlexLogix controller available in 512 Kbytes of user memory.

• FlexLogix controller that supports the Logix instructions.

• RSLogix 5000 programming software that supports every

Logix controller.

• FLEX I/O modules that provide a compact, DIN-rail mounted I/O system.

• 1788 communication daughtercard that provides communication over standard-based ControlNet, DeviceNet or EtherNet/IP networks. The controller allows the insertion of daughtercards for up to 2 networks (e.g., one for DeviceNet and one for EtherNet/IP).

Design

See:

• FlexLogix Selection Guide, 1794-SG001

• Logix5000 Controller Design Considerations Reference Manual,

1756-RM094

When designing a FlexLogix system, determine the network configuration and the placement of components in each location. Make these decisions as you design your system:

Design Step

o 1. o 2. o 3. o 4. o 5.

Select I/O devices

Select communication cards

Select controllers

Select power supplies

Select software

Publication 1794-UM001G-EN-P - January 2007

Where to Start 13

Install Hardware

See:

• FlexLogix Controller Installation

To install a FlexLogix controller, follow these steps:

Installation Step

o 1. o 2. o 3. o 4.

o 5.

o 6. o 7. o 8.

o 9.

Install a DIN rail

Use DIN rail locks that came with your controller

Mount an appropriate power supply on the DIN rail

Install the battery in the controller

See 8 “Maintain the Battery.“

Install the communication cards in the controller

See Chapter 3 “Communicate over Networks”

Install the controller on the DIN rail

Install the extended-local adapter (optional)

Make serial connections

See Chapter 2 “Directly Connect to the Controller via the Serial Port “

Load controller firmware

Publication 1794-UM001G-EN-P - January 2007

14 Where to Start

Notes:

Publication 1794-UM001G-EN-P - January 2007

Chapter

Directly Connect to the Controller via the Serial Port

Use This Chapter

See:

• EtherNet/IP Modules in Logix5000 Control Systems User Manual,

ENET-UM001

• ControlNet Modules in Logix5000 Control System User Manual,

CNET-UM001

• DeviceNet Modules in Logix5000 Control System User Manual,

DNET-UM004

Connect the Controller via the Serial Port

This chapter describes how to connect to the controller via the serial port so you can configure the controller and upload and/or download a project to the controller.

For this information See

Connect the Controller via the Serial Port 15

Configure the Serial Driver 18

Select the Controller Path 20

For the FlexLogix controller to operate on a serial network, you need:

• a workstation with a serial port

• RSLinx software to configure the serial communication driver

• RSLogix5000 programming software to configure the serial port

of the controller

The RS-232 port is a non-isolated serial port built-in to the front of the FlexLogix controller.

1. Determine whether you need an isolator.

If you connect the controller to a modem or an ASCII device, consider installing an isolator between the controller and modem or ASCII device. An isolator is also recommended when connecting the controller directly to a programming workstation.

15 Publication 1794-UM001G-EN-P - January 2007

16 Directly Connect to the Controller via the Serial Port

baud rate selector switch

One possible isolator is the 1761-NET-AIC interface converter.

port 2: mini-DIN 8 RS-232

port 1: DB-9 RS-232, DTE

dc power source selector switch

terminals for external 24V dc power supply

2. Select the appropriate cable.

If you are using an isolator: Use this cable:

yes The 1761-CBL-AP00 cable (right-angle bend connector to controller) or the 1761-CBL-PM02 cable

(straight connector to the controller) attaches the controller to port 2 on the 1761-NET-AIC isolator. The 8-pin mini-DIN connector is not commercially available, so you cannot make this cable.

DB-9 right-angle or straight cable end

Pin: DB-9 end: Mini-DIN end:

1DCD DCD

2 RxD RxD

3TxD TxD

4DTR DTR

5 ground ground

6DSR DSR

7 RTS RTS

8 CTS CTS

9na na

678

8-pin, mini-DIN cable end

Publication 1794-UM001G-EN-P - January 2007

Directly Connect to the Controller via the Serial Port 17

If you are using an isolator: Use this cable:

no The 1756-CP3 cable attaches the controller directly to the RS-232 device.

1 CD

2 RDX

3 TXD

4 DTR

COMMON

6 DSR

7 RTS

8 CTS

straight cable end

1 CD

2 RDX

3 TXD

4 DTR

COMMON

6 DSR

7 RTS

8 CTS

right-angle cable end

If you make your own cable, it must be shielded and the shields must be tied to the metal shell (that surrounds the pins) on both ends of the cable.

You can also use a 1747-CP3 cable from the SLC product family. This cable has a larger right-angle connector than the 1756-CP3 cable.

3. Connect the appropriate cable to the serial port on the

controller.

isolator 1761-NET-AIC

4. If necessary, attach the controller to the isolator.

1761 cable

user-supplied modem cable

modem

24 V dc

Publication 1794-UM001G-EN-P - January 2007

18 Directly Connect to the Controller via the Serial Port

Configure the Serial Driver

ATTENTION

The FlexLogix controller is grounded through its DIN rail. It is important that you understand the workstation’s grounding system before connecting it to the controller. An isolator is

recommended between the controller and the workstation.

Use RSLinx software to configure the RS-232 DF1 Device driver for serial communications. To configure the driver:

1. From the Communications menu in RSLinx software, select

Configure Drivers. Choose the RS-232 DF1 Device driver.

Publication 1794-UM001G-EN-P - January 2007

2. Click Add New to add the driver.

3. Specify the driver name and click OK.

Directly Connect to the Controller via the Serial Port 19

4. Specify the serial port settings:

a. From the Comm Port drop-down list, select the serial port (on

the workstation) that the cable is connected to. b. From the Device drop-down list, select Logix 5550-Serial Port. c. Click Auto-Configure.

5. Does the dialog box display the following message:

Auto Configuration Successful!

If: Then:

Yes Click OK.

No Go to step 4. and verify that you selected the correct Comm Port.

Then click Close.

Publication 1794-UM001G-EN-P - January 2007

20 Directly Connect to the Controller via the Serial Port

Select the Controller Path

In RSLogix 5000 software, select the controller path on the network.

1. Open an RSLogix 5000 project for the controller.

2. From the Communications menu, select Who Active.

3. Expand the communication driver to the level of the controller.

4. Select the controller.

To: Choose:

monitor the project in the controller Go Online

transfer a copy of the project from the controller to RSLogix 5000 software

transfer the open project to the controller Download

You may have to confirm the action.

Upload

Publication 1794-UM001G-EN-P - January 2007

Communicate over Networks

Chapter

Use This Chapter

The FlexLogix controller supports additional networks so that the controller can:

Supported networks for: Example:

Control distributed (remote) I/O

• EtherNet/IP

• ControlNet

• DeviceNet

Produce/consume (interlock) data between controllers

• EtherNet/IP

• ControlNet

FlexLogix controller

control network

distributed (remote) I/O platform

FlexLogix controller

control network

other Logix5000 controller

Send and receive messages to and from other devices (this includes access to the controller via RSLogix 5000 programming software)

• EtherNet/IP

• ControlNet

• DeviceNet (to devices only)

• serial

• DH-485

21 Publication 1794-UM001G-EN-P - January 2007

control network

FlexLogix controller

other remote devices

22 Communicate over Networks

This chapter summarizes the FlexLogix controller’s communications capabilities:

For this information: See:

EtherNet/IP 22

ControlNet 25

DeviceNet 28

Serial 31

DH-485 39

Third Party 42

EtherNet/IP

See:

• EtherNet/IP Modules in Logix5000 Control Systems User Manual,

ENET-UM001

• EtherNet/IP Web Server Module User Manual, ENET-UM527

• EtherNet/IP Performance Application Guide, ENET-AP001

• Logix5000 Controllers Design Considerations Reference Manual,

1756-RM094

• EtherNet/IP Daughtercard Installation Instructions,

1788-IN054

For EtherNet/IP communications, install a 1788-ENBT communication card in your FlexLogix controller.

Use these software products when you use a FlexLogix controller on EtherNet/IP:

Software Use Required/optional

RSLogix 5000 programming software

Use this to configure the FlexLogix project and define EtherNet/IP communications.

BOOTP/DHCP Utility

This utility comes with RSLogix 5000 software. Use this utility to assign IP addresses to devices on an EtherNet/IP network.

RSNetWorx for EtherNet/IP Use this software to

configure EtherNet/IP devices by IP addresses and/or host names.

Required

Optional

Publication 1794-UM001G-EN-P - January 2007

Communicate over Networks 23

The EtherNet/IP communication modules:

• support messaging, produced/consumed tags, HMI, and distributed I/O

• encapsulate messages within standard TCP/UDP/IP protocol

• share a common application layer with ControlNet and

DeviceNet

• interface via RJ45, category 5, unshielded, twisted-pair cable

• support half/full duplex 10 Mbps or 100 Mbps operation

• support standard switches

• require no network scheduling

• require no routing tables

In this example:

• The controllers can produce and consume tags among each other.

• The controllers can initiate MSG instructions that send/receive data or configure devices.

• The personal computer can upload/download projects to the controllers.

• The personal computer can configure devices on EtherNet/IP.

CompactLogix controller with integrated EtherNet/IP port

PowerFlex 700S AC drive with DriveLogix

FlexLogix controller with 1788-ENBT card

ControlLogix controller with 1756-ENBT module

switch

workstation

Distributed I/O

1756-ENBT module (as an adapter) with 1756 I/O modules

1794-AENT adapter with 1794 I/O modules

1734-AENT adapter with 1734 I/O modules

Publication 1794-UM001G-EN-P - January 2007

24 Communicate over Networks

Connections over EtherNet/IP

You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system. Connections are allocations of resources that provide more reliable communications between devices than unconnected messages.

All EtherNet/IP connections are unscheduled. An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval (RPI) or the program (such as a MSG instruction). Unscheduled messaging lets you send and receive data when needed.

The 1788-ENBT card supports 32 CIP connections over an EtherNet/IP network. With these controllers, the number of end-node connections they effectively support is dependent on the RPI of the connection:

If the RPI is: The EtherNet/IP card effectively

supports a maximum of this many communication connections:

2 ms 2

For more information...

4 ms 5

8 ms 10

16 ms 18

32 ms + 25

In the table above, with an RPI of 32 ms and greater, the EtherNet/IP card effectively supports 25 communications connections. In this case, the remaining 7 connections can be used for non-I/O purposes.

The EtherNet/IP Modules in Logix5000 Control Systems User Manual, ENET-UM001 provides information on how to:

• configure an EtherNet/IP communication module

• control I/O over EtherNet/IP

• send a message over EtherNet/IP

• produce/consume a tag over EtherNet/IP

• monitor diagnostics

• calculate controller connections over EtherNet/IP

The Logix5000 Controllers Design Guidelines Reference Manual, 1756-RM094 provides guidelines on optimizing a control application on an EtherNet/IP network.

Publication 1794-UM001G-EN-P - January 2007

Communicate over Networks 25

ControlNet

See:

• ControlNet Modules in Logix5000 Control Systems User Manual,

CNET-UM001

• Logix5000 Controllers Design Considerations Reference Manual,

1756-RM094

• ControlNet Daughtercard Installation Instructions,

1788-IN002

• ControlNet Daughtercard Installation Instructions,

For ControlNet communications, install a ControlNet communication card in your FlexLogix controller:

If you are using Use this card

fiber media 1788-CNF, 1788-CNFR

coaxial media 1788-CNC, 1788-CNCR

Use these software products when you use a FlexLogix controller on ControlNet:

Software Use Required/optional

RSLogix 5000 programming software

RSLinx Use this software to

RSNetWorx for ControlNet Use this software to

Use this to configure the FlexLogix project and define ControlNet communications.

configure the ControlNet communication driver.

configure the ControlNet network, define the NUT (Network update time), and schedule the ControlNet network.

Required

The ControlNet communications modules:

• support messaging, produced/consumed tags and distributed I/O

• share a common application layer with DeviceNet and EtherNet/IP

• require no routing tables

• support the use of coax and fiber repeaters for isolation and

increased distance

Publication 1794-UM001G-EN-P - January 2007

26 Communicate over Networks

In this example:

• The controllers can produce and consume tags among each other.

• The controllers can initiate MSG instructions that send/receive data or configure devices.

• The personal computer can upload/download projects to the controllers.

• The personal computer can configure devices on ControlNet, and it can configure the network itself.

personal computer/workstation

CompactLogix controller with built-in Control port

FlexLogix controller with 1788-CNC card

PowerFlex 700S drive

ControlNet

PLC-5/40C controller

PanelView terminal

Distributed I/O

1756-CNB module (as an adapter) with 1756 I/O modules

1794-ACN15 adapter with 1794 I/O modules

1734-ACNR adapter with 1734 I/O modules

Publication 1794-UM001G-EN-P - January 2007

Connections over ControlNet

more reliable communications between devices compared to unconnected messages.

ControlNet connections can be:

Connection method: Description:

Communicate over Networks 27

scheduled

(unique to ControlNet)

unscheduled An unscheduled connection is a message transfer between controllers that is triggered by

A scheduled connection is unique to ControlNet communications. A scheduled connection lets you send and receive data repeatedly at a predetermined interval, which is the requested packet interval (RPI). For example, a connection to an I/O module is a scheduled connection because you repeatedly receive data from the module at a specified interval. Other scheduled connections include connections to:

• communication devices

• produced/consumed tags

On a ControlNet network, you must use RSNetWorx for ControlNet to enable all scheduled connections and establish a network update time (NUT). Scheduling a connection reserves network bandwidth to specifically handle the connection.

ladder logic or the program (such as a MSG instruction). Unscheduled messaging lets you send and receive data when needed. Unscheduled messages use the remainder of network bandwidth after scheduled connections are allocated.

The FlexLogix controller supports 100 connections. However, the controller is limited by the number of connections each ControlNet communication card supports. The 1788-CNx cards support 32 total ControlNet connections, 22 of which can be scheduled and used for producing and consuming tags. With these controllers, the number of end-node connections they effectively support is dependent on the application’s NUT and RPI:

If the NUT and RPI are each: The controllers effectively support this

many communication connections

5 ms 3

10 ms 6

20 ms 13

40 ms + 22

In the table above, with a NUT and RPI of 40 ms and greater, the ControlNet card supports 22 communications connections. In this case, the remaining 10 connections can be used for unscheduled connections.

Publication 1794-UM001G-EN-P - January 2007

28 Communicate over Networks

For more information...

DeviceNet

See:

• DeviceNet Modules in Logix5000 Control Systems User Manual,

DNET-UM004

• Logix5000 Controllers Design Considerations Reference Manual,

1756-RM094

• DeviceNet Daughtercard

The ControlNet Modules in Logix5000 Control Systems User Manual, CNET-UM001 provides information on how to:

• configure a ControNet communication module

• control I/O over ControlNet

• send a message over ControlNet

• produce/consume a tag over ControlNet

• calculate controller connections over ControlNet

The Logix5000 Controllers Design Guidelines Reference Manual, 1756-RM094 provides guidelines on optimizing a control application on a ControlNet network.

The DeviceNet network uses the Common Industrial Protocol (CIP) to provide the control, configuration, and data collection capabilities for industrial devices.

For DeviceNet communications, install a 1788-DNBO communication card in your FlexLogix controller.

FlexLogix system with 1788-DNBO card

PanelView terminal

CompactLogix controller with 1769-SDN

laptop

Ultra 5000 servo drive

PLC-5 controller with 1771-SDN scanner module

DeviceNet network

motor starter

input/output devices

PowerFlex ac drive

sensor

indicator lights

ControlLogix controller with 1756-DNB module

pushbutton cluster

bar code scanner

Publication 1794-UM001G-EN-P - January 2007

Communicate over Networks 29

Use these software products when you use a FlexLogix controller on DeviceNet:

Software Use Required/optional

RSLogix 5000 programming software

Use this to configure the FlexLogix project and define

Required

DeviceNet communications.

RSNetWorx for DeviceNet Use this software to

Required configure DeviceNet devices and define the scan list for those devices.

The DeviceNet communications module:

• supports messaging to devices (not controller to controller)

• shares a common application layer with ControlNet and

EtherNet/IP

• offers diagnostics for improved data collection and fault detection

• requires less wiring than traditional, hardwired systems

personal computer

FlexLogix system with a 1788-DNBO card

You can use a linking device as a:

• gateway to connect information- or control-level networks to device-level networks for programming, configuration, control or data collection

• router/bridge to connect the EtherNet/IP or ControlNet network to the DeviceNet network

ControlLogix controller with 1756-ENBT module

EtherNet/IP network

FlexLogix controller

FLEX adapter and I/O

linking devices

DeviceNet network

sensor

motor starter

with a 1788-ENBT card

pushbutton cluster

input/output devices

PowerFlex ac drive

bar code

indicator lights

Publication 1794-UM001G-EN-P - January 2007

scanner

30 Communicate over Networks

Define Data Blocks

How you configure the DeviceNet devices determines how many words you use per device. The 1788-DNBO card supports a maximum of:

• 124 32-bit words of input data

• 123 32-bit words of output data

• 32 32-bit words of status data

Most DeviceNet devices support 16-bit words. Take care how you map these into the 32-bit words used in RSLogix 5000 programming software. RSNetWorx for DeviceNet lets you DINT-align the device data. While this might simplify the organization of the data, it might also limit the data you have available.

For more information...

The DeviceNet Modules in Logix5000 Control Systems User Manual, DNET-UM004 provides information on how to:

• configure DeviceNet communication module

• control devices on DeviceNet

The Logix5000 Controllers Design Guidelines Reference Manual, 1756-RM094 provides guidelines on optimizing a control application on a DeviceNet network.

Publication 1794-UM001G-EN-P - January 2007

+ 100 hidden pages