1747-6.6, Remote I/O Scanner, User...

User

Manual

Remote I/OScanner(Cat. No. 1747�SN)

Allen�Bradley

Because of the variety of uses for the products described in thispublication, those responsible for the application and use of thiscontrol equipment must satisfy themselves that all necessary stepshave been taken to assure that each application and use meets allperformance and safety requirements, including any applicable laws,regulations, codes and standards.

The illustrations, charts, sample programs and layout examplesshown in this guide are intended solely for purposes of example.Since there are many variables and requirements associated with anyparticular installation, Allen-Bradley does not assume responsibilityor liability (to include intellectual property liability) for actual usebased upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for theApplication, Installation, and Maintenance of Solid-State Control(available from your local Allen-Bradley office), describes someimportant differences between solid-state equipment andelectromechanical devices that should be taken into considerationwhen applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, inwhole or in part, without written permission of Allen-BradleyCompany, Inc., is prohibited.

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

!ATTENTION: Identifies information about practicesor circumstances that can lead to personal injury ordeath, 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 successfulapplication 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.

Important UserInformation

Preface

Publication 1747�6.6 - July 1996

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 useAllen-Bradley small logic controllers.

You should have a basic understanding of SLC 500� products. Youshould understand programmable controllers and be able to interpretthe ladder logic instructions required to control your application. Ifyou do not, contact your local Allen-Bradley representative forinformation on available training courses before using this product.

If using Advanced Programming Software (APS), we recommendthat you review The APS Quick Start for New Users, Publication9399-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 operatethe 1747-SN RIO Scanner (Series B or later).

Who Should Use thisManual

Purpose of this Manual

PrefaceP–2


Contents of this Manual

Chapter Title Contents

Preface

Describes the purpose, background, and scope of

this manual. Also specifies the audience for whom

this manual is intended.

1 Overview

Contains the system overview, RIO network

overview, scanner/SLC� interaction, compatible

devices, and features.

2Quick Start for

Experienced UsersServes as a Quick Start Guide for the RIO scanner.

3 Installation and WiringProvides baud rate settings, installation

instructions, and wiring information.

4Scanner Configuration

and Programming

Provides scanner configuration information, I/O file

information, and G and M file descriptions.

5 RIO Block Transfer

Describes RIO block transfer theory, M file block

transfer buffer layout, block transfer examples, and

how to set up block transfer operations.

6 TroubleshootingProvides LED status information, troubleshooting

suggestions, and error codes.

7 Application ExamplesContains application examples for various system

configurations.

Appendix A SpecificationsContains scanner and system specifications, as

well as throughput information.

Appendix B M0-M1 Files and G FilesContains general information and usage of M and

G files.

Appendix CRIO Configuration

Worksheets

Contains blank worksheets for you to use when

configuring the scanner's I/O images.

Related Documentation

The following documents contain additional information concerningAllen-Bradley SLC and PLC� products. To obtain a copy, contactyour local Allen-Bradley office or distributor.

Preface P–3


For Read This DocumentDocument

Number

An overview of the SLC 500 family of products SLC 500 System Overview 1747�2.30

A description on how to install and use your Modular SLC 500

programmable controller

Installation & Operation Manual for Modular

Hardware Style Programmable Controllers1747�6.2

A procedural manual for technical personnel who use APS to

develop control applications

Rockwell Software Advanced Programming

Software (APS) User Manual9399�APSUM

A reference manual that contains status file data and instruction set

information for the SLC 500 processors and MicroLogix 1000

controllers.

SLC 500� and MicroLogix 1000� Instruction Set

Reference Manual1747�6.15

An introduction to APS for first�time users, containing basic

concepts but focusing on simple tasks and exercises, and allowing

the reader to begin programming in the shortest time possible

APS Quick Start for New Users 9399�APSQS

A training and quick reference guide to APS

SLC 500 Software Programmer's Quick Reference

Guide available on PASSPORT at a list price of

$50.00

ABT�1747�TSG001

A guide of common procedures used in APS.SLC 500 Common Procedures Guide available on

PASSPORT at a list price of $50.00ABT�1747�TSJ50

A procedural and reference manual for technical personnel who

use an HHT to develop control applicationsAllen�Bradley Hand�Held Terminal User Manual 1747�NP002

An introduction to HHT for first�time users, containing basic

concepts but focusing on simple tasks and exercises, and allowing

the reader to begin programming in the shortest time possible

Getting Started Guide for HHT 1747�NM009

An article on wire sizes and types for grounding electrical

equipmentNational Electrical Code

Published by the

National Fire

Protection

Association of

Boston, MA.

A complete listing of current Allen�Bradley documentation,

including ordering instructions. Also indicates whether the

documents are available on CD�ROM or in multi�languages.

Allen�Bradley Publication Index SD499

A glossary of industrial automation terms and abbreviations Allen�Bradley Industrial Automation Glossary AG�7.1

The following conventions are used throughout this manual:

• Bulleted lists such as this one provide information, not proceduralsteps.

• Numbered lists provide sequential steps or hierarchicalinformation.

• 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, capitalletters within brackets (for example, [ENTER] ).

• A function key icon matches the name of the function key you

should press, such as CONFIGOFFLINE

CONFIG

SAVE &EXIT

F8

.

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

Common Techniques Used inthis Manual

�

PrefaceP–4


Allen-Bradley offers support services worldwide, with over 75Sales/Support Offices, 512 authorized Distributors and 260authorized Systems Integrators located throughout the United Statesalone, plus Allen-Bradley representatives in every major country inthe 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, pleasereview the information in the Troubleshooting chapter first. Thencall 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 theenclosed Publication Problem Report.

If you have any suggestions for how this manual could be mademore 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

Allen�Bradley Support

Summary of Changes


Summary of Changes

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

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

The table below lists sections that document new features andadditional information about existing features, and shows where tofind this new information.

For This New Information See

CE Certificationchapter 3,

appendix A

Enhanced ladder logic programming examples chapter 5

New Information

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

New Information 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preface P-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Purpose of this Manual P-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents of this Manual P-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Documentation P-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Common Techniques Used in this Manual P-3 . . . . . . . . . . . . . . . . . .

Allen�Bradley Support P-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Local Product Support P-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Product Assistance P-4 . . . . . . . . . . . . . . . . . . . . . . . . .

Your Questions or Comments on this Manual P-4 . . . . . . . . . . . . . .

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

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

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

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

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

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

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

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

Transferring Data with RIO Discrete and Block Transfers 1-9 . . . . . .

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

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

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

Guidelines for Configuring Complementary I/O 1-11 . . . . . . . . . . . . .

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

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

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

Summary for Placing Modules Used In Complementary I/O 1-15 . . . .

Discrete Modules 1-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Modules 1-15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

Baud Rate DIP Switch 1-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

Compatible Devices 1-20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

Table of Contentsii

Quick Start for Experienced Users 2-1 . . . . . . . . . . . . . . . . . . .

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

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

Installation and Wiring 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

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

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

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

RIO Link Wiring 3-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Start Up 3-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Operation 3-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

At Power Up 3-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

In Run Mode 3-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Status LEDs 3-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration and Programming 4-1 . . . . . . . . . . . . .

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

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

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

General 4-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Concerning Complementary I/O 4-5 . . . . . . . . . . . . . . . . . . . . . . . .

Example G File Showing Primary and Complementary DeviceConfigurations 4-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Illegal Configuration Examples 4-7 . . . . . . . . . . . . . . . . . . . . . . . .

Example Scanner Input Image of the Primary Devices 4-8 . . . . . . . .

Example Scanner Input Image of the Complementary Devices 4-9 . .

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

G File Considerations 4-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Crossing Logical Rack Boundaries 4-10 . . . . . . . . . . . . . . . . . . . . .

Examples of Crossing Logical Rack Boundaries 4-10 . . . . . . . . . . . .

Creating More than One Logical Rack Device 4-11 . . . . . . . . . . . . . .

Understanding M Files 4-12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M0 Control File Description 4-14 . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Example of Device Inhibit Control 4-15 . . . . . . . . . . . . . . . . . . . . . .

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

Example of Device Reset Control 4-16 . . . . . . . . . . . . . . . . . . . . . .

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

Example of Remote Output Reset Control 4-18 . . . . . . . . . . . . . . . .

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

M1 Status File Description 4-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

Active Device Status 4-24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logical Device Fault Status 4-26 . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Status Example 4-27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Retry Counter Example for Primary Devices 4-29 . . . . . . . . . . . . . . .

Understanding Slot Addressing 4-31 . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC/Scanner Configuration 4-32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer 5-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

Scanner I/O Image Allocation For Block Transfer 5-6 . . . . . . . . . . .

Examples of BT I/O Image File Allocation 5-6 . . . . . . . . . . . . . . . . .

Scanner's Block Transfer Buffer Layout 5-8 . . . . . . . . . . . . . . . . . . . .

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

M0 File BT Control Buffer Layout 5-9 . . . . . . . . . . . . . . . . . . . . . . .

BT Control Flag Definitions 5-9 . . . . . . . . . . . . . . . . . . . . . . . . . . .

M1 File - Block Transfer Input/Status Buffers 5-10 . . . . . . . . . . . . . .

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

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

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

Detailed Operation of RIO Block Transfer 5-13 . . . . . . . . . . . . . . . . . . .

Block Transfer Timing Diagrams 5-14 . . . . . . . . . . . . . . . . . . . . . . .

Successful Block Transfer Read/Write 5-15 . . . . . . . . . . . . . . . . . . .

Block Transfer Failure at Startup 5-16 . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Failure after Startup of Transmission Across the RIO Link 5-17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC Control Program Canceling a BT Once Transmitted Across RIO Link 5-18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC Control Program Canceling a BT Prior to Transmission Across RIO Link 5-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Block Transfer Application Considerations 5-20 . . . . . . . . . . . . . . .

Setting Up a Block Transfer 5-21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Quick Reference to Status and Control Bits 5-22 . . . . . . . . . . . . . . . . .

Status Bits 5-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Control Bits 5-22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BTR and BTW Control Logic Examples 5-23 . . . . . . . . . . . . . . . . . . . .

Table of Contentsiv

Block Transfer Read Control Logic Example 5-23 . . . . . . . . . . . . . . .

Block Transfer Write Control Logic Example 5-25 . . . . . . . . . . . . . . .

Directional Continuous Block Transfer Example 5-29 . . . . . . . . . . . .

Directional Repeating Block Transfer Example 5-32 . . . . . . . . . . . . .

Directional Non�Continuous Block Transfer Example 5-35 . . . . . . . . .

Bidirectional Continuous Block Transfer Example 5-38 . . . . . . . . . . .

Bidirectional Alternating Block Transfer 5-43 . . . . . . . . . . . . . . . . . .

Bidirectional Alternating Repeating Block Transfer 5-49 . . . . . . . . . . .

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

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

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

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

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

Application Examples 7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RediPANEL Keypad Module 7-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scanner Configuration 7-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Program 7-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RediPANEL/DCM 7-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Example Program 7-6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dataliner 7-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Example Program 7-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PanelView 7-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Example Program 7-13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Block Transfer Application Example 7-14 . . . . . . . . . . . . . . . . . . . . . . .


System Layout Diagram 7-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Program 7-16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

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

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

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

Discrete I/O Throughput without Block Transfers (Tdm-nbt) Present A-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Scan Time Calculation (TRIO) A-4 . . . . . . . . . . . . . . . . . . . . .

Example Discrete I/O Throughput without Block Transfers Present A-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

Table of Contents v

Determining TSNo-bt A-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining Tbtx A-7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Example Discrete I/O Throughput with Block Transfers Present A-8 .

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

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

Determining the Number of Logical Racks Configured A-12 . . . . . . . .

TSNo without M0 File Writes A-13 . . . . . . . . . . . . . . . . . . . . . . . . . .

TSNo with M0 File Writes (No Block Transfers) A-13 . . . . . . . . . . . . .

M0-M1 Files and G Files B-1 . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

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

Monitoring Bit Addresses B-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .

M0/M1 Monitoring Option Disabled B-3 . . . . . . . . . . . . . . . . . . . . .

M0/M1 Monitoring Option Enabled B-4 . . . . . . . . . . . . . . . . . . . . . .

Transferring Data Between Processor Files and M0 or M1 Files B-4 .

Access Time B-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SLC 5/02 Processor Example B-5 . . . . . . . . . . . . . . . . . . . . . . . . .



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

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

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

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

Configuring G Files Using APS Software B-9 . . . . . . . . . . . . . . . . .

Editing G File Data B-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RIO Configuration Worksheet C-1 . . . . . . . . . . . . . . . . . . . . . .

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

Glossary G-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1


Overview

This chapter contains the following information:

• system overview

• how the scanner interacts with the SLC processor

• how the scanner interacts with adapter modules

• scanner I/O image concepts

• extended node capability

• complementary I/O

• scanner features

• compatible network devices

The Remote I/O (RIO) scanner, Catalog Number 1747-SN, is theremote I/O scanner for the SLC 500. It enables communicationbetween an SLC processor (SLC 5/02� or later) and remotelylocated (3,048 meters [10,000 feet] maximum) 1746 I/O chassis andother RIO compatible Allen-Bradley operator interface and controldevices. The 1747-SN scanner communicates with remotely locateddevices using the A-B Remote I/O link. The RIO link consists of asingle master (scanner) and multiple slaves (adapters).Communication between devices occurs over twisted pair cable withthe devices daisy-chained together. The scanner can reside in anyslot of the local SLC chassis except for slot 0.

The scanner transfers input andoutput data between itself and allconfigured network devices overtwisted pair cable. Note that theend�to�end length of the cable can bea maximum of 3,048 meters (10,000feet).

Dataliner� Message Display (Adapter/Slave)

PanelView� Operator Terminal (Adapter/Slave)

SLC 5/02or LaterProcessor

Remote Chassis

Remote Expansion Chassis

1747�ASB Module(Adapter/Slave)

RediPANEL�(Adapter/Slave)

Local SLC Chassis

RIO Scanner(Master of theRIO Link)

System Overview

1–2 Overview


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

The scanner transfers discrete input and output databetween itself, remote adapters, and the SLC processor.Remote adapters consist of 1746 chassis and otherAllen�Bradley operator interface and control devices.

RIOScanner


Quarter LogicalRackDevice

HalfLogical RackDevice

Three QuarterLogical RackDevice

Full Logical RackDevice

Half LogicalRackDevice

Full Logical RackDevice

Adapter 1 Adapter 2 Adapter 3 Adapter 4 Adapter 5 Adapter 6

The SLC processor transfers the scanner’s 4 logical racks (32 inputimage and 32 output image words) of discrete remote I/O image datainto the SLC input and output image files. You can adjust the size ofthe scanner input and output image file during configuration of yourSLC system so that the scanner only transfers the discrete I/O datayour application program requires. Configuration is done throughthe confiGuration file (G file). Refer to chapter 4, Configuration andProgramming for more information.

Important: The SLC 500 processor (SLC 5/02 or later) supportsmultiple scanners in its local I/O chassis. Themaximum 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 processordependent)

1–3Overview


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’simage is used by local I/O, the other portion is used by the scannerfor remote I/O.

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

Processor I/O Image Scanner I/O Image AdapterImage

Logical Group 7

Local I/O

Remote I/O(Scanner Image)

Logical Rack 2

Logical Rack 1

Logical Rack 0

Logical Group 0

The scanner image contains the image of each adapter on the RIOlink. The adapter is assigned a portion of the scanner image, whichis referred to as the adapter image.

1–4 Overview


The scanner communicates with each logical device in a sequentialfashion. First, the scanner initiates communication with a device bysending output data to the device. The device then responds bysending its input data back to the scanner, as illustrated below. Yourefer to this exchange as a discrete I/O transfer. After the scannercompletes its discrete I/O transfer with the last configured networkdevice, it begins another discrete I/O transfer with the first device.

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

RIO Scanner Scan

Scanner OutputImage File

The scanner updates itsinput image file each timeit scans a logical device.

OutputDevice 3

OutputDevice 2

OutputDevice 1

InputDevice 3

InputDevice 2

InputDevice 1

ScannerInputImage File

How the Scanner ScansRemote I/O

1–5Overview


SLC and Scanner Asynchronous Operation

The SLC processor scan and RIO scanner scan are independent(asynchronous) of each other. The SLC processor reads the scannerinput image file during its input scan and writes the output image fileto the scanner during its output scan. The RIO scanner continuesreading 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, andapplication program size, the scanner may complete multiple scansbefore the SLC processor reads the scanner’s input image file. TheRIO scanner updates its I/O files on a per logical rack basis.

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

SLC Processor

SLC Processor Scan Cycle RIO Scanner Scan Cycle

Program

The scanner updates itsinput image file each timeit scans a logical device.The scanner may scan allof its configured logicaldevices several timesbefore the SLC processorreads the scanner's inputimage file.

The SLC processor reads thescanner input image file into theSLC input image file, processesit, and creates an SLC outputimage file. The SLC processortransfers its output file to thescanner.

SLC InputImage File

SLC OutputImage File

ScannerInputImage File

Scanner OutputImage File

OutputImageDevice 3

OutputImageDevice 2

OutputImageDevice 1

InputImageDevice 3

InputImageDevice 2

InputImageDevice 1

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

1–6 Overview


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

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

RediPANEL

PanelView OperatorTerminal

SLC Local Chassis

ScannerProcessor

RIO DiscreteTransfers with Adapter 1




How the Scanner Interactswith Adapters

1–7Overview


The scanner’s I/O image consists of RIO logical racks and I/Ogroups. A full RIO logical rack consists of eight input image andeight output image words. (A word consists of 16 bits of data.) Eachword within an RIO logical rack is assigned an I/O group numberfrom 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 outputwords), half logical rack (4 I/O words), three quarter logical rack (6I/O words), or full logical rack. You may configure devices to startat any even I/O group number within an RIO logical rack. Morethan one physical device’s (adapter) I/O information can reside in asingle logical rack. Also, by crossing logical rack boundaries adevice can consist of more than one logical rack.

Important: The illustration below shows only the input imageconfiguration of the scanner’s I/O image. The outputimage configuration is the same.

Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number (decimal)

Word 0

Word 1Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21

Rack 1 Group 7Rack 2 Group 0

RIOLogicalRack 0

0818283848586878108118128138148158168178Bit Number (octal)

RIOLogicalRack 1

RIOLogicalRack 2

RIOLogicalRack 3

Quarter LogicalRack

Half LogicalRack

Three QuarterLogical Rack

FullLogicalRack

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

Not Used In ThisExample



Scanner I/O ImageConcepts

1–8 Overview


Example Scanner I/O Image

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

RIOScanner


Three Quarter LogicalRack DeviceBegins at LogicalRack 1, Group 0.

Half Logical RackDeviceBegins at LogicalRack 2, Group 0.

Quarter Logical RackDeviceBegins at LogicalRack 2, Group 4.

Full Logical RackDeviceBegins at LogicalRack 0, Group 0.

Device 1 Device 2 Device 3 Device 4

Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit NumberInput FileAddress

I:e.0I:e.1I:e.2I:e.3I:e.4I:e.5I:e.6I:e.7I:e.8I:e.9I:e.10I:e.11I:e.12I:e.13I:e.14

I:e.30I:e.31

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

I:e.15I:e.16I:e.17I:e.18I:e.19I:e.20I:e.21I:e.22I:e.23I:e.24I:e.25I:e.26I:e.27I:e.28I:e.29

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


RIOLogicalRack 0

Device 1

Device 2

Device 3

Device 4

e = slot number of the SLC chassis containing the scanner

0818283848586878108118128138148158168178Bit Number (octal)

RIOLogicalRack 1

RIOLogicalRack 2

RIOLogicalRack 3

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

Not Used

Not Used

1–9Overview


Transferring Data with RIO Discrete and Block Transfers

Input and output image data and command information are quicklyexchanged between a scanner and adapter using RIO discretetransfers. RIO discrete transfers are the simplest and fastest way ascanner and adapter communicate with each other. RIO discretetransfers, which are transparent to the user, consist of the scannersending the output image data to the adapter, and the adaptertransmitting input data to the scanner. Each RIO discrete transferalso contains scanner commands for the adapter.

Through your control program you command the SLC processor toinitiate RIO block transfers, which directs the scanner to exchangelarge amounts of data to/from an adapter. Block Transfers (BTs) usethe basic RIO discrete transfer mechanism of the RIO link.However, the actual transfer of data occurs asynchronous to thediscrete transfers. It is possible for several discrete transfers to occurbefore 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 cancommunicate is determined by the scanner’s and adapter’s physicaland logical specifications, as described below:

• Physical Specifications are the maximum number of adapters thatcan be connected to the scanner. For more information, seeExtended Node Capability below.

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

Extended Node Capability

Extended node functionality allows you to connect up to 32 physicaldevices on an RIO link. You must use 82 Ohm RIO link resistors inan extended node configuration. You can only use extended node ifall RIO link devices have extended node capability. (Refer to theCompatible Devices table at the end of this chapter, or to thespecifications of your device.) The 1747-SN Series B Scanner hasextended node capability. However, the smallest logical rackdivision is 1/4 logical rack and the scanner image size is 4 logicalracks. Therefore, the scanner is limited to 16 devices unlesscomplementary I/O is used. Refer to the following section for moreinformation on complementary I/O.

1–10 Overview


Complementary I/O

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

!ATTENTION: Because the primary andcomplementary chassis images overlap, input andspecialty combination I/O modules must never sharethe same image location. Inputs received by thescanner may be incorrect and RIO block transfers willnot be serviced properly. If an output module shares its output image withanother output module, both output modules receivethe same output information.

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

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

Primary Chassis Complementary Chassis Logical Rack NumberPrimary Chassis

Logical Rack Number Decimal Octal

0 8 108

1 9 118

2 10 128

3 11 138

1–11Overview


!ATTENTION: If the logical rack numbers are notproperly assigned, unpredictable operation of bothASB modules results. No ASB module errors occur.Refer to your ASB module user manual for specificinformation on setting the address of thecomplementary chassis. (For example, in the1771-ASB manual the addresses for thecomplementary chassis are referred to ascomplementary 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 oppositeanother output module in the complementary chassis; they use thesame bits in the output image table. However, we do notrecommend this placement of modules for redundant I/O.

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

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

1–12 Overview


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

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

I 8

O 8

I 16

BTI 8O 8

I 8

O 8

O 16

O 8

O 8

O 8

BT

O 8

EMPTY

O 8

O 8

O 8

I 8

I 8

EMPTY

EMPTY

1 2

O 8

2

EMPTY

2

EMPTY

2

0 1 2 3 4 5

I 16

I 16

I 16

O 16

O 16

O 16

0 1 2 3 4 5

I 16

I 16

I 16

O 16

O 16

O 16

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

Example 1

Example 2

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

Important: With 2�slot addressing, if an input module resides in either slot, associated with alogical group, of the primary chassis, an input module cannot reside in that logical group'scomplementary chassis.

1 1

1

1–13Overview


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

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

I 16

EMPTY

1

2

0 1 2 3 4 5

Example 1

Example 2

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

I 16

I 16

I 16

O 16

O 16

O16

O 16

BT I 16

O 16

O 16

6 7 0 1 2 3

O 16

O 16

I 16

I 16

I 16

O 16

O 16

1

I 16

O 16

I 16

O 16

I 16

0 1 2 3 4 5

I 16

I 16

6 7 0 1 2 3

O 16

O 16

I 16

I 16

I 16

I 16

I 16

I 16

I 16

I 16

I 16

O 16

O 16

O 16

O 16

O 16

O 16

O 16

O 16

O 16

O 16

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

1–14 Overview


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

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

I

1

2

01 23 45 67 01 23

Example 1

Example 2

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

1 = Output modules use the same output image table bits. This is not recommended.

I I OO O O BT I

45 67 01 23

O O I I IO O

1

I

I I

O O

I I I I I I I I

O O O O O O O O

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

01 23 45 67 01 23 45 67 01 23

O

O

EMPTY

1–15Overview


Summary for Placing Modules Used In Complementary I/O

Discrete Modules

Addressing Method Types of Modules used Placement

2�slot 8�point

Install input modules

opposite output modules,

and output modules

opposite input modules.➀

1�slot 8�point, 16�point

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

➀ 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

2�slot

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

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

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

empty.

In the right slot of the complementary I/O group, you can

place an 8�point output module; this slot must be empty if

the corresponding slot in the primary I/O group is a block

transfer module.

1�slotLeave the corresponding I/O group in the complementary

chassis empty.

1/2�slotLeave the corresponding I/O group in the complementary

chassis empty.

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

1–16 Overview


0 1 2 3 4 5 6 7 8

Slot Pair 1 2 3 4

I I I IO O O O

0 1 2 3 4 5 6 7 8

Slot Pair 1 2 3 4

O O O O

O

I = Input Module

= Output Module

Input Image Output Image

= unused image space

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

1

Slot Pair

2

3

4

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

1

2

3

4

Input Imagefrom Primary Chassis

Output Imagefrom Primary Chassis

Output Imagefrom Complementary Chassis

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 7

Slot 7

Input Imagefrom Complementary Chassis

Slot Slot

Primary Chassis Complementary Chassis

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

1

2

3

4

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

1

2

3

4

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 7

Slot 7

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

Scanner's I/O Image

1

2

3

4

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 7

Slot 7

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

1

2

3

4

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Slot 1

Slot 2

Slot 3

Slot 4

Slot 5

Slot 6

Slot 7

Slot 8

Group 0

Group 2

Group 4

Group 6

Group 1

Group 3

Group 5

Group 7

Group 0

Group 2

Group 4

Group 6

Group 1

Group 3

Group 5

Group 7

Both images are overlapped in thescanner. The overlapped image

appears where the primary chassisimage is configured to reside.

In this case, the primary chassisimage is configured as starting

logical rack 0 and starting logicalgroup 0.

I I I I

Primary Chassis Configured As:Logical Rack Number 0

Logical Group Number 0Image Size (logical groups) 16

Addressing Mode 1/2-slotPrimary/Complementary Primary

Complementary Chassis Configured As: Logical Rack Number 8 (decimal)

Logical Group Number 0Image Size (logical groups) 16

Addressing Mode 1/2-slotPrimary/Complementary Complementary

LogicalRack 0

LogicalRack 1

07815

7 01017Decimal

Octal

07815

7 01017Decimal

Octal

07815

7 01017Decimal

Octal

07815

7 01017Decimal

Octal

07815

7 01017Decimal

Octal

07815

7 01017Decimal

Octal

Slot Pair Slot Pair Slot Pair

Slot Pair Slot Pair

1–17Overview


Complementary I/O Application Considerations

If you configure a complementary device to use more I/O imagespace than an associated primary device, then block transfers canonly be performed to locations in the complementary device thathave associated I/O image space in the primary device. Forexample, if a primary device is 1/2 logical rack and a complementarydevice is a full logical rack, block transfers can be performed only inthe first 1/2 logical rack of the complementary device. Attemptingblock transfers in the last half of the complementary device willresult in a BT error (error 11 – device not configured).

Word 7

Word 5Word 6

Word 3

Word 1Word 2

Word 0

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

ÉÉÉÉÉÉÉ

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

ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉ Logical

Rack 8

ËËËËËËËËËËË

ÉÉÉÉÉÉ

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

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


ÉÉÉÉÉÉÉÉ

ËËËËËËËËËËË

ÉÉÉÉÉÉÉÉ

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

1/2 logical rackconfigured andusable

1/2 logical rack notconfigured

1/2 logical rackconfigured and usable

1/2 logical rackconfigured, but notusable for BT sinceWords 4-7 are notconfigured for theprimary device.

Complementary 1771 I/O Module Details

Use the following modules in either primary or complementary I/Ochassis 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/Ochassis opposite any type of module. However, these modules donot work as stand-alone modules; each one has an associated mastermodule. Use care when placing the master modules in the I/Ochassis:

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

1–18 Overview


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

SCANNER

12

N O

SL

C 500

CA

T

SE

RIA

L NO

.

Rem

ote I/O

Scan

ner

SE

RFAC

U

LLIS

TE

D IN

D. C

ON

T. EQ

.

FO

R H

AZ

. LOC

. A196

CLA

SS

I, GR

OU

PS

A, B

, C A

ND

D, D

IV.2

OP

ER

AT

ING

S

AT

EM

PE

RA

TU

RE

CO

DE

T3C

B

HO

ST

FR

N.:

FR

N.:

PLU

G

CU

RR

EN

T R

EQ

UIR

EM

EN

T: 600 mA

@5V

DC

MA

KE

IN U

.S.A

.

1 2NO

COMM FAULT

SW1

CONNECT ONE END OFCABLE SHIELD TO CHASSISMOUNTING BOLT. REFER TO

USER'S MANUAL.

1747-SN

LINE 1

LINE 2

SHIELD

1 2 KBAUD

ON

OFF

OFF OFF

OFF

ON

ON

ON

57.6

115.2

230.4

230.4

√

2

1

3

456

7

ÎÎÎÎÎÎÎÎÎÎ

Table 2.A Hardware Features

1 Status LEDs Displays normal communication and fault status

2 Front Label Allows user to record configured baud rate

3 RIO Link Connector Allows for connections to RIO link devices

4 Cable Tie Slots Secures communication wiring from module

5 Self�Locking Tabs Secures module in chassis slot

6 Side Label (Nameplate) Provides module information

7 Baud Rate DIP switch Allows user to set baud rate

Hardware Features

1–19Overview


Baud Rate DIP Switch

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

• 57.6 Kbaud

• 115.2 Kbaud

• 230.4 Kbaud

Important: For proper system operation, the baud rate of all deviceson 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 isred. The FAULT LED’s normal state is off; therefore, it is offwhenever the scanner is operating properly.

COMM LED – allows you to monitor communication with allconfigured devices. This LED is green and its normal state is ononce the processor has entered Run mode. The LED is red if there isa communication problem. The COMM LED status information isvalid only when the FAULT LED is off.

RIO Link Connector

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

1–20 Overview


Compatible Devices

Catalog

NumberDevice Comments

1785�LT/x➀➁ PLC�5/15� (in adapter mode) -

1785�LT2➀➁ PLC�5/25� (in adapter mode) -

1785�LT3➀➁ PLC�5/12� (in adapter mode) -

1785�L30x➀➁ PLC�5/30� (in adapter mode) -



1771�ASC Remote I/O Adapter Module -

1771�ASB➂➄ Remote I/O Adapter Module -

1771�AM1➀ 1�Slot I/O Chassis W/Integral

Power Supply and Adapter-

1771�AM2➀ 2�Slot I/O Chassis W/Integral

Power Supply and Adapter-

1784�F30D➀ Plant Floor Terminal Remote

I/O Expansion Module-

1771�RIO Remote I/O Interface Module -

1771�JAB➀ Single Point I/O Adapter Module -

1771�DCM Direct Communication Module -

1778�ASB➀ Remote I/O Adapter Module -

1747�DCM➀ Direct Communication Module -

2706�xxxx➀➃ DL40 Dataliner -

2705�xxx➀ RediPANELRequires half logical rack configurationif you want to use stored messages.

2711�xx➀ PanelView TerminalYou can address PanelView Terminals asup to four full logical racks of discrete I/O.You can also assign partial logical racks.

1336�G2➀ Remote I/O Adapter for 1336

AC Industrial Drives-

1395�NA➀ Remote I/O Adapter for 1395

DC Industrial Drives-

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

1747�ASB➀ SLC 500 Remote I/O Adapter

Module-

1794�ASBFlex I/O 24VDC Remote I/O

Adapter-

➀ Extended node capability

➁ In adapter mode

➂ Series A, B, and C

➃ Must be Catalog Number 2706�ExxxxxB1

➄ Extended node capability for Series B and C

Chapter 2


Quick Start for Experienced Users

This chapter helps you to get started using the RIO Scanner. Webase the procedures here on the assumption that you have a basicunderstanding of SLC 500 products.

You must:

• understand electronic process control

• be able to interpret the ladder logic instructions for generating theelectronic signals that control your application

Because it is a start-up guide for experienced users, this chapter doesnot contain detailed explanations about the procedures listed. Itdoes, however, reference other chapters in this book where you canget more detailed information. It also references otherdocumentation that may be helpful if you are unfamiliar withprogramming techniques or system installation requirements.

If you have any questions, or are unfamiliar with the terms used orconcepts presented in the procedural steps, always read thereferenced chapters and other recommended documentation beforetrying 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 inthis manual demonstrate the use of Allen-Bradley’s AdvancedProgramming Software [APS] for personal computers.)

• termination kit (package of resistors and ring lug included withthe scanner)

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

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

Required Tools andEquipment

2–2 Quick Start for Experienced Users


1. Check the contents of the shipping box. Reference

Unpack the module making sure that the contents include:

• RIO Scanner (Catalog Number 1747 SN)• termination kit• user manual (Publication 1747�6.6)

-

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

2. Ensure your chassis supports placement of the 1747�SN module. Reference

Review the power requirements of your system to see that your chassis supports placement of the

scanner module. The scanner consumes 600 mA @ 5VDC.

For modular style systems, calculate the total load on the system power supply using the procedure

described in the SLC 500� Modular Hardware Style Installation & Operation Manual, Publication

1747�6.2, or the SLC 500� Family System Overview, Publication 1747�2.30.

Chapter 3(Installation and

Wiring)

Appendix A(Specifications)

3. Configure the module using the DIP switches. Reference

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.


Wiring)

Baud Rate DIP Switch Position

Switch 1 Switch 2

57.6K baud on on

115.2K baud on off

230.4K baud off on

230.4K baud off off

Procedures

2–3Quick Start for Experienced Users


4. Insert the 1747�SN module into the chassis. Reference

ATTENTION: Never install, remove, or wiremodules with power applied to the chassis ordevices wired to the module.!

(Chapter 3)(Installation and

Wiring)

Make sure system power is off; then insert the scanner module into your 1746 chassis.

In this example procedure, local slot 1 is selected.

Card

Guide

Top and Bottom

Module Release(s)

5. Connect all RIO link devices. Reference

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.

(Chapter 3)(Installation and

Wiring)

2–4 Quick Start for Experienced Users


6. 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 Allen�Bradley's Advanced Programming Software [APS] to

configure your system can be found in the APS User Manual, Publication 9399�APSUM.)

Example of Software Prompt:

Chapter 4(Configuration and

Programming)

yourprogramming

software's usermanual

Press ENTER to select I/O Module

Enter Module ID Code> 13608

offline SLC 5/02 File EXAMPLE

F2

SELECTMODULE

7. Enter the number of scanned words. Reference

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 Allen�Bradley's Advanced Programming Software [APS] to

configure your system can be found in the APS User Manual, Publication 9399�APSUM.)


Programming)

yourprogramming


2–5Quick Start for Experienced Users


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

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

9399�APSUM.)


Programming)

Chapter 5(Block Transfer

LadderProgramming

Examples)

Chapter 7(ApplicationExamples)

yourprogramming


9.9. Go through the system start�up procedure. Reference

1. Apply power.

2. Download your program to the SLC.

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


Wiring)

FAULT LED is off.

COMM LED is green.

SCANNERFAULTCOMM

Chapter 3


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 withinthe European Union and EEA regions. It has been designed andtested to meet the following directives.

EMC Directive

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

• EN 50081-2EMC – Generic Emission Standard, Part 2 – IndustrialEnvironment

• EN 50082-2EMC – Generic Immunity Standard, Part 2 – IndustrialEnvironment

This product is intended for use in an industrial environment.

Compliance to EuropeanUnion Directives

3–2 Installation and Wiring


Below are supported baud rates and switch positions:

Baud Rate DIP Switch Position

Switch 1 Switch 2

57.6K baud on on

115.2K baud on off

230.4K baud off on

230.4K baud off off

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

Important: For proper RIO link system operation, all devices mustbe configured for the same baud rate.

Baud RateDIP Switch

57.6K baud 115.2K baud

230.4K baud 230.4K baud

12

N O

12

N O

12

N O

12

N O

➀

➀ This is the default position as shipped from the factory.

Baud Rate Selection

3–3Installation and Wiring


Installation procedures for this module are the same as for any otherdiscrete I/O or specialty module. Refer to the illustration on page3–4 to identify chassis and module components listed in theprocedures below.

!ATTENTION: Disconnect system power beforeattempting to install, remove, or wire the scanner.

Important: Make sure you have set the DIP switches properlybefore installing the scanner.

Important: Before installation, ensure that your modular SLCpower 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 500processor.

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

4. Attach the RIO link cable to the connector on the front of themodule, behind the door. Ground the cable’s shield wire to achassis mounting bracket. Refer to the RIO link wiringillustration on page 3–4.

5. Insert the cable tie in the slots.

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

7. Cover all unused slots with the Card Slot Filler, Catalog Number1746-N2.

Scanner Installation



.

.

.

Card Guide

Cable Tie

Module Release

Removal

1. Disconnect power.

2. Remove all cabling.

3. Press the releases at the top and bottom of the module and slidethe module out of the chassis slot.

4. Cover all unused slots with the Card Slot Filler, Catalog Number1746-N2.

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

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

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

RIO Link Wiring



Baud RateMaximum Cable Distance

(Belden 9463) Resistor Size

Using Extended Node57.6K baud 3048 meters (10,000 feet)

82� 1/2 WattUsing Extended Node

Capability115.2K baud 1524 meters (5,000 feet)

82� 1/2 Watt

Brown Green Brown GoldCapability230.4K baud 762 meters (2,500 feet)

Brown-Green-Brown-Gold

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

Not Using Extended Node 115.2K baud 1524 meters (5,000 feet)

150� 1/2 Watt

Brown-Green-Brown-GoldNot Using Extended Node

Capability230.4K baud 762 meters (2,500 feet)

82� 1/2 Watt

Gray-Red-Black-Gold

LINE 1 _______

LINE 2 _______

RIO LinkConnector

RIO Scanner

Line 1 – Blue

Line 2 – Clear

For New Installations - To ensure a proper earth ground of the cable shield, follow these steps:1. While the RIO link connector is plugged into the scanner and lines 1 and 2 are connected, strip the cable back to expose enough shield drain wire to reach a chassis mounting bracket.2. Attach the ring terminal lug (supplied) to the end of the shield drain wire.3. Attach the ring terminal lug to the SLC chassis mounting bracket. Note that for new installations the middle (shield) terminal is not used when connecting to the scanner.Important:The RIO cable shield must be grounded at the scanner end only.For Series A Scanner Retrofits - To eliminate the need to strip the cable back, follow these steps:1. Attach the shield wire and a short piece of #20 AWG wire (dotted line) to the shield lug of the RIO Link Connector.2. Attach the other end of the #20 AWG wire to the ring terminal lug.3. Attach the ring terminal lug to a chassis mounting bracket.Important:The RIO cable shield must be grounded at the scanner end only.Ensure that the unshielded portion of the link communication wire (blue and clear) is as short as possible.

Chassis MountingBracket

RIO LinkConnector

TerminatingResistor Last PhysicalDevice End

TerminatingResistorScanner End

Shield Drain Wire

Shield – Shield

SHIELD _____

For New InstallationsUsing Series BScanners

For Series AScannerRetrofits

Shield Drain Wire

Ring Lug



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

1. Apply power to your SLC processor. If you powered down withthe SLC processor in Program, Test, or Fault mode, you will haveto place your processor in Run mode.

When power is applied to your scanner it requires about threeseconds to complete its power up diagnostics. During this time,the FAULT and COMM LEDs cycle on and off. After thediagnostics are complete and the SLC processor is in the Runmode, 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 isconfigured properly and all RIO link devices arecommunicating.

2. Make sure you have configured your SLC processor anddownloaded an application program. (Refer to chapter 4.)

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

Start Up



Below is a description of the scanner’s operation at power up, runmode, 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) isoff until the SLC is changed to Run or Test mode.

In Run Mode

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

FAULT

FAULT LED is off.

COMM LED is green.

SCANNERCOMM

When Changing From Run Mode

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

• scanner’s COMM LED remains green.

• the scanner continues to read its input devices and send outputdata to its RIO adapters.

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

Important: If you are using Block Transfer (BT) functionality, BTsmay not function on adapters in Hold Last Statesettings. Refer to each device’s user manual forinformation on BTs and Hold Last State settings.

Scanner Operation



The scanner has two LEDs that indicate its operating status, FAULTand 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 andoperating properly. The COMM LED state is valid only when theFAULT LED is off.

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

FAULT LED COMM LED Status Information

Flashing Red Not applicable Scanner configuration error

No RIO link communication attempted

Duplicate scanner detected on RIO link

Red Not applicable Major fault on scanner

No RIO link communication attempted

Off Red Hardware fault detected

Off Off Scanner is operating properly.

Scanner is offline (no RIO link communication

attempted).

Off Green Scanner is operating properly.

Scanner is online (active communication

established with all devices).

Off Flashing Green Scanner is operating properly.

At least one configured RIO link device is not

communicating.

Off Flashing Red Scanner is operating properly.

None of the configured RIO link devices are

communicating.

Status LEDs

Chapter 4


Scanner Configuration andProgramming

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

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

ÇÇÇÇÇÇÇ

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


ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉ

ÉÉÉÉÉÉ

ÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

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

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇ


ÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

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


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇ

ÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

078150717 10Bit Number Octal

LogicalRack 1

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

LogicalRack 0

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



ÉÉÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉ

ÇÇÇÇÇÇÇÇ

LogicalRack 2

ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ

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


ÇÇÇÇ


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





ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

LogicalRack 3

Input ImageOutput Image

SN Series B Scanner(RIO Master)

Scanner Input and Output Images

The scanner accommodates up to 32 words of output forremote devices.

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

Word 10Word 11

Word 8Word 9

Word 14

Word 12Word 13

Word 15

LogicalRack 1

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

LogicalRack 2

Word 26Word 27

Word 24Word 25

Word 30

Word 28Word 29

Word 31

Word 23

Word 21Word 22

Word 19Word 20

Word 17Word 18

Word 16

LogicalRack 3

Bit Number Decimal 078150717 10Bit Number Octal

Bit Number Decimal

Word 10Word 11

Word 8Word 9

Word 14

Word 12Word 13

Word 15

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

Word 26Word 27

Word 24Word 25

Word 30

Word 28Word 29

Word 31

Word 23

Word 21Word 22

Word 19Word 20

Word 17Word 18

Word 16

Note that some RIO devices (e.g.,1771) use octal bit numbers.

Understanding RemoteInput and Output ImageFiles

4–2 Scanner Configuration and Programming


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

Logical Rack 3 Group 6















0123456789101112131415Bit Number (decimal) SLC InputFile Address

I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.30

I:e.31

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31
















I:e.15

I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 2 4

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21

Logical Rack 1 Group 7Logical Rack 2 Group 0

LogicalRack 0

LogicalRack 1

LogicalRack 2

LogicalRack 3

0818283848586878108118128138148158168178Bit Number (octal)


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

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

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

4–3Scanner Configuration and Programming


When you program your SLC system you use the G file to configurethe scanner’s I/O image file. Your scanner’s G file configuration isbased on the devices that you have on the RIO link. G fileconfiguration consists of setting logical device starting addresses andthe logical device image size of each physical device/adapter withwhich the scanner communicates.

You enter G file configuration information using programmingsoftware, such as Advanced Programming Software (APS), or theHand-Held Terminal (HHT) if you have an SLC 5/02 processor. Seeappendix B for further details.

Neither your application program nor your programming device canaccess or alter the G file while online with the processor. To changethe G file you must go offline into the program file, make anynecessary changes, and download the program containing the alteredconfiguration. The G file consists of five words which are describedbelow.

Word 0 – contains scanner information for the SLC processor. Yourprogramming device automatically sets up Word 0. Do not attemptto alter word 0.

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

Word 1, Primary/Normal Logical Device Address – specifies thelogical 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 wordrepresents a logical address. To specify an address you place a 1 atthe bit corresponding to the starting logical address of each logicaldevice.

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

RIO Configuration Using GFiles



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

Word 4, Complementary Device Logical Image Size – specifiesthe logical image size (amount of scanner I/O image) of thecomplementary devices set in word 3. As with word 3, these bitscorrespond to RIO logical rack and logical group numbers. Tospecify image size you place a 1 at each group a device occupies.

Important: Setting device addresses in word 3 of the G fileconfigures the system to operate in the complementaryI/O mode. Not setting device addresses in word 3causes the system to operate only in the primary/normalmode. If you wish to operate in the complementarymode and you only have primary devices configured,word 3 of the G file must be set to a decimal “1,” andword 4 of the G file must be equal to zero.

ÉÉÉÉ

1

0

ÇÇÇÇ

1

0123456789101112131415

0000010000000100

ÉÉÉÉ

1000000ÇÇÇÇ

1000ÉÉÉÉ

100

ÉÉ100ÇÇ1ÉÉ1ÉÉ1ÉÉ1ÉÉÉ1ÇÇ1ÇÇ100ÉÉ1ÉÉ1ÉÉÉ1

Bit Number

024602460246

RIO Logical Rack 3Starting Logical Group

0246

I/O Mix, Word 0

Primary/Normal Logical Device Address,Word 1

Primary/Normal Logical Image Size,Word 2

G File

Contains scannerinformation for the SLC.Your programming deviceautomatically sets thescanner information.

Specifies the RIOstarting addresses ofprimary/normal logicaldevices.

Specifies the logicalimage size assigned toprimary/normal logicaldevices set in Word 1.

RIO Rack 0 Image Size

0246

RIO Rack 1Image Size

0246


0246


0246

Full Logical Rack DeviceHalf Logical Rack DeviceThree Quarter Logical Rack Device

Quarter Logical Rack Devices




ÇÇ1 ÉÉ100ÉÉ10000ÇÇ1000ÉÉ100

ÉÉÉÉ

100ÇÇÇÇ

1ÉÉÉÉ

1ÉÉÉÉ

1ÉÉÉÉ

1ÉÉÉÉÉÉ

10ÇÇÇÇ

1ÇÇÇÇ

100ÉÉÉÉ

1ÉÉÉÉ

1ÉÉÉÉÉÉ

1

024602460246


0246

Complementary Logical Device Address,Word 3

Complementary Logical Image Size,Word 4


0246


0246


0246


0246




Specifies the RIOstarting addresses ofcomplementary logicaldevices.

Specifies the logicalimage size assigned tocomplementary logicaldevices set in Word 3.

Note: A complementary logical rack is alwaysnumbered 8 above its primary logical rack. Also, logicalracks 8, 9, 10, and 11 are sometimes referred to ascomplementary logical racks 0, 1, 2, and 3.



Rules for Configuring the Scanner

General

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

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

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

Concerning Complementary I/O

• It is valid for you to have a complementary device configuredeven if no associated primary device exists. Also,complementary devices do not have to be the same logical imagesize 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 complementarydevice configured in G file words 3 and 4.

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

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

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

• A complementary device cannot be configured at locations whereprimary devices are configured unless they both start at the samelocation.

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

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



Example G File Showing Primary and Complementary Device

Configurations

In the example that follows we configured the scanner tocommunicate with primary and complementary devices. These arethe device addresses and image sizes:

• Logical Racks 0/8, Logical Group 2 contain a primary 3/4 logicalrack 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 logicalrack device, and a complementary 1/4 logical rack device.

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

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

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

ÇÇÇÇ

0

0123456789101112131415

0000010000000100

ÉÉÉÉ

010ÉÉÉÉ

00011ÇÇÇÇ

0000ÉÉÉÉÉÉ

101

ÉÉÉÉ

011ÇÇÇÇ

1ÉÉÉÉ

0ÉÉÉÉÉÉ

0ÉÉÉÉ

0ÉÉÉÉ

11ÇÇÇÇ

1ÇÇÇÇ

100ÉÉÉÉÉÉ

1ÉÉÉÉ

0ÉÉÉÉ

1

Bit Number

024602460246


0246

I/O Mix, Word 0

G File


0246


0246


0246


0246




ÇÇÇÇ

0ÉÉÉÉ

010ÉÉÉÉ

10011ÇÇÇÇ

0000ÉÉÉÉ

100

ÉÉÉÉ

011ÇÇÇÇ

1ÉÉÉÉ

1ÉÉÉÉ

1ÉÉÉÉÉÉ

0ÉÉÉÉ

11ÇÇÇÇ

0ÇÇÇÇ

000ÉÉÉÉ

1ÉÉÉÉÉÉ

1ÉÉÉÉ

0

024602460246


0246


0246


0246


0246


0246




Primary/Normal Logical Device Address,Word 1

Primary/Normal Logical Image Size,Word 2


Complementary Logical Image Size,Word 4



Illegal Configuration Examples

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

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

The G file configuration on page 4–6 would provide the primaryand complementary input images to the scanner, which are illustratedon the following pages. Note that the output images would be thesame.



Example Scanner Input Image of the Primary Devices

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

• Device 1 – starting at Logical Rack 0, Logical Group 2 is aprimary 3/4 logical rack device.

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




















I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.30

I:e.31

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12Word 13Word 14

Word 5Word 6

Word 30

Word 31















I:e.15

I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

Word 15

Word 16

Word 17Word 18

Word 19

Word 22

Word 23

Word 2 4

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21



Logical

Rack 0

Logical

Rack 1

Logical

Rack 2

Logical

Rack 3

0818283848586878108118128138148158168178Bit Number (octal)


Device 1

Device 5

Device 2

Device 3

Device 4

= not used



Example Scanner Input Image of the Complementary Devices

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

• Device 6 – starting at Logical Rack 8, Logical Group 2 is acomplementary 3/4 logical rack device.





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

















I:e.0

I:e.1

I:e.2

I:e.3

I:e.4

I:e.5

I:e.6

I:e.7

I:e.8

I:e.9

I:e.10

I:e.11

I:e.12

I:e.13

I:e.14

I:e.30

I:e.31

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31














I:e.15

I:e.16

I:e.17

I:e.18

I:e.19

I:e.20

I:e.21

I:e.22

I:e.23

I:e.24

I:e.25

I:e.26

I:e.27

I:e.28

I:e.29

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 2 4

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Logical

Rack 8

Logical

Rack 9

Logical

Rack 10

Logical

Rack 11

0818283848586878108118128138148158168178Bit Number (octal)


Device 6

Device 7

Device 8

Device 9

Device 10

= not used



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

G File Considerations

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

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

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

Crossing Logical Rack Boundaries

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

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

Examples of Crossing Logical Rack Boundaries

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

Considerations WhenConfiguring Remote I/O



Bit Number (Decimal)

LogicalRack 1

07815

Scanner Input or Output Image

LogicalRack 0

Group 2Group 3

Group 0Group 1

Group 6

Group 4Group 5

Bit Number (Decimal)

Group 7

LogicalRack 1

07815


Group 7

Group 5Group 6

Group 3Group 4

Group 1Group 2

Group 0

LogicalRack 0

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

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

Group 2Group 3

Group 0Group 1

Group 6

Group 4Group 5

Group 7

Group 7

Group 5Group 6

Group 3Group 4

Group 1Group 2

Group 0

AdapterImage

AdapterImage

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

Creating More than One Logical Rack Device

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

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

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

• The adapter may receive different communication commands foreach logical device. In this case, the adapter decides whichcommand it responds to.

Group 2Group 3

Group 0Group 1

Group 6

Group 4Group 5

Group 7

LogicalRack 1

Group 7

Group 5Group 6

Group 3Group 4

Group 1Group 2

Group 0

LogicalRack 0

In this example theadapter is configured tostart at Logical Rack 0,

Logical Group 0, and uses14 words of I/O image.

Note that two RIO discretetransfers are required for

the scanner to update theadapter image containing

two logical devices.

AdapterImage

LogicalDevice

LogicalDevice

Bit Number (Decimal) 07815




M Files OverviewThe scanner provides RIO device control and status informationthrough the M0 and M1 files. The M0 file is a control file. The M1file is a status file

The SLC processor does not automatically update M file data duringthe end of the program scan as it does I/O scans. Instead, M filevalues act as interrupts and are immediately read from or written toupon the execution of the ladder logic instruction in which they areused. When M-file data (bits or words) is addressed in the ladderprogram, the processor stops scanning the program to read or writethe M-file data to/from the scanner module. M-file bits/words in theladder program will, therefore, impact the ladder scan time. If scantime is critical, it is better to set binary file bits and copy them all atonce to the M0 file, or copy a portion of the M1 file to a binary fileand then address the binary file in the program. Refer to the ladderexample that follows. For more information on M files, refer toappendix B. You can find M file information relating to BlockTransfer operations in chapter 5, Block Transfer.

Understanding M Files



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

Rung 2:1Examine B3/13 (B3:0/13), an internal storage bit, to determine when ablock transfer is done. Note that examining multiple individual M–filebits 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:2Examine B3/12 (an internal storage bit) to determine if a BT erroroccurred. 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 datacannot be directly monitored. To monitor M files, youmust move the M file words into an SLC file that can bemonitored, e.g., an integer “N” file. SLC 5/03 or laterprocessors (running APS 4.02 or later) allow you tomonitor M files directly. However, do not address Mfile bits more than necessary throughout yourapplication program. The processor accesses M fileslike immediate I/O. Therefore, excessive addressing ofM files can greatly increase SLC processor scan time.For more information on M files, refer to appendix B.



M0 Control File Description

You can control the operation of individual devices on the RIO linkwith 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 stopscanning an RIO device by using words 8 – 11.

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

• Remote Output Reset – command an RIO device’s outputs toreset upon the SLC processor leaving Run mode (regardless ofthe RIO device’s Hold Last State setting), or while in Test modeby using words 24 – 27.

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

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

Important: The 1747-SN RIO Scanner does not use M0 words 0 – 7.

0123456789101112131415Bit Number

0110xxxxxxxxxxxxLogical Rack 0 Device Inhibit Word 8

0000xxxxxxxxxxxx

1001xxxxxxxxxxxx

1000xxxxxxxxxxxx

Logical Rack 1 Device Inhibit Word 9



0000xxxxxxxxxxxxLogical Rack 0 Device Reset Word 16

0000xxxxxxxxxxxx

0000xxxxxxxxxxxx

0000xxxxxxxxxxxx

Logical Rack 1 Device Reset Word 17



1001xxxxxxxxxxxxLogical Rack 0 Remote Output Reset Word 24

1000xxxxxxxxxxxx

0100xxxxxxxxxxxx

0100xxxxxxxxxxxx

Logical Rack 1 Remote Output Reset Word 25



M0 (Control) File - RIO Device Control Words

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

DeviceInhibitControl

DeviceResetControl

OutputResetControl

Important: Control functions (i.e., device inhibit, device reset, anddevice output reset) are only selectable for the primarydevice, but also apply to the complementary device.Control functions for complementary devices cannot beexclusively enabled.



M0 File - RIO Device Inhibit Control

M0 Words 8 through 11 – you use these words to command thescanner to stop scanning logical racks 0, 1, 2, and 3. Bits 0 – 3 ineach 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 thedevice to 1. Setting bits that do not correspond to the device logicalstarting group address will not inhibit the device. To resumescanning a device, reset the bit (which corresponds to the startinggroup address of the device) to 0.

Inhibiting a device does not affect the current settings of the DeviceFault Status (words 12 – 15 of the M1 file). Inhibited deviceseventually 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 scannerautomatically inhibits any device not configured in the Gfile (bit set to 1). Attempting to inhibit an unconfigureddevice has no effect.

M0 File

0110xxxxxxxxxxxxLogical Rack 0 Device Inhibit Word 8 M0:e.8

0000xxxxxxxxxxxx M0:e.9






0123456789101112131415Bit Number (decimal)

M0 (Control) File Words 8 through 11

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

Not Defined

Starting Group0246

Example of Device Inhibit Control

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

0123456789101112131415 M0 File



1001xxxxxxxxxxxx M0:e.101000xxxxxxxxxxxx M0:e.11

M0 (Control) File

RIO Logical Rack 0Starting Group

0246


0246


0246


0246

G File

1001111101100111Device Address, Word 1

Bit Number (decimal)Logical Rack 0 Device Inhibit Word 8







M0 File - RIO Device Reset Control

M0 Words 16 through 19 – you use these words to command areset (0) of RIO device outputs when the SLC processor is in Run orTest mode. This allows you to selectively reset logical deviceoutputs based on a previous condition(s) that you defined. Bits 0 – 3correspond 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 orTest mode), set the bit corresponding to the starting logical addressof the device to 1. Setting bits that do not correspond to a devicestarting address will not force a reset. To remove the reset condition,reset the bit (corresponding to the device logical starting address) to0. Refer to the mode table on page 4–20.

Default: The SLC processor resets all bits in this field to 0 when itenters Run or Test mode.

M0 File0123456789101112131415Bit Number (decimal)


Logical Rack 0 Device Reset Word 16 M0:e.160000xxxxxxxxxxxx M0:e.170000xxxxxxxxxxxx M0:e.180000xxxxxxxxxxxx M0:e.19





0000xxxxxxxxxxxx

Not Defined

Starting Group0246

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 defaultsetting for all device reset bits is 0.

0000xxxxxxxxxxxx

0000xxxxxxxxxxxx

0000xxxxxxxxxxxx

1000xxxxxxxxxxxx

0123456789101112131415M0 File

M0:e.16

M0:e.17

M0:e.18

M0:e.19

1 100100001000100Device Address, Word 1

G File

M0 (Control) FileBit Number (decimal)







0246


0246


0246


0246



M0 File - Remote Output Reset Control

M0 Words 24 through 27 – you use these words to command alogical device to reset all of its outputs when the SLC processorleaves 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 todetermine output operation when the SLC processor leaves the Runmode. Setting the bit to 1 will command all outputs off (regardlessof the device’s Hold Last State setting).

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

Default: When the processor enters Run or Test mode, the scannersets the starting address bit of each device configured inthe G file to 1.

!ATTENTION: The use of the device’s Hold LastState switch can result in its outputs remainingenergized when not under control of the SLCprocessor. We recommend the use of this function onlyby experienced SLC programmers.

M0 File0123456789101112131415Bit Number (decimal)


Logical Rack 0 Remote Output Reset Word 24 M0:e.24

M0:e.25

M0:e.26

M0:e.27





Not Defined

Starting Group0246

1001xxxxxxxxxxxx

1000xxxxxxxxxxxx

0100xxxxxxxxxxxx

0100xxxxxxxxxxxx



Example of Remote Output Reset Control

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

1001xxxxxxxxxxxx

1000xxxxxxxxxxxx

0100xxxxxxxxxxxx

0100xxxxxxxxxxxx

0123456789101112131415M0 File

M0:e.24

M0:e.25

M0:e.26

M0:e.27

1 100100001000100Device Address, Word 1

G File RIO Rack 0Starting Group

0246

RIO Rack 1Starting Group

0246


0246


0246

M0 (Control) FileBit Number (decimal)








The 1747-SN Scanner Device Reset words (M0:e.16 to M0:e.19) andthe Remote Output Reset words (M0:e.24 to M0:e.27) operate inconjunction with each RIO device to determine the state of that RIOdevice’s outputs. The output control information that the scannersends to the RIO device depends on how you configure these bits.The RIO device acts on the output control information in accordancewith its functionality and configuration. To fully understand how aspecific device responds to the Device Reset and Remote OutputReset words, you must determine the operation of the RIO device.To determine RIO device output operation, refer to that device’s usermanual.

!ATTENTION: When using the Device Reset andRemote Output Reset words, you must completelyunderstand and fully test all device output operationsbefore 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 devicesduring two SLC processor operating conditions:

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

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

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

If you modify the default settings, the Device Reset and RemoteOutput Reset words change. The table on the following pagecontains examples of what changes occur. We base the informationin the table on the assumption that the scanner’s slot is alwaysenabled and the RIO link device is communicating with the scanner.

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

Device Reset and RemoteOutput ResetConsiderations

Fro

m t

his

mo

de



Example 1 – When powering up into Run mode, the scanner, bydefault, resets the appropriate bit in the Device Reset word to 0. Theappropriate 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 theRemote Output Reset word have no effect on the RIO link device’soutputs. Setting the appropriate bits in the Device Reset Word to 1instructs the RIO link device to reset its outputs.

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

To this mode

Run Test Program

Power up DR = 0ROR = 1Default values are set automatically.Outputs reflect those of the scanneroutput image.

DR = XROR = X

Run ROR = X DR = 0 Outputs are unchanged. DR = 1 Outputs are turned OFF.

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

valid.


valid.

DR = X ROR = 1 These two combinations

will reset device outputs. DR = 1ROR = X



Test DR = 0ROR = 1Default values are set automatically.

Outputs reflect those of the scanneroutput image.


valid.

Once these outputs are reset, theyremain reset regardless of the DRand ROR settings.



Outputs remain unchanged.

Program DR = 0ROR = 1Default values are set automatically.Outputs reflect those of the scanneroutput image.

DR = 0ROR = 1These default values are setautomatically. Outputs are reset,unless ROR is changed to 0 on thefirst scan.

DR = XROR = X

DR = Device ResetROR=Remote Output ResetX = setting does not matter



M1 file words 0 through 47 contain the status of all devices on thescanner’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 devicefault 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 retrycounters

• Words 32–47 (M1:e.32–47) – complementary device retrycounters

General Communication Status - Enable Device Fault Bit

Word 0, bit 0 – is the Enabled Device Fault status bit. When anyenabled device is faulted, this bit is set to 1. A fault may be causedby a communication problem with a remote device.

0123456789101112131415

11xxxxxxxxxxxxxxGeneral Communication Status Word, Word 0 M1:e.0

M1 File

M1 (Status) File Word 0

Enabled DeviceFault Bit

Bit Number (decimal)

M1 Status File Description



General Communication Status - Communication Attempted Bit

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

Until this bit is set, all devices in M1 file word 10 (active devicestatus) appear to be inactive. This bit can be used to condition theEnabled Device Fault bit. If the Communications Attempted bit is 1,the Enabled Device Fault bit is valid.

0123456789101112131415

11xxxxxxxxxxxxxx M1:e.0

M1 File

CommunicationsAttemptedStatus Bit


M1 (Status) File Word 0

General Communication Status Word, Word 0

Enable DeviceFault Bit

RIO Baud Rate Status

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

0123456789101112131415

10xxxxxxxxxxxxxxRIO Baud Rate, Word 2

M1 File

M1:e.2

Baud Rate

M1 (Status) File - Word 2


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

Bit 1 - 0 Baud Rate SW 1 - 2

11 57.6 KBaud 11

01 115.2 KBaud 10

10 230.4 KBaud 01

00 230.4 KBaud 00



Logical Device Starting Address Status

Word 8 – provides status/feedback of the logical device startingaddresses you configured in word 1 of the G file (primary/normallogical devices). Writing to M1 file word 8 will not alter thecontents of the G file.

1

Primary Logical Device Address, Word 8 M1:e.8


1 100100001000100

G File - Word 1

1 10010000100000 Primary Logical Device Address, Word 1

0123456789101112131415M1 File


RIO Logical Rack 3Starting Group 2





Starting Group

0246

Starting Group

0246

Starting Group

0246

Starting Group

0246

Word 3 – provides status/feedback of the logical device startingaddresses you configured in word 3 of the G file (complementarydevices). Writing to M1 file word 3 will not alter the contents of theG file.

1


M1:e.3


1 100100001000100

G File - Word 3

1 10010000100000

0123456789101112131415M1 File







Starting Group

0246

Starting Group

0246

Starting Group

0246

Starting Group

0246Complementary Logical Device Address,

Word 3



Logical Device Image Size Status

Word 9 – provides status/feedback of the logical device image sizeyou configure in word 2 of the G file (primary/normal devices). Abit 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 Gfile.


0246


0246


0246


0246

0123456789101112131415M1 FilePrimary Logical Device Image Size, Word 9M1:e.9

G File - Word 2

Primary Logical Device Image Size, Word 2

M1 (Status) File - Word 9Bit Number (decimal)

1 100111101100111

1 100111101100111

Word 4 – provides status/feedback of the logical device image sizeyou configure in word 4 of the G file (complementary devices). Abit 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 Gfile.


0246


0246


0246


0246

0123456789101112131415M1 FileComplementary Logical Device Image Size, Word 4M1:e.4

G File - Word 4

Complementary Logical Device Image Size, Word 4

M1 (Status) File - Word 4Bit Number (decimal)

1 100111101100111

1 100111101100111

Active Device Status

Word 10 – provides active device status for primary/normal devices.When a RIO device is communicating with the scanner the bitcorresponding 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) arerepresented by a 0. Unless devices are inhibited, not responding tocommunications, or configured to an incorrect logical rack size, thisword is identical to the device configuration (M1:e.8).



0


0246


0246


0246


0246

0123456789101112131415

M1 File

Primary Logical Device Address, Word 8 M1:e.8

Primary Logical Image Size, Word 9 M1:e.9

Primary Active Device Status, Word 10 M1:e.10

1 100100001000100

101111101100111

1001100001000000

A 0 indicates that the device isinhibited, not responding tocommunications, or configured toan incorrect logical rack size.



A 1 indicates that the configureddevice is active.

Word 5 – provides active device status for complementary devices.When a RIO device is communicating with the scanner the bitcorresponding 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, orconfigured to an incorrect logical rack size, this word is identical tothe device configuration (M1:e.3).

Important: When a primary device is inhibited, its complementarydevice is also inhibited. A complementary devicecannot be exclusively inhibited.

0


0246


0246


0246


0246

0123456789101112131415

M1 File

Complementary Logical Device Address, Word 3 M1:e.3

Complementary Logical Image Size, Word 4 M1:e.4

Complementary Active Device Status, Word 5 M1:e.5

1 100100001000100

101111101100111

1001100001000000

A 0 indicates that the device isinhibited, not responding tocommunications, or configured toan incorrect logical rack size.



A 1 indicates that the configureddevice is active.



Logical Device Fault Status

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

0

0123456789101112131415

M1 File

Primary Device Address, Word 8 M1:e.8

Primary Device Size, Word 9 M1:e.9

Primary Active Device Status, Word 10 M1:e.10

M1 (Status) File Primary/Normal Device Fault Status

1 100100001000ÉÉ100

1001111101100ÉÉÉÉ

1ÉÉÉÉÉÉ

1ÉÉÉÉ

1

101100001000ÉÉÉÉ

000

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

xxxxxxxxxxxxLogical Rack 0 Device Fault Status Word 12 M1:e.12

xxxxxxxxxxxx M1:e.13



Logical Rack 1 Device Fault Status Word 13



000 0

000 0

000 0

ÉÉÉÉ

1ÉÉÉÉ

1ÉÉÉÉ

1 0


0246


0246


0246


0246



0

0123456789101112131415

M1 File

Complementary Device Address, Word 3 M1:e.3

Complementary Device Size, Word 4 M1:e.4


M1 (Status) File Complementary Device Fault Status

1 100100001000ÉÉ

100

1001111101100ÉÉÉÉ

1ÉÉÉÉÉÉ

1ÉÉÉÉ

1

101100001000ÉÉ000

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

0000xxxxxxxxLogical Rack 8 Device Fault Status Word 12 M1:e.12

0000xxxxxxxx M1:e.13


0ÉÉ1ÉÉ1ÉÉÉ1xxxxxxxx M1:e.15


Logical Rack 10 Device Fault Status Word 14Logical Rack11 Device Fault Status Word 15

xxx x

xxx x

xxx x

xxx x


0246


0246


0246


0246





RIO Status Example

The following example illustrates an M1 status file example. Itshows 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 deviceaddress) of the G file.

• M1:e.3 is an image of word 3 (complementary logical deviceaddress) of the G file.

• M1:e.9 is an image/copy of word 2 (primary/normal logicaldevice size) of the G file.

• M1:e.4 is an image/copy of word 4 (complementary logicaldevice 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 EnabledDevice 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 EnabledDevice 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, whichcorrespond 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, whichcorrespond 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.

0123456789101112131415

11xxxxxxxxxxxxxx

RIO LogicalRack 0

Status Word, Word 0

RIO LogicalRack 1

RIO LogicalRack 2

RIO LogicalRack 3

10xxxxxxxxxxxxxxBaud Rate, Word 2

M1:e.0

M1 File

M1:e.2

M1:e.8

M1:e.9

M1:e.10





M1 (Status) File Primary/Normal

1 100100001000100

1001111101100111

1001100001000000

000 0

000 0

000 0

111 0

1 100100001000100

1001111101100111


0246

Primary Logical Device Address, Word 1

Primary Logical Image Size, Word 2


G File



0246


0246


0246

Primary Device Address, Word 8

Primary Device Size, Word 9

Primary Active Device Status, Word 10







0123456789101112131415

11xxxxxxxxxxxxxx

RIO LogicalRack 8

Status Word, Word 0

RIO LogicalRack 9

RIO LogicalRack 10

RIO LogicalRack 11

10xxxxxxxxxxxxxxBaud Rate, Word 2

M1:e.0M1 File

M1:e.2

Complementary Device Starting Address, Word 3 M1:e.3

Complementary Device Image Size, Word 4 M1:e.4


0000xxxxxxxxLogical Rack 8 Device Fault Status Word 12 M1:e.12







M1 (Status) File Complementary

1 100100001000100

1001111101100111

1001100001000000

xxx x

xxx x

xxx x

xxx x

1 100100001000100

1001111101100111


0246

Complementary Logical Device Address, Word 3

Complementary Logical Image Size, Word 4


G File



0246


0246


0246

Important: Individual quarter logical racks within a device cannotbe faulted. Therefore, only the starting logical group ofthe device needs to be monitored.



M1 File Status Words 16 through 47 – indicate how many RIOcommunication retries the scanner makes to each adapter on the RIOlink if communication problems occur. Each word (16–47) containsa retry counter for each configured quarter logical rack (words 16–31are for primary logical racks, 0–3, and 32–47 are for complementaryracks, 8–11). Retry counters are useful for troubleshootingcommunication problems (such as electrical noise or poorcommunication line connections) between the scanner and anyadapters. The scanner clears the retry counters when going fromProgram to Run mode, Test to Run mode, and when going fromProgram to Test mode. Note that the display (in words M1:e.16 –31)of retry counters corresponds to the bits set in the Primary LogicalDevice Address – Word 1 of the G file. Likewise, the display (inwords M1:e.32–47) correspond to the bits set in the ComplementaryLogical Device Address – Word 3 of the G file.

Important: Your SLC control program cannot initialize/clear retrycounters.

Retry Counter Example for Primary Devices

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

ÇÇ0

0123456789101112131415

ÉÉ101ÉÉ10000ÇÇ1001ÉÉÉ001

Bit Number

Primary Logical Device Address, Word 1

G File - Primary

Specifies RIOaddresses forprimary logicaldevices.


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




ÇÇÇÇ

0

0123456789101112131415

ÉÉÉÉ

100ÉÉÉÉ

10001ÇÇÇÇ

0001ÉÉÉÉÉÉ

100

Bit Number


G File - Complementary

Specifies RIOaddresses forcomplementary devices.


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




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

RIO Communication RetryCounter (M1:e.16 � 47)



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

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

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




M1:e.44 – communication retry counter for RIO logical rack 11,group 0M1:e.45 – communication retry counter for RIO logical rack 11,group 2M1:e.46 – not used in this exampleM1:e.47 – not used in this example



This section provides information about:

• 2-slot addressing

• 1-slot addressing

• 1/2-slot addressing

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

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

2�SlotAddressing

Two slots are addressed as one logical group.

1�SlotAddressing

One slot is addressed as one logical group.

1/2�SlotAddressing

One slot is addressed as two logical groups.

Slot 1

Slot 1

Slot 1Slot 2

Slot 1

Slot 1

Slot 1Slot 2

Input Image

Input Image

Input Image

Output Image

Output Image

Output Image

Remote Chassis

Remote Chassis

Remote Chassis

07815 07815

07815 07815

07815 07815

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

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

Understanding SlotAddressing



Your SLC processor can be programmed with an HHT➀ (Hand-HeldTerminal) or APS (Advanced Programming Software). Although theconfiguration steps are similar, they are not identical. Therefore, thefollowing basic steps are provided. For specific instructions, refer tothe user manual included with your programming device. For moreinformation on M and G files, refer to appendix B.

1. Locate an open slot in your SLC chassis. Remember that youmust use an SLC 5/02 or later processor.

2. Assign the scanner to a physical slot in the SLC processor’schassis by selecting Scanner from the list. If the scannerselection is not available, select OTHER from the I/OConfiguration Screen and enter the Code ID number: 13608.

3. Enter the number of Scanned Input and Output Words using theSpecialty I/O and Advanced Setup menus.

The default value is 32 I/O words. You can specify less than 32and reduce the processor scan time by transferring only the partof 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 M0file sizes to 32 words (48 words if using complementary I/O).32 words is the minimum required for operation. If you do notset the M1 and M0 file sizes to at least 32 words theprogramming device will not allow you to access the M files inthe SLC control program.

If you are using the block transfer (BT) function, you should setthe M1 and M0 file sizes to 3,300. Refer to chapter 5 beforecompleting this selection.

5. Set the G file size to 3 (5 if using complementary I/O) using theSpecialty 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 rightstarting at slot 1, regardless of the module type.SLC 5/03 and later processors scan slots with discreteI/O modules first, left to right starting at slot 1, and thenslots with specialty modules, left to right starting at slot1.

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

SLC/ScannerConfiguration

Chapter 5


RIO Block Transfer

This chapter contains the following information:

• RIO block transfer theory of operation

• RIO block transfer general functional overview

• scanner’s block transfer buffer layout

• detailed operation of RIO block transfer

• RIO block transfer application considerations

• steps for setting up a block transfer

• quick reference for using status and control bits

• block transfer control logic examples

This section provides a conceptual overview of block transfer as itpertains to SLCs, RIO scanners, and remote devices. For specificfunctionality details, refer to the RIO Block Transfer GeneralFunctional Overview section on page 5–5.

What Is RIO Block Transfer?

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

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

RIO Block Transfer Theoryof Operation

5–2 RIO Block Transfer


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

RIOScanner

SLC Processor ➀

I/O Image

M Files

Chassis Backplane

RIO Link

= path of a Block Transfer (BT)

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

Refer to the diagrams on the following pagesfor more details on BTR and BTW sequence ofoperation.

Block Transfer Write (BTW) data travels from the SLC processoracross the chassis backplane via the scanner's M files. The scannerthen sends the data across the RIO link to the adapter or intelligent I/Omodule.

Block Transfer Read (BTR) data travels from the adapter or intelligentI/O module over the RIO link to the scanner. The chassis backplanethen transfers BTR data via the scanner's M files to the SLCprocessor. The SLC control program processes the data once theSLC receives it from the scanner.

➀ SLC 5/02 processor or above

Adapter or Intelligent I/O Module

MFiles

5–3RIO Block Transfer


�

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

1747 RIO Scanner

I/O Image

Chassis Backplane


RIO Link

= path of the BTR

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


ÉÉÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉ

ÇÇÇÇ


ÇÇÇÇ

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

ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


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

�

�

�

�

�

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.

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

M1 file

M0 file

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 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 processes the BTR information.

One byte is consumed from theinput and output image file for�handshake" purposes.

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

Word 24Word 23

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

Group 7

Slot 0

Slot 1

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

�

Slot 0

Slot 1

SLC Processor ➀

➀ SLC 5/02 processor or later

MFiles



�

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

I/O Image

Chassis Backplane

RIO Link

= path of the BTW

RIO Block Transfer Theory of Operation - 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.

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

M1 file

M0 file

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.

1747 RIO Scanner



ÉÉÉÉÉÉÉÉÉ

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

ÉÉÉÉÉÉÉÉ

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

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

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


One byte is consumed from theinput and output image file for�handshake" purposes.

Group 0Group 1

Group 2Group 3

Group 4Group 5

Group 6Group 7Group 0Group 1

Word 24Word 23

Group 0Group 1

Group 2Group 3

Group 4Group 5

Group 6Group 7

Group 7

Slot 0

Slot 1

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


Slot 0

Slot 1

SLC Processor ➀

➀ SLC 5/02 processor or later

MFiles



The RIO scanner performs block transfers through control/statusbuffers that you allocate in the scanner’s M0 and M1 files. ForBTWs, the M0 BT buffer contains BTW control data and BTW data,while a corresponding M1 BT buffer contains only BTW statusinformation. For BTRs, the M0 BT buffer contains only BTRcontrol data, while a corresponding M1 BT buffer contains BTRstatus information and BTR data. Block transfers occurasynchronous to RIO link discrete transfers. Note that blocktransfers occur as RIO scan time allows – discrete I/O transfers havefirst priority.

A total of 32 block transfer control/status buffers exist in the M0(output/control) and the M1 (input/status) files. Block transferbuffers 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 inan M1 file

BT buffers reside on 100 word boundaries in theM0/M1 files starting at word 100. For example, BTbuffer 1 resides at M0:e.100 and M1:e.100; BT buffer2 resides at M0:e.200 and M1:e.200; while BT buffer16 resides at M0:e.1600 and M1:e.1600. Note thatthe �e" in these examples refers to the physicalchassis slot number in which the scanner resides.

You use an M0 file BT control buffer to initiatea BT. The corresponding M1 file displays thestatus of the block transfer.

M0:e.100

Words100...109

3 words forcontrol and7 reserved

64 words forBT WriteData

M1:e.100

4 words for status and 6reserved

64 words forBT ReadData

M0:e.3200

Words3200...3209

3 words forcontrol and7 reserved

64 words forBT WriteData

M1:e.3200

4 words for status and 6reserved

64 words forBT ReadData

M0 Control Buffers 1 . . . 32

M1 Status Buffers 1 . . . 32 All block transfer buffers (M0 and M1) are cleared(set to zero) either when the RIO scanner goesthrough a power cycle or when the SLC processorcommands the scanner to change mode fromProgram to Test mode, Program to Run mode, orTest to Run mode.

Words110...173

Words3210...3273

Words100...109

Words3200...3209

Words110...173

Words3210...3273

RIO Block TransferGeneral FunctionalOverview



Scanner I/O Image Allocation For Block Transfer

Block transfer operations (BTR and BTW) consume only one byte ofthe RIO scanner’s I/O image file, independent of what type of I/Oslot addressing is used. This one byte image is reserved forcommunication “handshake” purposes between the remote device(adapter or intelligent I/O module) and the scanner. SLC controlprograms must never read/write to these image locations becauseunpredictable operations may result.

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

Examples of BT I/O Image File Allocation


ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉ


ÉÉÉÉ


ÉÉÉÉ

ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


The minimum portion of the scanner'simage that can be assigned to an adapteris 1/4 logical rack. Each logical devicethat you assign BT operations (BTR orBTW) consumes one byte from thescanner'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 onlyapplies for 2 slot addressing.

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

Word 24Word 23


Group 7

Logical Slot 0

Logical Slot 1

Note that the logical address of your RIOdevices (i.e., adapter and intelligent I/Omodules) determine where the blocktransfer gets mapped.

1747�SN RIO Scanner's I/O Image Files

In this example there are two block transferoperations mapped to the scanner' s I/Oimage. One BT operation is mapped toLogical Rack 0, Logical Group 4, LogicalSlot 1. The other is mapped to LogicalRack 3, Logical Group 4, Logical Slot 0.

Example 1




ÉÉÉÉÉÉ

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

ÉÉÉÉÉÉÉÉÉ

ÉÉÉ


ÉÉÉÉ

ÇÇÇÇÇÇÇÇ

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

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

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

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3

Input Image Output ImageGroup 0Group 1Group 2Group 3Group 4Group 5Group 6Group 7Group 0Group 1

Word 24Word 23


Group 7

Logical Slot 0

Logical Slot 1

# 1 # 2 # 3 # 4

These are all analog modulesthat are assigned block transfer operations.

I/OImage

Adapter

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


# 1# 1 # 2# 2# 3# 3 # 4# 4




ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉ

ÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇ


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇ

ÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


Word 24Word 23


Group 7

Logical Slot 0

Logical Slot 1

# 1 # 2 # 3 # 4

These are discrete modules.Module #2 is an 8 point outputmodule and module #4 is an 8point input module.

I/OImage

Adapter

In this example, the remote adapter is using 2�slot addressing. It is assigned 1/4 logical rack of the scanner's I/O image files starting atRIO Logical Rack 3, Logical Group 4. The remote adapter controls two analog devices, which are configured for block transfer operationsand two discrete devices (8 point input and 8 point output). Note that each analog module uses both the input and output byte of thelogical slot to which it is assigned, while the discrete modules use only the input or output byte.


# 1# 1 # 2not used

# 3# 3# 4

These are analog modules thatare assigned block transfer operations.

not used

Example 2

Example 3

Mod. Mod. Mod. Mod.

Mod. Mod. Mod. Mod.

Modules' �handshake" bytesmap to these I/O imageaddresses.

Modules' �handshake" bytesmap to these I/O image ad�dresses.



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 BTWoutput data. The following explains the layout of BT buffer 1.

Important: The general layout below of buffer 1 is the same for all32 M0 BT buffers. The “e” in the examples refers tothe physical chassis slot number in which the scannerresides. Remember that buffers start on 100 wordboundaries.

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

M0:e.101 – Used to configure BTR/BTW length information (0 to64). Length is the number of BTR/BTW words read from or writtento the end device. If length = 0, then the RIO device will inform theSLC processor as to how much data to transfer. The M0/M1 BTbuffers cannot overflow because they each reserve 64 words of dataarea.

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

Which Slot Number To UseWhen your adapter is configured for 2�slot addressing, 0 is the left slot and 1 is the right slot. For both 1�slot and 1/2 �slot addressing the slot number is al�ways 0.

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

Example M0:e.102 Configurations

Logical Rack 0, Group 0, Slot 0 = 0




The first number(reading fromright to left) is the�Slot Number."Leading 0s need notbe entered.



ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉÉÉ

ÉÉÉÉÉÉ

ÉÉÉÉÉÉ

ÇÇÇ

ÇÇÇÇÇÇÇÇÇ

ÇÇÇÇ

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


ÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


Word 24Word 23


Group 7

Logical Slot 0 (Low Byte)

Logical Slot 1(High Byte)

M0:e.102 Logical Address Example

Scanner's Block TransferBuffer Layout



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 BTbuffers. Buffer 1 = M0:e.100... buffer 32 = M0:e.3200.

BT Control Buffer Function M0 Address where x = buffer # from 1 to 32

Control Flags - See Control Flag

Definitions table below.

M0:e.x00

BT Length - 0 through 64 M0:e.x01

BT Address (logical rack, group, and

slot)

M0:e.x02

Reserved M0:e.x03 through M0:e. x09

BTW Data Locations 0 through 63 M0:e.x10 through M0:e.x73

BT Control Flag Definitions

Definition Control flags where x = buffer # from 1 to 32

These bits are reserved. M0:e.x00/0 through M0:e.x00/6

Type of BT operation (1 = BTR and

0 = BTW) ➀

M0:e.x00/7

Block Transfer Timeout (TO) = 1 =

Cancel the BT operation. ➁

M0:e.x00/8

These bits are reserved. M0:e.x00/9 through M0:e.x00/14

Block Transfer Enable (EN) = 1 =

Enable the BT operation. ➂

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.



M1 File - Block Transfer Input/Status Buffers

There are 32 BT status buffers allocated in the M1 file. These buffersindicate the status for all BTR and BTW operations and also containBTR input data. Below is the layout of BT buffer 1.

Important: The layout below is the same for all 32 M1 file BTbuffers.

M1:e.100 – Status flags that describe the status of the BTR andBTW operations. Status flags are described in detail on thefollowing page.

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

M1:e.102 – Contains the logical address you have selected in theM0:e.102 file in rack, group, and slot number format. The logicalrack, group, and slot are combined into one word.

Which Slot Number To UseWhen your adapter is configured for 2�slot addressing, 0 isthe left slot and 1 is the right slot. For both 1�slot and 1/2 �slot addressing the slot number isalways 0.

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

Example M1:e.102 Configurations Logical Rack 0, Group 0, Slot 0 = 0




The first number(reading fromright to left) is the�Slot Number."

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


ÉÉÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉ

ÇÇÇÇ


ÇÇÇÇ


ÇÇÇÇÇÇÇÇ


ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

ÇÇÇÇÇÇÇÇ

Word 8Word 9

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Word 26Word 27

Word 25

Word 30

Word 28Word 29

Word 31

LogicalRack 3


Word 24Word 23


Group 7

Logical Slot 0 (Low Byte)

Logical Slot 1(High Byte)

M1:e.102 Logical Address Example

M1:e.103 – The BTR/BTW error code. Refer to the M1 File ErrorCodes 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.



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

M0 Address for

BT buffer 1

...M0 Address for

BT buffer 32

Status Flags - Refer to the status

flags table on the following page.

M1:e.x00 M1:e.100 ...M1:e.3200

Actual Length Status- Number of

words that were transferred during BT.

M1:e.x01 M1:e.101 ...M1:e.3201

Logical Address Status - logical rack,

group, and slot

M1:e.x02 M1:e.102 ...M1:e.3202

Block Transfer error code - Refer to

the Error Codes table below.

M1:e.x03 M1:e.103 ...M1:e.3203

Reserved M1:e.x04 through

M1:e.x09

M1:e.104 through

M1:e.109

...M1:e.3204

through

M1:e.3209

BTR Data Locations 0 through 63 M1:e.x10 through

M1:e.x73

M1:e.110 through

M1:e.173

...M1:e.3210

through

M1:e.3273

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

Error Code Description

- 0 The BT completed successfully.

- 6 Illegal BT length requested.

- 7 BT communication error occurred when BT request was initiated.

- 8 Error in BT protocol.

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

- 10 No RIO channel configured.

- 11 Attempted a BT either to a non�configured 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.

- 12 Attempted a BT to an inhibited device.



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

Status Flag Description

M1:e.100/0 through

M1:e.100/9

These bits are reserved.

M1:e.100/10 Block Transfer Enabled and Waiting for block transfer to start -

(EW = Enable Waiting) ➀

M1:e.100/11 This bit is reserved.

M1:e.100/12 Block Transfer Error - (ER = Error) ➁

M1:e.100/13 Block Transfer Successful - (DN = Done) ➂

M1:e.100/14 Block Transfer Started - (ST = Started) ➃

M1:e.100/15 This bit is reserved.

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



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

This section describes step-by-step how the RIO scanner usesM0/M1 files to accomplish block transfer operations. The stepsbelow are based on the following assumptions:

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

• No pending BT operation utilizing a particular M0 output/controland 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 flagoperation follow this section.

1. You set up a BTR or BTW by filling in control information(about block transfer length, logical rack, logical group, andlogical slot address) in an M0 output/control buffer. If you wantto set up a BTW, then you must place your write data in the BTWdata area of the M0 output control buffer. You set up M0 bufferinformation in an integer file and a COP instruction copies theinformation into the M0 output control file.

2. Your SLC control program initiates a BTR/BTW operation byfilling 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 = BTWand 1 = BTR). Your SLC control program also sets the EN (Enable) flag(M0:e.100/15) which signals the RIO scanner that a new blocktransfer operation is to begin.

3. The scanner processes the BTR/BTW when it detects that theSLC control program has set the EN flag.

If the RIO scanner detects any problem at this point (such asinvalid BT control field, or unconfigured device) the M1 inputstatus buffer’s error code field fills in and the ER (Error) flag inthe status field sets. If no problems occur, the EW (EnableWaiting) flag and ST (Start) flag set in the status field. (Note thatthe ST flag will not set if the scanner is already in the process ofblock transferring data to a location within the same logical rack.The ST flag will set only after any previous pending BTs to thesame logical rack have been completed and the BT request hasbeen scheduled on the RIO link.)

Detailed Operation of RIOBlock Transfer



Your SLC control program can monitor the block transfer byexamining the M1 status flags. They indicate when the scannerhas started processing (EW and ST flags) the BT and whether theBT operation completed successfully (DN flag) or failed (ERflag). Your SLC control program takes different actions based onthese status flags.

4. If the BT completes successfully, the scanner fills in the M1 BTlength status field. If it was a BTW operation, the BTR data areaof the M1 BT buffer is not updated. If it was a BTR operation, thenew BTR input data (based on length) is placed in the BTR dataarea of the M1 BT buffer and the unused buffer area clears. TheDN status flag then sets to indicate to the SLC control programthat the BT operation completed successfully and that the M1input 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 theproblem type. The ER flag sets to indicate to the SLC controlprogram that the BT operation was unsuccessful.

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

7. When the RIO scanner detects that the EN flag has been clearedby the SLC control program, it then clears the EW, ST and DN orER flags. This ensures that the status flags in the M1 input statusbuffer 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 clearsthe status flags. These fields are only updated when the scannerhas processed a BT operation as indicated by the DN or ER flag.For example, if there was a problem with a BT operation, theerror code will remain in the M1 BT buffer until the next BToperation causes it to be changed (cleared if DN is set or an errorcode if ER is set). Therefore, the SLC control program shouldprecede the examination of the error code field with the ER flag.

Block Transfer Timing Diagrams

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



M0 Control Information

M1 Status Information

EN

Successful Block Transfer

DN

ER

TO

Status Flag

�

�

�

�

�

Control Flag

EW

�

ST

�

�

Successful Block Transfer Read/Write

This example illustrates a successful BT operation.

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

� The scanner detects that the EN flag is set, validates the controlinformation, puts the BT request on the RIO link successfully,and since no other BTs are pending for the same logical rack, setsthe enable waiting (EW) and start (ST) flag in M1 status field.

� The scanner receives a BT reply (with no errors) from the RIOlink device, fills in any requested BTR data, and sets the done(DN) flag.

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

� The scanner detects that the SLC control program has completedprocessing (because the EN flag is clear) and clears the EW, STand DN flags. At this point the SLC control program couldinitiate another BT operation in the same M0 BT buffer by settingthe EN flag.



�



EN

DN

ER

TO

Status Flag

�Control Flag

EW

Block Transfer Failure at Startup

�

ST �

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

� The SLC control program fills in the M0 BT buffer and sets theEN flag.

� The scanner detects that the EN flag is set, determines that thereis some invalid information in the M0 control buffer, fills in theM1 BT buffer status error code field, and sets the ER flag.

� The SLC control program detects the ER flag, examines the M1BT status buffer error code, and clears the EN flag afterprocessing the error.

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

Note that in this example the EW and ST flags never set. Also, theSLC control program must clear the EN flag in order to start a newBT after the error has been corrected.





EN

Block Transfer Failure After Startup of Transmission Across RIO Link

DN

ER

TO

Status Flag

�

�

�

�

�

Control Flag

EW�

ST

�

�

Block Transfer Failure after Startup of Transmission Across the RIO

Link

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

� The SLC control program fills in the M0 BT output/control bufferand 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 EWand ST flags in the M1 BT input status buffer.

� The scanner receives a BT reply (with some error) from the RIOlink 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 M1BT buffer error code, and clears the EN flag after processing theerror.

� The scanner detects that the SLC control program has processedthe reply in the M1 BT buffer and clears the EW, ST and ERflags.



�



EN

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

DN

ER

TO

Status Flag �

�

�

�

Control Flag

EW�

ST

�

�

�

SLC Control Program Canceling a BT Once Transmitted Across RIO

Link

This example illustrates an SLC control program cancelling a BToperation.

� In this example, the SLC control program wants a BT timeoutvalue less than the four second default value that the scanner uses.When the SLC control program detects that the ST flag has set, atimer in the SLC control program starts.

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

� The scanner fills in the error code field and sets the ER flag. TheSLC control program must still clear the EN flag to complete theBT operation. Note that because of the asynchronous nature ofcancelling a transmission to a device that has a BT in progress,the BT reply may indicate either a successful completion or anerror.

� The SLC control program clears the TO and EN flags. Note thatif the SLC control program later attempts to initiate another BTand the TO flag is still set, the scanner will ignore the BTrequest.

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





EN

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

DN

ER

TO

Status Flag

�

�

�

�

�

Control Flag

EW��

ST

�

�

SLC Control Program Canceling a BT Prior to Transmission Across

RIO Link

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

� When the SLC control program detects that the EW has set, atimer in the SLC control program starts.

� If the timer expires before the scanner begins transmitting acrossthe RIO link (ST = 1), then the SLC control program will set theTO flag. Note that the cancellation will not occur until allpreviously scheduled BTs to the same logical rack have beencompleted (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 tothat device have been completed. The SLC control program mustclear the EN flag to complete the BT operation. Note thatbecause of the asynchronous nature of cancelling a device thathas a BT in progress, the BT reply may indicate either asuccessful completion or an error.

� The SLC control program clears the TO and EN flags. Note thatif the SLC control program later attempts to initiate another BTand the TO flag is still set, the scanner will ignore the BTrequest.

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



Below are points to consider when implementing BT operations:

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

• If a BT device is a 1747-ASB RIO Adapter, then multiple SLC500 modules (such as analog modules) could be scanned by the1747-ASB and the data block transferred to the RIO scanner.Since the RIO network handles one BT request per logical rack ata time, there will be a delay before all devices in the 1747-ASBrack can be accessed. Therefore you should only perform BTs asnecessary (i.e., “on demand”).

• Inhibiting a device on the RIO network (via control wordsM0:e.8...11) precludes that device from block transfer operations.Attempting to initiate a BT to an inhibited device results in anerror reply. The scanner will cancel a BT that is in progress if itdetects that the device is inhibited. Because of the asynchronousnature of inhibiting a device that has a BT in progress, the BTreply may indicate either a successful completion or an error. Ineither case, the SLC control program must still clear the Enableflag.

• All M0 and M1 BT buffers are cleared (set to all zeros) after apower cycle and when the SLC processor goes from Program toRun mode, Program to Test mode, or Test to Run mode.

When using complementary I/O, if you configure a complementarydevice to use more I/O image space than an associated primarydevice, then block transfers can only be performed to locations in thecomplementary device that have associated I/O image space in theprimary device. For example, if a primary device is 1/2 logical rackand a complementary device is a full logical rack, block transfers canbe performed only in the first 1/2 logical rack of the complementarydevice. Attempting block transfers in the last half of thecomplementary device will result in a BT error (error – 11 – devicenot configured).

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0




ÉÉÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉ

078150717 10Bit Number Octal

LogicalRack 8




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


ÉÉÉÉÉÉÉÉ


ÉÉÉÉÉÉÉÉ

Complementary I/O ImagePrimary I/O Image

Word 7

Word 5Word 6

Word 3Word 4

Word 1Word 2

Word 0

LogicalRack 0

Bit Number Decimal 078150717 10Bit Number Octal

Bit Number Decimal

1/2 logical rackconfigured andusable

1/2 logical rack notconfigured

1/2 logical rackconfigured and usable

1/2 logical rackconfigured, but notusable for BT sinceWords 4-7 are notconfigured for theprimary device.

RIO Block TransferApplicationConsiderations



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

1. To use the BT functionality, you must increase the size of the M0and M1 files in an offline APS session. The size depends on thenumber of BT buffers your applications requires. Note thatsetting the buffers to maximum size (3300) will not affect systemperformance. However, addressing M-files in your SLC controlprogram does affect system performance.

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

If You Want to Transfer

Data:

Use:

To the scanner from the

adapter

BTR (Block Transfer Read)

From the scanner to the

adapter

BTW (Block Transfer Write)

If You Want to specify a: Do this to the M0:e.x00/7 file :

BTR (Block Transfer Read) Set the bit to 1 to specify a read operation

BTW (Block Transfer Write) Set the bit to 0 to specify a write operation.

3. Specify the length of the data you wish to block transfer in wordM0:e.x01. Note that maximum length is 64 words.

4. Specify the device’s logical rack, group, and slot in wordM0:e.x02.

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

Setting Up a BlockTransfer



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

Status Bits

This Bit: Is Set:

Enable Waiting EW -

M1:e.x00/10

upon the scanner's first detection of EN being set. The EW

bit gets reset when the EN flag resets.

Error ER - M1:e.x00/12 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:

Read�Write RW -

M0:e.x00/7

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.

Enable EN -

M0:e.x00/15

by your SLC control program to initiate a BT request.

Quick Reference to Statusand Control Bits



The following pages contain generic BTR and BTW control logicexamples. Refer to chapter 7, Application Examples for specificproduct applications using BT examples.

Block Transfer Read Control Logic Example

Rung 2:0CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BITB3: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:1COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THEPROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAMSCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE ISSCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS ANDTHEREFORE 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| || | | |Dest #B3:0| || | | |Length 4| || | | +––––––––––––––––––+ || | CHECK BTR | || | STATUS | || | UNTIL DN | || | OR ER BIT | || | IS OFF | || | B3:5 | || +––––] [–––––+ || 1 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH THE ENABLEBIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE BIT BEFORE ANOTHER BTRTO 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 |

BTR and BTW ControlLogic Examples



Rung 2:3WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BT DATA AND UNLATCH THE BT ENABLEBIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUESCHECKING 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| | || | |Dest #N7:10| | || | |Length 64| | || | +––––––––––––––––––+ | || | 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:4IF 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 CHECKINGTHE 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| | || | |Dest B3:4| | || | | 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 |



Rung 2:5WHEN USER LOGIC INITIATES A NEW BTR, LATCH THE ENABLE BIT , AS LONG AS A BTR ISNOT IN PROGRESS. ALSO, LATCH THE BTR PENDING BIT , SO THE BTR STATUS FILE WILLBE READ BY THE LADDER PROGRAM.| | | | SERVICE || USER LOGIC| | | THE BTR || TO |VIRTUAL |VIRTUAL |VIRTUAL STATUS/ || INITIATE A|BT ENABLE |BTR DONE |BTR ERROR BTR || 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:6MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHENEVER ATRANSITION OF THE BTR ENABLE BIT OCCURS.| || || VIRTUAL || BT ENABLE || BIT || B3:100 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source B3:100| || | | | 0000000000000000| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | 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:0CONFIGURE THE BTW LENGTH AND RIO ADDRESS AT POWER–UP. ALSO, BE SURE THE BLOCKTRANSFER OPERATION BIT IS A ”0” INDICATING A BTW. ALL THESE PARAMETERS MUST BEENTERED 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| || +––––––––––––––––––+ |



Rung 2:1COPY THE BTW STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THEPROGRAM, ONLY WHEN A BTW IS PENDING. THIS AVOIDS ACCESSING THE M1 FILE MULTIPLETIMES DURING EACH PROGRAM SCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILEBIT, WORD OR FILE IS SCANNED BY THE PROCESSOR,AN IMMEDIATE DATA TRANSFER TOTHE 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| || | | |Dest #B3:0| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | CHECK BTW | || | STATUS | || | UNTIL DONE | || | BIT IS OFF | || | B3:5 | || +––––] [–––––+ || 1 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW ISCOMPLETE, THE DONE BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCH THE ENABLEBIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE BIT BEFORE ANOTHER BTWTO 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 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 1 || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | B3:0 | || +––––]/[–––––+ || 12 |Rung 2:3WHEN A BTW SUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT. ALSO, UNLATCHTHE BTW PENDING BIT AND LATCH THE BIT THAT CONTINUES CHECKING THE BTW STATUSUNTIL 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 |



Rung 2:4IF A BTW ERRORS, UNLATCH THE ENABLE BIT, THE BTW PENDING BIT AND BUFFER THE BTWERROR CODE. ALSO, LATCH THE BIT THAT CONTINUES CHECKING THE BTW STATUS UNTILTHE SN MODULE TURNS OFF THE ERROR BIT.| || || VIRTUAL || BTW ERROR BUFFER BTW || BIT ERROR CODE || B3:0 +MOV–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|| 12 | |Source B3:3| | || | | 0000000000000000| | || | |Dest B3:4| | || | | 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:5WHEN USER LOGIC INITIATES A NEW BTW, COPY THE DATA TO THE M0 FILE DATA AREAAND 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 THELADDER PROGRAM.| | | | || USER LOGIC| | | || TO |VIRTUAL |VIRTUAL |VIRTUAL || INITIATE A|BTW ENABLE|BTW DONE |BTW ERROR || 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| | || | |Dest #M0:1.110| | || | |Length 64| | || | +––––––––––––––––––+ | || | SERVICE | || | THE BTW | || | STATUS/ | || | BTW | || | PENDING | || | B3:5 | || +––––(L)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTW ENABLE | || | BIT | || | B3:100 | || +––––(L)–––––––––––––––+ || 15 |



Rung 2:6MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHENEVER ATRANSITION OF THE BTW ENABLE BIT OCCURS.| || || VIRTUAL || BTW ENABLE || BIT || B3:100 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source B3:100| || | | | 0000000000000000| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTW DONE | || | BIT | || | B3:0 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | B3:0 | || +––––] [–––––+ || 12 |Rung 2:7| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |



Directional Continuous Block Transfer Example

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

Rung 2:0CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BITB3: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:1COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THEPROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAMSCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE ISSCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS ANDTHEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 80 | |Source #M1:1.100| || | | |Dest #B3:0| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 81 |Rung 2:2WHEN THE ERROR OR DONE BIT IS SET INDICATING THAT THE BTR COMPLETED EITHERUNSUCCESSFULLY OR SUCCESSFULLY, THE ENABLE BIT MUST BE UNLATCHED BY THE LADDERPROGRAM. THE 1747–SN SCANNER THEN UNLATCHES THE ERROR/DONE BIT TO COMPLETE THEBLOCK TRANSFER HAND–SHAKE PROCESS. AT THIS TIME THE ”CHECK BTR STATUS” BITMUST BE UNLATCHED TO AVOID UNNECESSARY M–FILE ACCESSES.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || B3 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 81 || | | || | | || | | || | | || | VIRTUAL | || | BT ERROR | || | BIT | || | B3 | || +––––]/[–––––+ || 12 |



Rung 2:3WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTRENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUESCHECKING 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| | || | |Dest #N7:10| | || | |Length 64| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 80 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | B3 | || +––––(U)–––––––––––––––+ || | 1615 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 81 |Rung 2:4WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BRENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT INORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL ITTURNS THE ERROR BIT OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL || BT ERROR BTR ERROR || BIT CODE || B3 +MOV–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|| 12 | |Source M1:1.103| | || | | *| | || | |Dest N7:9| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 80 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | B3 | || +––––(U)–––––––––––––––+ || | 1615 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 81 |



Rung 2:5BLOCK TRANSFER READS WILL EXECUTE CONTINUOUSLY AS LONG AS THE BTR PRECONDITIONBIT IS TRUE.| | | | || | | | || BTR PRE– |VIRTUAL |VIRTUAL |VIRTUAL || CONDITION |BTR ENABLE|BTR DONE |BT ERROR BTR || BIT |BIT |BIT |BIT PENDING || B3 B3 B3 B3 B3 ||––––] [––––––––]/[––––––––]/[––––––––]/[–––––––––––––––––––––––+––––(L)–––––+–|| 83 1615 13 12 | 80 | || | | || | | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | B3 | || +––––(L)–––––+ || 1615 |Rung 2:6MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR ISIN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS AREALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL BTR || BTR ENABLE CONTROL || BIT WORD || B3 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 1615 | |Source B3:100| || | | | 0000000000000000| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTR DONE | || | BIT | || | B3 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BT ERROR | || | BIT | || | B3 | || +––––] [–––––+ || 12 |Rung 2:7| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |



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 aspossible. Use the same method for a BTW.

Rung 2:0CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BITB3: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:1COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THEPROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAMSCAN. EACH TIME AN INSTRUCTION CONTAINING AN M–FILE BIT, WORD OR FILE ISSCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS ANDTHEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 80 | |Source #M1:1.100| || | | |Dest #B3:0| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 81 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BITBEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONECOMPLETE BTR CYCLE.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || B3 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 81 || | | || | | || | | || | | || | VIRTUAL | || | BT ERROR | || | BIT | || | B3 | || +––––]/[–––––+ || 12 |



Rung 2:3WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTRENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUESCHECKING 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| | || | |Dest #N7:10| | || | |Length 64| | || | +––––––––––––––––––+ | || | | || | | || | | || | 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| | || | | *| | || | |Dest N7:9| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 80 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | B3 | || +––––(U)–––––––––––––––+ || | 1615 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 81 |



Rung 2:5BLOCK TRANSFER READS WILL REPEAT AS FAST AS POSSIBLE AS LONG AS THESE RUNGSARE 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:6MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR ISIN PROGRESS AND CONTINUE DOING SO UNTIL THE SCANNER TURNS THE DONE/ERROR BITOFF.| || || VIRTUAL || BTR ENABLE || BIT || B3 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 1615 | |Source B3:100| || | | | 0000000000000000| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTR DONE | | | | BIT | || | B3 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BT ERROR | || | BIT | || | B3 | || +––––] [–––––+ || 12 |Rung 2:7| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |



Directional Non�Continuous Block Transfer Example

The following rungs demonstrate a directional non-continuous blocktransfer. The block transfer executes once for every false-to-truetransition of the input. Please note that the input bit I:2.0/0 waschosen randomly for this example and can be any address in yourprogram used to initiate a BTR. Also note that this same methodmay be used for a BTW.

Rung 2:0CONFIGURE THE BTR OPERATION TYPE, LENGTH AND RIO ADDRESS AT POWER–UP. BITB3: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:1COPY THE BTR STATUS AREA TO A BINARY FILE WHICH WILL BE USED THROUGHOUT THEPROGRAM. THIS AVOIDS ADDRESSING THE M1 FILE MULTIPLE TIMES DURING EACH PROGRAMSCAN. EACH TIME AN INSTRUCTION CONTAINING AN M1 FILE BIT, WORD OR FILE ISSCANNED BY THE PROCESSOR, AN IMMEDIATE DATA TRANSFER TO THE MODULE OCCURS ANDTHEREFORE WILL IMPACT THE OVERALL PROCESSOR SCAN TIME.| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 80 | |Source #M1:1.100| || | | |Dest #B3:0| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 81 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BITBEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONECOMPLETE BTR CYCLE.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || B3 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 81 || | | || | | || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | B3 | || +––––]/[–––––+ || 12 |



Rung 2:3WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH THE BTRENABLE BIT. ALSO, UNLATCH THE BTR PENDING BIT AND LATCH THE BIT THAT CONTINUESCHECKING 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| | || | |Dest #N7:10| | || | |Length 64| | || | +––––––––––––––––––+ | || | | || | | || | | || | 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| | || | | *| | || | |Dest N7:9| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 80 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | B3 | || +––––(U)–––––––––––––––+ || | 1615 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 81 |



Rung 2:5INITIATE 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:6WHEN USER LOGIC INITIATES A NEW BTR, LATCH THE ENABLE BIT AS LONG AS A BTR ISNOT IN PROGRESS. ALSO, LATCH THE BTR PENDING BIT SO THE BTR STATUS FILE WILL BEREAD 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:7MOVE THE VIRTUAL CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTR ISIN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITS AREALL TURNED OFF, COMPLETING THE BTR HAND–SHAKE PROCESS.| || || VIRTUAL BTR || BTR ENABLE CONTROL || BIT WORD || B3 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 1615 | |Source B3:100| || | | | 0000000000000000| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTR DONE | || | BIT | || | B3 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | B3 | || +––––] [–––––+ || 12 |Rung 2:8| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |



Bidirectional Continuous Block Transfer Example

The following rungs demonstrate a bidirectional continuous blocktransfer. The BTR and BTW will each execute as fast as possible,continuously and independently of one another.

Rung 2:0CONFIGURE THE BT OPERATION TYPE, LENGTH AND RIO ADDRESS (R,G,S IN DECIMAL) ATPOWER–UP. BIT N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND BIT N7:53/7MUST BE A LOGICAL ”0” TO INDICATE A BTW OPERATION.| || || || POWER–UP BTR || BIT CONTROL || S:1 +COP–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|| 15 | |Source #N7:50| | || | |Dest #M0:1.100| | || | |Length 3| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTW | || | CONTROL | || | +COP–––––––––––––––+ | || +–+COPY FILE +–+ || |Source #N7:53| || |Dest #M0:1.200| || |Length 3| || +––––––––––––––––––+ |Rung 2:1COPY 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 LIMITTHE NUMBER OF M–FILE ACCESSES.| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 0 | |Source #M1:1.100| || | | |Dest #N7:60| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 2 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BITBEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONECOMPLETE BTR CYCLE.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || N7:60 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 2 || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | N7:60 | || +––––]/[–––––+ || 12 |



Rung 2:3COPY 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 THENUMBER OF M–FILE ACCESSES.| || || || BTW BTW || PENDING STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 1 | |Source #M1:1.200| || | | |Dest #N7:64| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTW | || | STATUS | || | B3 | || +––––] [–––––+ || 3 |Rung 2:4UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BITBEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETESONE BTW CYCLE.| || || VIRTUAL || BTW DONE CHECK BTW || BIT STATUS || N7:64 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 3 || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––]/[–––––+ || 12 |



Rung 2:5WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH BOTH THEBTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE BIT THATCONTINUES 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| | || | |Dest #N7:0| | || | |Length 10| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 2 |Rung 2:6WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTRENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT INORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL ITTURNS 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| | || | | *| | || | |Dest N7:0| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 2 |



Rung 2:7WHEN A BTW SUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BIT AND THE BTWPENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THAT CONTINUESCHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE BIT OFF.| || || VIRTUAL || BTW DONE BTW || BIT PENDING || N7:64 B3 ||––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––+––––(U)–––––+–|| 13 | 1 | || | | || | | || | VIRTUAL | || | BTW ENABLE | || | BIT | || | N7:53 | || +––––(U)–––––+ || | 15 | || | | || | | || | | || | CHECK BTW | || | STATUS | || | B3 | || +––––(L)–––––+ || 3 |Rung 2:8WHEN A BTW UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTWENABLE BIT AND THE BTW PENDING BIT. ALSO, LATCH THE CHECK BTW STATUS BIT INORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL ITTURNS 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| | || | | *| | || | |Dest N7:1| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTW | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 1 | || | | || | | || | | || | | || | | || | VIRTUAL | || | BTW ENABLE | || | BIT | || | N7:53 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | CHECK BTW | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 3 |



Rung 2:9THIS 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 ||––––]/[––––––––]/[––––––––]/[––––––––––––––––––––––––––––––––––+––––(L)–––––+–|| 15 13 12 | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(L)–––––+ || 15 |Rung 2:10THIS 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| | || | |Dest #M0:1.210| | || | |Length 11| | || | +––––––––––––––––––+ | || | | | | | | || | | || | | || | | || | VIRTUAL | || | BTW ENABLE | || | BIT | || | N7:53 | || +––––(L)–––––––––––––––+ || | 15 | || | | || | | || | | || | BTW | || | PENDING | || | B3 | || +––––(L)–––––––––––––––+ || 1 |Rung 2:11MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTRIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE , DONE AND ERROR BITSARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL BTR || BTR ENABLE CONTROL || BIT BITS || N7:50 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:50| || | | | 0| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTR DONE | || | BIT | || | N7:60 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | N7:60 | || +––––] [–––––+ || 12 |



Rung 2:12MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTWIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITSARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL BTW || BTW ENABLE CONTROL || BIT BITS || N7:53 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:53| || | | | 0| || | | |Dest M0:1.200| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTW DONE | || | BIT | || | N7:64 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––] [–––––+ || 12 |Rung 2:13| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |

Bidirectional Alternating Block Transfer

The following rungs demonstrate a bidirectional alternating blocktransfer. Using these rungs ensures the block transfer requests areexecuted in the order in which they are sent to the queue. Thisexample also ensures that the block transfer read and block transferwrite alternate. The XIO conditions prevent the BTR and BTW fromqueueing simultaneously. The block transfers continue as long as theXIC precondition bit is true.

Rung 2:0CONFIGURE THE BT OPERATION TYPE, LENGTH, AND RIO ADDRESS (R,G,S IN DECIMAL) ATPOWER–UP. N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND N7:53/7 MUST BEA LOGICAL ”0” TO INDICATE A BTW OPERATION.| || || || POWER–UP BTR || BIT CONTROL || S:1 +COP–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|| 15 | |Source #N7:50| | || | |Dest #M0:1.100| | || | |Length 3| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTW | || | CONTROL | || | +COP–––––––––––––––+ | || +–+COPY FILE +–+ || |Source #N7:53| || |Dest #M0:1.200| || |Length 3| || +––––––––––––––––––+ |



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 THENUMBER OF M–FILE ACCESSES.| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 0 | |Source #M1:1.100| || | | |Dest #N7:60| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 2 |Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BITBEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONECOMPLETE BTR CYCLE.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || N7:60 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 2 || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | N7:60 | || +––––]/[–––––+ || 12 |Rung 2:3COPY 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 THENUMBER OF M–FILE ACCESSES.| || || || BTW BTW || PENDING STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 1 | |Source #M1:1.200| || | | |Dest #N7:64| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTW | || | STATUS | || | B3 | || +––––] [–––––+ || 3 |



Rung 2:4UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BITBEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETESONE BTW CYCLE.| || || VIRTUAL || BTW DONE CHECK BTW || BIT STATUS || N7:64 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 3 || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––]/[–––––+ || 12 |Rung 2:5WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH BOTH THEBTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE BIT THATCONTINUES 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| | || | |Dest #N7:0| | || | |Length 10| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ |



Rung 2:6WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE BTR ERROR CODE AND UNLATCH THEBTR ENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BITIN ORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL ITTURNS 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| | || | | *| | || | |Dest N7:21| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 2 |Rung 2:7WHEN A BTW SUCCESSFULLY OR UNSUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BITAND THE BTW PENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THATCONTINUES CHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE/ERROR BITOFF.| || || VIRTUAL || BTW DONE BTW || BIT PENDING || N7:64 B3 ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––+––––(U)–––––––––––––––+–|| | 13 | | 1 | || | | | | || | | | | || | VIRTUAL | | VIRTUAL | || | BTW ERROR | | BTW ENABLE | || | 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:8THIS RUNG AND THE NEXT RUNG WILL TOGGLE BETWEEN EXECUTING A BTR AND A BTWWHILE THE USER SUPPLIED BT PRECONDITION BIT (B3:0/11 IS USED IN THIS EXAMPLE)IS TRUE.| | | | | || | | | | || BT |VIRTUAL |VIRTUAL |VIRTUAL |VIRTUAL || PRECON– |BTR ENABLE|BTW ENABLE|BTR DONE |BTR ERROR BTR || 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| | | | | || BT |VIRTUAL |VIRTUAL |VIRTUAL |VIRTUAL || PRECON– |BTR ENABLE|BTW ENABLE|BTW DONE |BTW ERROR || 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| | || | |Dest #M0:1.210| | || | |Length 11| | || | +––––––––––––––––––+ | || | | || | | || | | || | | || | VIRTUAL | | | | BTW ENABLE | || | BIT | || | N7:53 | | | +––––(L)–––––––––––––––+ || | 15 | || | | || | | || | | || | BTW | || | PENDING | || | B3 | || +––––(L)–––––––––––––––+ || 1 |



Rung 2:10MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTRIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITSARE ALL TURNED OFF.| || || VIRTUAL BTR || BTR ENABLE CONTROL || BIT BITS || N7:50 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:50| || | | | 0| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTR DONE | || | BIT | || | N7:60 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTR ERROR | || | BIT | || | N7:60 | || +––––] [–––––+ || 12 |Rung 2:11MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTWIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITSARE ALL TURNED OFF.| || || VIRTUAL BTW || BTW ENABLE CONTROL || BIT BITS || N7:53 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:53| || | | | 0| || | | |Dest M0:1.200| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTW DONE | || | BIT | || | N7:64 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––] [–––––+ || 12 |Rung 2:12| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |



Bidirectional Alternating Repeating Block Transfer

The following rungs demonstrate a bidirectional alternatingrepeating block transfer. Using these rungs ensures the blocktransfer requests are executed in the order in which they are sent tothe queue. This example also ensures that the BTR and BTWrepeatedly alternate. The XIO conditions prevent the BTR and BTWfrom queuing simultaneously. The BT’s continue as long as theladder rungs are scanned.

Rung 2:0CONFIGURE THE BT OPERATION TYPE, LENGTH AND RIO ADDRESS (R,G,S IN DECIMAL) ATPOWER–UP. BIT N7:50/7 MUST BE SET TO A ”1” TO INDICATE A BTR AND N7:53/7 MUSTBE A LOGICAL ”0” TO INDICATE A BTW OPERATION.| || || || POWER–UP BTR || BIT CONTROL || S:1 +COP–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|| 15 | |Source #N7:50| | || | |Dest #M0:1.100| | || | |Length 3| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTW | || | OPERATION | || | +COP–––––––––––––––+ | || +–+COPY FILE +–+ || |Source #N7:53| || |Dest #M0:1.200| || |Length 3| || +––––––––––––––––––+ |Rung 2:1COPY 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 THENUMBER OF M–FILE ACCESSES| || || || BTR || PENDING BTR STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 0 | |Source #M1:1.100| || | | |Dest #N7:60| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––] [–––––+ || 2 |



Rung 2:2UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTR STATUS. WHEN A BTR ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE DONE/ERROR BITBEFORE ANOTHER BTR TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS IS ONECOMPLETE BTR CYCLE.| || || VIRTUAL || BTR DONE CHECK BTR || BIT STATUS || N7:60 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 2 || | | || | | || | | || | BTR ERROR | || | BIT | || | N7:60 | || +––––]/[–––––+ || 12 |Rung 2:3COPY 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 THENUMBER OF M–FILE ACCESSES.| || || || BTW BTW || PENDING STATUS || B3 +COP–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+COPY FILE +–|| | 1 | |Source #M1:1.200| || | | |Dest #N7:64| || | | |Length 4| || | | +––––––––––––––––––+ || | | || | | || | | || | CHECK BTW | || | STATUS | || | B3 | || +––––] [–––––+ || 3 |Rung 2:4UNLATCH THE BIT THAT CONTINUES TO CHECK THE BTW STATUS. WHEN A BTW ISCOMPLETE, THE DONE OR ERROR BIT IS SET. THE LADDER PROGRAM MUST THEN UNLATCHTHE ENABLE BIT, THEN WAIT FOR THE SN MODULE TO TURN OFF THE THE DONE/ERROR BITBEFORE ANOTHER BTW TO THE SAME M–FILE LOCATION CAN BE INITIATED. THIS COMPLETESONE BTW CYCLE.| || || VIRTUAL || BTW DONE CHECK BTW || BIT STATUS || N7:64 B3 ||–+––––]/[–––––+–––––––––––––––––––––––––––––––––––––––––––––––––––––––(U)–––––|| | 13 | 3 || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––]/[–––––+ || 12 |



Rung 2:5WHEN A BTR SUCCESSFULLY COMPLETES, BUFFER THE BTR DATA AND UNLATCH BOTH THEBTR VIRTUAL ENABLE BIT AND THE BTR PENDING BIT . ALSO, LATCH THE BIT THATCONTINUES 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| | || | |Dest #N7:0| | || | |Length 10| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 2 |Rung 2:6WHEN A BTR UNSUCCESSFULLY COMPLETES, BUFFER THE ERROR CODE AND UNLATCH THE BTRENABLE BIT AND THE BTR PENDING BIT. ALSO, LATCH THE CHECK BTR STATUS BIT INORDER TO CONTINUE READING THE STATUS INFORMATION FROM THE SCANNER UNTIL ITTURNS THE ERROR BIT OFF, COMPLETING THE HAND–SHAKE PROCESS. | || || BTR ERROR || BIT || N7:60 +MOV–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+MOVE +–+–|| 12 | |Source M1:1.103| | || | | *| | || | |Dest N7:21| | || | | 0| | || | +––––––––––––––––––+ | || | | || | | || | | || | BTR | || | PENDING | || | B3 | || +––––(U)–––––––––––––––+ || | 0 | || | | || | | || | VIRTUAL | || | BTR ENABLE | || | BIT | || | N7:50 | || +––––(U)–––––––––––––––+ || | 15 | || | | || | | || | | || | CHECK BTR | || | STATUS | || | B3 | || +––––(L)–––––––––––––––+ || 2 |



Rung 2:7WHEN A BTW SUCCESSFULLY OR UNSUCCESSFULLY COMPLETES, UNLATCH THE BTW ENABLE BITAND THE BTW PENDING BIT TO COMPLETE A BTW SEQUENCE. ALSO, LATCH THE BIT THATCONTINUES CHECKING THE BTW STATUS UNTIL THE SN MODULE TURNS THE DONE/ERROR BITOFF. IN ADDITION, BUFFER THE BTW ERROR CODE IN CASE AN ERROR OCCURS.| || || VIRTUAL || BTW DONE BTW || BIT PENDING || N7:64 B3 ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––+––––(U)–––––––––––––––+–|| | 13 | | 1 | || | | | | || | | | | || | VIRTUAL | | VIRTUAL | || | BTW ERROR | | BTW ENABLE | || | 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:8THIS RUNG AND THE NEXT RUNG WILL TOGGLE BETWEEN EXECUTING A BTR AND A BTW.| | | | || | | | || VIRTUAL |VIRTUAL |VIRTUAL | || BTR ENABLE|BTW ENABLE|BTR DONE |BTR ERROR BTR || 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 |



Rung 2:9| | | | || | | | || VIRTUAL |VIRTUAL |VIRTUAL |VIRTUAL || BTR ENABLE|BTW ENABLE|BTW DONE |BTW ERROR || BIT |BIT |BIT |BIT BTW DATA || N7:50 N7:53 N7:64 N7:64 +COP–––––––––––––––+ ||––––]/[––––––––]/[––––––––]/[––––––––]/[–––––––––––––+–+COPY FILE +–+–|| 15 15 13 12 | |Source #N7:10| | || | |Dest #M0:1.210| | || | |Length 11| | || | +––––––––––––––––––+ | || | | || | | || | VIRTUAL | || | BTW ENABLE | || | BIT | || | N7:53 | || +––––(L)–––––––––––––––+ || | 15 | || | | || | | || | | || | BTW | || | PENDING | || | B3 | || +––––(L)–––––––––––––––+ || 1 |Rung 2:10MOVE THE VIRTUAL BTR CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTRIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITSARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL BTR || BTR ENABLE CONTROL || BIT WORD || N7:50 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:50| || | | | 0| || | | |Dest M0:1.100| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | | || | | || | VIRTUAL | || | BTR DONE | || | BIT | || | N7:60 | || +––––] [–––––+ || | 13 | || | | || | | || | | || | BTR ERROR | || | BIT | || | N7:60 | || +––––] [–––––+ || 12 |



Rung 2:11MOVE THE VIRTUAL BTW CONTROL WORD TO THE M0 FILE FOR THE SN MODULE WHILE A BTRIS IN PROGRESS, AND CONTINUE DOING SO UNTIL THE ENABLE, DONE AND ERROR BITSARE ALL TURNED OFF, COMPLETING THE HAND–SHAKE PROCESS.| || || VIRTUAL BTW || BTW ENABLE CONTROL || BIT WORD || N7:53 +MOV–––––––––––––––+ ||–+––––] [–––––+––––––––––––––––––––––––––––––––––––––––––+MOVE +–|| | 15 | |Source N7:53| || | | | 0| || | | |Dest M0:1.200| || | | | *| || | | +––––––––––––––––––+ || | | || | | || | VIRTUAL | || | BTW DONE | || | BIT | || | N7:64 | || +––––] [–––––+ || | 13 | || | | || | | || | VIRTUAL | || | BTW ERROR | || | BIT | || | N7:64 | || +––––] [–––––+ || 12 |Rung 2:12| ||–––––––––––––––––––––––––––––––––––––+END+––––––––––––––––––––––––––––––––––––|| |

Chapter 7


Application Examples

This chapter provides application examples for systems configuredwith 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 todisplay stored messages. An alarm is connected to an output modulein case communications with the RediPANEL is lost. The systemconsists 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

RIO Network

Alarm

RediPANEL

RediPANEL KeypadModule

7–2 Application Examples


As shown in the G file below, the RediPANEL is configured as a halfrack device beginning at rack 0, group 0.

0 100000000000000

1100000000000000


0246


0246


0246


0246

Device Address, Word 1

Device Size, Word 2

G File

The scanner input file is shown below. The output file is similar, it isaddressed O:1.0 to O:1.3.

Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number 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.30

I:1.31

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

I:1.15I: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

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Rack 0

Rack 1

Rack 2

Rack 3

RediPANEL

0818283848586878108118128138148158168178Bit Number (octal)= not used

7–3Application 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 Configurationfunction. The M0 and M1 file sizes are set to 32 in the Advanced SetUp function.

Since only the first 4 words of the input and output files containvalid information, the scanned input and output words can be set to4. Reducing the number of scanned input and output wordsdecreases your SLC scan time.

Configuration information is entered in the Modify G File function.Word 0 is reserved, and therefore, cannot be modified. Word 1indicates the starting address of the device; word 2 indicates its size.

Example Program

The example program is shown below. Each time a function key ispressed 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.

MEQ( )

2

O:2

END

] [

I:1.0

8

] [

I:1.0

If the Communications attempted andEnabled Device Fault bits are set to 1,

activate the alarm.

If function key 1 is pressed (bit 8 ofinput word 0), T4:0 Preset is moved

to the display.

When a new number is enteredonto the RediPANEL, it is moved to

preset T4:0.

MOVMOVESource T4:0.PREDest O:1.1

MOVMOVESource I:1.1Dest T4:0.PRE

] [

I:1.0If function key 2 is pressed (bit 9 of

input word 0), RediPANEL message#2 is triggered and displayed.

MOVMOVESource 2Dest O:1.2

14

9

MASKED EQUALSource M1:1.0Mask 0003Compare 3



In this example, a Bulletin 2705 RediPANEL and a Catalog Number1747-DCM are connected to the RIO network. This combinationforms a distributed control system consisting of two SLC processorsmonitored from a single operator interface device.

The system consists of:

• Catalog Number 1747-L524 processor (SLC 5/02) in slot 0 of thefirst SLC controller

• Catalog Number 1747-SN (RIO Scanner) in slot 1 of the firstSLC controller

• Bulletin 2705 RediPANEL

• Catalog Number 1747-L511 processor (SLC 5/01�) in slot 0 ofthe second SLC controller

• Catalog Number 1747-DCM in slot 1 of the second SLCcontroller

RIO NetworkRediPANEL SLC 5/01 Processor

DCM (Direct CommunicationsModule)

SLC 5/02 Processor

RIO Scanner

Controller 1

Controller 2

RediPANEL/DCM



As shown in the G file (of controller 1) below, the RediPANEL isconfigured as a three quarter rack device beginning at rack 0, startinggroup 0. The Catalog Number 1747-DCM is configured as a halfrack device beginning at rack 1, starting group 0.

0 100100000000000

1110110000000000


0246


0246


0246


0246


Device Size, Word 2

G File

The scanner input file is shown below. The output file is similar, it isaddressed O:1.0 to O:1.5 for the RediPANEL and O:1.8 to O:1.11 forthe DCM.

Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Rack 0

Rack 1

Rack 2

Rack 3

RediPANEL

DCM

0818283848586878108118128138148158168178Bit Number (octal)

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

I:1.31

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

= not used







Configuration information is entered in the Modify G File function.Word 0 is reserved and, therefore, cannot be modified. Word 1indicates the starting address of the device; word 2 indicates its size.

Example Program

The example program is shown on the following page. Duringnormal 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 theDCM to select a message to be displayed on the RediPANEL. Bit 8of the RediPANEL input word 0 (I:1.0/8) activates bit 1 of the DCMoutput word 2 (O:1.10/1).

Upon the scanner’s first scan, the application program copies the M1file to integer file N7. The contents of the M1 file can then bemonitored by performing a data monitor of the N7 file. The baudrate (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 theinteger file upon each scan.

The program monitors the active device status bits that aretransferred to the integer file. If the RediPANEL is not active, theDCM is forced to a reset by setting the device reset bit (M0:1.17). Ifthe DCM is not active, an error message (message #4) is displayedon the RediPANEL by moving 4 to output word 2 (O:1.2).

The active device status bits are conditioned with the communicationattempted bit (M1:1.1) before any fault actions are taken. Thisensures that the scanner has attempted to communicate with allconfigured devices before an inactive device is considered faulted.



N7:0

1( )

0

M0:1.17

END

] [

S:1

Move input word 10 (I:1.10) from the DCMto output word 2 (O:1.2) of the RediPANEL.

MOVMOVESource I:1.10Dest O:1.2

MOVMOVESource M1:1.2Dest N7:1

] [

I:1.0

8( )

1

O:1.10



Bit 8 of the RediPANEL input word 0activates bit 1 of the DCM output word 2.

Upon the first processor scan, move thebaud rate setting, device address, and

device size to integer file N7.



N7:4

0


Move the active device status andgeneral status words to integer file N7

upon each scan.

If communications is attempted and theRediPANEL is not communicating, reset

the DCM.

If communications is attempted and theDCM is not communicating, display

message 4 on the RediPANEL.

15

N7:4

4

N7:0

1



In the following example, a DL40 Dataliner is used to display astored message containing an accumulator value when certaincounting conditions are met. In addition, the Dataliner displays analarm message that must be acknowledged with the [MSG ACK]

button located on its front panel when conveyor alarm conditionsexist.

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

RIO Network

RIO Scanner

Dataliner Message Display

SLC 5/02 Processor

Dataliner



As shown in the G file below, the Dataliner is configured as a halfrack device beginning at rack 1, starting group 0.

0 000100000000000

0000110000000000


0246


0246


0246


0246


Device Size, Word 2

G File


Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Rack 0

Rack 1

Rack 2

Rack 3

Dataliner

0818283848586878108118128138148158168178Bit Number (octal)

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

I:1.31

I:1.15I: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

= not used








Example Program

( )0

B3

END

Cycle

Message 1 is triggered by moving thevalue 1 to output module group 0 of the

Dataliner.

This also updates an embedded variable inmessage 1 by moving the accumulatedvalue of counter C5:0 to output module

group 1 of the Dataliner.


MOVMOVESource C5:0.ACCDest O:1.9

I:1.8

13

Conveyor

OSR MOVMOVESource 2Dest O:1.8

CountingConditions

AlarmConditions

( )0

B3

OTL

OTU

EQUEQUALSource A I:1.9Source B 2

If alarm conditions go from false to true,trigger message 2 by sending the value 2to output module group 0 of the Dataliner.

If B3/0 is ON, message 2 has not beenacknowledged.

If the Dataliner input module group 1 isequal to 2 (message 2 is presently

displayed) and the [MSG ACK] button ispressed (I:1.8/13), unlatch the Alarm Not

Acknowledged bit (B3/0).



In the following example, a Catalog Number 2711-KC1 PanelViewterminal is used to control a pump and display its ON/OFF status andpressure. The pump is connected to an output module and a pressuregauge 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

RIO Scanner

PanelView Operator Terminal

Pump

Pressure GaugeOutput Module

Analog Input Module

SLC 5/02 Processor

PanelView



As shown in the G file below, the PanelView terminal is configuredas a one and three quarter device beginning at rack 2, starting group0. The scanner addresses the PanelView terminal as if it were twodevices, one full rack and another three quarter rack.

0 000000010001000

0000000011111110


0246


0246


0246


0246


Device Size, Word 2

G File


Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Rack 0

Rack 1

Rack 2

Rack 3

PanelView

0818283848586878108118128138148158168178Bit Number (octal)

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

I:1.31

I:1.15I: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

= not used








Example Program

( )1

O:1.16

END

MOVMOVESource I:3.0Dest O:1.17

ON button

] [0

OFF button

I:1.16

O:2

0 1

I:1.16( )

0

O:2Pump

0

O:2

Pump ONConditions

If the ON push button is pressed, turn thepump on. If the OFF pushbutton is

pressed, turn the pump off.

When the pump is on, display the pressurefrom the pressure gauge on the PanelView

terminal Numeric Value Display.

When the pump is on, display the ON stateof the multi�state indicator on the

PanelView.



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 SLCprocessor as well as display the analog value on a meter at theremote 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 chassishas only 1/4 logical rack of I/O image space remaining (due toother RIO devices on this RIO link)

• needs 16 discrete inputs and 16 discrete outputs at this sameremote 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 withonly 1/4 logical rack of the I/O image available

With only 1/4 logical rack image to work with, the remote systemconsists 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 itsimage size to 1/4 logical rack. The discrete modules use the entireimage for logical rack 3, group 6 in a complementary slot pairarrangement and the combination analog module uses the image forlogical rack 3, group 7. This image size for the analog module is 1input and 1 output word short of what is required by the NIO4Imodule. Therefore, block transfer to/from the analog module will beused (BT operations only require one input and one output byte). Inthe future, the other analog input and output on the 1747-NIO4I maybe used.


The technician addresses the 1747-ASB to logical rack 3, startinglogical group 6. Since the analog module’s image (2 input/outputwords) will not fit into one logical group (1 input/output word), hemust use block transfer to read analog input values and write toanalog outputs. In this example, the SLC processor will receive theanalog input data via BTR, scale it, and send it to the analog outputvia a BTW.

Block Transfer ApplicationExample



As shown in the G file below, the 1747-ASB consumes 1/4 logicalrack of the scanner’s I/O image table beginning at logical rack 3,starting at group 6.

0 10010001000100ÉÉÉÉ

1

111111111111111ÉÉ1


0246


0246


0246


0246


Device Size, Word 2

G File

The scanner input file is shown below.

Rack 3 Group 6

Rack 3 Group 7

Rack 1 Group 2

Rack 1 Group 3

Rack 1 Group 0

Rack 1 Group 1

Rack 1 Group 6

Rack 1 Group 4

Rack 1 Group 5

Rack 0 Group 6

Rack 0 Group 7

Rack 0 Group 4

Rack 0 Group 5

Rack 0 Group 2

Rack 0 Group 3

0123456789101112131415Bit Number

Word 0

Word 1

Word 2

Word 3

Word 4

Word 7

Word 8

Word 9

Word 10

Word 11

Word 12

Word 13

Word 14

Word 5Word 6

Word 30

Word 31

Rack 0 Group 0

Rack 0 Group 1

Rack 3 Group 1

Rack 3 Group 2

Rack 2 Group 7

Rack 3 Group 0

Rack 3 Group 5

Rack 3 Group 3

Rack 3 Group 4

Rack 2 Group 5

Rack 2 Group 6

Rack 2 Group 3

Rack 2 Group 4

Rack 2 Group 1

Rack 2 Group 2

Word 15Word 16

Word 17

Word 18

Word 19

Word 22

Word 23

Word 24

Word 25

Word 26

Word 27

Word 28

Word 29

Word 20Word 21


Rack 0

Rack 1

Rack 2

Rack 3

1746�NIO4Ialso usesO:1.31

0818283848586878108118128138148158168178Bit Number (octal)

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

I:1.31

I:1.15I: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

= used by other devices

IV16 - OV16uses O:1.30



System Layout Diagram

RIO Scanner

SLC 5/03 Processor

NIO4I

IV16 Module

OV16 Module

1747-ASB

RIO Link

Output

Input

4 to 20 mA Transducer

4 to 20 mA AnalogMeter

(0 to 100%)

To Other RIODevices

Local System

Remote System

0 100

Example Program

The following program samples the analog input data from the1746-NIO4I module located in the remote I/O chassis every 100 msby executing a BTR every 100 ms. This data is then scaled for the4 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 to100% scale. Refer to the system layout diagram above. Also referto the analog module user manual, Catalog Number 1746-6.4 fordetails on analog input and output ranges as well as scaling.

Important: The following block transfer program example accessesmultiple M-file addresses throughout the program. Thisincreases the SLC processor scan time. If processorscan time is a concern, please refer to the block transferprogram examples in chapter 5 instead. Theseexamples manage the M-file addresses more efficiently.



Rung 2:0Configure the BTR and BTW length and RIO address at power–up. Also, set the blocktransfer operation bit for BTR operation only.| || || || POWER–UP BTR || BIT CONTROL || S:1 +COP–––––––––––––––+ ||––––] [––––––––––––––––––––––––––––––––––––––––––––––+–+COPY FILE +–+–|| 15 | |Source #N7:50| | || | |Dest #M0:1.101| | || | |Length 2| | || | +––––––––––––––––––+ | || | BT | || | OPERATION | || | BIT | || | M0:1.100 | || +––––(L)–––––––––––––––+ || | 7 | || | BTW | || | CONTROL | || | +COP–––––––––––––––+ | || +–+COPY FILE +–+ || |Source #N7:52| || |Dest #M0:1.201| || |Length 2| || +––––––––––––––––––+ |

Rung 2:1Copy the BTR status area to an integer file only when a BTR is in progress. Thisstatus data will then be used throughout the program and will limit the number ofM–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:2Copy the BTW status area to an integer file only when a BTW is in progress. Thisstatus data will then be used throughout the program and will limit the number ofM–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| || +––––––––––––––––––+ |



Rung 2:3When a BTR successfully completes, buffer the block transfer data and unlatch boththe BTR enable bit and the BTR pending bit. The data in this example is fromanalog 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| | || | |Dest #N7:10| | || | |Length 2| | || | +––––––––––––––––––+ | || | 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:4When a BTW successfully completes, unlatch the BTW enable bit and the BTW pendingbit to complete a BTW sequence.| SERVICE || THE BTW || VIRTUAL STATUS/ || BTW DONE BTW || BIT PENDING || N7:64 B3:0 ||––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––+––––(U)–––––+–|| 13 | 1 | || | | || | | || | | || | BTW ENABLE | || | BIT | || | M0:1.200 | || +––––(U)–––––+ || 15 |



Rung 2:5If 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 thecause of the error.| SERVICE || THE BTR || STATUS/ || BTR ERROR BTR || BIT PENDING || N7:60 B3:0 ||––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––+––––(U)–––––+–|| 12 | 0 | || | | || | | || | | || | BTR ENABLE | || | BIT | || | M0:1.100 | || +––––(U)–––––+ || 15 |

Rung 2:6If 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 thecause of the error.| || || || BTW ERROR BTW ENABLE || BIT BIT || N7:64 M0:1.200 ||––––] [––––––––––––––––––––––––––––––––––––––––––––––––––––––––+––––(U)–––––+–|| 12 | 15 | || | | || | | || | SERVICE | || | THE BTW | || | STATUS/ | || | BTW | || | PENDING | || | B3:0 | || +––––(U)–––––+ || 1 |

Rung 2:7Free–running timer to execute a BTR to the analog input in Logical Rack 3, Group 7left 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:8Initiate a BTR every 100ms as long as a BTR is not in progress. A complete cyclerequires that when complete or error, the ladder program unlatches the enable bitand the scanner then unlatches the done bit. A new BTR must not be initiated untilthese 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 |



Rung 2:9This rung checks the analog input data (4–20MA input) to ensure that it is within the proper rangeand turns on outputs for under and over range. If the value is within range it is scaled to the4–20MA analog output range and is then placed into the BTW data area. The BTW enable bit and pendingbits are then latched to initiate the BTW to the analog combination module, output 0. Output 0 isconnected 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| | || | |Source B 3277| | || | | | | || | +––––––––––––––––––+ | || | | || | | || | | || | ABOVE | || | RANGE FLAG | || | +GRT–––––––––––––––+ O:2.0 | || +–+GREATER THAN +–––––––––––––––––––––––––––––––––––––––––––––––––––––––––(L)–––––+ || | |Source A N7:10| 1 | || | | 0| | || | |Source B 16384| | || | | | | || | +––––––––––––––––––+ | || | +LIM–––––––––––––––+ +SCL–––––––––––––––+ | || +–+LIMIT TEST +–+–––––––––––––––––––––––––––––––+SCALE +–+––––––––––+ || |Low Lim 3277| | |Source N7:10| | || | | | | 0| | || |Test N7:10| | |Rate [/10000] 5250| | || | 0| | | | | || |High Lim 16384| | |Offset 4522| | || | | | | | | || +––––––––––––––––––+ | |Dest M0:1.210| | || | | *| | || | +––––––––––––––––––+ | || | | SERVICE | || | | THE BTW | || | | STATUS/ | || | BTW ENABLE|BTW DONE BTW | || | 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+–––––––––––––––––––––––––––––––––––––––––––|| |

Appendix A


Specifications

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

• scanner operating specifications

• network specifications

• throughput introduction

• calculating throughput

Backplane Current Consumption 600 mA @ 5VDC

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

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

Humidity 5 to 95% without condensation

Noise Immunity NEMA Standard ICS 2�230

Agency Certification(when product or packaging ismarked)

• CSA certified• CSA Class I, Division 2

Groups A, B, C, D certified• UL listed• CE marked for all applicable directives

Baud Rate Determination of Maximum Cable Lengthand Terminating Resistor Size

Baud RateMaximum Cable Distance

(Belden 9463) Resistor Size

Using Extended57.6K baud 3048 meters (10,000 feet)

82� 1/2 WattUsing Extended

Node Capability115.2K baud 1524 meters (5,000 feet)

82� 1/2 Watt

Brown Green Brown GoldNode Capability230.4K baud 762 meters (2,500 feet)

Brown-Green-Brown-Gold

Not Using57.6K baud 3048 meters (10,000 feet) 150� 1/2 Watt

Not Using

Extended Node115.2K baud 1524 meters (5,000 feet)

150� 1/2 Watt

Brown-Green-Brown-GoldExtended Node

Capability 230.4K baud 762 meters (2,500 feet)82� 1/2 Watt

Gray-Red-Black-Gold

DIP Switch Position for Baud Rate Selection

Baud Rate SW 1 SW 2

57.6K baud 1 ON 1 ON

115.2K baud 1 ON 0 OFF

230.4K baud 0 OFF 1 ON

230.4K baud 0 OFF 0 OFF

Scanner OperatingSpecifications

Network Specifications

SpecificationsA–2


RIO throughput is defined as the time between when an input eventoccurs at an I/O module in an RIO chassis to when an output eventoccurs at an I/O module within the same RIO chassis. There arethree types of throughput concerning the 1747-SN Series B Scannerand its RIO network:

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

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

• BT throughput (time from when a BT is enabled to when the BTsuccessfully 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

Remote Expansion Chassis

SLC Local Chassis

Remote Chassis

Scanner

Processor I/O Module

Output Device

I/O Module

Input Device

Outputs from ModulesInputs to Modules

Outputs to Modules

Inputs from Modules

RIO Scan

ASB Module

ASB Backplane Scan

Processor Scan

Scanner Scan

When the SLC control program detects that the remote input hasbeen turned on (via the scanner input image), it activates theremote output device (via the scanner output image). Throughputis then defined as the time between when the remote input deviceis activated to when the remote output turns on.

Throughput Introduction

Specifications A–3


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

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

Present

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

If BTs are present on the RIO link you must use the Discrete I/OThroughput with Block Transfers (Tdm–bt) Present section todetermine your throughput. See page A–6.

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

Tdm–nbt = 2Tps + 2TRIO + Tadp + TSNo + TSNi + Tid + Tod

Tdm–nbt = The maximum discrete throughput without BTs inmilliseconds (ms)

To calculate Tdm–nbt throughput, substitute values for the variables inthe formula above. Locate these values in the following documents:

Variable Variable Description Location of Variable

TpsThe total processor scan time

(ms)APS reference manual

TRIO The total RIO scan time (ms)

see the section RIO Scan Time

Calculation (TRIO) on page

A-4

Tadp

The adapter throughput delay.

For a 1747�ASB, this is two

ASB backplane scan times.

adapter user manual

TSNoThe scanner module output

delay time (ms)

see the section RIO Scanner

Output Delay Time (TSNo) on

page A-11

TSNiThe scanner module input

delay time (ms)

5 ms (constant value for all

formulas in this appendix)

TidThe input module delay time

(ms)

I/O product data and I/O

instruction sheets

TodThe output module delay time

(ms)


instruction sheets

Calculating Throughput

SpecificationsA–4


RIO Scan Time Calculation (TRIO)

The RIO scan time is calculated by identifying the baud rate andimage size of each logical device on the RIO link. Locate thecorresponding time value in the following table. If you are usingmultiple logical devices, add the time values together to determinethe total RIO scan time (TRIO).

TRIO = Tadapter 1 + Tadapter 2 + Tadapter 3

RIO Scan Times for Adapters

Adapter Baud RateAdapter

Size 57.6K 115.2K 230.4K

1/4 logical

rack6.0 ms 3.5 ms 2.5 ms

1/2 logical


3/4 logical


Full logical


Example Discrete I/O Throughput without Block Transfers Present

An SLC 5/03 is controlling an RIO link running at 115.2K baud thathas the following adapters:

• One 1747-ASB module module is configured as a 1/2 logical rackstarting 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 (logicalracks 1 and 2).

• Three adapters are each configured as 1/4 logical racks (logicalrack 3).



You need to calculate your Tdm–nbt: the RIO throughput time fromwhen the input closes on the 1746-IN16 until the output on the1746-OB16 is on.

1. Use the throughput formula to calculate the maximumthroughput.

Tdm–nbt = 2Tps + 2TRIO + Tadp + TSNo + TSNi + Tid + Tod

Tps = 25.0 ms, which is from the APS reference manual (assume forexample)

TRIO = The total RIO scan time (ms)

TSNo = See value in the table on page A–13, TSNo without M0 FileWrites

(Normal Mode).

TSNi = 5.0 ms

Tid = 10.0 ms, which is from I/O module instruction sheets

Tod = 1.0 ms, which is from I/O module instruction sheets

Tdm–nbt = 2(25.0) + 2TRIO + 8.0 + TSNo + 5.0 + 10.0 + 1.0

2. Calculate the total RIO scan time (TRIO). Locate the baud rate(115.2K) and adapter size, which is found in the table on pageA–4. Multiply the RIO scan times listed under the 115.2Kheading by the number of each different type of rack that youhave. Add those numbers together:

TRIO = Tadapter 1 + Tadapter 2 + Tadapter 3

TRIO = 1(4.0 ms) + 2(5.5 ms) + 3(3.5 ms)

TRIO = 25.5 ms

3. Find TSNo on page A–13 in the table TSNo without M0 FileWrites (Normal Mode). For this example Tupd > Thold, and thereare 4 logical racks configured. Therefore:

TSNo = 7.0 ms

4. Substitute all the values for variables in the throughput formulaand solve for throughput:

Tdm–nbt = 2Tps + 2TRIO + 2Tbp + TSNo + TSNi + Tid + Tod

Tdm–nbt = 2(25.0)+ 2(25.5) + 8.0 + 7.0 + 5.0 + 10.0 + 1.0

Tdm–nbt = 132.0 ms = maximum throughput

SpecificationsA–6


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

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

If BTs are not present on the RIO link, you must use the Discrete I/OThroughput without Block Transfers (Tdm–nbt) Present section todetermine your throughput. See page A–3.

The formula to calculate discrete I/O throughput with BTs present is:

Tdm–bt = 2Tps + 2TRIO + 2Tbtx + Tadp + TSNo–bt + TSNi + Tid + Tod

Tdm–bt = The maximum discrete throughput with BTs in milliseconds(ms)

To calculate Tdm–bt throughput, substitute values for the variables inthe formula above. Locate these values in the following documents:


TpsThe total processor scan time

(ms)APS reference manual

TRIO The total RIO scan time (ms)

see the section RIO Scan Time

Calculation (TRIO) on page

A-4

TbtxAdditional time due to sending

any BT data on the RIO link.

see the section Determining

Tbtx on page A-7

Tadp

The adapter throughput delay.

For a 1747�ASB, this is two

ASB backplane scan times.

adapter user manual

TSNo–btScanner output delay time with

BTs present


TSNo-bt on page A-7

TSNiThe scanner module input

delay time (ms)

5 ms (constant value for all

formulas in this appendix)

TidThe input module delay time

(ms)


instruction sheets

TodThe output module delay time

(ms)


instruction sheets



Determining TSNo-bt

Use the following table to find TSNo–bt for your particularconfiguration.

Important: The times shown are, to the best of our knowledge, themaximum delay times of the scanner. However, ininstances that throughput is an important consideration,test the application thoroughly first to ensure properoperation. Note that in most situations the averagethroughput is much better than the calculated maximumthroughput.

Number of LogicalRacks

Normal Mode Complementary ModeRacks

Configured➀ All Baud Rates 57.6K baud 115.2K baud 230.4K baud

1 Logical Rack 16.0 19.0 24.0 32.0

2 Logical Racks 19.0 23.0 27.0 36.0

3 Logical Racks 22.0 26.0 30.0 39.0

4 Logical Racks 25.0 28.0 34.0 42.0

➀ See page A-12 if you are not sure how to determine the number of logical racks configured.

Determining Tbtx

Before determining (Tbtx), you need to establish the maximum BTwrite or read length that is to be processed by each logical rack onthe RIO link. RIO scan time is increased each time an BT is sent toany logical device on the RIO network. The scan time increasedepends on the number of words sent in the BT and the selectedbaud rate.

RIO link protocol allows for a maximum of one BT to be sent toeach logical rack on the RIO link during any single RIO scan.Therefore, if multiple BTs are sent to devices within the same logicalrack, only the longest BT to that logical rack needs to be consideredto determine your maximum throughput. The RIO scan timeincrease (Tri) for each logical rack is:

Baud Rate RIO Scan Time Increase (Tri)

57.6K baud 0.300 x BT length + 5.0 ms



The total increase in the RIO scan time (Tbtx) is equal to:

Tbtx = sum of T ri for all logical racks

SpecificationsA–8


Example Discrete I/O Throughput with Block Transfers Present

An SLC 5/03 is using a scanner to control a 115.2K baud RIO linkthat 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



• 2 logical groups (1/4 logical rack)

• one 64 word BT write/read module



• 2 logical groups (1/4 logical rack)

• one 32 word BT write/read module

1. Use the throughput formula to calculate the maximum throughputof the 1747-ASB module.

Tdm–bt = 2Tps + 2TRIO + 2Tbtx + Tadp + TSNo–bt + TSNi + Tid + Tod

Tps = 25.0 ms, which is from the APS reference manual (assume forexample)

TRIO = The total RIO scan time (ms)

Tbtx = Additional time due to sending any BT data on the RIO link

Tadp = Two 1747-ASB module backplane scan times (calculated fromASB

manual) = 2(4.5) = 9.0 ms

TSNo–bt = 22.0 ms from the table on page A–13, TSNo with BlockTransfers

(Normal Mode). There are 3 logical racks configured.

TSNi = 5.0 ms

Tid = 10.0 ms, which is from I/O module instruction sheets

Tod = 1.0 ms, which is from I/O module instruction sheets

Tdm–bt = 2(25.0) + 2TRIO + 2Tbtx + 9.0 + 22.0 + 5.0 + 10.0 + 1.0



2. Calculate the total RIO scan time (TRIO). Locate the baud rate(115.2K) and adapter size which is found in the table on pageA–4. Multiply the RIO scan times listed under the 115.2Kheading by the number of each different type of rack that youhave. Add those number together.

TRIO = Tadapter1 + Tadapter2 + Tadapter3

TRIO = 1(5.5) + 1(4.0) + 2(3.5)

TRIO = 16.5 ms

3. Calculate the maximum Tri time for each logical rack. Do this bydetermining the largest BT that will occur to any device within alogical rack and calculating the transfer time using the table onpage A–7. Then add together the Tri times for each logical rackto obtain Tbtx.

Tri for rack 0 = 0.150(8) + 3.5 = 4.7 ms (maximum BT to rack 0 is 8words)



Tbtx = Tri0 + Tri1 + Tri2 = 4.7 + 3.8 + 13.1 = 21.6 ms

4. Substitute all the values for variables in the throughput formulaand solve for throughput.

Tdm–bt = 2(25.0) + 2(16.5) + 2(21.6) + 9.0 + 22.0 + 5.0 + 10.0 + 1.0

Tdm–bt = 173.2 ms = maximum throughput

SpecificationsA–10


Block Transfer Throughput

Block transfer throughput is the time from when the BT is enabledvia the EN bit, until the DN bit is processed. The following BTtiming explanations are based on the directional continuous BTexample shown on page 5–29, where a BT is re–triggeredautomatically 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 beingprocessed 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 (DNflag set)➀

The time to free up the BT buffer (by clearing the EN flag so anotherBT 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 beencleared➀

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

TM0 + TSNo–bt (number of BTs + 1) + Tbtwait + 2TRIO + 2Tbtx + Tadp–bt + Tps

The equation for freeing up the BT buffer is:

TM0 + TSNo–bt (number of BTs) + T ps

Substitute values for the variables in the formulas above. Locatethese values in the following documents:




TM0Time to perform M0 file write to enable

BTappendix B

TSNo–bt

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

TSNo-bt (to minimize the impact on

discrete I/O throughput).➀


TSNo-bt on page A-7

Tbtwait

Equals the sum of the throughput times

for all BTs scheduled to the same logical

rack (time waiting is queue), + TSNo-bt

(time to schedule pending BT). If

multiple BTs are not being performed to

the same logical rack, this value equals

zero.

calculated

TRIO RIO scan time without BTs

see the section RIO Scan

Time Calculation (TRIO) on

page A-4

Tbtx

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.


Tbtx on page A-7

Tadp–bt

Time for the adapter to acknowledge the

BT request. For the 1747�ASB, 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.

adapter user manual

Tps

One processor scan time may occur

before the SLC control program detects

that the DN flag has been set or cleared

APS reference manual

➀ When calculating BT throughput, one TSNo-bt is also required to handle the BT response.

RIO Scanner Output Delay Time (TSNo) Tables

The tables provided in this section show the maximum scanneroutput delay time (TSNo) for specific applications. TSNo isdependent on the following:

• processor scan time, or time between immediate outputs (if noBTs 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)

SpecificationsA–12


The following variables are used in the TSNo tables on page A–13:

Variable Variable Description

TSNoThe maximum scanner output

delay time

Tupd

The time between SLC

processor output scan updates

or immediate output updates

Thold

A constant time threshold that

is dependent on your

configuration. Refer to the

tables on page A-13.

TSNo increases if the interval between Tupd decreases to the timethreshold (Thold). If Tupd is less than Thold, then the larger TSNonumber must be used. Otherwise, either number may be used.

Important: The times shown in this section are, to the best of ourknowledge, the maximum delay times of the scanner.However, in instances that throughput is an importantconsideration, test the application thoroughly first toensure proper operation. Note that in most situationsthe average throughput is much better than thecalculated maximum throughput.

Determining the Number of Logical Racks Configured

The number of logical racks configured is determined by the numberof racks that contain configured devices. For example, if there arefour 1/4 rack devices in logical rack 0 and one full rack device inlogical rack 3, there would be two logical racks configured. Notethat the number of logical devices on the RIO network affects onlyTRIO, and only affects TSNo when additional logical racks are used.

When complementary mode is selected, the number of configuredracks is also determined by the number of primary or complementaryracks configured, but not by both. (The maximum number ofconfigured racksis 4.) That is, if there is a primary rack configured with acorresponding complementary rack, that is considered one logicalrack. If there is a primary rack configured without a complementaryrack (or vice versa), that also is considered one logical rack.



TSNo without M0 File Writes

Normal Mode➀

Number of LogicalAll Baud Rates

Number of Logical

Racks Configured TSNo if

Tupd�TholdThold

TSNo if Tupd

>Thold

1 Logical Rack 5.0 5.0 2.5

2 Logical Racks 7.0 7.0 4.0



Complementary Mode➀➁

Number of Logical57.6K baud 115.2K baud 230.4K baud

Number of Logical


Tupd�TholdThold

TSNo if Tupd

>Thold

TSNo if

Tupd�TholdThold

TSNo if Tupd

>Thold

TSNo if

Tupd�TholdThold

TSNo if Tupd

>Thold

1 Logical Rack 6.0 5.0 4.0 7.0 7.0 4.0 10.0 9.0 4.0

2 Logical Racks 9.0 8.0 5.0 10.0 10.0 6.0 12.0 12.0 7.0

3 Logical Racks 12.0 11.0 7.0 12.0 12.0 8.0 16.0 16.0 10.0

4 Logical Racks 15.0 14.0 9.0 16.0 16.0 10.0 21.0 22.0 13.0

TSNo with M0 File Writes (No Block Transfers)

Normal Mode➀

Number of LogicalAll Baud Rates

Number of Logical


Tupd�TholdThold

TSNo if Tupd

>Thold

1 Logical Rack 8.0 6.0 4.5




Complementary Mode➀➁

Number of Logical57.6K baud 115.2K baud 230.4K baud

Number of Logical


Tupd�TholdThold

TSNo if Tupd

>Thold

TSNo if

Tupd�TholdThold

TSNo if Tupd

>Thold

TSNo if

Tupd�TholdThold

TSNo if Tupd

>Thold

1 Logical Rack 10.0 6.0 6.0 12.0 8.0 8.0 15.0 10.0 9.0

2 Logical Racks 12.0 9.0 8.0 14.0 11.0 9.0 17.0 15.0 12.0

3 Logical Racks 15.0 12.0 9.0 16.0 14.0 11.0 21.0 20.0 14.0

4 Logical Racks 18.0 15.0 10.0 20.0 17.0 12.0 26.0 24.0 17.0

➀ All times shown are in milliseconds (ms).

➁ Although a faster baud rate decreases RIO scan time (TRIO), it has an inverse affect on TSNo

when complementary I/O mode is selected.

Appendix B


M0-M1 Files and G Files

This appendix contains important information about M0–M1 filesand G files. The information is general in nature and supplementsspecific 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 modulesonly. There is no image for these files in the processor memory. Theapplication of these files depends on the function of the particularspecialty I/O module. With respect to the SLC processor (SLC 5/02or later), the M0 file is a module output file (a write only file) andthe M1 file is a module input file (a read only file). The opposite istrue 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 theycan also be acted upon by the specialty I/O module – independent ofthe processor scan. It is important that you keep the following inmind in creating and applying your ladder logic:

Important: During the processor scan, the ladder program canaddress M0 and M1 data with bit, word, or fileinstructions. Each time an M0–M1 file address isencountered in the program, an immediate data transferto or from the specialty I/O module occurs. Theimpact these immediate data transfers have onprocessor scan time is described in appendix D of theSLC 500� and MicroLogix� 1000 Instruction SetReference Manual, Publication 1747-6.15.

Configuring M0-M1 Files Using APS Software

M0 and M1 files are configured as part of the I/O configurationprocedure for the processor file. After you have assigned thespecialty I/O module to a slot (the procedure is the same as assigningother modules), the following functions appear at the bottom of theAPS screen:

F4 F5 F6 F7

MODIFYRACKS

MODIFYSLOT

DELETESLOT

UNDELSLOT

F8 F9

EXIT SPIOCONFIG

F1 F2

READCONFIG

ONLINECONFIG

M0-M1 Files

M0–M1 Files and G FilesB–2


Complete the following steps to configure the M0 and M1 files:

1. Press [F9] , Specialty I/O Configuration. The following functionsappear:

F1 F3 F5 F7

ISRNUMBER

MODIFYG FILE

ADVNCDSETUP

G FILESIZE

2. Press [F5] , Advanced Setup. The following functions appear:

F1

INPUTSIZE

F2

OUTPUTSIZE

F3

SCANNEDINPUT

F4

SCANNEDOUTPUT

F5

M0 FILESIZE

F6

M1 FILESIZE

3. Press [F5] , then enter the number of M0 file words required (therequired number is listed in the user manual for the specificspecialty I/O module).

4. Press [F6] , then enter the number of M1 file words required (therequired number is listed in the user manual for the specificspecialty I/O module).

The specialty I/O module may require that you also configure the Gfile and specify an ISR (interrupt subroutine) number. These tasksare accomplished with function keys F1, F3, and F7 shown in step 1above. 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 = modulef = file type (0 or 1)e = slot (1�30)s = word (0 to max. supplied by module)b = bit (0�15)

Restrictions on Using M0�M1 Data File Addresses

M0 and M1 data file addresses can be used in all instructions exceptthe OSR instruction and the instruction parameters noted below:

Instruction Parameter (uses file indicator #)

BSL, BSR File (bit array)

SQO, SQC, SQL File (sequencer file)

LFL, LFU LIFO (stack)

FFL, FFU FIFO (stack)

M0–M1 Files and G Files B–3


Monitoring Bit Addresses

For SLC 5/02 processors, the M0/M1 Monitoring option is alwaysdisabled. (This processor does not allow you to monitor the actualstate of each addressed M0/M1 address.) For SLC 5/03 and SLC5/04 processors, you can choose to disable or enable the monitoringoption 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 withthe M0/M1 Monitoring option disabled, the following bitinstructions, addressed to an M0 or M1 file, are indicated as falseregardless of their actual true/false logical state.

When you are monitoring the ladder program in the Run or Test mode, theAPS or HHT display does not show these instructions as being true when theprocessor evaluates them as true.

] [Mf:e.s

b]/[

Mf:e.s

b( )

Mf:e.s

b(L)

Mf:e.s

b(U)

Mf:e.s

b

f = file (0 or 1)

If you need to show the state of the M0 or M1 addressed bit, you cantransfer the state to an internal processor bit. This is illustratedbelow, where an internal processor bit is used to indicate thetrue/false state of a rung.

This rung will not show its true rung state because the EQU instruction is always shownas true and the M0 instruction is always shown as false.

OTE instruction B3/2 has been added to the rung. This instruction shows the true orfalse state of the rung.

EQUEQUALSource A N7:12

Source B N7:3

] [B3

0] [

B3

1( )

M0:3.0

1

( )M0:3.0

1

] [B3

0] [

B3

1

EQUEQUALSource A N7:12

Source B N7:3

( )B3

2



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 theactual state of each addressed M0/M1 address (or data table). Thehighlighting appears normal when compared to the other processordata files. The processor’s performance will be degraded to thedegree of M0/M1 referenced screen data. For example, if yourscreen has only one M0/M1 element, degradation will be minimal.If your screen has 69 M0/M1 elements, degradation will besignificant.

Transferring Data Between Processor Files and M0 or M1 Files

The processor does not contain an image of the M0 or M1 file. As aresult, you must edit and monitor M0 and M1 file data viainstructions in your ladder program. For example, you can copy ablock of data from a processor data file to an M0 or M1 data file orvice versa using the COP instruction in your ladder program.

The COP instructions below copy data from a processor bit file andinteger file to an M0 file. For the example, assume the data isconfiguration information affecting the operation of the specialty I/Omodule.

COPCOPY FILESource #B3:0Dest #M0:1.0Length 16

COPCOPY FILESource #N7:0Dest #M0:1.16Length 27

] [S:1

15

First scan bit. It makesthis rung true only for

the first scan afterentering Run mode.

The COP instruction below copies data from an M1 data file to aninteger file. This technique is used to monitor the contents of an M0or M1 data file indirectly, in a processor data file.

COPCOPY FILESource #M1:4.3Dest #N10:0Length 6



Access Time

During the program scan, the processor must access the specialty I/Ocard to read/write M0 or M1 data. This access time must be added tothe execution time of each instruction referencing M0 or M1 data.For the SLC 5/03 and SLC 5/04 processors, the instruction typesvary in their execution times.

The following table shows approximate access times per instructionor word of data for the SLC 5/02, SLC 5/03, and SLC 5/04processors.

Processor Instruction TypeAccess Time per Bit

Instruction or Word of Data

Access Time per

Multi�Word Instruction

SLC 5/02 Series B All types➀ 1930 µs1580 µs plus 670 µs per

word

SLC 5/02 Series C All types➀ 1160 µs 950 µs plus 400 µs per word

XIC or XIO 782 µs --

OTU, OTE, or OTL 925 µs --

COP to M file -- 772 µs plus 23 µs per word

SLC 5/03 (All

S i )

COP from M file -- 760 µs plus 22 µs per word

Series)FLL -- 753 µs plus 30 µs per word

MVM to M file 894 µs --

any source or Destination M file

address730 µs --

XIC or XIO 743 µs --

OTU, OTE, or OTL 879 µs --

COP to M file -- 735 µs plus 23 µs per word

SLC 5/04 OS400COP from M file -- 722 µs plus 22 µs per word

SLC 5/04 OS400

FLL -- 716 µs plus 30 µs per word

MVM to M file 850 µs --

any source or Destination M file

address694 µs --

➀ Except the OSR instruction and the instruction parameters noted on page B-2.

SLC 5/02 Processor Example

] [M0:2.1

1]/[

M1:3.1

1( )

M0:2.1

10



If you are using a SLC 5/02 Series B processor, add 1930 µs to theprogram scan time for each bit instruction addressed to an M0 or M1data file. If you are using a SLC 5/03 Series C processor, add 1160 µs.


If you are using a SLC 5/02 Series B processor, add 1580 µs plus670 µs per word of data addressed to the M0 or M1 file. As shownabove, 34 words are copied from #B3:0 to M0:1.0. Therefore, thisadds 24360 µs to the scan time of the COP instruction. If you areusing a SLC 5/02 Series C processor, add 950 µs plus 400 µs perword. This adds 14550 µs to the scan time of the COP instruction.



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 anexample, if you use a COP to M file instruction like the one shownabove, add 772 µs plus 23 µs per word. This adds 1554 µs to theSLC 5/03 processor scan time due to the COP instruction.



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 anexample, if you use a COP to M file instruction like the one shownabove, add 735 µs plus 23 µs per word. This adds 1517 µs to theSLC 5/04 processor scan time due to the COP instruction.



Minimizing the Scan Time

You can keep the processor scan time to a minimum by economizingon the use of instructions addressing the M0 or M1 files. Forexample, XIC instruction M0:2.1/1 is used in rungs 1 and 2 of thefigure below, adding approximately 2 ms to the scan time if you areusing a SLC 5/02 Series B processor.

XIC instructions in rungs 1 and 2 are addressed to the M0 data file. Each ofthese instructions adds approximately 1 ms to the scan time (SLC 5/02Series B processor).

1

] [B3

12] [

M0:2.1

1( )

B3

14

] [M0:2.1

1( )

B3

10

2

In the equivalent rungs of the figure below, XIC instruction M0:2.1/1is used only in rung 1, reducing the SLC 5/02 scan time byapproximately 1 ms.

These rungs provide equivalent operation to those of figure A by substitutingXIC instruction B3/10 for XIC instruction M0:2.1/1 in rung 2. Scan time isreduced by approximately 1 ms (Series B processor).

] [B3

12] [

B3

10( )

B3

14

] [M0:2.1

1( )

B3

101

2

The following figure illustrates another economizing technique. TheCOP instruction addresses an M1 file, adding approximately 4.29 msto the scan time if you are using a SLC 5/02 Series B processor.Scan time economy is realized by making this rung true onlyperiodically, as determined by clock bit S:4/8. (Clock bits arediscussed in appendix B of the SLC 500� and MicroLogix� 1000Instruction Set Reference Manual, Publication 1747-6.15.) A rungsuch as this might be used when you want to monitor the contents ofthe M1 file, but monitoring need not be on a continuous basis.

[OSR]B11

0

COPCOPY FILESource #M1:4.3Dest #N10:0Length 6

] [S:4

8S:4/8 causes the#M1:4.3 file to updatethe #N10:0 file every

2.56 seconds.



Capturing M0-M1 File Data

The first two ladder diagrams in the last section illustrate a techniqueallowing you to capture and use M0 or M1 data as it exists at aparticular time. In the first figure, bit M0:2.1/1 could change statebetween rungs 1 and 2. This could interfere with the logic applied inrung 2. The second figure avoids the problem. If rung 1 is true, bitB3/10 captures this information and places it in rung 2.

In the second example of the last section, a COP instruction is usedto monitor the contents of an M1 file. When the instruction goestrue, the 6 words of data in file #M1:4.3 is captured as it exists at thattime 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 afterpower is removed. See your specialty I/O module user’s manual.This means that an OTE instruction having an M0 or M1 addressremains on if it is on when power is removed. A “hold-in” rung asshown below will not function as it would if the OTE instructionwere non-retentive on power loss. If the rung is true at the timepower is removed, the OTE instruction latches instead of droppingout; when power is again applied, the rung will be evaluated as trueinstead of false.

] [B3

0( )

M0:2.1

1

] [M0:2.1

1

!ATTENTION: When used with a speciality I/Omodule having retentive outputs, this rung can causeunexpected start-up on powerup.

You can achieve non-retentive operation by unlatching the retentiveoutput with the first pass bit at powerup:

] [S:1

15(U)

M0:2.1

1

] [B3

0( )

M0:2.1

1

] [M0:2.1

1

This rung is truefor the first scanafter powerup tounlatch M0:2.1/1.



Some specialty I/O modules use G (confiGuration) files (indicated inthe specific specialty I/O module user’s manual). These files can bethought of as the software equivalent of DIP switches.

The content of G files is accessed and edited offline under the I/OConfiguration function. You cannot access G files under the MonitorFile function. Data you enter into the G file is passed on to thespecialty I/O module when you download the processor file andenter the REM Run or any one of the REM Test modes.

Configuring G Files Using APS Software

The G file is configured as part of the I/O configuration procedurefor the processor file. After you have assigned the specialty I/Omodule to a slot (the procedure is the same as assigning othermodules except that you must specify the ID code of the specialtyI/O module), the following functions appear at the bottom of theAPS screen:

F4 F5 F6 F7

MODIFYRACKS

MODIFYSLOT

DELETESLOT

UNDELSLOT

F8 F9

EXIT SPIOCONFIG

F1 F2

READCONFIG

ONLINECONFIG

This is the starting point for configuring the G file and otherparameters of the specialty I/O module. Complete the followingsteps to create and monitor the G file:

1. Press [F9] , Specialty I/O Configuration. A screen similar to thefollowing is displayed:

RACK 1 = 1746-A4 4-SLOT BackplaneRACK 2 =RACK 3 =

SLOT C*0*1*2*3 4 5 6 7 8

Press a function key

I/O CONFIGURATION FOR:EXAMPLE

F7F5

G FILESIZE

ADVNCDSETUP

F1

ISR NUMBER

F3

MODIFYG FILE

SPECIAL CONFIG FOR SLOT: 1

Module’s ID Code: 12705Maximum Input Words: 0Maximum Output Words: 0Scanned Input Words: 0Scanned Output Words: 0M0 Length: 0M1 Length: 0‘G’ File Size: 0ISR Number: 0

ESC exits

ESC exits

2. Press [F7] , G File Size, then specify the number of wordsrequired for the specialty I/O module.

G Files



3. Press [F3] , Modify G File. The content of the G file appears inthe display area. Data is shown in the default form, decimal:

address 0 1 2 3 4 5 6 7 8 9G1:0 xxxx 0 0 0 0 0 0 0 0 0G1:10 0 0 0 0 0 0

The function keys appearing below the data table indicate the threedata formats available to you – binary data, decimal data, andhex/bcd data:

F3

HEX/BCDDATA

F1 F2

BINARYDATA

DECIMALDATA

The following figure illustrates the three G file data formats that youcan select. Word addresses begin with the file identifier G and theslot number you have assigned to the specialty I/O module. In thiscase, the slot number is 1. Sixteen words have been created(addresses G1:0 through G1:15).

address 0 1 2 3 4 5 6 7 8 9G1:0 xxxx 0 0 0 0 0 0 0 0 0G1:10 0 0 0 0 0 0

16�word G file, I/O slot 1, decimal format

address 0 1 2 3 4 5 6 7 8 9G1:0 xxxx 0000 0000 0000 0000 0000 0000 0000 0000 0000G1:10 0000 0000 0000 0000 0000 0000

address 15 data 0G1:0 xxxx xxxx xxxx xxxxG1:1 0000 0000 0000 0000G1:2 0000 0000 0000 0000G1:3 0000 0000 0000 0000G1:4 0000 0000 0000 0000G1:5 0000 0000 0000 0000G1:6 0000 0000 0000 0000G1:7 0000 0000 0000 0000G1:8 0000 0000 0000 0000G1:9 0000 0000 0000 0000G1:10 0000 0000 0000 0000G1:11 0000 0000 0000 0000G1:12 0000 0000 0000 0000G1:13 0000 0000 0000 0000G1:14 0000 0000 0000 0000G1:15 0000 0000 0000 0000

16�word G file, I/O slot 1, hex/bcd format

16�word G file, I/O slot 1, binary format



Editing G File Data

Data in the G file must be edited according to your application andthe requirements of the specialty I/O module. You edit the dataoffline under the I/O configuration function only. With the decimaland 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 automaticallyby the processor according to the particularspecialty I/O module. Word 0 cannot be edited.

Appendix C


RIO Configuration Worksheet

This appendix provides a worksheet to help you configure your RIOdevices.

We recommend that you use a photocopy of the worksheet so youretain a blank worksheet for future applications.

Bit Number − Decimal

LogicalRack 1

07815

LogicalRack 0

LogicalRack 2

ÉÉÉÉÉÉÉÉÉÉ


ÉÉÉÉÉ




LogicalRack 3

SLC Processor Input Image

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

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

High Byte Low ByteBit Number − Decimal

LogicalRack 1

07815

LogicalRack 0

LogicalRack 2



ÉÉÉÉÉ




LogicalRack 3

SLC Processor Output Image

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


High Byte Low Byte

e = 1747�SN Slot Number

Directions

RIO Configuration WorksheetC–2


Bit Number − Decimal

LogicalRack 1

07815

LogicalRack 0

LogicalRack 2






LogicalRack 3

SLC Processor Input Image

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


High Byte Low ByteBit Number − Decimal

LogicalRack 1

07815

LogicalRack 0

LogicalRack 2






LogicalRack 3

SLC Processor Output Image

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


High Byte Low Byte

e = 1747�SN Slot Number

Glossary


Glossary

The following terms are used throughout this manual. Refer to theAllen-Bradley Industrial Automation Glossary, Publication NumberAG-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 anindividual adapter.

ASB Module The Catalog Number 1747-ASB, 1771-ASB, or1794 - ASB Remote I/O Adapter Module. The ASB module is anadapter.

ASB Module Chassis The chassis directly controlled by the ASBmodule. This includes the remote chassis and (if installed) tworemote expansion chassis when using the 1747-ASB.

Block Transfer (BT) See RIO Block Transfer.

Block Transfer Read (BTR) A form of block transfer that occurswhen a remote device transfers data to the SLC processor.

Block Transfer Write (BTW) A form of block transfer thatoccurs when the SLC processor transfers data to a remote device.

Complementary I/O Functionality that allows you to maximizeI/O usage by pairing up I/O data from a primary and complementarychassis.

Discrete I/O An input or output device that has corresponding bitlocations in the scanner’s input or output file.

Discrete I/O Module An I/O module used to sense or controltwo-state (ON/OFF) devices.

Extended Node Capability Functionality that allows you to usean 82 Ohm termination resistor at both ends of the RIO link for allbaud rates. This functionality also allows for up to 32 adapters to beconnected to the RIO link.

G file The SLC file used to configure the scanner. You enterconfiguration information into this file during SLC processorprogramming. This file is loaded to the scanner by the SLCprocessor upon entering run mode.

GlossaryG–2


Inhibit A function by which the scanner stops communicatingwith a logical device. The logical device will consider itselfinhibited if it does not receive communications from the scannerwithin a certain period of time.

Input file The scanner’s input image file that is updated duringthe SLC processor input scan.

Local Expansion Chassis A chassis that is connected to a localSLC 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 processorand scanner.

Logical Device Any portion of a logical rack that is assigned to asingle adapter. Adapters may appear as more than one logicaldevice.

Logical Group A logical group consists of one input and oneoutput word within a logical rack. A word consists of 16 bits, eachbit represents one terminal on a discrete I/O module.

Logical Rack A fixed section of the scanner image comprised ofeight input image words and eight output image words.

Logical Slot A logical slot consists of one input and one outputbyte within a logical group. A byte consists of 8 bits, each bitrepresents 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 byyour application program. Also, the M files are used to control andmonitor RIO block transfer operations.

Output file The scanner’s output file that is updated during theSLC processor output scan.

Remote Chassis The chassis containing an ASB module andconnected to the local SLC chassis via the RIO link.

Remote Expansion Chassis A chassis that is connected to aremote chassis using a 1747-C9 (91.4 cm [36 in.]) or 1747-C7 (15.2cm [6 in.]) cable.

Reset, Adapter Decide Commands sent by the scanner to alogical device during an RIO discrete transfer. These commandsinstruct the logical device to reset all of its discrete outputs if holdlast state is not selected, or to hold all of its discrete outputs in theirlast state if hold last state is selected.

Glossary G–3


Reset, Adapter Reset Commands sent by the scanner to a logicaldevice during an RIO discrete transfer. These commands instruct thelogical device to reset all of its discrete outputs, regardless of thehold last state selection.

RIO Block Transfer The exchange of up to 64 words of databetween the scanner and a remote device. RIO block transfers onlyoccur if you program them in your processor control program.

RIO Discrete Transfer The exchange of image data between thescanner and adapter. RIO discrete transfers occur continuouslywhenever the scanner and adapter are communicating on the RIOlink.

RIO Link An Allen-Bradley communication system supportinghigh-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 thirdparty product that connects to the RIO link as an adapter or slavedevice.

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 toexchange I/O information between the scanner and all the adapterson the RIO link. The scanner image is a portion of the SLCprocessor image.

SLC Chassis A physical SLC rack that houses SLC processorsand 1746 and 1747 I/O modules.

SLC Processor The processor that controls the SLC chassis inwhich the the scanner is installed.

Slot The physical location in any SLC chassis used to insert I/Omodules.

Specialty I/O Module An I/O module other than a discrete I/Omodule (e.g., an analog module).

Numbers

1-slot addressing, complementary I/O,1-13

1/2-slot addressing, complementary I/O,1-14

2-slot addressing, complementary I/Oconfiguration, 1-12

A

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 examplesBlock Transfer, 7-14 Dataliner, 7-8 PanelView, 7-11 RediPANEL keypad module, 7-1 RediPANEL/DCM, 7-4

B

baud rate, DIP switch, 1-19

Belden 9463 cable, maximum distance, 3-5, A-1

bitscommunication attempted, 4-22 enable device fault, 4-21

block transferBTR 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 layoutblock transfer, 5-8 M0 file output/control, 5-8

C

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

configurationG file, 4-3

Index

IndexI–2

general rules, 4-5 rules concerning complimentary I/O, 4-5

configuring scanner, 4-32

considerationsblock 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 logicalrack boundaries, 4-11

crossing logical rack boundaries, 4-10 to create multiple logical devices, 4-11

D

data transferblock 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 transferspresent example, A-8

discrete I/O throughput without blocktransfers present example, A-4

discrete transfer, 1-6 transferring data, 1-9

E

EMC Directive, 3-1

equipment needed, 2-1

error codes, 6-2 block transfer, 5-11

European Union Directive Compliance, 3-1

examplescommunication 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

F

fault, LED, 1-19

functional overview, block transfer, 5-5

G

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/Oconfiguration, 1-11

H

hardware featuresDIP switch, 1-18 LEDs, 1-18 RIO network connector, 1-18

I

I/O imagedescription, 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

illustrationsconnecting 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

L

LED conditions, table, 6-1

LEDscomm, 1-19 fault, 1-19 green, 1-19 red, 1-19 status table, 3-8 troubleshooting, 6-1

link specificationlogical, 1-9 physical, 1-9

logical device image size, 4-24

logical rack, crossing logical rackboundaries, 4-10

logical rack boundaries, crossing, 4-10

M

M filesoverview, 4-12 using binary files in conjunction, 4-12

M0 and M1 data filescapturing 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 filedescription, 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, blocktransfer, 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 datawords 0-63, 5-9

M1 fileactive 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 status flags, 5-12 word 0, 4-22 word 10, 4-24 word 2, 4-22 word 3, 4-23 word 4, 4-24 word 5, 4-25 word 8, 4-23 word 9, 4-24 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 transferbuffer 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 transfererror codes, 5-11

M1:e.110-173, block transfer data words 0through 63, 5-10

manuals, related, P-2

module release, 3-4

N

network wiring, 3-4

noise immunity, A-1

O

operationrun mode, 3-7 startup, 3-7

IndexI–4

operation modes, changing, 3-7

overview, M files, 4-12

P

power consumption, A-1

programming scanner, 4-32

publications, related, P-2

Q

Quick Start for Experienced Users, 2-1

R

rack boundaries, crossing logical, 4-10

related documentation, P-2

remote I/O, configuration considerations,4-10

remote output reset control, 4-18

removing the scanner, 3-4

required tools and equipment, 2-1

resistors, terminating, 3-5 , A-1

retrofits and new installation, shield drainwire, 3-5

retry counters, 6-2

RIO baud rate status, 4-22

RIO block transfer, path of a block transfer,5-2

RIO block transfer - what it is, 5-1

RIO device reset control, 4-16

RIO image files, 4-1

RIO link, physical and logical specifications,1-9

RIO link connector, 1-19

RIO link wiring, 3-3

RIO scan time, throughput, A-4

rules, configuration, 4-5

run mode, operation, 3-7

S

scannerasynchronous operation, 1-5 G file configuration, 4-3 I/O image division, 1-3 image files, 4-1 insertion, 3-3 interacting with adapters, 1-2 , 1-6

interaction with adapters, 1-6 operating with SLCs, 1-5 output delay time

with block transfer, A-7 without block transfer, A-11

scanning remote I/O, 1-4

scanner I/O image, concepts, 1-7

selecting, baud rate, 3-2

setting up scanner, 4-32 G file, 4-3

shield drain wire, retrofits and newinstallation, 3-5

slot addressing, 4-31 block transfer, 5-6

slot number, 5-10

specificationsbaud rate, A-1 cable distance, 3-5 , A-1 dip switch settings, A-1 humidity, A-1 noise immunity, A-1 operating temperature, A-1 power consumption, A-1 resistor size, 3-5 , A-1 storage temperature, A-1

start-up instructions, 2-1

startup, 3-6 operation, 3-7

status table, LEDs, 3-8

step-by-step explanation, how blocktransfer works, 5-13

steps for programming scanner, 4-32

T

tablebits, baud rate, switch settings, 4-22 error codes, 6-1 LEDs, 6-1

temperatureoperating, A-1 storage, A-1

terminating resistor, size of, 3-4

terms, G-1

theory of operationblock transfer, 5-2 block transfer read, 5-3 block transfer write, 5-4

throughput, A-2 calculating throughput, A-3

block transfer, A-10

Index I–5

with block transfers present, A-6 ,A-10

without block transfers present, A-3 introduction, A-2

timing diagramsblock transfer, 5-14 control program cancelling a BT, 5-18 ,

5-19 failure after startup, 5-17 successful block transfer, 5-15

tools needed, 2-1

transferring datablock transfer, 1-9 discrete, 1-9

troubleshooting, 6-1 communication problems, 6-2 contacting Allen-Bradley, P-4

U

understandingI/O image files, 4-1

slot addressing, 4-31 slot numbers, 5-10

W

wiring the network, 3-4

word 0, G file, 4-3

word 1, primary logical device address, Gfile, 4-3

word 2, primary logical image size, G file,4-3

word 3, secondary logical device address, Gfile, 4-4

word 4, secondary logical image size, G file,4-4

words 24 through 27, M0 file, 4-17


Allen�Bradley, a Rockwell Automation Business, has been helping its customers improveproductivity and quality for more than 90 years. We design, manufacture and support a broadrange of automation products worldwide. They include logic processors, power and motioncontrol devices, operator interfaces, sensors and a variety of software. Rockwell is one of theworld's leading technology companies.

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 • Russia�CIS • Saudi Arabia • Singapore • Slovakia • Slovenia • South Africa, Republic • Spain • Sweden • Switzerland • Taiwan • Thailand • Turkey •United Arab Emirates • United Kingdom • United States • Uruguay • Venezuela • Yugoslavia

Allen�Bradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1) 414 382�2000 Fax: (1) 414 382�4444

Publication 1747�6.6 - July 1996Supersedes Publication 1747�6.6 - February 1995

PN 40072�005�01(B)Copyright 1996 Allen�Bradley Company, Inc. Printed in USA

Date post:	21-Apr-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

1747-6.6, Remote I/O Scanner, User...

Documents