Allen-Bradley 1747-SN User Manual

Allen-Bradley 1747-SN is a Remote I/O (RIO) scanner that provides a flexible and cost-effective way to connect remote I/O devices to a host controller. It supports a wide range of I/O modules, allowing you to customize your system to meet your specific needs.

PDF Download

Document

AllenBradley

Remote I/O

Scanner

(Cat. No. 1747SN)

User

Manual

Important User

Information

Because of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example.

Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the

Application, Installation, and Maintenance of Solid-State Control

(available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley

Company, Inc., is prohibited.

Throughout this manual we use notes to make you aware of safety considerations:

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage or economic loss.

Attention statements help you to:

• identify a hazard

• avoid the hazard

• recognize the consequences

Important:

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

PLC is a registered trademark of the Allen-Bradley Company, Inc.

SLC, SLC 500, SLC 5/01, SLC 5/02, SLC 5/03, SLC 5/04, MicroLogix, PanelView, RediPANEL, Dataliner, PLC-5/15,

PLC-5/12, PLC-5/25, PLC-5/30, PLC-5/40, PLC-5/60 are trademarks of Allen-Bradley Company, Inc.

Who Should Use this

Manual

Purpose of this Manual

Preface

Read this preface to familiarize yourself with the rest of the manual.

This preface covers the following topics:

• who should use this manual

• the purpose of this manual

• conventions used in this manual

•

Allen-Bradley support

Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use

Allen-Bradley small logic controllers.

You should have a basic understanding of SLC 500 t

products. You should understand programmable controllers and be able to interpret the ladder logic instructions required to control your application. If you do not, contact your local Allen-Bradley representative for information on available training courses before using this product.

If using Advanced Programming Software (APS), we recommend that you review The APS Quick Start for New Users, Publication

9399-APSQS, before you begin.

This manual is a reference guide for the Remote I/O (RIO) scanner.

It describes the procedures you use to install, configure, and operate the 1747-SN RIO Scanner (Series B or later).

Publication 17476.6 - July 1996

P–2

Preface

Contents of this Manual

Chapter

Appendix A

Appendix B

Appendix C

Preface

Overview

Title

Quick Start for

Experienced Users

Installation and Wiring

Scanner Configuration and Programming

RIO Block Transfer

Troubleshooting

Application Examples

Specifications

M0-M1 Files and G Files

RIO Configuration

Worksheets

Contents

Describes the purpose, background, and scope of this manual. Also specifies the audience for whom this manual is intended.

Contains the system overview, RIO network overview, scanner/SLC t interaction, compatible devices, and features.

Serves as a Quick Start Guide for the RIO scanner.

Provides baud rate settings, installation instructions, and wiring information.

Provides scanner configuration information, I/O file information, and G and M file descriptions.

Describes RIO block transfer theory, M file block transfer buffer layout, block transfer examples, and how to set up block transfer operations.

Provides LED status information, troubleshooting suggestions, and error codes.

Contains application examples for various system configurations.

Contains scanner and system specifications, as well as throughput information.

Contains general information and usage of M and

G files.

Contains blank worksheets for you to use when configuring the scanner's I/O images.

Common Techniques Used in this Manual

"

The following conventions are used throughout this manual:

•

Bulleted lists such as this one provide information, not procedural steps.

•

Numbered lists provide sequential steps or hierarchical information.

•

Italic type is used for emphasis.

•

Text in this font

indicates words or phrases you should type.

•

Key names match the names shown and appear in bold, capital letters within brackets (for example,

[ENTER]

•

A function key icon matches the name of the function key you should press, such as

OFFLINE

CONFIG

EXIT .

We also use this convention to call attention to helpful information.

Publication 17476.6 - July 1996

P–4

Preface

AllenBradley Support

Allen-Bradley offers support services worldwide, with over 75

Sales/Support Offices, 512 authorized Distributors and 260 authorized Systems Integrators located throughout the United States alone, plus Allen-Bradley representatives in every major country in the world.

Local Product Support

Contact your local Allen-Bradley representative for:

• sales and order support

• product technical training

• warranty support

• support service agreements

Technical Product Assistance

If you need to contact Allen-Bradley for technical assistance, please review the information in the Troubleshooting chapter first. Then call your local Allen-Bradley representative.

Your Questions or Comments on this Manual

If you find a problem with this manual, please notify us of it on the enclosed Publication Problem Report.

If you have any suggestions for how this manual could be made more useful to you, please contact us at the address below:

Allen-Bradley Company, Inc.

Automation Group

Technical Communication, Dept. 602V, T122

P.O. Box 2086

Milwaukee, WI 53201–2086

Publication 17476.6 - July 1996

New Information

Summary of Changes

The information below summarizes the changes to this manual since the last printing in February 1995.

To help you find new information 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 sections that document new features and additional information about existing features, and shows where to find this new information.

For This New Information

CE Certification

Enhanced ladder logic programming examples

See

chapter 3,

appendix A

chapter 5

Publication 17476.6 - July 1996

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . .

New Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Who Should Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . .

Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Techniques Used in this Manual

AllenBradley Support

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local Product Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Product Assistance . . . . . . . . . . . . . . . . . . . . . . . . .

Your Questions or Comments on this Manual . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner I/O Image Division . . . . . . . . . . . . . . . . . . . . . . . . . . .

How the Scanner Scans Remote I/O . . . . . . . . . . . . . . . . . . . . . .

SLC and Scanner Asynchronous Operation . . . . . . . . . . . . . . .

How the Scanner Interacts with Adapters

Scanner I/O Image Concepts

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Scanner I/O Image . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring Data with RIO Discrete and Block Transfers . . . . . .

Physical and Logical RIO Link Specifications

Extended Node Capability

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Complementary I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Guidelines for Configuring Complementary I/O . . . . . . . . . . . . .

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

Complementary I/O: Placing Modules with 1Slot Addressing

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

. .

Summary for Placing Modules Used In Complementary I/O

Discrete Modules

. . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Complementary I/O Application Considerations . . . . . . . . . . . . .

Complementary 1771 I/O Module Details . . . . . . . . . . . . . . . . .

Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Baud Rate DIP Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Link Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Compatible Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Quick Start for Experienced Users . . . . . . . . . . . . . . . . . . .

Required Tools and Equipment

Procedures

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

2-2

Installation and Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Compliance to European Union Directives

EMC Directive

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Baud Rate Selection

Scanner Installation

Insertion

Removal

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Link Wiring

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

At Power Up

In Run Mode

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

When Changing From Run Mode

Status LEDs

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration and Programming . . . . . . . . . . . . .

Understanding Remote Input and Output Image Files

RIO Configuration Using G Files

. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

Rules for Configuring the Scanner . . . . . . . . . . . . . . . . . . . . . .

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Concerning Complementary I/O . . . . . . . . . . . . . . . . . . . . . . . .

Example G File Showing Primary and Complementary Device

Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Illegal Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . .

Example Scanner Input Image of the Primary Devices . . . . . . . .

Example Scanner Input Image of the Complementary Devices . .

Considerations When Configuring Remote I/O

G File Considerations

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Crossing Logical Rack Boundaries . . . . . . . . . . . . . . . . . . . . .

Examples of Crossing Logical Rack Boundaries

Creating More than One Logical Rack Device

Understanding M Files

. . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M0 Control File Description . . . . . . . . . . . . . . . . . . . . . . . . . . .

M0 File - RIO Device Inhibit Control

Example of Device Inhibit Control

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

M0 File - RIO Device Reset Control

Example of Device Reset Control

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

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

Example of Remote Output Reset Control

Device Reset and Remote Output Reset Considerations

M1 Status File Description

. . . . . . . . . . . . . . . .

. . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents iii

General Communication Status - Enable Device Fault Bit . . . . .

4-21

General Communication Status - Communication Attempted Bit

4-22

RIO Baud Rate Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logical Device Starting Address Status

Logical Device Image Size Status

Active Device Status

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-22

4-23

4-24

Logical Device Fault Status

RIO Status Example

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Retry Counter Example for Primary Devices

. . . . . . . . . . . .

. . . . . . . . . . . . . . .

Understanding Slot Addressing

SLC/Scanner Configuration

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer Theory of Operation

What Is RIO Block Transfer?

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer General Functional Overview . . . . . . . . . . . . .

Scanner I/O Image Allocation For Block Transfer

Examples of BT I/O Image File Allocation

. . . . . . . . . . .

. . . . . . . . . . . . . . . . .

Scanner's Block Transfer Buffer Layout . . . . . . . . . . . . . . . . . . . .

M0 File - Block Transfer Output/Control Buffers . . . . . . . . . . . .

M0 File BT Control Buffer Layout

BT Control Flag Definitions

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

M1 File - Block Transfer Input/Status Buffers

M1 File - Input/Status BT Buffer Layout

. . . . . . . . . . . . . .

(M1:e.100 ... M1:e.3200) . . . . . . . . . . . . . . . . . . . . . . . . . .

M1 File - BTR/BTW Error Codes

(M1:e.103 ... M1:e.3203) . . . . . . . . . . . . . . . . . . . . . . . . . .

M1 File - BTR/BTW Status Flag Definitions

(M1:e.100 ... M1:e.3200) . . . . . . . . . . . . . . . . . . . . . . . . . .

Detailed Operation of RIO Block Transfer

Block Transfer Timing Diagrams

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

Successful Block Transfer Read/Write

Block Transfer Failure at Startup

. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Failure after Startup of Transmission

Across the RIO Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC Control Program Canceling a BT Once Transmitted

Across RIO Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC Control Program Canceling a BT Prior to Transmission

Across RIO Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer Application Considerations

Setting Up a Block Transfer

. . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Quick Reference to Status and Control Bits

Status Bits

. . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Control Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTR and BTW Control Logic Examples . . . . . . . . . . . . . . . . . . . .

Table of Contents

Block Transfer Read Control Logic Example

Block Transfer Write Control Logic Example

. . . . . . . . . . . . . . .

Directional Continuous Block Transfer Example . . . . . . . . . . . .

Directional Repeating Block Transfer Example . . . . . . . . . . . . .

Directional NonContinuous Block Transfer Example . . . . . . . . .

Bidirectional Continuous Block Transfer Example . . . . . . . . . . .

Bidirectional Alternating Block Transfer . . . . . . . . . . . . . . . . . .

Bidirectional Alternating Repeating Block Transfer . . . . . . . . . . .

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting

Error Codes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Retry Counters

Block Transfers

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1

6-2

Application Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RediPANEL Keypad Module

Scanner Configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Program

RediPANEL/DCM

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Program

Dataliner

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration

Example Program

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PanelView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration

Example Program

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Application Example

Scanner Configuration

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System Layout Diagram

Example Program

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Operating Specifications

Network Specifications

. . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Throughput Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Network Throughput Components . . . . . . . . . . . . . . . . . . .

Calculating Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Discrete I/O Throughput without Block Transfers

(Tdm-nbt) Present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Scan Time Calculation (TRIO) . . . . . . . . . . . . . . . . . . . . .

Example Discrete I/O Throughput without Block Transfers

Present . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Table of Contents v

Determining TSNo-bt

Determining Tbtx

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Discrete I/O Throughput with Block Transfers Present

Block Transfer Throughput

. . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Scanner Output Delay Time (TSNo) Tables . . . . . . . . . . . .

Determining the Number of Logical Racks Configured . . . . . . . .

TSNo without M0 File Writes . . . . . . . . . . . . . . . . . . . . . . . . . .

TSNo with M0 File Writes (No Block Transfers) . . . . . . . . . . . . .

M0-M1 Files and G Files . . . . . . . . . . . . . . . . . . . . . . . . . .

M0-M1 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring M0-M1 Files Using APS Software . . . . . . . . . . . . .

Addressing M0-M1 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Restrictions on Using M0M1 Data File Addresses . . . . . . . . . .

Monitoring Bit Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M0/M1 Monitoring Option Disabled

M0/M1 Monitoring Option Enabled

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . .

Transferring Data Between Processor Files and M0 or M1 Files

Access Time

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC 5/02 Processor Example . . . . . . . . . . . . . . . . . . . . . . . . .

SLC 5/03 Processor Example

SLC 5/04 Processor Example

Minimizing the Scan Time

. . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Capturing M0-M1 File Data . . . . . . . . . . . . . . . . . . . . . . . . . . .

Specialty I/O Modules with Retentive Memory . . . . . . . . . . . . . .

G Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring G Files Using APS Software . . . . . . . . . . . . . . . . .

Editing G File Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Configuration Worksheet

Directions

. . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-1

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

G-1

Chapter

Overview

System Overview

SLC 5/02 or Later

Processor

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

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 t

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 A-B 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.

RIO Scanner

(Master of the

RIO Link)

Local SLC Chassis

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

Remote Chassis

1747ASB Module

(Adapter/Slave)

Remote Expansion Chassis

Dataliner t Message Display

(Adapter/Slave)

PanelView t Operator Terminal

(Adapter/Slave)

RediPANEL t

(Adapter/Slave)

Publication 17476.6 - July 1996

1–2

Overview

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.

SLC 5/02 or Later

Processor

RIO

Scanner

The scanner transfers discrete input and output data between itself, remote adapters, and the SLC processor.

Remote adapters consist of 1746 chassis and other

AllenBradley operator interface and control devices.

Adapter 1

Half Logical

Rack

Device

Adapter 2

Quarter Logical

Rack

Device

Adapter 3

Half

Logical Rack

Device

Adapter 4

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 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)

Publication 17476.6 - July 1996

Overview

1–3

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–7.

Local I/O

Logical Rack 0

Remote I/O

(Scanner Image)

Logical Rack 1

Processor I/O Image

Logical Rack 2

Logical Group 0

Logical Group 7

Scanner I/O Image Adapter

Image

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.

Publication 17476.6 - July 1996

1–4

Overview

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

Output

Device 3

Input

Device 1

Input

Device 3

Output

Device 1

Output

Device 2

Input

Device 2

Scanner Output

Image File

Publication 17476.6 - July 1996

SLC Processor Scan Cycle

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 transfers its output file to the scanner.

Program

Overview

1–5

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.

The figure below illustrates the asynchronous operation of the SLC processor and RIO scanner.

SLC Input

Image File

Scanner

Input

Image File

Output

Image

Device 3

Input

Image

Device 3

Output

Image

Device 2

RIO Scanner Scan Cycle

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 Processor

SLC Output

Image File

Scanner Output

Image File

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

Publication 17476.6 - July 1996

1–6

Overview

How the Scanner Interacts with Adapters

Processor Scanner

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.

SLC Local Chassis

RIO Discrete

Transfers

with Adapter 1

RIO Discrete

Transfers

with Adapter 2

PanelView Operator

Terminal

RIO Discrete

Transfers

with Adapter 3

RIO Discrete

Transfers

with Adapter 4

RediPANEL

Publication 17476.6 - July 1996

Overview

1–7

Scanner I/O Image

Concepts

RIO

Logical

Rack 0

RIO

Logical

Rack 1

RIO

Logical

Rack 2

RIO

Logical

Rack 3

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 illustration below shows only the input image configuration of the scanner’s I/O image. The output image configuration is the same.

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

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

Bit Number (octal)

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

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

13 12 11 10

9 8

2 1

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

Publication 17476.6 - July 1996

1–8

Overview

SLC 5/02 or Later

Processor

RIO

Scanner

Example Scanner I/O Image

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

Device 1

Full Logical Rack

Device

Begins at Logical

Rack 0, Group 0.

Device 2

Three Quarter Logical

Rack Device

Begins at Logical

Rack 1, Group 0.

Device 3

Half Logical Rack

Device

Begins at Logical

Rack 2, Group 0.

Device 4

Quarter Logical Rack

Device

Begins at Logical

Rack 2, Group 4.

RIO

Logical

Rack 0

RIO

Logical

Rack 1

RIO

Logical

Rack 2

RIO

Logical

Rack 3

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

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

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

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Input File

Address

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

I:e.30

I:e.31

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.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.15

I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

Bit Number (octal) 17

Device 1

Device 2

Not Used

Device 3

Device 4

Not Used e = slot number of the SLC chassis containing the scanner

Publication 17476.6 - July 1996

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 I/O is used. Refer to the following section for more information on complementary I/O.

Publication 17476.6 - July 1996

1–10

Overview

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 17476.6 - July 1996

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 17476.6 - July 1996

1–12

Overview

Example 1

Example 2

Complementary I/O: Placing Modules with 2Slot Addressing

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

0 1

2 3 4

BT O

0 1 2 3 4 5

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 2slot 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.

Publication 17476.6 - July 1996

Example 1

Example 2

Overview

1–13

Complementary I/O: Placing Modules with 1Slot Addressing

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

0 1 2

3 4 5 6 7

0 1 2 3

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

I = Input Module (8 or 16point) O = Output Module (8 or 16point)

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.

Publication 17476.6 - July 1996

1–14

Overview

Example 1

Example 2

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

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

I I O O I O

01 23 45 67 01 23

O BT

O I

45 67 01 23

O I I O I O

I O

I I I I I I I I I I

01 23 45 67 01 23 45 67 01 23

O O O O O O O O O O

I = Input Module (8, 16, or 32point) O = Output Module (8, 16, or 32point)

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.

Publication 17476.6 - July 1996

Overview

1–15

Summary for Placing Modules Used In Complementary I/O

Discrete Modules

Addressing Method

2slot

Types of Modules used

8point

Placement

Install input modules opposite output modules, and output modules opposite input modules.

➀

1slot

1/2slot

8point, 16point

8point, 16point, 32 point

➀

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

Addressing Method Placement

The right slot of the primary I/O group can be another block transfer module, or an 8point input or output module.

2slot

1slot

1/2slot

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 8point output module; this slot must be empty if the corresponding slot in the primary I/O group is a block transfer module.

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 17476.6 - July 1996

1–16

Overview

I O I O I O I O

I = Input Module

O = Output Module

Slot 0 1 2 3 4 5 6 7 8

Slot Pair

1 2 3 4

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

Slot 0 1 2 3 4 5 6 7 8

Slot Pair

1 2 3 4

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

Primary Chassis I/O Image

Input Image from Primary Chassis

Output Image from Primary Chassis

Octal

Decimal

Octal

Decimal

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot Pair

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot Pair

Complementary Chassis I/O Image

Input Image from Complementary Chassis

Octal

Decimal

Output Image from Complementary Chassis

Octal

Decimal

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot Pair

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Slot Pair

= unused image space

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.

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

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Input Image

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Octal

Decimal

Slot Pair

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Output Image

Slot 4

Slot 5

Slot 6

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 7

Slot 8

Octal

Decimal

Slot Pair

Publication 17476.6 - July 1996

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).

Logical

Rack 0

Word 0

Word 1

ÉÉÉ ÉÉÉÉ

Word 2

Word 3

ÉÉÉ ÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉ ÉÉÉ Word 4

Word 5

ÉÉÉ ÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 6

Word 7

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 configured and usable

1/2 logical rack configured, but not usable for BT since

Words 4-7 are not 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 17476.6 - July 1996

1–18

Overview

Hardware Features

Below are the scanner’s features. You can find LED information in

chapter 6, Troubleshooting.

SCANNER

COMM FAULT

ÎÎ ÎÎ

FRN.: PLUG

ÎÎ ÎÎ ÎÎ

Table 2.A Hardware Features

1 Status LEDs

2 Front Label

3 RIO Link Connector

4 Cable Tie Slots

5 SelfLocking Tabs

6 Side Label (Nameplate)

7 Baud Rate DIP switch

SW1

1 2

√

1 2

OFF

OFF OFF

OFF

KBAUD

57.6

115.2

230.4

CONNECT ONE END OF

CABLE SHIELD TO CHASSIS

MOUNTING BOLT. REFER TO

USER'S MANUAL.

LINE 1

SHIELD

LINE 2

1747-SN

Displays normal communication and fault status

Allows user to record configured baud rate

Allows for connections to RIO link devices

Secures communication wiring from module

Secures module in chassis slot

Provides module information

Allows user to set baud rate

Publication 17476.6 - July 1996

Overview

1–19

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

Important:

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

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.

Publication 17476.6 - July 1996

1–20

Overview

Compatible Devices

Catalog

Number

1785LT/x ➀➁

1785LT2

➀➁

1785LT3 ➀➁

1785L30x

➀➁

1785L40x ➀➁

1785L60x ➀➁

1771ASC

1771ASB ➂➄

1771AM1 ➀

1771AM2

1784F30D ➀

1771RIO

1771JAB

➀

1771DCM

1778ASB ➀

1747DCM ➀

2706xxxx ➀➃

2705xxx

➀

2711xx

➀

Device Comments

PLC5/15 t (in adapter mode)

PLC5/25 t (in adapter mode)

PLC5/12 t (in adapter mode)

PLC5/30 t (in adapter mode)

PLC5/40 t (in adapter mode)

PLC5/60 t (in adapter mode)

Remote I/O Adapter Module

1Slot I/O Chassis W/Integral

Power Supply and Adapter

2Slot I/O Chassis W/Integral

Power Supply and Adapter

Plant Floor Terminal Remote

I/O Expansion Module

Remote I/O Interface Module

Single Point I/O Adapter Module

Direct Communication Module

Remote I/O Adapter Module

Direct Communication Module

DL40 Dataliner

RediPANEL

PanelView Terminal

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

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

You can also assign partial logical racks.

1336G2

1395NA

1791xxx

➀

Remote I/O Adapter for 1336

AC Industrial Drives

Remote I/O Adapter for 1395

DC Industrial Drives

Block I/O Products

1747ASB ➀

➀

➁

➂

➃

➄

1794ASB

SLC 500 Remote I/O Adapter

Module

Flex I/O 24VDC Remote I/O

Adapter

Extended node capability

In adapter mode

Series A, B, and C

Must be Catalog Number 2706ExxxxxB1

Extended node capability for Series B and C

The adapter is built into the block.

Publication 17476.6 - July 1996

Required Tools and

Equipment

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.

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 (All programming examples shown in this manual demonstrate the use of Allen-Bradley’s Advanced

Programming Software [APS] for personal computers.)

• 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

Publication 17476.6 - July 1996

2–2

Quick Start for Experienced Users

Procedures

Check the contents of the shipping box.

Unpack the module making sure that the contents include:

•

RIO Scanner (Catalog Number 1747 SN)

• termination kit

• user manual (Publication 17476.6)

If the contents are incomplete, call your local AllenBradley representative for assistance.

Reference

Ensure your chassis supports placement of the 1747SN 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 t Modular Hardware Style Installation & Operation Manual , Publication

17476.2, or the SLC 500 t Family System Overview , Publication 17472.30.

Reference

Chapter 3

(Installation and

Wiring)

Appendix A

(Specifications)

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

57.6K baud

115.2K baud

230.4K baud

230.4K baud on on off off

DIP Switch Position

Switch 1 Switch 2 on off on off

Reference

Chapter 3

(Installation and

Wiring)

Publication 17476.6 - July 1996

Quick Start for Experienced Users

Insert the 1747SN module into the chassis.

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.

Reference

(Chapter 3)

(Installation and

Wiring)

2–3

Top and Bottom

Module Release(s)

Card

Guide

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.

Reference

(Chapter 3)

(Installation and

Wiring)

Publication 17476.6 - July 1996

2–4

Quick Start for Experienced Users

Configure the system.

Reference

Set up your system I/O configuration for the particular slot in which you installed the scanner (slot 1 in this example). If using APS software, select the 1747 scanner from the list of modules. If it 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.

(Additional information about how to use AllenBradley's Advanced Programming Software [APS] to configure your system can be found in the APS User Manual, Publication 9399APSUM.)

Example of Software Prompt:

Chapter 4

(Configuration and

Programming) your programming software's user manual

Press ENTER to select I/O Module

Enter Module ID Code> 13608 offline SLC 5/02 File EXAMPLE

SELECT

MODULE

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.

(Additional information about how to use AllenBradley's Advanced Programming Software [APS] to configure your system can be found in the APS User Manual, Publication 9399APSUM.)

Reference

Chapter 4

(Configuration and

Programming) your programming software's user manual

Publication 17476.6 - July 1996

Quick Start for Experienced Users

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. (Complete information about how to do ladder programming using the APS software can be found in the APS User Manual, Publication

9399APSUM.)

Reference

Chapter 4

(Configuration and

Programming)

Chapter 5

(Block Transfer

Ladder

Programming

Examples)

Chapter 7

(Application

Examples) your programming software's user manual

2–5

Go through the system startup procedure.

Apply power.

Download your program to the SLC.

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.) I

SCANNER

COMM FAULT

FAULT LED is off.

COMM LED is green.

Reference

Chapter 3

(Installation and

Wiring)

Publication 17476.6 - July 1996

Compliance to European

Union Directives

Chapter

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

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.

Publication 17476.6 - July 1996

3–2

Installation and Wiring

Baud Rate Selection

Below are supported baud rates and switch positions:

Baud Rate

57.6K baud

115.2K baud

230.4K baud

230.4K baud on on off off

DIP Switch Position

Switch 1 Switch 2 on off on 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.

Baud Rate

DIP Switch

➀

57.6K baud 115.2K baud

230.4K baud 230.4K baud

➀

This is the default position as shipped from the factory.

Publication 17476.6 - July 1996

Scanner Installation

Installation and Wiring

3–3

Installation procedures for this module are the same as for any other discrete I/O or specialty module. Refer to the illustration on page

3–4 to identify chassis and module components listed in the

procedures below.

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

Important:

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

Important:

Before installation, ensure that your modular SLC power supply has adequate reserve current capacity.

The scanner requires 600 mA @ 5 volts DC.

Insertion

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. Refer to the RIO link wiring

illustration on page 3–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 17476.6 - July 1996

3–4

Installation and Wiring

RIO Link Wiring

Publication 17476.6 - July 1996

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.

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.

Installation and Wiring

3–5

Using Extended Node

Capability

Not Using Extended Node

Capability

Baud Rate

57.6K baud

115.2K baud

230.4K baud

57.6K baud

115.2K baud

230.4K baud

Maximum Cable Distance

(Belden 9463)

3048 meters (10,000 feet)

1524 meters (5,000 feet)

762 meters (2,500 feet)

3048 meters (10,000 feet)

1524 meters (5,000 feet)

762 meters (2,500 feet)

Resistor Size

82 W 1/2 Watt

150 W 1/2 Watt

Brown-Green-Brown-Gold

82 W 1/2 Watt

Gray-Red-Black-Gold

RIO Scanner

Terminating

Resistor Last Physical

Device End

RIO Link

Connector

RIO Link

Connector

Terminating

Resistor

Scanner End

LINE 1 _______

SHIELD _____

LINE 2 _______

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

For New Installations - To ensure a proper earth ground of the cable shield, follow these steps:

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.

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

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.

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:

Attach the shield wire and a short piece of #20 AWG wire (dotted line) to the shield lug of the RIO Link Connector.

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

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.

Publication 17476.6 - July 1996

3–6

Start Up

Installation and Wiring

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.

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.

Publication 17476.6 - July 1996

Scanner Operation

Installation and Wiring

3–7

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 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

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.

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.

Publication 17476.6 - July 1996

3–8

Status LEDs

Installation and Wiring

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

Flashing Red

Red

Off

Red

Off

COMM LED

Not applicable

Status Information

Scanner configuration error

No RIO link communication attempted

Duplicate scanner detected on RIO link

Major fault on scanner

No RIO link communication attempted

Hardware fault detected

Scanner is operating properly.

Scanner is offline (no RIO link communication attempted).

Scanner is operating properly.

Green

Scanner is online (active communication established with all devices).

Flashing Green Scanner is operating properly.

Flashing Red

At least one configured RIO link device is not communicating.

Scanner is operating properly.

None of the configured RIO link devices are communicating.

Publication 17476.6 - July 1996

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.

SN Series B Scanner

(RIO Master)

Output Image

Bit Number Octal

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 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

Scanner Input and Output Images

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

Note that some RIO devices (e.g.,

1771) use octal bit numbers.

Bit Number Octal

Bit Number Decimal

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Input Image

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

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

ÇÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Publication 17476.6 - July 1996

4–2

Scanner Configuration and Programming

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.

Bit Number (decimal)

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

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 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 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Bit Number (octal)

15 14

e = slot number of the SLC chassis containing the scanner

13 12 11 10 9 8 7 6 5 4 3

2 1

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

I:e.30

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

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.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–7 and high byte is bits 8–15.

•

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

Publication 17476.6 - July 1996

RIO Configuration Using G

Files

Scanner Configuration and Programming

4–3

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.

You enter G file configuration information using programming software, such as Advanced Programming Software (APS), or the

Hand-Held Terminal (HHT) if you have an SLC 5/02 processor. See

appendix B for further details.

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 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–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.

Publication 17476.6 - July 1996

4–4

Scanner Configuration and Programming

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.

Bit Number

I/O Mix, Word 0

Primary/Normal Logical Device Address,

Word 1

ÉÉ

RIO Rack 3

Image Size

4 2 0

Primary/Normal Logical Image Size,

Word 2

1 1 1 0

ÉÉ ÉÉ ÉÉÉ

Important:

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.

G File

15 14 13 12

0 0 1 0

RIO Logical Rack 3

Starting Logical Group

ÉÉ

11 10 9 8

0 0 0 0

RIO Logical Rack 2

Starting Logical Group

ÇÇ

7 6 5 4 3 2 1 0

0 0 1 0 0 0 0 0

RIO Logical Rack 1

Starting Logical Group

2 0 6

RIO Logical Rack 0

Starting Logical Group

0 1 1

ÇÇ ÉÉ

ÉÉ

ÇÇ ÉÉ ÉÉ

RIO Rack 2

Image Size

RIO Rack 1

Image Size

0 6

RIO Rack 0

Image Size

4 2

0 0

ÇÇ ÉÉÉ ÇÇ ÉÉ ÉÉ ÉÉ ÇÇ ÉÉ

Contains scanner information for the SLC.

Your programming device automatically sets the scanner information.

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

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

Complementary Logical Device Address,

Word 3

RIO Logical Rack 11

Starting Logical Group

ÉÉ

RIO Logical Rack 10

Starting Logical Group

ÇÇ

Starting Logical Group

RIO Logical Rack 9

RIO Logical Rack 8

Starting Logical Group

ÉÉ ÇÇ ÉÉ

Specifies the RIO starting addresses of complementary logical devices.

RIO Rack 1 1

Image Size

4 2 0

1 1 0 Complementary Logical Image Size,

Word 4

ÉÉ ÉÉ ÉÉÉ

RIO Rack 10

Image Size

4 2 0 6

RIO Rack 9

Image Size

4 2 0 6

1 1 0 1 1 1 1 1

RIO Rack 8

Image Size

4 2

ÇÇ ÉÉÉ ÇÇ ÉÉ ÉÉ ÉÉ ÇÇ ÉÉ

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

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.

Quarter Logical Rack Devices

Full Logical Rack Device

Half Logical Rack Device

Three Quarter Logical Rack Device

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–5

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.

•

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.

Publication 17476.6 - July 1996

4–6

Scanner Configuration and Programming

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.

Bit Number

I/O Mix, Word 0

G File

Primary/Normal Logical Device Address,

Word 1

RIO Logical Rack 3

Starting Logical Group

ÉÉÉ

RIO Logical Rack 2

Starting Logical Group

4 2

0 0

ÇÇ

RIO Logical Rack 1

Starting Logical Group

0 6

RIO Logical Rack 0

Starting Logical Group

0 0 0

ÉÉ ÇÇ

ÉÉ

ÉÉÉ

RIO Rack 3

Image Size

Primary/Normal Logical Image Size,

Word 2

ÉÉ ÉÉÉ ÉÉ

ÇÇ ÉÉ ÇÇ

ÇÇ ÉÉ ÇÇ ÉÉ ÉÉÉ ÉÉ ÇÇ

ÉÉ

RIO Rack 2

Image Size

4 2 0 6

RIO Rack 1

Image Size

4 2 0 6

RIO Rack 0

Image Size

ÇÇ ÉÉ ÇÇ ÉÉ ÉÉÉ ÉÉ ÇÇ

1 1 1 1 0 0 0 1

2 0

ÉÉ

1 0

ÉÉ

Complementary Logical Device Address,

Word 3

RIO Logical Rack 11

Starting Logical Group

2 0

ÉÉ

1 0

RIO Logical Rack 10

Starting Logical Group

4 2

ÇÇ

ÉÉ ÇÇ

RIO Logical Rack 9

Starting Logical Group

RIO Logical Rack 8

Starting Logical Group

6 4

ÉÉ ÇÇ

1 0 0

2 0

ÉÉ

1 0

ÉÉ ÇÇ ÉÉ

RIO Rack 1 1

Image Size

4 2 0

Complementary Logical Image Size,

0 1 1 0

ÉÉÉ ÉÉ ÉÉ

Word 4

ÉÉÉ ÉÉ ÉÉ

RIO Rack 10

Image Size

1 1

RIO Rack 9

Image Size

0 6

RIO Rack 8

Image Size

ÇÇ ÉÉ ÇÇ ÉÉÉ ÉÉ ÉÉ ÇÇ

4 2 0

1 0

ÉÉ

ÇÇ ÉÉ ÇÇ ÉÉÉ ÉÉ ÉÉ ÇÇ ÉÉ

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–7

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 4–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.

Publication 17476.6 - July 1996

4–8

Scanner Configuration and Programming

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.

Logical Rack 0 Group 0

Logical Rack 0 Group 1

Logical

Rack 0

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

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

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

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

Bit Number (decimal)

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 15

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

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)

15 14

e = slot number of the SLC chassis containing the scanner

13 12 11 10 9 8 7 6 5 4 3

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

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.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

Device 1

Device 2

Device 3

Device 4

Device 5

= not used

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–9

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.

Bit Number (decimal)

Logical Rack 8 Group 0

Logical Rack 8 Group 1

Logical Rack 8 Group 2

Logical

Rack 8

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

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

Logical Rack 10 Group 3

Logical Rack 10 Group 4

Logical Rack 10 Group 5

Logical Rack 10 Group 6

Logical

Rack 11

Logical Rack 10 Group 7

Logical Rack 11 Group 0

Logical Rack 11 Group 1

Logical Rack 11 Group 2

Logical Rack 11 Group 3

Logical Rack 11 Group 4

Logical Rack 11 Group 5

Logical Rack 11 Group 6

Logical Rack 11 Group 7

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 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Bit Number (octal)

15 14

e = slot number of the SLC chassis containing the scanner

13 12 11 10 9 8 7 6 5 4 3

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

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.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

Device 6

Device 7

Device 8

Device 9

Device 10

= not used

Publication 17476.6 - July 1996

4–10

Scanner Configuration and Programming

Considerations When

Configuring Remote I/O

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.

•

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.

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–11

Crossing Logical Rack Boundaries - Example 1

Scanner Input or Output Image

8 7 0

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

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

Crossing Logical Rack Boundaries - Example 2

Scanner Input or Output Image

8 7 0

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

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

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.

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.

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

8 7 0

Logical

Device

Logical

Device

Adapter

Image

Publication 17476.6 - July 1996

4–12

Scanner Configuration and Programming

Understanding M Files

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

appendix B. You can find M file information relating to Block

Transfer operations in chapter 5, Block Transfer.

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–13

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

Examine B3/13 (B3:0/13), an internal storage bit, to determine when a block transfer is done. Note that examining multiple individual M–file bits directly (every scan) can measurably increase processor scan time.

| ”BT DONE” |

| B3 +COP––––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–| |

| 13 |Source #B3:10| |

| |Dest #N10:0| |

| |Length 64| |

| +–––––––––––––––––––+ |

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 (running APS 4.02 or later) 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 17476.6 - July 1996

4–14

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 – 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 –

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 – 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 – 7.

M0 (Control) File - RIO Device Control Words

Device

Inhibit

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 11

x x x x

Output

Reset

Control

Device

Reset

Control

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 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

x x x x x x x x x x x x

x x x x

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

Important:

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.

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–15

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 – 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 – 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).

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)

M0 (Control) File Words 8 through 11

Not Defined

15 14 13 12 11 10 9 8 7

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 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

6 x x x x

5 x x x x

4 x x x x

Starting Group

4 2

2 1

M0 File

M0:e.8

M0:e.9

M0:e.10

M0:e.11

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

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.

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

15 x x x x

RIO Logical Rack 3

Starting Group

4 2 0

1 1 1 0

RIO Logical Rack 2

Starting Group

4 2 0

0 1 1 0

RIO Logical Rack 1

Starting Group

4 2 0

1 1 1 1

RIO Logical Rack 0

Starting Group

4 2 0

1 0 0 1

14 x x x x

13 x x x x

12 x x x x

11 x x x x

10 x x x x

9 x x x x

8 x x x x

7 x x x x

6 x x x x

5 x x x x

4 x x x x

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

M0 File

M0:e.8

M0:e.9

M0:e.10

M0:e.11

Publication 17476.6 - July 1996

4–16

Scanner Configuration and Programming

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 – 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 address will not force a reset. To remove the reset condition, reset the bit (corresponding to the device logical starting address) to

0. Refer to the mode table on page 4–20.

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

15 x x x x

M0 (Control) File Words 16 through 19

14 x x x x

13 x x x x

12 x x x x

11 x x x x x x x x

Not Defined

10 9 8 x x x x x x x x

7 x x x x

6 x x x x

5 x x x x

4 x x x x

Starting Group

4 2

2 1

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

M0 File

M0:e.16

M0:e.17

M0:e.18

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.

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

15 x x x x

RIO Logical Rack 3

Starting Group

4 2 0

0 0 1 0

14 x x x x

RIO Logical Rack 2

Starting Group

4 2 0

0 0 1 0

RIO Logical Rack 1

Starting Group

4 2 0

0 0 0 1

RIO Logical Rack 0

Starting Group

4 2 0

1 0 0 1

13 x x x x

12 x x x x

11 x x x x

10 x x x x

9 x x x x

8 x x x x

7 x x x x

6 x x x x

5 x x x x

4 x x x x

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

M0 File

M0:e.16

M0:e.17

M0:e.18

M0:e.19

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–17

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. 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 – 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.

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.

Bit Number (decimal)

M0 (Control) File Words 24 through 27

Not Defined

15 14 13 12 11 10 9 8 7

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 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

6 x x x x

5 x x x x

4 x x x x

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

Starting Group

4 2 0

3 2 1 0

M0 File

M0:e.24

M0:e.25

M0:e.26

M0:e.27

Publication 17476.6 - July 1996

4–18

Scanner Configuration and Programming

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

15 x x x x

RIO Rack 3

Starting Group

4 2

0 1

14 x x x x

13 x x x x

12 x x x x

RIO Rack 2

Starting Group

4 2

0 1

RIO Rack 1

Starting Group

4 2

0 0

RIO Rack 0

Starting Group

4 2

0 0

11 10 9 8 7 6 5 4 3 2 1 x x x x x x x x x x x x x x x x x x x x x x x x x

0 x x x x x x x 0 0

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

M0 File

M0:e.24

M0:e.25

M0:e.26

M0:e.27

Publication 17476.6 - July 1996

Device Reset and Remote

Output Reset

Considerations

Scanner Configuration and Programming

4–19

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: 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.

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:

•

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 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.

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.

Publication 17476.6 - July 1996

4–20

Scanner Configuration and Programming

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.

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.

Run

Power up DR = 0

ROR = 1

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 output image.

Program DR = 0

ROR = 1

Default values are set automatically.

Outputs reflect those of the scanner output image.

To this mode

Test

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 = 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 = Device Reset

ROR=Remote Output Reset

X = setting does not matter

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

Outputs remain unchanged.

DR = X

ROR = X

Program

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–21

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–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

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.

M1 (Status) File Word 0

Bit Number (decimal)

General Communication Status Word, Word 0

15 x

14 x

13 x

12 x

11 x

10 x

9 x

8 x

7 x

6 x

5 x

4 x

3 x

2 x

M1 File

M1:e.0

Enabled Device

Fault Bit

Publication 17476.6 - July 1996

4–22

Scanner Configuration and Programming

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 Device Fault bit. If the Communications Attempted bit is 1, the Enabled Device Fault bit is valid.

M1 (Status) File Word 0

Bit Number (decimal)

General Communication Status Word, Word 0

15 x

14 x

13 x

12 x

11 x

10 x

9 x

8 x

7 x

6 x

5 x

4 x

3 x

2 x

M1 File

M1:e.0

Communications

Attempted

Status Bit

Enable Device

Fault Bit

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 - Word 2

Bit Number (decimal)

RIO Baud Rate, Word 2

15 x

14 x

13 x

12 x

11 x

10 x

9 x

8 x

7 x

6 x

5 x

4 x

3 x

2 x

M1 File

M1:e.2

Baud Rate

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

Bit 1 - 0

Baud Rate

57.6 KBaud

115.2 KBaud

230.4 KBaud

SW 1 - 2

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–23

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.

M1 (Status) File - Word 8

Bit Number (decimal)

Primary Logical Device Address, Word 8

M1 File

M1:e.8

G File - Word 1

Primary Logical Device Address, Word 1

Starting Group

6 4

0 0

Starting Group

6 4 2

0 0 1

0 0

Starting Group

4 2

0 0

Starting Group

4 2

0 0

RIO Logical Rack 3

Starting Group 2

RIO Logical Rack 2

Starting Group 2

RIO Logical Rack 1

Starting Group 0

RIO Logical Rack 0

Starting Group 6

RIO Logical Rack 0

Starting Group 0

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.

M1 (Status) File - Word 3

Bit Number (decimal)

Complementary Logical Device Address,

Word 3

G File - Word 3

Complementary Logical Device Address,

Word 3

Starting Group

6 4 2

0 0 1

Starting Group

6 4 2

0 0 1

0 0

Starting Group

4 2

0 0

Starting Group

4 2

0 0

M1 File

M1:e.3

RIO Logical Rack 11

Starting Group 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

Publication 17476.6 - July 1996

4–24

Scanner Configuration and Programming

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.

M1 (Status) File - Word 9

Bit Number (decimal)

Primary Logical Device Image Size, Word 9

M1 File

M1:e.9

G File - Word 2

RIO Rack 3

Image Size

4 2

Primary Logical Device Image Size, Word 2

1 1 1

RIO Rack 2

Image Size

4 2

1 1

RIO Rack 1

Image Size

4 2

1 1

RIO Rack 0

Image Size

4 2

0 0

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 - Word 4

Bit Number (decimal)

15 14 13 12

Complementary Logical Device Image Size, Word 4

1 1 1 0

M1 File

M1:e.4

G File - Word 4

RIO Rack 11

Image Size

4 2

1 1 1

Complementary Logical Device Image Size, Word 4

RIO Rack 10

Image Size

4 2

1 1

RIO Rack 9

Image Size

4 2

1 1

RIO Rack 8

Image Size

4 2

0 0

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 – 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).

Publication 17476.6 - July 1996

Scanner Configuration and Programming

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

15 14 13

RIO Rack 3

Starting Group

4 2

10 9

RIO Rack 2

Starting Group

4 2

6 5

RIO Rack 1

Starting Group

4 2

2 1

RIO Rack 0

Starting Group

4 2

M1 File

M1:e.8

M1:e.9

M1:e.10

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.

4–25

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).

Important:

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

M1 (Status) File - Word 5

Bit Number (decimal)

Complementary Logical Device Address, Word 3

Complementary Logical Image Size, Word 4

Complementary Active Device Status, Word 5

14 13

RIO Rack 11

Starting Group

4 2

0 1 0

10 9

RIO Rack 10

Starting Group

4 2

0 1 0

6 5

RIO Rack 9

Starting Group

4 2

0 0 1

2 1

RIO Rack 8

Starting Group

4 2

0 0 1

M1 File

M1:e.3

M1:e.4

M1:e.5

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.

Publication 17476.6 - July 1996

4–26

Scanner Configuration and Programming

Logical Device Fault Status

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.

M1 (Status) File Primary/Normal Device Fault Status

Bit Number (decimal)

15 14 13 12

RIO Rack 3

Starting Group

4 2 0 6

Primary Device Address, Word 8

0 0 1 0

ÉÉ ÉÉÉ ÉÉ ÉÉ

Primary Device Size, Word 9

1 1 1 0

Primary Active Device Status, Word 10

0 0 0 0

ÉÉÉ ÉÉ ÉÉ ÉÉ

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.

ÉÉ

11 10 9 8

RIO Rack 2

Starting Group

4 2 0

7 6 5 4

RIO Rack 1

Starting Group

4 2

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 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

3 2 1 0

RIO Rack 0

Starting Group

4 2 0

1 x x

0 x 0 0 0 x 1 1 1

ÉÉ ÉÉ ÉÉ

M1 File

M1:e.8

M1:e.9

M1:e.10

M1:e.12

M1:e.13

M1:e.14

M1:e.15

ÉÉ ÉÉ ÉÉ

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

M1 (Status) File Complementary Device Fault Status

Bit Number (decimal)

15 14 13 12

RIO Rack 11

Starting Group

4 2 0 6

Complementary Device Address, Word 3

0 0 1 0

Complementary Device Size, Word 4

1 1 1 0

Complementary Active Device Status, Word 5

0 0 0 0

ÉÉ

ÉÉÉ ÉÉ ÉÉ

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.

11 10 9 8

RIO Rack 10

Starting Group

4 2

0 1

7 6 5 4

RIO Rack 9

Starting Group

4 2

0 0

3 2 1 0

RIO Rack 8

Starting Group

4 2

0 0

M1 File

M1:e.3

M1:e.4

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 Rack11 Device Fault Status Word 15 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

0 x 0 0 0 0 x 1 1 1 0

ÉÉ ÉÉ ÉÉÉ

0 x x x x x x x x x x x x x x x x

M1:e.12

M1:e.13

M1:e.14

M1:e.15

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

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–27

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:

•

M1:e.8 is an image of word 1 (primary/normal logical device address) of the G file.

•

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.

M1 (Status) File Primary/Normal

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

15 x

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 x x x x

14 x x x x x

13 x x

0 x x

RIO Logical

Rack 3

0 1

12 x x

11 x

10 x

9 x x

0 x x

RIO Logical

Rack 2

0 1

1 x

8 x

7 x

6 x

5 x x

0 x x

RIO Logical

Rack 1

0 0

0 x

4 x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

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

3 x x

2 x

1 x 0 1

RIO Logical

Rack 0

0 0 1

M1 File

M1:e.0

M1:e.2

M1:e.8

M1:e.9

M1:e.10

M1:e.12

M1:e.13

M1:e.14

M1:e.15

G File

RIO Logical Rack 3

Starting Group

4 2 0

Primary Logical Device Address, Word 1

Primary Logical Image Size, Word 2

RIO Logical Rack 2

Starting Group

4 2 0 6

RIO Logical Rack 1

Starting Group

4 2 0

RIO Logical Rack 0

Starting Group

4 2 0

Publication 17476.6 - July 1996

4–28

Scanner Configuration and Programming

M1 (Status) File Complementary

Bit Number (decimal)

Status Word, Word 0

15 x

14 x

13 x

12 x

11 x

10 x

9 x

Baud Rate, Word 2 x

Complementary Device Starting Address, Word 3

Complementary Device Image Size, Word 4

Complementary Active Device Status, Word 5 x

0 x x

RIO Logical

Rack 11

0 1

0 x

0 x x

RIO Logical

Rack 10

0 1

1 x

8 x

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 x x x x x x x x

7 x x

6 x

5 x x x

RIO Logical

Rack 9

0 0

0 x

4 x x x x x x x x x x x x x x x x x x x x x x x x x

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

x x x x

3 x x

2 x

1 x 0

RIO Logical

Rack 8

0 0

1 x x x x x x x x x x x x

G File

RIO Logical Rack 11

Starting Group

4 2 0

Complementary Logical Device Address, Word 3

Complementary Logical Image Size, Word 4

RIO Logical Rack 10

Starting Group

4 2 0 6

RIO Logical Rack 9

Starting Group

4 2 0

RIO Logical Rack 8

Starting Group

4 2 0

M1 File

M1:e.0

M1:e.2

M1:e.3

M1:e.4

M1:e.5

M1:e.12

M1:e.13

M1:e.14

M1:e.15

Important:

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

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–29

RIO Communication Retry

Counter (M1:e.16 47)

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–47) contains a retry counter for each configured quarter logical rack (words 16–31 are for primary logical racks, 0–3, and 32–47 are for complementary racks, 8–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 –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–47) correspond to the bits set in the Complementary

Logical Device Address – Word 3 of the G file.

Important:

Your SLC control program cannot initialize/clear retry counters.

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:

G File - Primary

Bit Number

Primary Logical Device Address, Word 1

RIO Logical Rack 3

Starting Group

6 4 2 0

ÉÉÉ

RIO Logical Rack 2

Starting Group

6 4 2 0

ÇÇ

RIO Logical Rack 1

Starting Group

6 4 2 0

3 2

RIO Logical Rack 0

Starting Group

6 4 2 0

0 0

ÉÉ ÇÇ ÉÉ

Specifies RIO addresses for primary logical devices.

G File - Complementary

Bit Number

Complementary Logical Device Address,

Word 3

15 14 13 12

RIO Logical Rack 11

Starting Group

6 4 2 0

0 0 1 1

ÉÉÉ

RIO Logical Rack 10

Starting Group

6 4 2 0

ÇÇ

ÉÉÉ ÇÇ

RIO Logical Rack 9

Starting Group

6 4 2 0

3 2 1 0

RIO Logical Rack 8

Starting Group

6 4 2 0

1 0 0

ÉÉ ÇÇ

0 1

ÉÉ

ÉÉ ÇÇ ÉÉ

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

Publication 17476.6 - July 1996

4–30

Scanner Configuration and Programming

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

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

Publication 17476.6 - July 1996

Scanner Configuration and Programming

4–31

Understanding Slot

Addressing

2Slot

Addressing

Remote Chassis

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:

Slot 2

Input Image

8 7

Two slots are addressed as one logical group.

0 15

Output Image

8 7

Slot 1 Slot 2 Slot 1

1Slot

Addressing

Remote Chassis

1/2Slot

Addressing

Remote Chassis

Input Image

8 7

One slot is addressed as one logical group.

0 15

Output Image

8 7

Slot 1 Slot 1

Input Image

8 7

One slot is addressed as two logical groups.

0 15

Output Image

8 7

Slot 1

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.

Slot 1

Publication 17476.6 - July 1996

4–32

Scanner Configuration and Programming

SLC/Scanner

Configuration

Your SLC processor can be programmed with an HHT

➀

(Hand-Held

Terminal) or APS (Advanced Programming Software). 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.

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

➀

The SLC 5/03 t and SLC 5/04 t processors cannot be programmed with the HHT.

Publication 17476.6 - July 1996

RIO Block Transfer

Chapter

RIO Block Transfer Theory of Operation

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

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 the RIO Block Transfer General

Functional Overview section 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.

Publication 17476.6 - July 1996

5–2

RIO Block Transfer

RIO Block Transfer Theory of Operation - Path of a Block Transfer

Chassis Backplane

SLC

Processor

➀

M Files

ÉÉÉÉÉÉÉ

Files

RIO

ÉÉÉÉÉÉÉ

I/O

Image

ÉÉÉÉÉÉÉ

RIO Link

= path of a Block Transfer (BT)

➀

SLC 5/02 processor or above

Adapter or

Intelligent

I/O Module

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 SLC processor across the chassis backplane via 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 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 the scanner.

Publication 17476.6 - July 1996

RIO Block Transfer

5–3

Chassis Backplane

SLC

Processor

➀

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

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

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

handshake" purposes.

M0 file

M1 file

ÉÉÉÉÉÉ

1747 RIO

Files

I/O

Image

ÉÉÉÉÉÉ

= path of the BTR

➀

SLC 5/02 processor or later

RIO Link

Logical

Rack 0

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

ÇÇÇÇ ÇÇÇÇ Word 25

Word 26

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 27

Word 28

Word 29

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 30

Word 31

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

ÇÇÇÇ ÇÇÇÇ

Adapter or

Intelligent

I/O Module

Slot 1

Slot 0

Slot 1

Slot 0

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

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.)

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.

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.

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. (Refer to the Block Transfer Buffer Layout section for details on status information.)

The SLC control program processes the BTR information.

Publication 17476.6 - July 1996

5–4

RIO Block Transfer

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

Chassis Backplane

SLC

Processor

➀

M0 file

M1 file

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

ÉÉÉÉÉÉ

1747 RIO

ÉÉÉÉÉÉ

Scanner

Files

I/O

Image

ÉÉÉÉÉÉ

RIO Link

Slot 1

Slot 0

Slot 1

Slot 0

Logical

Rack 0

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Word 23

Word 24

Word 25

Word 26

ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ

Word 27

Word 28

Word 29

ÇÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇÇ

Group 7

Word 31

ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇÇ

ÇÇÇ ÇÇÇÇ

= path of the BTW

➀

SLC 5/02 processor or later

Adapter or

Intelligent

I/O Module

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

handshake" purposes.

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

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. (Refer to the Block Transfer Buffer

Layout section for details on control information.)

The scanner reads the BTW data and control data from the M0 file. One byte of the scanner'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.

The M1 file contains BTW status information. (Refer to the Block Transfer Buffer Layout section for details on status information.)

The RIO scanner transfers BTW information across the RIO link to the adapter.

The adapter transfers the BTW information to the appropriate adapter or intelligent I/O module.

Publication 17476.6 - July 1996

RIO Block Transfer

5–5

RIO Block Transfer

General Functional

Overview

Words

100...109

The RIO scanner performs block transfers through control/status buffers that you allocate in the scanner’s M0 and M1 files. For

BTWs, the M0 BT buffer contains BTW control data and BTW data, while a corresponding M1 BT buffer contains only BTW status information. For BTRs, the M0 BT buffer contains only BTR control data, while a corresponding M1 BT buffer contains BTR status information and BTR data. Block transfers occur asynchronous to RIO link discrete transfers. Note that block transfers occur as RIO scan time allows – discrete I/O transfers have first priority.

A total of 32 block transfer control/status buffers exist in the M0

(output/control) and the M1 (input/status) files. Block transfer buffers consist of:

•

3 BT control words in an M0 file BT buffer

•

4 BT status words in an M1 file BT buffer

•

64 words of BTW data in an M0 file and 64 words of BTR data in an M1 file

M0:e.100

3 words for control and

7 reserved

M0 Control Buffers 1 . . . 32

Words

3200...3209

M0:e.3200

3 words for control and

7 reserved

You use an M0 file BT control buffer to initiate a BT. The corresponding M1 file displays the status of the block transfer.

Words

110...173

Words

100...109

64 words for

BT Write

Data

Words

3210...3273

M1:e.100

4 words for status and 6 reserved

M1 Status Buffers 1 . . . 32

Words

3200...3209

64 words for

BT Write

Data

M1:e.3200

4 words for status and 6 reserved

BT buffers reside on 100 word boundaries in the

M0/M1 files starting at word 100. For example, BT buffer 1 resides at M0:e.100 and M1:e.100; BT buffer

2 resides at M0:e.200 and M1:e.200; while BT buffer

16 resides at M0:e.1600 and M1:e.1600. Note that the e" in these examples refers to the physical chassis slot number in which the scanner resides.

All block transfer buffers (M0 and M1) are cleared

(set to zero) either when the RIO scanner goes through a power cycle or when the SLC processor commands the scanner to change mode from

Program to Test mode, Program to Run mode, or

Test to Run mode.

Words

110...173

64 words for

BT Read

Data

Words

3210...3273

64 words for

BT Read

Data

Publication 17476.6 - July 1996

5–6

RIO Block Transfer

Scanner I/O Image Allocation For Block Transfer

Block transfer operations (BTR and BTW) consume only one byte of the RIO scanner’s I/O image file, independent of what type of I/O slot addressing is used. This one byte image is reserved for communication “handshake” purposes between the remote device

(adapter or intelligent I/O module) and the scanner. SLC control programs must never read/write to these image locations because unpredictable operations may result.

Block transfer operations (BTR and BTW) can be addressed to any logical slot within the RIO scanner’s four logical racks. See the examples below and on the following page.

Examples of BT I/O Image File Allocation

Example 1

1747SN RIO Scanner's I/O Image Files

Logical

Rack 0

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

Word 25

ÇÇÇÇ ÇÇÇÇ

Word 26

Word 27

Word 28

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 29

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 30

Word 31

ÇÇÇÇ ÇÇÇÇ

Logical Slot 0

Logical Slot 1

The minimum portion of the scanner's image that can be assigned to an adapter is 1/4 logical rack. Each logical device that you assign BT operations (BTR or

BTW) consumes one byte from the scanner's input and output image file.

The one byte can come from either the

low" byte (Logical Slot 0) or the high" byte (Logical Slot 1). Logical Slot 1 only applies for 2 slot addressing.

In this example there are two block transfer operations mapped to the scanner' s I/O image. One BT operation is mapped to

Logical Rack 0, Logical Group 4, Logical

Slot 1. The other is mapped to Logical

Rack 3, Logical Group 4, Logical Slot 0.

Note that the logical address of your RIO devices (i.e., adapter and intelligent I/O modules) determine where the block transfer gets mapped.

Publication 17476.6 - July 1996

RIO Block Transfer

5–7

Example 2

In this example, the remote adapter is configured for 2slot addressing. It is assigned 1/4 logical rack of the scanner's I/O image files starting at RIO Logical Rack 3, Logical Group 4. The remote adapter controls four analog modules that are configured for block transfer operations. Note that each module uses both the input and output byte of the logical slot to which it is assigned.

Logical

Rack 0

Logical

Rack 3

1747SN RIO Scanner's I/O Image Files

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Adapter

Mod.

# 1 # 2 # 3 # 4

I/O

Image

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

Word 25

ÇÇÇÇ ÇÇÇ

Word 26

Word 27

Word 28

ÇÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇÇ

# 2 # 1 # 2 # 1

Word 29

Word 30

Word 31

# 4 # 3 # 4 # 3

ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

ÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇÇ

Modules' handshake" bytes map to these I/O image addresses.

Logical Slot 0

Logical Slot 1

These are all analog modules that are assigned block transfer operations.

Example 3

In this example, the remote adapter is using 2slot addressing. It is assigned 1/4 logical rack of the scanner's I/O image files starting at

RIO Logical Rack 3, Logical Group 4. The remote adapter controls two analog devices, which are configured for block transfer operations and two discrete devices (8 point input and 8 point output). Note that each analog module uses both the input and output byte of the logical slot to which it is assigned, while the discrete modules use only the input or output byte.

Logical

Rack 0

Logical

Rack 3

1747SN RIO Scanner's I/O Image Files

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Adapter

Mod.

# 1 # 2 # 3 # 4

I/O

Image

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

ÇÇÇ ÇÇÇÇ

Word 25

Word 26

Word 27

Word 28 not used

# 1

ÇÇÇ ÇÇÇ

# 2 # 1

Word 29

# 4 # 3 not used # 3

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ

Word 30

Word 31

ÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇ

Modules' handshake" bytes map to these I/O image ad dresses.

Logical Slot 0

Logical Slot 1

These are analog modules that are assigned block transfer operations.

These are discrete modules.

Module #2 is an 8 point output module and module #4 is an 8 point input module.

Publication 17476.6 - July 1996

5–8

RIO Block Transfer

Scanner's Block Transfer

Buffer Layout

This section describes the scanner’s M0 (output/control) and M1

(input/status) block transfer buffers.

M0 File - Block Transfer Output/Control Buffers

There are 32 BT output/control buffers allocated in the M0 file.

These buffers contain BTR/BTW control information and BTW output data. The following explains the layout of BT buffer 1.

Important:

The general layout below of buffer 1 is the same for all

32 M0 BT buffers. The “e” in the examples refers to the physical chassis slot number in which the scanner resides. Remember that buffers start on 100 word boundaries.

M0:e.100 – Contains BTR/BTW control flags that control block transfers. Control flags are explained on the following page.

M0:e.101 – Used to configure BTR/BTW length information (0 to

64). Length is the number of BTR/BTW words read from or written to the end device. If length = 0, then the RIO device will inform the

SLC processor as to how much data to transfer. The M0/M1 BT buffers cannot overflow because they each reserve 64 words of data area.

M0:e.102 – Contains the logical address of the BTR/BTW operation in logical rack, group, and slot number format. The logical rack, group, and slot are combined into one word, which you enter in

decimal form.

Logical

Rack 0

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

Word 25

Word 26

ÇÇÇÇ ÇÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇ ÇÇÇÇ

Word 27

Word 28

Word 29

ÇÇÇ ÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇ

Word 30

Word 31

ÇÇÇ ÇÇÇÇ

ÇÇÇÇ ÇÇÇ

Logical Slot 0

(Low Byte)

Logical Slot 1

(High Byte)

M0:e.102 Logical Address Example

The Slot Number" (0 or 1) in M0:e.102 indicates the logical slot number within a logical group. 0 designates the least significant image byte and 1 designates the most significant image byte.

Which Slot Number To Use

When your adapter is configured for 2slot addressing, 0 is the left slot and 1 is the right slot.

For both 1slot and 1/2 slot addressing the slot number is al ways 0.

Example M0:e.102 Configurations

Logical Rack 0 , Group 0 , Slot 0 = 0

Logical Rack 0 , Group 0 , Slot 1 = 1

Logical Rack 2 , Group 3 , Slot 1 = 231

Logical Rack 0 , Group 7 , Slot 0 = 70

The first number

(reading from right to left) is the

Slot Number."

Leading 0s need not be entered.

Publication 17476.6 - July 1996

RIO Block Transfer

5–9

M0:e.103 through M0:e.109 – These words are reserved.

M0:e.110 through M0:e.173 – BTW data Words 0 through 63.

M0 File BT Control Buffer Layout

Important:

The buffer layout below is the same for all 32 BT buffers. Buffer 1 = M0:e.100... buffer 32 = M0:e.3200.

BT Control Buffer Function

Control Flags - See Control Flag

Definitions table below.

BT Length - 0 through 64

BT Address (logical rack, group, and slot)

Reserved

BTW Data Locations 0 through 63

M0 Address where x = buffer # from 1 to 32

M0:e.x00

M0:e.x01

M0:e.x02

M0:e.x03 through M0:e. x09

M0:e.x10 through M0:e.x73

BT Control Flag Definitions

Definition

These bits are reserved.

Type of BT operation (1 = BTR and

0 = BTW)

➀

Block Transfer Timeout (TO) = 1 =

Cancel the BT operation.

➁

These bits are reserved.

Block Transfer Enable (EN) = 1 =

Enable the BT operation.

➂

Control flags where x = buffer # from 1 to 32

M0:e.x00/0 through M0:e.x00/6

M0:e.x00/7

M0:e.x00/8

M0:e.x00/9 through M0:e.x00/14

M0:e.x00/15

➀

Bit 7 indicates whether the SLC control program is initiating a BTR or a BTW.

➁

You set bit 8 (timeout bit - TO) = 1 to cancel a BT. You can cancel a BT operation (by timing out) once the Enabled Waiting (EW) bit sets and before the RIO scanner's internal four second BT timer times out or the BT completes. Cancelling a BT causes an error (ER) bit to set and an error code to display in the M1 BT buffer. Note that the Timeout (TO) flag must be cleared before initiating a new BT. (You can initiate a new BT by clearing the EN flag, waiting for the ER flag to clear, and then setting the EN bit.) The RIO scanner will ignore a BT request if both TO and EN flags are set at the same time.

➂

You set bit 15 = 1 to Enable (EN) a BT operation. You set this bit after you have entered all other control information i.e., bits 7 and 8 in the M0 BT buffer. You clear this bit after either the Done

(DN) or Error (ER) bits are set in the M1 Status file. See the M1 file BT Buffer Layout section for more details on the DN and ER bits.

Publication 17476.6 - July 1996

5–10

RIO Block Transfer

Logical

Rack 0

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 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

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Word 23

Word 24

ÇÇÇÇ ÇÇÇÇ

Word 25

Word 26

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 27

Word 28

Word 29

Word 30

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

Word 31

ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ ÇÇÇÇ

ÇÇÇÇ ÇÇÇÇ

Logical Slot 0

(Low Byte)

Logical Slot 1

(High Byte)

M1 File - Block Transfer Input/Status Buffers

There are 32 BT status buffers allocated in the M1 file. These buffers indicate the status for all BTR and BTW operations and also contain

BTR input data. Below is the layout of BT buffer 1.

Important:

The layout below is the same for all 32 M1 file BT buffers.

M1:e.100 – Status flags that describe the status of the BTR and

BTW operations. Status flags are described in detail on the following page.

M1:e.101 – Status of actual number of BTW words sent or the number of BTR words received.

M1:e.102 – Contains the logical address you have selected in the

M0:e.102 file in rack, group, and slot number format. The logical rack, group, and slot are combined into one word.

M1:e.102 Logical Address Example

The Slot Number" (0 or 1) in M1:e.102 indicates the logical slot number within a logical group. 0 designates the least significant image byte and 1 designates the most significant image byte.

Which Slot Number To Use

When your adapter is configured for 2slot addressing, 0 is the left slot and 1 is the right slot.

For both 1slot and 1/2 slot addressing the slot number is always 0.

Example M1:e.102 Configurations

Logical Rack 0 , Group 0 , Slot 0 = 0

Logical Rack 0 , Group 0 , Slot 1 = 1

Logical Rack 2 , Group 3 , Slot 1 = 231

Logical Rack 0 , Group 7 , Slot 0 = 70

The first number

(reading from right to left) is the

Slot Number."

M1:e.103 – The BTR/BTW error code. Refer to the M1 File Error

Codes table on the following page.

M1:e.104 through M1:e.109 – These words are reserved.

M1:e.110 through M1:e.173 – BTR data Words 0 through 63.

Publication 17476.6 - July 1996

RIO Block Transfer

5–11

M1 File - Input/Status BT Buffer Layout (M1:e.100 ... M1:e.3200)

BT Status Buffer Function M1 Address where x = buffer

# from 1 to 32

M1:e.x00

M0 Address for

BT buffer 1

M1:e.100

...M0 Address for

BT buffer 32

...M1:e.3200

Status Flags - Refer to the status flags table on the following page.

Actual Length Status- Number of words that were transferred during BT.

Logical Address Status - logical rack, group, and slot

Block Transfer error code - Refer to the Error Codes table below.

Reserved

BTR Data Locations 0 through 63

M1:e.x01

M1:e.x02

M1:e.x03

M1:e.x04 through

M1:e.x09

M1:e.x10 through

M1:e.x73

M1:e.101

M1:e.102

M1:e.103

M1:e.104 through

M1:e.109

M1:e.110 through

M1:e.173

...M1:e.3201

...M1:e.3202

...M1:e.3203

...M1:e.3204

through

M1:e.3209

...M1:e.3210

through

M1:e.3273

M1 File - BTR/BTW Error Codes (M1:e.103 ... M1:e.3203)

Error Code

- 0

- 6

- 7

- 8

- 9

- 10

- 11

- 12

Description

The BT completed successfully.

Illegal BT length requested.

BT communication error occurred when BT request was initiated.

Error in BT protocol.

BT timeout - either the SLC user program cancelled the BT or the scanner's BT timer timed out. Note that a timeout error will occur if a

BT is attempted at a location that is not configured for BT operation

(e.g., requesting a BT for a location that is an output module).

No RIO channel configured.

Attempted a BT either to a nonconfigured BT 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.

Attempted a BT to an inhibited device.

Publication 17476.6 - July 1996

5–12

RIO Block Transfer

M1 File - BTR/BTW Status Flag Definitions (M1:e.100 ... M1:e.3200)

Status Flag

M1:e.100/0 through

M1:e.100/9

M1:e.100/10

Description

These bits are reserved.

M1:e.100/11

M1:e.100/12

M1:e.100/13

M1:e.100/14

M1:e.100/15

Block Transfer Enabled and Waiting for block transfer to start -

(EW = Enable Waiting)

➀

This bit is reserved.

Block Transfer Error - (ER = Error)

This bit is reserved.

➁

Block Transfer Successful - (DN = Done)

Block Transfer Started - (ST = Started)

➃

➂

➀

When set to a 1" (with bit 14 set to a 0"), bit 10 indicates that a BT operation is pending . You can program a timer in your SLC control program to cancel a BT prior to bit 14 being set. Note that bit

10 must be set to 1" before your SLC user program can cancel the BT operation.

➁

When set to a 1", bit 12 indicates that an error occurred while the BT was being processed.

M1:e.103 contains an error code that is useful in determining the cause of an error. Once this bit is set, the SLC user program can reset the Enable (EN) bit in the M0 BT buffer so that a new BT can occur.

➂

When set to a 1", bit 13 indicates the successful completion of a BT operation. If the operation was a BTR, the BT data is available in the M1 BT buffer. Once this bit is set, the SLC user program can reset the Enable (EN) bit in the M0 BT buffer so that a new BT can occur.

➃

When set to a 1", bit 14 indicates that a BT operation has started. Once the BT operation starts, an RIO system 4 second timer begins counting down. You can program a timer in your SLC user program to cancel a Started (bit 14) BT.

Publication 17476.6 - July 1996

Detailed Operation of RIO

Block Transfer

RIO Block Transfer

5–13

You use the 1747-SN Scanner M0 file BTR/BTW output control buffers to set up and control BT operations. Status information regarding the progress and completion of BTR/BTW operations displays in corresponding M1 file input status buffers.

This section describes step-by-step how the RIO scanner uses

M0/M1 files to accomplish block transfer operations. The steps below are based on the following assumptions:

•

The size of the M0 and M1 files has already been set to 3,300 words. (You set the M file sizes in APS while in off-line programming mode.)

•

No pending BT operation utilizing a particular M0 output/control and M1 status/control buffer is in progress.

•

Both the M0/M1 control/status buffers are completely empty.

Important:

Timing diagrams describing BT control and status flag operation follow this section.

1. You set up a BTR or BTW by filling in control information

(about block transfer length, logical rack, logical group, and logical slot address) in an M0 output/control buffer. If you want to set up a BTW, then you must place your write data in the BTW data area of the M0 output control buffer. You set up M0 buffer information in an integer file and a COP instruction copies the information into the M0 output control file.

2. Your SLC control program initiates a BTR/BTW operation by filling in the BT control field (M0:e.100/7) of the M0 BT buffer.

This indicates whether a BTR or BTW will be initiated (0 = BTW and 1 = BTR).

Your SLC control program also sets the EN (Enable) flag

(M0:e.100/15) which signals the RIO scanner that a new block transfer operation is to begin.

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

SLC control program has set the EN flag.

If the RIO scanner detects any problem at this point (such as invalid BT control field, or unconfigured device) the M1 input status buffer’s error code field fills in and the ER (Error) flag in the status field sets. If no problems occur, the EW (Enable

Waiting) flag and ST (Start) flag set in the status field. (Note that the ST flag will not set if the scanner is already in the process of block transferring data to a location within the same logical rack.

The ST flag will set only after any previous pending BTs to the same logical rack have been completed and the BT request has been scheduled on the RIO link.)

Publication 17476.6 - July 1996

5–14

RIO Block Transfer

Your SLC control program can monitor the block transfer by examining the M1 status flags. They indicate when the scanner has started processing (EW and ST flags) the BT and whether the

BT operation completed successfully (DN flag) or failed (ER flag). Your SLC control program takes different actions based on these status flags.

4. If the BT completes successfully, the scanner fills in the M1 BT length status field. If it was a BTW operation, the BTR data area of the M1 BT buffer is not updated. If it was a BTR operation, the new BTR input data (based on length) is placed in the BTR data area of the M1 BT buffer and the unused buffer area clears. The

DN status flag then sets to indicate to the SLC control program that the BT operation completed successfully and that the M1 input status buffer has been completely updated.

5. If the BT fails, the length field and BTR data area are not updated

(length remains cleared). The error code field indicates the problem type. The ER flag sets to indicate to the SLC control program that the BT operation was unsuccessful.

6. The SLC control program must indicate to the scanner when it is done processing the M1 input/status buffer (because DN or ER was set) so the corresponding M0 output/control buffer can be re-used for another BT operation. The SLC control program indicates that it is through processing when it clears the EN flag.

7. When the RIO scanner detects that the EN flag has been cleared by the SLC control program, it then clears the EW, ST and DN or

ER flags. This ensures that the status flags in the M1 input status buffer are not reflecting the results of the previous BT operation.

Note that the other M1 BT Status buffer fields, such as length, error code, and BTR data are not cleared when the scanner clears the status flags. These fields are only updated when the scanner has processed a BT operation as indicated by the DN or ER flag.

For example, if there was a problem with a BT operation, the error code will remain in the M1 BT buffer until the next BT operation causes it to be changed (cleared if DN is set or an error code if ER is set). Therefore, the SLC control program should precede the examination of the error code field with the ER flag.

Block Transfer Timing Diagrams

The following pages contain timing diagrams that illustrate the effects of different control flags on a BT operation.

Publication 17476.6 - July 1996

Control Flag

Status Flag

RIO Block Transfer

Successful Block Transfer

M0 Control Information

5–15

M1 Status Information

Successful Block Transfer Read/Write

This example illustrates a successful BT operation.

The SLC control program fills in the M0 BT output/control buffer and sets the enable (EN) flag.

The scanner detects that the EN flag is set, validates the control 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) flag in M1 status field.

The scanner receives a BT reply (with no errors) from the RIO link device, fills in any requested BTR data, and sets the done

(DN) flag.

The SLC control program detects the DN flag, processes the BT data, and clears the enable (EN) flag.

The scanner detects that the SLC control program has completed processing (because the EN flag is clear) and clears the EW, ST and DN flags. At this point the SLC control program could initiate another BT operation in the same M0 BT buffer by setting the EN flag.

Publication 17476.6 - July 1996

5–16

RIO Block Transfer

Control Flag

Status Flag

Block Transfer Failure at Startup

M0 Control Information

M1 Status Information

Publication 17476.6 - July 1996

Block Transfer Failure at Startup

In the above example, the scanner found invalid control information

(e.g., an improper logical address) in the M0 block transfer control buffer.

The SLC control program fills in the M0 BT buffer and sets the

EN flag.

The scanner detects that the EN flag is set, determines that there is some invalid information in the M0 control buffer, fills in the

M1 BT buffer status error code field, and sets the ER flag.

The SLC control program detects the ER flag, examines the M1

BT status buffer error code, and clears the EN flag after processing the error.

The scanner detects that the SLC control program has processed the error and clears the ER flag.

Note that in this example the EW and ST flags never set. Also, the

SLC control program must clear the EN flag in order to start a new

BT after the error has been corrected.

RIO Block Transfer

Block Transfer Failure After Startup of Transmission Across RIO Link

M0 Control Information

Control Flag

M1 Status Information

Status Flag

5–17

Block Transfer Failure after Startup of Transmission Across the RIO

Link

This example illustrates control and status changes when a BT fails after it starts.

The SLC control program fills in the M0 BT output/control buffer and sets the EN flag.

The scanner detects the EN flag, validates the M0 information, puts the BT request on the RIO link successfully, and sets the EW and ST flags in the M1 BT input status buffer.

The scanner receives a BT reply (with some error) from the RIO link device, fills in the M1 BT buffer’s error code field, and sets the ER flag.

The SLC control program detects the ER flag, examines the M1

BT buffer error code, and clears the EN flag after processing the error.

The scanner detects that the SLC control program has processed the reply in the M1 BT buffer and clears the EW, ST and ER flags.

Publication 17476.6 - July 1996

5–18

RIO Block Transfer

SLC Control Program Cancelling a Block Transfer Once Transmitted Across RIO Link

M0 Control Information

Control Flag

M1 Status Information

Status Flag

SLC Control Program Canceling a BT Once Transmitted Across RIO

Link

This example illustrates an SLC control program cancelling a BT operation.

In this example, the SLC control program wants a BT timeout value less than the four second default value that the scanner uses.

When the SLC control program detects that the ST flag has set, a timer in the SLC control program starts.

If the timer expires before the scanner returns a BT response (DN or ER), then the program will set the TO flag.

The scanner fills in the error code field and sets the ER flag. The

SLC control program must still clear the EN flag to complete the

BT operation. Note that because of the asynchronous nature of cancelling a transmission to a device that has a BT in progress, the BT reply may indicate either a successful completion or an error.

The SLC control program clears the TO and EN flags. Note that if the SLC control program later attempts to initiate another BT and the TO flag is still set, the scanner will ignore the BT request.

Finally, the EW, ST and ER bits are reset.

Publication 17476.6 - July 1996

RIO Block Transfer

5–19

SLC Control Program Cancelling a Block Transfer Prior To Transmission Across RIO Link

M0 Control Information

Control Flag

M1 Status Information

Status Flag

SLC Control Program Canceling a BT Prior to Transmission Across

RIO Link

In this example, the SLC control program cancels a BT that has been pending (EW = 1, ST = 0) for a specific amount of time.

When the SLC control program detects that the EW has set, a timer in the SLC control program starts.

If the timer expires before the scanner begins transmitting across the RIO link (ST = 1), then the SLC control program will set the

TO flag. Note that the cancellation will not occur until all previously scheduled BTs to the same logical rack have been completed (i.e., when the ST bit would normally have been set).

The scanner fills in the error code field and sets the ER flag.

Also, the ER bit is not set until any previously pending BTs to that device have been completed. The SLC control program must clear the EN flag to complete the BT operation. Note that because of the asynchronous nature of cancelling a device that has a BT in progress, the BT reply may indicate either a successful completion or an error.

The SLC control program clears the TO and EN flags. Note that if the SLC control program later attempts to initiate another BT and the TO flag is still set, the scanner will ignore the BT request.

Finally, the EW, ST (if set) and ER bits are reset.

Publication 17476.6 - July 1996

5–20

RIO Block Transfer

Application

Considerations

Primary I/O Image

Bit Number Octal

Bit Number Decimal

Logical

Rack 0

Word 0

ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 1

Word 2

ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 3

Word 4

Word 5

ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 6

Word 7

ÉÉÉÉ ÉÉÉÉ

Below are points to consider when implementing BT operations:

•

The minimum amount of scanner image that can be assigned to a device on the RIO link is 1/4 logical rack in the G file configuration. This allows up to four separate devices per logical rack. Each device could have a maximum of four BTs configured to it. Thus, up to 16 BTRs and/or 16 BTWs could be assigned to each logical rack.

•

If a BT device is a 1747-ASB RIO Adapter, then multiple SLC

500 modules (such as analog modules) could be scanned by the

1747-ASB and the data block transferred to the RIO scanner.

Since the RIO network handles one BT request per logical rack at a time, there will be a delay before all devices in the 1747-ASB rack can be accessed. Therefore you should only perform BTs as necessary (i.e., “on demand”).

•

Inhibiting a device on the RIO network (via control words

M0:e.8...11) precludes that device from block transfer operations.

Attempting to initiate a BT to an inhibited device results in an error reply. The scanner will cancel a BT that is in progress if it detects that the device is inhibited. Because of the asynchronous nature of inhibiting a device that has a BT in progress, the BT reply may indicate either a successful completion or an error. In either case, the SLC control program must still clear the Enable flag.

•

All M0 and M1 BT buffers are cleared (set to all zeros) after a power cycle and when the SLC processor goes from Program to

Run mode, Program to Test mode, or Test to Run mode.

When using complementary I/O, 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 configured and usable

1/2 logical rack not configured

Complementary I/O Image

Bit Number Octal

Bit Number Decimal

Logical

Rack 8

Word 0

ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 1

Word 2

ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ ÉÉÉÉ

Word 3

Word 4

Word 5

ËËËË ËËËË ËËËË ËËËË ÉÉÉÉ ÉÉÉÉ

Word 6

Word 7

ËËËË ËËËË ËËËË ËËËË ËËËË ËËËË

ËËËË ËËËË

1/2 logical rack configured and usable

1/2 logical rack configured, but not usable for BT since

Words 4-7 are not configured for the primary device.

Publication 17476.6 - July 1996

Setting Up a Block

Transfer

RIO Block Transfer

5–21

Follow the steps below to set up your scanner and SLC control program for either BTWs or BTRs.

1. To use the BT functionality, you must increase the size of the M0 and M1 files in an offline APS session. The size depends on the number of BT buffers your applications requires. Note that setting the buffers to maximum size (3300) will not affect system performance. However, addressing M-files in your SLC control program does affect system performance.

2. Set the control flags in M0:e.x00. Where x = block transfer buffer number. See the tables below for read/write settings.

If You Want to Transfer

Data:

To the scanner from the adapter

From the scanner to the adapter

Use:

BTR (Block Transfer Read)

BTW (Block Transfer Write)

If You Want to specify a:

BTR (Block Transfer Read)

BTW (Block Transfer Write)

Do this to the M0:e.x00/7 file :

Set the bit to 1 to specify a read operation

Set the bit to 0 to specify a write operation.

3. Specify the length of the data you wish to block transfer in word

M0:e.x01. Note that maximum length is 64 words.

4. Specify the device’s logical rack, group, and slot in word

M0:e.x02.

5. Set up your SLC control program to set the EN bit.

Publication 17476.6 - July 1996

5–22

RIO Block Transfer

Quick Reference to Status and Control Bits

The tables below provide a quick reference for block transfer status and control bits. In the tables, x = the block transfer file.

Status Bits

This Bit: Is Set:

Enable Waiting EW -

M1:e.x00/10

Error ER - M1:e.x00/12 upon the scanner's first detection of EN being set. The EW bit gets reset when the EN flag resets.

when the scanner detects that the block transfer failed. The

ER bit is reset when the EN flag resets.

Done DN - M1:e.x00/13 at completion of the block transfer, if the data is valid. The DN bit is reset when the EN flag resets.

Start ST - M1:e.x00/14 when the scanner schedule" the BT for the adapter. The data transfers may not start for some time. The ST bit is reset when the EN flag resets.

Control Bits

This Bit: Is Set:

ReadWrite RW -

M0:e.x00/7

Enable EN -

M0:e.x00/15 by your SLC control program. A 0 indicates a write operation; a 1 indicates a read operation.

Timeout TO - M0:e.x00/8 if you leave the timeout bit reset, the scanner repeatedly tries to send a block transfer request to an unresponsive module for four seconds before setting the ER bit.

if you set the TO bit through your SLC program the scanner attempts to cancel the BT request.

by your SLC control program to initiate a BT request.

Publication 17476.6 - July 1996

RIO Block Transfer

5–23

BTR and BTW Control

Logic Examples

The following pages contain generic BTR and BTW control logic

examples. Refer to chapter 7, Application Examples for specific

product applications using BT examples.

Block Transfer Read Control Logic Example

Rung 2:0

CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BIT

B3:100/7 MUST BE SET PRIOR TO GOING TO RUN TO INDICATE A BTR OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 15 |Source #B3:100| |

| |Dest #M0:1.100| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THE

PROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAM

SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE IS

SCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS AND

THEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.

| SERVICE |

| THE BTR |

| STATUS/ |

| BTR |

| PENDING BTR STATUS |

| B3:5 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 0 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | CHECK BTR | |

| | STATUS | |

| | UNTIL DN | |

| | OR ER BIT | |

| | IS OFF | |

| | B3:5 | |

| +––––] [–––––+ |

| 1 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH THE ENABLE

BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE BIT BEFORE ANOTHER BTR

TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE COMPLETE BTR CYCLE.

| | CHECK BTR |

| | STATUS |

| VIRTUAL | UNTIL DN |

| BTR DONE | OR ER BIT |

| BIT | IS OFF |

| B3:0 B3:5 |

|–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|

| | 13 | 1 |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | B3:0 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

5–24

RIO Block Transfer

Rung 2:3

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BT DATA AND UNLATCH THE BT ENABLE

BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUES

CHECKING THE BTR STATUS UNTIL THE SN MODULE TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| B3:0 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | SERVICE | |

| | THE BTR | |

| | STATUS/ | |

| | BTR | |

| | PENDING | |

| | B3:5 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BT ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | CHECK BTR | |

| | STATUS | |

| | UNTIL DN | |

| | OR ER BIT | |

| | IS OFF | |

| | B3:5 | |

| +––––(L)–––––––––––––––+ |

| 1 |

Rung 2:4

IF A BTR ERROR OCCURS, UNLATCH THE ENABLE BIT AND BUFFER THE BT ERROR CODE.

ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUES CHECKING

THE BTR STATUS UNTIL THE SN MODULE TURNS OFF THE ERROR BIT.

| |

| VIRTUAL |

| BTR ERROR BTR ERROR |

| BIT CODE |

| B3:0 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source B3:3| | |

| | | 0000000000000000| | |

| | | 0000000000000000| | |

| | +––––––––––––––––––+ | |

| | | |

| | SERVICE | |

| | THE BTR | |

| | STATUS/ | |

| | BTR | |

| | PENDING | |

| | B3:5 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BT ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | CHECK BTR | |

| | STATUS | |

| | UNTIL DN | |

| | OR ER BIT | |

| | IS OFF | |

| | B3:5 | |

| +––––(L)–––––––––––––––+ |

| 1 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:5

WHEN USER LOGIC INITIATES A NEW BTR, LATCH THE ENABLE BIT , AS LONG AS A BTR IS

NOT IN PROGRESS. ALSO, LATCH THE BTR PENDING BIT , SO THE BTR STATUS FILE WILL

BE READ BY THE LADDER PROGRAM.

| BTR |BIT |BIT |BIT PENDING |

| I:2.0 B3:100 B3:0 B3:0 B3:5 |

|––––] [––––––––]/[––––––––]/[––––––––]/[–––––––––––––––––––––––+––––(L)–––––+–|

| 0 15 13 12 | 0 | |

| | | |

| | VIRTUAL | |

| | BT ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(L)–––––+ |

| 15 |

Rung 2:6

MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHENEVER A

TRANSITION OF THE BTR ENABLE BIT OCCURS.

| |

| VIRTUAL |

| BT ENABLE |

| BIT |

| B3:100 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source B3:100| |

| | | | 0000000000000000| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | B3:0 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | B3:0 | |

| +––––] [–––––+ |

| 12 |

Rung 2:7

| |

|–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|

| |

Block Transfer Write Control Logic Example

Rung 2:0

CONFIGURE THE BTW LENGTH AND RIO ADDRESS AT POWER–UP. ALSO, BE SURE THE BLOCK

TRANSFER OPERATION BIT IS A ”0” INDICATING A BTW. ALL THESE PARAMETERS MUST BE

ENTERED PRIOR TO PLACING THE PROCESSOR IN THE RUN MODE.

| |

| POWER–UP |

| BIT |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 15 |Source #B3:100| |

| |Dest #M0:1.100| |

| |Length 3| |

| +––––––––––––––––––+ |

5–25

Publication 17476.6 - July 1996

5–26

RIO Block Transfer

Rung 2:1

COPY THE BTW STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THE

PROGRAM, ONLY WHEN A BTW IS PENDING. THIS AVOIDS ACCESSING THE M1 FILE MULTIPLE

TIMES DURING EACH PROGRAM SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE

BIT, WORD OR FILE IS SCANNED BY THE PROCESSOR,AN IMMEDIATE DATA TRANSFER TO

THE MODULE OCCURS AND THEREFORE WILL IMPACT THE PROCESSOR SCAN TIME.

| SERVICE |

| THE BTW |

| STATUS/ |

| BTW |

| PENDING BTW STATUS |

| B3:5 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 0 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | UNTIL DONE | |

| | BIT IS OFF | |

| | B3:5 | |

| +––––] [–––––+ |

| 1 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW IS

COMPLETE, THE DONE BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH THE ENABLE

BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE BIT BEFORE ANOTHER BTW

TO THE SAME M–FILE LOCATION CAN BE INITIALIZED. THIS IS ONE COMPLETE BTW CYCLE.

| | |

| | CHECK BTW |

| VIRTUAL | STATUS |

| BTW DONE | UNTIL DONE |

| BIT | BIT IS OFF |

| B3:0 B3:5 |

| | 13 | 1 |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | B3:0 | |

| +––––]/[–––––+ |

| 12 |

Rung 2:3

WHEN A BTW SUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT. ALSO, UNLATCH

THE BTW PENDING BIT AND LATCH THE BIT THAT CONTINUES CHECKING THE BTW STATUS

UNTIL THE SN MODULE TURNS OFF THE DONE BIT.

| SERVICE |

| THE BTW |

| VIRTUAL STATUS/ |

| BTW DONE BTW |

| BIT PENDING |

| B3:0 B3:5 |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––+––––(U)–––––+–|

| 13 | 0 | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(U)–––––+ |

| | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | UNTIL DONE | |

| | BIT IS OFF | |

| | B3:5 | |

| +––––(L)–––––+ |

| 1 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:4

IF A BTW ERRORS, UNLATCH THE ENABLE BIT, THE BTW PENDING BIT AND BUFFER THE BTW

ERROR CODE. ALSO, LATCH THE BIT THAT CONTINUES CHECKING THE BTW STATUS UNTIL

THE SN MODULE TURNS OFF THE ERROR BIT.

| |

| VIRTUAL |

| BTW ERROR BUFFER BTW |

| BIT ERROR CODE |

| B3:0 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source B3:3| | |

| | | 0000000000000000| | |

| | | 0000000000000000| | |

| | +––––––––––––––––––+ | |

| | SERVICE | |

| | THE BTW | |

| | STATUS/ | |

| | BTW | |

| | PENDING | |

| | B3:5 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | UNTIL DONE | |

| | BIT IS OFF | |

| | B3:5 | |

| +––––(L)–––––––––––––––+ |

| 1 |

Rung 2:5

WHEN USER LOGIC INITIATES A NEW BTW, COPY THE DATA TO THE M0 FILE DATA AREA

AND LATCH THE VIRTUAL BTW ENABLE BIT, PROVIDED THAT A BTW IS NOT IN PROGRESS.

ALSO, LATCH THE BTW PENDING BIT, SO THE BT STATUS FILE WILL BE READ BY THE

LADDER PROGRAM.

| | | | |

| BTW |BIT |BIT |BIT BTW DATA |

| I:2.0 B3:100 B3:0 B3:0 +COP–––––––––––––––+ |

|––––] [––––––––]/[––––––––]/[––––––––]/[–––––––––––––+–+COPY FILE +–+–|

| 0 15 13 12 | |Source #N7:110| | |

| | +––––––––––––––––––+ | |

| | SERVICE | |

| | THE BTW | |

| | STATUS/ | |

| | BTW | |

| | PENDING | |

| | B3:5 | |

| +––––(L)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | B3:100 | |

| +––––(L)–––––––––––––––+ |

| 15 |

5–27

Publication 17476.6 - July 1996

5–28

RIO Block Transfer

Rung 2:6

MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHENEVER A

TRANSITION OF THE BTW ENABLE BIT OCCURS.

| |

| VIRTUAL |

| BTW ENABLE |

| BIT |

| B3:100 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source B3:100| |

| | | | 0000000000000000| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTW DONE | |

| | BIT | |

| | B3:0 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | B3:0 | |

| +––––] [–––––+ |

| 12 |

Rung 2:7

| |

Publication 17476.6 - July 1996

RIO Block Transfer

5–29

Directional Continuous Block Transfer Example

The following rungs demonstrate a directional continuous block transfer. As long as the BTR precondition bit is true, block transfer reads execute continuously. Use the same method for a BTW.

Rung 2:0

CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BIT

B3:100/7 MUST BE SET PRIOR TO GOING TO RUN TO INDICATE A BTR OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 15 |Source #B3:100| |

| |Dest #M0:1.100| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THE

PROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAM

SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE IS

SCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS AND

THEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 80 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 81 |

Rung 2:2

WHEN THE ERROR OR DONE BIT IS SET INDICATING THAT THE BTR COMPLETED EITHER

UNSUCCESSFULLY OR SUCCESSFULLY, THE ENABLE BIT MUST BE UNLATCHED BY THE LADDER

PROGRAM. THE 1747–SN SCANNER THEN UNLATCHES THE ERROR/DONE BIT TO COMPLETE THE

BLOCK TRANSFER HAND–SHAKE PROCESS. AT THIS TIME THE ”CHECK BTR STATUS” BIT

MUST BE UNLATCHED TO AVOID UNNECESSARY M–FILE ACCESSES.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| B3 B3 |

| | 13 | 81 |

| | | |

| | VIRTUAL | |

| | BT ERROR | |

| | BIT | |

| | B3 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

5–30

RIO Block Transfer

Rung 2:3

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTR

ENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUES

CHECKING THE BTR STATUS UNTIL THE SN TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| B3 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

Rung 2:4

WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BR

ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT IN

ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL IT

TURNS THE ERROR BIT OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL |

| BT ERROR BTR ERROR |

| BIT CODE |

| B3 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:5

BLOCK TRANSFER READS WILL EXECUTE CONTINUOUSLY AS LONG AS THE BTR PRECONDITION

BIT IS TRUE.

| | | | |

| BIT |BIT |BIT |BIT PENDING |

| B3 B3 B3 B3 B3 |

| 83 1615 13 12 | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(L)–––––+ |

| 1615 |

Rung 2:6

MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR IS

IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS ARE

ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL BTR |

| BTR ENABLE CONTROL |

| BIT WORD |

| B3 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 1615 | |Source B3:100| |

| | | | 0000000000000000| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BT ERROR | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| 12 |

Rung 2:7

| |

5–31

Publication 17476.6 - July 1996

5–32

RIO Block Transfer

Directional Repeating Block Transfer Example

The following example shows a directional repeating block transfer.

This means that block transfer reads will be sent repeatedly, as fast as possible. Use the same method for a BTW.

Rung 2:0

CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BIT

B3:100/7 MUST BE SET PRIOR TO GOING TO RUN TO INDICATE A BTR OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 15 |Source #B3:100| |

| |Dest #M0:1.100| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THE

PROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAM

SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M–FILE BIT, WORD OR FILE IS

SCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS AND

THEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 80 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 81 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BIT

BEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE

COMPLETE BTR CYCLE.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| B3 B3 |

| | 13 | 81 |

| | | |

| | VIRTUAL | |

| | BT ERROR | |

| | BIT | |

| | B3 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:3

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTR

ENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUES

CHECKING THE BTR STATUS UNTIL THE SN TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| B3 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

Rung 2:4

| |

| VIRTUAL |

| BT ERROR |

| BIT |

| B3 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

5–33

Publication 17476.6 - July 1996

5–34

RIO Block Transfer

Rung 2:5

BLOCK TRANSFER READS WILL REPEAT AS FAST AS POSSIBLE AS LONG AS THESE RUNGS

ARE SCANNED.

| | | |

| VIRTUAL |VIRTUAL |VIRTUAL |

| BTR ENABLE|BTR DONE |BT ERROR BTR |

| BIT |BIT |BIT PENDING |

| B3 B3 B3 B3 |

|––––]/[––––––––]/[––––––––]/[––––––––––––––––––––––––––––––––––+––––(L)–––––+–|

| 1615 13 12 | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(L)–––––+ |

| 1615 |

Rung 2:6

MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR IS

IN PROGRESS AND CONTINUE DOING SO UNTIL THE SCANNER TURNS THE DONE/ERROR BIT

OFF.

| |

| VIRTUAL |

| BTR ENABLE |

| BIT |

| B3 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 1615 | |Source B3:100| |

| | | | 0000000000000000| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BT ERROR | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| 12 |

Rung 2:7

| |

Publication 17476.6 - July 1996

RIO Block Transfer

5–35

Directional NonContinuous Block Transfer Example

The following rungs demonstrate a directional non-continuous block transfer. The block transfer executes once for every false-to-true transition of the input. Please note that the input bit I:2.0/0 was chosen randomly for this example and can be any address in your program used to initiate a BTR. Also note that this same method may be used for a BTW.

Rung 2:0

CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BIT

B3:100/7 MUST BE SET PRIOR TO GOING TO RUN TO INDICATE A BTR OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 15 |Source #B3:100| |

| |Dest #M0:1.100| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THE

PROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAM

SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE IS

SCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS AND

THEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 80 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 81 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BIT

BEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE

COMPLETE BTR CYCLE.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| B3 B3 |

| | 13 | 81 |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | B3 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

5–36

RIO Block Transfer

Rung 2:3

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTR

ENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUES

CHECKING THE BTR STATUS UNTIL THE SN TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| B3 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

Rung 2:4

| |

| VIRTUAL |

| BTR ERROR |

| BIT |

| B3 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1615 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 81 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:5

INITIATE A BTR FOR EACH FALSE–TO–TRUE TRANSITION OF THE USER INPUT.

| USER LOGIC |

| TO |

| INITIATE A |

| BTR |

| I:2 B3 B3 |

|––––] [––––––[OSR]–––––––––––––––––––––––––––––––––––––––––––––––––––––––(L)––|

| 0 82 83 |

Rung 2:6

WHEN USER LOGIC INITIATES A NEW BTR, LATCH THE ENABLE BIT AS LONG AS A BTR IS

NOT IN PROGRESS. ALSO, LATCH THE BTR PENDING BIT SO THE BTR STATUS FILE WILL BE

READ BY THE LADDER PROGRAM.

| | | |

| VIRTUAL |VIRTUAL |VIRTUAL |

| BTR ENABLE|BTR DONE |BTR ERROR BTR |

| BIT |BIT |BIT PENDING |

| B3 B3 B3 B3 B3 |

|––] [–––––]/[––––––––]/[––––––––]/[––––––––––––––––––––––––––––+––––(L)–––––+–|

| 83 1615 13 12 | 80 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | B3 | |

| +––––(L)–––––+ |

| | 1615 | |

| | B3 | |

| +––(U)–––––––+ |

| 83 |

Rung 2:7

MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR IS

IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS ARE

ALL TURNED OFF, COMPLETING THE BTR HAND–SHAKE PROCESS.

| |

| VIRTUAL BTR |

| BTR ENABLE CONTROL |

| BIT WORD |

| B3 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 1615 | |Source B3:100| |

| | | | 0000000000000000| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | B3 | |

| +––––] [–––––+ |

| 12 |

Rung 2:8

| |

5–37

Publication 17476.6 - July 1996

5–38

RIO Block Transfer

Bidirectional Continuous Block Transfer Example

The following rungs demonstrate a bidirectional continuous block transfer. The BTR and BTW will each execute as fast as possible, continuously and independently of one another.

Rung 2:0

CONFIGURE THE BT OPERATION TYPE, LENGTH AND RIO ADDRESS (R,G,S IN DECIMAL) AT

POWER–UP. BIT N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND BIT N7:53/7

MUST BE A LOGICAL ”0” TO INDICATE A BTW OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 15 | |Source #N7:50| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTW | |

| | CONTROL | |

| | +COP–––––––––––––––+ | |

| +–+COPY FILE +–+ |

| |Source #N7:53| |

| |Dest #M0:1.200| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTR IS IN PROGRESS.

THIS STATUS INFORMATION WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT

THE NUMBER OF M–FILE ACCESSES.

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 0 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 2 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BIT

BEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE

COMPLETE BTR CYCLE.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| N7:60 B3 |

| | 13 | 2 |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:3

COPY THE BTW STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTW IS IN PROGRESS.

THIS STATUS DATA WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT THE

NUMBER OF M–FILE ACCESSES.

| |

| BTW BTW |

| PENDING STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 1 | |Source #M1:1.200| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 3 |

Rung 2:4

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BIT

BEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETES

ONE BTW CYCLE.

| |

| VIRTUAL |

| BTW DONE CHECK BTW |

| BIT STATUS |

| N7:64 B3 |

| | 13 | 3 |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––]/[–––––+ |

| 12 |

5–39

Publication 17476.6 - July 1996

5–40

RIO Block Transfer

Rung 2:5

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH BOTH THE

BTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE BIT THAT

CONTINUES CHECKING THE BTR STATUS UNTIL THE SN MODULE TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| N7:60 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Rung 2:6

WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTR

ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT IN

ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL IT

TURNS OFF THE ERROR BIT, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL |

| BTR ERROR BTR ERROR |

| BIT CODE |

| N7:60 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:7

WHEN A BTW SUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT AND THE BTW

PENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THAT CONTINUES

CHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE BIT OFF.

| |

| VIRTUAL |

| BTW DONE BTW |

| BIT PENDING |

| N7:64 B3 |

| 13 | 1 | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | N7:53 | |

| +––––(U)–––––+ |

| | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––+ |

| 3 |

Rung 2:8

WHEN A BTW UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTW

ENABLE BIT AND THE BTW PENDING BIT. ALSO, LATCH THE CHECK BTW STATUS BIT IN

ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL IT

TURNS OFF THE ERROR BIT, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL |

| BTW ERROR BTW ERROR |

| BIT CODE |

| N7:64 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.203| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTW | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 1 | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | N7:53 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 3 |

5–41

Publication 17476.6 - July 1996

5–42

RIO Block Transfer

Rung 2:9

THIS RUNG WILL EXECUTE BLOCK TRANSFER READS CONTINUOUSLY, AS FAST AS POSSIBLE.

| | | |

| VIRTUAL |VIRTUAL |VIRTUAL |

| BTR ENABLE|BTR DONE |BTR ERROR BTR |

| BIT |BIT |BIT PENDING |

| N7:50 N7:60 N7:60 B3 |

| 15 13 12 | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(L)–––––+ |

| 15 |

Rung 2:10

THIS RUNG WILL EXECUTE BLOCK TRANSFER WRITES CONTINUOUSLY, AS FAST AS POSSIBLE.

| | | |

| VIRTUAL |VIRTUAL |VIRTUAL |

| BTW ENABLE|BTW DONE |BTW ERROR |

| BIT |BIT |BIT BTW DATA |

| N7:53 N7:64 N7:64 +COP–––––––––––––––+ |

|––––]/[––––––––]/[––––––––]/[––––––––––––––––––––––––+–+COPY FILE +–+–|

| 15 13 12 | |Source #N7:10| | |

| | +––––––––––––––––––+ | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | N7:53 | |

| +––––(L)–––––––––––––––+ |

| | 15 | |

| | | |

| | BTW | |

| | PENDING | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 1 |

Rung 2:11

MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE , DONE AND ERROR BITS

ARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL BTR |

| BTR ENABLE CONTROL |

| BIT BITS |

| N7:50 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:50| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| 12 |

Publication 17476.6 - July 1996

RIO Block Transfer

5–43

Rung 2:12

MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTW

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS

ARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL BTW |

| BTW ENABLE CONTROL |

| BIT BITS |

| N7:53 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:53| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTW DONE | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| 12 |

Rung 2:13

| |

Bidirectional Alternating Block Transfer

The following rungs demonstrate a bidirectional alternating block transfer. Using these rungs ensures the block transfer requests are executed in the order in which they are sent to the queue. This example also ensures that the block transfer read and block transfer write alternate. The XIO conditions prevent the BTR and BTW from queueing simultaneously. The block transfers continue as long as the

XIC precondition bit is true.

Rung 2:0

CONFIGURE THE BT OPERATION TYPE, LENGTH, AND RIO ADDRESS (R,G,S IN DECIMAL) AT

POWER–UP. N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND N7:53/7 MUST BE

A LOGICAL ”0” TO INDICATE A BTW OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 15 | |Source #N7:50| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTW | |

| | CONTROL | |

| | +COP–––––––––––––––+ | |

| +–+COPY FILE +–+ |

| |Source #N7:53| |

| |Dest #M0:1.200| |

| |Length 3| |

| +––––––––––––––––––+ |

Publication 17476.6 - July 1996

5–44

RIO Block Transfer

COPY THE BTR STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTR IS IN PROGRESS.

THIS STATUS DATA WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT THE

NUMBER OF M–FILE ACCESSES.

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 0 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 2 |

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BIT

BEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE

COMPLETE BTR CYCLE.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| N7:60 B3 |

| | 13 | 2 |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––]/[–––––+ |

| 12 |

Rung 2:3

COPY THE BTW STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTW IS IN PROGRESS.

THIS STATUS DATA WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT THE

NUMBER OF M–FILE ACCESSES.

| |

| BTW BTW |

| PENDING STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 1 | |Source #M1:1.200| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 3 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:4

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BIT

BEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETES

ONE BTW CYCLE.

| |

| VIRTUAL |

| BTW DONE CHECK BTW |

| BIT STATUS |

| N7:64 B3 |

| | 13 | 3 |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––]/[–––––+ |

| 12 |

Rung 2:5

WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH BOTH THE

BTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE BIT THAT

CONTINUES CHECKING THE BTR STATUS UNTIL THE SN MODULE TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| N7:60 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

5–45

Publication 17476.6 - July 1996

5–46

RIO Block Transfer

Rung 2:6

WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE BTR ERROR CODE AND UNLATCH THE

BTR ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT

IN ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL IT

TURNS THE ERROR BIT OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL |

| BTR ERROR BTR ERROR |

| BIT CODE |

| N7:60 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Rung 2:7

WHEN A BTW SUCCESSFULLY OR UNSUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT

AND THE BTW PENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THAT

CONTINUES CHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE/ERROR BIT

OFF.

| |

| VIRTUAL |

| BTW DONE BTW |

| BIT PENDING |

| N7:64 B3 |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––+––––(U)–––––––––––––––+–|

| | 13 | | 1 | |

| | | | | |

| | BIT | | BIT | |

| | N7:64 | | N7:53 | |

| +––––] [–––––+ +––––(U)–––––––––––––––+ |

| 12 | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| | 3 | |

| | | |

| | BTW ERROR | |

| | CODE | |

| | +MOV–––––––––––––––+ | |

| +–+MOVE +–+ |

| |Source M1:1.203| |

| | *| |

| |Dest N7:22| |

| | 0| |

| +––––––––––––––––––+ |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:8

THIS RUNG AND THE NEXT RUNG WILL TOGGLE BETWEEN EXECUTING A BTR AND A BTW

WHILE THE USER SUPPLIED BT PRECONDITION BIT (B3:0/11 IS USED IN THIS EXAMPLE)

IS TRUE.

| | | | | |

| DITION BIT|BIT |BIT |BIT |BIT PENDING |

| B3 N7:50 N7:53 N7:60 N7:60 B3 |

|––––] [––––––––]/[––––––––]/[––––––––]/[––––––––]/[––––––––––––+––––(L)–––––+–|

| 11 15 15 13 12 | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(L)–––––+ |

| 15 |

Rung 2:9

| | | | | |

| DITION BIT|BIT |BIT |BIT |BIT BTW DATA |

| B3 N7:50 N7:53 N7:64 N7:64 +COP–––––––––––––––+ |

|––––] [––––––––]/[––––––––]/[––––––––]/[––––––––]/[|–+–+COPY FILE +–+–|

| 11 15 15 13 12 | |Source #N7:10| | |

| | +––––––––––––––––––+ | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | N7:53 | |

| +––––(L)–––––––––––––––+ |

| | 15 | |

| | | |

| | BTW | |

| | PENDING | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 1 |

5–47

Publication 17476.6 - July 1996

5–48

RIO Block Transfer

Rung 2:10

MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS

ARE ALL TURNED OFF.

| |

| VIRTUAL BTR |

| BTR ENABLE CONTROL |

| BIT BITS |

| N7:50 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:50| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| 12 |

Rung 2:11

MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTW

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS

ARE ALL TURNED OFF.

| |

| VIRTUAL BTW |

| BTW ENABLE CONTROL |

| BIT BITS |

| N7:53 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:53| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTW DONE | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| 12 |

Rung 2:12

| |

Publication 17476.6 - July 1996

RIO Block Transfer

5–49

Bidirectional Alternating Repeating Block Transfer

The following rungs demonstrate a bidirectional alternating repeating block transfer. Using these rungs ensures the block transfer requests are executed in the order in which they are sent to the queue. This example also ensures that the BTR and BTW repeatedly alternate. The XIO conditions prevent the BTR and BTW from queuing simultaneously. The BT’s continue as long as the ladder rungs are scanned.

Rung 2:0

CONFIGURE THE BT OPERATION TYPE, LENGTH AND RIO ADDRESS (R,G,S IN DECIMAL) AT

POWER–UP. BIT N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND N7:53/7 MUST

BE A LOGICAL ”0” TO INDICATE A BTW OPERATION.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 15 | |Source #N7:50| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTW | |

| | OPERATION | |

| | +COP–––––––––––––––+ | |

| +–+COPY FILE +–+ |

| |Source #N7:53| |

| |Dest #M0:1.200| |

| |Length 3| |

| +––––––––––––––––––+ |

Rung 2:1

COPY THE BTR STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTR IS IN PROGRESS.

THIS STATUS DATA WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT THE

NUMBER OF M–FILE ACCESSES

| |

| BTR |

| PENDING BTR STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 0 | |Source #M1:1.100| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 2 |

Publication 17476.6 - July 1996

5–50

RIO Block Transfer

Rung 2:2

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BIT

BEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONE

COMPLETE BTR CYCLE.

| |

| VIRTUAL |

| BTR DONE CHECK BTR |

| BIT STATUS |

| N7:60 B3 |

| | 13 | 2 |

| | | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––]/[–––––+ |

| 12 |

Rung 2:3

COPY THE BTW STATUS AREA TO AN INTEGER FILE ONLY WHEN A BTW IS IN PROGRESS.

THIS STATUS DATA WILL THEN BE USED THROUGHOUT THE PROGRAM AND WILL LIMIT THE

NUMBER OF M–FILE ACCESSES.

| |

| BTW BTW |

| PENDING STATUS |

| B3 +COP–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| | 1 | |Source #M1:1.200| |

| | | +––––––––––––––––––+ |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––] [–––––+ |

| 3 |

Rung 2:4

UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW IS

COMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH

THE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BIT

BEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETES

ONE BTW CYCLE.

| |

| VIRTUAL |

| BTW DONE CHECK BTW |

| BIT STATUS |

| N7:64 B3 |

| | 13 | 3 |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––]/[–––––+ |

| 12 |

Publication 17476.6 - July 1996

RIO Block Transfer

5–51

Rung 2:5

WHEN A BTR SUCCESSFULLY COMPLETES

BUFFER THE BTR DATA AND UNLATCH BOTH THE

BTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT

ALSO

LATCH THE BIT THAT

CONTINUES CHECKING THE BTR STATUS UNTIL THE SN MODULE TURNS OFF THE DONE BIT.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| N7:60 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Rung 2:6

WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTR

ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT IN

ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL IT

TURNS THE ERROR BIT OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| BTR ERROR |

| BIT |

| N7:60 +MOV–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|

| 12 | |Source M1:1.103| | |

| | | *| | |

| | | 0| | |

| | +––––––––––––––––––+ | |

| | | |

| | BTR | |

| | PENDING | |

| | B3 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | CHECK BTR | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Publication 17476.6 - July 1996

5–52

RIO Block Transfer

Rung 2:7

WHEN A BTW SUCCESSFULLY OR UNSUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT

AND THE BTW PENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THAT

CONTINUES CHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE/ERROR BIT

OFF. IN ADDITION, BUFFER THE BTW ERROR CODE IN CASE AN ERROR OCCURS.

| |

| VIRTUAL |

| BTW DONE BTW |

| BIT PENDING |

| N7:64 B3 |

| | 13 | | 1 | |

| | | | | |

| | BIT | | BIT | |

| | N7:64 | | N7:53 | |

| +––––] [–––––+ +––––(U)–––––––––––––––+ |

| 12 | 15 | |

| | | |

| | CHECK BTW | |

| | STATUS | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| | 3 | |

| | | |

| | BTW ERROR | |

| | CODE | |

| | +MOV–––––––––––––––+ | |

| +–+MOVE +–+ |

| |Source M1:1.203| |

| | *| |

| |Dest N7:22| |

| | 0| |

| +––––––––––––––––––+ |

Rung 2:8

THIS RUNG AND THE NEXT RUNG WILL TOGGLE BETWEEN EXECUTING A BTR AND A BTW.

| | | | |

| BIT |BIT |BIT |BIT PENDING |

| N7:50 N7:53 N7:60 N7:60 B3 |

|––––]/[––––––––]/[––––––––]/[––––––––]/[–––––––––––––––––––––––+––––(L)–––––+–|

| 15 15 13 12 | 0 | |

| | | |

| +++ +++|

| | | |

| | VIRTUAL | |

| | BTR ENABLE | |

| | BIT | |

| | N7:50 | |

| +––––(L)–––––+ |

| 15 |

Publication 17476.6 - July 1996

RIO Block Transfer

Rung 2:9

| | | | |

| BIT |BIT |BIT |BIT BTW DATA |

| N7:50 N7:53 N7:64 N7:64 +COP–––––––––––––––+ |

|––––]/[––––––––]/[––––––––]/[––––––––]/[–––––––––––––+–+COPY FILE +–+–|

| 15 15 13 12 | |Source #N7:10| | |

| | +––––––––––––––––––+ | |

| | | |

| | VIRTUAL | |

| | BTW ENABLE | |

| | BIT | |

| | N7:53 | |

| +––––(L)–––––––––––––––+ |

| | 15 | |

| | | |

| | BTW | |

| | PENDING | |

| | B3 | |

| +––––(L)–––––––––––––––+ |

| 1 |

Rung 2:10

MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS

ARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL BTR |

| BTR ENABLE CONTROL |

| BIT WORD |

| N7:50 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:50| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTR DONE | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | BTR ERROR | |

| | BIT | |

| | N7:60 | |

| +––––] [–––––+ |

| 12 |

5–53

Publication 17476.6 - July 1996

5–54

RIO Block Transfer

Rung 2:11

MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR

IS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS

ARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.

| |

| VIRTUAL BTW |

| BTW ENABLE CONTROL |

| BIT WORD |

| N7:53 +MOV–––––––––––––––+ |

|–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|

| | 15 | |Source N7:53| |

| | | | 0| |

| | | | *| |

| | | +––––––––––––––––––+ |

| | | |

| | VIRTUAL | |

| | BTW DONE | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| | 13 | |

| | | |

| | VIRTUAL | |

| | BTW ERROR | |

| | BIT | |

| | N7:64 | |

| +––––] [–––––+ |

| 12 |

Rung 2:12

| |

Publication 17476.6 - July 1996

RediPANEL Keypad

Module

Application Examples

Chapter

This chapter provides application examples for systems configured with the following:

•

RediPANEL Keypad Module

•

RediPANEL/DCM

•

Dataliner

•

PanelView

• a 4 to 20 mA transducer

In the following example, a Bulletin 2705 RediPANEL is used to display stored messages. An alarm is connected to an output module in case communications with the RediPANEL is lost. The system consists of:

•

Catalog Number 1747-L524 processor (SLC 5/02) in slot 0

•

Catalog Number 1747-SN (RIO Scanner) in slot 1

•

Catalog Number 1746-OB8 (output module) in slot 2

• an alarm connected to the output module

•

Bulletin 2705 RediPANEL

Alarm

RIO Network

RediPANEL

Publication 17476.6 - July 1996

7–2

Application Examples

As shown in the G file below, the RediPANEL is configured as a half rack device beginning at rack 0, group 0.

G File

Device Address, Word 1

Device Size, Word 2

RIO Rack 3

Starting Group

4 2

0 0

0 0 0

RIO Rack 2

Starting Group

4 2

0 0

0 0 0

RIO Rack 1

Starting Group

4 2

0 0

0 0 0

RIO Rack 0

Starting Group

4 2

0 0

0 0 1 1

The scanner input file is shown below. The output file is similar, it is addressed O:1.0 to O:1.3.

Bit Number

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 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

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

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

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

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

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Bit Number (octal)

15 14

13 12 11 10 9

8 7

6 5 4 3

Input File

I:1.0

I:1.1

I:1.2

RediPANEL

I:1.3

I:1.10

I:1.11

I:1.12

I:1.13

I:1.14

I:1.15

I:1.16

I:1.17

I:1.18

I:1.4

I:1.5

I:1.6

I:1.7

I:1.8

I:1.9

I:1.19

I:1.20

I:1.21

I:1.22

I:1.23

I:1.24

I:1.25

I:1.26

I:1.27

I:1.28

I:1.29

I:1.30

I:1.31

= not used

Publication 17476.6 - July 1996

Application Examples

7–3

Scanner Configuration

The baud rate is 115.2K. DIP switch 1 should be in the ON position;

DIP switch 2 should be OFF.

The G file size is set to 3 using the Specialty I/O Configuration function. The M0 and M1 file sizes are set to 32 in the Advanced Set

Up function.

Since only the first 4 words of the input and output files contain valid information, the scanned input and output words can be set to

4. Reducing the number of scanned input and output words decreases your SLC scan time.

Configuration information is entered in the Modify G File function.

Word 0 is reserved, and therefore, cannot be modified. Word 1 indicates the starting address of the device; word 2 indicates its size.

Example Program

The example program is shown below. Each time a function key is pressed on the RediPANEL, its associated message is displayed.

This program also monitors the scanner’s Enabled Device Fault bit

(M1:1.0/0). If communications is lost, an alarm is activated.

If the Communications attempted and

Enabled Device Fault bits are set to 1, activate the alarm.

MEQ

MASKED EQUAL

Source M1:1.0

Mask

Compare

0003

O:2

( )

If function key 1 is pressed (bit 8 of input word 0), T4:0 Preset is moved to the display.

I:1.0

] [

MOV

MOVE

Source

Dest

T4:0.PRE

O:1.1

When a new number is entered onto the RediPANEL, it is moved to preset T4:0.

I:1.0

] [

If function key 2 is pressed (bit 9 of input word 0), RediPANEL message

#2 is triggered and displayed.

I:1.0

] [

MOV

MOVE

Source

Dest

I:1.1

T4:0.PRE

MOV

MOVE

Source

Dest

O:1.2

END

Publication 17476.6 - July 1996

7–4

Application Examples

RediPANEL/DCM

In this example, a Bulletin 2705 RediPANEL and a Catalog Number

1747-DCM are connected to the RIO network. This combination forms a distributed control system consisting of two SLC processors monitored from a single operator interface device.

The system consists of:

•

Catalog Number 1747-L524 processor (SLC 5/02) in slot 0 of the first SLC controller

•

Catalog Number 1747-SN (RIO Scanner) in slot 1 of the first

SLC controller

•

Bulletin 2705 RediPANEL

•

Catalog Number 1747-L511 processor (SLC 5/01 t

) in slot 0 of the second SLC controller

•

Catalog Number 1747-DCM in slot 1 of the second SLC controller

Controller 1

SLC 5/02 Processor

RIO Scanner

RIO Network

RediPANEL

SLC 5/01 Processor

DCM (Direct Communications

Module)

Controller 2

Publication 17476.6 - July 1996

Application Examples

7–5

As shown in the G file (of controller 1) below, the RediPANEL is configured as a three quarter rack device beginning at rack 0, starting group 0. The Catalog Number 1747-DCM is configured as a half rack device beginning at rack 1, starting group 0.

G File

Device Address, Word 1

Device Size, Word 2

RIO Rack 3

Starting Group

4 2 0

RIO Rack 2

Starting Group

4 2 0

RIO Rack 1

Starting Group

4 2

RIO Rack 0

Starting Group

4 2 0

The scanner input file is shown below. The output file is similar, it is addressed O:1.0 to O:1.5 for the RediPANEL and O:1.8 to O:1.11 for the DCM.

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 Group 3

Rack 0

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

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 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

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

Bit Number

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 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 30

Word 31

Bit Number (octal)

15 14 13 12 11 10 9 8

I:1.24

I:1.25

I:1.26

I:1.27

I:1.28

I:1.29

I:1.30

I:1.14

I:1.15

I:1.16

I:1.17

I:1.18

I:1.19

I:1.20

I:1.21

I:1.22

I:1.23

Input File

I:1.0

I:1.1

I:1.2

I:1.3

I:1.4

I:1.5

I:1.6

I:1.7

I:1.8

I:1.9

I:1.10

I:1.11

I:1.12

I:1.13

I:1.31

RediPANEL

DCM

= not used

Publication 17476.6 - July 1996

7–6

Application Examples

Scanner Configuration

The baud rate is 115.2K. DIP switch 1 should be in the ON position;

DIP switch 2 should be OFF.

The G file size is set to 3 using the Specialty I/O Configuration function. The M0 and M1 file sizes are set to 32 in the Advanced Set

Up function.

Since only the first 12 words of the input and output files contain valid information, the scanned input and output words can be set to

12. Reducing the number of scanned input and output words decreases your SLC scan time.

Configuration information is entered in the Modify G File function.

Word 0 is reserved and, therefore, cannot be modified. Word 1 indicates the starting address of the device; word 2 indicates its size.

Example Program

The example program is shown on the following page. During normal operation, the program moves input word 2 from the DCM

(I:1.10) to output word 2 of the RediPANEL (O:1.2). This allows the

DCM to select a message to be displayed on the RediPANEL. Bit 8 of the RediPANEL input word 0 (I:1.0/8) activates bit 1 of the DCM output word 2 (O:1.10/1).

Upon the scanner’s first scan, the application program copies the M1 file to integer file N7. The contents of the M1 file can then be monitored by performing a data monitor of the N7 file. The baud rate (M1:1.2), device address (M1:1.8), and device size (M1:1.9) information will not change during operation. The general status

(M1:1.0) and active device status (M1:1.10) words are updated in the integer file upon each scan.

The program monitors the active device status bits that are transferred to the integer file. If the RediPANEL is not active, the

DCM is forced to a reset by setting the device reset bit (M0:1.17). If the DCM is not active, an error message (message #4) is displayed on the RediPANEL by moving 4 to output word 2 (O:1.2).

The active device status bits are conditioned with the communication attempted bit (M1:1.1) before any fault actions are taken. This ensures that the scanner has attempted to communicate with all configured devices before an inactive device is considered faulted.

Publication 17476.6 - July 1996

Move input word 10 (I:1.10) from the DCM to output word 2 (O:1.2) of the RediPANEL.

Bit 8 of the RediPANEL input word 0 activates bit 1 of the DCM output word 2.

Upon the first processor scan, move the baud rate setting, device address, and device size to integer file N7.

I:1.0

] [

S:1

] [

Move the active device status and general status words to integer file N7 upon each scan.

If communications is attempted and the

RediPANEL is not communicating, reset the DCM.

If communications is attempted and the

DCM is not communicating, display message 4 on the RediPANEL.

N7:0

N7:4

N7:0

N7:4

Application Examples

MOV

MOVE

Source

Dest

7–7

I:1.10

O:1.2

O:1.10

( )

MOV

MOVE

Source

Dest

MOV

MOVE

Source

Dest

MOV

MOVE

Source

Dest

M1:1.2

N7:1

M1:1.8

N7:2

M1:1.9

N7:3

MOV

MOVE

Source

Dest

MOV

MOVE

Source

Dest

M1:1.10

N7:4

M1:1.0

N7:0

M0:1.17

( )

MOV

MOVE

Source

Dest

O:1.2

END

Publication 17476.6 - July 1996

7–8

Dataliner

Application Examples

In the following example, a DL40 Dataliner is used to display a stored message containing an accumulator value when certain counting conditions are met. In addition, the Dataliner displays an alarm message that must be acknowledged with the

[MSG ACK]

button located on its front panel when conveyor alarm conditions exist.

The system consists of a:

•

Catalog Number 1747-L524 processor (SLC 5/02) in slot 0

•

Catalog Number 1747-SN scanner (RIO Scanner) in slot 1

•

Catalog Number 2706 Dataliner Message Display

SLC 5/02 Processor

RIO Scanner

RIO Network

Dataliner Message Display

Publication 17476.6 - July 1996

Application Examples

7–9

As shown in the G file below, the Dataliner is configured as a half rack device beginning at rack 1, starting group 0.

G File

Device Address, Word 1

Device Size, Word 2

RIO Rack 3

Starting Group

4 2

0 0

0 0 0

RIO Rack 2

Starting Group

4 2

0 0

0 0 0

RIO Rack 1

Starting Group

4 2

0 0

0 1 1

RIO Rack 0

Starting Group

4 2

0 0

0 0 0 0

The scanner input file is shown below. The output file is similar, it is addressed O:1.8 to O:1.11.

Bit Number

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0

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

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

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 Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

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

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Bit Number (octal)

15 14 13 12 11 10 9 8

I:1.25

I:1.26

I:1.27

I:1.28

I:1.29

I:1.30

I:1.31

I:1.19

I:1.20

I:1.21

I:1.22

I:1.23

I:1.24

I:1.9

I:1.10

I:1.11

I:1.12

I:1.13

I:1.14

I:1.15

I:1.16

I:1.17

I:1.18

Input File

I:1.0

I:1.1

I:1.2

I:1.3

I:1.4

I:1.5

I:1.6

I:1.7

I:1.8

Dataliner

= not used

Publication 17476.6 - July 1996

7–10

Application Examples

Scanner Configuration

The baud rate is 115.2K. DIP switch 1 should be in the ON position;

DIP switch 2 should be OFF.

The G file size is set to 3 using the Specialty I/O Configuration function. The M0 and M1 file sizes are set to 32 in the Advanced Set

Up function.

Since only the first 12 words of the input and output files contain valid information, the scanned input and output words can be set to

12. Reducing the number of scanned input and output words decreases your SLC scan time.

Configuration information is entered in the Modify G File function.

Word 0 is reserved and, therefore, cannot be modified. Word 1 indicates the starting address of the device; word 2 indicates its size.

Example Program

Cycle

Counting

Conditions

Message 1 is triggered by moving the value 1 to output module group 0 of the

Dataliner.

This also updates an embedded variable in message 1 by moving the accumulated value of counter C5:0 to output module group 1 of the Dataliner.

If alarm conditions go from false to true, trigger message 2 by sending the value 2 to output module group 0 of the Dataliner.

If B3/0 is ON, message 2 has not been acknowledged.

If the Dataliner input module group 1 is equal to 2 (message 2 is presently displayed) and the

[MSG ACK]

button is pressed (I:1.8/13), unlatch the Alarm Not

Acknowledged bit (B3/0).

MOV

MOVE

Source

Dest

O:1.8

MOV

MOVE

Source

Dest

C5:0.ACC

O:1.9

Conveyor

Alarm

Conditions

OSR

EQU

EQUAL

Source A

Source B

I:1.9

MOV

MOVE

Source

Dest

O:1.8

I:1.8

END

Publication 17476.6 - July 1996

PanelView

Application Examples

7–11

In the following example, a Catalog Number 2711-KC1 PanelView terminal is used to control a pump and display its ON/OFF status and pressure. The pump is connected to an output module and a pressure gauge is connected to an analog input module.

The system consists of:

• a Catalog Number 1747-L524 processor (SLC 5/02) in slot 0

• a Catalog Number 1747-SN scanner (RIO Scanner) in slot 1

• an output module in slot 2

• an analog input module in slot 3

• a pump connected to the output module

• a pressure gauge connected to the input module

• a Catalog Number 2711-KC1 PanelView terminal

SLC 5/02 Processor

RIO Scanner

Output Module

Analog Input Module

Pump

Pressure Gauge

PanelView Operator Terminal

Publication 17476.6 - July 1996

7–12

Application Examples

As shown in the G file below, the PanelView terminal is configured as a one and three quarter device beginning at rack 2, starting group

0. The scanner addresses the PanelView terminal as if it were two devices, one full rack and another three quarter rack.

G File

Device Address, Word 1

Device Size, Word 2

RIO Rack 3

Starting Group

4 2 0

RIO Rack 2

Starting Group

4 2 0

RIO Rack 1

Starting Group

4 2

RIO Rack 0

Starting Group

4 2 0

The scanner input file is shown below. The output file is similar, it is addressed O:1.16 to O:1.29.

Bit Number

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 Group 3

Rack 0

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

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

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

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

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 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 15

Word 16

Word 17

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Bit Number (octal)

15 14 13 12 11 10 9 8

I:1.9

I:1.10

I:1.11

I:1.12

I:1.13

I:1.14

I:1.15

I:1.16

I:1.17

I:1.18

Input File

I:1.0

I:1.1

I:1.2

I:1.3

I:1.4

I:1.5

I:1.6

I:1.7

I:1.8

I:1.19

I:1.20

I:1.21

I:1.22

I:1.23

I:1.24

I:1.25

I:1.26

I:1.27

I:1.28

I:1.29

I:1.30

I:1.31

PanelView

= not used

Publication 17476.6 - July 1996

Application Examples

7–13

Scanner Configuration

The baud rate is 115.2K. DIP switch 1 should be in the ON position;

DIP switch 2 should be OFF.

The G file size is set to 3 using the Specialty I/O Configuration function. The M0 and M1 file sizes are set to 32 in the Advanced Set

Up function.

Since only the first 30 words of the input and output files contain valid information, the scanned input and output words can be set to

30. Reducing the number of scanned input and output words decreases your SLC scan time.

Configuration information is entered in the Modify G File function.

Word 0 is reserved and, therefore, cannot be modified. Word 1 indicates the starting address of the device; word 2 indicates its size.

Example Program

If the ON push button is pressed, turn the pump on. If the OFF pushbutton is pressed, turn the pump off.

When the pump is on, display the pressure from the pressure gauge on the PanelView terminal Numeric Value Display.

ON button

I:1.16

OFF button

I:1.16

O:2

] [

O:2

MOV

MOVE

Source

Dest

Pump

O:2

( )

I:3.0

O:1.17

When the pump is on, display the ON state of the multistate indicator on the

PanelView.

Pump ON

Conditions

O:1.16

( )

END

Publication 17476.6 - July 1996

7–14

Application Examples

Block Transfer Application

Example

In the following example, a technician has these requirements:

• install a 4 to 20 mA transducer located approximately 701 meters

(2,300 feet) from an SLC 5/03 processor

• bring this analog input value from the transducer into the SLC processor as well as display the analog value on a meter at the remote location

• the meter must display 0 to 100% and accept a 4 to 20 mA signal

• in addition, the remote I/O scanner in the SLC processor chassis has only 1/4 logical rack of I/O image space remaining (due to other RIO devices on this RIO link)

• needs 16 discrete inputs and 16 discrete outputs at this same remote location

The local system consists of (refer to system layout diagram):

• a Catalog Number 1747-L532 processor (SLC 5/03) in slot 0

• a Catalog Number 1747-SN scanner (RIO Scanner) in slot 1 with only 1/4 logical rack of the I/O image available

With only 1/4 logical rack image to work with, the remote system consists of (refer to system layout diagram):

•

4-slot remote chassis with a 1747-ASB in slot 0

•

1746-IV16 module in slot 1

•

1746-OV16 module in slot 2

•

1746-NIO4I in slot 3

2-slot addressing must be selected for the remote chassis to keep its image size to 1/4 logical rack. The discrete modules use the entire image for logical rack 3, group 6 in a complementary slot pair arrangement and the combination analog module uses the image for logical rack 3, group 7. This image size for the analog module is 1 input and 1 output word short of what is required by the NIO4I module. Therefore, block transfer to/from the analog module will be used (BT operations only require one input and one output byte). In the future, the other analog input and output on the 1747-NIO4I may be used.

Scanner Configuration

The technician addresses the 1747-ASB to logical rack 3, starting logical group 6. Since the analog module’s image (2 input/output words) will not fit into one logical group (1 input/output word), he must use block transfer to read analog input values and write to analog outputs. In this example, the SLC processor will receive the analog input data via BTR, scale it, and send it to the analog output via a BTW.

Publication 17476.6 - July 1996

Application Examples

7–15

As shown in the G file below, the 1747-ASB consumes 1/4 logical rack of the scanner’s I/O image table beginning at logical rack 3, starting at group 6.

G File

Device Address, Word 1

Device Size, Word 2

1 0

ÉÉ

RIO Rack 3

Starting Group

ÉÉ ÉÉ

RIO Rack 2

Starting Group

4 2 0

RIO Rack 1

Starting Group

4 2

RIO Rack 0

Starting Group

4 2 0

The scanner input file is shown below.

Bit Number

Rack 0 Group 0

Rack 0 Group 1

Rack 0 Group 2

Rack 0 Group 3

Rack 0

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

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

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

Rack 3 Group 3

Rack 3 Group 4

Rack 3 Group 5

Rack 3 Group 6

Rack 3 Group 7

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

Word 0

Word 1

Word 2

Word 3

Word 4

Word 5

Word 6

Word 7

Word 8

Word 9

Word 10

Bit Number (octal)

15 14 13 12 11 10 9 8

Input File

I:1.0

I:1.1

I:1.2

I:1.3

I:1.4

I:1.5

I:1.6

I:1.7

I:1.8

I:1.9

I:1.10

I:1.11

I:1.12

I:1.13

I:1.14

I:1.15

I:1.16

I:1.17

I:1.18

I:1.19

I:1.20

I:1.21

I:1.22

I:1.23

I:1.24

I:1.25

I:1.26

I:1.27

I:1.28

I:1.29

I:1.30

I:1.31

IV16 - OV16 uses O:1.30

1746NIO4I also uses

O:1.31

= used by other devices

Publication 17476.6 - July 1996

7–16

Application Examples

SLC 5/03 Processor

RIO Scanner

System Layout Diagram

Local System

Remote System

RIO Link

1747-ASB

IV16 Module

OV16 Module

NIO4I

Output

To Other RIO

Devices

100

4 to 20 mA Analog

Meter

(0 to 100%)

Input

4 to 20 mA Transducer

Example Program

The following program samples the analog input data from the

1746-NIO4I module located in the remote I/O chassis every 100 ms by executing a BTR every 100 ms. This data is then scaled for the

4 to 20 mA output and sent back to the analog module via a BTW.

The meter will then display the 4 to 20mA analog output as a 0 to

100% scale. Refer to the system layout diagram above. Also refer to the analog module user manual, Catalog Number 1746-6.4 for details on analog input and output ranges as well as scaling.

Important:

The following block transfer program example accesses multiple M-file addresses throughout the program. This increases the SLC processor scan time. If processor scan time is a concern, please refer to the block transfer

program examples in chapter 5 instead. These

examples manage the M-file addresses more efficiently.

Publication 17476.6 - July 1996

Application Examples

7–17

Rung 2:0

Configure the BTR and BTW length and RIO address at power–up. Also, set the block transfer operation bit for BTR operation only.

| |

| POWER–UP BTR |

| BIT CONTROL |

| S:1 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 15 | |Source #N7:50| | |

| | +––––––––––––––––––+ | |

| | BT | |

| | OPERATION | |

| | BIT | |

| | M0:1.100 | |

| +––––(L)–––––––––––––––+ |

| | 7 | |

| | BTW | |

| | CONTROL | |

| | +COP–––––––––––––––+ | |

| +–+COPY FILE +–+ |

| |Source #N7:52| |

| |Dest #M0:1.201| |

| |Length 2| |

| +––––––––––––––––––+ |

Rung 2:1

Copy the BTR status area to an integer file only when a BTR is in progress. This status data will then be used throughout the program and will limit the number of

M–File accesses.

| SERVICE |

| THE BTR |

| STATUS/ |

| BTR |

| PENDING BTR STATUS |

| B3:0 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 0 |Source #M1:1.100| |

| |Dest #N7:60| |

| |Length 4| |

| +––––––––––––––––––+ |

Rung 2:2

Copy the BTW status area to an integer file only when a BTW is in progress. This status data will then be used throughout the program and will limit the number of

M–File accesses.

| SERVICE |

| THE BTW |

| STATUS/ |

| BTW BTW |

| PENDING STATUS |

| B3:0 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|

| 1 |Source #M1:1.200| |

| |Dest #N7:64| |

| |Length 4| |

| +––––––––––––––––––+ |

Publication 17476.6 - July 1996

7–18

Application Examples

Rung 2:3

When a BTR successfully completes, buffer the block transfer data and unlatch both the BTR enable bit and the BTR pending bit. The data in this example is from analog input 0 located at remote address: Logical Rack 3, Group 7, left slot (0).

This analog input is 4–20mA input from a transducer.

| |

| VIRTUAL |

| BTR DONE |

| BIT BTR DATA |

| N7:60 +COP–––––––––––––––+ |

|––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|

| 13 | |Source #M1:1.110| | |

| | +––––––––––––––––––+ | |

| | SERVICE | |

| | THE BTR | |

| | STATUS/ | |

| | BTR | |

| | PENDING | |

| | B3:0 | |

| +––––(U)–––––––––––––––+ |

| | 0 | |

| | | |

| | BTR ENABLE | |

| | BIT | |

| | M0:1.100 | |

| +––––(U)–––––––––––––––+ |

| | 15 | |

| | | |

| | GOOD BTR | |

| | DATA BIT | |

| | B3:0 | |

| +––––(L)–––––––––––––––+ |

| 2 |

Rung 2:4

When a BTW successfully completes, unlatch the BTW enable bit and the BTW pending bit to complete a BTW sequence.

| SERVICE |

| THE BTW |

| VIRTUAL STATUS/ |

| BTW DONE BTW |

| BIT PENDING |

| N7:64 B3:0 |

| 13 | 1 | |

| | | |

| | BTW ENABLE | |

| | BIT | |

| | M0:1.200 | |

| +––––(U)–––––+ |

| 15 |

Publication 17476.6 - July 1996

Application Examples

7–19

Rung 2:5

If a BTR errors, unlatch the BTR enable bit and the BTR pending bit. In addition, the BTR error code (N7:63 OR M1:1.103) must be viewed or buffered to determine the cause of the error.

| SERVICE |

| THE BTR |

| STATUS/ |

| BTR ERROR BTR |

| BIT PENDING |

| N7:60 B3:0 |

| 12 | 0 | |

| | | |

| | BTR ENABLE | |

| | BIT | |

| | M0:1.100 | |

| +––––(U)–––––+ |

| 15 |

Rung 2:6

If a BTW errors, unlatch the BTW enable bit and the BTW pending bit. In addition, the BTW error code (N7:67 OR M1;1.203) must be viewed or buffered to determine the cause of the error.

| |

| BTW ERROR BTW ENABLE |

| BIT BIT |

| N7:64 M0:1.200 |

| 12 | 15 | |

| | | |

| | SERVICE | |

| | THE BTW | |

| | STATUS/ | |

| | BTW | |

| | PENDING | |

| | B3:0 | |

| +––––(U)–––––+ |

| 1 |

Rung 2:7

Free–running timer to execute a BTR to the analog input in Logical Rack 3, Group 7 left slot every 100ms (0).

| T4:0 +TON–––––––––––––––+ |

|––]/[–––––––––––––––––––––––––––––––––––––––––––––––+TIMER ON DELAY +–(EN)–|

| DN |Timer T4:0+–(DN) |

| |Time Base 0.01| |

| |Preset 10| |

| |Accum 0| |

| +––––––––––––––––––+ |

Rung 2:8

Initiate a BTR every 100ms as long as a BTR is not in progress. A complete cycle requires that when complete or error, the ladder program unlatches the enable bit and the scanner then unlatches the done bit. A new BTR must not be initiated until these conditions occur.

| | SERVICE |

| | THE BTR |

| | STATUS/ |

| BTR ENABLE|BTR DONE BTR |

| BIT |BIT PENDING |

| T4:0 M0:1.100 M1:1.100 B3:0 |

|––] [–––––]/[––––––––]/[–––––––––––––––––––––––––––––––––––––––+––––(L)–––––+–|

| DN 15 13 | 0 | |

| | | |

| | BTR ENABLE | |

| | BIT | |

| | M0:1.100 | |

| +––––(L)–––––+ |

| 15 |

Publication 17476.6 - July 1996

7–20

Application Examples

Rung 2:9

This rung checks the analog input data (4–20MA input) to ensure that it is within the proper range and turns on outputs for under and over range. If the value is within range it is scaled to the

4–20MA analog output range and is then placed into the BTW data area. The BTW enable bit and pending bits are then latched to initiate the BTW to the analog combination module, output 0. Output 0 is connected to a meter to display the current range in percent.

| |

| GOOD BTR BELOW |

| DATA BIT RANGE FLAG |

| B3:0 +LES–––––––––––––––+ O:2.0 |

|––] [––+–+LESS THAN +–––––––––––––––––––––––––––––––––––––––––––––––––––––––––(L)–––––+–|

| 2 | |Source A N7:10| 0 | |

| | | 0| | |

| | | | | |

| | +––––––––––––––––––+ | |

| | | |

| | ABOVE | |

| | RANGE FLAG | |

| | +GRT–––––––––––––––+ O:2.0 | |

| +–+GREATER THAN +–––––––––––––––––––––––––––––––––––––––––––––––––––––––––(L)–––––+ |

| | |Source A N7:10| 1 | |

| | | 0| | |

| | | | | |

| | +––––––––––––––––––+ | |

| | +LIM–––––––––––––––+ +SCL–––––––––––––––+ | |

| +–+LIMIT TEST +–+–––––––––––––––––––––––––––––––+SCALE +–+––––––––––+ |

| | | | | 0| | |

| | 0| | | | | |

| | | | | | | |

| +––––––––––––––––––+ | |Dest M0:1.210| | |

| | | *| | |

| | +––––––––––––––––––+ | |

| | BIT |BIT PENDING | |

| | M0:1.200 M1:1.200 B3:0 | |

| +––––]/[––––––––]/[–––––+––––(L)––––––––––––+––––––––+ |

| 15 13 | 1 | |

| | | |

| | BTW ENABLE | |

| | BIT | |

| | M0:1.200 | |

| +––––(L)––––––––––––+ |

| | 15 | |

| | | |

| | B3:0 | |

| |––––––––(U)––––––––| |

| 2 |

| |

Rung 2:10

| |

|––––––––––––––––––––––––––––––––––––––––––––––––+END+–––––––––––––––––––––––––––––––––––––––––––|

| |

Publication 17476.6 - July 1996

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

Scanner Operating

Specifications

Backplane Current Consumption

Operating Temperature

Storage Temperature

Humidity

Noise Immunity

Agency Certification

(when product or packaging is marked)

600 mA @ 5VDC

+32

F to 140

F (0

C to +60

F to 185

F (40

C to +85

5 to 95% without condensation

NEMA Standard ICS 2230

•

CSA certified

• CSA Class I, Division 2

Groups A, B, C, D certified

•

UL listed

•

CE marked for all applicable directives

Network Specifications

Using Extended

Node Capability

Not Using

Extended Node

Capability

Baud Rate

57.6K baud

115.2K baud

230.4K baud

57.6K baud

115.2K baud

230.4K baud

Maximum Cable Distance

(Belden 9463)

3048 meters (10,000 feet)

1524 meters (5,000 feet)

762 meters (2,500 feet)

3048 meters (10,000 feet)

1524 meters (5,000 feet)

762 meters (2,500 feet)

Resistor Size

82 W 1/2 Watt

150 W 1/2 Watt

Brown-Green-Brown-Gold

82 W 1/2 Watt

Gray-Red-Black-Gold

DIP Switch Position for Baud Rate Selection

Baud Rate

57.6K baud

115.2K baud

230.4K baud

1 ON

0 OFF

SW 1

1 ON

0 OFF

1 ON

0 OFF

SW 2

Publication 17476.6 - July 1996

A–2

Specifications

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

Scanner

Processor

Processor Scan

Scanner Scan

SLC Local Chassis

RIO Scan

Outputs to Modules

Inputs from Modules

ASB Module I/O Module

ASB Backplane Scan

I/O Module

Remote Chassis

Inputs to Modules

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 input 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.

Input Device

Publication 17476.6 - July 1996

Calculating Throughput

Specifications

A–3

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 dm–bt

) Present section to

determine your throughput. See page A–6.

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

T dm–nbt

= 2T ps

+ 2T

RIO

+ T adp

+ T

SNo

+ T

SNi

+ T id

+ T od

T dm–nbt

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

To calculate T dm–nbt

throughput, substitute values for the variables in the formula above. Locate these values in the following documents:

T ps

Variable

RIO

T adp

SNo

SNi

T id

T od

The total processor scan time

(ms)

Variable Description

The total RIO scan time (ms)

The adapter throughput delay.

For a 1747ASB, this is two

ASB backplane scan times.

The scanner module output delay time (ms)

The scanner module input delay time (ms)

The input module delay time

(ms)

The output module delay time

(ms)

Location of Variable

APS reference manual see the section RIO Scan Time

Calculation (T

A-4

RIO

) on page adapter user manual see the section RIO Scanner

Output Delay Time (T

page A-11

SNo

) on

5 ms (constant value for all formulas in this appendix)

I/O product data and I/O instruction sheets

Publication 17476.6 - July 1996

A–4

Specifications

Adapter

Size

1/4 logical rack

1/2 logical rack

3/4 logical rack

Full logical rack

RIO Scan Time Calculation (T

RIO

)

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)

RIO

= T adapter 1

+ T adapter 2

+ T adapter 3

RIO Scan Times for Adapters

Baud Rate

57.6K

115.2K

230.4K

6.0 ms

6.5 ms

7.5 ms

9.5 ms

3.5 ms

4.0 ms

4.5 ms

5.5 ms

2.5 ms

2.75 ms

3.0 ms

3.5 ms

Example Discrete I/O Throughput without Block Transfers Present

An SLC 5/03 is controlling an RIO link running at 115.2K baud that has the following adapters:

•

One 1747-ASB module module is configured as a 1/2 logical rack starting at logical rack 0.

I/O chassis slot 1 contains 1746-IB16, 16 point input module

I/O chassis slot 2 contains 1746-OB16, 16 point output module

•

Two adapters are each configured as full logical racks (logical racks 1 and 2).

•

Three adapters are each configured as 1/4 logical racks (logical rack 3).

Publication 17476.6 - July 1996

Specifications

A–5

You need to calculate your T dm–nbt

: the RIO throughput time from when the input closes on the 1746-IN16 until the output on the

1746-OB16 is on.

1. Use the throughput formula to calculate the maximum throughput.

T dm–nbt

= 2T ps

+ 2T

RIO

+ T adp

+ T

SNo

+ T

SNi

+ T id

+ T od

T ps

= 25.0 ms, which is from the APS reference manual (assume for example)

RIO

= The total RIO scan time (ms)

SNo

= See value in the table on page A–13, T

SNo

without M0 File

Writes

(Normal Mode).

SNi

= 5.0 ms

T id

= 10.0 ms, which is from I/O module instruction sheets

T od

= 1.0 ms, which is from I/O module instruction sheets

T dm–nbt

= 2(25.0) + 2T

RIO

+ 8.0 + T

SNo

+ 5.0 + 10.0 + 1.0

2. Calculate the total RIO scan time (T

RIO

). Locate the baud rate

(115.2K) and adapter size, which is found in the table on page

A–4. Multiply the RIO scan times listed under the 115.2K

heading by the number of each different type of rack that you have. Add those numbers together:

RIO

= T adapter 1

+ T adapter 2

+ T adapter 3

RIO

= 1(4.0 ms) + 2(5.5 ms) + 3(3.5 ms)

RIO

= 25.5 ms

3. Find T

SNo

on page A–13 in the table T

SNo

without M0 File

Writes (Normal Mode). For this example T upd

> T hold

, and there are 4 logical racks configured. Therefore:

SNo

= 7.0 ms

4. Substitute all the values for variables in the throughput formula and solve for throughput:

T dm–nbt

= 2T ps

+ 2T

RIO

+ 2T bp

+ T

SNo

+ T

SNi

+ T id

+ T od

T dm–nbt

= 2(25.0)+ 2(25.5) + 8.0 + 7.0 + 5.0 + 10.0 + 1.0

T dm–nbt

= 132.0 ms = maximum throughput

Publication 17476.6 - July 1996

A–6

Specifications

Discrete I/O Throughput with Block Transfers (T

dm-bt

) Present

The information in this section is used to calculate the discrete throughput of the 1747-SN Scanner if there are BTs occurring on the

RIO link to any chassis.

If BTs are not present on the RIO link, you must use the Discrete I/O

Throughput without Block Transfers (T dm–nbt

) Present section to

determine your throughput. See page A–3.

The formula to calculate discrete I/O throughput with BTs present is:

T dm–bt

= 2T ps

+ 2T

RIO

+ 2T btx

+ T adp

+ T

SNo–bt

+ T

SNi

+ T id

+ T od

T dm–bt

= The maximum discrete throughput with BTs in milliseconds

(ms)

To calculate T dm–bt

throughput, substitute values for the variables in the formula above. Locate these values in the following documents:

T ps

Variable

RIO

T btx

T adp

SNo–bt

SNi

T id

T od

The total processor scan time

(ms)

Variable Description

The total RIO scan time (ms)

Location of Variable

APS reference manual see the section RIO Scan Time

Calculation (T

A-4

RIO

) on page see the section Determining

T btx

on page A-7

Additional time due to sending any BT data on the RIO link.

The adapter throughput delay.

For a 1747ASB, this is two

ASB backplane scan times.

Scanner output delay time with

BTs present

The scanner module input delay time (ms)

The input module delay time

(ms)

The output module delay time

(ms) adapter user manual see the section Determining

SNo-bt

on page A-7

5 ms (constant value for all formulas in this appendix)

I/O product data and I/O instruction sheets

Publication 17476.6 - July 1996

Specifications

A–7

Determining T

SNo-bt

Use the following table to find T

SNo–bt for your particular configuration.

Important:

The times shown are, to the best of our knowledge, the maximum delay times of the scanner. However, in instances that throughput is an important consideration, test the application thoroughly first to ensure proper operation. Note that in most situations the average throughput is much better than the calculated maximum throughput.

Number of Logical

Racks

Configured

➀

1 Logical Rack

2 Logical Racks

3 Logical Racks

4 Logical Racks

Normal Mode

All Baud Rates

16.0

19.0

22.0

25.0

Complementary Mode

57.6K baud 115.2K baud 230.4K baud

19.0

24.0

32.0

23.0

26.0

28.0

27.0

30.0

34.0

36.0

39.0

42.0

➀

See page A-12 if you are not sure how to determine the number of logical racks configured.

Determining T btx

Before determining (T btx

), you need to establish the maximum BT write or read length that is to be processed by each logical rack on the RIO link. RIO scan time is increased each time an BT is sent to any logical device on the RIO network. The scan time increase depends on the number of words sent in the BT and the selected baud rate.

RIO link protocol allows for a maximum of one BT to be sent to each logical rack on the RIO link during any single RIO scan.

Therefore, if multiple BTs are sent to devices within the same logical rack, only the longest BT to that logical rack needs to be considered to determine your maximum throughput. The RIO scan time increase (T ri

) for each logical rack is:

Baud Rate

57.6K baud

115.2K baud

230.4K baud

RIO Scan Time Increase (T ri

0.300 x BT length + 5.0 ms

)

0.150 x BT length + 3.5 ms

0.075 x BT length + 2.0 ms

The total increase in the RIO scan time (T btx

) is equal to:

T btx

= sum of T ri

for all logical racks

Publication 17476.6 - July 1996

A–8

Specifications

Example Discrete I/O Throughput with Block Transfers Present

An SLC 5/03 is using a scanner to control a 115.2K baud RIO link that has 3 adapters and 4 logical devices.

Adapter #1 (1747-ASB module):

• starting logical rack 0, logical group 0

•

12 logical groups (1 1/2 logical racks)

• one 8 word and two 4 word BT write/read modules in logical rack 0

• one 2 word BT write/read module in logical rack 1

Adapter #2 (1771-ASB module):

• starting logical rack 2, logical group 0

•

2 logical groups (1/4 logical rack)

• one 64 word BT write/read module

Adapter #3 (1771-ASB module):

• starting logical rack 2, logical group 2

•

2 logical groups (1/4 logical rack)

• one 32 word BT write/read module

1. Use the throughput formula to calculate the maximum throughput of the 1747-ASB module.

T dm–bt

= 2T ps

+ 2T

RIO

+ 2T btx

+ T adp

+ T

SNo–bt

+ T

SNi

+ T id

+ T od

T ps

= 25.0 ms, which is from the APS reference manual (assume for example)

RIO

= The total RIO scan time (ms)

T btx

= Additional time due to sending any BT data on the RIO link

T adp

= Two 1747-ASB module backplane scan times (calculated from

ASB

manual) = 2(4.5) = 9.0 ms

SNo–bt

= 22.0 ms from the table on page A–13, T

SNo

with Block

Transfers

(Normal Mode). There are 3 logical racks configured.

SNi

= 5.0 ms

T id

= 10.0 ms, which is from I/O module instruction sheets

T od

= 1.0 ms, which is from I/O module instruction sheets

T dm–bt

= 2(25.0) + 2T

RIO

+ 2T btx

+ 9.0 + 22.0 + 5.0 + 10.0 + 1.0

Publication 17476.6 - July 1996

Specifications

A–9

2. Calculate the total RIO scan time (T

RIO

). Locate the baud rate

(115.2K) and adapter size which is found in the table on page

A–4. Multiply the RIO scan times listed under the 115.2K

heading by the number of each different type of rack that you have. Add those number together.

RIO

= Tadapter1 + Tadapter2 + Tadapter3

RIO

= 1(5.5) + 1(4.0) + 2(3.5)

RIO

= 16.5 ms

3. Calculate the maximum T ri

time for each logical rack. Do this by determining the largest BT that will occur to any device within a logical rack and calculating the transfer time using the table on

page A–7. Then add together the T

times for each logical rack to obtain T btx

T ri

for rack 0 = 0.150(8) + 3.5 = 4.7 ms (maximum BT to rack 0 is 8 words)

T ri

for rack 1 = 0.150(2) + 3.5 = 3.8 ms (maximum BT to rack 1 is 2 words)

T ri

for rack 2 = 0.150(64) + 3.5 = 13.1 ms (maximum BT to rack 2 is 64 words)

T btx

= T ri0

+ T ri1

+ T ri2

= 4.7 + 3.8 + 13.1 = 21.6 ms

4. Substitute all the values for variables in the throughput formula and solve for throughput.

T dm–bt

= 2(25.0) + 2(16.5) + 2(21.6) + 9.0 + 22.0 + 5.0 + 10.0 + 1.0

T dm–bt

= 173.2 ms = maximum throughput

Publication 17476.6 - July 1996

A–10

Specifications

Block Transfer Throughput

Block transfer throughput is the time from when the BT is enabled via the EN bit, until the DN bit is processed. The following BT timing explanations are based on the directional continuous BT

example shown on page 5–29, where a BT is re–triggered

automatically upon each completion.

BT throughput is always slower than discrete data transfer.

Completing a BT is dependent on the time involved for the:

•

SLC control program to enable the BT via an M0 file write

➀

• scanner to detect that a BT has been requested

➁

•

BT to be waiting in the queue due to another BT already being processed on the same logical rack

➂

• scanner to schedule a pending bit

➁

• adapter to acknowledge the request

➃

• scanner to initiate the BT and transfer the data

➁

•

SLC control program to detect that the BT has completed (DN flag set)

➀

The time to free up the BT buffer (by clearing the EN flag so another

BT can be performed) depends on the:

• instruction time of the M0 file write which clears the EN flag

➀

• time for the scanner to detect that the EN flag has been cleared

➁

• time for SLC control program to detect that the DN flag has been cleared

➀

➁

➂

➃

This is dependent on the SLC processor you are using.

Refer to the equations that follow.

The RIO network allows only one BT per logical rack (not logical device) per RIO scan. Therefore, if multiple BTs are performed on devices within the same logical rack, BTs will have to wait in the queue until any previously scheduled BTs for the same logical rack have been completed.

This is dependent on the RIO adapter.

The formula to calculate BT throughput is:

+ T

SNo–bt

(number of BTs + 1) + T btwait

+ 2T

RIO

+ 2T btx +

T adp–bt

+ T ps

The equation for freeing up the BT buffer is:

+ T

SNo–bt

(number of BTs) + T ps

Substitute values for the variables in the formulas above. Locate these values in the following documents:

Publication 17476.6 - July 1996

Specifications

A–11

Variable

SNo–bt btwait

Variable Description

Time to perform M0 file write to enable

Scanner Output Delay time with BTs present. There must be an output delay time added for each BT buffer that is being used since the scanner processes only one BT enable or disable every

SNo-bt

(to minimize the impact on discrete I/O throughput).

➀

Equals the sum of the throughput times for all BTs scheduled to the same logical rack (time waiting is queue), + T

SNo-bt

(time to schedule pending BT). If multiple BTs are not being performed to the same logical rack, this value equals zero.

Location of Variable

appendix B

see the section Determining

SNo-bt

on page A-7

calculated

RIO

RIO scan time without BTs see the section RIO Scan

Time Calculation (T

page A-4

RIO

) on

T btx adp–bt ps

Amount that the RIO scan time can be increased due to BTs. This includes the time for the scanner to initiate the BT and transfer the data.

Time for the adapter to acknowledge the

BT request. For the 1747ASB, the manual defines this as no more than one

(ASB) backplane scan time and two RIO scans. However, the two RIO scans are already included in the above equation so only the ASB scan time needs to be added.

One processor scan time may occur before the SLC control program detects that the DN flag has been set or cleared see the section Determining

T btx

on page A-7

adapter user manual

APS reference manual

➀

When calculating BT throughput, one T

SNo-bt

is also required to handle the BT response.

RIO Scanner Output Delay Time (T

SNo

) Tables

The tables provided in this section show the maximum scanner output delay time (T

SNo

) for specific applications. T

SNo

is dependent on the following:

• processor scan time, or time between immediate outputs (if no

BTs are present)

• number of logical racks configured

• whether normal or complementary I/O mode is selected

•

RIO baud rate (if complementary I/O is selected)

Publication 17476.6 - July 1996

A–12

Specifications

The following variables are used in the T

SNo

tables on page A–13:

SNo

Variable

T upd

T hold

Variable Description

The maximum scanner output delay time

The time between SLC processor output scan updates or immediate output updates

A constant time threshold that is dependent on your configuration. Refer to the

tables on page A-13.

SNo

increases if the interval between T upd

decreases to the time threshold (T hold

). If T upd

is less than T hold

, then the larger T

SNo number must be used. Otherwise, either number may be used.

Important:

The times shown in this section are, to the best of our knowledge, the maximum delay times of the scanner.

However, in instances that throughput is an important consideration, test the application thoroughly first to ensure proper operation. Note that in most situations the average throughput is much better than the calculated maximum throughput.

Determining the Number of Logical Racks Configured

The number of logical racks configured is determined by the number of racks that contain configured devices. For example, if there are four 1/4 rack devices in logical rack 0 and one full rack device in logical rack 3, there would be two logical racks configured. Note that the number of logical devices on the RIO network affects only

RIO

, and only affects T

SNo

when additional logical racks are used.

When complementary mode is selected, the number of configured racks is also determined by the number of primary or complementary racks configured, but not by both. (The maximum number of configured racks is 4.) That is, if there is a primary rack configured with a corresponding complementary rack, that is considered one logical rack. If there is a primary rack configured without a complementary rack (or vice versa), that also is considered one logical rack.

Publication 17476.6 - July 1996

Specifications

A–13

SNo

without M0 File Writes

Number of Logical

Racks Configured

1 Logical Rack

2 Logical Racks

3 Logical Racks

4 Logical Racks

Normal Mode

➀

All Baud Rates

SNo

T upd

T hold

5.0

7.0

9.0

11.0

T hold

5.0

7.0

9.0

11.0

4.0

5.5

7.0

SNo

if T upd

T hold

2.5

Number of Logical

Racks Configured

1 Logical Rack

2 Logical Racks

3 Logical Racks

4 Logical Racks

57.6K baud

SNo

T upd

T hold

6.0

9.0

12.0

15.0

T hold

5.0

8.0

5.0

11.0

7.0

SNo

if T upd

T hold

4.0

14.0

9.0

Complementary Mode

➀➁

115.2K baud

SNo

T upd

T hold

7.0

10.0

12.0

16.0

T hold

7.0

SNo

if T upd

T hold

4.0

10.0

6.0

12.0

8.0

16.0

10.0

230.4K baud

SNo

T upd

T hold

10.0

12.0

16.0

21.0

T hold

9.0

SNo

if T upd

T hold

4.0

12.0

7.0

16.0

10.0

22.0

13.0

SNo

with M0 File Writes (No Block Transfers)

Number of Logical

Racks Configured

1 Logical Rack

2 Logical Racks

3 Logical Racks

4 Logical Racks

Normal Mode

➀

All Baud Rates

SNo

T upd

T hold

8.0

10.0

12.0

14.0

T hold

6.0

8.0

10.0

12.0

5.5

7.0

8.0

SNo

if T upd

T hold

4.5

Number of Logical

Racks Configured

1 Logical Rack

2 Logical Racks

3 Logical Racks

4 Logical Racks

57.6K baud

SNo

T upd

T hold

10.0

12.0

15.0

18.0

T hold

6.0

9.0

12.0

9.0

15.0

10.0

SNo

if T upd

T hold

6.0

8.0

Complementary Mode

➀➁

115.2K baud

SNo

T upd

T hold

12.0

14.0

T hold

8.0

SNo

if T upd

T hold

8.0

11.0

9.0

16.0

20.0

14.0

11.0

17.0

12.0

230.4K baud

SNo

T upd

T hold

15.0

17.0

21.0

26.0

T hold

SNo

if T upd

T hold

10.0

9.0

15.0

12.0

20.0

14.0

24.0

17.0

➀

All times shown are in milliseconds (ms).

➁

Although a faster baud rate decreases RIO scan time (T

RIO when complementary I/O mode is selected.

), it has an inverse affect on T

SNo

Publication 17476.6 - July 1996

M0-M1 Files

Appendix

M0-M1 Files and G Files

This appendix contains important information about M0–M1 files and G files. The information is general in nature and supplements specific information contained in earlier chapters of this manual.

Topics include:

•

M0–M1 Files

•

G Files

M0 and M1 files are data files that reside in specialty I/O modules only. There is no image for these files in the processor memory. The application of these files depends on the function of the particular specialty I/O module. With respect to the SLC processor (SLC 5/02 or later), the M0 file is a module output file (a write only file) and the M1 file is a module input file (a read only file). The opposite is true for specialty I/O modules, where the M0 file is a read only file, and the M1 file is a write only file.

M0 and M1 files can be addressed in your ladder program and they can also be acted upon by the specialty I/O module – independent of the processor scan. It is important that you keep the following in mind in creating and applying your ladder logic:

Important:

During the processor scan, the ladder program can address M0 and M1 data with bit, word, or file instructions. Each time an M0–M1 file address is encountered in the program, an immediate data transfer to or from the specialty I/O module occurs. The impact these immediate data transfers have on processor scan time is described in appendix D of the

SLC 500

and MicroLogix

1000 Instruction Set

Reference Manual, Publication 1747-6.15.

READ

CONFIG

ONLINE

CONFIG

Configuring M0-M1 Files Using APS Software

M0 and M1 files are configured as part of the I/O configuration procedure for the processor file. After you have assigned the specialty I/O module to a slot (the procedure is the same as assigning other modules), the following functions appear at the bottom of the

APS screen:

MODIFY

RACKS

MODIFY

SLOT

DELETE

SLOT

UNDEL

SLOT

EXIT

SPIO

CONFIG

Publication 17476.6 - July 1996

B–2

M0–M1 Files and G Files

Complete the following steps to configure the M0 and M1 files:

1. Press

[F9]

, Specialty I/O Configuration. The following functions appear:

ISR

NUMBER

MODIFY

G FILE

ADVNCD

SETUP

G FILE

SIZE

2. Press

[F5]

, Advanced Setup. The following functions appear:

INPUT

SIZE

OUTPUT

SIZE

SCANNED

INPUT

SCANNED

OUTPUT

M0 FILE

SIZE

M1 FILE

SIZE

3. Press

[F5]

, then enter the number of M0 file words required (the required number is listed in the user manual for the specific specialty I/O module).

4. Press

[F6]

, then enter the number of M1 file words required (the required number is listed in the user manual for the specific specialty I/O module).

The specialty I/O module may require that you also configure the G file and specify an ISR (interrupt subroutine) number. These tasks are accomplished with function keys F1, F3, and F7 shown in step 1 above. G files are discussed later in this appendix.

Addressing M0-M1 Files

The addressing format for M0 and M1 files is below:

Mf:e.s/b

Where M = module f = file type (0 or 1) e = slot (130) s = word (0 to max. supplied by module) b = bit (015)

Restrictions on Using M0M1 Data File Addresses

M0 and M1 data file addresses can be used in all instructions except the OSR instruction and the instruction parameters noted below:

Instruction

BSL, BSR

SQO, SQC, SQL

LFL, LFU

FFL, FFU

Parameter (uses file indicator #)

File (bit array)

File (sequencer file)

LIFO (stack)

FIFO (stack)

Publication 17476.6 - July 1996

M0–M1 Files and G Files

B–3

Monitoring Bit Addresses

For SLC 5/02 processors, the M0/M1 Monitoring option is always disabled. (This processor does not allow you to monitor the actual state of each addressed M0/M1 address.) For SLC 5/03 and SLC

5/04 processors, you can choose to disable or enable the monitoring option by selecting

[F6]

, System Config, from the APS main menu.

M0/M1 Monitoring Option Disabled

When you monitor a ladder program in the Run or Test mode with the M0/M1 Monitoring option disabled, the following bit instructions, addressed to an M0 or M1 file, are indicated as false regardless of their actual true/false logical state.

Mf:e.s

] [

Mf:e.s

]/[

Mf:e.s

( )

Mf:e.s

(L)

Mf:e.s

(U)

b f = file (0 or 1)

When you are monitoring the ladder program in the Run or Test mode, the

APS or HHT display does not show these instructions as being true when the processor evaluates them as true.

If you need to show the state of the M0 or M1 addressed bit, you can transfer the state to an internal processor bit. This is illustrated below, where an internal processor bit is used to indicate the true/false state of a rung.

] [

EQU

EQUAL

Source A

Source B

N7:12

N7:3

M0:3.0

( )

This rung will not show its true rung state because the EQU instruction is always shown as true and the M0 instruction is always shown as false.

] [

EQU

EQUAL

Source A

Source B

N7:12

N7:3

( )

M0:3.0

( )

OTE instruction B3/2 has been added to the rung. This instruction shows the true or false state of the rung.

Publication 17476.6 - July 1996

B–4

M0–M1 Files and G Files

M0/M1 Monitoring Option Enabled

Important:

This option is not supported by the SLC 5/02 processor.

The SLC 5/03 and SLC 5/04 processors allows you to monitor the actual state of each addressed M0/M1 address (or data table). The highlighting appears normal when compared to the other processor data files. The processor’s performance will be degraded to the degree of M0/M1 referenced screen data. For example, if your screen has only one M0/M1 element, degradation will be minimal.

If your screen has 69 M0/M1 elements, degradation will be significant.

Transferring Data Between Processor Files and M0 or M1 Files

The processor does not contain an image of the M0 or M1 file. As a result, you must edit and monitor M0 and M1 file data via instructions in your ladder program. For example, you can copy a block of data from a processor data file to an M0 or M1 data file or vice versa using the COP instruction in your ladder program.

The COP instructions below copy data from a processor bit file and integer file to an M0 file. For the example, assume the data is configuration information affecting the operation of the specialty I/O module.

First scan bit. It makes this rung true only for the first scan after entering Run mode.

S:1

] [

COP

COPY FILE

Source

Dest

Length

#B3:0

#M0:1.0

COP

COPY FILE

Source

Dest

Length

#N7:0

#M0:1.16

The COP instruction below copies data from an M1 data file to an integer file. This technique is used to monitor the contents of an M0 or M1 data file indirectly, in a processor data file.

COP

COPY FILE

Source

Dest

Length

#M1:4.3

#N10:0

Publication 17476.6 - July 1996

M0–M1 Files and G Files

B–5

Access Time

During the program scan, the processor must access the specialty I/O card to read/write M0 or M1 data. This access time must be added to the execution time of each instruction referencing M0 or M1 data.

For the SLC 5/03 and SLC 5/04 processors, the instruction types vary in their execution times.

The following table shows approximate access times per instruction or word of data for the SLC 5/02, SLC 5/03, and SLC 5/04 processors.

Processor

SLC 5/02 Series B All types

➀

Instruction Type

SLC 5/02 Series C All types

➀

XIC or XIO

OTU, OTE, or OTL

SLC 5/03 (All

Series)

COP to M file

COP from M file

FLL

MVM to M file any source or Destination M file address

XIC or XIO

OTU, OTE, or OTL

COP to M file

COP from M file

FLL

MVM to M file any source or Destination M file address

Access Time per Bit

Instruction or Word of Data

1930

1160

782

925

894

730

743

µ s

879

µ s

850

694

µ s s s s s s s s

Access Time per

MultiWord Instruction

1580 µ s plus 670 µ s per word

950

µ s plus 400

µ s per word

772

µ s plus 23

µ s per word

760

µ s plus 22

µ s per word

753

µ s plus 30

µ s per word

735

µ s plus 23

µ s per word

722

µ s plus 22

µ s per word

716

µ s plus 30

µ s per word

➀

Except the OSR instruction and the instruction parameters noted on page B-2.

SLC 5/02 Processor Example

M0:2.1

] [

M1:3.1

]/[

M0:2.1

( )

Publication 17476.6 - July 1996

B–6

M0–M1 Files and G Files

If you are using a SLC 5/02 Series B processor, add 1930

µ s to the program scan time for each bit instruction addressed to an M0 or M1 data file. If you are using a SLC 5/03 Series C processor, add 1160

µ s.

COP

COPY FILE

Source

Dest

Length

#B3:0

#M0:1.0

If you are using a SLC 5/02 Series B processor, add 1580

µ s plus

670

µ s per word of data addressed to the M0 or M1 file. As shown above, 34 words are copied from #B3:0 to M0:1.0. Therefore, this adds 24360

µ s to the scan time of the COP instruction. If you are using a SLC 5/02 Series C processor, add 950

µ s plus 400

µ s per word. This adds 14550

µ s to the scan time of the COP instruction.

SLC 5/03 Processor Example

COP

COPY FILE

Source

Dest

Length

#B3:0

#M0:1.0

The SLC 5/03 processor access times depend on the instruction type.

Consult the table on B–5 for the correct access times to add. As an

example, if you use a COP to M file instruction like the one shown above, add 772

µ s plus 23

µ s per word. This adds 1554

µ s to the

SLC 5/03 processor scan time due to the COP instruction.

SLC 5/04 Processor Example

COP

COPY FILE

Source

Dest

Length

#B3:0

#M0:1.0

The SLC 5/04 processor access times depend on the instruction type.

Consult the table on B–5 for the correct access times to add. As an

example, if you use a COP to M file instruction like the one shown above, add 735

µ s plus 23

µ s per word. This adds 1517

µ s to the

SLC 5/04 processor scan time due to the COP instruction.

Publication 17476.6 - July 1996

M0–M1 Files and G Files

B–7

Minimizing the Scan Time

You can keep the processor scan time to a minimum by economizing on the use of instructions addressing the M0 or M1 files. For example, XIC instruction M0:2.1/1 is used in rungs 1 and 2 of the figure below, adding approximately 2 ms to the scan time if you are using a SLC 5/02 Series B processor.

M0:2.1

] [

M0:2.1

] [

( )

XIC instructions in rungs 1 and 2 are addressed to the M0 data file. Each of these instructions adds approximately 1 ms to the scan time (SLC 5/02

Series B processor).

In the equivalent rungs of the figure below, XIC instruction M0:2.1/1 is used only in rung 1, reducing the SLC 5/02 scan time by approximately 1 ms.

M0:2.1

] [

( )

These rungs provide equivalent operation to those of figure A by substituting

XIC instruction B3/10 for XIC instruction M0:2.1/1 in rung 2. Scan time is reduced by approximately 1 ms (Series B processor).

The following figure illustrates another economizing technique. The

COP instruction addresses an M1 file, adding approximately 4.29 ms to the scan time if you are using a SLC 5/02 Series B processor.

Scan time economy is realized by making this rung true only periodically, as determined by clock bit S:4/8. (Clock bits are

discussed in appendix B of the SLC 500

and MicroLogix

1000

Instruction Set Reference Manual, Publication 1747-6.15.) A rung such as this might be used when you want to monitor the contents of the M1 file, but monitoring need not be on a continuous basis.

S:4/8 causes the

#M1:4.3 file to update the #N10:0 file every

2.56 seconds.

S:4

] [

B11

[OSR]

COP

COPY FILE

Source

Dest

Length

#M1:4.3

#N10:0

Publication 17476.6 - July 1996

B–8

M0–M1 Files and G Files

Capturing M0-M1 File Data

The first two ladder diagrams in the last section illustrate a technique allowing you to capture and use M0 or M1 data as it exists at a particular time. In the first figure, bit M0:2.1/1 could change state between rungs 1 and 2. This could interfere with the logic applied in rung 2. The second figure avoids the problem. If rung 1 is true, bit

B3/10 captures this information and places it in rung 2.

In the second example of the last section, a COP instruction is used to monitor the contents of an M1 file. When the instruction goes true, the 6 words of data in file #M1:4.3 is captured as it exists at that time and placed in file #N10.0.

Specialty I/O Modules with Retentive Memory

Certain specialty I/O modules retain the status of M0-M1 data after power is removed. See your specialty I/O module user’s manual.

This means that an OTE instruction having an M0 or M1 address remains on if it is on when power is removed. A “hold-in” rung as shown below will not function as it would if the OTE instruction were non-retentive on power loss. If the rung is true at the time power is removed, the OTE instruction latches instead of dropping out; when power is again applied, the rung will be evaluated as true instead of false.

] [

M0:2.1

] [

M0:2.1

( )

ATTENTION: When used with a speciality I/O module having retentive outputs, this rung can cause unexpected start-up on powerup.

You can achieve non-retentive operation by unlatching the retentive output with the first pass bit at powerup:

S:1

] [

M0:2.1

(U)

This rung is true for the first scan after powerup to unlatch M0:2.1/1.

] [

M0:2.1

( )

M0:2.1

] [

Publication 17476.6 - July 1996

G Files

M0–M1 Files and G Files

B–9

Some specialty I/O modules use G (confiGuration) files (indicated in the specific specialty I/O module user’s manual). These files can be thought of as the software equivalent of DIP switches.

The content of G files is accessed and edited offline under the I/O

Configuration function. You cannot access G files under the Monitor

File function. Data you enter into the G file is passed on to the specialty I/O module when you download the processor file and enter the REM Run or any one of the REM Test modes.

READ

CONFIG

ONLINE

CONFIG

Configuring G Files Using APS Software

The G file is configured as part of the I/O configuration procedure for the processor file. After you have assigned the specialty I/O module to a slot (the procedure is the same as assigning other modules except that you must specify the ID code of the specialty

I/O module), the following functions appear at the bottom of the

APS screen:

MODIFY

RACKS

MODIFY

SLOT

DELETE

SLOT

UNDEL

SLOT

EXIT

SPIO

CONFIG

This is the starting point for configuring the G file and other parameters of the specialty I/O module. Complete the following steps to create and monitor the G file:

1. Press

[F9]

, Specialty I/O Configuration. A screen similar to the following is displayed:

I/O CONFIGURATION FOR:EXAMPLE

RACK 1

RACK 2

RACK 3

SLOT

1746-A4 4-SLOT Backplane

SPECIAL CONFIG FOR SLOT:

Module’s ID Code:

Maximum Input Words:

Maximum Output Words:

Scanned Input Words:

Scanned Output Words:

M0 Length:

M1 Length:

‘G’ File Size:

ISR Number:

ESC exits

Press a function key

ISR

NUMBER

MODIFY

G FILE

ADVNCD

SETUP

12705

G FILE

SIZE

2. Press

[F7]

, G File Size, then specify the number of words required for the specialty I/O module.

Publication 17476.6 - July 1996

B–10

M0–M1 Files and G Files

3. Press

[F3]

, Modify G File. The content of the G file appears in the display area. Data is shown in the default form, decimal: address 0 1 2 3 4 5 6 7 8 9

G1:0 xxxx 0 0 0 0 0 0 0 0 0

G1:10 0 0 0 0 0 0

The function keys appearing below the data table indicate the three data formats available to you – binary data, decimal data, and hex/bcd data:

BINARY

DATA

DECIMAL

DATA

HEX/BCD

DATA

The following figure illustrates the three G file data formats that you can select. Word addresses begin with the file identifier G and the slot number you have assigned to the specialty I/O module. In this case, the slot number is 1. Sixteen words have been created

(addresses G1:0 through G1:15).

16word G file, I/O slot 1, decimal format

address 0 1 2 3 4 5 6 7 8 9

G1:0 xxxx 0 0 0 0 0 0 0 0 0

G1:10 0 0 0 0 0 0

16word G file, I/O slot 1, hex/bcd format

address 0 1 2 3 4 5 6 7 8 9

G1:0 xxxx 0000 0000 0000 0000 0000 0000 0000 0000 0000

G1:10 0000 0000 0000 0000 0000 0000

16word G file, I/O slot 1, binary format

address 15 data 0

G1:0 xxxx xxxx xxxx xxxx

G1:1 0000 0000 0000 0000

G1:2 0000 0000 0000 0000

G1:3 0000 0000 0000 0000

G1:4 0000 0000 0000 0000

G1:5 0000 0000 0000 0000

G1:6 0000 0000 0000 0000

G1:7 0000 0000 0000 0000

G1:8 0000 0000 0000 0000

G1:9 0000 0000 0000 0000

G1:10 0000 0000 0000 0000

G1:11 0000 0000 0000 0000

G1:12 0000 0000 0000 0000

G1:13 0000 0000 0000 0000

G1:14 0000 0000 0000 0000

G1:15 0000 0000 0000 0000

Publication 17476.6 - July 1996

M0–M1 Files and G Files

B–11

Editing G File Data

Data in the G file must be edited according to your application and the requirements of the specialty I/O module. You edit the data offline under the I/O configuration function only. With the decimal and hex/bcd formats, you edit data at the word level:

•

G1:1 = 234 (decimal format)

G1:1 = 00EA (hex/bcd format)

With the binary format, you edit data at the bit level:

•

G1/19 = 1

Important:

Word 0 of the G file is configured automatically by the processor according to the particular specialty I/O module. Word 0 cannot be edited.

Publication 17476.6 - July 1996

Appendix

RIO Configuration Worksheet

This appendix provides a worksheet to help you configure your RIO devices.

Directions

We recommend that you use a photocopy of the worksheet so you retain a blank worksheet for future applications.

SLC Processor Input Image

High Byte Low Byte

Bit Number

−

Decimal

15 8 7 0

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

I:e.0

I:e.1

I:e.2

I:e.3

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

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

Group 5

Group 6

I:e.13

I:e.14

Group 7

Group 1

I:e.15

Group 0

ÉÉÉÉÉ ÉÉÉÉÉ

I:e.16

I:e.17

Group 2

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

I:e.18

Group 3

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

I:e.19

Group 4 I:e.20

Group 5

ÉÉÉÉÉ ÉÉÉÉÉ

I:e.21

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

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

e = 1747SN Slot Number

SLC Processor Output Image

High Byte Low Byte

Bit Number

−

Decimal

15 8 7 0

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

O:e.0

O:e.1

O:e.2

O:e.3

O:e.4

O:e.5

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

O:e.6

O:e.7

O:e.8

O:e.9

O:e.10

O:e.11

Group 4

Group 5

O:e.12

O:e.13

Group 6

Group 7

O:e.14

O:e.15

Group 0

ÉÉÉÉÉ ÉÉÉÉÉ

O:e.16

Group 1

O:e.17

Group 2

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

O:e.18

Group 3

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

O:e.19

Group 4

O:e.20

Group 5

ÉÉÉÉÉ ÉÉÉÉÉ

O:e.21

Group 6

Group 7

Group 0

Group 1

O:e.22

O:e.23

O:e.24

O:e.25

Group 2

Group 3

Group 4

Group 5

O:e.26

O:e.27

O:e.28

Group 6

Group 7

O:e.29

O:e.30

O:e.31

Publication 17476.6 - July 1996

C–2

RIO Configuration Worksheet

SLC Processor Input Image

High Byte Low Byte

Bit Number

−

Decimal

15 8 7 0

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

I:e.0

I:e.1

I:e.2

I:e.3

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

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

Group 5

Group 6

I:e.13

I:e.14

Group 7 I:e.15

Group 0

ÉÉÉÉÉ ÉÉÉÉÉ

I:e.16

Group 1

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

I:e.17

Group 2 I:e.18

Group 3

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

I:e.19

Group 4

ÉÉÉÉÉ ÉÉÉÉÉ

I:e.20

Group 5 I:e.21

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

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

e = 1747SN Slot Number

SLC Processor Output Image

High Byte Low Byte

Bit Number

−

Decimal

15 8 7 0

Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

Group 0

Group 1

Group 2

Group 3

Group 4

Group 5

Group 6

Group 7

Group 0

Group 1

Group 2

Group 3

O:e.0

O:e.1

O:e.2

O:e.3

O:e.4

O:e.5

O:e.6

O:e.7

O:e.8

O:e.9

O:e.10

O:e.11

Group 4

Group 5

Group 6

O:e.12

O:e.13

O:e.14

Group 7 O:e.15

Group 0

ÉÉÉÉÉ ÉÉÉÉÉ

O:e.16

Group 1 O:e.17

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

Group 2 O:e.18

Group 3

ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ ÉÉÉÉÉ

O:e.19

Group 4 O:e.20

ÉÉÉÉÉ ÉÉÉÉÉ

Group 5

Group 6

Group 7

O:e.21

O:e.22

Group 0

Group 1

Group 2

O:e.23

O:e.24

O:e.25

O:e.26

Group 3

Group 4

Group 5

Group 6

Group 7

O:e.27

O:e.28

O:e.29

O:e.30

O:e.31

Publication 17476.6 - July 1996

Glossary

The following terms are used throughout this manual. Refer to the

Allen-Bradley Industrial Automation Glossary, Publication Number

AG-7.1, for a complete guide to Allen-Bradley technical terms.

Adapter



Any physical device that is a slave on the RIO link.

Adapter Image



That portion of the scanner image assigned to an individual adapter.

ASB Module



The Catalog Number 1747-ASB, 1771-ASB, or

1794 - ASB Remote I/O Adapter Module. The ASB module is an adapter.

ASB Module Chassis



The chassis directly controlled by the ASB module. This includes the remote chassis and (if installed) two remote expansion chassis when using the 1747-ASB.

Block Transfer (BT)



See RIO Block Transfer.

Block Transfer Read (BTR)



A form of block transfer that occurs when a remote device transfers data to the SLC processor.

Block Transfer Write (BTW)



A form of block transfer that occurs when the SLC processor transfers data to a remote device.

Complementary I/O



Functionality that allows you to maximize

I/O usage by pairing up I/O data from a primary and complementary chassis.

Discrete I/O



An input or output device that has corresponding bit locations in the scanner’s input or output file.

Discrete I/O Module



An I/O module used to sense or control two-state (ON/OFF) devices.

Extended Node Capability



Functionality that allows you to use an 82 Ohm termination resistor at both ends of the RIO link for all baud rates. This functionality also allows for up to 32 adapters to be connected to the RIO link.

G file



The SLC file used to configure the scanner. You enter configuration information into this file during SLC processor programming. This file is loaded to the scanner by the SLC processor upon entering run mode.

Publication 17476.6 - July 1996

G–2

Glossary

Publication 17476.6 - July 1996

Inhibit



A function by which the scanner stops communicating with a logical device. The logical device will consider itself inhibited if it does not receive communications from the scanner within a certain period of time.

Input file



The scanner’s input image file that is updated during the SLC processor input scan.

Local Expansion Chassis



A chassis that is connected to a local

SLC chassis using a 1747-C9 (91.4 cm [36 in.]) or 1747-C7 (15.2 cm

[6 in.]) cable.

Local SLC Chassis



The chassis that contains the SLC processor and scanner.

Logical Device



Any portion of a logical rack that is assigned to a single adapter. Adapters may appear as more than one logical device.

Logical Group



A logical group consists of one input and one output word within a logical rack. A word consists of 16 bits, each bit represents one terminal on a discrete I/O module.

Logical Rack



A fixed section of the scanner image comprised of eight input image words and eight output image words.

Logical Slot



A logical slot consists of one input and one output byte within a logical group. A byte consists of 8 bits, each bit represents one terminal on a discrete I/O module.

M files



The SLC M0 and M1 data files that reside in the scanner.

M files contain RIO network status (M1) and control (M0) information. The contents of these files can be directly accessed by your application program. Also, the M files are used to control and monitor RIO block transfer operations.

Output file



The scanner’s output file that is updated during the

SLC processor output scan.

Remote Chassis



The chassis containing an ASB module and connected to the local SLC chassis via the RIO link.

Remote Expansion Chassis



A chassis that is connected to a remote chassis using a 1747-C9 (91.4 cm [36 in.]) or 1747-C7 (15.2

cm [6 in.]) cable.

Reset, Adapter Decide



Commands sent by the scanner to a logical device during an RIO discrete transfer. These commands instruct the logical device to reset all of its discrete outputs if hold last state is not selected, or to hold all of its discrete outputs in their last state if hold last state is selected.

Glossary

G–3

Reset, Adapter Reset



Commands sent by the scanner to a logical device during an RIO discrete transfer. These commands instruct the logical device to reset all of its discrete outputs, regardless of the hold last state selection.

RIO Block Transfer



The exchange of up to 64 words of data between the scanner and a remote device. RIO block transfers only occur if you program them in your processor control program.

RIO Discrete Transfer



The exchange of image data between the scanner and adapter. RIO discrete transfers occur continuously whenever the scanner and adapter are communicating on the RIO link.

RIO Link



An Allen-Bradley communication system supporting high-speed serial transfer of Remote I/O (RIO) control information.

This link consists of one master and one or more slaves.

RIO Link Device



Refers to any Allen-Bradley or licensed third party product that connects to the RIO link as an adapter or slave device.

Scanner



The Catalog Number 1747-SN, Remote I/O Scanner, which is the master on the RIO network.

Scanner Image



The data table area within the scanner, used to exchange I/O information between the scanner and all the adapters on the RIO link. The scanner image is a portion of the SLC processor image.

SLC Chassis



A physical SLC rack that houses SLC processors and 1746 and 1747 I/O modules.

SLC Processor



The processor that controls the SLC chassis in which the the scanner is installed.

Slot



The physical location in any SLC chassis used to insert I/O modules.

Specialty I/O Module



An I/O module other than a discrete I/O module (e.g., an analog module).

Publication 17476.6 - July 1996

Index

Numbers

1-slot addressing, complementary I/O,

1-13

1/2-slot addressing, complementary I/O,

1-14

2-slot addressing, complementary I/O

configuration, 1-12

active device status, 4-24

adapter, 1-3

interaction with scanner, 1-6

adapter image, 1-3

size of, 4-10

addressing I/O modules, 4-31 overview, 4-31

Allen-Bradley, P-4 contacting for assistance, P-4

application examples

Block Transfer, 7-14

Dataliner, 7-8

PanelView, 7-11

RediPANEL keypad module, 7-1

RediPANEL/DCM, 7-4

baud rate, DIP switch, 1-19

Belden 9463 cable, maximum distance, 3-5

, A-1

bits

communication attempted, 4-22

enable device fault, 4-21

block transfer

BTR and BTW logic examples, 5-23

buffer layout, 5-8

considerations, 5-20

control flag definitions, 5-9 data words 0 through 63, 5-9

detailed explanation, 5-13

error codes, 5-11

general functional overview, 5-5

I/O image allocation, 5-6

logical address - M0:e.102, 5-8

M0 file BT control buffer layout, 5-9

M1 file buffer layout, 5-11

M1 file input/status buffers, 5-10

M1:e.102 - logical address status, 5-10

M1:e.103 - error code, 5-10

setting up, 5-21

slot addressing, 5-6

status flags, 5-12

theory of operation, 5-1 , 5-2

throughput, A-10

timing diagrams, 5-14

block transfer control flags, M0:e.100, 5-8 block transfer length, M0:e.101, 5-8

block transfer read, 5-1

data words 0 through 63, 5-10 block transfer status flags, M1:e.100, 5-10 block transfer words status, M1:e.101, 5-10

block transfer write, 5-1

BTR, 5-1

BTR and BTW logic examples, 5-23

BTW, 5-1

buffer layout

block transfer, 5-8

M0 file output/control, 5-8

cable distance, maximum, 3-5 , A-1

cable tie slots, 3-4

capturing M0-M1 file data, B-8

CE certification, 3-1

changing modes, table, 4-20

changing scanner mode, 3-7

chassis slot, 3-3 , 3-4 card guides, 3-3 , 3-4

communication problems, retry counters,

6-2

communication retry counters, 4-29

compatible devices, 1-20

complementary I/O, 1-10

1-slot addressing, 1-13

1/2-slot addressing, 1-14

2-slot addressing, 1-12

configuration rules, 4-5

considerations, 1-17

guidelines, 1-11

concepts, scanner I/O image, 1-7

configuration

G file, 4-3

I–2

Index

general rules, 4-5 rules concerning complimentary I/O, 4-5

configuring scanner, 4-32

considerations

block transfer applications, 5-20

complementary I/O, 1-17

configuring remote I/O, 4-10

device and remote output reset, 4-19

contacting Allen-Bradley for assistance,

P-4

contents of manual, P-2

control flag definitions, block transfer, 5-9

creating logical devices, crossing logical

rack boundaries, 4-11

crossing logical rack boundaries, 4-10

to create multiple logical devices, 4-11

D data transfer

block transfer, 1-9 discrete, 1-9

definitions, G-1

ER, DN, ST, 5-12

M1 file block transfer status flags, 5-12

detailed explanation, block transfer, 5-13

device control words, M0 file, 4-14

device fault status, 4-26

device inhibit, 4-14 device output reset, 4-14 device reset, 4-14

device starting address status, 4-23

devices, compatible with RIO scanner, 1-20

DIP switches, 1-18 , 1-19

discrete I/O throughput with block transfers

present example, A-8

discrete I/O throughput without block

transfers present example, A-4

discrete transfer, 1-6

transferring data, 1-9

EMC Directive, 3-1

equipment needed, 2-1

error codes, 6-2

block transfer, 5-11

European Union Directive Compliance, 3-1

examples

communication retry counters, 4-29

crossing logical rack boundaries, 4-10

device inhibit control, 4-15

resetting devices, 4-20

RIO device reset control, 4-16

RIO status, 4-27

extended node, 1-9

extended node capability, specifications,

3-5 , A-1

fault, LED, 1-19

functional overview, block transfer, 5-5

G file, 4-3

editing G file data, B-11

word 0, 4-3

word 1, primary logical device address,

4-3 word 2, primary logical image size, 4-3

word 3, secondary logical device

address, 4-4

word 4, secondary logical image size,

4-4

getting started, 2-1

procedure, 2-2

guidelines, complementary I/O

configuration, 1-11

H hardware features

DIP switch, 1-18

LEDs, 1-18

RIO network connector, 1-18

I/O image

description, 4-2 logical racks, groups, words, bits, 4-2

I/O image allocation, block transfer, 5-6

I/O image division, scanner, 1-3

I/O image files, overview, 4-1

illustrations

connecting drain shield, 3-4 wiring scanner, 3-4

inserting the cable tie, 3-3

Index

I–3

insertion, scanner, 3-3

installation, getting started, 2-1

LED conditions, table, 6-1

LEDs

comm, 1-19 fault, 1-19 green, 1-19 red, 1-19

status table, 3-8

troubleshooting, 6-1

link specification

logical, 1-9 physical, 1-9

logical device image size, 4-24

logical rack, crossing logical rack

boundaries, 4-10 logical rack boundaries, crossing, 4-10

M files

overview, 4-12 using binary files in conjunction, 4-12

M0 and M1 data files

capturing M0-M1 file data, B-8

minimizing the scan time, B-7

specialty I/O modules with retentive

memory, B-8

transferring data between processor files,

B-4

M0 file

description, 4-14 device control words, 4-14 device inhibit, 4-14

device inhibit control, 4-15

device output reset, 4-14 device reset, 4-14

RIO device reset control, 4-16

words 24 through 27, 4-17

words 8 through 11, 4-15

M0 file BT control buffer layout, block

transfer, 5-9

M0 file output/control, block transfer buffer,

5-8

M0:e.100, block transfer control flags, 5-8

M0:e.101, block transfer length, 5-8

M0:e.102, block transfer logical address,

5-8

M0:e.110 through 173, block transfer data

words 0-63, 5-9

M1 file

active device status, 4-24

block transfer status flags, 5-12

communication retry counters, 4-29

communication status, 4-21 description, 4-21

device fault status, 4-26

device starting address status, 4-23

enable device fault bit, 4-21

logical device image size, 4-24

M1:e.100 through 3200, 5-11

RIO baud rate status, 4-22

words 12 through 15, 4-26

words 16 through 31, 4-29

M1 file buffer layout, block transfer, 5-11

M1 file input/status buffers, block transfer,

5-10

M1:e.100, block transfer status flags, 5-10

M1:e.100 through 3200, block transfer

buffer layout, 5-11

M1:e.101, words sent or received, 5-10

M1:e.102, logical address status, 5-10

M1:e.103, block transfer - error code, 5-10

M1:e.103 through M1:e.3203, block transfer

error codes, 5-11

M1:e.110-173, block transfer data words 0

through 63, 5-10

manuals, related, P-2

module release, 3-4

network wiring, 3-4

noise immunity, A-1

O operation

run mode, 3-7 startup, 3-7

I–4

Index

operation modes, changing, 3-7

overview, M files, 4-12

power consumption, A-1

programming scanner, 4-32

publications, related, P-2

Quick Start for Experienced Users, 2-1

rack boundaries, crossing logical, 4-10

Worldwide representation.

Argentina • Australia • Austria • Bahrain • Belgium • Brazil • Bulgaria • Canada • Chile • China, PRC • Colombia • Costa Rica • Croatia • Cyprus • Czech Republic • Denmark •

Ecuador

•

Egypt

•

El Salvador

•

Finland

•

France

•

Germany

•

Greece

•

Guatemala

•

Honduras

•

Hong Kong

•

Hungary

•

Iceland

•

India

•

Indonesia

•

Ireland

•

Israel

•

Italy

•

Jamaica • Japan • Jordan • Korea • Kuwait • Lebanon • Malaysia • Mexico • Netherlands • New Zealand • Norway • Pakistan • Peru • Philippines • Poland • Portugal • Puerto

Rico

•

Qatar

•

Romania

•

RussiaCIS

•

Saudi Arabia

•

Singapore

•

Slovakia

•

Slovenia

•

South Africa, Republic

•

Spain

•

Sweden

•

Switzerland

•

Taiwan

•

Thailand

•

Turkey

•

United Arab Emirates • United Kingdom • United States • Uruguay • Venezuela • Yugoslavia

AllenBradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 3822000 Fax: (1) 414 3824444

Publication 17476.6 - July 1996

Supersedes Publication 17476.6 - February 1995

Publication 17476.6 - July 1996

PN 4007200501(B)

Key Features

Supports up to 64 I/O modules
Baud rates up to 115.2 Kbaud
Diagnostic LEDs for easy troubleshooting
Supports RIO block transfer for high-speed data transfer
Compatible with SLC 500 and PLC 5 controllers