Rockwell Automation 1747-SCNR User Manual

ControlNet Scanner

1747-SCNR

Reference Manual

Important User Information

SHOCK HAZARD

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/) describes some important 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.

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

WARNING

IMPORTANT

ATTENTION

BURN HAZARD

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.

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

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

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

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

Allen-Bradley, FLEX I/O, RSLinx, RSLogix 500, RSNetWorx, SLC, and SLC 500 are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.

Summary of Changes

This publication contains new and revised information not in the last release.

New and Revised Information

See the table for a summary of the major additions in this manual.

For See Page

An explanation of the processor and firmware levels that include the ControlNet explicit message instruction capability

New information about the ControlNet explicit message instruction that uses the CIP client management capability of module

Other changes in this manual provide an update or clarification of th e material.

2-12

4-1

Change Bars

Change bars (as shown with this paragraph) show the areas in this manual that are different from previous editions and indicate the addition of new or revised information.

1 Publication 1747-RM623D-EN-P - June 2006

2 Summary of Changes

Notes:

Publication 1747-RM623D-EN-P - June 2006

Preface

Install and Connect the ControlNet Scanner

Prepare to Use the ControlNet Scanner

What This Manual Contains. . . . . . . . . . . . . . . . . . . . . . . . P-1

Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . P-1

Common Techniques Used in This Manual. . . . . . . . . . . . . P-1

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2

Chapter 1

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 1-1

Identify Scanner Features . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Prepare for Module Installation . . . . . . . . . . . . . . . . . . . . . 1-2

Select the ControlNet Node Address. . . . . . . . . . . . . . . . . . 1-3

Insert the 1747-SCNR Scanner Into the Chassis . . . . . . . . . . 1-3

Connect to a ControlNet Network . . . . . . . . . . . . . . . . . . . 1-5

Connect Programming Terminal to ControlNet Network 1-6

SLC 500 I/O Configuration for the 1747-SCNR Module . . . . 1-8

Chapter 2

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 2-1

What Your Scanner Does . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Communicate with Your SLC Processor . . . . . . . . . . . . . . . 2-1

Communicating with Your SLC processor Using M1

and M0 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Understand ControlNet Data transfer . . . . . . . . . . . . . . . . . 2-3

Scheduled Data Transfer Operations on a ControlNet

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Unscheduled Data Transfer Operations on a ControlNet

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Link Layer Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Understand 1747-SCNR Mapping . . . . . . . . . . . . . . . . . . . . 2-5

Discrete Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

1747-SCNR M1 File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Discrete Output File. . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

1747-SCNR M0 File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Communicate with Your Devices. . . . . . . . . . . . . . . . . . . . 2-9

I/O Scheduled Data Transfer . . . . . . . . . . . . . . . . . . . . 2-9

Unscheduled Data Server . . . . . . . . . . . . . . . . . . . . . . . 2-10

CIP Client Request Transfer . . . . . . . . . . . . . . . . . . . . . 2-10

Configure and Map Scheduled Data Exchange with RSNetWorx for ControlNet Software

3 Publication 1747-RM623D-EN-P - June 2006

Chapter 3

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 3-1

Begin the Configuration Process . . . . . . . . . . . . . . . . . . . . 3-1

Questions to Ask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Data Transfer Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Table of Contents 4

Work with the ControlNet Explicit Message Instruction

Chapter 4

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 4-1

Understand the ControlNet Explicit Message Instruction . . 4-1

Work with the Explicit Message Instruction (CEM) . . . . . . . 4-2

CEM Instruction Parameters . . . . . . . . . . . . . . . . . . . . . . 4-2

CEM Instruction Setup Screen Parameters . . . . . . . . . . . . 4-3

Troubleshoot Chapter 5

What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . 5-1

Troubleshoot with the Status Indicators and

Status Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Apply Chassis Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Alphanumeric Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

OK Indicator and Display Mnemonics . . . . . . . . . . . . . . . . 5-3

Local Database Access Using PLC-5 MSG Instructions

Appendix A

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . A-1

What We Assume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Read and Write Access To 1747-SCNR Local Database

Using PLC-5 MSG Instruction. . . . . . . . . . . . . . . . . . . . . . . A-1

Use CIP Messaging to Access Local Database and ControlNet Data Files Access

Appendix B

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . B-1

What We Assume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Read and Write Access to 1747-SCNR Data Files Using

Assembly Object Services . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Assembly Object Instance Numbers Supported for Get

and Set Member on Data Attribute . . . . . . . . . . . . . . . . B-2

1747-SCNR Memory Layout . . . . . . . . . . . . . . . . . . . . . . . . B-3

Publication 1747-RM623D-EN-P - June 2006

CIP Client Management Appendix C

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . C-1

What We Assume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

CIP Client Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Send a Get Attribute All Request to Node 14 Identity Object C-4

SLC 500 Processor: N7 Data File (hex) . . . . . . . . . . . . . C-5

SLC 500 Ladder Program . . . . . . . . . . . . . . . . . . . . . . . C-6

SLC 500 Processor: Data Files (hex) . . . . . . . . . . . . . . . C-7

Send a Set Attribute Single Request . . . . . . . . . . . . . . . . . . C-8

SLC 500 Processor: N7 Data File (hex) . . . . . . . . . . . . . C-9

Example: SLC 500 Ladder Program . . . . . . . . . . . C-10

SLC 500 Processor: Target Input Data File (hex) . C-11

Send a Set Member Request. . . . . . . . . . . . . . . . . . . . . . . C-12

SLC 500 Processor: N7 Data File (hex) . . . . . . . . . . . . C-13

Example: SLC 500 Ladder Program . . . . . . . . . . . C-14

SLC 500 Processor: Target Input Data File (hex) . C-15

Example of Reset Bit Management Appendix D

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . D-1

What We Assume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Table of Contents 5

Publication 1747-RM623D-EN-P - June 2006

Table of Contents 6

Application Examples Appendix E

What This Appendix Contains . . . . . . . . . . . . . . . . . . . . . . E-1

What We Assume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Example 1: Configure the 1747-SCNR Scanner with the

1746-IV16 Input Module . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Configure the ControlNet Network with RSNetWorx

for ControlNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Example 2: Configure the 1747-SCNR Scanner with the

1746-NIO4V Analog Input/Output Module. . . . . . . . . . . . . E-9

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-9

Configure the ControlNet Network with RSNetWorx

for ControlNe Software. . . . . . . . . . . . . . . . . . . . . . . . . E-9

Configure a Module Connection. . . . . . . . . . . . . . . . . E-16

Example 3: Configure the 1747-SCNR Scanner with the

1746-NI8 Analog Input Module . . . . . . . . . . . . . . . . . . . . E-19

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-19

Configure the ControlNet Network with RSNetWorx

for ControlNet Software . . . . . . . . . . . . . . . . . . . . . . . E-19

Configure a Module Connection. . . . . . . . . . . . . . . . . E-25

Example 4: Configure the 1747-SCNR Scanner with the 1746-BAS

Series B Interface Module . . . . . . . . . . . . . . . . . . . . . . . . E-28

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-28

Configure the ControlNet Network with RSNetWorx

for ControlNet Software . . . . . . . . . . . . . . . . . . . . . . . E-28

Configure a Module Connection. . . . . . . . . . . . . . . . . E-34

Example 5: Configure the 1747-SCNR Scanner with the

1794-IE4XOE2 Analog Combo Module. . . . . . . . . . . . . . . E-41

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-42

Configure the ControlNet Network with RSNetWorx

for ControlNet Software . . . . . . . . . . . . . . . . . . . . . . . E-42

Configure a Module Connection. . . . . . . . . . . . . . . . . E-48

Example 6: Creating Peer-to-Peer Scheduled Connections

Between 1747-SCNR ControlNet Scanners . . . . . . . . . . . . E-51

Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-51

Configure the ControlNet Network with RSNetWorx

for ControlNet Software . . . . . . . . . . . . . . . . . . . . . . . E-52

Configure a Scheduled Connection Between

ControlNet Scanners. . . . . . . . . . . . . . . . . . . . . . . . . . E-54

Publication 1747-RM623D-EN-P - June 2006

Preface

What This Manual Contains

Who Should Use This Manual

Use this manual to install, configure, and apply the features of the scanner. See the table for a list of where to find specific information. For specification and hazardous locations i nformation, refer to SLC ControlNet Scanner Installation Instructions, publication 1747-IN059.

For Information About See

How to install and connect the module Chapter 1 How to prepare to install the module Chapter 2 How to configure and map scheduled data exchange using RSNetWorx for

ControlNet software How to use the SLC ControlNet explicit message instruction Chapter 4 How to troubleshoot and read LEDs Chapter 5 Local database access using PLC-5 MSG instructions Appendix A Local database and ControlNet data files access using CIP messaging Appendix B CIP client management Appendix C Reset bit management Appendix D Application examples Appendix E

We wrote this manual for control engineers and technicians who are installing, programming, and maintaining a control system that includes an SLC 500 processor communicating on a ControlNet network with a ControlNet scanner. Here is what we assume.

Chapter 3

Common Techniques Used in This Manual

• You are developing a ControlNet network using an SLC processor in conjunction with a ControlNet scanner.

• You know each of your device’s I/O parameters and requirements.

• You understand SLC processor programming and operation.

• You are familiar with RSNetWorx for ControlNet software.

• You are familiar with the Microsoft Windows environment.

We use the following conventions throughout this manual.

• Numbered lists provide sequential steps.

• Bulleted lists provide information, not procedural steps.

1 Publication 1747-RM623D-EN-P - June 2006

Preface P-2

The screen captures shown in this manual are pictures of the software’s actual screens.

Terminology

See these tables for a list of ControlNet network terms and acronyms used in this manual.

Term Definition

Actual Packet Interval (API)

Big-endian A computer architecture in which, within a given multi-byte

Bit A unit of information consisting of a 1 or a 0. This is the smallest

Class A set of objects all of which represent a similar system

Client 1. An object that uses the services of another (server)

Connection A logical binding between two application objects. These

Connection Path The attribute is made up of a byte stream that defines the

Consume The act of receiving data from a producer. Consumer A node that is receiving data from a producer. Device A physical hardware connection to the link. A device may

Error A discrepancy between a computed, observed, or measured

Frame Single data transfer on a link. Instance The actual physical presentation of an object within a class.

Link A collection of nodes with unique MAC IDs. Segments

Little-endian A computer architecture in which, within a given multi-byte

The measure of how frequently a specific connection produces its data.

numeric representation, the most significant byte has the lowest address (the word is stored big-end-first - typically Motorola architecture).

data unit that can be transmitted.

component. A class is a generalization of the object, a template for defining variables and methods. All objects in a class are identical in form and behavior, but they may contain different attribute values.

object to perform a task.

2. An initiator of a message to which a server reacts.

application objects may be in the same or different devices.

application object to which a connection instance applies.

contain more than one node.

value or condition and the specified or theoretically correct value or condition.

Identifies one of many objects within the same object class.

connected by repeaters make up a link; links connected by routers make up a network.

numeric representation, the least significant byte has the lowest address (the word is stored little-end first - typically Intel architecture).

Publication 1747-RM623D-EN-P - June 2006

Preface P-3

Multicast Connection A connection where one node produces data and multiple nodes

consume that exact same data. Connections can be either point-to-point or multicast.

Network A series of nodes connected by some type of communication

medium. The connection paths between any pair of nodes can include repeaters, routers, and gateways.

Network Access Port (NAP)

Physical Layer variant that lets a temporary node to be connected to the link by connection to the NAP of a permanent node.

Network Address or

A node’s address on the link (also called MAC ID).

Node Address Network Status

Indicators Network Update Interval

(NUI) Network Update Time

Indicators on a node displaying the status of the Physical and Data Link Layers.

A single occurrence of the ControlNet Network Update Time (NUT).

Repetitive time interval in which data can be sent on the link.

(NUT) Node A connection to a link that requires a single MAC ID. Object 1. An abstract representation of a computer’s capabilities.

Objects can be composed of any or all of the following components: data (information which changes with time) configuration (parameters for behavior) methods (things that can be done using data and configuration)

2. A collection of related data (in the form of variables) and methods (procedures) for operating on that data that have clearly defined interface and behavior.

Originator The client responsible for establishing a connection path to the

target.

Point to Point Connection

A connection that exists between two nodes only. Connections

can be either point-to-point or multicast. Produce Act of sending data to a consumer. Producer A node that is responsible for transmitting data. Redundant Media A system using more than one medium to help prevent

communication failures. Requested Packet

Interval (RPI) Scanner Configuration

Tool (SCT)

The measure of how frequently the originating application

requires the transmission of data from the target application.

Software tool that lets you to configure scheduled connections,

map data for these connections, and monitor the status for the

configured connections. Scheduled Data transfers that occur in a deterministic and repeatable

manner on predefined NUTs. Server An object which provides services to another (client) object. Service Operation or function that an object performs upon request from

another object. Target The end-node to which a connection is established. Unscheduled Data transfers that use the remaining time in the NUT after the

scheduled transfers have been completed.

Publication 1747-RM623D-EN-P - June 2006

Preface P-4

Abbreviations and

Meaning Acronym

API Actual packet interval BNC A connector for coaxial cable having a bayonet-type shell

with two small knobs on the female connector which

lock into spiral slots in the male connector when it is

twisted CIP The control and information protocol defined by part 4 of

the ControlNet standard. CIP includes both connected

and unconnected messaging. LED Light emitting diode MAC ID The address of a node NAP Network access port NUI Network update interval NUT Network update time RPI Requested packet interval SCT Scanner configuration tool

Publication 1747-RM623D-EN-P - June 2006

Install and Connect the ControlNet Scanner

Chapter

What This Chapter Contains

Identify Scanner

This chapter describes how to install and connect your ControlNet 1747-SCNR scanner. See the table that shows where to find specific information in this chapter.

The following drawing identifies the features of the 1747-SCNR scanner.

Module Features

For Information About See Page

Identifying scanner features 1-1 Preparing the module for installation 1-2 Selecting the ControlNet node address 1-3 Inserting the 1747-SCNR into an SLC chassis 1-4 Connecting the 1747-SCNR to a ControlNet network 1-5 SLC 500 I/O configuration 1-8

Node Address and Status Display

displays scanner node address and

Channel B

Status Indicator

Channel A

Status Indicator

ControlNet Network Access Port

NAP RJ45 connector

status.

Module Status Indicator

indicates whether the device is powered and is functioning properly.

ControlNet Redundant Media Ports BNC Connectors (Channels A and B)

1 Publication 1747-RM623D-EN-P - June 2006

30751

1-2 Install and Connect the ControlNet Scanner

Prepare for Module Installation

Before you install your module, you need the following items:

RSNetWorx for

Personal Computer with Microsoft Windows

SLC 1746 Chassis with SLC 5/02, 5/03, 5/04, or 5/05 Processor and Appropriate Programming Software (RSLogix 500 Software)

ControlNet software, Catalog Number 9357-CNETL3

ControlNet 1784-PCC (shown), or 1784-PCIC, or 1784-KTCX15, or 1770-KFC15 Module

1747-SCNR Scanner Reference Manual, Publication 1747-RM62 (this manual)

Before you install the module, you must know how to do this.

41523

• Program and operate an Allen-Bradley SLC 50 0 programmable controller.

• Install and configure the devices on your ControlNet network.

The 1747-SCNR scanner fits in any slot of the chassis except for the leftmost slot of the first chassis, which is reserved for the SLC 500 processor.

Publication 1747-RM623D-EN-P - June 2006

Install and Connect the ControlNet Scanner 1-3

Select the ControlNet Node Address

Select the ControlNet node address of the 1747-SCNR module by setting the two 10-digit rotary switches on the top of the scanner.

10-digit Rotary Switch: Ones Digit

10-digit Rotary Switch: Tens Digit

Top View of Module

30752

You can select a node address from 01 to 99 for a device on a ControlNet link. Zero (00) is not a valid node address.

IMPORTANT

Since 00 is the default value from manufacturing, you must change the node address when using the scanner for the first time. Turning on the scanner with the node address set to 00 clears the module memory back to the factory default.

Publication 1747-RM623D-EN-P - June 2006

1-4 Install and Connect the ControlNet Scanner

Insert the 1747-SCNR Scanner Into the Chassis

To insert the 1747-SCNR scanner into the SLC chassis complete these procedures.

ATTENTION

Do not install the 1747-SCNR scanner with the chassis power supply on. Installing the module with the chassis power supply on may damage the module.

1. Turn off the SLC chassis power supply.

IMPORTANT

If you disconnect the ac power, you lose the chassis ground. Electrostatic damage (ESD) protection is lost.

2. Select a slot for the module in the chassis, choosing any slot except the left-most slot of the first chassi s, which is reserv ed for the SLC 500 processor.

Publication 1747-RM623D-EN-P - June 2006

30801-M

Install and Connect the ControlNet Scanner 1-5

3. Insert the module into the slot you have selected, noting that we recommend that you insert the 1747-SCNR scanner as close to the chassis power supply as possible.

4. Apply firm and even pressure to seat the module in the I/O chassis backplane connectors.

5. Restore power to the SLC chassis.

Connect to a ControlNet Network

Connect the 1747-SCNR scanner to a ControlNet network via a tap with a 1 m (39.4 in.) drop cable. Four taps are available from Rockwell Automation, Inc., as shown in the figure.

Straight T-tap

1786-TPS 1786-TPYR

IMPORTANT

Straight Y-tap

1786-TPYS

1786-TPR

Right-angle Y-tapRight-angle-Tap

Allen-Bradley ControlNet taps contain passive

20094

electronics and must be purchased from Rockwell Automation for the network to function properly.

After terminating your segments, connect your node to the network.

WARNING

If you connect or disconnect the ControlNet cable with power applied to this module or any device on the network, an electrical arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.

Publication 1747-RM623D-EN-P - June 2006

1-6 Install and Connect the ControlNet Scanner

Nonredundant Media

Remove the tap’s dust cap—located on the straight or right-angle connector—and set it aside.

Redundant Media

30802

If Your Network Supports Connect the Tap’s Straight or Right-angle

Connector

Nonredundant media To the channel A connector on the scanner—channel B is

not used.

(1)

Redundant media From the trunk-cable A to channel A on the scanner

andfrom trunk-cable B to channel B on the scanner

(1)

We recommend using channel A for nonredundant media.

For detailed information on planning and installing your ControlNet system, see the table for a list of related publications.

Publication 1747-RM623D-EN-P - June 2006

Publication Publication Number

ControlNet Coax Tap Installation Instructions 1786-IN007 ControlNet Network Access Cable Installation Instructions 1786-TD006 Industrial Automation Wiring and Grounding Guidelines 1770-IN041

Install and Connect the ControlNet Scanner 1-7

Connect Programming Terminal to a ControlNet Network

You can connect the programming terminal to a ControlNet network through a:

• ControlNet product NAP using a network access cable (1786-CP).

• tap on a ControlNet network.

ATTENTION

Do not connect the same communication card to both the NAP and a tap on the ControlNet network.

Using 1784-PCIC communication card on coax media

ControlNet 1747-SCNR Scanner

Programming Terminal

1784-KTCx15

ControlNet Network

Using 1770-KFC15 communication interface on coax media

ControlNet 1747-SCNR Scanner

Programming Terminal

Serial Connection

Using 1784-PCC or -PCIC communication card and NAP

ControlNet 1747-SCNR Scanner

1784-PCC

Programming Terminal

or -KTCx15

1786-CP

ControlNet Network

Using 1770-KFC15 communication interface and NAP

Serial Connection

1770-KFC15

1786-CP

1770-KFC15

ControlNet Network

Shown with redundant media (redundant media is not required).

The network access cable (1786-CP) can be plugged into any ControlNet product’s NAP to provide programming capability on the

ControlNet Network

41521

ControlNet network. A programming terminal connected through this cable is counted as a node and must have a unique address.

The 1784-PCC ships with its own ControlNet cable (1784-PCC1).

Publication 1747-RM623D-EN-P - June 2006

1-8 Install and Connect the ControlNet Scanner

SLC 500 I/O Configuration for the 1747-SCNR Module

ATTENTION

Select the I/O card. If you do not have an I/O card, complete the following procedure.

Open RSLogix 500 software and use the following procedure to configure the 1747-SCNR module.

In the RSLogix 500 project Window:

1. Open the I/O Configuration window.

2. Select the 1747-SCNR slot number.

3. Select the 1747-SCNR module from the current available cards

list. If it is not available, perform the following steps: a. Choose the other ..Requires I/O card type ID line in the

Current cards available list. b. In the Other type I/O Card window, type 13628. c. On the line associated with the scanner slot, the I/O

Configuration window will report the following:

Use the 1786-CP cable when connecting a scanner to the network through a NAP. Using a commercially-available RJ-style cable could result in network failure.

Publication 1747-RM623D-EN-P - June 2006

OTHER I/O Module- ID Code = 13628

d. Double-click the scanner line to open the Advanced I/O

Configuration window. e. Se t M0 Length to 1651 (decimal) and M1 Length to 608

(decimal).

4. Close the I/O Configuration and Advanced I/O Configuration windows.

Chapter

Prepare to Use the ControlNet Scanner

What This Chapter Contains

What Your Scanner Does

Read this chapter to understand how to use your ControlNet 1747-SCNR Scanner. The following table describes what this chapter contains and where to find specific information.

In a typical configuration, the scanner acts as an interface between ControlNet devices and an SLC processor. The scanner communicates with ControlNet devices over the network to do this:

For Information About See Page

What your scanner does 2-1 Communicating with your SLC processor 2-1 Understanding ControlNet data transfer 2-3 Understanding 1747-SCNR mapping 2-5 Communicating with your devices 2-9

• Read inputs from a device.

• Write outpu ts to a device.

• Issue native ControlNet requests to a remote node on the

ControlNet link (CIP client).

• Download configuration data.

Communicating with Your SLC Processor

1 Publication 1747-RM623D-EN-P - June 2006

The scanner communicates with the processor in the form of M1/M0 File Transfers and/or Discrete I/O (DIO). Information exchanged includes the following.

• Device I/O data

• Status and control information

• CIP client requests and response s

• Local database

An M1/M0 file transfer is a method of moving large amounts of data between an SLC 500 processor and its scanner.

Discrete input and output (DIO) is the transfer of one to 32 words between an SLC 500 processor and a scanner. All 32 words of input data and all 32 words of output data are updated on each SLC program scan.

2-2 Prepare to Use the ControlNet Scanner

Communicating with Your SLC processor Using M1 and M0 Files

Y our processor can communicate with the scanner via M1 file transfer reads and M0 file transfer writes.

The scanner does not send data to your processor. Data transfer between your scanner and the processor must be initiated by the processor. For example, data is sent, or written, to the scanner by your processor by placing the data in the M0 file. This data is organized in the scanner and then, based on the area you updated, the appropriate action is initiated to send it on the ControlNet network.

An M1 file transfer is the transfer of data from the scanner to the processor. The scanner makes data collected from the network’s devices available for the processor to read.

An M0 file transfer is the transfer of data from the SLC 500 processor to the scanner. The processor writes data to the scanner’s memory.

SLC 500 Processor

Discrete Input Image

M1 Data File

D E

Discrete Output Image

M0 Data File

Discrete Input Transfer

M1 file transfer (read)

Discrete Output Transfer

I/O Map

M0 file transfer (write)

1747-SCNR Scanner

Internal Input Data Storage

C A2 D E

ControlNe network

Internal Output Data Storage

X Y

Publication 1747-RM623D-EN-P - June 2006

41553

Prepare to Use the ControlNet Scanner 2-3

Understand ControlNet Data transfer

The ControlNet system is designed to do this:

• Provide high-speed, repeatable, deterministic I/O transmission.

• Let control and message information co-exist on the same

physical media.

• Make sure that I/O data transfers are not affected by:

• programming-terminal activity.

• inter-scanner message activity on the network.

Scheduled Data Transfer Operations on a ControlNet Network

ControlNet scheduled data transfer on a 1747-SCNR Scanner:

• is continuous.

• transmits on the network asynchronously to the ladder logic

program scan.

• occurs at the actual rate that is determined by RSNetWorx for ControlNet software.

For discrete I/O data transfer between logic scans (during housekeeping), the following updates occur.

• The gathered input image is moved from the scanner to the SLC processor's input image file for use during the next logic scan.

• The 1747-SCNR output data is updated with data from the SLC processor output image file and is sent during the next scheduled communication.

M0 and M1 files are data files that reside in the 1747-SCNR scanner only. Data from these files will be available to the SLC processor using ladder instructions. Scheduled data update will be triggered by the Housekeeping period start, which occurs once per scan. This process is illustrated below.

Housekeeping

Scheduled

Data Table Files

Logic Scan

LC 500 Program Scan Data Tables Files Housekeeping

Data Update

Data Private Memory Buffers

Scheduled Data Transfers

41554

1747-SCNR Scheduled Data

Publication 1747-RM623D-EN-P - June 2006

2-4 Prepare to Use the ControlNet Scanner

Unscheduled Data Transfer Operations on a ControlNet Network

The ControlNet network lets you use unscheduled mess agin g in addition to deterministic delivery.

Unscheduled operations include:

• peer-to-peer messaging.

• messaging from any remote CIP client device.

• messaging from programming devices.

• CIP client message initiated by the SLC processor ladder

program.

This process is illustrated in the figure.

Housekeeping

Logic Scan

Data Table Files

Data

M0 file transfer (SLC processor read and write)

Table Files

SLC 500 Program Scan

M0 file transfer (write request read response)

1747-SCNR Unscheduled Data

Data Tables Files Housekeeping

Link Layer Services

The figure illustrates link layer services.

Network Update Time (NUT)

Scheduled Service

Unscheduled Service

M0 Local Database area

M0 CIP client message area

Unscheduled Data Transfers

41555

Network Maintenance

Publication 1747-RM623D-EN-P - June 2006

Time

4155

Prepare to Use the ControlNet Scanner 2-5

The ControlNet system places your scheduled transfers in the first part of each network update interval (NUI). Time is automatically reserved for network maintenance, and unscheduled transfers are performed during the remainder of the interval.

Unscheduled messaging on a ControlNet network is non-deterministic.Your application and your configuration (for example, number of nodes, application program, NUT) deter mine how much time there is for unscheduled messaging.

Understand 1747-SCNR Mapping

IMPORTANT

The ControlNet network reserves time for at least one unscheduled transfer per NUI.

The 1747-SCNR scanner and the SLC processor exchange the following information through the backplane:

• Input data

• Output data

• Status data

• Command data

• CIP messages

The 1747-SCNR mapping is described in the following. Bit field descriptions follow each table.

Discrete Input File

Word Offsets

0 1 N/A Module Status (see

1-31 31 Scheduled ControlNet Input

Word Size

ControlNet Transfer Mode

Contents Description

the next section, “Module Status”)

Data

Bit field reporting general status information.

You can map up to 31 words of input data using RSNetWorx for ControlNet software.

Publication 1747-RM623D-EN-P - June 2006

2-6 Prepare to Use the ControlNet Scanner

Module Status (I:e.0)

Bit 0 1747-SCNR Module Faulted. Bit 1 1747-SCNR Communication Module Fault

The 1747-SCNR scanner is not on line. See M1 word 2 (M1:e2) for the ControlNet network status.

Bit 2 1747-SCNR Connection Fault

There is a fault in at least one scheduled connection. Bit 3-7 Reserved. Bit 8 Reset 1747-SCNR Module Acknowledge

The 1747-SCNR scanner will complement this bit each time the scanner is reset

due to complementing the Reset module command bit (O:e.0/8 where e is the

scanner slot number). See Example of Reset Bit Management. Bit 9 Disable ControlNet Scheduled Connections Acknowledge

The 1747-SCNR scanner will set this bit when the Disable ControlNet

Scheduled Connections Command bit is set (O:e.0/9) and all scheduled

connections have been closed. The 1747-SCNR scanner will clear this bit when

the Disable ControlNet Scheduled Connections Command bit is cleared. Bit 10 Scanner Mode

The 1747-SCNR scanner clears this bit when it is in idle mode. The 1747-SCNR

Scanner sets this bit when it is in run mode. Bit 11-15 Reserved.

1747-SCNR M1 File

Word Offsets

0 1 N/A Reserved Reserved for future use. 1 1 N/A Module

2 1 N/A ControlNet

3-255 253 Scheduled ControlNet

256-599 344 N/A Reserved Reserved. 600-607 8 N/A Connection

Word Size

ControlNet Transfer Mode

Contents Description

Value indicating the current Status (See the next page “Module Status”)

Status (See the next page “ControlNet Status”)

Input Data

Status

operational status of the module. See

the Troubleshooting for probable

causes and recommended actions.

Value indicating the current channel

LEDs.

You can map scheduled input data in

this area using RSNetWorx for

ControlNet software.

Bit field reporting scheduled

connections status.

Two consecutive bits per scheduled

connection:

Connection State

(Even bit numbers)

1:connection opened

0:connection closed

Remote Device Mode

(Odd bit numbers)

1:remote device is in run mode

0:remote device is in idle mode

Publication 1747-RM623D-EN-P - June 2006

Prepare to Use the ControlNet Scanner 2-7

Module Status (M1:e.1)

See Troubleshooting for probable causes and recommended actions.

Value Description

0x20 The scanner is not configured. 0x21 The current configuration is not valid. 0x22 Connections are configured, but no connections are established. 0x23 Connections are configured, but only 25% are successfully established. 0x24 Connections are configured, but only 50% are successfully established. 0x25 Connections are configured, but only 75% are successfully established. 0x26 All configured connections are established. 0x42 The node address is set to 00. This caused the scanner to erase network and

connection configuration stored in flash.

0x43 The scanner detected a network error due to a ControlNet cable problem or there

are no other nodes on the network.

0x44 The scanner has the same ControlNet address as another device on the network.

ControlNet Status (M1:e.2)

See the table that contains bit numbers and their descriptions.

Bit 0-2 Channel A status

Value LED State

000 Off 001 Green 010 Flashing green/off 011 Flashing red/off 100 Flashing red/green 101 Alternating red/off 110 Alternating red/green

111 Red Bit 3 Reserved Bit 4-6 Channel B status

Value LED State

000 Off

001 Green

010 Flashing green/off

011 Flashing red/off

100 Flashing red/green

101 Alternating red/off

110 Alternating red/green

111 Red Bit 7-15 Reserved

Publication 1747-RM623D-EN-P - June 2006

2-8 Prepare to Use the ControlNet Scanner

Discrete Output File

Word Offsets

0 1 N/A Module Command Bit field used to send commands 1-31 31 Scheduled ControlNet Output

Word Size

ControlNet Transfer Mode

Contents Description

to the 1747-SCNR Scanner. You can map up to 31 words of

Data

output data using RSNetWorx for ControlNet software.

Module Command (O:e.0)

Bit 0-7 Reserved Bit 8 Reset Scanner Command

By complementing this bit, you reset the 1747-SCNR scanner (the reset occurs when the SLC slot is de-activated). It is important to note that if you do not disable the slot while the scanner is resetting, the SLC module will fault with the error code nn57h (specifically, I/O module in slot nn did not respond to a lock shared memory command in the requested time limit) where nn is the slot number of the scanner . This is why the reset bit change is not taken into account until the slot is disabled.

Bit 9 Disable ControlNet Scheduled Connections Command

When the bit value is 1, the 1747-SCNR scanner will close all scheduled connections. When the bit value is 0, the 1747-SCNR scanner will enable all scheduled connections.

Bit 10 Scanner Mode Command

When the bit value is 0, the 1747-SCNR scanner is forced to Idle mode. When the bit value is 1, the scanner’s mode will be determined by the mode of the processor in slot 0.

Bit 11-15 Reserved

Publication 1747-RM623D-EN-P - June 2006

1747-SCNR M0 File

Prepare to Use the ControlNet Scanner 2-9

Word Offsets

0-2 3 N/A Reserved Reserved. 3-255 253 Scheduled ControlNet

256-699 444 N/A Reserved Reserved. 700-955 256 Unscheduled Local

1000-1650 651 Unscheduled CIP Client

Word Size

ControlNet Transfer Mode

Contents Description

Using the RSNetWorx for

Output Data

Database

Message Area

ControlNet software, you can map scheduled output data in this area.

Memory area used by remote devices to read or write data using CIP messaging or PLC-5 messaging.

Memory used to send CIP client requests. These messages are then sent by the 1747-SCNR module as unscheduled messaging.

Only Input and Output data (from Input file, Output file, M0 ControlNet Output data area, and M1 ControlNet Input data area) are exchanged during scheduled time.

Data transfer to the M0 Local Database is performed using Unscheduled messaging. Services available to read or write in this area are Set Attribute Single, Get Attribute Single, Set Member, and Get Member.

Communicating with Your Devices

The 1747-SCNR scanner supports up to 64 simultaneous scheduled connections and up to 50 simultaneous unscheduled connections. The 1747-SCNR scanner also supports up to 32 simultaneous incoming unconnected requests.

I/O Scheduled Data Transfer

Data received from the devices, or input data, is organized by the scanner and made available to your processor in the Input file or the M1 ControlNet data area.

Data received from your SLC processor, or output data, is stored within the Output file or M0 ControlNet data area. The 1747-SCNR scanner can then send the data to your remote ControlNet devices.

Publication 1747-RM623D-EN-P - June 2006

2-10 Prepare to Use the ControlNet Scanner

All scheduled data transfer to Input, Output, M0 and M1 files must be mapped on a ControlNet network. You have to specify where I/O data is to be read from or written to, in other words, mapped. Data size and location within 1747-SCNR data files have to be configure d for each connection you want to setup with a remote device. The configuration is performed using RSNetWorx for ControlNet so ftware.

Unscheduled Data Server

The scanner supports some CIP data server functionality on a specific local database of 256 words located in the M0 file. Any device on ControlNet can read or write in this database using the supported services as described in Local Database Access Using PLC-5 MSG Instructions and Local Database and ControlNet Data Files Access Using CIP Messaging.

The SLC processor that has read and write access to this area is then able to receive or modify data into the database.

Using this Local Database:

• a device can send data to an SLC processor us in g unscheduled data transfer.

• two devices can exchange unscheduled data by using this database as a proxy data storage.

• a PLC-5 controller can exchange data with the SLC processor by reading or writing in this area using MSG instructions.

• an HMI can exchange data with the SLC processor by reading or writing in this area using PLC-5 type read and write commands.

Publication 1747-RM623D-EN-P - June 2006

+ 114 hidden pages