Rockwell Automation 1785-Vx0B, D17856.5.9 User Manual

Allen-Bradley
PLC-5 VME VMEbus
User
Programmable Controllers
(1785-V30B, -V40B,
-V40L, and -V80B)
Manual

Important User Information

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based on the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation, and Maintenance of Solid State Control (available from your local Allen-Bradley office), describes some important dif equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole or in part, without written permission of Allen-Bradley Company, Inc., is prohibited.
Throughout this manual we use notes to make you aware of safety considerations:
ferences between solid-state
ATTENTION: Identifies information about practices or
circumstances that can lead to personal injury or death, property damage, or economic loss.
Attention statements help you to:
identify a hazard avoid the hazard recognize the consequences
Important: Identifies information that is critical for successful application and understanding of the product.

Table of Contents

Summary of Changes
Using this Manual
Manual Objectives What
this Manual Contains Audience Terms Related
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
and Conventions
Publications
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview
Chapter Objectives Features System Description VMEbus Compatibility Compatibility
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface
with the Standard PLC-5 Processor with the 6008-L
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TV Processor
. . . . . . . . . . . . . . . . .
Installation
Chapter Objectives Handling the Processor Setting the Switches Configuring the VME Backplane Jumpers Inserting the Processor into a Chassis Grounding Determining Power-Supply Requirements Connecting Connecting Connecting a DH+ Link Connecting a Programming T Installing,
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
to Remote I/O an Extended-Local I/O Link
Removing, and Disposing of the Battery
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
erminal to Channel 0
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
i
iii
iii iii iii
iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1 1-1 1-4 1-6 1-9 1-9
2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1 2-2 2-2 2-4 2-5 2-5 2-6
2-6 2-10 2-12 2-14 2-15
VMEbus Interface
Chapter Objectives System Bus-Release Modes VME LEDs VME Configuration Registers Commands
Controller
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Signal Usage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-1
3-1
3-2
3-2
3-3
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-4
3-7
ii
Table of Contents
Ladder-Program Interfaces
Chapter Objectives Ladder Messages Message VME Continuous Copy to/from VME VMEbus
Completion and Status Bits
Status File
Interrupts
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
Commands
Chapter Objectives Command Continuous-Copy Commands Handle-Interrupts Command Send-PCCC Command Command-Protocol Error Codes Response-Word Error Codes
T
ypes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
PLC-5/VME Processor Communications Commands 6-1. . . . .
Chapter Objectives PCCC Structure Supported PCCCs Header Bit/Byte Descriptions Echo
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identify Read-Modify-Write Typed Data Typed Write Set CPU Mode Upload Download Upload Download Read Bytes Physical Write Bytes Physical Get Edit Resource Return Edit Resource Apply Restore Upload
Host and Status
Read
T
ypes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All Request
All Request
Complete
Complete
Port Configuration
Port Configuration
and Download Procedure
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
4-1. . . . . . . . . . . . . . . . . . . . . . . .
4-1 4-1 4-6
4-7 4-10 4-1
1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1
5-1
5-2
5-5
5-7
5-8
5-8
6-1
6-1
6-3
6-4
6-5
6-6
6-8 6-10 6-12 6-18 6-20 6-21 6-23 6-24 6-25 6-26 6-27 6-29 6-30 6-31 6-32 6-34
Table of Contents
iii
Performance and Operation
Chapter Objectives VME
Throughput T Communication Methods Benchmark Introduction to PLC-5/VME Processor Scanning Discrete
T
ests
and Block T
Sample Applications
Appendix Objectives VMEDEMO.CPP VMEDEMO.MAK UPLOAD.CPP UPLOAD.MAK DOWNLOAD.CPP DOWNLOAD.MAK
Sample Application Programming Interface Modules B-1
Appendix Objectives COMMON.H COMMON.C P40VCC0.H P40VCC0.C PCCC.H P40VHINT.H P40VHINT.C P40VSPCC.H P40VSPCC.C P40VWBP.H P40VWBP.C P40VAPC.H P40VAPC.C P40VULC.H P40VULC.C P40VDLA.H P40VDLA.C P40VDLC.H P40VDLC.C P40VECHO.H P40VECHO.C P40VGER.H P40VGER.C P40VIHAS.H P40VIHAS.C
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ime
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
ransfer I/O Scanning
. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1. . . . . . . . . . . . . . . . . . . . . . . .
7-1 7-1 7-2 7-4 7-7
7-12
A-1
A-1
A-2 A-13 A-15 A-26 A-27 A-34
B-1
B-3
B-5 B-17 B-18 B-30 B-32 B-33 B-39 B-40 B-43 B-44 B-46 B-47 B-49 B-50 B-52 B-53 B-55 B-56 B-58 B-59 B-61 B-62 B-64 B-67
iv
Table of Contents
P40VRBP.H P40VRBP.C P40VRER.H P40VRER.C P40VRMW.H P40VRMW.C P40VRPC.H P40VRPC.C P40VSCM.H P40VSCM.C P40VULA.H P40VULA.C
Specifications
Environmental VMEbus
Troubleshooting
Appendix Objectives VME Backplane Jumpers VME LEDs Message Continuous-Copy Error Codes Command-Protocol Error Codes Response-Word Error Codes PCCC Command Status Codes Avoiding Inserting Recovering from Possible Memory Corruption Examining Avoiding Run-time Errors when Executing FBC and
DDT Instructions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifications
Specifications
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Completion and Status Bits Error Codes
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . .
Multiple Watchdog Faults1. Ladder Rungs at the 56K-W
Fault Codes
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
ord Limit
. . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
B-69 B-70 B-72 B-73 B-75 B-76 B-80 B-81 B-83 B-84 B-86 B-87
C-1
C-1 C-2
D-1
D-1 D-1 D-1 D-2 D-2 D-2 D-3 D-3 D-5 D-5 D-6 D-6
D-6
Cable Connections
Cable Connections for Communication Boards Cable
Connections for Serial-Port Communications
Front
Panel
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Pin Assignments Cable
Specifications
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . .
E-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E-1 E-1 E-2 E-6 E-7
Figures/Tables
Table of Contents
v
Compliance
to European Union Directives
. . . . . . . . . . . . . . . . . .
Figure 2.3
Terminating a Remote I/O Link Using a Resistor
. . . . . . . . . . .
Figure 2.4
Programming Terminal to Channel 0 of a PLC-5/VME Processor
Figure 2.5
Installing a Processor Battery (cat. no. 1770-XYV)
able 2.C
T
Programming Terminal to Channel 0 Interconnect Cables 2-14
. . . . . . . . . .
. . . .
2-1
2-9 2-14 2-15

Summary of Changes

Summary of Changes
This release of the PLC-5/VME VMEbus Programmable Controllers User Manual contains new and updated information on PLC-5/VMEt systems.
For infornmation about: See chapter/appendix:
CE compliance 2 making VME self-references in POST tests 2 improved .WRDY and .LOCK bit description 3 changes to the status file 4 setting the NOCV bit to 0 7 revised specifications C additional troubleshooting tips D
To help you find new and updated information in this release of the manual, we have included change bars as shown to the left of this paragraph.
In addition to the new and updated information discussed above, we have altered the way we reference software documentation in this manual. Rather than show specific screens and key sequences which may vary according to the software package you are using, we refer you instead to the programming software documentation that accompanies your particular software package. Of course, we still provide the basic background information you need to accomplish your programming tasks, but if you have specific questions, you should refer to your programming software documentation set.
vii
Using this Manual
Preface
Manual
Objectives

What this Manual Contains

The purpose of this manual is to familiarize you with the installation and use of the PLC-5/VME programmable controllers. This manual focuses on the specific VMEbus aspects of this processor. Typically, you use this processor in a VMEbus system with one or more host CPU modules that control(s) and communicate(s) with the processor. You need to develop software driver programs to execute on the host CPU module(s) to accomplish this. You must also write ladder programs for your processor to monitor and control the I/O of your control system. This manual helps you write the VMEbus-specific aspects of these programs.
Chapter/ Appendix
Title Contents
1 Overview Overview of the PLC-5/VME processors 2 Installation Configuration and installation procedures 3 VMEbus Interface Configuration registers and commands 4 Ladder-Program Interfaces How to interact with your VMEbus environment from
your ladder program 5 Commands Commands used to interface to the processor 6 PLC-5/VME Processor
Communications Commands
7 Performance and Operation Overview of the performance and operation of the
A Sample Applications How to write applications to interact with your
B Sample API Modules How to write API modules to interact with your
C Specifications PLC-5/VME processor specifications D Troubleshooting Troubleshooting and error-code information E Cable Connections Communication boards and cable connections for
The function of the extended PCCCs in the
PLC-5/VME processor
PLC-5/VME processor
PLC-5/VME processor
PLC-5/VME processor
family processors
PLC-5

Audience

This manual assumes that you have background in:
VMEbus concepts and basics PLC-5 ladder logic PLC-5/VME operation C-language programming
iii
Preface
Using this Manual

Terms and Conventions

We refer to the: As the:
Data Highway DH link Data Highway Plus Programmable Logic Controller processor PLC-5 Processor
Programmable Controller Communications Commands
Release on request ROR Release when done RWD
Term Definition
Extended-local I/O I/O connected to a processor across a parallel link, thus limiting its
Extended-local I/O link a parallel link for carrying I/O data between a PLC-5/V40L
Remote I/O link a serial communication link between a PLC-5 processor port in
Remote I/O chassis the hardware enclosure that contains an adapter and I/O modules
Discrete-transfer data data (words) transferred to/from a discrete I/O module Block-transfer data data transferred, in blocks of data up to 64 words, to/from a block-
distance from the processor
processor and extended-local I/O adapters
scanner mode and an adapter as well as I/O modules that are located remotely from the PLC-5 processor
that are located remotely on a serial communication link to a PLC-5 processor in scanner mode
transfer I/O module (for example, an analog module)
DH+ link
PLC-5/VME processor. Unless noted otherwise, we use PLC-5/VME processor to denote all processors.
PCCC
iv
In addition, you may encounter words in different typefaces. We use these conventions to help differentiate descriptive information from information that you enter while programming your processor.
The Enter key looks like this (boldface and in brackets):
[Enter]
Words or commands that you enter appear in boldface. For example:
CTV # SVI
Variables that you enter appear in italics. For example:
vmeaddr width
“Type” means type in the information.
“Enter” means type in the information and then press the [Enter] key.
Preface
Using this Manual

Related Publications

The 1785 PLC-5 programmable controller documentation is organized into manuals according to the tasks that you perform. This organization lets you find the information that you want without reading through information that is not related to your current task.
Enhanced PLC-5
Processors System
System Overview
Overview of processor
specifications. selection,
and justification information
1785-2.36
Enhanced and Ethernet
PLC-5 Programmable
Controller User Manual
Explanation of processor
functionality, system
design, and programming
considerations
1785-6.5.12
1785 PLC-5
Programmable Controllers
Quick Reference
Quick access to switches,
status bits, indicators,
instructions, SW screens
1785-7.1
For more information on 1785 PLC-5 programmable controllers or the above publications, contact your local Allen-Bradley sales office, distributor, or system integrator.
We also suggest that you acquire the following publications for reference:
Data Highway / Data Highway Plus DH-485 Communication Protocol
and Command Set Reference, Allen-Bradley, publication 1770-6.5.16
The VMEbus Specification—Rev: C.1, Motorola, HB212
VMEbus User’s Handbook, Steve Heath, CRC Press, ISBN
0-8493-7130-9
v
Overview
Chapter
1
Chapter

Features

Objectives
Read this chapter to understand the overall operation of the PLC-5/VME processor, how you can use it in VME systems, and how its features and functions relate to those of other Allen-Bradley processors.
PLC-5/VME processors are programmable controllers that bring the technology of the 1785 PLC-5 processor to the VMEbus environment.
The PLC-5/VME processor is equivalent (in terms of I/O, ladder programming, and instruction timing) to the standard PLC-5 processor, except that the PLC-5/VME processor:
plugs into a VMEbus system
has a VMEbus communication interface designed for use with other
VMEbus CPU modules
can access VMEbus I/O modules
has no EEPROM memory module
Figure 1.1 shows examples of the PLC-5/VME processors.
1-1
Chapter 1
Overview
Figure 1.1 Examples
of PLC-5/VME Processors
Battery installed
Program Remote Run
Battery low Proc run/Fault Force Ch 0 Status SYSFAIL Master Access Slave Access
Chan 0
Chan 1
Battery installed
1A
1B
Program Remote Run
Battery low Proc run/Fault Force Ch 0 Status SYSFAIL Master Access Slave Access
Chan 0
Chan 1
Chan 2
Battery installed
Battery low Proc run/Fault Force Ch 0 Status SYSFAIL
1A
Master Access Slave Access
1B
Program Remote Run
Chan 1
1A
1B
Chan 0
Chan 2
1-2
PLC-5/V30B processor
PLC-5/V40B or -5/V80B processor PLC-5/V40L processor
19499
All PLC-5/VME processors have at least one configurable I/O channel and one serial port (channel 0).
Channel: Is configured for:
0 supporting RS-232C
The PLC-5/VME processor channel 0 protocol defaults to the system mode of operation (DF1 point-to-point), which allows programming from a PC terminal.
The default communication rate is 2400. 1A DH+ mode (by default) 1B scanner mode (by default) 2 (if applicable) DH+ and remote I/O (RIO) communication or extended-local I/O
Chapter 1
Overview
In the PLC-5/V40B, both channels (1 and 2) are identical although they are independently configurable. In the PLC-5/V40L, channel 2 is a local I/O (LIO) interface.
The PLC-5/VME processor has the same instruction set as the standard PLC-5 processor. It supports:
complex expressions in compare and compute instructions statistical instructions floating-point calculations in PID instructions ASCII string-handling instructions main control programs (MCPs)
Use the keyswitch to change the mode in which a processor is operating.
If you want to: Turn the keyswitch to:
Run your program, force I/O, and save your programs to a disk drive. Outputs are enabled. (Equipment being controlled by the I/O addressed in the ladder program begins operation.)
Enable outputs.
Note:
You cannot create or delete a program file, create or delete data files, or change the modes of operation through the programming software while in run mode.
Disable outputs
Create, modify, and delete ladder files or data files; download to an EEPROM module; and save/restore programs.
Notes:
The processor does not scan the program.
You cannot change the mode of operation through the programming software while in program mode.
RUN
PROG
R E M
RUN
PROG (program)
PROG
R E M
RUN
Change between remote program, remote test, and remote run
REM (remote)
modes through the programming software.
Remote run
Enable outputs.
You can save/restore files and edit online.
Remote program
PROG
RUN
See the program-mode description above.
Remote test
Execute ladder programs with outputs disabled.
You cannot create or delete ladder programs or data files.
R E M
1-3
Chapter 1
Overview

System Description

CPU
PLC-5/VME processor
CPUs
PLC-5/VME processor
CPU
DH+ link
Remote I/O or Extended­Local I/O
19500
Use the PLC-5/VME processor in a 6U (full-height) VMEbus chassis. You can use the PLC-5/VME processor by itself (i.e., with no other VME modules), but typically the PLC-5/VME processor is used in conjunction with other VMEbus computers (CPUs) and I/O modules. The examples below illustrate possible configurations.
The
PLC-5/VME processor is used in conjunction with a VMEbus CPU module. The processor serves as a real-time I/O processor under the direction of the CPU. The processor is a slave of the CPU, where, in addition to its normal ladder logic and I/O processing in each scan loop, the processor responds to directions from the CPU and passes data back to the CPU.
There is no fixed relationship between processor and CPU, so multiple CPUs can communicate with one processor. Multiple CPUs run multiple tasks, all sending and receiving data from the processor at the same time.
One CPU can control multiple PLC-5/VME processors. Each processor maps into the VMEbus address space; so you map each processor to a different address space.
PLC-5/VME processors
PLC-5/VME processor
19500
No CPU interacts with the processor or more remote I/O racks and has the capability
. The processor interacts with I/O modules in one
, from its ladder program, of generating VMEbus accesses. This means that the processor can access VMEbus I/O modules as well.
1-4
Chapter 1
Overview
The following diagrams show three basic configurations for programming and debugging your ladder-logic programs.
PLC-5/VME processor
DH+ link
Connect 1784-KT communication device in your IBM A
a computer via the DH+ link, typically using a
T computer
and a 1784-CP6 cable.
PLC-5/VME processor
RS-232
PLC-5/VME processorPC/CPU
19501
Connect a computer using the RS-232C on-board serial port of the PLC-5/VME processor RS-232C cable connects one of the computer to the channel 0 (serial) port of the processor
ou can program as well as download files directly over the
Y
. In this configuration, the
s COM ports
.
VMEbus backplane to your PLC-5/VME processor if you:
run 6200 Series PLC-5 Programming Software release
4.4 or later use an 8086-based CPU from RadiSys—i.e., a EPC-1,
EPC-4, or EPC-5 VME PC-compatible computer
Important:
In order to use the
save
feature of the 6200
.
Series PLC-5 Programming Software when you communicate with the processor in this way release 4.5 or later
.
, you must run
1-5
Chapter 1
Overview

VMEbus Interface

Configuration/control/ status/message registers in A16 space
Optional general-purpose memory in A24 space
VMEbus
The PLC-5/VME is fully compliant with the C.1 VMEbus specification. The PLC-5/VME processor occupies two 6U VMEbus slots. It can reside in any adjacent pair of slots, including slot 1, the system-controller slot. The PLC-5/VME processor has a single VMEbus P1 connector, allowing it to be used in VMEbus systems that have either the full J1 and J2 backplanes or only the J1 backplane.
The PLC-5/VME processor occupies 64 bytes in the VME A16 (or “short”) address space, and you can configure an additional 64 Kbytes of the A24 (or “standard”) address space.
The
PLC-5/VME processor has 8 16-bit registers accessible in the VMEbus A16 address space. A set of switches establishes the base address of these registers. These registers can be used by a VMEbus CPU to establish certain programmable configuration options of the processor, control and monitor certain low-level conditions, and send commands to the processor
The PLC-5/VME processor also has 64 KB of memory that can be enabled and mapped in the VME A24 address space. This memory is a general-purpose memory that you can use for any purpose (or not at all). If you enable it and tell the processor to do something to a VME address that happens to fall into this 64KB memory, the processor can access it without actually using VMEbus cycles. If you need some global VMEbus memory that can be accessed by the processor and another CPU, there may be performance benefits to using this 64KB of memory
.
.
Processor
1-6
Ladder programs
Processor data Files
Chapter 1
Overview
Figure 1.2 illustrates the basic forms of communications. Table 1.A summarizes these communication forms.
Figure 1.2 Basic
Forms of Communications
1
Commands sent to the processor
2
3
4
5
6
7 8
9
10 11
Read/write accesses to the processor’s A16 registers and/or the A24 memory block
Interrupt to a ladder program Interrupt signalled by a ladder program One-shot block copy into or out of processor data files
Continuous block copies into or out of processor data files Interrupt signalling command completion
Interrupt signalling completion of one block copy One-shot block copy into or out of processor data files as a
result of some commands sent to the processor VMEbus SYSRESET VMEbus SYSFAIL
VME status file
12 13
1
Required
VMEbus ACFAIL
1
Optional VMEbus system controller functions
by the PLC-5/VME processor
. Asserted by VME power supply
.
1-7
Chapter 1
Overview
T
able 1.A
Summary
of Figure 1.2
In Figure 1.2,
It means that:
when you see :
Commands are high-level directives sent to the processor from another VMEbus master, typically a controlling CPU. Commands specific to the VME processor can establish a continuous block copy to/from
1
the processor and tell the processor to which VMEbus interrupts it should respond. You can also send any PCCC via this mechanism. PCCCs are commands supported in all 1785 PLC-5 processors. You can use them to change and modify processor state, for example, or to upload and download memory files.
2
The PLC-5/VME processor responds as a VMEbus slave to certain A16 accesses (to its configuration registers) and to certain A24 accesses (to its general-purpose memory, if enabled).
You can configure the PLC-5/VME processor to respond as an interrupt handler to specified VMEbus
3
interrupt lines. When one of these interrupts occurs, the processor performs an 8-bit interrupt acknowledge cycle on the VMEbus to read an 8-bit status/ID from the interrupter. The interrupt and the status/ID value are then posted for accessibility by the ladder program.
The PLC-5/VME processor can perform as a VMEbus interrupter (sender of interrupts) in three different ways:
4
Another function available via the MSG instruction is VMEbus reads and writes. Rather than just individual
5
8- or 16-bit accesses, the function allows a block read or write to be done (i.e., of an arbitrary number of bytes). This is done between a data file in the processor and an arbitrary address range on the VMEbus. The ladder program can specify the VMEbus address space and data widths to be used.
One of the main interfaces of the 6008-LTV processor, and one preserved in the PLC-5/VME processor, is
6
the ability to predefine two block-copy operations, one into the processor data files and one out of the processor data files, to be executed automatically every scan loop. These operations are predefined to the processor via initialization commands from the CPU or from your programming software.
7
The processor can be a VMEbus interrupter signalling completion of a command. This is an option on all commands and can serve as a way to synchronize the CPU and the processor.
The processor can be a VMEbus interrupter signalling completion of each block copy operation for the
8
continuous copy operations. This is another option that allows the CPU to synchronize with the scan loop of the processor.
9
Certain standard PCCC commands cause data to be moved into and out of the processor; thus these commands represent another type of VMEbus interface between the processor and a controlling CPU.
The PLC-5/VME processor can be reset with the VME SYSRESET
10
also asserts SYSRESET responding to VMEbus accesses.
The PLC-5/VME processor asserts the VME SYSFAIL
11
completes successfully. The PLC-5/VME processor makes the state of the VME SYSFAIL available to the ladder program.
Assertion of VME ACFAIL
12
maintained in the battery-backed memory such that the processor can be restarted upon power up. Your power supply must assert ACFAIL
The PLC-5/VME processor can serve as a VMEbus slot-1 system controller. This enables the PLC-5/VME
13
processor as a single-level arbiter, a bus timeout timer, and the driver of the VMEbus 16 MHz SYSCLK signal.
1
indicates a low true signal.
from a ladder program; the ladder MSG instruction has been extended in the PLC-5/VME processor to allow a ladder program to generate a VMEbus interrupt.
signalling completion of a command (see 7). signalling a completion of each block copy operation for the continuous copy operations (see 8).
1
1
during power-up initialization until its VMEbus interface hardware is capable of
1
signal after a reset until the firmware’s self-test
1
causes the processor to halt, with integrity of the ladder program and data files
1
at least 9ms in advance of the +5VDC supply dropping beneath 4.75V.
signal. The PLC-5/VME processor
1
signal
1-8
Chapter 1
Overview

Compatibility with the Standard PLC-5 Processor

Ladder programs from a standard PLC-5 processor run in the PLC-5/VME processor. The PLC-5/VME processor has the same program scan time as the PLC-5 processor. The PLC-5/VME processor has the same extended instruction set as the PLC-5 processor.
Features of the PLC-5 processor not present in the PLC-5/VME processor are:
PIIs EEPROM memory module logical rack 0 (128 less I/O points)
Features of the PLC-5/VME processor not present in the PLC-5 processor are:
The PLC-5/VME processor defines a special data file called the “VME
status file.” This file gives ladder programs the ability to control and monitor certain VMEbus state information.
The ladder MSG instruction is extended to allow ladder programs to
perform VMEbus data transfers and generate VMEbus interrupts.
Finally, features present in both but implemented or represented differently are:
Compatibility with the 6008-L
TV Processor
The serial port (channel 0) on the PLC-5/VME processor is RS-232C
only (not configurable for RS-422 and RS-423).
Different batteries are used (cat. no. 1770-XYV).
The PLC-5/VME processor has a memory-protect switch. In the PLC-5
processor, the equivalent switch is on the 1771 I/O rack.
The PLC-5/VME processor retains a significant amount of compatibility with the 6008-LTV processor. This eases the task of converting 6008-LTV ladder programs and CPU driver programs to use with the PLC-5/VME processor.
6008-LTV ladder programs may need editing because the VME status file in the PLC-5/VME processor is different in several ways from 6008-LTV status file. The 6008-LTV ladder programs that access the VME status file will need to be changed.
1-9
Chapter 1
Overview
T
able 1.B
Comparison
Attributes 6008-LTV PLC-5/VME Comments
VME slots 3 2 Bus arbitration No Yes or No (user configurable) Single level arbiter VME master Yes Yes VME Slave Yes Yes Global memory (bytes) Programming and downloading
over backplane Saving over backplane No Yes With 6200 series software
PLC data table to global memory trans­fer method
Asserts VME SYSFAIL Yes Yes PLC resets upon VME SYSRESET Yes Yes Bus request line 0, 1, 2, 3 1, 3 Bus release ROR, RWD, ROC ROR, RWD, ROC Continuous-copy command file size 500 words 1000 words Ladder MSG file size N/A 1000 words RS-232 port No Yes Remote I/O baud rate 57.6k baud fixed 57.6k, 115.2k, 230.4k baud configurable Remote I/O fractional rack addressing No Yes
1
All
of the 6008-L
VME short memory
1
TV’
s global memory could be configured to be totally within short memory
, it can only be selected with a standard memory address. This may be a consideration when replacing a 6008-LTV with a PLC-5/VME processor
1K short, 4K short or standard 64K standard Global memory is selectable No Yes With 6200 series software
Continuous-copy command Continuous-copy and/or ladder
of 6008-LTV and PLC-5/VME Processor Attributes
release 4.4 and later
release 4.5 and later
MSG commands
. Because the PLC-5/VME processor
’s global memory would totally fill all of
.
1-10
There are some areas of potential incompatibility to consider:
The configuration/control/status/message registers are slightly different,
requiring changes to the host driver program.
The LTV VME global memory can be selected to be in short or standard
memory space. The PLC-5/VME processor’s global memory can only be selected to be in standard memory. Because of this, the 6008-LTV will accept address modifiers 2D, 3D 29 and 39. The PLC-5/VME processor will only respond to address modifiers 3D.
The 6008-LTV supports logical rack address 0; the PLC-5/VME
processor does not.
The 6008-LTV has a status/configuration bit to enable or ignore ROC
(release on clear). The PLC-5/VME processor will always respond to ROC.
Chapter 1
Overview
The PLV-5/VME processor status files in the processor status area are
different in several ways.
When floating point values are converted to integer, they are rounded
differently. 6008-LTV rounds 0.5 to the next highest integer, the PLC-5/VME processor rounds to the nearest even integer.
CPU driver programs are affected in these ways:
The low-level protocol for how commands are given to the processor
and how command-sending errors are reported is significantly different. However, the higher-level interfaces (e.g., the commands themselves) are compatible.
The manner in which the VME setup interface parameters are
configured is significantly different:
In the: The information is in the:
PLC-5/VME processor configuration registers in the A16 space. 6008-LTV processor “Slave 0” global memory in the A16 space.
See chapter 3 for more information.
1-11
Installation
Chapter
2
Chapter
Objectives
Compliance to European Union Directives
Read this chapter to learn how to set the switches in your PLC-5/VME processor and install it into a VMEbus chassis.
See the Classic 1785 PLC-5 Programmable Controller Hardware Installation Manual, publication 1785-6.6.1 for more information about installing PLC-5 family processors.
If this product has the CE mark it is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives.

EMC Directive

This product is tested to meet Council Directive 89/336/EEC Electromagnetic Compatibility (EMC) and the following standards, in whole or in part, documented in a technical construction file:
EN 50081-2EMC – Generic Emission Standard, Part 2 – Industrial
Environment
EN 50082-2EMC – Generic Immunity Standard, Part 2 – Industrial
Environment
This product is intended for use in an industrial environment.

Low Voltage Directive

This product is tested to meet Council Directive 73/23/EEC Low Voltage, by applying the safety requirements of EN 61131–2 Programmable Controllers, Part 2 – Equipment Requirements and Tests.
For specific information required by EN 61131-2, see the appropriate sections in this publication, as well as the following Allen-Bradley publications:
Industrial Automation Wiring and Grounding Guidelines For Noise
Immunity, publication 1770-4.1
Enhanced and Ethernet PLC-5 Programmable Controller User
Manual, publication 1785-6.5.12
Guidelines for Handling Lithium Batteries, publication AG-5.4
Automation Systems Catalog, publication B111
2-1
Chapter 2
Installation

Handling the Processor

Wrist strap
19897

Setting the Switches

The processor is shipped in a static-shielded container to guard against electrostatic damage. Electrostatic discharge can damage integrated circuits or semiconductors in the processor module if you touch backplane connector pins. It can also damage the module when you set configuration plugs or switches inside the module. Avoid electrostatic damage by observing the following precautions.
Remain in contact with an approved ground point while handling the
module (by wearing a properly grounded wrist strap).
Do not touch the backplane connector or connector pins.
When not in use, keep the module in its static-shielded container.
Before installing the PLC-5/VME processor, you need to make some decisions about its configuration and operation and set the switches on the circuit board accordingly. You need to know:
DH+ station (node) number
Memory protection—whether you want the processor’s program
RAM protected
Memory protect
DH+ station number
12345678
SW1 set of switches
Power­up Test
Up (off)
Down (on)
Location of configuration registers in VMEbus A16 address space
System controller—whether you want the processor to serve as the
VMEbus slot-1 system controller
VMEbus request level—whether you want the processor to request
access to the VMEbus at level 3 or level 1
Figure 2.1 Switch
Location
Front plate
SW1
Bottom
SW2
Table 2.A and Table 2.B describe the switch settings for SW1.
19502
2-2
Chapter 2
Installation
T
able 2.A
SW1
Set of Switches
Switches 1-6 Switch 7 Switch 8
DH+ station number for channels 1A and 0 (see Table 2.B)
T
able 2.B
Station
Numbers SW1 (Switches 1-6)
Station
Number
(Octal)
1
2 3 4 5 6
0 on on on on on on 1 off on on on on on 2 on off on on on on 3 off off on on on on
.
.
.
.
.
.
. . .
77 off off off off off off
Unused (off) Memory protect.
If on, RAM memory protect is enabled.
LSD MSD
. . .
. . .
. . .
. . .
Table 2.C and Table 2.D describe the switch settings for SW2.
T
able 2.C
SW2
Set of Switches
Switches 1-3 Switch 4 Switch 5 Switch 6 Switch 7 Switch 8
A16 address range of the configuration registers.
See Table 2.D.
Important: Switch 6 is meaningful only if switch 4 is off.
1
SW2,
position 7,
now
self-references as it did before series C, revision K. If you set SW2, position 7 to ON (down position), then the POST test will skip all VME self-references, causing the following ef – The PLC-5 processor cannot test its bus-master hardware. – The PLC-5 processor cannot determine its own unique logical address and assumes its ULA is F0H regardless of how you set SW2, positions 1–3. – The VME status file ULA field (word 1, bits 3-15) will always contain 000, regardless of how you set SW2, positions 1–3.
If on, the processor functions as the VMEbus system controller, and no other VME cards should attempt to be the system controller.
Important: The PLC-5/VME processor must be in the left-most slot of the VME chassis.
See page 3-1 for a description of the system controller.
controls whether the PLC-5 processor makes a VME self-reference in its POST test. If you set SW2, position 7 to OFF (up position), then the VME will make
Unused (off)
VMEbus request level. If switch 4 is OFF, switch 6 on defines
Unused (off)
the bus request level as 3. If switch 6 is OFF, the bus request level is 1.
If switch 4 is ON, the bus request level is 3 independent of the setting of switch 6.
Unused
1
(off)
fects:
2-3
Chapter 2
Installation
System controller
Unused (off)
Request level
Unused
A16 address range
12345678
SW2 set of switches
(off)
Unused (off)
Up (off)
Down (on)
T
able 2.D
Address
Range SW2 (Switches 1-3)
1
ULA
1 2 3 A16 Address Range
0 on on on FC00-FC3F (hex) 1 off on on FC40-FC7F 2 on off on FC80-FCBF 3 off off on FCC0-FCFF 4 on on off FD00-FD3F 5 off on off FD40-FD7F 6 on off off FD80-FDBF 7 off off off FDC0-FDFF
1
Unique
Logical Address is used by the 6200 series programming the
software to determine the A16 base address
PLC-5/VME processor’s registers..
of
Configuring
the VME
Backplane Jumpers
Five backplane jumpers
Left connector
Backplane
Right connector
The VMEbus contains several daisy-chained control signals. Almost all VMEbus backplanes contain jumpers for these control signals to allow systems to operate with empty slots. Failing to install these jumpers properly is a common source of problems in configuring a new VMEbus system.
There are five jumpers per VME slot, one for each of the four bus-grant arbitration levels and one for the interrupt-acknowledge daisy chain. Depending on the backplane manufacturer, the jumpers can be on the rear pins of the J1 connector or alongside it on the front of the backplane. The PLC-5/VME processor uses two slots. Based on what is in the VME slot, install or remove the backplane jumpers as follows:
VME Slot Content Five Backplane Jumpers
PLC-5/VME processor’s left slot Remove PLC-5/VME processor’s right slot Install Empty slot Install Other VME module Consult manufacturer’s literature
Note: Consult manufacturer’s literature.
2-4
Other VME module
PLC-5/VME processor
Empty
CPU
Chapter 2
Installation
Inserting
the Processor
into a Chassis
You insert the PLC-5/VME processor in two adjacent slots in a 6U (full-height) VMEbus chassis.
ATTENTION: Make sure that your VME system is powered off. The PLC-5/VME processor is not designed to be inserted or removed from a live system.
ATTENTION: Avoid touching the circuit board and connectors.
After sliding the processor into the VME chassis using its cardguides, use firm pressure on the top and bottom handles of the processor to make its P1 connector fit firmly into the connector on the backplane. Tighten the screws in the top and bottom of the front panel to prevent your PLC-5/VME processor from loosening.

Grounding

19556
Allen-Bradley makes specific recommendations for properly grounding its racks so that their operation is as safe and error-free as possible. VME systems, on the other hand, may have no formal specifications for grounding the VME chassis frame. Allen-Bradley recommends that you ground the VME chassis frame and that you connect the logic ground (common) of the VME power supply to the chassis frame’s earth ground.
2-5
Chapter 2
Installation
The specific procedure for grounding a VME chassis varies depending on the style of the chassis. Read the instructions found in the Classic PLC-5 Family Programmable Controllers Installation Manual, publication 1785-6.6.1 for information on how Allen-Bradley racks are grounded, and try to ground your VME chassis frame in a similar way.
ATTENTION: If you are using a PLC-5/V40L processor, your VME power supply should not float with respect to earth ground. Connect the power supply’s logic ground (common) for the 5V supply before connecting the PLC-5/40L processor to a 1771-ALX adapter. Also, use a single point of ground between the VME chassis and the extended-local I/O system to ensure proper performance.

Determining Power-Supply Requirements

Connecting to Remote I/O

The PLC-5/VME processor draws 4 A (maximum)—3.2 A (typical)—from the VME power supply. The processor also monitors the ACFAIL signal on the backplane to determine when the +5 VDC supply is within tolerances. The VME power supply must assert ACFAIL at least 9 ms in advance of the +5 VDC supply dropping beneath 4.75V or memory corruption and processor fault occurs. Therefore, make sure that your power supply has ACFAIL capability.
You must use a Safety Extra Low Voltage (SELV)- or Protected Extra Low Voltage (PELV)-certified power supply with the VME processor to comply with Low Voltage directive requirements.
Use Belden 9463 twin-axial cable (cat. no.1770-CD) to connect devices to a remote I/O link. To connect a remote I/O link, do the following:
To connect a remote I/O link, you must: See page:
Make sure the cables are the correct length 2-6 Prepare the cable 2-7 Make the remote I/O connections 2-7 Terminate the link 2-8
2-6

Make Sure that You Have Correct Cable Lengths

Verify that your system’s design plans specify remote I/O cable lengths within allowable measurements.
Chapter 2
Installation
A remote I/O link using this communication rate: Cannot exceed this cable length:
57.6 kbps 3,048 m (10,000 ft)
115.2 kbps 1,524 m (5,000 ft)
230.4 kbps 762 m (2,500 ft)

Prepare the Cable

Cut the cable according to the lengths you need. Route the cable to the devices.

Make Remote I/O Connections

Use Figure 2.2 when connecting the remote I/O cable to PLC-5 processors and remote I/O adapter modules.
2-7
Chapter 2
Installation
Figure 2.2 Remote
I/O Terminal Connectors
To connect remote I/O cable, do the following:
1. Run the cable (1770-CD) from the processor to each remote I/O adapter module or processor in the remote I/O system.
2. Connect the signal conductor with blue insulation to the 3-pin connector terminal labeled 1 on the processor and to each remote I/O adapter module (or PLC-5 adapter) in the remote I/O system.
3. Connect the signal conductor with clear insulation to the 3-pin connector terminal labeled 2.
4. Connect the shield drain wire to the 3-pin terminal labeled SH.
5. Tie wrap the remote I/O network cable to the chassis to relieve strain
on the cable.
Blue Shield
Chan 0
Blue Shield Clear
Chan 2
PLC-5/V40B
Processor channel must be configured for remote I/O communication.
Clear
Remote I/O Terminal Connectors
1771-ASB Remote I/O Adapter Module
1 Line 1 2 Shield 3 Line 2 4 Line 1 5 Shield 6 Line 2 7 No Connection 8 No Connection 9 No Connection 10 No Connection 11 In 12 Ret
Cable Cable for
daisy-chain configuration
Reset

Terminate the Link

For proper operation, terminate both ends of a remote I/O link by using the external resistors shipped with the programmable controller. Use either a 150W or 82W terminator.
Remote I/O Terminal Connectors
Chan 1
PLC-5/V40L
Blue Shield Clear
19539
2-8
If your remote I/O link: Use this resistor rating: The maximum number of
operates at 230.4 kbps operates at 57.6 kbps or 115.2 kbps and no
devices listed in Table 2.A are on the link
82
W
physical
devices you
can connect on the link
32 16
The maximum number of racks you can scan on the link
Loading...
+ 245 hidden pages