Rockwell Automation 1747-SN User Manual

Download

Page 1

Remote I/O Scanner

1747-SN

User Manual

Page 2

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://www.ab.com/manuals/gi) 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

SHOCK HAZARD

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

• recognize the consequence

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

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

Page 3

Summary of Changes

The information below summarizes the changes to this manual since the last printing. Updates to the manual include using RSLogix 500 instead of APS software.

To help you find new and updated information in this release of the manual, we have included change bars as shown to the right of this paragraph.

The table below lists the sections that document new features and additional or updated information on existing features.

For this information: See

configuring RIO using G Files page 4-4

using block transfer instruction (BTR and BTW)

removed Chapter 7 application examples can be found in

configuring G files using RSLogix 500 page B-9

block transfer examples for earlier processors

page 5-5

Chapter 4 and Chapter 5

Appendix D

1 Publication 1747-UM013B-EN-P - January 2005

Page 4

Summary of Changes 2

Publication 1747-UM013B-EN-P - January 2005

Page 5

Important User Information . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table of Contents Chapter 1 Overview

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Scanner I/O Image Division . . . . . . . . . . . . . . . . . . . . . 1-3

How the Scanner Scans Remote I/O . . . . . . . . . . . . . . . . . 1-4

SLC and Scanner Asynchronous Operation . . . . . . . . . . 1-4

How the Scanner Interacts with Adapters . . . . . . . . . . . . . . 1-5

Scanner I/O Image Concepts . . . . . . . . . . . . . . . . . . . . . . . 1-6

Example Scanner I/O Image. . . . . . . . . . . . . . . . . . . . . 1-7

Transferring Data with RIO Discrete and Block Transfers 1-9

Physical and Logical RIO Link Specifications . . . . . . . . . 1-9

Extended Node Capability . . . . . . . . . . . . . . . . . . . . . . 1-9

Complementary I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Complementary I/O: Placing Modules with 2-Slot Addressing

1-12

Complementary I/O: Placing Modules with 1-Slot Addressing

1-13

Complementary I/O: Placing Modules with 1/2-Slot

Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Summary for Placing Modules Used In Complementary I/O.

1-15

Complementary I/O Application Considerations . . . . . . 1-17

Complementary 1771 I/O Module Details . . . . . . . . . . . 1-17

Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

Baud Rate DIP Switch . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

RIO Link Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Compatible Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

Chapter 2

Quick Start for Experienced Users

Required Tools and Equipment . . . . . . . . . . . . . . . . . . . . . 2-1

Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Chapter 3

Installation and Wiring

1 Publication 1747-UM013B-EN-P - January 2005

Compliance to European Union Directives . . . . . . . . . . . . . 3-1

EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Baud Rate Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Scanner Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Insertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

RIO Link Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

New Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

For Series A Scanner Retrofits . . . . . . . . . . . . . . . . . . . . 3-7

Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Scanner Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

At Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

In Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Page 6

Table of Contents 2

Scanner Configuration and Programming

When Changing From Run Mode . . . . . . . . . . . . . . . . . 3-8

Status LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Chapter 4

Understanding Remote Input and Output Image Files. . . . . 4-1

RIO Configuration Using G Files . . . . . . . . . . . . . . . . . . . . 4-4

Rules for Configuring the Scanner. . . . . . . . . . . . . . . . . 4-7

Considerations When Configuring Remote I/O . . . . . . . . . . 4-12

G File Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Crossing Logical Rack Boundaries . . . . . . . . . . . . . . . . 4-13

Understanding M Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

M Files Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

M0 Control File Description . . . . . . . . . . . . . . . . . . . . . 4-16

M0 File - RIO Device Inhibit Control. . . . . . . . . . . . . . . 4-17

M0 File - RIO Device Reset Control. . . . . . . . . . . . . . . . 4-18

M0 File - Remote Output Reset Control. . . . . . . . . . . . . 4-19

Device Reset and Remote Output Reset Considerations. . . . 4-21

M1 Status File Description . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

General Communication Status - Enable Device Fault Bit. . .

4-23

General Communication Status - Communication Attempted

Bit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

RIO Baud Rate Status . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

Logical Device Starting Address Status . . . . . . . . . . . . . 4-24

Logical Device Image Size Status . . . . . . . . . . . . . . . . . 4-25

Active Device Status. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Logical Device Fault Status . . . . . . . . . . . . . . . . . . . . . . 4-27

RIO Status Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

RIO Communication Retry Counter (M1:e.16 -47) . . . . . . . . 4-30

Understanding Slot Addressing . . . . . . . . . . . . . . . . . . . . . 4-32

SLC/Scanner Configuration . . . . . . . . . . . . . . . . . . . . . . . . 4-33

RIO Block Transfer

Troubleshooting

Publication 1747-UM013B-EN-P - January 2005

Chapter 5

RIO Block Transfer Theory of Operation . . . . . . . . . . . . . . 5-1

What Is RIO Block Transfer? . . . . . . . . . . . . . . . . . . . . 5-1

Using Block Transfer Instructions (BTR and BTW) . . . . . . . 5-5

RIO Block Transfer General Functional Overview . . . . . 5-5

Parameters for BTR and BTW. . . . . . . . . . . . . . . . . . . . 5-6

Control Status Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Instruction Operation. . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Programming Examples . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Comparison to the PLC-5 BTR and BTW . . . . . . . . . . . . 5-16

Chapter 6

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Page 7

Specifications

M0 - M1 Files and G Files

Table of Contents 3

Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Retry Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Block Transfers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Appendix A

Scanner Operating Specifications . . . . . . . . . . . . . . . . . . . . A-1

Network Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Throughput Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

RIO Network Throughput Components. . . . . . . . . . . . . A-2

Calculating Throughput. . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Discrete I/O Throughput without Block Transfers (Tdm-nbt)

Present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Discrete I/O Throughput with Block Transfers (Tdm-bt)

Present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Block Transfer Throughput . . . . . . . . . . . . . . . . . . . . A-10

RIO Scanner Output Delay Time (TSNo) Tables . . . . . A-13

Appendix B

M0 - M1 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Addressing M0-M1 Files . . . . . . . . . . . . . . . . . . . . . . . . B-2

Restrictions on Using M0-M1 Data File Addresses . . . . . B-2

Monitoring Bit Addresses . . . . . . . . . . . . . . . . . . . . . . . B-2

Transferring Data Between Processor Files and M0 or M1 Files

B-4

Access Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4

Minimizing the Scan Time . . . . . . . . . . . . . . . . . . . . . . B-7

Capturing M0-M1 File Data. . . . . . . . . . . . . . . . . . . . . . B-8

Specialty I/O Modules with Retentive Memory . . . . . . . B-8

G Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Configuring G Files using RSLogix 500 . . . . . . . . . . . . . B-9

After all devices have been properly mapped, click OK and

the G file is automatically configured. This procedure

eliminates the bit by bit process needed to configure the G

file with other programming tools. . . . . . . . . . . . . . . . B-13

Editing G File Data . . . . . . . . . . . . . . . . . . . . . . . . . . B-14

RIO Configuration Worksheet

Block Transfer Examples for Earlier Processors

Appendix C

Directions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D

BTR and BTW Control Logic Examples . . . . . . . . . . . . . . . D-1

Block Transfer Read Control Logic Example . . . . . . . . . D-1

Block Transfer Write Control Logic Example . . . . . . . . D-4

Directional Continuous Block Transfer Example . . . . . . D-6

Directional Repeating Block Transfer Example . . . . . . . D-9

Publication 1747-UM013B-EN-P - January 2005

Page 8

Table of Contents 4

Glossary Index

Directional Non-Continuous Block Transfer Example . D-12

Bidirectional Continuous Block Transfer Example . . . . D-16

Bidirectional Alternating Block Transfer . . . . . . . . . . . D-21

Bidirectional Alternating Repeating Block Transfer . . . D-27

Rockwell Automation Support . . . . . . . . . . . . . . . . . . . . . . 1-7

Installation Assistance . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

New Product Satisfaction Return. . . . . . . . . . . . . . . . . . 1-7

Publication 1747-UM013B-EN-P - January 2005

Page 9

Overview

This chapter contains the following information:

• system overview

• how the scanner interacts with the SLC processor

• how the scanner interacts with adapter modules

• scanner I/O image concepts

• extended node capability

• complementary I/O

• scanner features

• compatible network devices

Chapter

System Overview

The Remote I/O (RIO) Scanner, Catalog Number 1747-SN, is the remote I/O scanner for the SLC 500. It enables communication between an SLC processor (SLC 5/02 or later) and remotely located (3,048 meters [10,000 feet] maximum) 1746 I/O chassis and other RIO compatible Allen-Bradley operator interface and control devices. The 1747-SN Scanner communicates with remotely located devices using the Allen-Bradley Remote I/O link. The RIO link consists of a single master (scanner) and multiple slaves (adapters). Communication between devices occurs over twisted pair cable with the devices daisy-chained together. The scanner can reside in any slot of the local SLC chassis except for slot 0.

1 Publication 1747-UM013B-EN-P - January 2005

Page 10

1-2 Overview

SLC 5/02 or Later Processor

Local SLC Chassis

Dataliner Message Display

(Adapter/Slave)

RIO Scanner (Master of the RIO Link)

The scanner transfers input and output data between itself and all configured network devices over twisted pair cable. Note that the end-to-end length of the cable can be a maximum of 3,048 meters (10,000 feet).

PanelView Operator Terminal (Adapter/Slave)

The scanner can be configured for and transfer a maximum of 4 logical racks of discrete data on the RIO link. The scanner provides discrete I/O and block (Series B or later) transfers. Configurations allowed are any combination of quarter, half, three-quarter, or full logical rack devices.

1747-ASB Module (Adapter/Slave)

Remote Chassis

Remote Expansion Chassis

RediPANEL (Adapter/Slave)

SLC 5/02 or Later Processor

Adapter 1

Half Logical Rack Device

Publication 1747-UM013B-EN-P - January 2005

RIO Scanner

Adapter 2

Quarter Logical Rack Device

The scanner transfers discrete input and output data between itself, remote adapters, and the SLC processor.. Remote adapters consist of 1746 chassis and other Allen-Bradley operator interface and control devices.

Adapter 3 Adapter 4

Half Logical Rack Device

Three-Quarter Logical Rack Device

Adapter 5

Full Logical Rack Device

Adapter 6

Full Logical Rack Device

The SLC processor transfers the scanner’s 4 logical racks (32 input image and 32 output image words) of discrete remote I/O image data into the SLC input and output image files. You can adjust the size of the scanner input and output image file during configuration of your SLC system so that the scanner only transfers the discrete I/O data

Page 11

Overview 1-3

your application program requires. Configuration is done through the confiGuration file (G file). Refer to Chapter 4, Configuration and Programming, for more information.

IMPORTANT

The SLC 500 processor (SLC 5/02 or later) supports multiple scanners in its local I/O chassis. The maximum number is dependent on the following:

• backplane power requirements (power supply dependent)

• SLC 500 processor I/O data table limit (4,096 I/O)

• processor memory to support the application

(SLC 500 processor dependent)

Scanner I/O Image Division

The scanner allows each adapter to use a fixed amount (user defined) of the scanner’s input and output image. Part of the SLC processor’s image is used by local I/O, the other portion is used by the scanner for remote I/O.

The scanner remote I/O image is divided into logical racks and further divided into logical groups. A full logical rack consists of eight input and eight output image words. A logical group consists of one input and one output word in a logical rack. Each logical group is assigned a number from 0 to 7.

Local I/O

Logical Rack 0

Remote I/O

(Scanner Image)

Processor I/O Image Scanner I/O Image Adapter

Logical Rack 1

Logical Group 0

Logical Rack 2

Logical Group 7

Image

Publication 1747-UM013B-EN-P - January 2005

Page 12

1-4 Overview

The scanner image contains the image of each adapter on the RIO link. The adapter is assigned a portion of the scanner image, which is referred to as the adapter image.

How the Scanner Scans Remote I/O

The scanner communicates with each logical device in a sequential fashion. First, the scanner initiates communication with a device by sending output data to the device. The device then responds by sending its input data back to the scanner, as illustrated below. You refer to this exchange as a discrete I/O transfer. After the scanner completes its discrete I/O transfer with the last configured network device, it begins another discrete I/O transfer with the first device.

It is important to understand that the scanner transfers RIO data on a logical device basis not on an adapter basis. A logical device is a full logical rack or portion of a logical rack assigned to an adapter.

RIO Scanner Scan

The scanner updates its input image file each time it scans a logical device.

Scanner Input Image File

Input Device 3

Output Device 3

Output Device 2

Input Device 1

Output Device 1

Input Device 2

Publication 1747-UM013B-EN-P - January 2005

Scanner Output Image File

SLC and Scanner Asynchronous Operation

The SLC processor scan and RIO scanner scan are independent (asynchronous) of each other. The SLC processor reads the scanner input image file during its input scan and writes the output image file to the scanner during its output scan. The RIO scanner continues reading inputs and writing outputs to the scanner I/O image file, independent of the SLC processor scan cycle.

Depending on your SLC processor, RIO link configuration, and application program size, the scanner may complete multiple scans before the SLC processor reads the scanner’s input image file. The RIO scanner updates its I/O files on a per logical rack basis.

Page 13

The figure below illustrates the asynchronous operation of the SLC

processor and RIO scanner.

SLC Processor Scan Cycle RIO Scanner Scan Cycle

Overview 1-5

The SLC processor reads the scanner input image file into the SLC input image file, processes it, and creates an SLC output image file. The SLC processor

ransfers its output file to the

scanner..

Important: The outputs of the RIO are updated after the end of the first SLC processor scan.

Program

SLC Processor

How the Scanner Interacts with Adapters

Input Image Device 1

Input Image Device 2

Output Image Device 1

The scanner updates its input image file each time it scans a logical device. The scanner may scan all of its configured logical devices several times before the SLC processor reads the scanner's input image file.

SLC Input Image File

SLC Output Image File

Scanner Input Image File

Input Image Device 3

Output Image Device 2

Scanner Output Image File

Output Image Device 3

The scanner’s function is to continuously scan the adapters on the RIO link in a consecutive manner. This scan consists of one or more RIO discrete transfers to each adapter on the RIO link.

RIO discrete transfers consist of the scanner sending output image data and communication commands to the adapter that instruct the adapter on how to control its output. (These include run, adapter reset, and reset decide commands.) The adapter responds by sending input data to the scanner. The scanner performs as many RIO discrete transfers as necessary to update the entire adapter image. If RIO discrete transfers do not occur, data is not exchanged between the scanner and adapter. RIO discrete transfers are asynchronous to the processor scan.

Publication 1747-UM013B-EN-P - January 2005

Page 14

1-6 Overview

SLC Local Chassis

Processor

Scanner

RIO Discrete Transfers with Adapter 1

RIO Discrete Transfers with Adapter 2

RIO Discrete Transfers with Adapter 3

RIO Discrete Transfers with Adapter 4

PanelView Operator Terminal

RediPANEL

Scanner I/O Image Concepts

The scanner’s I/O image consists of RIO logical racks and I/O groups. A full RIO logical rack consists of eight input image and eight output image words. (A word consists of 16 bits of data.) Each word within an RIO logical rack is assigned an I/O group number from 0 to 7.

You assign devices on the RIO link a portion of the scanner’s image. Devices can occupy a quarter logical rack (2 input and output words), half logical rack (4 I/O words), three-quarter logical rack (6 I/O words), or full logical rack. You may configure devices to start at any even I/O group number within an RIO logical rack. More than one physical device’s (adapter) I/O information can reside in a single logical rack. Also, by crossing logical rack boundaries, a device can consist of more than one logical rack.

IMPORTANT

The following illustration shows only the input image configuration of the scanner’s I/O image. The output image configuration is the same.

Publication 1747-UM013B-EN-P - January 2005

Page 15

Input Image Half of a Scanner's I/O Image

Overview 1-7

RIO Logical Rack 0

RIO Logical Rack 1

RIO

Logical Rack 2

RIO

Logical Rack 3

Bit Number (decimal)

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 Group 3

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 4

Rack 1 Group 5

Rack 1 Group 6 Rack 1 Group 7 Rack 2 Group 0

Rack 2 Group 1

Rack 2 Group 2

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 1

Rack 3 Group 2

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

Word 0

Word 1 Word 2

Word 3

Word 4

Word 5 Word 6

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14 Word 15 Word 16

Word 17

Word 18

Word 19

Word 20 Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29 Word 30

Word 31

Bit Number (octal)

0123456789101112131415

Quarter Logical Rack

Not Used In This Example

Half Logical Rack

Not Used In This Example

Three-Quarter Logical Rack

Not Used In This Example

Full Logical Rack

1828384858687

8108118128138148158168178

Example Scanner I/O Image

The illustrations below show a scanner’s input image of 4 RIO link devices.

Publication 1747-UM013B-EN-P - January 2005

Page 16

1-8 Overview

SLC 5/02 or Later Processor

RIO Scanner

RIO

Logical

Rack 0

RIO

Logical

Rack 1

RIO

Logical

Rack 2

RIO

Logical

Rack 3

Device 1

Full Logical Rack Device Begins at Logical Rack 0, Group 0.

Important: The illustration below shows only the scanner's input image. The output image looks the same.

Bit Number

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 Group 3

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 4

Rack 1 Group 5

Rack 1 Group 6 Rack 1 Group 7 Rack 2 Group 0

Rack 2 Group 1

Rack 2 Group 2

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 1

Rack 3 Group 2

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5 Rack 3 Group 6

Rack 3 Group 7

Bit Number (octal)

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5 Word 6

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 15 Word 16

Word 17

Word 18

Word 19

Word 20 Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Device 2

Three-Quarter Logical Rack Device Begins at Logical Rack 1, Group 0.

Device 3 Device 4

Half Logical Rack Device Begins at Logical Rack 2, Group 0.

8108118128138148158168178

e = slot number of the SLC chassis containing the scanner

Quarter Logical Rack Device Begins at Logical Rack 2, Group 4.

Input File

0123456789101112131415

Address

I:e.0 I:e.1 I:e.2 I:e.3 I:e.4 I:e.5 I:e.6 I:e.7 I:e.8 I:e.9 I:e.10 I:e.11 I:e.12 I:e.13 I:e.14 I:e.15 I:e.16 I:e.17 I:e.18 I:e.19 I:e.20 I:e.21 I:e.22 I:e.23 I:e.24 I:e.25 I:e.26 I:e.27 I:e.28 I:e.29 I:e.30 I:e.31

1828384858687

Device 1

Device 2

Not Used

Device 3

Device 4

Not Used

Publication 1747-UM013B-EN-P - January 2005

Page 17

Overview 1-9

Transferring Data with RIO Discrete and Block Transfers

Input and output image data and command information are quickly exchanged between a scanner and adapter using RIO discrete transfers. RIO discrete transfers are the simplest and fastest way a scanner and adapter communicate with each other. RIO discrete transfers, which are transparent to the user, consist of the scanner sending the output image data to the adapter, and the adapter transmitting input data to the scanner. Each RIO discrete transfer also contains scanner commands for the adapter.

Through your control program, you command the SLC processor to initiate RIO block transfers, which directs the scanner to exchange large amounts of data to/from an adapter. Block Transfers (BTs) use the basic RIO discrete transfer mechanism of the RIO link. However, the actual transfer of data occurs asynchronous to the discrete transfers. It is possible for several discrete transfers to occur before the scanner processes a block transfer. Refer to Chapter 5, RIO Block Transfer for more details.

Physical and Logical RIO Link Specifications

The maximum number of adapters with which your scanner can communicate is determined by the scanner’s and adapter’s physical and logical specifications, as described below:

• Physical Specifications are the maximum number of adapters that can be connected to the scanner. For more information, see Extended Node Capability below.

• Logical Specifications for the scanner are the maximum number of logical racks the scanner can address, how the logical racks can be assigned, and whether the scanner can perform BTs.

Extended Node Capability

Extended node functionality allows you to connect up to 32 physical devices on an RIO link. You must use 82 Ohm RIO link resistors in an extended node configuration. You can only use extended node if all RIO link devices have extended node capability. (Refer to the Compatible Devices table at the end of this chapter, or to the specifications of your device.) The 1747-SN Series B Scanner has extended node capability. However, the smallest logical rack division is 1/4 logical rack and the scanner image size is 4 logical racks. Therefore, the scanner is limited to 16 devices unless complementary

Publication 1747-UM013B-EN-P - January 2005

Page 18

1-10 Overview

I/O is used. Refer to the following section for more information on complementary I/O.

Complementary I/O

Complementary I/O is very useful when portions of your input and output images are unused because it allows the images of two adapters to overlap each other in the scanner’s I/O image. To use complementary I/O, the I/O image from one adapter must be the mirror (complement) of the other. This means that there must be an input module in the primary chassis and an output module in the same slot of the complementary chassis. This enables total use of the scanner’s 32 input and 32 output word image for I/O addressing of up to 1024 discrete points.

ATTENTION

Because the primary and complementary chassis images overlap, input and specialty combination I/O modules must never share the same image location. Inputs received by the scanner may be incorrect and RIO block transfers will not be serviced properly. If an output module shares its output image with another output module, both output modules receive the same output information.

If you want to use complementary I/O, two adapters that support this function are required (e.g., 1747-ASB modules). One adapter is configured (via its DIP switches) as a primary chassis, the other as a complementary chassis. If a primary chassis exists, it is scanned first.

Primary and complementary chassis cannot have the same logical rack number. The logical rack numbers must be assigned to the primary and complementary racks as shown below:

Primary Chassis Logical Rack Number

Complementary Chassis Logical Rack Number

Decimal Octal

Publication 1747-UM013B-EN-P - January 2005

0810

1911

21012

31113

Page 19

Overview 1-11

ATTENTION

If the logical rack numbers are not properly assigned, unpredictable operation of both ASB modules results. No ASB module errors occur. Refer to your ASB module user manual for specific information on setting the address of the complementary chassis. (For example, in the 1771-ASB manual the addresses for the complementary chassis are referred to as complementary chassis 0-3.)

Guidelines for Configuring Complementary I/O

When you configure your remote system for complementary I/O, follow these guidelines:

• You can place an output module in the primary chassis opposite another output module in the complementary chassis; they use the same bits in the output image table. However, we do not recommend this placement of modules for redundant I/O.

• You cannot use complementary I/O with a chassis that uses 32-point I/O modules and 1-slot addressing or 16-point I/O modules with 2-slot addressing.

• Do not place an input module in the primary chassis opposite an input module in the complementary chassis; they will use the same bits in the input image table.

Publication 1747-UM013B-EN-P - January 2005

Page 20

1-12 Overview

Example 1

Complementary I/O: Placing Modules with 2-Slot Addressing

The following figures illustrate a possible module placement to configure complementary I/O using 2-slot addressing.

Example 2

I 8

012345

O 8

I 16

012345

I 8

O 8

O 16

O 8

I 8I 8

I 16

O 8

O 16

I 16

E M P T Y

I 16

O 16O 8O 8

E M

8O 8

T Y

O 16

I 16

O 16

E M P T Y

I 16

O 8

I 8 O 8

O 16

I 16

O 16

Publication 1747-UM013B-EN-P - January 2005

Outputs in the complementary chassis would use the same bits in the output image table as the outputs in the primary chassis. You cannot place inputs in the complementary chassis.

1 = Output modules use the same output image table bits. This is not recommended. 2 = Must be empty if corresponding primary slot is a block transfer module.

Important: With 2-slot addressing, if an input module resides in either slot associated with a logical group of the primary chassis, an input module cannot reside in that logical group' s complementary chassis.

Page 21

Example 1

Overview 1-13

Complementary I/O: Placing Modules with 1-Slot Addressing

The figure below illustrates a possible module placement to configure complementary I/O using 1-slot addressing.

Example 2

I 16

01234 5

O 16O 16I 16I 16

I 16

01234 5

16O16

16I 16I 16I 16I 16I 16I 16I 16I 16

O 16

I 16

O 16

I 16

BT I

67 0 1 2 3

O 16

67 0 1 2 3

16O 16O 16

E M P

I 16

I 16O 16

I 16

O 16O 16

I = Input Module (8- or 16-point) O = Output Module (8- or 16-point) BT = Block Transfer Module 1 = Output modules use the same output image table bits. This is not recommended.

2 = Must be empty if corresponding primary slot is block transfer..

O 16O 16O 16O 16O 16O 16O 16O 16O 16O 16

Publication 1747-UM013B-EN-P - January 2005

Page 22

1-14 Overview

Example 1

Complementary I/O: Placing Modules with 1/2-Slot Addressing

The figure below illustrates a possible module placement to configure complementary I/O using 1-slot addressing.

IIOOO O BT I

Example 2

01 23 45 67 01 23

OOII IOO1I

I I

01 23 45 67 01 23 45 67 01 23

IIIIIIII

OOO OOO OO

45 67 01 23

E M P T Y

Publication 1747-UM013B-EN-P - January 2005

I = Input Module (8-, 16-, or 32-point) O = Output Module (8-, 16-, or 32-point) BT = Block Transfer Module

1 = Output modules use the same output image table bits. This is not recommended. 2 = Must be empty if corresponding primary slot is block transfer.

Page 23

Overview 1-15

Summary for Placing Modules Used In Complementary I/O

Discrete Modules

Addressing Method Types of Modules used Placement

2-slot 8-point Install input modules

opposite output modules, and output modules

opposite input modules.

1-slot 8-point, 16-point

1/2-slot 8-point, 16-point, 32-point

(1) If an input module resides in either slot associated with a logical group of the primary chassis, an input module

cannot reside in that logical group’s complementary chassis.

Block Transfer Modules

(1)

Addressing Method Placement

2-slot The right slot of the primary I/O group can be another block

transfer module, or an 8-point input or output module.

The left slot of the complementary I/O group must be empty.

In the right slot of the complementary I/O group, you can place an 8-point output module; this slot must be empty if the corresponding slot in the primary I/O group is a block transfer module.

1-slot Leave the corresponding I/O group in the complementary

chassis empty.

1/2-slot Leave the corresponding I/O group in the complementary

chassis empty.

The following example illustrates how I/O modules requiring two words of the input or output image can leave unused image space.

Publication 1747-UM013B-EN-P - January 2005

Page 24

1-16 Overview

OOOO

IIII

012 3 45 678

Slot Slot

Slot Pair

1234

I = Input Module

= Output Module

Primary Chassis

Primary Chassis Configured As:

Logical Rack Number 0

Logical Group Number 0

Image Size (logical groups) 16

Addressing Mode 1/2-slot

Primary/Complementary Primary

Primary Chassis I/O Image Complementary Chassis I/O Image

Input Image

from Primary Chassis

701017

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5

Slot 6

Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

07815

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5

Slot 6

Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

Octal

Decimal

Slot Pair

Output Image

from Primary Chassis

701017

Decimal

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

07815

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

Input Image

Octal

Slot Pair Slot Pair Slot Pair

from Complementary Chassis

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

= unused image space

OOOO

IIII

012 3 45 678

Slot Pair

1234

Complementary Chassis

Complementary Chassis Configured As:

Logical Rack Number 8 (decimal)

Logical Group Number 0

Image Size (logical groups) 16

Addressing Mode 1/2-slot

Primary/Complementary Complementary

701017

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

Decimal

07815

from Complementary Chassis

Octal

Output Image

701017

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Octal

Decimal

07815

Scanner's I/O Image

Both images are overlapped in the

scanner. The overlapped image

appears where the primary chassis

image is configured to reside.

In this case, the primary chassis

image is configured as starting

logical rack 0 and starting logical

group 0.

Publication 1747-UM013B-EN-P - January 2005

Logical

Rack 0

Logical

Rack 1

Group 0 Group 1 Group 2 Group 3 Group 4 Group 5 Group 6 Group 7 Group 0 Group 1 Group 2 Group 3 Group 4 Group 5 Group 6 Group 7

Input Image Output Image

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

701017

Octal

Decimal

07815

Slot 1 Slot 1

Slot 2 Slot 2 Slot 3 Slot 3

Slot 4 Slot 4

Slot Pair Slot Pair

Slot 5 Slot 5

Slot 6 Slot 6 Slot 7 Slot 7

Slot 8 Slot 8

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

701017

Slot 1 Slot 1 Slot 2 Slot 2 Slot 3 Slot 3 Slot 4 Slot 4 Slot 5 Slot 5 Slot 6 Slot 6 Slot 7 Slot 7 Slot 8 Slot 8

Octal

Decimal

07815

Page 25

Logical

Rack 0

Word 0 Word 1

Word 2

Word 3 Word 4

Word 5 Word 6 Word 7

Overview 1-17

Complementary I/O Application Considerations

If you configure a complementary device to use more I/O image space than an associated primary device, then block transfers can only be performed to locations in the complementary device that have associated I/O image space in the primary device. For example, if a primary device is 1/2 logical rack and a complementary device is a full logical rack, block transfers can be performed only in the first 1/2 logical rack of the complementary device. Attempting block transfers in the last half of the complementary device will result in a BT error (error - 11 - device not configured).

1/2 logical rack

1/2 logical rack configured and usable

1/2 logical rack not configured

Logical Rack 8

Word 0

Word 1

Word 2

Word 3 Word 4

Word 5 Word 6 Word 7

1/2 logical rack

ured and us

confi

configured and usable

1/2 logical rack

confi

ured, but no

usable for BT sinc

configured, but not

Words 4-7 are not

usable for BT since

configured for the

Words 4 to 7 are not

primary device.

configured for the primary device.

Complementary 1771 I/O Module Details

Use the following modules in either primary or complementary I/O chassis opposite any type of module:

• Communication Adapter Module (1771-KA2)

• Communication Controller Module (1771-KE)

• PLC-2 Family/RS-232-C Interface Module (1771-KG)

• Fiber Optics Converter Module (1771-AF)

• DH/DH+ Communication Adapter Module (1785-KA)

• DH+/RS-232C Communications Interface Module (1785-KE)

Use the following modules in either primary or complementary I/O chassis opposite any type of module. However, these modules do not work as stand-alone modules; each one has an associated master module. Use care when placing the master modules in the I/O chassis:

• Analog Input Expander Module (1771-E1, -E2, -E3)

• Analog Output Expander Module (1771-E4)

• Servo (Encoder Feedback) Expander Module (1771-ES)

• Pulse Output Expander Module (1771-OJ)

Publication 1747-UM013B-EN-P - January 2005

Page 26

1-18 Overview

Hardware Features

Below are the scanner’s features. You can find LED information in Chapter 6, Troubleshooting.

SCANNER

COMM FAULT

SW1

1 2 KBAUD

ONON57.6

OFF

115.2

OFF

230.4

OFF OFF

230.4

CONNECT ONE END OF

CABLE SHIELD TO CHASSIS

MOUNTING BOLT. REFER T O

USER'S MANUAL.

LINE 1

SHIELD

LINE 2

1747±SN

CAT

SERIAL NO.

Remote I/O Scanner

SLC 500

SER

FAC

)

CLASS I, GROUPS A, B, C AND D, DIV.2

FOR HAZ. LOC. A196

LISTED IND. CONT. EQ.

)

OPERATING

TEMPERATURE

CODE T3C

HOST

FRN.:

CURRENT REQUIREMENT: 600 mA @5VDC

FRN.:

PLUG

MAKE IN U.S.A.

1. Status Led Displays normal communication and fault status

2. Front Label Allows user to record configured baud rate

3. RIO Link Connector Allows for connections to RIO link devices

4. Cable Tie Slots Secures communication wiring from module

5. Self-Locking Tabs Secures module in chassis slot

6. Side Label (Nameplate) Provides module information

7. Baud Rate DIP Switch Allows user to set baud rate

Baud Rate DIP Switch

The Baud Rate DIP switch selects the RIO link baud rate. The baud rates are:

• 57.6 Kbaud

• 115.2 Kbaud

• 230.4 Kbaud

Publication 1747-UM013B-EN-P - January 2005

IMPORTANT

For proper system operation, the baud rate of all devices on the RIO link must be the same.

Page 27

Overview 1-19

LEDs

Two LEDs allow you to monitor scanner and communication status.

FAULT LED - allows you to monitor scanner status. This LED is red. The FAULT LED’s normal state is off; therefore, it is off whenever the scanner is operating properly.

COMM LED - allows you to monitor communication with all configured devices. This LED is green and its normal state is on once the processor has entered Run mode. The LED is red if there is a communication problem. The COMM LED status information is valid only when the FAULT LED is off.

RIO Link Connector

This 3-pin male connector connects the scanner to the RIO link. The Allen-Bradley repair part number is 1746-RT29.

Compatible Devices

Catalog Number Device Comments

1785-LT/x

1785-LT2

1785-LT3

1785-L30x

1785-L40x

1785-L60x

1771-ASC Remote I/O Adapter Module -

1771-ASB

1771-AM1

1771-AM2

1784-F30D

1771-RIO Remote I/O Interface Module -

(1) (2)

(1)(2)

(3) (4)

(1)

PLC- 5/15 (in adapter mode) -

PLC- 5/25 (in adapter mode) -

PLC- 5/12 (in adapter mode) -

PLC- 5/30 (in adapter mode) -

PLC- 5/40 (in adapter mode) -

PLC- 5/60 (in adapter mode) -

Remote I/O Adapter Module -

1-Slot I/O Chassis W/Integral Power Supply and Adapter

2-Slot I/O Chassis W/Integral Power Supply and Adapter

Plant Floor Terminal Remote I/O Expansion Module

Publication 1747-UM013B-EN-P - January 2005

Page 28

1-20 Overview

Catalog Number Device Comments

1771-JAB

(1)

Single Point I/O Adapter Module Single Point I/O

Adapter Module

1771-DCM Direct Communication Module -

1778-ASB

1747-DCM

2706-xxxx

2705-xxx

(1)

(1)(5)

(1)

Remote I/O Adapter Module -

Direct Communication Module -

DL40 Dataliner -

RediPANEL Requires half logical rack configuration if you want to use

stored messages.Requires half logical rack configuration if you want to use stored messages.

2711-xx

(1)

PanelView Terminal You can address PanelView Terminals as up to four full

logical racks of discrete I/O. You can also assign partial logical racks.You can address PanelView Terminals as up to four full logical racks of discrete I/O. You can also assign partial logical racks.

1336-G2

(1)

Remote I/O Adapter for 1336 AC Industrial

Drives

1395-NA

(1)

Remote I/O Adapter for 1395 DC Industrial

Drives

1791-xxx Block I/O Products The adapter is built into the block.

1747-ASB

(1)

SLC 500 Remote I/O Adapter Module -

1794-ASB Flex I/O 24VDC Remote I/O Adapter -

(1) Extended node capability

(2) In adapter mode

(3) Series A, B, and C

(4) Extended node capability for Series B and C

(5) Must be Catalog Number 2706-ExxxxxB1

Publication 1747-UM013B-EN-P - January 2005

Page 29

Chapter

Quick Start for Experienced Users

This chapter helps you to get started using the RIO Scanner. We base the procedures here on the assumption that you have a basic understanding of SLC 500 products.

You must:

• understand electronic process control

• be able to interpret the ladder logic instructions for generating

the electronic signals that control your application

Because it is a start-up guide for experienced users, this chapter does not contain detailed explanations about the procedures listed. It does, however, reference other chapters in this book where you can get more detailed information. It also references other documentation that may be helpful if you are unfamiliar with programming techniques or system installation requirements.

Required Tools and Equipment

If you have any questions, or are unfamiliar with the terms used or concepts presented in the procedural steps, always read the referenced chapters and other recommended documentation before trying to apply the information.

This chapter:

• tells you what tools and equipment you need

• lists preliminary considerations

• describes when to address, configure and program the module

• explains how to install and wire the module

• discusses system power-up procedures

Have the following tools and equipment ready:

• medium blade screwdriver

• programming equipment

• termination kit (package of resistors and ring lug included with

the scanner)

• approximately 15 inches of #20 AWG for grounding the drain shield to the SLC chassis (for Series A retrofits)

• an adequate length of RIO communication cable (Belden 9463) for your specific application

1 Publication 1747-UM013B-EN-P - January 2005

Page 30

2-2 Quick Start for Experienced Users

Procedures

1. Check the contents of the shipping box.

Unpack the module making sure that the contents include:

• RIO Scanner (Catalog Number 1747 SN)

• termination kit

If the contents are incomplete, call your local Allen-Bradley representative for assistance.

2. Ensure you chassis supports placement of the 1747-SN module.

Review the power requirements of your system to see that your chassis supports placement of the scanner module. The scanner consumes 600 mA @ 5VDC.

For modular style systems, calculate the total load on the system power supply using the procedure described in the SLC 500 Modular Hardware Style User Manual, Publication 1747-UM011.

See Chapter 3, Installation and Wiring and Appendix A Specifications in this manual.

3. Configure the module using the DIP switches.

Set the DIP switches (located on the printed circuit board) to the desired baud rate. Note that all RIO devices must be configured for the same baud rate.

Baud Rate DIP Switch Position

Switch 1 Switch 2

57.6K baud on on

115.2K baud on off

230.4K baud off on

230.4K baud off off

See Chapter 3, Installation and Wiring.

4. Insert the 1747-SN module into the chassis.

Publication 1747-UM013B-EN-P - January 2005

Page 31

Quick Start for Experienced Users 2-3

ATTENTION

Never install, remove, or wire modules with power applied to the chassis or devices wired to the module.

Make sure system power is off; then insert the scanner module into your 1746 chassis. In this example procedure, local slot 1 is selected.

See Chapter 3, Installation and Wiring.

Make sure system power is off; then insert the scanner module into your 1746 chassis. In this example procedure, local slot 1 is selected.

Top and Bottom Module Release(s)

Card Guide

5. Connect all RIO link devices.

Ensure that you:

• Daisy chain each RIO link device.

• Ground the shield drain wire to the nearest chassis mounting

bolt.

• Connect the appropriate termination resistors on each end of the link.

6. Configure the system.

Set up your system I/O configuration for the particular slot in which you installed the scanner (slot 1 in this example). If your module is not listed in your software version, select Other and enter the scanner input module ID code (13608) at the prompt on the I/O configuration display.

See Chapter 4, Configuration and Programming.

Publication 1747-UM013B-EN-P - January 2005

Page 32

2-4 Quick Start for Experienced Users

7. Enter the number of scanned words.

Enter the number of Scanned Input and Output Words using the Specialty I/O and Advanced Setup menus. The default value is 32 I/O words. You can specify less than 32 and reduce the processor scan time by transferring only the part of the input and output image that your application requires. It is important that you do not set either of these values to 0. If you do, the scanner will not work correctly.

See Chapter 4, Configuration and Programming.

8. Set the M0 - M1 and G file sizes.

Using the Specialty I/O Configuration menu, set the M1 and M0 file sizes to 32 words (48 words if using complementary I/O). (32 words is the minimum required for operation.) If you do not set the M1 and M0 file sizes to at least 32 words, the programming device will not allow you to access the M files in the SLC control program.

Set the G file size to 3 (5 if using complementary I/O) using the Specialty I/O Configuration menu. Do the programming necessary to configure the M0 and M1 Block Transfer Buffers. If you are using the block transfer (BT) function, you should set the M1 and M0 file sizes to 3,300. Ensure that you refer to chapter 5 before completing this selection.

Write the remainder of the SLC control program that specifies how your scanner will transfer data to/from the SLC processor and RIO devices.

Refer to Chapter 4, Configuration and Programming and Chapter 5, RIO Block Transfer.

9. Go through the system start-up procedure.

a. Apply power. b. Download your program to the SLC. c. Place the SLC in Run mode.

The scanner’s FAULT LED is off and the COMM LED is green, as shown below. (This is the valid LED pattern when in Run mode or after a Run mode to Program mode transition.)

Publication 1747-UM013B-EN-P - January 2005

See Chapter 3, Installation and Wiring.

Page 33

SCANNER

COMM

FAULT

Quick Start for Experienced Users 2-5

FAULT LED is off.

COMM LED is green.

Publication 1747-UM013B-EN-P - January 2005

Page 34

2-6 Quick Start for Experienced Users

Publication 1747-UM013B-EN-P - January 2005

Page 35

Installation and Wiring

This chapter contains the information necessary to:

• select the baud rate

• insert the scanner into the SLC chassis

• wire the RIO link

• power up the scanner

Chapter

Compliance to European Union Directives

If this product has the CE mark, it is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives.

EMC Directive

This product is tested to meet Council Directive 89/336/EEC Electromagnetic Compatibility (EMC) and the following standards, in whole or in part, documented in a technical construction file:

• EN 50081-2 EMC - Generic Emission Standard, Part 2 - Industrial Environment

• EN 50082-2 EMC - Generic Immunity Standard, Part 2 - Industrial Environment

This product is intended for use in an industrial environment.

1 Publication 1747-UM013B-EN-P - January 2005

Page 36

3-2 Installation and Wiring

Baud Rate Selection

Below are supported baud rates and switch positions:

Baud Rate DIP Switch Position

Switch 1 Switch 2

57.6K baud on on

115.2K baud on off

230.4K baud off on

230.4K baud off off

The figure below shows the location of the DIP switches on the scanner. Also, the DIP switch settings are shown for each baud rate.

IMPORTANT

For proper RIO link system operation, all devices must be configured for the same baud rate.

Scanner Installation

Baud Rate DIP Switch

57.6K baud 115.2K baud

230.4K baud 230.4K baud

Installation procedures for this module are the same as for any other discrete I/O or specialty module. Refer to the illustration on page 2-4 to identify chassis and module components listed in the procedures below.

Publication 1747-UM013B-EN-P - January 2005

Page 37

Installation and Wiring 3-3

ATTENTION

IMPORTANT

Insertion

Disconnect system power before attempting to install, remove, or wire the scanner.

Make sure you have set the DIP switches properly before installing the scanner.

Before installation, ensure that your modular SLC power supply has adequate reserve current capacity. The scanner requires 600 mA @ 5V dc.

1. Disconnect power.

2. Align the full-sized circuit board with the chassis card guides.

The first slot (slot 0) of the first rack is reserved for the SLC 500 processor.

3. Slide the module into the chassis until the top and bottom

latches catch.

4. Attach the RIO link cable to the connector on the front of the

module, behind the door. Ground the cable’s shield wire to a chassis mounting bracket. See the RIO link wiring illustration on page 2-4.

5. Insert the cable tie in the slots.

6. Route the cable down and away from module, securing it with

the cable tie.

7. Cover all unused slots with the Card Slot Filler, Catalog Number

1746-N2.

Publication 1747-UM013B-EN-P - January 2005

Page 38

3-4 Installation and Wiring

Module Release

Card Guide

Cable Tie

Removal

1. Disconnect power.

2. Remove all cabling.

3. Press the releases at the top and bottom of the module and slide

the module out of the chassis slot.

4. Cover all unused slots with the Card Slot Filler, Catalog Number

1746-N2.

Publication 1747-UM013B-EN-P - January 2005

Page 39

Installation and Wiring 3-5

RIO Link Wiring

The scanner is connected to other devices on the RIO link in a daisy chain (serial) configuration. There are no restrictions governing the space between each device, provided the maximum cable distance (Belden 9463) is not exceeded.

A 1/2 watt terminating resistor (included with the module) must be attached across line 1 and line 2 of the connectors at each end (scanner and last physical device) of the RIO link. The value of the resistor depends on the baud rate and extended node capability, as shown in the table that follows.

IMPORTANT

To use extended node, all devices on the RIO link must support it. Refer to each device’s user manual.

Using Extended Node Capability

Baud Rate Maximum Cable

Distance (Belden 9463)

57.6K baud 3048 meters (10,000 feet) 82 ohm 1/2 Watt

115.2K baud 1524 meters (5000 feet)

230.4K baud 762 meters (2500 feet)

Resistor Size

Brown - Green Brown - Gold

Not Using Extended Node Capability

57.6K baud 3048 meters (10,000 feet) 150 ohm 1/2 Watt

115.2K baud 1524 meters (5000 feet)

230.4K baud 762 meters (2500 feet) 82 ohm 1/2 Watt Gray

Brown - Green Brown - Gold

- Red - Black - Gold

Publication 1747-UM013B-EN-P - January 2005

Page 40

3-6 Installation and Wiring

RIO Link Connector

LINE 1 _______

SHIELD _____

LINE 2 _______

RIO Scanner

RIO Link Connector

Terminating Resistor Last Physical Device End

Terminating Resistor Scanner End

Line 1 ± Blue

Shield ± Shield

Line 2 ± Clear

Chassis Mounting Bracket

Ring Lug

Shield Drain Wire For New Installations Using Series B Scanners

Shield Drain Wire For Series A Scanner Retrofits

New Installations

To ensure a proper earth ground of the cable shield, follow these steps:

1. While the RIO link connector is plugged into the scanner and

lines 1 and 2 are connected, strip the cable back to expose enough shield drain wire to reach a chassis mounting bracket.

2. Attach the ring terminal lug (supplied) to the end of the shield

drain wire.

Publication 1747-UM013B-EN-P - January 2005

3. Attach the ring terminal lug to the SLC chassis mounting bracket.

Note that for new installations the middle (shield) terminal is not used when connecting to the scanner.

Page 41

Installation and Wiring 3-7

IMPORTANT

The RIO cable shield must be grounded at the scanner end only.

For Series A Scanner Retrofits

To eliminate the need to strip the cable back, follow these steps:

1. Attach the shield wire and a short piece of #20 AWG wire

(dotted line) to the shield lug of the RIO Link Connector.

2. Attach the other end of the #20 AWG wire to the ring terminal

lug.

3. Attach the ring terminal lug to a chassis mounting bracket.

IMPORTANT

The RIO cable shield must be grounded at the scanner end only. Ensure that the unshielded portion of the link communication wire (blue and clear) is as short as possible.

Start Up

The following steps will assist you in the start up of your RIO system.

1. Apply power to your SLC processor. If you powered down with

the SLC processor in Program, Test, or Fault mode, you will have to place your processor in Run mode.

When power is applied to your scanner it requires about three seconds to complete its power up diagnostics. During this time, the FAULT and COMM LEDs cycle on and off. After the diagnostics are complete and the SLC processor is in the Run mode, the scanner’s LEDs are in the following states:

• The FAULT LED is off.

• The COMM LED is green.

IMPORTANT

The above states are true only if the scanner is configured properly and all RIO link devices are communicating.

Publication 1747-UM013B-EN-P - January 2005

Page 42

3-8 Installation and Wiring

2. Make sure you have configured your SLC processor and

downloaded an application program. (Refer to chapter 4.)

3. Make sure power is applied to all devices on the RIO link.

Scanner Operation

Below is a description of the scanner’s operation at power up, run mode, and when changing from run mode to program or test mode.

At Power Up

At power up, the scanner’s communication LED (green LED) is off until the SLC is changed to Run or Test mode.

In Run Mode

During normal scanner operation (SLC in Run mode), the scanner’s LEDs illuminate as shown below:

SCANNER

COMM

FAULT

Publication 1747-UM013B-EN-P - January 2005

FAULT LED is off.

COMM LED is green.

When Changing From Run Mode

When the SLC processor is changed from Run mode, to Program or Test mode the following occurs:

• scanner’s COMM LED remains green.

• the scanner continues to read its input devices and send output

data to its RIO adapters.

• the scanner instructs adapters to either clear all outputs or hold them in their last state (depending on their configuration). Refer to the user manual included with each RIO device for specific information relating to the Hold Last State setting.

Page 43

Installation and Wiring 3-9

Status LEDs

IMPORTANT

If you are using Block Transfer (BT) functionality, BTs may not function on adapters in Hold Last State settings. Refer to each device’s user manual for information on BTs and Hold Last State settings.

The scanner has two LEDs that indicate its operating status, FAULT and COMM. The FAULT LED indicates the scanner’s overall status. The COMM LED indicates the RIO link communication status.

The FAULT LED is off whenever the scanner is configured and operating properly. The COMM LED state is valid only when the FAULT LED is off.

The table below provides the scanner and communication status as indicated by the FAULT and COMM LEDs.

FAULT LED COMM LED Status Information

Flashing Red Not Applicable Scanner configuration error

No RIO link communication attempted

Duplicate scanner detected on RIO link

Red Not Applicable Major fault on scanner

No RIO link communication attempted

Off Red Hardware fault detected

Off Off Scanner is operating properly

Scanner is offline (no RIO link communication attempted)

Off Green Scanner is operating properly

Scanner is online (active communication established with all devices)

Off Flashing Green Scanner is operation properly

At least one configured RIO link device is not communicating

Off Flashing Red Scanner is operating properly

None of the configured RIO link devices are communicating

Publication 1747-UM013B-EN-P - January 2005

Page 44

3-10 Installation and Wiring

Publication 1747-UM013B-EN-P - January 2005

Page 45

Chapter

Scanner Configuration and Programming

This chapter contains information necessary to:

• understand remote I/O image files

• understand RIO configuration using G files

• control and view RIO devices using the M0 and M1 files

• understand slot addressing

• quickly configure the RIO Scanner

Understanding Remote Input and Output Image Files

The SLC system allows you to assign up to 32 words of input and output image data to a scanner. This allows your scanner to access a maximum of 4 full logical racks (512 input and output points) of data from remote devices.

1 Publication 1747-UM013B-EN-P - January 2005

Page 46

4-2 Scanner Configuration and Programming

SN Series B Scanner (RIO Master)

Bit Number Decimal

Logical Rack 0

Logical Rack 1

Logical Rack 2

Logical Rack 3

Word 10

Word 1 1

Word 12

Word 13

Word 14

Word 15

Word 16

Word 17

Word 18

Word 19

Word 20

Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Word 0

Word 1 Word 2 Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Output Image

Scanner Input and Output Images

0717 10Bit Number Octal 07815

The scanner accommodates up to 32 words of output for remote devices.

Bit Number Decimal

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Word 0

Word 1 Word 2 Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 1 1

Word 12

Word 13

Word 14

Word 15

Word 16

Word 17

Word 18

Word 19

Word 20

Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Input Image

Note that some RIO devices (e.g.,

1771) use octal bit numbers.

0717 10Bit Number Octal 07815

The scanner accommodates up to 32 words of input from remote devices.

Publication 1747-UM013B-EN-P - January 2005

The illustration below shows how logical racks, logical groups, and words are allocated within the I/O image files. Note that this illustration describes the input image file. The scanner’s output image file is the same, except that its addressing scheme starts with O:e.0 and ends with 0:e.31.

Page 47

Logical Rack 0

Logical Rack 1

Logical Rack 2

Logical Rack 3

Bit Number (decimal)

Logical Rack 0 Group 0

Logical Rack 0 Group 1

Logical Rack 0 Group 2

Logical Rack 0 Group 3

Logical Rack 0 Group 4

Logical Rack 0 Group 5

Logical Rack 0 Group 6

Logical Rack 0 Group 7

Logical Rack 1 Group 0

Logical Rack 1 Group 1

Logical Rack 1 Group 2

Logical Rack 1 Group 3

Logical Rack 1 Group 4

Logical Rack 1 Group 5

Logical Rack 1 Group 6

Logical Rack 1 Group 7

Logical Rack 2 Group 0

Logical Rack 2 Group 1

Logical Rack 2 Group 2

Logical Rack 2 Group 3

Logical Rack 2 Group 4

Logical Rack 2 Group 5

Logical Rack 2 Group 6

Logical Rack 2 Group 7

Logical Rack 3 Group 0

Logical Rack 3 Group 1

Logical Rack 3 Group 2

Logical Rack 3 Group 3

Logical Rack 3 Group 4

Logical Rack 3 Group 5

Logical Rack 3 Group 6

Logical Rack 3 Group 7

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 15 Word 16

Word 17

Word 18

Word 19

Word 20 Word 21

Word 22

Word 23

Word 2

Word 25

Word 26

Word 27

Word 28

Word 29 Word 30

Word 31

Bit Number (octal)

Scanner Configuration and Programming 4-3

e = slot number of the SLC chassis containing the scanner

0123456789101112131415

SLC Input File Address

I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.15 I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

8128138148158168

86878108

8283848

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

I:e.30

I:e.31

The 1747-SN Scanner’s I/O image structure is described below:

• The I/O image file consists of four logical racks (numbered 0,1,2, and 3) of input image and four logical racks of output image.

• Each logical rack consists of eight logical groups (numbered 0, 1, 2, 3, 4, 5, 6, and 7).

• Each logical group consists of two words (an input word and an output word).

• Each word consists of two bytes (a high and a low byte). Low byte is bits 0 to 7 and high byte is bits 8 to 15.

• Each byte consists of 8 bits with each bit having the ability to control one discrete I/O point.

Publication 1747-UM013B-EN-P - January 2005

Page 48

4-4 Scanner Configuration and Programming

RIO Configuration Using G Files

When you program your SLC system you use the G file to configure the scanner’s I/O image file. Your scanner’s G file configuration is based on the devices that you have on the RIO link. G file configuration consists of setting logical device starting addresses and the logical device image size of each physical device/adapter with which the scanner communicates.

Publication 1747-UM013B-EN-P - January 2005

For RSLogix 500 version 5.50 and later, configure the 1747-BSN M0/M1 size for 5548 words so that this non-generic G file configuration screen appears after you click on the configure G file button. For RSLogix 500 versions prior to 5.50, configure the 1747-BSN M0/M1 size for 5547 words in order for this non-generic G file configuration screen to appear after you click on the configure G file button.

Neither your application program nor your programming device can access or alter the G file while online with the processor. To change the G file you must go offline into the program file, make any necessary changes, and download the program containing the altered

Page 49

Scanner Configuration and Programming 4-5

configuration. The G file consists of five words which are described below.

Word 0 - contains scanner information for the SLC processor. Your programming device automatically sets up Word 0. Do not attempt to alter word 0.

IMPORTANT

The term “primary” is used in conjunction with the term “complementary,” when referring to a complementary I/O configuration. “Primary” refers to I/O image space found in Logical Racks 0 through 3 when in complementary I/O mode and “normal” refers to the same image space (racks 0 through 3) when not in complementary I/O mode.

Word 1, Primary/Normal Logical Device Address - specifies the logical starting address of each primary/normal RIO link device. The logical address consists of the logical rack number (0, 1, 2, or 3) and starting logical group (0, 2, 4, or 6). Each bit in this word represents a logical address. To specify an address you place a 1 at the bit corresponding to the starting logical address of each logical device.

Word 2, Primary/Normal Device Logical Image Size - specifies the logical image size (amount of scanner I/O image) of the devices set in word 1. As with word 1, these bits correspond to RIO logical rack and logical group numbers. To specify image size, you place a 1 at each group a device occupies.

Word 3, Complementary Logical Device Address - specifies the logical starting address of each complementary RIO link device. The logical address consists of the logical rack number (8, 9, 10, or 11 because a complementary device is always 8 above its primary) and starting logical group (0, 2, 4, or 6). Each bit in this word represents a logical address. To specify an address you place a 1 at the bit corresponding to the starting logical address of each logical device.

Word 4, Complementary Device Logical Image Size - specifies the logical image size (amount of scanner I/O image) of the complementary devices set in word 3. As with word 3, these bits correspond to RIO logical rack and logical group numbers. To specify image size you place a 1 at each group a device occupies.

Publication 1747-UM013B-EN-P - January 2005

Page 50

4-6 Scanner Configuration and Programming

IMPORTANT

G File

Bit Number

I/O Mix, Word 0

RIO Logical Rack 3

Starting Logical Group

Primary/Normal Logical Device Address,

Primary/Normal Logical Image Size,

Complementary Logical Device Address,

Complementary Logical Image Size,

Word 1

Word 2

Word 3

Word 4

RIO Rack 3

Image Size

RIO Logical Rack 1 1

Starting Logical Group

RIO Rack 1 1

Image Size

Note: A complementary logical rack is always numbered 8 above its primary logical rack. Also, logical

racks 8, 9, 10, and 11 are sometimes referred to as

complementary logical racks 0, 1, 2, and 3.

0246

RIO Logical Rack 2

Starting Logical Group

RIO Rack 2

Image Size

RIO Logical Rack 10

Starting Logical Group

RIO Rack 10

Image Size

Setting device addresses in word 3 of the G file configures the system to operate in the complementary I/O mode. Not setting device addresses in word 3 causes the system to operate only in the primary/normal mode. If you wish to operate in the complementary mode and you only have primary devices configured, word 3 of the G file must be set to a decimal “1,” and word 4 of the G file must be equal to zero.

0123456789101112131415

Contains scanner information for the SLC.

0000010000000100

RIO Logical Rack 1

Starting Logical Group

RIO Rack 1

0246

Image Size

RIO Logical Rack 9

Starting Logical Group

RIO Rack 9

Image Size

RIO Logical Rack 0

Starting Logical Group

101

RIO Rack 0

Image Size

0246

RIO Logical Rack 8

Starting Logical Group

1 100100001000100

RIO Rack 8

Image Size

0246

Your programming device automatically sets the scanner information.

024602460246

10000001000100

Specifies the RIO starting addresses of primary/normal logical devices.

0246

100111111100111

Specifies the logical image size assigned to primary/normal logical devices set in Word 1.

024602460246

Specifies the RIO starting addresses of complementary logical devices.

0246

1001111101100111

Specifies the logical image size assigned to complementary logical devices set in Word 3.

Quarter Logical Rack Devices Full Logical Rack Device Half Logical Rack Device Three Quarter Logical Rack Device

Publication 1747-UM013B-EN-P - January 2005

Page 51

Scanner Configuration and Programming 4-7

Rules for Configuring the Scanner

General

• The smallest portion of the scanner’s I/O image that can be allocated to a single RIO device is two logical groups (1/4 logical rack).

• If a device is configured in word 1, there must be image allocated to it in word 2. This rule also applies to words 3 and 4 with the following exception: if word 3 = 1 and word 4 = 0, the complementary mode is selected even though no complementary devices are configured.

• A logical device’s starting group must begin at even group numbers (0, 2, 4, or 6). Each bit in words 2 and 4 represent an even logical group number.

Concerning Complementary I/O

• It is valid for you to have a complementary device configured even if no associated primary device exists. Also, complementary devices do not have to be the same logical image size as the primary device.

• G file words 1 and 2 can both be zero (no primary devices). However, in this case there must be at least one complementary device configured in G file words 3 and 4.

Publication 1747-UM013B-EN-P - January 2005

Page 52

4-8 Scanner Configuration and Programming

• If there is at least one primary device configured in G file words 1 and 2, words 3 and 4 can both be zero, or the G file size can be set to 3 (complementary mode not selected).

• The starting group of the primary and complementary chassis should be the same if they share the same image space. If the starting group is not the same, the image of the complementary device must not “cross over” into the space of a primary device.

For example, if a primary device exists at Logical Rack 1 Logical Group 4, the maximum size of a complementary device at Logical Rack 9 Logical Group 0 is a half logical rack, so its image does not cross over into Logical Group 4.

• A complementary device cannot be configured at locations where primary devices are configured unless they both start at the same location.

• If you configure your system so that complementary I/O is not selected (words 3 and 4 are zero), you must not set up any of the actual devices to be in the primary mode. If you do, the system will flag the device as faulted and prevent the device from running.

• Control functions (i.e., device inhibit, device reset, and device output reset) are only selectable for the primary device, but also apply to the complementary device. Control functions for complementary devices cannot be exclusively enabled.

Example G File Showing Primary and Complementary Device Configurations

In the example that follows, we configured the scanner to communicate with primary and complementary devices. These are the device addresses and image sizes:

• Logical Racks 0/8, Logical Group 2 contain a primary 3/4 logical rack device, and a complementary 3/4 logical rack device.

• Logical Racks 1/9, Logical Group 0 contain no primary device, and a complementary 1/2 logical rack device.

• Logical Racks 1/9, Logical Group 6 contain a primary 1/4 logical rack device, and a complementary 1/4 logical rack device.

• Logical Racks 2/10, Logical Group 0 contain a primary 3/4 logical rack device, and a complementary 1/4 logical rack device.

• Logical Racks 3/11, Logical Group 2 contain a primary 1/4 logical rack device, and a complementary 1/2 logical rack device.

• Logical Racks 3/11, Logical Group 6 contain a primary 1/4 logical rack device, and no complementary device.

Publication 1747-UM013B-EN-P - January 2005

Page 53

Bit Number

I/O Mix, Word 0

Primary/Normal Logical Device Address,

Word 1

G File

RIO Logical Rack 3

Starting Logical Group

RIO Logical Rack 2

Starting Logical Group

0246

Scanner Configuration and Programming 4-9

0123456789101112131415

0000010000000100

RIO Logical Rack 1

Starting Logical Group

RIO Logical Rack 0

Starting Logical Group

024602460246

010000110000101

Primary/Normal Logical Image Size,

Complementary Logical Device Address,

Complementary Logical Image Size,

Word 2

Word 3

Word 4

RIO Rack 3

Image Size

RIO Logical Rack 1 1

Starting Logical Group

RIO Rack 1 1

Image Size

RIO Rack 2

0246

Image Size

RIO Logical Rack 10

Starting Logical Group

RIO Rack 10

Image Size

RIO Rack 1

Image Size

0246

RIO Logical Rack 9

Starting Logical Group

RIO Rack 9

0246

Image Size

RIO Rack 0

Image Size

0246

RIO Logical Rack 8

Starting Logical Group

0 010100110000100

RIO Rack 8

Image Size

0246

0111000111100101

024602460246

0246

0111110110000110

Publication 1747-UM013B-EN-P - January 2005

Page 54

4-10 Scanner Configuration and Programming

Illegal Configuration Examples

Having a primary device configured at Logical Rack 1, Logical Group 2 (bit 5) would be illegal since this image space is already being used by a complementary device. Having a complementary device configured at Logical Rack 10, Logical Group 2 (bit 9) would also be illegal since this image space is already being used by a primary device.

Note that the complementary device at Logical Rack 8, Logical Group 2 could be an ASB using 10 words (1-1/4 logical racks) of data, and thereby cross into RIO Logical Rack 9.

The G file configuration on page 2-6 would provide the primary and complementary input images to the scanner, which are illustrated on the following pages. Note that the output images would be the same.

Example Scanner Input Image of the Primary Devices

Below are the primary device addresses and sizes. The following page contains complementary device addresses and sizes.

• Device 1 - starting at Logical Rack 0, Logical Group 2 is a primary 3/4 logical rack device.

• Logical Rack 1, Logical Group 0 contains no primary device.

• Device 2 - starting at Logical Rack 1, Logical Group 6 is a

primary 1/4 logical rack device.

• Device 3 - starting at Logical Rack 2, Logical Group 0 is a primary 3/4 logical rack device.

• Device 4 - starting at Logical Rack 3, Logical Group 2 is a primary 1/4 logical rack device.

• Device 5 - starting at Logical Rack 3, Logical Group 6 is a primary 1/4 logical rack device.

Publication 1747-UM013B-EN-P - January 2005

Page 55

Logical Rack 0

Logical Rack 1

Logical Rack 2

Logical Rack 3

Bit Number (decimal)

Logical Rack 0 Group 0

Logical Rack 0 Group 1

Logical Rack 0 Group 2

Logical Rack 0 Group 3

Logical Rack 0 Group 4

Logical Rack 0 Group 5

Logical Rack 0 Group 6

Logical Rack 0 Group 7

Logical Rack 1 Group 0

Logical Rack 1 Group 1

Logical Rack 1 Group 2

Logical Rack 1 Group 3

Logical Rack 1 Group 4

Logical Rack 1 Group 5

Logical Rack 1 Group 6

Logical Rack 1 Group 7

Logical Rack 2 Group 0

Logical Rack 2 Group 1

Logical Rack 2 Group 2

Logical Rack 2 Group 3

Logical Rack 2 Group 4

Logical Rack 2 Group 5

Logical Rack 2 Group 6

Logical Rack 2 Group 7

Logical Rack 3 Group 0

Logical Rack 3 Group 1

Logical Rack 3 Group 2

Logical Rack 3 Group 3

Logical Rack 3 Group 4

Logical Rack 3 Group 5

Logical Rack 3 Group 6

Logical Rack 3 Group 7

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 15

Word 16

Word 17

Word 18

Word 19

Word 20

Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Bit Number (octal)

e = slot number of the SLC chassis containing the scanner

8108118128138148158168178

Scanner Configuration and Programming 4-11

0123456789101112131415

SLC Input File Address

I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.1 1

I:e.12

I:e.13

I:e.14

I:e.15 I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

I:e.30

I:e.31

1828384858687

= not used

Device 1

Device 2

Device 3

Device 4

Device 5

Example Scanner Input Image of the Complementary Devices

Below are the complementary device addresses and sizes. The previous page contains primary device addresses and sizes.

• Device 6 - starting at Logical Rack 8, Logical Group 2 is a complementary 3/4 logical rack device.

• Device 7 - starting at Logical Rack 9, Logical Group 0 is a complementary 1/2 logical rack device.

• Device 8 - starting at Logical Rack 9, Logical Group 6 is a complementary 1/4 logical rack device.

• Device 9 - starting at Logical Rack 10, Logical Group 0 is a complementary 1/4 logical rack device.

• Device 10 - starting at Logical Rack 11, Logical Group 2 is a complementary 1/2 logical rack device.

• Logical Rack 11, Logical Group 6 has no complementary device.

Publication 1747-UM013B-EN-P - January 2005

Page 56

4-12 Scanner Configuration and Programming

Logical Rack 8

Logical Rack 9

Logical Rack 10

Logical Rack 11

Bit Number (decimal)

Logical Rack 8 Group 0

Logical Rack 8 Group 1

Logical Rack 8 Group 2

Logical Rack 8 Group 3

Logical Rack 8 Group 4

Logical Rack 8 Group 5

Logical Rack 8 Group 6

Logical Rack 8 Group 7

Logical Rack 9 Group 0

Logical Rack 9 Group 1

Logical Rack 9 Group 2

Logical Rack 9 Group 3

Logical Rack 9 Group 4

Logical Rack 9 Group 5

Logical Rack 9 Group 6

Logical Rack 9 Group 7

Logical Rack 10 Group 0

Logical Rack 10 Group 1

Logical Rack 10 Group 2

Logical Rack 10 Group 3

Logical Rack 10 Group 4

Logical Rack 10 Group 5

Logical Rack 10 Group 6

Logical Rack 10 Group 7

Logical Rack 1 1 Group 0

Logical Rack 1 1 Group 1

Logical Rack 1 1 Group 2

Logical Rack 1 1 Group 3

Logical Rack 1 1 Group 4

Logical Rack 1 1 Group 5

Logical Rack 1 1 Group 6

Logical Rack 1 1 Group 7

Bit Number (octal)

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5 Word 6

Word 7

Word 8

Word 9

Word 10

Word 1

Word 12

Word 13

Word 14

Word 15 Word 16

Word 17

Word 18

Word 19

Word 20

Word 21

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29 Word 30

Word 31

e = slot number of the SLC chassis containing the scanner

SLC Input

0123456789101112131415

File Address

I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.15 I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

I:e.30

I:e.31

= not used

8118128138148158168178

1828384858687810

Device 6

Device 7

Device 8

Device 9

Device 10

Considerations When Configuring Remote I/O

Publication 1747-UM013B-EN-P - January 2005

The following sections contain information that you must understand before you configure your scanner’s G file.

G File Considerations

• You can only change the RIO configuration by modifying the G file while offline in your program file. Your application program cannot access the G file, nor can you access it while online with your programming device. However, your SLC control program can dynamically inhibit and uninhibit RIO devices via the M0 file.

• RIO devices larger than 1 logical rack appear as multiple devices on the RIO link. Refer to the Crossing Logical Rack Boundaries section below.

Page 57

Scanner Configuration and Programming 4-13

• The address and size of the devices you list in the G file must match the settings of each RIO device.

Crossing Logical Rack Boundaries

You express remote I/O image boundaries in an even number of groups. For example, the 1747-ASB image can be any size from two logical groups up to 32 logical groups (four logical racks), in 2 logical group increments.

If the scanner image assigned to an adapter is greater than 8 logical groups (one logical rack), the image crosses logical rack boundaries. If the scanner image assigned to an adapter is less than 8 logical groups, it too can cross a logical rack boundary depending upon the starting logical group number. The significance of crossing logical rack boundaries is discussed in the next section.

Examples of Crossing Logical Rack Boundaries

Examples 1 and 2 that follow show adapters with logical image sizes that cross logical racks 0 and 1. The image size of the adapter in example 1 consumes all of logical rack 0 (eight logical groups) and half of logical rack 1 (four logical groups). The image size of the adapter in example 2 consumes two groups in logical rack 0 and four groups in logical rack 1.

Crossing Logical Rack Boundaries - Example 1 Crossing Logical Rack Boundaries - Example 2

Scanner Input or Output Image

Bit Number (Decimal)

Logical

Rack 0

Logical

Rack 1

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Adapter image is 12 logical groups in size and crosses a logical rack boundary due to its size.

07815

Bit Number (Decimal)

Logical

Adapter

Image

Rack 0

Logical

Rack 1

Adapter image is 6 logical groups in size and crosses a logical rack boundary due to its starting logical group number..

Scanner Input or Output Image

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

07815

Adapter

Image

Creating More than One Logical Rack Device

RIO discrete transfers occur on a logical device basis, not on an adapter basis. A logical device is any portion of a logical rack that is assigned to a single adapter.

Publication 1747-UM013B-EN-P - January 2005

Page 58

4-14 Scanner Configuration and Programming

When the scanner image assigned to an adapter is more than one logical device, the scanner sees the single physical device as multiple logical devices on the RIO link. The scanner communicates with each logical device independently, even if the logical devices are all assigned to one adapter. If a physical device image is more than one logical device, the following is true:

• The scanner does not update all of the adapter image at the same time. The number of logical devices determines the number of RIO discrete transfers that are needed to update the entire adapter image.

• The adapter may receive different communication commands for each logical device. In this case, the adapter decides which command it responds to.

Scanner Input or Output Image

In this example the adapter is configured to start at Logical Rack 0, Logical Group 0, and uses 14 words of I/O image. Note that two RIO discrete transfers are required for the scanner to update the adapter image containing two logical devices.

Understanding M Files

Bit Number (Decimal)

Logical

Rack 0

Logical Rack 1

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

07815

Logical Device

Adapter

Image

M Files Overview

The scanner provides RIO device control and status information through the M0 and M1 files. The M0 file is a control file. The M1 file is a status file

The SLC processor does not automatically update M file data during the end of the program scan as it does I/O scans. Instead, M file values act as interrupts and are immediately read from or written to upon the execution of the ladder logic instruction in which they are used. When M file data (bits or words) is addressed in the ladder program, the processor stops scanning the program to read or write the M file data to/from the scanner module. M file bits/words in the ladder program will, therefore, impact the ladder scan time. If scan time is critical, it is better to set binary file bits and copy them all at once to the M0 file, or copy a portion of the M1 file to a binary file and then address the binary file in the program. Refer to the ladder example that follows. For more information on M files, refer to

Publication 1747-UM013B-EN-P - January 2005

Page 59

Scanner Configuration and Programming 4-15

Appendix B. You can find M file information relating to Block Transfer operations in Chapter 5, Block Transfer.

Rung 2:0 To decrease program scan time, copy the first four words of the M1 File to a binary file and use these addresses throughout the program to access block transfer done, error, data, etc. information without interrupting the program scan many times. | +COP±±±±±±±±±±±±±±±±+ |±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±+COPY FILE +±| | |Source #M1:1.100| | |Dest #B3:0| | |Length 4|

| +±±±±±±±±±±±±±±±±±±±+ Rung 2:1

Rung 2:2 Examine B3/12 (an internal storage bit) to determine if a BT error occurred. Buffer the BT status from B3:3 if an error does occur. | ºBT ERRORº | | B3 +MOV±±±±±±±±±±±±±±±±+ |±±±±] [±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±+MOVE +±

| 12 |Source B3:3| | | 0000000000000000| | |Dest N10:64| | | 0| | +±±±±±±±±±±±±±±±±±±±+

Rung 2:3 | |±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±±+END+±±±±±±±±±±±±±±±±±±±±±±±±±±±±±

IMPORTANT

If you are using an SLC 5/02 processor, M file data cannot be directly monitored. To monitor M files, you must move the M file words into an SLC file that can be monitored, e.g., an integer “N” file. SLC 5/03 or later processors allow you to monitor M files directly. However, do not address M file bits more than necessary throughout your application program. The processor accesses M files like immediate I/O. Therefore, excessive addressing of M files can greatly increase SLC processor scan time. For more information on M files, refer to Appendix B.

Publication 1747-UM013B-EN-P - January 2005

Page 60

4-16 Scanner Configuration and Programming

M0 Control File Description

You can control the operation of individual devices on the RIO link with M0 word 8 through M0 word 27 (M0:e.8 through M0:e.27). Through your application program, you can use the M0 file to:

• Device Inhibit - command the 1747-SN RIO Scanner to stop scanning an RIO device by using words 8 through 11.

• Device Reset - command an RIO device’s outputs to reset while the SLC processor is in Run or Test mode by using words 16 through 19.

• Remote Output Reset - command an RIO device’s outputs to reset upon the SLC processor leaving Run mode (regardless of the RIO device’s Hold Last State setting), or while in Test mode by using words 24 through 27.

If you do not modify the Device Reset and Remote Output Reset words, the device outputs reflect the scanner output image whenever the SLC processor is in Run mode. If the SLC processor is in Program, Test, or Fault mode, it instructs the device to reset its outputs.

M file data is nonretentive. Upon entering Run or Test modes, the SLC processor sets the M0 file to a default state. The processor does not use the M0 file until a full program scan occurs (after entering Run mode). This allows you to change the M file settings before they take effect.

IMPORTANT

The 1747-SN RIO Scanner does not use M0 words 0 through 7.

Publication 1747-UM013B-EN-P - January 2005

Page 61

M0 (Control) File - RIO Device Control Words

Scanner Configuration and Programming 4-17

Output Reset Control

Device Inhibit Control

Device Reset Control

Bit Number

Logical Rack 0 Device Inhibit Word 8

Logical Rack 1 Device Inhibit Word 9

Logical Rack 2 Device Inhibit Word 10

Logical Rack 3 Device Inhibit Word 1

Logical Rack 0 Device Reset Word 16

Logical Rack 1 Device Reset Word 17

Logical Rack 2 Device Reset Word 18

Logical Rack 3 Device Reset Word 19

Logical Rack 0 Remote Output Reset Word 24

Logical Rack 1 Remote Output Reset Word 25

Logical Rack 2 Remote Output Reset Word 26

Logical Rack 3 Remote Output Reset Word 27

IMPORTANT

0123456789101112131415

M0:e.8

0110xxxxxxxxxxxx

M0:e.9

0000xxxxxxxxxxxx

M0:e.10

1001xxxxxxxxxxxx

M0:e.11

e = slot number of the SLC rack containing the scanner x = bit not used/defined

1000xxxxxxxxxxxx

M0:e.12

0000xxxxxxxxxxxx

M0:e.13

0000xxxxxxxxxxxx

M0:e.14

0000xxxxxxxxxxxx

M0:e.15

0000xxxxxxxxxxxx

1001xxxxxxxxxxxx

M0:e.16

1000xxxxxxxxxxxx

M0:e.17

0100xxxxxxxxxxxx

M0:e.18

0100xxxxxxxxxxxx

M0:e.19

Control functions (i.e., device inhibit, device reset, and device output reset) are only selectable for the primary device, but also apply to the complementary device. Control functions for complementary devices cannot be exclusively enabled.

M0 File - RIO Device Inhibit Control

M0 Words 8 through 11 - you use these words to command the scanner to stop scanning logical racks 0, 1, 2, and 3. Bits 0 to 3 in each word correspond to I/O group locations within logical racks 0, 1, 2, and 3.

To stop scanning (inhibit) a device listed in the configuration (G) file, set the bit corresponding to the starting group address of the device to

1. Setting bits that do not correspond to the device logical starting group address will not inhibit the device. To resume scanning a device, reset the bit (which corresponds to the starting group address of the device) to 0.

Inhibiting a device does not affect the current settings of the Device

Fault Status (words 12 to 15 of the M1 file). Inhibited devices eventually time out and either return to their last state or reset

(depending on the device’s last state setting).

Publication 1747-UM013B-EN-P - January 2005

Page 62

4-18 Scanner Configuration and Programming

Default: When the processor enters the Run mode, the scanner

automatically inhibits any device not configured in the G file (bit set to 1). Attempting to inhibit an unconfigured device has no effect.

Bit Number (decimal)

Logical Rack 0 Device Inhibit Word 8

Logical Rack 1 Device Inhibit Word 9

Logical Rack 2 Device Inhibit Word 10

Logical Rack 3 Device Inhibit Word 11

G File

Device Address, Word 1

M0 (Control) File

Bit Number (decimal)

Logical Rack 0 Device Inhibit Word 8

Logical Rack 1 Device Inhibit Word 9

Logical Rack 2 Device Inhibit Word 10

Logical Rack 3 Device Inhibit Word 11

M0 (Control) File Words 8 through 11

Not Defined

e = slot number of the SLC rack containing the scanner x = not used/defined

Starting Group

0246

0123456789101112131415

M0 File

0110xxxxxxxxxxxx

M0:e.8

0000xxxxxxxxxxxx

M0:e.9

1001xxxxxxxxxxxx

M0:e.10

1000xxxxxxxxxxxx

M0:e.11

Example of Device Inhibit Control

The 1747-SN Scanner inhibits (sets to 1) the bits in M0:e.8 through M0:e.11 (by default) wherever there are no configured devices present. The illustration below compares the configured devices (G file word 2) to the groups that the scanner automatically inhibits.

0246

RIO Logical Rack 0

Starting Group

0246

1001111101100111

0123456789101112131415

M0 File

0110xxxxxxxxxxxx

M0:e.8

0000xxxxxxxxxxxx

M0:e.9

1001xxxxxxxxxxxx

M0:e.10

1000xxxxxxxxxxxx

M0:e.11

RIO Logical Rack 3

Starting Group

RIO Logical Rack 2

Starting Group

0246

e = slot number of the SLC rack containing the scanner x = not used/defined

0246

RIO Logical Rack 1

Starting Group

Publication 1747-UM013B-EN-P - January 2005

M0 File - RIO Device Reset Control

M0 Words 16 through 19 - you use these words to command a reset (0) of RIO device outputs when the SLC processor is in Run or Test mode. This allows you to selectively reset logical device outputs based on a previous condition(s) that you defined. Bits 0 to 3 correspond to the logical I/O group locations within logical racks 0, 1, 2, and 3.

To command an RIO device to a reset (0) condition (from Run or Test mode), set the bit corresponding to the starting logical address of the device to 1. Setting bits that do not correspond to a device starting

Page 63

Scanner Configuration and Programming 4-19

address will not force a reset. To remove the reset condition, reset the bit (corresponding to the device logical starting address) to 0. See the mode table on page 4-22.

Default: The SLC processor resets all bits in this field to 0 when it

enters Run or Test mode.

Bit Number (decimal)

Logical Rack 0 Device Reset Word 16

Logical Rack 1 Device Reset Word 17

Logical Rack 2 Device Reset Word 18

Logical Rack 3 Device Reset Word 19

G File

Device Address, Word 1

M0 (Control) File

Bit Number (decimal)

Logical Rack 0 Device Reset Word 16

Logical Rack 1 Device Reset Word 17

Logical Rack 2 Device Reset Word 18

Logical Rack 3 Device Reset Word 19

M0 (Control) File Words 16 through 19

Not Defined

e = slot number of the SLC rack containing the scanner x = bit not used/defined

Starting Group

0246

0123456789101112131415

M0 File

0000xxxxxxxxxxxx

M0:e.16

0000xxxxxxxxxxxx

M0:e.17

0000xxxxxxxxxxxx

M0:e.18

0000xxxxxxxxxxxx

M0:e.19

Example of Device Reset Control

The application has commanded the device starting at Logical Rack 0, Group 0 (M0:e.16/0) to a reset condition (bit set to 1). The default setting for all device reset bits is 0.

RIO Logical Rack 3

Starting Group

RIO Logical Rack 2

Starting Group

0246

e = slot number of the SLC rack containing the scanner x = bit not used/defined

0246

RIO Logical Rack 1

Starting Group

RIO Logical Rack 0

Starting Group

0246

00001000100

1 100

0246

0123456789101112131415

M0 File

1000xxxxxxxxxxxx

M0:e.16

0000xxxxxxxxxxxx

M0:e.17

0000xxxxxxxxxxxx

M0:e.18

0000xxxxxxxxxxxx

M0:e.19

M0 File - Remote Output Reset Control

M0 Words 24 through 27 - you use these words to command a logical device to reset all of its outputs when the SLC processor leaves the Run mode and enters the Test, Program, or Fault mode (regardless of the device’s Hold Last State setting).

Resetting the bit (corresponding to the starting address of a device) to 0 allows the Hold Last State switch on the logical device to determine output operation when the SLC processor leaves the Run mode.

Publication 1747-UM013B-EN-P - January 2005

Page 64

4-20 Scanner Configuration and Programming

Setting the bit to 1 will command all outputs off (regardless of the device’s Hold Last State setting).

Only the device’s logical starting address bit matters. Setting other bits has no effect. Bits 0 to 3 correspond to I/O group locations within logical racks 0, 1, 2, and 3.

Default: When the processor enters Run or Test mode, the

scanner sets the starting address bit of each device configured in the G file to 1.

Bit Number (decimal)

Logical Rack 0 Remote Output Reset Word 24

Logical Rack 1 Remote Output Reset Word 25

Logical Rack 2 Remote Output Reset Word 26

Logical Rack 3 Remote Output Reset Word 27

ATTENTION

The use of the device’s Hold Last State switch can result in its outputs remaining energized when not under control of the SLC processor. We recommend the use of this function only by experienced SLC programmers.

M0 (Control) File Words 24 through 27

Not Defined

e = slot number of the SLC rack containing the scanner x = not used/defined

Starting Group

0246

0123456789101112131415

M0 File

M0:e.24

1001xxxxxxxxxxxx

M0:e.25

1000xxxxxxxxxxxx

M0:e.26

0100xxxxxxxxxxxx

M0:e.27

0100xxxxxxxxxxxx

Example of Remote Output Reset Control

By default the scanner sets the bits in M0:e.24 through M0:e.27 to 1 wherever there are configured devices present. This commands all devices’ outputs to reset regardless of their Hold Last State switch. The application program can remove commanded reset of devices by resetting bits to 0.

G File

Device Address, Word 1

M0 (Control) File

Bit Number (decimal)

Logical Rack 0 Remote Output Reset Word 24

Logical Rack 1 Remote Output Reset Word 25

Logical Rack 2 Remote Output Reset Word 26

Logical Rack 3 Remote Output Reset Word 27

Publication 1747-UM013B-EN-P - January 2005

RIO Rack 3

Starting Group

RIO Rack 2

Starting Group

0246

e = slot number of the SLC rack containing the scanner x = not used/defined

0246

Starting Group

RIO Rack 1

0246

RIO Rack 0

Starting Group

1 100100001000100

0246

0123456789101112131415

M0 File

1001xxxxxxxxxxxx

M0:e.24

1000xxxxxxxxxxxx

M0:e.25

0100xxxxxxxxxxxx

M0:e.26

0100xxxxxxxxxxxx

M0:e.27

Page 65

Scanner Configuration and Programming 4-21

Device Reset and Remote Output Reset Considerations

The 1747-SN Scanner Device Reset words (M0:e.16 to M0:e.19) and the Remote Output Reset words (M0:e.24 to M0:e.27) operate in conjunction with each RIO device to determine the state of that RIO device’s outputs. The output control information that the scanner sends to the RIO device depends on how you configure these bits. The RIO device acts on the output control information in accordance with its functionality and configuration. To fully understand how a specific device responds to the Device Reset and Remote Output Reset words, you must determine the operation of the RIO device. To determine RIO device output operation, refer to that device’s user manual.

ATTENTION

To properly use the Device Reset and Remote Output Reset words, you must consider the output control information sent to the devices during two SLC processor operating conditions:

When using the Device Reset and Remote Output Reset words, you must completely understand and fully test all device output operations before beginning normal system operation.

• The SLC processor is in any given mode (Run, Program, Test, or Fault).

• The SLC processor is leaving any mode and entering another.

If you modify the default settings, the Device Reset and Remote Output Reset words change. The table on the following page contains examples of what changes occur. We base the information in the table

on the assumption that the scanner’s slot is always enabled and the RIO link device is communicating with the scanner.

To determine how the Device Reset and Remote Output Reset words operate, locate the box where the row and column are headed by the modes in question. The shaded boxes represent the Device Reset and Remote Output Reset word operation while in that mode.

Example 1 - When powering up into Run mode, the scanner, by default, resets the appropriate bit in the Device Reset word to 0. The appropriate bit in the Remote Output Reset word is set to 1. As a result, the RIO link device outputs reflect the scanner’s output image.

Publication 1747-UM013B-EN-P - January 2005

Page 66

4-22 Scanner Configuration and Programming

Run Test Program

Power up

DR = 0 ROR = 1

(1)

(2)

Default values are set automatically. Outputs reflect those of the scanner output image.

Run ROR = X

DR = 0 Outputs are unchanged. DR = 1 Outputs are turned off.

Test DR = 0

ROR = 1 Default values are set automatically.

Outputs reflect those of the scanner

From This Module

output image.

Example 2 - Once the SLC processor is in Run mode, the bits in the Remote Output Reset word have no effect on the RIO link device’s outputs. Setting the appropriate bits in the Device Reset Word to 1 instructs the RIO link device to reset its outputs.

Example 3 - When going from Run to Program mode, if both of the appropriate bits in the Device Reset and Remote Output Reset words are reset to 0 before leaving Run mode, the RIO link device is instructed to decide whether to hold its last output state or to reset its outputs.

To This Module

(3)

DR = X ROR = X

DR = 0 In this instance, the last ROR = 0 state switch setting is valid.

DR = X ROR = 1 These two combinations will reset device outputs. DR = 1 ROR = X

DR = 0 In this instance, the last ROR = 0 state switch setting is valid.

Once these outputs are reset, they remain reset regardless of the DR and ROR settings.

DR = 0 In this instance, the last ROR = state switch setting is valid.

DR = X ROR = 1 These two combinations will reset device outputs. DR = 1 ROR = X

Outputs remain unchanged.

Program DR = 0

ROR = 1 Default values are set automatically. Outputs reflect those of the scanner output image.

(1) DR = Device Reset

(2) ROR = Remote Output Reset

(3) X = Setting does not matter

Publication 1747-UM013B-EN-P - January 2005

DR = X ROR = 1 These two combinations will reset device outputs. DR = 1 ROR = X

DR = 0 ROR = 1 These default values are set automatically. Outputs are reset, unless ROR is changed to 0 on the first scan.

DR = X ROR = X

Page 67

Scanner Configuration and Programming 4-23

M1 Status File Description

M1 file words 0 through 47 contain the status of all devices on the scanner’s RIO link. M1 is a read only file; do not write to this file.

Words 0 to 47 of the M1 file provide the following information:

• Word 0 (M1:e.0) - general communication status (overall device fault and communications attempted)

• Word 2 (M1:e.2) - RIO baud rate status

• Word 3 (M1:e.3) - complementary device starting address status

• Word 4 (M1:e.4) - complementary logical image size status

• Word 5 (M1:e.5) - complementary active device status

• Word 8 (M1:e.8) - primary/normal device starting address status

• Word 9 (M1:e.9) - primary/normal logical image size status

• Word 10 (M1:e.10) - active device status

• Words 12-15 (M1:e.12 -15) - device fault status

• Words 16-31 (M1:e.16-31) - primary/normal device retry

counters

• Words 32-47 (M1:e.32-47) - complementary device retry counters

M1 (Status) File Word 0

Bit Number (decimal)

General Communication Status Word, Word 0

General Communication Status - Enable Device Fault Bit

Word 0, bit 0 - is the Enabled Device Fault status bit. When any enabled device is faulted, this bit is set to 1. A fault may be caused by a communication problem with a remote device.

0123456789101112131415

M1 File

11xxxxxxxxxxxxxx

M1:e.0

Enabled Device Fault Bit

General Communication Status - Communication Attempted Bit

Word 0, bit 1 - is the Communications Attempted status bit. When RIO communication has been attempted with all configured devices, this bit is set to 1. There are no further transitions of this bit until a processor change of state occurs (i.e., Program mode to Run mode or Test mode, or Test mode to Run mode).

Until this bit is set, all devices in M1 file word 10 (active device status) appear to be inactive. This bit can be used to condition the Enabled

Publication 1747-UM013B-EN-P - January 2005

Page 68

4-24 Scanner Configuration and Programming

M1 (Status) File Word 0

Bit Number (decimal)

General Communication Status Word, Word 0

Device Fault bit. If the Communications Attempted bit is 1, the Enabled Device Fault bit is valid.

0123456789101112131415

11xxxxxxxxxxxxxx

M1 File

M1:e.0

RIO Baud Rate Status

Word 2, bits 0 to 1 - displays the RIO communication/baud rate you have set the scanner to via its DIP switch. Writing to word 2 does not change the scanner baud rate.

M1 (Status) File - W ord 2

Bit Number (decimal)

RIO Baud Rate, Word 2

As illustrated by the table below, bit 0 = SW1 and bit 1 = SW2.

Bit 1 - 0 Baud Rate SW 1 - 2

Communications Attempted Status Bit

Baud Rate

Enable Device Fault Bit

0123456789101112131415

M1 File

10xxxxxxxxxxxxxx

M1:e.2

Publication 1747-UM013B-EN-P - January 2005

11 57.6K Baud 11

01 115.2K Baud 10

10 230.4K Baud 01

00 230.4K Baud 00

Logical Device Starting Address Status

Word 8 - provides status/feedback of the logical device starting addresses you configured in word 1 of the G file (primary/normal logical devices). Writing to M1 file word 8 will not alter the contents of the G file.

Page 69

M1 (Status) File - W ord 8

Scanner Configuration and Programming 4-25

Bit Number (decimal)

Primary Logical Device Address, Word 8

G File - W ord 1

Primary Logical Device Address, Word 1

RIO Logical Rack 3

Starting Group 2

M1 (Status) File - W ord 3

Bit Number (decimal)

Complementary Logical Device Address,

Word 3

G File - W ord 3

Complementary Logical Device Address,

Word 3

0123456789101112131415

M1 File M1:e.8

0246

100

RIO Logical Rack 0

Starting Group 0

Starting Group

0246

RIO Logical Rack 2

Starting Group 2

Starting Group

0246

RIO Logical Rack 1

Starting Group 0

0246

0000100000

RIO Logical Rack 0

Starting Group 6

1 100100001000100

Starting Group

Word 3 - provides status/feedback of the logical device starting addresses you configured in word 3 of the G file (complementary devices). Writing to M1 file word 3 will not alter the contents of the G file.

0123456789101112131415

M1 File M1:e.3

0246

100

Starting Group

1 100100001000100

0246

Starting Group

0000100000

0246

Starting Group

0246

RIO Logical Rack 11

Starting Group 2

M1 (Status) File - W ord 9

Bit Number (decimal)

Primary Logical Device Image Size, Word 9

G File - W ord 2

Primary Logical Device Image Size, Word 2

RIO Logical Rack 10

Starting Group 2

RIO Logical Rack 9

Starting Group 0

RIO Logical Rack 8

Starting Group 6

RIO Logical Rack 8

Starting Group 0

Logical Device Image Size Status

Word 9 - provides status/feedback of the logical device image size you configure in word 2 of the G file (primary/normal devices). A bit set to 1 shows the logical image size of each logical device. Writing to word M1 file word 9 will not alter the contents of the G file.

0123456789101112131415

M1 File

M1:e.9

0246

RIO Rack 3

Image Size

0246

RIO Rack 2

Image Size

0246

RIO Rack 1

Image Size

0246

1 100111101100111

RIO Rack 0

Image Size

1 100111101100111

Publication 1747-UM013B-EN-P - January 2005

Page 70

4-26 Scanner Configuration and Programming

Bit Number (decimal)

Complementary Logical Device Image Size, Word 4

Word 4 - provides status/feedback of the logical device image size you configure in word 4 of the G file (complementary devices). A bit set to 1 shows the logical image size of each logical device. Writing to word M1 file word 4 will not alter the contents of the G file.

M1 (Status) File - W ord 4

0123456789101112131415

1 100111101100111

M1 File

M1:e.4

G File - W ord 4

Complementary Logical Device Image Size, Word 4

Active Device Status

Word 10 - provides active device status for primary/normal devices. When a RIO device is communicating with the scanner the bit corresponding to the device’s logical starting group is set to 1.

Devices that are inhibited in the M0 file (M0:e.8 through M0:e.11) are represented by a 0. Unless devices are inhibited, not responding to communications, or configured to an incorrect logical rack size, this word is identical to the device configuration (M1:e.8).

M1 (Status) File - Word 10

Bit Number (decimal)

Primary Logical Device Address, Word 8

Primary Logical Image Size, Word 9

Primary Active Device Status, Word 10

RIO Rack 11

Image Size

RIO Rack 3

Starting Group

0246

RIO Rack 10

Image Size

RIO Rack 2

Starting Group

0246

RIO Rack 9

Image Size

RIO Rack 1

Starting Group

0246

RIO Rack 8

Image Size

1 100111101100111

RIO Rack 0

Starting Group

1 100100001000100

0246

0123456789101112131415

0246

M1 File

M1:e.8

101111101100111

M1:e.9

1001100001000000

M1:e.10

Publication 1747-UM013B-EN-P - January 2005

A 0 indicates that the device is inhibited, not responding to communications, or configured to an incorrect logical rack size.

A 1 indicates that the configured device is active.

Word 5 - provides active device status for complementary devices. When a RIO device is communicating with the scanner the bit corresponding to the device’s logical starting group is set to 1.

Devices that are inhibited in the M0 file are represented by a 0. Unless devices are inhibited, not responding to communications, or configured to an incorrect logical rack size, this word is identical to the device configuration (M1:e.3).

Page 71

Scanner Configuration and Programming 4-27

M1 (Status) File - W ord 5

Bit Number (decimal)

Complementary Logical Device Address, Word 3

Complementary Logical Image Size, Word 4

Complementary Active Device Status, Word 5

IMPORTANT

When a primary device is inhibited, its complementary device is also inhibited. A complementary device cannot be exclusively inhibited.

0246

RIO Rack 10

Starting Group

RIO Rack 1 1

Starting Group

A 0 indicates that the device is inhibited, not responding to communications, or configured to an incorrect logical rack size.

Logical Device Fault Status

0246

RIO Rack 9

Starting Group

A 1 indicates that the configured device is active.

0246

1 100100001000100

RIO Rack 8

Starting Group

0123456789101112131415

0246

M1 File

M1:e.3

101111101100111

M1:e.4

1001100001000000

M1:e.5

Words 12 through 15, bits 0 to 7 - indicate the device fault status for logical racks 0, 1, 2, 3, 8, 9, 10, and 11. Bits 0 through 3 are for primary/normal devices and bits 4 through 7 are for complementary devices. Each bit corresponds to a quarter logical rack location. If a device is not responding to communications, has gone off line, or is configured to an incorrect logical rack size, all bits corresponding to the device will be set to 1. This is highlighted in the example below.

Publication 1747-UM013B-EN-P - January 2005

Page 72

4-28 Scanner Configuration and Programming

M1 (Status) File Primary/Normal Device Fault Status

Bit Number (decimal)

Primary Device Address, Word 8

Primary Device Size, Word 9

Primary Active Device Status, Word 10

The information contained in words 8, 9, and 10 indicates a three quarter logical rack device beginning at Logical Rack 3 Logical Group 2 is faulted or configured to an incorrect logical rack size. This device status is confirmed in bits 1, 2, and 3 of Device Fault Status Word

15.

Logical Rack 0 Device Fault Status Word 12

Logical Rack 1 Device Fault Status Word 13

Logical Rack 2 Device Fault Status Word 14

Logical Rack 3 Device Fault Status Word 15

RIO Rack 3

Starting Group

RIO Rack 2

Starting Group

0246

e = slot number of the SLC rack containing the scanner x = not used/defined

0246

RIO Rack 1

Starting Group

0123456789101112131415

RIO Rack 0

Starting Group

0246

00001000100

1 100

xxxxxxxxxxxx

000 0

111 0

0246

M1 File

M1:e.8

1001111101100111

M1:e.9

101100001000000

M1:e.10

M1:e.12

M1:e.13

M1:e.14

M1:e.15

M1 (Status) File Complementary Device Fault Status

Bit Number (decimal)

Complementary Device Address, Word 3

Complementary Device Size, Word 4

Complementary Active Device Status, Word 5

The information contained in word 3, 4, and 5 indicates a three quarter logical rack device beginning at group 2 is inhibited, faulted, or configured to an incorrect logical rack size. This device status is confirmed in bits 5, 6, and 7 of Device Fault Status Word 15.

Logical Rack 8 Device Fault Status Word 12

Logical Rack 9 Device Fault Status Word 13

Logical Rack 10 Device Fault Status Word 14

Logical Rack1 1 Device Fault Status Word 15

0123456789101112131415

0246

0000xxxxxxxx

0111xxxxxxxx

RIO Rack 8

Starting Group

1 100

xxx x

0246

M1 File

M1:e.3

1001111101100111

M1:e.4

101100001000000

M1:e.5

M1:e.12

M1:e.13

M1:e.14

M1:e.15

RIO Rack 1 1

Starting Group

0246

RIO Rack 9

Starting Group

RIO Rack 10

Starting Group

0246

e = slot number of the SLC rack containing the scanner x = not used/defined

00001000100

RIO Status Example

The following example illustrates an M1 status file example. It shows a typical M1 file and the G file used to configure the scanner. There are no inhibited devices specified in the M0 file (not shown). Notice that:

Publication 1747-UM013B-EN-P - January 2005

• M1:e.8 is an image of word 1 (primary/normal logical device

address) of the G file.

Page 73

Scanner Configuration and Programming 4-29

• M1:e.3 is an image of word 3 (complementary logical device

address) of the G file.

• M1:e.9 is an image/copy of word 2 (primary/normal logical

device size) of the G file.

• M1:e.4 is an image/copy of word 4 (complementary logical

device size) of the G file.

• The three quarter logical rack device located in logical rack 3

(M1:e.9/13) is not active. The fault is indicated by the Enabled Device Fault status bit, bit 0, word 0 (M1:e.0/0).

• The three quarter logical rack device located in logical rack 11

(M1:e.4/13) is not active. The fault is indicated by the Enabled Device Fault status bit, bit 0, word 0 (M1:e.0/0).

Because the device at M1:e.8/13 is faulted, bit 13 of word 10 (M1:e.10/13) is 0. M1:e.15/1 through M1:e.15/3, which correspond to M1:e.9/13 through M1:e.9/15 are also set to 1, indicating a problem with the device in logical rack 3.

Because the device at M1:e.3/13 is faulted, bit 13 of word 5 (M1:e.5/13) is 0. M1:e.15/5 through M1:e.15/7, which correspond to M1:e.4/13 through M1:e.4/15 are also set to 1, indicating a problem with the device in logical rack 11.

Bit Number (decimal)

Status Word, Word 0

Baud Rate, Word 2

Primary Device Address, Word 8

Primary Device Size, Word 9

Primary Active Device Status, Word 10

Logical Rack 0 Device Fault Status Word 12

Logical Rack 1 Device Fault Status Word 13

Logical Rack 2 Device Fault Status Word 14

Logical Rack 3 Device Fault Status Word 15

Primary Logical Device Address, Word 1

Primary Logical Image Size, Word 2

M1 (Status) File Primary/Normal

0246

RIO Logical

Rack 2

RIO Logical Rack 2

Starting Group

G File

RIO Logical

Rack 3

e = slot number of the SLC rack containing the scanner x = not used/defined

RIO Logical Rack 3

Starting Group

0246

RIO Logical

Rack 1

00001000100

RIO Logical Rack 1

Starting Group

00001000100

xxxxxxxxxxxx

0246

RIO Logical

Rack 0

1 100

RIO Logical Rack 0

Starting Group

1 100

000 0

111 0

0123456789101112131415

M1 File

11xxxxxxxxxxxxxx

M1:e.0

10xxxxxxxxxxxxxx

M1:e.2

M1:e.8

1001111101100111

M1:e.9

1001100001000000

M1:e.10

M1:e.12

M1:e.13

M1:e.14

M1:e.15

0246

1001111101100111

Publication 1747-UM013B-EN-P - January 2005

Page 74

4-30 Scanner Configuration and Programming

M1 (Status) File Complementary

Bit Number (decimal)

Status Word, Word 0

Baud Rate, Word 2

Complementary Device Starting Address, Word 3

Complementary Device Image Size, Word 4

Complementary Active Device Status, Word 5

RIO Logical

Rack 1 1

RIO Logical

Rack 10

RIO Logical

Rack 9

00001000100

0123456789101112131415

M1 File

11xxxxxxxxxxxxxx

M1:e.0

10xxxxxxxxxxxxxx

RIO Logical

Rack 8

1 100

M1:e.2

M1:e.3

1001111101100111

M1:e.4

1001100001000000

M1:e.5

Logical Rack 8 Device Fault Status Word 12

Logical Rack 9 Device Fault Status Word 13

Logical Rack 10 Device Fault Status Word 14

Logical Rack 11 Device Fault Status Word 15

Complementary Logical Device Address, Word 3

Complementary Logical Image Size, Word 4

RIO Communication Retry Counter (M1:e.16 -47)

xxx x

RIO Logical Rack 8

Starting Group

M1:e.12

M1:e.13

M1:e.14

M1:e.15

0246

1001111101100111

G File

e = slot number of the SLC rack containing the scanner x = not used/defined

RIO Logical Rack 1 1

Starting Group

IMPORTANT

0000xxxxxxxx

0111xxxxxxxx

0246

RIO Logical Rack 10

Starting Group

0246

RIO Logical Rack 9

Starting Group

00001000100

0246

1 100

Individual quarter logical racks within a device cannot be faulted. Therefore, only the starting logical group of the device needs to be monitored.

M1 File Status Words 16 through 47 - indicate how many RIO communication retries the scanner makes to each adapter on the RIO link if communication problems occur. Each word (16 through 47) contains a retry counter for each configured quarter logical rack (words 16 through 31 are for primary logical racks, 0 through 3, and 32 through 47 are for complementary racks, 8 through 11). Retry counters are useful for troubleshooting communication problems (such as electrical noise or poor communication line connections) between the scanner and any adapters. The scanner clears the retry counters when going from Program to Run mode, Test to Run mode, and when going from Program to Test mode. Note that the display (in words M1:e.16 through 31) of retry counters corresponds to the bits set in the Primary Logical Device Address - Word 1 of the G file. Likewise, the display (in words M1:e.32 through 47) correspond to the bits set in the Complementary Logical Device Address - Word 3 of the G file.

Publication 1747-UM013B-EN-P - January 2005

Page 75

Scanner Configuration and Programming 4-31

G File - P rimary

Bit Number

Primary Logical Device Address, Word 1

G File - Comp lementary

Bit Number

Complementary Logical Device Address,

Word 3

IMPORTANT

Retry Counter Example for Primary Devices

The scanner’s I/O image tables are configured as shown with M1 status files displaying the corresponding retry counters:

RIO Logical Rack 3

Starting Group

RIO Logical Rack 1 1

Starting Group

RIO Logical Rack 2

Starting Group

RIO Logical Rack 10

Starting Group

Your SLC control program cannot initialize/clear retry counters.

0123456789101112131415

RIO Logical Rack 1

Starting Group

RIO Logical Rack 9

Starting Group

RIO Logical Rack 0

Starting Group

6 4 2 0 6 4 2 0 6 4 2 0 6 4 2 0

RIO Logical Rack 8

Starting Group

6 4 2 0 6 4 2 0 6 4 2 0 6 4 2 0

101100001001001

Specifies RIO addresses for primary logical devices.

0123456789101112131415

100100010001100

Specifies RIO addresses for complementary devices.

M1:e.16 - communication retry counter for RIO logical rack 0, group 0 M1:e.17 - not used in this example M1:e.18 -communication retry counter for RIO logical rack 0, group 4 M1:e.19 - not used in this example

M1:e.20 - communication retry counter for RIO logical rack 1, group 0 M1:e.21 - not used in this example M1:e.22 - not used in this example M1:e.23 - not used in this example

M1:e.24 - not used in this example M1:e.25 - communication retry counter for RIO logical rack 2, group 2 M1:e.26 - not used in this example M1:e.27 - not used in this example

M1:e.28 - communication retry counter for RIO logical rack 3, group 0 M1:e.29 - not used in this example M1:e.30 - not used in this example M1:e.31 - communication retry counter for RIO logical rack 3, group 6

Publication 1747-UM013B-EN-P - January 2005

Page 76

4-32 Scanner Configuration and Programming

M1:e.32 - communication retry counter for RIO logical rack 8, group 0 M1:e.33 - not used in this example M1:e.34 - not used in this example M1:e.35 - not used in this example

M1:e.36 - communication retry counter for RIO logical rack 9, group 0 M1:e.37 - not used in this example M1:e.38 - not used in this example M1:e.39 - not used in this example

M1:e.40 - communication retry counter for RIO logical rack 10,

group 0

M1:e.41 - not used in this example M1:e.42 - not used in this example M1:e.43 - not used in this example

M1:e.44 - communication retry counter for RIO logical rack 11,

group 0

M1:e.45 - communication retry counter for RIO logical rack 11,

group 2

M1:e.46 - not used in this example M1:e.47 - not used in this example

Understanding Slot Addressing

This section provides information about:

• 2-slot addressing

• 1-slot addressing

• 1/2-slot addressing

Understanding slot addressing is critical to most efficiently allocate your scanner’s I/O image files.

Slot addressing refers to how each remote chassis slot is assigned a specific amount of the I/O image. The amount depends on which type of slot addressing you choose at your adapter; 2-slot, 1-slot, and 1/2-slot addressing is available, as shown below:

Publication 1747-UM013B-EN-P - January 2005

Page 77

Scanner Configuration and Programming 4-33

2-Slot Addressing

Remote Chassis

1-Slot Addressing

Remote Chassis

1/2-Slot Addressing

Remote Chassis

Input Image

Slot 1

Input Image

Two slots are addressed as one logical group.

Output Image

07815 07815

Slot 1Slot 2

One slot is addressed as one logical group.

Output Image

07815 07815

One slot is addressed as two logical groups.

Output Image

07815 07815

Slot 1

Slot 1Slot 2

Slot 1

SLC/Scanner Configuration

For more information on slot addressing, refer to your ASB module user manual.

Note that slot addressing (e.g., 1/2-, 1-, and 2-slot) may not apply to all types of RIO devices. Refer to each RIO device’s user manual to determine the type of slot addressing required.

Your SLC 5/02 processor can be programmed with an HHT

(1)

(Hand-Held Terminal). Although the configuration steps are similar, they are not identical. Therefore, the following basic steps are provided. For specific instructions, refer to the user manual included with your programming device. For more information on M and G files, refer to appendix B.

1. Locate an open slot in your SLC chassis. Remember that you

must use an SLC 5/02 or later processor.

(1) The SLC 5/03 and SLC 5/04 processors cannot be programmed with the HHT.

Publication 1747-UM013B-EN-P - January 2005

Page 78

4-34 Scanner Configuration and Programming

2. Assign the scanner to a physical slot in the SLC processor’s

chassis by selecting Scanner from the list. If the scanner selection is not available, select OTHER from the I/O Configuration Screen and enter the Code ID number: 13608.

3. Enter the number of Scanned Input and Output Words using the

Specialty I/O and Advanced Setup menus.

The default value is 32 I/O words. You can specify less than 32 and reduce the processor scan time by transferring only the part of the input and output image that your application requires.

IMPORTANT

Do not set either of these values to 0. If you do, the scanner will not work correctly.

4. Using the Specialty I/O Configuration menu, set the M1 and M0

file sizes to 32 words (48 words if using complementary I/O). 32 words is the minimum required for operation. If you do not set the M1 and M0 file sizes to at least 32 words the programming device will not allow you to access the M files in the SLC control program.

If you are using the block transfer (BT) function, you should set the M1 and M0 file sizes to 3,300. Refer to Chapter 5 before completing this selection.

5. Set the G file size to 3 (5 if using complementary I/O) using the

Specialty I/O Configuration menu.

6. Enter your setup information using the Modify G File menu.

IMPORTANT

SLC 5/02 processors scan chassis I/O slots left to right starting at slot 1, regardless of the module type. SLC 5/03 and later processors scan slots with discrete I/O modules first, left to right starting at slot 1, and then slots with specialty modules, left to right starting at slot 1.

Publication 1747-UM013B-EN-P - January 2005

Page 79

RIO Block Transfer

This chapter contains the following information:

• RIO block transfer theory of operation

• RIO block transfer general functional overview

• scanner’s block transfer buffer layout

• detailed operation of RIO block transfer

• RIO block transfer application considerations

• steps for setting up a block transfer

• quick reference for using status and control bits

• block transfer control logic examples

Chapter

RIO Block Transfer Theory of Operation

This section provides a conceptual overview of block transfer as it pertains to SLCs, RIO scanners, and remote devices. For specific functionality details, refer to Using Block Transfer Instructions (BTR and BTW) on page 5-5.

What Is RIO Block Transfer?

RIO Block Transfer is a data transfer mechanism that allows you to control the transfer of up to 64 words of data to or from a remote device over the Allen-Bradley RIO link. A Block Transfer Read (BTR) is used when a remote device transfers data to the SLC. A Block Transfer Write (BTW) is used when an SLC processor writes data to a remote device.

The diagrams on the following pages illustrate the concepts of how block transfers occur using an SLC processor, an RIO scanner, and a remote device. The first diagram illustrates the path a block transfer follows. The second and third diagrams illustrate in greater detail the theory of operation of a BTR and a BTW, respectively.

1 Publication 1747-UM013B-EN-P - January 2005

Page 80

5-2 RIO Block Transfer

RIO Block Transfer Theory of Operation - Path of Block Transfer

Chassis Backplane

SLC

Processor

(SLC 5/02 or above)

M Files

= path of a Block Transfer (BT)

Refer to the diagrams on the following pages for more details on BTR and BTW sequence of operation.

Block Transfer Write (BTW) data travels from the

M Files

RIO Scanner

SLC processor across the chassis backplane via

I/O Image

the scanner’s M files. The scanner then sends the data across the RIO link to the adapter or intelligent I/O module.

Block Transfer Read (BTR) data travels from the

RIO Link

adapter or intelligent I/O module over the RIO link to the scanner. The chassis backplane then transfers BTR data via the scanner’s M files to the SLC processor. The SLC control program processes the data once the SLC receives it from

Adapter or

the scanner.

Intelligent I/O Module

RIO Block Transfer Theory of Operation - Block Transfer Read (BTR)

Chassis Backplane

SLC 5/02 Processor (or later)

= path of the BTR

M0 file

M1 file

In this example, Logical Rack 0, Logical Group 0, Logical Slot 1 is used.

Logical

1747 RIO

Rack 0

Scanner

M Files

I/O Image

Logical Rack 3

RIO Link

Adapter or Intelligent I/O Module

One byte is consumed from the input and output image file for handshake purposes.

Input Image Output Image

Group 0

Group 2

Group 4

Group 6

Group 0

Group 2

Group 4

Group 6

Group 1

Group 3

Group 5

Group 7

Group 1

Group 7

Group 1

Group 3

Group 5

Group 7

Word 0

Word 1 Word 2 Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Slot 0

Slot 1

Slot 0

Slot 1

Publication 1747-UM013B-EN-P - January 2005

Page 81

RIO Block Transfer 5-3

The steps below detail a successful Block Transfer Read (BTR).

1. The M0 file contains BTR control information which controls

(initiates) the scanner BTR operation. (Refer to the Block Transfer Buffer Layout section for details on control information.)

2. The SLC control program initiates a block transfer read by

commanding the scanner to perform the read operation. The adapter/intelligent I/O module sends BTR data across the RIO link to the RIO scanner.

3. The scanner writes the BTR data to a unique M1 file location

that you specify. Also, one byte of the scanner’s I/O image file is used for “handshake” purposes between the scanner and the adapter/intelligent I/O module. Note that the SLC control program must never read or write to this “handshake” image space.

4. Using the M1 file and a COP instruction in the control program

the scanner transfers the BTR data to the SLC processor via the chassis backplane. The M1 file also contains BTR status information. (See the Block Transfer Buffer Layout section for details on status information.)

5. The SLC control program processes the BTR information.

Publication 1747-UM013B-EN-P - January 2005

Page 82

5-4 RIO Block Transfer

RIO Block Transfer Theory of Operation - Block Transfer Write (BTW)

SLC 5/02

Processor (or later)

= path of the BTW

Chassis Backplane

M0 file

M1 file

In this example, Logical Rack 3, Logical Group 7, Logical Slot 1 is used.

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 7

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Group 6

Word 30

Word 31

M Files

1747 RIO Scanner

I/O Image

Logical Rack 0

Logical Rack 3

RIO Link

Adapter or Intelligent I/O Module

Slot 0

Slot 1

Input Image Output Image

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

One byte is consumed from the input and output image file for handshake purposes.

Slot 0

The steps below detail a successful Block Transfer Write (BTW):

1. The user’s control program executes a MOV or COP instruction

to the M0 file to initiate a BTW. The SLC processor sends BTW data (via the chassis backplane) to the scanner’s M0 block transfer control and write data file. (See the Block Transfer Buffer Layout section for details on control information.)

2. The scanner reads the BTW data and control data from the M0

file. One byte of the scanners’s I/O image file is used for handshake purposes. Note that the SLC user program must never read or write to this image space.

3. The M1 file contains BTW status information. (See the Block

Transfer Buffer Layout section for details on the status information.)

4. The RIO scanner transfers BTW information across the RIO link

to the adapter.

5. The adapter transfers the BTW information to the appropriate

adapter or intelligent I/O module.

Publication 1747-UM013B-EN-P - January 2005

Page 83

RIO Block Transfer 5-5

Using Block Transfer Instructions (BTR and BTW)

BTR Block Transfer Read Rack 0 Group 0 Slot 0 Control Block N10:140 Data File N21:100 Buffer File M1:1.3200 Requested Word Count 0 Transmitted Word Count 0

BTW

BTW Block Transfer Write Rack 0 Group 0 Slot 0 Control Block N10:10 Data File N20:0 Buffer File M0:1.100 Requested Word Count 0 Transmitted Word Count 0

Block transfer instructions are supported by SLC 5/03 (OS302, Series C), SLC 5/04 (OS401, Series C) and SLC 5/05 (OS501, Series C) and higher processors only. For application examples for block transferring with SLC 5/02 processors, refer to Appendix D. With block-transfer instructions, you can transfer up to 64 words to or from a remote device over an Allen-Bradley Remote I/O (RIO) link. A Block Transfer Read (BTR) is used to receive data from a remote device. A Block Transfer Write (BTW) is used to send data to a remote device. The RIO Series B scanner (1747-SN) and the back-up scanner (1747-BSN) perform block transfers via M0 and M1 file buffers.

A false-to-true rung transition initiates a BTW or BTR instruction. The BTW instruction tells the processor to write data stored in the BTW Data File to a device at the specified RIO rack/group/slot address. The BTR instruction tells the processor to read data from a device at the specified RIO rack/group/slot address and store it in the BT Data File. A total of 32 block transfer buffers are available; you can execute a maximum of 32 different block transfers. The processor runs each block transfer request in the order it is requested. When the processor changes to Program mode, all pending block transfers are cancelled.

A BTR or BTW instruction writes information into its control structure address (a three-word integer Control Block) when the instruction is entered. The processor uses these values to execute the transfer.

You must enter an M1 file address into BTR Instructions and an M0 file address into BTW Instructions. However, each instruction uses both the M0 and M1 file for that buffer number (1 through 32). For example, to use the first available buffer (1) for a BTR, enter M1:e.100 into the “Buffer File” field. However, M0:e.100 is also used by this BTR. So, the next BT instruction must use another M-file buffer (2 through 32).

RIO Block Transfer General Functional Overview

The RIO scanner performs block transfers through control/status buffers allocated in the scanner’s M0 and M1 files. For BTW’s, the data stored in the File is copied into the M0 block transfer buffer, the M0 block transfer buffer is then transferred to the RIO device. The corresponding M1 block transfer buffer contains only BTW status information. For BTR’s, the M0 block transfer buffer contains only BTR control information. The actual data read from the remote device is received in the scanner’s M1 block transfer buffer. This data is then copied into the BTR Data File. A total of 32 block transfer control/status buffers exist in the M0 (output/control) and the M1 (input/status) files.

Publication 1747-UM013B-EN-P - January 2005

Page 84

5-6 RIO Block Transfer

Parameters for BTR and BTW

The instructions have the following parameters:

• Data File - The address in the SLC processor’s data file containing the BTW or BTR data.

• BTR/BTW Buffer File - Block transfer buffer file address; i.e. M0: e.x00, where “e” is the slot number of the scanner and “x” is the buffer number. The range of the buffer number is from 1 to 32. Each BTR and BTW instruction uses both the M1 and M0 files for a specific buffer number. M0 is used for BTR and BTW control and for BTW data. M1 is used for BTR and BTW status and BTR data.

• Control - The control block is an integer data file address that stores all the block transfer control and status information. The control block is three words in length. Note that these integer file addresses should not be used for any other instructions. You should provide the following information for the control structure.

– Rack - The I/O rack number (0 to 3) of the I/O chassis in

which you placed the target I/O module.

– Group - The I/O group number (0 to 7) which specifies the

position of the target I/O module in the I/O chassis. When using 1/2-slot addressing, only even group numbers are valid.

– Slot - The slot number (0 or 1) within the group. When using

2-slot addressing, the 0 slot is the low (right) slot and the 1 slot is the high (left) slot within the group. When using 1-slot or 1/2-slot addressing, always select slot 0.

– Requested Word Count - The number of words to transfer. If

you set the length to 0, the processor reserves 64 words for block transfer data. The block transfer module transfers the maximum words the adapter can handle. If you set the length from 1 to 64, the processor transfers the number of words specified.

Publication 1747-UM013B-EN-P - January 2005

TIP

The three-word control block has the following structure. Before executing a block transfer, the BTR and BTW instructions clear all status bits and initialize word 2 to 0. See Table 5.1, “Control Block Structure,” for more information.

Page 85

RIO Block Transfer 5-7

Table 5.1 Control Block Structure

1514131211109876543210

Word 0 EN ST DN ER EW TO RW Rack Group Slot

Word 1 Requested word count

Word 2 Transmitted word count/Error code

Control Status Bits

To use the BTR and BTW instructions correctly, examine the instruction’s control and status bits stored in the control structure. These bits are mapped to bits in word 0 of the control block structure.

Figure 5.1 Successful Block Transfer

Control Bits

Status Bits

Control Information

Status Information

12243

Publication 1747-UM013B-EN-P - January 2005

Page 86

5-8 RIO Block Transfer

Successful Block Transfer Read/Write

The illustration on the previous page shows a successful BT operation.

1. The SLC control program copies new data to the data file (BTW

only) and solves the BT rung true, which sets the enable (EN) bit.

2. The scanner detects that the EN bit is set, validates the control

block information, puts the BT request on the RIO link successfully, and since no other BTs are pending for the same logical rack, sets the enable waiting (EW) and start (ST) bits.

3. The scanner receives a BT reply (with no errors) from the RIO

link device, copies the received data to the data file (BTR only) and sets the done (DN) bit.

4. The SLC control program detects the DN bit, processes the BTR

data and solves the BT rung false, which clears the enable (EN) bit.

5. The scanner detects that the SLC control program has completed

processing (because the EN bit is clear) and clears the EW, ST and DN bits. At this point, the SLC control program could re-initiate the same BT operation by solving the BT rung true again.

TIP

Except for the time-out bit, TO (bit 08), do not modify any controller status bits while the block transfer is in progress.

IMPORTANT

The BTR/BTW instruction must be scanned (true or false) in order to update the control and status bits.

Publication 1747-UM013B-EN-P - January 2005

Page 87

RIO Block Transfer 5-9

Table 5.2 Control and Status Bit Descriptions

Control/Status Bit Description

Enable EN (bit 15) Block Transfer Enabled - (EN = Enabled). The processor sets/resets this bit depending on the rung state

(true/false). The processor sends the enable bit to the RIO scanner when the BTR/BTW instruction is scanned. If the BT is not waiting (EW set) and is not started (ST set), and the EN bit sees a false-to-true transition, the RIO scan triggers a BT.

Start ST (bit 14) Block Transfer Started - (ST = Started). When the instruction is scanned (true or false), the processor reads

this bit from the RIO scanner. The scanner sets this bit when the BT starts. The scanner resets this bit when the ladder logic (processor) clears the EN bit indicating the BT is finished.

Done DN (bit 13) Block Transfer Successful - (DN = Done). When this bit is set, it indicates the successful completion of a

block transfer operation. When the instruction is scanned (true or false), the processor reads the DN bit from the RIO scanner. The scanner clears the DN bit when the ladder logic (processor) clears the EN bit.

Error ER (bit 12) Block Transfer Error - (ER = Error). When this bit is set, it indicates that the process detected a failed block

transfer. When the instruction is scanned (true or false), the processor reads the ER bit from the RIO scanner. The scanner clears the ER bit when the ladder logic (processor) clears the EN bit.

Enable-waiting EW (bit 10) Block Transfer Enabled and Waiting for Block Transfer to Start - (EW = Enable Waiting). When the EW bit is

set and the ST bit is clear, this indicates that a block transfer operation is pending. When the instruction is scanned (true or false), the processor reads the EW bit from the scanner. The scanner clears the EW bit after the ladder logic (processor) clears the EN bit.

Time Out TO (bit 08) Block Transfer Time-out (TO = Time-out). You can set this bit to cancel block transfer operation by forcing the

BT to time out once the Enabled Waiting (EW) bit sets and before the RIO scanner’s internal four-second block transfer timer times out or the block transfer completes. Cancelling a block transfer causes an error (ER) bit to set and an error code of -9 to display in the control structure. Note that the Time-out (TO) bit must be cleared before initiating a new block transfer. The RIO scanner ignores a block transfer request if both TO and EN bits are set at the same time.

Read-Write RW (bit 07) Block Transfer Type. This bit is controlled by the instruction type. A “0” indicates a write operation (BTW);

a “1” indicates a read operation (BTR).

In addition to the control and status bits, the control block contains two other parameters the processor uses to execute the block transfer instructions.

Requested Word Count, Word 1 (RLEN)

This is used to configure BTR/BTW length information (0 to 64). Length is the number of BTR/BTW words read from or written to the RIO device. If RLEN = 0 for a BTW instruction, 64 words are sent. If RLEN = 0 for a BTR instruction, the actual length is determined by the RIO device responding to the block transfer read request.

Publication 1747-UM013B-EN-P - January 2005

Page 88

5-10 RIO Block Transfer

Transmitted Word Count/Error Code, Word 2 (DLEN)

Transmitted Word Count is the status of the actual number of BTW words sent or the number of BTR words received. The processor uses this number to verify the transfer. This number should match the requested word count (unless the transmitted word count is zero). If these numbers do not match, the processor sets the ER bit (bit 12). If there is an error, the processor gives the error code in Word 2 of the control structure in the form of a negative number. See Table 5.3, “BTR/BTW Error Codes,” for a list of error codes. Only one error code is stored at a time (a new error code overwrites the previous error code).

Table 5.3 BTR/BTW Error Codes

Error Code Description

0 The block transfer completed successfully.

-6 Illegal block transfer length requested.

-7 Block transfer communication error occurred when block transfer request was initiated.

-8 Error in block transfer protocol.

-9 Block Transfer Time-out - Either the SLC user program cancelled the block transfer or the scanner’s block transfer timer timed out. Note that a time-out error occurs if a block transfer is attempted at a location that is not configured for block transfer operation (e.g., requesting a block transfer for a location that is an output module).

-10 No RIO channel configured.

-11 Attempted a block transfer either to a non-configured block transfer device (i.e., an invalid logical rack, group, or slot), or at a complementary device location where there is no corresponding primary image space allocated.

-12 Attempted a block transfer to an inhibited device.

Publication 1747-UM013B-EN-P - January 2005

Page 89

RIO Block Transfer 5-11

Instruction Operation

1. The scanner processes the BTR/BTW when it detects that the

SLC control program rung, which contains the BTR/BTW, goes true.

If the RIO scanner detects any problem at this point (such as invalid block transfer control field, or unconfigured device), the control structure word 2 fills with the error code and the ER bit (bit 12) is set. If no problems occur, the EW bit (bit 10) and ST bit (bit 14) are set in the control block.

TIP

The ST bit is not set if the scanner is already in the process of block transferring data to a location within the same logical RIO rack. The ST bit is set only after any previous pending block transfers to the same logical rack are completed and the block transfer request is scheduled on the RIO link.

The SLC control program can monitor the block transfer by examining bits in word 0 of the control block. They indicate when the scanner has started processing (EW and ST) the block transfer and whether the block transfer operation completed successfully (DN) or failed (ER). The SLC control program can take different actions based on these status bits.

2. When a block transfer completes successfully, the DN bit is set.

This indicates that the block transfer control block has been updated with the actual transmitted word count. This is important for BTR instructions, because this indicates the number of valid data words received from the remote device. This data is stored in the BTR data file.

3. If the block transfer fails, the length field and the data file are

not updated. The ER bit is set and the error code field indicates the problem.

4. The SLC control program must indicate to the scanner when it is

done processing the status word in the control structure (because DN or ER was set) so the corresponding control bits can be reused for another block transfer operation. The SLC control program indicates that it is done processing the block transfer when it solves the BT rung false, which clears the EN bit in the control block.

Publication 1747-UM013B-EN-P - January 2005

Page 90

5-12 RIO Block Transfer

5. When the RIO scanner detects that the EN bit cleared, it then

clears the EW, ST and DN or ER bits, as well as the Transmitted Word Count/Error Code. This ensures that the status bits in the control block are not reflecting the results of the previous block transfer operation.

IMPORTANT

To prevent configuration conflicts, it is highly recommended that each M-file buffer (My:e.x00) should be used by only one block transfer instruction.

Programming Examples

Table 5.4 Block Transfer Programming Examples

Figure 5.2, "Directional" on page 5-13

Figure 5.3, "Directional Repeating" on page 5-13

Figure 5.4, "Directional Continuous" on page 5-14

Figure 5.5, "Bi-directional Continuous" on page 5-14

Figure 5.6, "Bi-directional Alternating" on page 5-15

Figure 5.7, "Bi-directional Alternating Repeating" on page 5-15

Publication 1747-UM013B-EN-P - January 2005

Page 91

Figure 5.2 Directional

RIO Block Transfer 5-13

Figure 5.3 Directional Repeating

Publication 1747-UM013B-EN-P - January 2005

Page 92

5-14 RIO Block Transfer

Figure 5.4 Directional Continuous

Figure 5.5 Bi-directional Continuous

Publication 1747-UM013B-EN-P - January 2005

Page 93

Figure 5.6 Bi-directional Alternating

Figure 5.7 Bi-directional Alternating Repeating

RIO Block Transfer 5-15

Publication 1747-UM013B-EN-P - January 2005

Page 94

5-16 RIO Block Transfer

Comparison to the PLC-5 BTR and BTW

Block Transfer Reads and Writes in SLC processors are quite similar to the instructions in the PLC-5. However, some differences exist between them, as shown in Table 5.5 on page 5-16.

Table 5.5 Block Transfer Comparison

SLC PLC-5

Control Block 3-element integer (N) type 5-element integer (N) type

or 1-element block transfer (BT) type.

EN (Enable Bit) Follow BT rung state. Gets set when BT rung goes

true. Remains set until the BT finishes or fails, and the BT rung goes false.

NR (No Response bit) None This bit is in control block

word 0, bit 9.

CO (Continuous bit) None This bit is in control block

word 0, bit 11.

FILE (File Number) None This word is control block

word 3.

ELEM (Element Number) None This word is control block

word 4.

Error Codes 7 error codes 11 error codes

BTR/BTW number limitation for one scanner/channel

BT Status Bits Can only change when BT

IMPORTANT

Do not manipulate the I/O image words of the RIO

32 64

Can change at any point in

rung is scanned.

the program scan.

scanner for modules to which you are block transferring. These words are used by the RIO scanner and the remote device as block transfer handshake bits. Any manipulation of them by the user program while a block transfer is in progress causes the block transfer to fail.

Publication 1747-UM013B-EN-P - January 2005

Page 95

Chapter

Troubleshooting

This chapter provides information for troubleshooting the RIO scanner.

Troubleshooting

COMM LED

(Red/Green)

SCANNER

FAULT LED

(Red)

The FAULT LED is off whenever the scanner is operating properly. The COMM LED state is valid only when the FAULT LED is off. When the scanner’s LEDs change state, use the following table to isolate the cause.

LED Condition Problem Solution

FAULT LED flashing red

FAULT LED red Hardware error on

COMM LED off SLC Processor

COMM LED flashing green

COMM LED flashing red

COMM LED red Hardware error on

G file is missing. Enter configuration

information in G file.

Invalid G file configuration.

Duplicate node detected.

scanner.

powered up in Program mode.

A device is not properly configured, connected, powered, or is faulted.

Scanner is incorrectly connected, or all devices are incorrectly configured, have no power, or are faulted.

scanner.

Check configuration for proper G file size and settings.

Disconnect the RIO link from the scanner and either cycle the scanner’s power, or re-enter the Run mode. Look for another scanner on the same network. If the condition persists, replace the scanner.

Replace scanner. 68H - 6FH

Return to Run mode.

Check the RIO link connections, power and switch settings. (A device may be too large or too small).

CHeck the RIO link wiring at the scanner. CHeck device configurations, power status, and network baud rate.

Replace scanner.

Error Code

62H

63H

64H

(2)

(1)

(1) Word 6 of the SLC processor status file contains this code. Refer to your programming device’s user manual.

(2) These conditions do not generate error indications to the SLC processor.

1 Publication 1747-UM013B-EN-P - January 2005

Page 96

6-2 Troubleshooting

Error Codes

Retry Counters

The SLC processor reports error codes in word 6 of the SLC processor status file. Below are the format of the status word and applicable error codes.

Slot Number Error Code 01H to 1EH

62H - G File is missing 63H - Invalid user configuration 64H - Duplicate node fault 68H to 6FH - Scanner hardware problem

For a complete description of the error codes, refer to the user manual provided with your programming device.

Electrically noisy environments can cause RIO communication problems. You can use the retry counters to determine if your scanner is having problems communicating with configured devices. To access retry counter information, you must view status file words M1:e.16 through M1:e.31 (and M1:e.32 through M1:e.47 if complementary I/O is used). These counters display the number of communication retries the scanner has made. See the section on retry counters in Chapter 4, Configuration and Programming for more detailed information.

Block Transfers

Publication 1747-UM013B-EN-P - January 2005

If you are having problems with Block Transfers, see Chapter 5, RIO Block Transfer, for information on error codes.

Page 97

Scanner Operating

Appendix

Specifications

This appendix provides scanner and system specifications, as well as throughput information. Topics include:

• scanner operating specifications

• network specifications

• throughput introduction

• calculating throughput

Specifications

Network Specifications

Backplane Current Consumption 600 mA @ 5V dc

Operating Temperature +32°F to 140°F (0°C to +60°C)

Storage Temperature -40°F to 185°F (-40°C to +85°C)

Humidity 5 to 95% without condensation

Noise Immunity NEMA Standard ICS 2-230

Agency Certification (when product or packaging is marked)

Table A.1 Baud Rate Determination of Maximum Cable Length and Terminating Resistor Size

Baud Rate Maximum Cable

Distance (Belden 9463)

• CSA certified

• CSA Class I, Division 2

Groups A, B, C, D certified

• UL listed

•

CE marked for all applicable directives

Resistor Size

Using Extended Node Capability

Not Using Extended Node Capability

1 Publication 1747-UM013B-EN-P - January 2005

57.6K baud 3048 meters (10,000 feet) 82 ohm 1/2 Watt

115.2K baud 1524 meters (5000 feet)

230.4K baud 762 meters (2500 feet)

57.6K baud 3048 meters (10,000 feet) 150 ohm 1/2 Watt

115.2K baud 1524 meters (5000 feet)

230.4K baud 762 meters (2500 feet) 82 ohm 1/2 Watt Gray

Brown - Green Brown - Gold

- Red - Black - Gold

Page 98

A-2 Specifications

Table A.2 DIP Switch Position for Baud Rate Selection

Baud Rate DIP Switch Position

Switch 1 Switch 2

57.6K baud on on

115.2K baud on off

230.4K baud off on

230.4K baud off off

Throughput Introduction

RIO throughput is defined as the time between when an input event occurs at an I/O module in an RIO chassis to when an output event occurs at an I/O module within the same RIO chassis. There are three types of throughput concerning the 1747-SN Series B Scanner and its RIO network:

• discrete throughput (time from discretely mapped input to discretely mapped output) without block transfers (BTs) present

• discrete throughput (time from discretely mapped input to discretely mapped output) with BTs present

• BT throughput (time from when a BT is enabled to when the BT successfully completes)

RIO Network Throughput Components

The following components affect RIO network throughput:

• the total SLC processor scan time

• the total RIO link scan time

• adapter(s) backplane scan time(s)

• the scanner’s output delay time

• the scanner’s input delay time

• input module delay times

• output module delay times

Publication 1747-UM013B-EN-P - January 2005

Page 99

Processor Scan

Specifications A-3

Scanner Scan

Scanner

Processor

SLC Local Chassis

ASB Backplane Scan

ASB Module

RIO Scan

Outputs to Modules

Inputs from Modules

I/O Module

Remote Chassis

Inputs to Modules

Input Device

I/O Module

Remote Expansion Chassis

Outputs from Modules

Output Device

When the SLC control program detects that the remote input has been turned on (via the scanner output image), it activates the remote output device (via the scanner output image). Throughput is then defined as the time between when the remote input device is activated to when the remote output turns on.

Calculating Throughput

The 1747-SN Series B Scanner’s throughput is determined by using the formulas provided in this section.

Discrete I/O Throughput without Block Transfers (T

dm-nbt

)

Present

The information in this section is used to calculate the discrete throughput of the 1747-SN Scanner if there are no BTs occurring on the RIO link to any chassis.

If BTs are present on the RIO link you must use the Discrete I/O Throughput with Block Transfers (T

determine your throughput. See page B-6.

The formula to calculate the maximum scanner discrete I/O throughput without BTs present is:

dm nbt–

dm-nbt

= The maximum discrete throughput without BTs in milliseconds (ms)

++++++=

RIOTadpTSNoTSNiTidTod

) Present section to

dm-bt

Publication 1747-UM013B-EN-P - January 2005

Page 100

A-4 Specifications

To calculate T

dm-nbt

throughput, substitute values for the variables in

the formula above. Locate these values in the following documents:

Variable Variable Description Location of Variable

RIO

adp

SNo

SNi

The total processor scan

Measured or estimated

time (ms)

The total RIO scan time (ms) see the section RIO Scan

Time Calculation (T

RIO

) on

page A-4

The adapter throughput

adapter user manual delay. For a 1747-ASB, this is two ASB backplane scan times.

The scanner module output delay time (ms)

see the section RIO Scanner

Output Delay Time (T

SNo

on page A-13

The scanner module input delay time (ms)

The input module delay time (ms)

5 ms (constant value for all

formulas in this appendix)

I/O product data and I/O

instruction sheets

)

RIO Scan Time Calculation (T

The output module delay time (ms)

)

RIO

I/O product data and I/O

instruction sheets

The RIO scan time is calculated by identifying the baud rate and image size of each logical device on the RIO link. Locate the corresponding time value in the following table. If you are using multiple logical devices, add the time values together to determine the total RIO scan time (T

RIO

Adapter Size Baud Rate

1/4 logical rack 6.0 ms 3.5 ms 2.5 ms

1/2 logical rack 6.5 ms 4.0 ms 2.75 ms

3/4 logical rack 7.5 ms 4.5 ms 3.0 ms

adapter1Tadapter2Tadapter3

++=

57.6K 115.2K 230.4K

RIO)

RIO Scan TImes for Adapters

Publication 1747-UM013B-EN-P - January 2005

Full logical rack 9.5 ms 5.5 ms 3.5 ms

Rockwell Automation 1747-SN User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Important User Information

Summary of Changes

Table of Contents

Overview

System Overview

How the Scanner Scans Remote I/O

How the Scanner Interacts with Adapters

Scanner I/O Image Concepts

Hardware Features

Quick Start for Experienced Users

Required Tools and Equipment

Procedures

Installation and Wiring

Compliance to European Union Directives

Baud Rate Selection

Scanner Installation

RIO Link Wiring

Start Up

Scanner Operation

Status LEDs

Scanner Configuration and Programming

Understanding Remote Input and Output Image Files

RIO Configuration Using G Files

Considerations When Configuring Remote I/O

Understanding M Files

Device Reset and Remote Output Reset Considerations

M1 Status File Description

RIO Communication Retry Counter (M1:e.16 -47)

Understanding Slot Addressing

SLC/Scanner Configuration

RIO Block Transfer

RIO Block Transfer Theory of Operation

Using Block Transfer Instructions (BTR and BTW)

Troubleshooting

Troubleshooting

Error Codes

Retry Counters

Block Transfers

Specifications

• scanner operating specifications

Network Specifications

Throughput Introduction

Calculating Throughput