M0 0054 WDPF

Table of Contents
Section Title Page
Section 1. Introduction
1-1. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1-2. Contents of this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1-3. Additional Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Section 2. Remote Q-Line Overview

2-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2-2. Definitions of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2-3. Purpose of Remote Q-Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2-4. Features of Remote Q-Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2-5. Remote I/O Subsystem DIOB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2-6. Redundant Controller Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Section 3. Hardware Configuration and Installation

3-2. Hardware Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3-3. DIOB Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-3.1. HW Record Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
3-3.2. RIO Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3-4. MRC Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3-4.1. MRC Jumper Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
3-4.2. MRC Status Indication LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3-4.3. Port Connection Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3-5. QRC Card (4256A26) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
3-5.1. QRC Jumper Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3-5.2. DIOB Address Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
3-5.3. Hexadecimal Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3-5.4. DIOB Address Switch Setting Examples . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
3-5.5. QRC RIOB Addressing Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
3-6. QOR Card (3A99257). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
3-6.1. QOR Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3-6.2. Placing the MAUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
3-6.3. Connecting the Fiber-Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3-6.4. Connecting the AUI Cable (5A26147) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
3-6.5. Remote Node Addressing Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
2/00 i M0-0054 (Rev 2)

Westinghouse Proprietary Class 2C
Table of Contents, Cont’d
Section Title Page
Section 4. Cabinets and Cabling

4-2. Remote I/O Enclosure (Remote Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-2.1. Cabinets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4-2.2. Wiring, Knockouts, and Grounding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
4-2.3. Card Crate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4-3. Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4-4. Copper Wire Communications Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4-4.1. TRC Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4-5. Copper Cable Communications Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4-6. Fiber-Optic Cable Communications Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4-6.1. Installing Fiber-Optic Communications Cable . . . . . . . . . . . . . . . . . . . . . 4-17
4-6.2. Fiber-Optic Cable Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
4-6.3. Fiber-Optic Cable Integrity Test Procedure . . . . . . . . . . . . . . . . . . . . . . . 4-19
4-6.4. Fiber-Optic Cable Termination Procedure. . . . . . . . . . . . . . . . . . . . . . . . . 4-22
4-6.5. Fiber-Optic Cable Splicing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4-6.6. Optical Power Loss Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4-7. QFR Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
4-7.1. QFR Jumper Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4-7.2. Slot Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4-7.3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4-8. TFR Panel Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4-9. Fiber-Optic Extension Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
4-9.1. Remote Node Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Section 5. Remote Q-Line Specifications

5-2. Operating Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5-3. Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5-3.1. Master Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
5-3.2. Remote Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
5-4. Single Crate Remote Enclosure, Weight and Dimensions . . . . . . . . . . . . . . . . . . . . 5-7
5-5. Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Appendix A. Invalid QRC Switch Settings

A-1. QRC Invalid Switch Setting Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
M0-0054 (Rev 2) ii 2/00

Table of Contents, Cont’d
Section Title Page
Appendix B. MRC Status Algorithm

B-1. MRC Status Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C. Remote Node Temperature Compensation

C-1. Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C-2. Half-Shell/Terminal Assembly Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C-3. RTD Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
C-4. On-Card Compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
2/00 iii M0-0054 (Rev 2)

Summary of Changes
This revision of “Remote Q-Line Installation Manual” (M0-0054) has been updated
to include the following:
• Information about the new QOR card. This card replaces the QRC card in
WDPF Remote Node cabinets when remote Q-Line I/O is migrated to Ovation.
In a migrated system, the QOR card will interface to the Ovation Controller
which replaces the DPU Controller.
2/00 Changes-1 M0-0054 (Rev 2)

Section 1. Introduction
1-1. Overview
Westinghouse Distributed Processing Family (WDPF) is a distributed control
system that provides modulating control, sequential control, and data acquisition
for a variety of system applications. The WDPF system consists of a variable mix
of functional units (drops) that communicate on the WDPF Data Highway.
Two WDPF drop styles, DPU and TCU, interface to the customer process. The DPU
(Distributed Processing Unit) and the TCU (Total Control Unit) drops use Q-Line
process I/O printed circuit cards to receive and send data for the WDPF system.
These Q-Line I/O printed circuit cards are housed in one or more Q-crates.
Each DPU or TCU drop contains a functional processor card. The functional
processor contains circuitry to permit it to transfer byte data to and from the drop’s
Q-Line I/O cards. The parallel data path that links the Q-Line cards to the functional
processor is identified as the Distributed I/O Bus (DIOB).
The DPU and TCU drops will support either one DIOB (DIOB1) or two separate
DIOBs (DIOB1 and DIOB2). To add a second (expansion) DIOB (DIOB2) to a
DPU or TCU drop, an “AX” expansion cabinet is placed adjacent to the DPU or
TCU drop’s “A” cabinet. The “AX” cabinet houses Q-crates and I/O card power
supplies, but does not contain a Multibus chassis. The MBU card is added to the
DPU or TCU drop to provide the functional processor with a parallel interface to
DIOB2.
DIOB length restrictions prevent Q-Line I/O cards from being located outside the
confines of an “A” cabinet or an “AX” expansion cabinet. Some customer
applications require that some Q-Line I/O cards be in close proximity to the process
being monitored or controlled. Since many of these locations do not require a large
number of Q-Line I/O cards, locating an entire drop “A” cabinet at these sites is not
cost effective. For these situations, WDPF Remote Q-Line I/O Subsystem (RIO)
can be physically separated from the drop “A” cabinet.
WDPF Remote Q-Line I/O is a cost effective hardware and software solution for
distributing Q-Line I/O cards to strategic locations or nodes throughout a plant, thus
reducing I/O cabling costs. The RIO subsystem provides redundant serial
communications between a master node and remote nodes, via either twisted pair
metallic conductors or duplex fiber-optic cables.
The WDPF Remote Q-Line I/O subsystem employs a serial, multi-node

communications architecture. In this case, a “node” is defined as a location where
RIO communications cabling is terminated. A “master” node is located within a
DPU or TCU drop. “Remote” nodes contain Q-Line I/O cards.
2/00 1-1 M0-0054 (Rev 2)

1-2. Contents of this Document
1-2. Contents of this Document

This document explains the installation, configuration and usage of remote
Q-Line cards.
Topics addressed include:
Section 1. Introduction covers an overview of WDPF, DPU and TCU drops, the
DIOB, and Remote Q-Line I/O.
Section 2. Remote Q-Line Overview details specific features and usage of Remote
Q-Line I/O cards.
Section 3. Hardware Configuration and Installation covers setting jumpers and

switches to achieve desired hardware requirements.
Section 4. Cabinets and Cabling details capabilities and set-up requirements for
both copper and fiber-optic cabling.
Section 5. Remote Q-Line Specifications covers overall system power

requirements, and gives physical dimensions and capabilities of various system
components.
Appendix A. Invalid QRC Switch Settings gives several examples of why various
switch settings are incorrect.
Appendix B. MRC Status Algorithm describes optional software for checking the
status of an MRC card.
Appendix C. Remote Node Temperature Compensation describes various

hardware options for temperature compensation.
M0-0054 (Rev 2) 1-2 2/00

1-3. Additional Reference Documents
1-3. Additional Reference Documents

Table 1-1 lists additional reference documentation which may be helpful while
using this document.
Table 1-1. Reference Documents
Document
Number Title Description
M0-0003 Self-Test Diagnostics Lists the WDPF System fault codes.
M0-0053 Q-Line Installation Manual Provides descriptions and installation
instructions for Q-Line I/O cards.
M0-8000 WDPF System Planning and Provides descriptions and installation
Highway Installation Manual instructions for the WESTNET Data
Highway
M0-8005 Drop Installation Manual Describes the installation of Multibus-
based drops.
In addition to the documents listed in Table 1-1, this manual may refer to
“applicable vendor documentation” which is defined on a project basis.
2/00 1-3 M0-0054 (Rev 2)

Section 2. Remote Q-Line Overview
2-1. Section Overview

The following topics are addressed in this section
• Definitions of terms (Section 2-2).
• Purpose of remote Q-line (Section 2-3).
• Features of remote Q-line (Section 2-4).
• Remote I/O subsystem DIOB configuration (Section 2-5).
• Redundant applications (Section 2-6).
2/00 2-1 M0-0054 (Rev 2)

2-2. Definitions of Terms
2-2. Definitions of Terms

AMI Alternate Mark Inversion (AMI) coding produces alternate positive
and negative level pulses, symmetric about 0 volts, when successive
binary ones occur in sequence. AMI is a three level (ternary) signal,
where a binary one is represented by a positive-going or negative -
going pulse in a signal interval.
FPGA Field Programmable Gate Array (FPGA) is a configurable IC that
can be programmed by the designer to perform one or more specific
functions on the card on which the FPGA is located.
DIOB The Distributed Input/Output Bus (DIOB) is a collection of parallel
electrical conductors that link Q-Line I/O cards to a DPU/TCU drop
DIOB controller. With the addition of the WDPF Remote Q-Line I/O
subsystem, this form of DIOB is also known as a Local DIOB.
DPU Distributed processing unit (DPU). The DPU is a WDPF drop whose
Functional Processor uses floating point and ladder logic
co-processors to perform data acquisition, modulate control
functions, and sequential control functions.
Drop A station on the WDPF Westnet II Data Highway. Each WDPF drop
contains its own local processing unit (Functional processor), a Data
Highway Communications controller, and shared memory that is
used to pass data between the Functional Processor and the Data
Highway Communications controller.
Master Node The Master Node is the Remote Q-Line I/O subsystem node that
controls all serial data communications with the remote node(s). The
Master Node is physically located within the DPU or TCU drop’s
cabinet. It houses the Remote Q-Line I/O subsystem’s
communications controller.
Q-Line The Q-Line is a family of Westinghouse process I/O printed circuit
cards. These printed circuit cards provide the WDPF system with the
ability to accumulate and disseminate data. The DPU and TCU
drops use Q-Line I/O printed circuit cards.
Remote Node A Remote Node is a Remote Q-Line I/O subsystem node which
contains one or more Q-Line I/O cards and an RIOB controller.
RIOB A Remote Input/Output Bus (RIOB) contains one or more remote
nodes connected to a master node.
TCU Total Control Unit (TCU). The TCU is a WDPF drop that combines
the functional characteristics of both continuous and batch control
within a single controller. The TCU drop enables WDPF users to
implement complex batch, sequential, and other advanced control
applications.
M0-0054 (Rev 2) 2-2 2/00

2-3. Purpose of Remote Q-Line
2-3. Purpose of Remote Q-Line

The WDPF Remote Q-Line I/O subsystem allows Q-Line I/O cards to be located
outside the confines of an “A” cabinet or an “AX” expansion cabinet. A redundant
serial communications link connects remote Q-Line I/O cards to a DPU1 or TCU
drop. The serial communications link consists of two channels, a primary channel
(Channel A or Channel 1) and a secondary channel (Channel B or Channel 2).
This serial interface to remote Q-Line I/O cards is identified as a “remote” DIOB or
RIOB. In contrast, those Q-Line cards that communicate with the DPU or TCU via
a parallel interface are referred to as “local” or DIOB.
Note
Adding an RIOB to a DPU or TCU drop does

not increase the drop’s DIOB addressing
ability. DPU or TCU drops are still limited to
controlling a maximum of two DIOBs
(DIOB1 and DIOB2) with a maximum of 244
addresses on each DIOB.
1. If the WDPF system is migrated to an Ovation system, the DPU chassis will be replaced by an Ovation
Controller chassis. Consult your Westinghouse representative for details.
2/00 2-3 M0-0054 (Rev 2)

2-4. Features of Remote Q-Line
2-4. Features of Remote Q-Line

Remote Q-Line provides the following features:
• Allows DPU/TCU drops the flexibility to support one or two local DIOBs, one
or two RIOBs, or one local DIOB and one RIOB.
• Distribution of an RIOB’s Q-Line I/O cards among one or more remote nodes.
• Two styles of redundant serial communications medium are available:
— shielded twisted copper wire pairs
— optical fiber
• Add-on kits for a DPU or TCU drops for RIO subsystem capability.
• Single or multiple Q-crate remote nodes.
• Each RIOB supports up to eight remote nodes with shielded twisted copper wire
pair serial communications media using a “daisy-chain” system configuration.
• Each RIOB supports up to four remote nodes with fiber optic serial
communications media using a radial or “star” system configuration.
M0-0054 (Rev 2) 2-4 2/00

2-5. Remote I/O Subsystem DIOB Configuration

DPU or TCU drops support one or two DIOBs as shown in Table 3-1. The Remote
Q-Line I/O Subsystem allows one or two remote DIOBs to be added to a DPU or
TCU drop. DPU or TCU drops also support one or two local DIOBs. The Q-Line
I/O cards of the first local DIOB are housed in the DPU or TCU drop’s cabinet. The
second local (expansion) DIOB’s Q-Line I/O cards are housed in Q-crates mounted
in an AX cabinet, which is located adjacent to the DPU or TCU cabinet.
The remote DIOB Q-Line I/O cards are housed in Q-crates located in enclosures
that are physically separated from the DPU or TCU drop’s cabinet. These
enclosures (remote nodes) may house a single Q-crate (Westinghouse part
5D32134) or up to four Q-crates.
Figure 2-1 shows a dual remote DIOB Remote Q-Line I/O Subsystem with copper
wire serial communication channels. Each remote DIOB has four remote nodes that
each contain a single Q-crate.
Figure 2-2 shows a single remote DIOB Q-Line I/O subsystem with copper wire
serial communications channels and a multiple crate remote node. There is no local
DIOB.
Figure 2-3 shows a redundant DPU/TCU drop that has a local DIOB and a remote
DIOB that use twisted copper wire pairs.
2/00 2-5 M0-0054 (Rev 2)

Remote
Remote DIOB2
DIOB1
TRC TRC
Q-Line Q Q
I/O Cards R Q-Line I/OR
C Redundant DPU/TCU C
I/O I/O
Termination Termination
TRC
Panel
M S D M S D
R F M H R F M H
TRC P P TRC
C C C C
Q-Line Q
R
Q-Line QR
I/O Cards C I/O Cards C
I/O I/O
TRC TRC
Q-Line Q Q
R Q-Line R
I/O Cards C I/O Cards C
I/O I/O
FP=Functional Processor
SM=Shared Memory
DHC=Data Highway
Controller
TRC Panel TRC Panel
Q-Line Q Q
R Q-Line R
I/O I/O
C C
I/O I/O
Remote Nodes Remote Nodes
Figure 2-1. Twisted Wire Pairs - Dual Remote DIOBs. Multiple Remote Nodes
M0-0054 (Rev 2) 2-6 2/00

Remote Node
Master Node
I/O Power
Supplies
TRC Panel
TRC Panel
M F S D M F S D
R P M H R P M H
C C C C
Q
Q-Line R
I/O Cards C
Redundant
(DPU or TCU)
Drop
Q-Line Q
I/O Cards B
E
FP = Functional Processor Q
SM = Shared Memory Q-Line B
DHC = Data Highway Controller I/O Cards E
Figure 2-2. Twisted Wire Pairs - Remote DIOB Multi-Crate Single Remote Node
2/00 2-7 M0-0054 (Rev 2)

TRC
Q
Q-Line I/O R
C
I/O
Termination
Master Node
TRC
Q
Q-Line I/O R
C
I/O
Termination
TRC Panel
M D M D TRC
F S F S
R H R H
P M P M Q
C C C C Q-Line I/O R
C
Q I/O
B Termination
Q-Line I/O E
Local DIOB
Q-Line I/O Q
Local DIOB B
E TRC
Q
Q-Line I/O R
Q-Line I/O Q C
B
Local DIOB E
I/O
Termination
Remote Nodes
Figure 2-3. Remote Q-Line Combination Local/Remote I/O
M0-0054 (Rev 2) 2-8 2/00

2-6. Redundant Controller Applications
2-6. Redundant Controller Applications

When an RIO subsystem is added to redundant DPU/TCU drops, an MRC must be
added to the Multibus I chassis of both DPU/TCU drops. A fourteen conductor
cross-connect flat cable assembly links the J3 cross-connect headers of the two
MRC cards. The MRC cards’ redundancy control logic and cross-connect cable
assembly work in conjunction with the functional processors’ redundancy logic and
cross-connect cable assembly to specify which DPU/TCU drop is the primary drop
and which DPU/TCU drop is the backup drop. Only one MRC may control access
to the redundant DPU/TCU drops’ RIOB(s) at any given time.
2/00 2-9 M0-0054 (Rev 2)

Section 3. Hardware Configuration and
Installation

This section addresses the following topics:
• Hardware overview (Section 3-2).
• DIOB addressing (Section 3-3).
• MRC card (Section 3-4).
• QRC card (Section 3-5).
• QOR card (Section 3-6).
2/00 3-1 M0-0054 (Rev 2)

3-2. Hardware Configuration Overview
3-2. Hardware Configuration Overview

The major components that make up the RIO (Remote I/O) system are as follows:
• MRC (Multibus Remote I/O Controller) circuit board
• QRC (Q-Line Remote Controller) circuit board
• QOR (Q-Line to Ovation Remote Controller) circuit board
• TRC Panel Assembly (twisted wire pairs termination)
All RIO subsystems contain at least two main printed circuit card styles (MRC and
QRC/QOR) and a serial communications medium. Figure 3-1 shows the three most
commonly used RIO printed circuit cards.
MRC
Profile
QRC QOR
Profile Profile
Figure 3-1. Basic RIO Card Outlines
M0-0054 (Rev 2) 3-2 2/00

3-3. DIOB Addressing

Each DIOB allows a maximum of 244 card edge connector addresses for Q-Line I/O
cards. The 244 allowable hexadecimal DIOB card edge addresses range from 08H to
FBH. These DIOB addressing restrictions apply to both local and RIOB installations.
Note that some Q-Line I/O cards, such as QAVs and QAXs, require more than one
DIOB card edge connector address. Refer to “Q-Line Installation Manual”
(M0-0053) for additional information pertaining to Q-Line I/O cards and their
addressing.
3-3.1. HW Record Field

For analog and digital process point record considerations, the HW record field is
user initialized for points read from or written to the field I/O (Q-Line I/O cards).
For a point read from or written to a DIOB Q-Line I/O card, the HW field indicates
the byte offset from the beginning of the DIOB address space where the pertinent
point resides. This offset value depends on the card edge connector address, the
relative point number (PN) on the (analog points only), and which DIOB (DIOB1
or DIOB2) that the Q-Line I/O resides in.
For analog points, HW is calculated as follows:
HW = 2[ADDR + (PN - 1)] + MBU
where
HW = Hardware offset field (3 digit hexadecimal value)

ADDR = Card edge connector address (in hexadecimal)
PN = Relative point number on the (starts at 1)
MBU = DIOB2 offset. MBU = 0 for DIOB1. MBU = 200H for DIOB2
For digital points, HW is calculated as follows:
HW = 2[ADDR] + MBU
where
HW = Hardware offset field (3 digit hexadecimal value)

ADDR = Card edge connector address (in hexadecimal)
MBU = DIOB2 offset. MBU = 0 for DIOB1. MBU = 200H for DIOB2
2/00 3-3 M0-0054 (Rev 2)

As a result, DIOB1 is accessed by HW field offset addresses 000H through 1FFH

and DIOB2 is accessed by HW field offset addresses 200H through 3FFH.
3-3.2. RIO Subsystem

When an RIO subsystem is implemented, a DPU or TCU drop may use a
combination of a local DIOB and an RIOB or it may use RIOBs (one or two)
exclusively. Table 3-1 illustrates the only possible DIOB configurations.
Table 3-1. DIOB Configurations
DIOB1 DIOB2
Local None
Remote a None
Local Local
Remote b Remote
Local c Remote
a. DPU Functional Processor EPROMs for this DIOB configuration typically have R1 added to their labels.
b. DPU Functional Processor EPROMs for this DIOB configuration typically have R1R2 added to their
labels.
c. DPU Functional Processor EPROMs for this DIOB configuration typically have L1R2 added to their
labels.
M0-0054 (Rev 2) 3-4 2/00

3-4. MRC Card
3-4. MRC Card

The MRC (Multibus Remote I/O Controller) is housed in the DPU drop’s Multibus
I chassis. The MRC provides a serial communications interface to one or two
RIOBs. When an RIO subsystem is added to a DPU or TCU drop, that drop is
identified as the master node for the RIO subsystem’s RIOB(s), since the drop
houses the MRC card. Figure 3-2 shows the outline and general configuration of an
MRC card.
J3 Connector
R88
J2 Connector
R82
R64
R56
J1 Connector
JS8
JS10
JS7
JS6
JS9
JS12(3)
JS3,4,5
P1 Multibus I
Connector
JS2 JS1
Figure 3-2. MRC Card
2/00 3-5 M0-0054 (Rev 2)

3-4. MRC Card
3-4.1. MRC Jumper Configuration

The MRC contains seven 2-position headers (JS1, JS2, and JS6 through JS10), one
3-position header (JS12), and three 5-position headers (JS3, JS4, and JS5). Some of
these jumpers must be relocated to define various RIO subsystem configurations.
Table 3-2 list the possible jumper configurations. Figure 3-2 shows all jumper and
connector locations on an MRC card. Figure 3-3, an enlargement of a portion of the
MRC board, shows the factory installed jumper settings for the MRC card:
JS7
2 1
1 2
1 2
1 2
JS8 JS9 JS10
1 2
JS5
JS6
JS4
1 2 3 4 5
JS3
JS12
3 2 1
JS2 JS1
2 1
1 2
Figure 3-3. MRC Standard Jumper Settings
M0-0054 (Rev 2) 3-6 2/00

3-4. MRC Card
Table 3-2 is a guide to the MRC card’s user-configurable and factory set jumpers:
Table 3-2. MRC User Configurable and Factory Set Jumpers
Factory Set
Jumpers
DPU/TCU (DO NOT
Drop’s CHANGE)
JS1
RIOB J1 Port J2 Port JS6 JS2
Communications JS12 Jumper Jumper JS7 JS9
DIOB1 DIOB2 Medium Jumper Position Position JS8 JS10
Remote None Copper Posts 2, 3 JS3-1, JS4-1 JS4-2, JS5-2 In Out

Remote None Fiber Posts 1, 2 JS3-1, JS4-1 JS4-2, JS5-2 In Out
Remote Remote Copper Posts 2, 3 JS3-1, JS4-1 JS4-2, JS5-2 In Out
Remote Remote Fiber Posts 1, 2 JS3-1, JS4-1 JS4-2, JS5-2 In Out
Local Remote Copper Posts 2, 3 JS3-5, JS4-5 JS4-2, JS5-2 In Out
Local Remote Fiber Posts 1, 2 JS3-2, JS4-2 JS4-5, JS5-5 In Out
Local None No MRC No MRC No MRC No MRC
needed. N/A
Local Local No MRC No MRC No MRC No MRC
needed.
Remote Local Not allowed Not allowed Not allowed Not allowed
None Remote Not allowed Not allowed Not allowed Not allowed
MRC cards (Revision level U or later) have sockets installed at component locations
R56, R64, R82, and R88 (see Figure 3-2). When placed in the following RIO fiber-
optic subsystem master nodes, these MRC cards have four capacitors installed in
the sockets as specified below.
Master Node Style Number MRC Capacitors - Locations R56, R64, R82, R88
3A59345G02, 3A59345G04, 1000 pF 10% 100V, Multilayer Ceramic, axial leads
3A59345G06, 3A98752G02, (Westinghouse Part Number 669A521H13)
3A98752G04, 3A98752G06
3A59345G05, 3A98752G01, (Westinghouse Part Number 669A521H14)
3A98752G03, 3A98752G05
2/00 3-7 M0-0054 (Rev 2)

3-4. MRC Card
3-4.2. MRC Status Indication LEDs

The MRC contains twenty red LED indicators mounted near the front edge of the
printed circuit card. The LEDs are arranged in three groups as shown in Figure 3-4.
LE1 LE3 LE5 LE7 LE9 LE11 LE13 LE15 LE17 LE18 LE19 LE20
Accessing
J2 Port
Remote
Processor DIOB
LE2 LE4 LE6 LE8 LE10 LE12 LE14 LE16 Alive
Accessing
Remote J1 Port
LEDs 1-8 Show Display DIOB Remote
LEDs 9-16 are Diagnostic
Register State of Bits Interface DIOB
(Note: LEDs 10 and 12 are Enabled
0-7, Respectively
Never Illuminated).
Figure 3-4. MRC LED Arrangement
The drop’s functional processor controls the state of the MRC card’s Display
register. Normally, if the drop is functioning correctly, all eight MRC Display
register LEDs are continuously illuminated
Note
If the drop has one local DIOB and one

RIOB, the MRC card’s display register LEDs
will NOT be lit.
M0-0054 (Rev 2) 3-8 2/00

3-4. MRC Card
Table 3-3 describes the meaning of lit/unlit for the various LEDs:
Table 3-3. MRC LED Display
LED Condition
Number
Lit Unlit
LE9 The MRC PC card’s microcontroller is Microcontroller is not functioning
functioning correctly. correctly.
User Action: None required. User Action: Replace the MRC card.
LE11 The MRC PC card’s serial Flashing steadily if the U46 FPGA has
communications controller FPGA (U46) not been properly configured.
has been properly configured. User Action: Replace the MRC card.
User Action: None required.
LE13 The RIOB assigned to the MRC PC Either there is no MRC-J1 to TRC J2
card’s J1 communications port has been communications cable attached to the
correctly configured. MRC card’s J1 communications port,
User Action: None required. OR
the RIOB assigned to the J1
communications port is not correctly
configured
User Actions: If LE14 is not lit, no action
is required. If LE14 is lit, check the
following:
1. MRC-J1 to TRC-J2 cable.
2. Serial communications channel
connections.
3. Remote node power status.
4. Remote node QRC card edge address
limits (SW1 and SW2 settings).
LE14 The RIOB assigned to the MRC PC Either there is no RIOB card assigned to
card’s J1 communications port has not the MRC card’s J1 communications port,
been correctly configured, or neither of OR
the J1 or J2 ports has cables attached. the RIOB assigned to the J1
User Actions: If an RIOB is assigned to communications port has been correctly
the J1 communications port, check the configured.
following: User Action: None required.
connections.
2/00 3-9 M0-0054 (Rev 2)

3-4. MRC Card
Table 3-3. MRC LED Display (Cont’d)
LE15 The RIOB assigned to the MRC PC Either there is no MRC-J2 to TRC J2
card’s J2 communications port has been communications cable attached to the
correctly configured. MRC card’s J1 communications port,
User Action: None required. OR
the RIOB assigned to the J2
communications port is not correctly
configured
User Actions: If LE16 is not lit, no action
is required. If LE16 is lit, check the
following:
connections.
LE16 Either the RIOB assigned to the MRC PC MRC card attached to the J2 port is
card’s J1 communications port has not functioning correctly.
been correctly configured, Cables are attached to both J1 and J2.
OR User Action: None required.
neither of the J1 or J2 ports has cables
attached.
If neither the J1 nor the J2
communications ports has cables
attached, both LE14 and LE 16 are lit.
LE13 and LE15 are unlit.
User Action: If an RIOB is assigned to
the J2 communications port, check the
following:
connections.
M0-0054 (Rev 2) 3-10 2/00

3-4. MRC Card
Table 3-3. MRC LED Display (Cont’d)
LED Condition
Number
Lit Unlit
LE17 (ALIVE) The drop’s functional processor The WDPF drop’s functional processor is
is continuously pulsing the MRC card’s not pulsing the MRC card’s ALIVE timer
ALIVE timer to prevent a timer timeout. and the time has timed out.
User Action: None required. User Action: Check the operation of the
card’s functional processor. Replace the
MRC card if necessary.
LE18 (ENABLE) The WDPF drop has enabled The WDPF drop is in backup mode and
the MRC card to access the Q-Line cards will not permit the MRC card to access
in the RIOB(s) assigned to the MRC card. the Q-Line cards in the RIOB(s) assigned
User Action: None required. to that MRC card.
User Action: No action required
LE19 The WDPF drop’s functional processor is Either there is no RIOB assigned to the
actively accessing the address space of MRC cards J1 communications port,
the RIOB assigned to the MRC card’s J1 OR
communications port. The number of the the WDPF drop is in Backup mode.
RIOB may not match the name of this User Action: None required unless there
LED as stenciled on the pc card. is an RIOB assigned to the J1
User Action: None required. communications port and the WDPF
drop is in Control Mode. In this case, try
replacing the MRC card.
LE20 The drop’s functional processor is Either there is no RIOB assigned to the
accessing the address space of the RIOB MRC cards J2 communications port,
assigned to the MRC card’s J2 OR
communications port. The WDPF drop’s the WDPF drop is in Backup mode.
functional processor’s operating program User Action: None required unless there
may cause this LED to be lit even if there is an RIOB assigned to the J2
is no RIOB assigned to the MRC card’s communications port and the WDPF
J2 communications port. drop is in Control Mode. In this case, try
User Action: None required. replacing the MRC card.
2/00 3-11 M0-0054 (Rev 2)

3-4. MRC Card
3-4.3. Port Connection Guidelines

The DIOB-MRC connections are detailed in Table 3-4:
Table 3-4. Port Connections for Local and RIOB
Configuration J1 Header Connected to J2 Header Connected to

Single RIOB DIOB1 N/A
Dual RIOB DIOB1 DIOB2
DIOB1 Local and DIOB2 N/A DIOB2
Remote, (copper wire)
DIOB1 Local and DIOB2 DIOB2 N/A
Remote, (fiber-optic)
Mixed Remote, 1 copper and DIOB1 for fiber-optic. DIOB2 for copper wire.
1 fiber-optic
Note: For the Mixed Remote (copper and fiber-optic), JS12 on the MRC card must have posts 1
and 2 shorted together. See Figure 3-3 and Table 3-2.
M0-0054 (Rev 2) 3-12 2/00

3-5. QRC Card (4256A26)
3-5. QRC Card (4256A26)

The QRC is a Q-Line that performs the following tasks:
• Serial communication with the MRC card.

• Q-Line I/O interface.
• DIOB extender to interface Q-Line I/O cards located in adjacent Q-crates.
• Performs address range recognition.
• All of the QBE functions (the QRC will replace the QBE in the first RIOB
Q-crate). QBE Functions include:
— Distributed I/O Bus extension to multiple Q-Crates.
— Distributed I/O Bus voltage discharge of data lines.
— Distributed I/O Bus voltage level clamping.
Each RIO subsystem remote node contains a QRC card (see Figure 3-5), which is
housed in the rightmost slot of the Q crate (slot usually occupied by a QBE card).
Fuse JS6
F1 LE1
Power &
Fuse OK
P1
MSB J2
SW1 Remote
DIOB LSB
P2 Transmit
Connector MSB Connector
SW2
JS4 JS5 LSB
JS3 Extended
J3
DIOB
JS2 Connector
R94
Serial
R95 Communications
Connector
Figure 3-5. QRC Basic Card and Jumper Configuration
One QRC card is installed at every remote Q-Line node. It provides a redundant
serial link to the DPU, plus the drivers and receivers necessary to interface with
Q-Line I/O cards. In multiple Q-Crate remote nodes, the QRC also provides the link
to the QBE cards located in the additional Q-Crates. The QRC card also contains
switches to define the range of applicable addresses for a particular remote node.
2/00 3-13 M0-0054 (Rev 2)

3-5. QRC Card (4256A26)
3-5.1. QRC Jumper Configuration

The plug-in jumpers located on the QRC card headers JS3 and JS4 are installed in
the factory as shown in Figure 3-6. No jumper comes installed on header JS5.
JS4 JS5
XMIT REC
123
REC XMIT
321
JS3
Figure 3-6. QRC User Configured Jumpers
Note
Jumpers JS3 and JS4 should be modified only

if a remote node contains both QAI and QTB
cards.
Table 3-5 details the various modifications required for the applicable arrangement
and number of cards.
Table 3-5. QRC User Configured and Factory Set Jumpers
Factory Set
Number of
Q-Crates in JS6
the Remote QRC and QTB card JS3 Jumper JS4 Jumper JS2 Jumper Jumper
Node Compatibility Setting Setting Setting Setting
1 If QRC and QTB XMIT (pins 1, 2) XMIT (pins 1, 2) Pins 1, 2 Pins 1, 2
are in the same Q- or or
Crate, set jumpers Removed. Removed.
JS3 and JS4.
M0-0054 (Rev 2) 3-14 2/00

3-5. QRC Card (4256A26)
Table 3-5. QRC User Configured and Factory Set Jumpers (Cont’d)
Factory Set
Number of
Q-Crates in JS6
the Remote QRC and QTB card JS3 Jumper JS4 Jumper JS2 Jumper Jumper
Node Compatibility Setting Setting Setting Setting
2 or more If QRC and QTB REC (pins 2, 3) REC (pins 2, 3) Pins 1, 2 Pins 1, 2
are in different Q-
Crates, set jumpers
JS3 and JS4.
2 or more If QRC and QTB XMIT (pins 1, 2) XMIT (pins 1, 2) Pins 1, 2 Pins 1, 2
are in same Q-
Crate, set jumpers
JS3 and JS4.
Figure 3-7 illustrates the position of the factory set JS2 jumper.
JS2
1 2
Figure 3-7. QRC Jumper JS2 (Do Not Change)
2/00 3-15 M0-0054 (Rev 2)

3-5. QRC Card (4256A26)
Figure 3-8 illustrates the position of the factory set JS6 jumper.
JS6
123
Figure 3-8. QRC Jumper JS6 (Do Not Change)
QRC cards (Revision level K or later) have sockets installed at component locations
R94 and R95 (see Figure 3-5). When placed in the following RIO fiber-optic
subsystem slave remote nodes, these QRC cards have two capacitors installed in the
sockets as specified below.
Remote Node Style Number QRC Capacitors - Locations R94 and R95
3A59333G01 (Westinghouse Part Number 669A521H14)
M0-0054 (Rev 2) 3-16 2/00

3-5. QRC Card (4256A26)
3-5.2. DIOB Address Switches

Each remote node must be assigned a DIOB card edge connector address range. The
244 usable DIOB card edge connector addresses range from 08H to FBH. (Note that
all DIOB addresses are given as hexadecimal).
Each remote node’s DIOB card edge connector address range is configured by
setting a pair of eight position DIP switches (SW1 and SW2) located near the front
edge of the remote node’s Q-Line Remote Controller (QRC). (Figure 3-5 shows the
location of these switches).
SW1 specifies the remote node’s highest assigned DIOB address.

SW2 specifies the remote node’s lowest assigned address.
DIOB Address Rules
• When setting the remote nodes’ QRC SW2 and SW1 DIP switches, all
addresses must be consecutive.
• On multiple node RIOBs:
— No gaps between addresses are permitted.
— No address overlaps are permitted.
• In each RIOB, each of the 244 allowable DIOB I/O card edge connector
addresses (08H through FBH) must be assigned to one of the remote nodes.
• The SW1 switch setting (the highest assigned DIOB address) must be greater
than or equal to the SW2 switch setting (the remote node’s lowest assigned
address).
2/00 3-17 M0-0054 (Rev 2)

3-5. QRC Card (4256A26)
3-5.3. Hexadecimal Conversion

To set the DIOB address switches, determine the binary equivalent of the
hexadecimal base address (see Table 3-6).
Table 3-6. Hexadecimal to Binary Conversion
Hexadecimal Decimal Binary Hexadecimal Decimal Binary

Digit Equivalent Equivalent Digit Equivalent Equivalent
0 0 0000 8 8 1000
1 1 0001 9 9 1001
2 2 0010 A 10 1010
3 3 0011 B 11 1011
4 4 0100 C 12 1100
5 5 0101 D 13 1101
6 6 0110 E 14 1110
7 7 0111 F 15 1111
The bits 1- 8 determine the SW1 and SW2 switch settings (0 = open, 1 = closed).
For example, the binary and decimal equivalents for hexadecimal values 52H is
shown below:
First, convert from 52H = 82 (Decimal) = 0 1 0 1 0 0 1 0 (Binary)

hexadecimal
Switch Number 8 7 6 5 4 3 2 1
MSB LSB
Then, set corresponding O O O O O O O O

switch positions f n f n f f n f
f f f f f
See Figure 3-5 and Figure 3-9 for switch locations
M0-0054 (Rev 2) 3-18 2/00

3-5. QRC Card (4256A26)
3-5.4. DIOB Address Switch Setting Examples

If a switch is open, the corresponding DIOB card edge connector
address bit = logical 0. If a switch is closed, the corresponding DIOB card edge
connector address bit = logical 1.
SW1 selects the remote node’s highest assigned DIOB card edge connector address.
SW2 selects the remote node’s lowest assigned DIOB card edge connector address.
Table 3-7. DIOB Address Setting, QRC Card

SW1 or SW2 DIOB Card Edge Connector
Switch Number Address Bit
8 7
Most Significant Bit (MSB)
7 6
6 5
5 4
4 3
3 2
2 1
1 0
The following tables show the settings required to set a range of addresses for an
RIO subsystem remote node. The block of connector addresses assigned to the
DIOB card edge range from 58H through 9AH. The QRC’s SW2 and SW1 switches
are set as follows:
Table 3-8. Sample Switch Setting
SW2 Switch Number Switch State SW1 Switch Number Switch State
8 Open (0) 8 Closed (1)
7 Closed (1) 7 Open (0)
6 Open (0) 6 Open (0)
5 Closed (1) 5 Closed (1)
4 Closed (1) 4 Closed (1)
3 Open (0) 3 Open (0)
2 Open (0) 2 Closed (1)
1 Open (0) 1 Open (0)
2/00 3-19 M0-0054 (Rev 2)

3-5. QRC Card (4256A26)
As a reference, SW2 switch

number 8 is shown in the “up”
position.
Low Address High Address
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Up = Open SW2 SW1
Up = Logic 0
Least Most L M
Significant Significant S S
Bit Bit B B
Figure 3-9. Remote Node (QRC) DIOB Address Selection
M0-0054 (Rev 2) 3-20 2/00

3-5. QRC Card (4256A26)
3-5.5. QRC RIOB Addressing Examples

Table 3-9 through Table 3-16 show low and high addresses for 1 through 8 remote
nodes.
Table 3-9. Single Remote QRC Node a
Remote Node Number Low Address High Address

1 08H FBH
a. This configuration is the QRC default setting.
Table 3-10. Two Remote QRC Nodes

1 08H 5FH
2 60H FBH
Table 3-11. Three Remote QRC Nodes

1 08H 2FH
2 30H A7H
3 A8H FBH
Table 3-12. Four Remote QRC Nodes

1 08H 7FH
2 80H 9FH
3 A0H CFH
4 D0H FBH
2/00 3-21 M0-0054 (Rev 2)

3-5. QRC Card (4256A26)
Note
With more than four remote nodes using

shielded copper wire pairs, the total length of
the communications cable assemblies must
be 600 meters (1,968 feet) or less.
Table 3-13. Five Remote QRC Nodes

1 08H 2FH
2 30H 77H
3 78H 9FH
4 A0H CFH
5 D0H FBH
Table 3-14. Six Remote QRC Nodes

1 08H 1FH
2 20H 37H
3 38H 57H
4 58H 7FH
5 80H BFH
6 C0H FBH
M0-0054 (Rev 2) 3-22 2/00

3-5. QRC Card (4256A26)
Table 3-15. Seven Remote QRC Nodes

1 08H 27H
2 28H 47H
3 48H 6FH
4 70H A7H
5 A8H CFH
6 D0H E7H
7 E8H FBH
Table 3-16. Eight Remote QRC Nodes

1 08H 1FH
2 20H 2FH
3 30H 47H
4 48H 9FH
5 A0H BFH
6 C0H CFH
7 D0H DFH
8 E0H FBH
2/00 3-23 M0-0054 (Rev 2)

3-6. QOR Card (3A99257)
3-6. QOR Card (3A99257)

When a WDPF Q-Line system is migrated to an Ovation system, the installed
Q-Line I/O cards can then communicate with an Ovation Controller. Typically, to
accomplish this, a Migration Team will install an Ovation Controller chassis into a
WDPF DPU chassis and make any other necessary modifications.
If a WDPF system that contains Remote Q-Line I/O is migrated, the QRC cards that
are housed in the WDPF remote nodes must be replaced with QOR cards. These
cards are then connected to Ovation Remote I/O Media Attachment Units (MAUs),
which are connected to PCRR cards in the Ovation Controller (see Figure 3-10).
WDPF DPU
Power Supply Rack
F4 OUT 2
TB1 TB3
(PRI) (SEC)
L(+) OFFON OFFON 1

0 1 0 1
N(-) F5
PRI 2
3
SEC
L(+)
F6
4 Power Cable Assembly
N(-)
5 (I/O Adapter to Power Supply Rack)
OUTPUT 2OUTPUT 1 INPUT OUTPUT 2OUTPUT 1 INPUT 6
TB2 TB4
Primary Backup
Controller Controller Ovation I/O Adapter
PCPS Converter
PCPS Converter
Optional Card 3
Optional Card 3
Attachment Unit Base with
Primary and Backup MAU
PCRR Card
PCRR Card
Processor
Processor
modules installed 1
(Used for Remote Nodes
1 through 4)
NIC
NIC
AUI Cables
Q-Crate Q1
62.5 Micron
optical fibers
with ST optical
connectors
Q-Crate Q2
Q-Crate Q3 QQ
Q-Line OO
I/O Cards RR
1 A second Attachment Unit Base I/O

is needed for remote nodes 5 through 8. Q-Crate Q4 2 Termination
2 DPU cabinet may contain up to four Q-Crates.
3 PCRR or PCQL card can be used. Remote Node
for Q-Line I/O
DPU Cabinet
Figure 3-10. DPU Cabinet after Migration
M0-0054 (Rev 2) 3-24 2/00

3-6. QOR Card (3A99257)
3-6.1. QOR Description

Each remote node in a migrated system contains a QOR card (see Figure 3-11) in
the rightmost slot of the Q-Crate (formerly occupied by a QRC card).
The QOR provides a redundant serial link to the Controller, plus the drivers and
receivers necessary to interface with Q-Line I/O cards. In multiple Q-Crate remote
nodes, the QOR also provides the link to the QBE cards located in the additional
Q-Crates.
There are no jumpers installed on the QOR card. Removable jumpers are used only
for factory testing. The QOR card contains eight status LEDs (described in Table
3-17) and a remote node address switch (described in Section 3-6.5).
LE1 Power OK
Status LEDs LE1 Communications OK
LE3 External Error
P1 34-Position DIOB Backplane
Card-Edge Connector LE4 Internal Error
Remote Node Optical Transmitter

Controller ST Receptacle J1 TX
Circuit One
Optical Receiver J2 RX
ST Receptacle
RS-232 Serial Port

RJ-45 Jack J3
SW2
(Position 0 is
illustrated) 50-Position DIOB Extension P2
Card-Edge Connector
POS. NODE
0 1
NODE 1 2
ADDRESS 2 3 NOTE:
SELECTION 3 4 DO NOT
SWITCH 4 5 SELECT
5 6 POS. 8 or 9
6 7
7 8
RS-232 Serial Port
RJ-45 Jack J4
Optical Transmitter TX
Remote Node ST Receptacle J5
Controller
Circuit Two Optical Receiver J6 RX
ST Receptacle
LE5 Power OK
LE6 Communications OK
Status LEDs
LE7 External Error
LE8 Internal Error
Figure 3-11. Illustration of QOR Card
2/00 3-25 M0-0054 (Rev 2)

3-6. QOR Card (3A99257)
The QOR card performs the following tasks:
• Serial communication with the Ovation Controller.

• Q-Line I/O interface.
• Performs remote node address assignment.
• All of the QBE functions (the QOR will replace the QBE in the first Q-crate).
QBE Functions include:
— Distributed I/O Bus voltage discharge of data lines.

— Distributed I/O Bus voltage level clamping.
— DIOB extender to interface Q-Line I/O cards located in adjacent Q-crates.
QOR LEDs
The following table describes the eight LEDs on the QOR card (see Figure 3-11).
Table 3-17. QOR LEDs
LED Description
LE1, LE5 (Green) Power OK. Lit if the remote node controller circuit’s power supply output voltage
level is above a minimum acceptable level.
LE2, LE6 (Green) Communications OK. Lit if the Ovation Controller is periodically accessing the
QOR remote node controller circuit.
LE3, LE7 (Red) External Error. Normally unlit. Lit if QOR remote node controller circuit’s receiver
optical input power level is too low or if the optical input signal transitions are too
infrequent.
LE4, LE8 (Red) Internal Error. Normally unlit. Lit if one or more of these conditions are true:
- Ovation Controller has forced a QOR remote node controller circuit internal
error condition.
- QOR remote node controller circuit has detected a self-test error.
- Ovation Controller has stopped accessing the QOR remote node

controller circuit.
M0-0054 (Rev 2) 3-26 2/00

3-6. QOR Card (3A99257)
3-6.2. Placing the MAUs

An MAU (Figure 3-12) consists of an Attachment Unit Base (AUB) and up to two
MAU modules. An MAU module is made up of an Electronics module and a
Personality module. Typically, an MAU contains two MAU modules, one
connected to the Primary Controller PCRR and the other connected to the Backup
Controller PCRR.
Media Attachment Unit

Personality
Modules
Media Attachment Unit (with
Electronics Modules channels)
Power 1 2 3 4 1 2 3 4 Power
R T R T R T R T R T R T R T R T
Fiber-Optic Transmit/Receive
A-Side TWI Connector Pairs B-Side TWI
Connector Connector
P3 P5
AUI Cable Connectors
Attachment Unit Base
Figure 3-12. Media Attachment Unit (MAU)
The MAUs (up to two) are located in a migrated WDPF DPU cabinet. The MAU
bases (AUB 1 and AUB 2) are two separate Attachment Unit Bases which may be
located anywhere in the DPU cabinet (space permitting). One AUI cable connects
AUB 1 P3 (see Figure 3-12) to P1 on the Primary Controller PCRR (see Figure 3-
14), and a second AUI cable connects AUB 1 P5 to P1 on the Backup Controller
PCRR.
If there are two MAUs in the cabinet, one AUI cable connects AUB 2 P3 to P2 on
the Primary Controller PCRR. A second AUI cable connects AUB 2 P5 to P2 on the
Backup Controller PCRR.
2/00 3-27 M0-0054 (Rev 2)

3-6. QOR Card (3A99257)
3-6.3. Connecting the Fiber-Optic Cable
Procedure
Use the following procedure to connect the MAU channels (see Figure 3-13) and
the corresponding QOR card in a Q-Line remote node:
1. Use duplex fiber optic cable that meets the specifications provided below.
2. Connect the Primary Controller MAU module to the QOR Circuit One optical
ports (see Figure 3-13).
3. Connect the Backup Controller MAU module to the QOR Circuit Two optical
ports (see Figure 3-13).
4. Be sure to connect the MAU TX ports to the QOR RX ports, and connect the
MAU RX ports to the QOR TX ports.
5. Set the specific switch settings on the QOR card as described in Section 3-6.5.
Fiber Optic Cable Specifications
The following physical layer specifications are provided as guidelines for the
optical link between the MAU channels and the WDPF remote Q-Line QOR:
• Ethernet 10 BASE-FL using two multi-mode optical fibers, each with a 62.5
micron fiber optic core and a 125 micron outer cladding.
• Optical wave length: 820/850 nanometers.
• Optical connectors: ST (BFOC/2.5) Spring-loaded bayonet and connector.
• Maximum link optical loss: 10 dB
• Data transmission rate: 10 Mbits/sec
• Maximum link length: 2000 meters (6560 feet).
M0-0054 (Rev 2) 3-28 2/00

3-6. QOR Card (3A99257)
Remote Node
Controller AUI Cable (5A26147) to AUB 1
Circuit One Primary Controller PCRR P1
RX1
Optical Transmitter
ST Receptacle J1 TX TX1
Optical Receiver J2 RX RX2

ST Receptacle
TX2
P3
RX3
TX3
RX4
SW2
Position 2 is TX4
illustrated
(selects remote QOR 62.5 Micron Optical
Fiber with ST Optical
node address 3) Card Connectors
POS. NODE
0 1
NODE 1 2 RX1
ADDRESS 2 3 NOTE:
SELECTION 3 4 DO NOT
SWITCH SELECT TX1
4 5
5 6 POS. 8 or 9
6 7 RX2
7 8
TX2
P5
RX3
Optical Transmitter TX
ST Receptacle J5
TX3
Optical Receiver J6 RX
ST Receptacle RX4
TX4
Remote Node
Controller
Circuit Two AUI Cable (5A26147) to
Backup Controller PCRR P1
Figure 3-13. Typical QOR Connection to MAU (Optical Link)
2/00 3-29 M0-0054 (Rev 2)

3-6. QOR Card (3A99257)
3-6.4. Connecting the AUI Cable (5A26147)

The Attachment Unit Interface (AUI) cable in the DPU cabinet is used to connect
P1 and P2 (see Figure 3-14) on the PCRR card to an Attachment Unit Base. The
MAU modules contain transceivers that translate signals between the PCRR and the
fiber-optic media that is used to connect remote nodes to the Controller.
P1 is the 15-pin D-connector on the PCRR closest to the front edge of the card
where the LEDs are displayed. Controls and communication signals for nodes 1-4
are accessible through P1 on the PCRR.
P2 is the 15-pin D-connector on the PCRR closest to the back edge of the card.
Control and communication signals for nodes 5-8 are accessible through P2 on the
PCRR.
One PCRR provides two ports for AUI cables. The AUI cable connects the PCRR
to the Attachment Unit Base whose MAU modules provide the receive and transmit
ports for the fiber-optic cables. Both AUI ports are used on a single PCRR if the
PCRR is to control more than four remote nodes. This configuration requires two
AUI cables per PCRR card.
M0-0054 (Rev 2) 3-30 2/00

3-6. QOR Card (3A99257)
si oll f
s er
ha tr o
C on nt
C ro
F
LEDs on Front of
PCRR Card
(with cover)
s
si
ha
rC
lle
AUI cable connects P1 to

tro
on
an Attachment Unit Base . AUI cable connects P2 to

fC
ro
This controls Remote an Attachment Unit Base .

ea
R
Nodes 1 - 4. This controls Remote

P1 Nodes 5 - 8.
P2 is located behind P1
Figure 3-14. AUI Connections on PCRR Card
2/00 3-31 M0-0054 (Rev 2)

3-6. QOR Card (3A99257)
3-6.5. Remote Node Addressing Switch

A Controller PCRR card can control up to eight remote nodes. A 10-position rotary
switch (located on a QOR card) is used to assign a node address to the remote node.
Note
Each remote Q-Line node is assigned all 244

possible DIOB addresses (08H through
FBH).
Positions 0-7 on the switch assign the lowest-to-highest order remote node from an
addressing standpoint. Selecting position 8 or 9 on the switch is the same as
assigning position 0 or 1, respectively, to a remote node.
The remote node must be connected to a specific channel of the Controller cabinet’s
MAU so that the PCRR communication signals can be directed to the proper node.
Similarly, the AUI cable connecting the MAU to the PCRR must be connected to a
specific port on the PCRR.
The following table lists the control path for a PCRR controlling eight remote nodes
through two MAUs.
Table 3-18. Remote Node Addressing Switch
Remote PCRR Port MAU QOR Remote Node’s
Node for AUI Cable Channel Rotary Switch Setting
1 P1 AUB 1 - channel 1 0
Do not use. 8 or 9
1 Optional for migration projects.
M0-0054 (Rev 2) 3-32 2/00

Section 4. Cabinets and Cabling

• This section addresses:
• Remote I/O enclosure (Section 4-2)
• Communications (Section 4-3).
• Copper Cable communications links (Section 4-4).
• Copper cable communications medium (Section 4-5).
• Fiber-optic cable communications links (Section 4-6).
• QFR card (Section 4-7).
• TFR panel assembly (Section 4-8).
• Fiber-optic extension subsystem (Section 4-9).
2/00 4-1 M0-0054 (Rev 2)

4-2. Remote I/O Enclosure (Remote Node)
4-2.1. Cabinets
RIO subsystem remote nodes may either be housed in a standard quad cabinet, or
in the Single Q-Crate (12-Slot) Remote I/O Enclosure (5D32134). This enclosure
was designed specifically for use in RIO subsystems. This steel enclosure is
designed to meet the NEMA 3R specification which provides a degree of protection
(limited time period) against windblown dust, rain, sleet, and external ice
formation. It is designed to be mounted on a wall or on a panel using six 3/8 inch
mounting bolts. Figure 4-1 shows the exterior of an RIO cabinet. A single front door
with a locking latch allows front access to the inside of the enclosure. The cabinet
mounts on the backplane, with three upper and three lower fasteners.
228.6 mm 228.6 mm
(9 in) (9 in)
744.2 mm
(29.3 in)
800.1 mm
(31.5 in)
Westinghouse
REMOTE I/O
431.8 mm
(17 in)
Figure 4-1. Remote I/O Cabinet
M0-0054 (Rev 2) 4-2 2/00

4-2.2. Wiring, Knockouts, and Grounding

The bottom surface of the enclosure has three sets of knockouts.
• The first group of two knockouts is located near the rear of the enclosure
adjacent to the AC distribution center’s AC input terminal block. These two
knockouts are designed to accommodate 1/2 inch box connectors or 1/2 inch
conduit and are to be used to bring in the enclosure’s AC power wiring.
• A second group of four knockouts is located near the front right corner of the
enclosure. Like the first group of knockouts, these four knockouts are designed
to accommodate 1/2 inch box connectors or 1/2 inch conduit. These conduits are
intended for use with the RIO subsystem serial communication cables. Either
twisted pair cable assemblies or duplex fiber-optic cable assemblies may be
accommodated. In addition to the box connectors or conduit, 1/2 inch cord
fittings (such as Crouse-Hinds CGB116) may be used with these knockouts.
• The third group of twelve knockouts is intended for use with the enclosure’s
Q-Line I/O card field wiring. The base knockouts are designed to accommodate
3/4 inch conduit. If required, conduit up to 1 1/2 inch diameter may be used if a
hole punch is used to enlarge the holes formed by the removal of these
knockouts.
• Refer to the “Grounding Requirements” section of “WDPF System Planning

and Highway Installation Manual” (M0-8000) for grounding requirements for
WDPF system drops. M0-8000 states that all WDPF grounds must be within
one ohm of true earth ground and within one ohm of each other at 25 degrees
Celsius. This requirement also applies to the single Q-Crate Remote I/O
enclosure (hereafter known as enclosure) ground connections.
M0-8000 specifies the recommended hardware required to make Multibus-

based drop ground connections. Based on this information, use a No. 4 AWG
(or larger) insulated welding cable (Westinghouse style No. 2428A71H01 or
equivalent) terminated with a No. 10 ring terminal (AMP No. 33114 or
equivalent) to connect each enclosure to true earth ground.
The customer grounding connection to the enclosure is made to an internal

copper bus bar. A metal AC distribution panel assembly is located inside the
enclosure in the lower left-hand side. Near the rear of the enclosure, a copper
bus bar is bolted to the top surface of the AC distribution panel assemble. The
grounding cable must terminate on this copper bus bar.
2/00 4-3 M0-0054 (Rev 2)

A bus bar 10-32 x 0.625 thread forming screw (Westinghouse style number
406A146H01) is used to fasten the grounding cable’s ring terminal to the copper
bus bar. The bottom surface of the enclosure has three separate groups of
knockouts. A group of four 0.875 inch diameter knockouts is located near the
front right-hand side of the enclosure. An entry path for the grounding cable is
obtained by removing one of these knockouts and installing a 1/2 inch box
connector in its place.
Note
This data applies only to the Part Number

5D32134 single Q-Crate enclosure.
(Right Side, w/ fans)

= 22.23 mm (0.875 in) 355.6 mm
dia. inward knockout (14 in)
= 28.17 mm (1.109 in)

dia. inward knockout
50.8 mm
(2.0 in)
31.8 mm
(1.25 in)
71.1 mm (2.8 in) 431.8 mm

(17.0 in)
71.1 mm (2.8 in)
71.1 mm (2.8 in)
71.1 mm (2.8 in)
71.1 mm (2.8 in)
76.2 mm 63.5 mm 177.8 mm

(3.0 in) (2.5 in) (7.0 in)
203.2 mm
(Not to Scale) (8 in)
Figure 4-2. Knockouts, RIO Cabinet, Bottom View
M0-0054 (Rev 2) 4-4 2/00

4-2.3. Card Crate

The Remote I/O enclosure contains the following:
• Single 12-slot Q-Line I/O card crate
• Metal terminal panel that can accommodate twelve terminal blocks
• AC power distribution center
• Slide-out power supply tray containing the primary and backup +12.75 V
Q-Line I/O card power supplies
• Auxiliary power supply options.
The enclosure’s Q-crate can typically house up to twelve Q-Line I/O cards in
addition to the QRC card. There is a limit to the number of QAX cards that may be
located within the enclosure. Each QAX card requires two terminal block positions
of the enclosure’s twelve available terminal blocks, so a maximum of six QAX
cards may be placed within the enclosure. Terminal blocks to Q-Line I/O card edge
connector assemblies are added to the enclosure according to the Q-Line I/O cards
specified.
Two add-on kits are available to be used to add the hardware necessary to use either
twisted pair or fiber-optic serial communications links.
• The 3A59332 add-on kit provides an interface to twisted pair serial

communications channels. A TRC panel assembly is used for physical
connections.
• The 3A59333 add-on kit provides an interface to fiber-optic communications

channels. A TFR panel assembly that contains two QFR cards is used for
physical connections to the fiber-optic communications channel.
2/00 4-5 M0-0054 (Rev 2)

4-3. Communications
4-3. Communications
The RIO subsystem consists of one or more remote nodes linked to a master node (a
WDPF DPU or TCU drop). To simplify the RIO subsystem wiring and to reduce wiring
costs, all communications between the master node and the remote nodes are performed
using serial data transmission.The master node’s MRC card converts parallel data
received from the functional processor into serial data. The serial data is encoded for
transmission on the communications channels. Upon arrival at the remote nodes, the
serial data is converted back to parallel data by the remote nodes’ QRC cards.
If the Q-Line I/O card being accessed is within the node’s address range, the QRC card
performs a DIOB cycle. If the DIOB cycle is a read operation, the QRC card converts
the parallel DIOB data read from the addressed Q-Line I/O card into serial form. A reply
message is transmitted. If the DIOB cycle is a write cycle, the QRC card transmits a
short acknowledgment reply message. Upon arrival at the master node, the incoming
reply message serial data is converted to parallel form by the MRC card. The MRC card
then acknowledges completion of the DIOB operation to the DPU or TCU drop’s
functional processor.
The RIO subsystem redundant serial communication channels may be implemented

with shielded twisted copper wire pairs or duplex fiber-optic cables. One copper wire
pair or one fiber is used to transmit data continuously from the MRC card in the master
node. The other copper wire pair or fiber transmits reply message data from the QRC
card to the master node’s MRC card using time division multiplexing. The second or
redundant communications channels performs an identical task. If one communications
channels is broken or is disconnected, master node-remote node communications may
continue using just the second communications channel.
The standard WDPF RIO subsystem uses copper wire pairs as its communications
medium. Standard RIO subsystem signaling is similar to the 1.544 MHz T1 digital
carrier system used by the telephone company. Serial binary NRZ data (two voltage
levels, 0 volts and 5 volts) is encoded using Alternate Mark Inversion (AMI) coding.
There are several advantages obtained with AMI signaling when copper wire
communications media is implemented:
• Most of the energy of bipolar signals is concentrated at frequencies of about half

of the pulse repetition frequency (1.544 MHz for the T1 carrier, 1.600 MHz for
the RIO subsystem carrier).
• No DC component is present, permitting transformer coupling of the bipolar
AMI coded data to the twisted copper wire pairs to be implemented.
• The AMI alternating pulse pattern may be used for error detection.
• Inexpensive copper wire pairs may be used as the communications media.
• The clock may be regenerated from the received data.
M0-0054 (Rev 2) 4-6 2/00

4-4. Copper Wire Communications Links
4-4.1. TRC Panel

This 19-inch rack mounted panel is one rack unit high (44.5 mm (1.75 in)) and
provides screw terminations for the twisted pair field communications links. The
field communication links are then transitioned to ribbon cable connectors via the
TRC, a passive circuit board mounted on the rear of the termination panel. A ribbon
cable connects the TRC to either the MRC or the QRC, depending on the type of
node. This termination panel is available in several configurations and is used in
both remote nodes and master nodes.
REMOTE I/O TERMINATION PANEL

DIOB1 DIOB2
J1 MRC/QRC MRC/QRC
CHANNEL A CHANNELB CONNECTOR J1 CHANNEL A CHANNELB CONNECTOR
J2 J2
JS1 1 2 3 4 5 6 7 8 9 10 JS1 1 2 3 4 5 6 7 8 9 10
MASTER 1
R4 R5 TRC1 MASTER 1 R4 R5 TRC2
REMOTE 2 R6 R7
REMOTE 2 R6 R7
3 3
(Not to Scale)
Figure 4-3. TRC Panel
Every RIO subsystem that use twisted pair communications links contains a TRC
Panel Assembly (4D33730) in each node (master and remote). Additional panel
configurations are listed in Table 4-1 and Table 4-2.
Table 4-1. TRC Panel Configurations
Master Node Configuration (DPU/TCU) TRC Panel Part Number

DIOB1 and DIOB2 Two TRC boards, 4D33730G02
Only DIOB1 4D33730G01
Only DIOB2 4D33730G03
2/00 4-7 M0-0054 (Rev 2)

Table 4-2. TRC Panel Configurations, Groups 1 and 3
Group Number TRC Board Position, Number

Group 1 DIOB1, 4D33730G01
Group 3 DIOB2, 4D33730G03
A twenty conductor cable assembly links the TRC board’s J2 communications

header to an MRC (J1 or J2) or QRC (J3) card communications header.
Warning
The TRC board contains four 150 ohm 1%

0.25 watt termination resistors (R4, R5,
R6, & R7) that are mounted in spring
sockets. These resistors are factory
installed in every TRC board and must be
removed from all TRC panels that are not
in the master node or in the remote node at
the far end of the twisted pair
communications link.
The copper wire pair cable assemblies are routed in sequential “daisy-chain”
fashion from the master node (DPU or TCU drop) to the nearest remote node and
then on to the next remote node until all of the remote DIOB’s remote nodes are
connected to the serial communications channel. See Figure 4-4.
M0-0054 (Rev 2) 4-8 2/00

Note:
Plug-in Resistors TRC Panel
R4-R7 must be Q-Line
Q
R
removed from the C
I/O
TRC board Termination
for all remote

nodes except for the
farthest remote node.
TRC Panel
Q
Q-Line CardsR
C
I/O
Termination
Remote
TRC Panel Nodes
TRC Panel
Q
M D Q-Line Cards R
F S
R H C
P M
C C
I/O
Termination
Master Node TRC Panel

(DPU or TCU Drop)
Q
Q-Line Cards R
C
FP=Functional Processor
SM=Shared Memory
DHC=Data Highway Controller I/O
Termination
Figure 4-4. Serial Connection of Copper Cabling (Single Remote DIOB)
2/00 4-9 M0-0054 (Rev 2)

4-5. Copper Cable Communications Medium

Each RIO subsystem copper wire communications channel consists of a cable
assembly that meets the requirements of the IBM Part number 4716748 Type 1
cable. The equivalent Westinghouse part number is 3A98653.
• This cable assembly consists of four polyethylene insulated copper 22 AWG

solid conductors arranged in two parallel pairs.
• Each wire pair is foil shielded.
• An overall braid shield of tinned copper surrounds the two wire pairs.
• The overall braid shield is formed into a conductor and is also terminated with
a number 6 ring lug.
• The Westinghouse cable assembly is available in groups where the lengths
range from 3 meters (~10 feet) to 1,000 meters (3,280 feet).
Note
The minimum recommended length of 3A98653

cable between the master node and the closest remote
node is 30 meters (100 feet).
• One twisted pair transmits serial data; the other twisted pair receives serial data.
• The serial data is transmitted in a differential format and is transformer coupled
to the twisted pair communications channel.
When the RIO subsystem serial data is being transmitted, one twisted pair transmits
data (XMIT, XMIT/). The other twisted pair receives data (RCV, RCV/). The
WDPF RIO subsystem remote DIOB twisted pair cable assemblies are routed in a
serial “daisy-chain” fashion from the master node to the remote node(s). No radial
routing of the twisted pair communications cable is permitted from the master node
to the remote nodes.
The maximum allowable overall length of the shielded copper twisted pair
communications channel, from the master node to the furthest remote node, is
dependent on the number of remote nodes. Table 4-3 defines the maximum cable
length for various node quantities.
Table 4-3. Remote Node Number and Cable Length Maximums
Remote Node Qty. Max. Cable Length

1-4 1000 meters (3280 feet)
5-8 600 meters (1968 feet)
M0-0054 (Rev 2) 4-10 2/00

The TRC board’s TB1 terminal block interfaces the twisted pair communications
media to the RIO subsystem master and remote nodes. The master node TRC board
and the TRC board located in the remote node farthest from the master node will
terminate two cable assemblies (one cable assembly for Channel A and one cable
assembly for Channel B) at their TB1 terminal block (see Figure 4-5). In these
locations, each terminal on TB1 has one wire terminated. All other remote nodes in
the RIO subsystem have to terminate four cable assemblies (two cable assemblies
for Channel A and two cable assemblies for Channel B). For these remote nodes,
each TRC board TB1 terminal has two wires terminated. Table 4-4 shows the color
coding for various signal assignments and terminal numbers (see Figure 4-6).
Top View - TRC Board TB1 Terminal Block
CH. A CH. B
1 2 3 4 5 6 7 8 9 10
Figure 4-5. TRC Board Copper Wire Communications Cable Termination
Table 4-4. TB1 Wire Assignments (All Nodes)
Signal Assignment
TB1 Terminal No. Wire Insulation Color Channel Master Node Remote Node
1 Black A RCVA XMITA
2 Orange A RCVA/ XMITA/
3 Red A XMITA RCVA
4 Green A XMITA/ RCVA/
5 Shield A Shield A Shield A
6 Shield B Shield B Shield B
7 Black B RCVB XMITB
8 Orange B RCVB/ XMITB/
9 Red B XMITB RCVB
10 Green B XMITB/ RCVB/
2/00 4-11 M0-0054 (Rev 2)

Channel A is always connected to Channel A,

and Channel B is always connected to Channel B, as shown below.
GREEN GREEN GREEN

10 10
RED RED RED
9 9
ORANGE 3A98653 ORANGE ORANGE
CH. B 8 8
Cable Assembly
BLACK BLACK BLACK
7 7
SHIELD SHIELD SHIELD
6 6
SHIELD SHIELD SHIELD
5 5
GREEN GREEN GREEN
4 4
RED 3A98653 RED RED
CH. A 3 3
Cable Assembly
ORANGE ORANGE ORANGE
2 2
BLACK BLACK BLACK
1 1
TRC Board TRC Board To next

Terminal Block Terminal Block Remote
Node, if
Master Node Remote Node present.
TRC Panel Assembly TRC Panel Assembly
or Remote Node
TFR Panel Assembly
Figure 4-6. Copper Wire Communications Medium Connections
M0-0054 (Rev 2) 4-12 2/00

The RIO subsystem’s copper twisted pair cable assemblies carry balanced electrical
signals. Unlike the Westnet II Data Highway coaxial cable, where the outer
conductor (shield) is directly tied to ground at each cabinet that the coaxial cable
enters, the RIO subsystem’s twisted pair cable assemblies are tied directly to ground
only at the master node.
At the master node, the cable shields are connected to terminals 5 and 6 of TB1, the
TRC board’s ten position terminal block. A plug-in jumper is used to short pins 1 and
2 of the TRC board JS1 three position header. This plug-in jumper position directly
connects TB1 terminals 5 and 6 to PS1. PS1 is a 0.138-32 (No. 6) threaded stud that
is mounted on the circuit side of the TRC board. A ground cable ties the TRC board’s
PS1 (GND) stud to the master node’s cabinet CG copper bus bar. The TRC board
may be mounted in either the DIOB1 or DIOB2 position (see Figure 4-3).
At each remote node, within an RIO subsystem that uses twisted pair
communications media, the shields of the communications cable assemblies are
connected to terminals 5 and 6 of TB1 on the remote node’s TRC board. Each
remote node TRC board must have the JS1 header’s plug-in jumper placed in the
2-3 position. This plug-in jumper position causes TB1 terminals 5 and 6 to be routed
to the PS1 GND stud through a parallel 1 Megohm resistor/0.01 microfarad
capacitor network. A ground cable ties the TRC board’s PS1 (GND) stud to the
remote node’s cabinet CG copper bus bar. The TRC board may be mounted in either
the DIOB1 or DIOB2 position (see Figure 4-3). Table 4-5 details how to set
jumpers for defining a TRC panel as either a remote or master node.
Table 4-5. TRC Board Plug-in Jumper Placement
TRC Board Location JS1 Plug-in Jumper Location

Master Node Posts 1 and 2
Remote Node Posts 2 and 31
1The TRC board JS1 header’s plug-in jumper comes factory installed in this position. If a TRC
board is located in an RIO subsystem master node, the JS1 plug-in jumper must be moved to posts
1 and 2.
As with any metallic communications cable, the RIO subsystem’s copper shielded
twisted pair communications cable assemblies may be affected by electrical noise and
must be protected to ensure proper operation of the RIO subsystem. The RIO
subsystem copper shielded twisted pair communications cable routing requirements
are the same as the routing requirements for the Westnet II coaxial Data Highway cable
as defined in “System Planning and Data Highway Installation Manual” (M0-0051) or
"WDPF System Planning and Highway Installation Manual" (M0-8000).
2/00 4-13 M0-0054 (Rev 2)

4-6. Fiber-Optic Cable Communications Links

Each RIO Fiber-Optic subsystem communications channel uses a duplex fiber-optic
cable assembly.
• The standard Westinghouse fiber-optic cable used for Channel A has a green
outer jacket (3A98763).
• The standard Westinghouse fiber-optic cable used for Channel B has a yellow
outer jacket (3A98764).
— Parts 3A98763 and 3A98764 are identical except for the outer jacket color.
• These standard fiber-optic cable assemblies are duplex (two optical fibers).
— Fiber number 1 has a white jacket with a longitudinal black stripe.
— Fiber number 2 has a white jacket.
• Each optical fiber is a 62.5/125 micron multimode glass graded-index fiber.
• The fiber-optic cable assemblies are terminated with ST bayonet style plug
connectors.
• Both standard Westinghouse fiber-optic cable assemblies are water blocking,

are flame retardant, and have halogen free jackets.
Notes
1. A maximum fiber-optic cable length (no

in-line cable splices) of 1 mile (1609 meters)
is permitted for the 3A98763 and
3A98764 fiber-optic cable assemblies when
they are used in the RIO Fiber-Optic
subsystem or in the RIO Fiber-Optic
Extension subsystem.
2. The standard Remote I/O fiber-optic cable

assemblies (3A98763 and 3A98764) are not
to be used in applications that involve aerial
suspension, direct burial, or unprotected
outdoor installation.
M0-0054 (Rev 2) 4-14 2/00

The RIO Fiber-Optic subsystem’s optical fiber communications link uses the same
serial data coding that is used for the shielded twisted copper wire pair
communications link. AMI encoded serial data, which has three distinct voltage
levels, is converted to infrared light (wavelength = 820 to 850 nanometers). The
infrared light has three distinct power levels that correspond to the three voltage
levels of the AMI data. The infrared light is transmitted via an optical waveguide
(optical fiber) communications channel.
The RIO Fiber-Optic subsystem links the remote nodes to the master node using a
“star” configuration. Each remote node has its own dedicated “point to point” fiber-
optic communications link with the master node (see Figure 4-7).
Q Q
F
R
F TRC
R
TFR Duplex Fiber-
Q Q Q Q Q Q Q Q T
Q-Line I/O
Q
R F F F F F F F F R Panel Optic Cable
C
C R R R R R R R R
Assembly Assemblies
I/O Termination
M M S D M M S D
R S M H R S M H
C C C C
Q Q
F F TRC
R R
Q
Master Node
Q-Line I/O R (Redundant DPU or
C
TCU Drop)
I/O Termination
Q Q Q Q
F F TRC F F TRC
R R
R R
Q
Q-Line I/O R Q
C Q-Line I/O R
I/O Termination C
I/O Termination
Remote Nodes
Figure 4-7. Remote Q-Line I/O Fiber Optic Subsystem
2/00 4-15 M0-0054 (Rev 2)

The fiber-optic RIO subsystem provides redundant communications. Each channel

uses a duplex fiber-optic cable assembly. One fiber in each cable assembly is used
to transmit data. The other fiber is used to receive data.
The RIO Fiber-Optic subsystem master node may directly interface up to four
remote nodes via optical fiber.
Note
If the master node interfaces two fiber-optic

remote DIOBs, both DIOBs’ QFR cards must
be powered from the same pair of DC power
supplies.
Every RIO Fiber-Optic subsystem node contains a TFR Panel Assembly

(4D33764). The TFR Panel Assembly requires two rack units (88.9 mm
(3.5 inches)) of vertical cabinet space. It contains a card cage in its left half. The
right half is a flat panel with cutouts to provide access to the TFR Panel Assembly’s
TRC (4256A56G01) board. The TFR Panel Assembly’s card cage contains ten card
slots and may house up to eight QFR cards (see Section 4-8 for more information
on the TFR Panel Assembly).
M0-0054 (Rev 2) 4-16 2/00

4-6.1. Installing Fiber-Optic Communications Cable

As described in Section 4-6, the standard Remote Q-Line I/O fiber-optic cable
assemblies have not been designed for aerial suspension, direct burial, or
unprotected outdoor installation. Therefore, care must be taken to protect and
support the cable. (This is generally accomplished by the use of conduit ducts or
cable trays to contain the cable.)
When pulling the fiber-optic cable through ducts or conduit, be sure that the tensile
load does not exceed the fiber-optic cable manufacturer’s recommendations. If a
winch is used, it is recommended that it be equipped with an automatic cut-off if the
tension exceeds the manufacturer’s recommendations. Also, during fiber-optic
cable installation, observe the minimum recommended cable bend radius. See Table
5-5 for specifications for the standard WDPF Remote Q-Line I/O subsystem fiber-
optic cable assemblies.
The fiber-optic cable assemblies are generally supplied with the optical connectors
attached; therefore precautions to protect the connectors must be taken. These
precautions include leaving the protective dustcaps on the connectors until the fiber-
optic cable is to be connected to the QFR card, covering the connectors with PVC
tubing, wrapping the connectors with electrical tape, and using a cable grip that
transfers the pulling load to the fiber-optic cable while protecting the connector.
A device that can be used to pull optical cable and protect the optical connector is
the Kellums Flexible Eye Pulling Grip. This pulling grip is a multi-weave mesh
sleeve that is placed around the cable which tightens around the cable as pulling
pressure is applied. This grip also provides a steel nose cone that connects easily to
a swivel or a pulling line.
For information on the pulling grips contact:
Kellums Division
Harvey Hubbel, Inc.
Stonington, CT 06378
Telephone: (203) 535-1250
2/00 4-17 M0-0054 (Rev 2)

4-6.2. Fiber-Optic Cable Test Equipment

The following types of fiber-optic test equipment will be useful in the testing of the
fiber-optic cable and of the fiber-optic light sources:
• Fiber-optic Source
• Optical Power Meter
• Terminated Fiber-Optic Test Cable and Coupling Adaptor
• Optical Time Domain Reflectometer (OTDR)
Note
The selected fiber-optic test equipment must
be compatible with the ST bayonet style
fiber-optic connectors used by the WDPF
Remote Q-Line I/O Fiber-Optic subsystem
fiber-optic cable.
Fiber-Optic Source and Optical Power Meter
The fiber-optic source may be used in conjunction with the optical power meter to
determine fiber-optic cable optical power loss. The following equipment manufacturers
have provided Westinghouse with Fiber-Optic Sources and Optical Power Meters that
are compatible with the WDPF Remote Q-Line I/O Fiber-Optic subsystem fiber-optic
cables. Please contact the vendor for additional information on their fiber-optic
equipment product line.
• Fotec, Inc.
• 3M Photodyne, Inc.
AMP Inc. can supply terminated fiber-optic test cables and optical coupling adaptors
that are compatible with the WDPF Remote Q-Line Fiber-Optic subsystem fiber-optic
cables. Contact AMP for additional information. The Optical Power Meter and the
Fiber-Optic source may be used to determine total cable fiber and connector loss.
Another device which may be used to locate and analyze splices and breaks in the fiber
is an short-dead-zone Optical Time Domain Reflectometer (OTDR). The OTDR
launches a very short light pulse into an optical fiber. Small reflections occur throughout
the fiber, becoming weaker as power levels drop with distance. At major breaks, large
reflections occur and appear as strong peaks on the OTDR’s display. OTDR’s are
available from the following manufacturers:
• 3M Photodyne
• Tektronix
• Laser Precision
In most cases, the use of an OTDR will not be necessary. The Optical Power meter-
Fiber-Optic source combination will normally be adequate for testing the fiber-optic
cable assembly.
M0-0054 (Rev 2) 4-18 2/00

4-6.3. Fiber-Optic Cable Integrity Test Procedure

The following test procedure should be performed after routing the fiber-optic
cable. In addition, the test procedure may be performed prior to cable routing and
may be performed for maintenance checks of the WDPF Remote Q-Line I/O Fiber-
Optic subsystem after installation is completed.
Optical Cable Integrity Test
Required Equipment:
• Adjustable fiber-optic source (850 nanometer LED)
• Two test fiber-optic cables (one meter long)
• Two coupling adaptors (AMP 501381-1 or equivalent)
• Optical power meter (850 nanometer wavelength and dBu scale)
All of the required optical test equipment must be physically compatible with the
ST optical connectors on the fiber-optic cable assembly under test. In addition, the
test fiber-optic cables should be of the same construction as the fiber-optic cable
being tested (same glass core/glass cladding fiber construction, multimode, graded
index, same core/cladding diameter). The two coupling adaptors should be
mechanically compatible with ST fiber-optic connectors.
2/00 4-19 M0-0054 (Rev 2)

Fiber-Optic Cable Insertion Loss Procedure
The EIA FOTP-171 double ended test is used to verify the total optical loss of each
optical fiber in the fiber-optic cable assembly under test, including the insertion
losses of the optical fiber’s two ST fiber-optic connectors. Each optical fiber and its
two ST optical connectors are tested individually.
1. Attach a one meter long test (launch) fiber-optic cable to the optical light source’s
optical output receptacle. Connect the other end of the launch cable to the optical
input receptacle of the optical power meter as shown below in Figure 4-8:
LED Optical
Light Power
Source Meter
Launch Cable
Figure 4-8. Launch Level Power Determination
2. Apply power to the optical source and to the optical power meter. Select the
optical power meter’s dBu measurement scale and select the 850 nanometer
optical wavelength (if the meter has multiple wavelengths). Adjust the optical
source’s 850 nanometer optical output power level so that the optical power
meter reading is 0.0 dBu (one microwatt).
M0-0054 (Rev 2) 4-20 2/00

3. Disconnect the launch cable from the optical power meter. Clean all ST optical
connectors of the cable assembly under test with optic wipes. For the cable
under test, connect the first optical fiber’s transmit end to the launch cable using
a ST optical coupling adaptor. Connect the other end (receive end) of the optical
fiber to a second one meter long test (receive) cable using a ST optical coupling
adaptor. Connect the other end of the receive cable to the optical input
receptacle of the optical power meter as shown below:
Optical Launch Cable ST Coupling

Adaptor
Optical LED
Light
Source
Optical Cable Under Test

ST Coupling
Adaptor
Optical
Power
Meter
Optical Receive Cable
Figure 4-9. Receive Power Level Determination
4. Examine the optical power meter reading, ignoring the minus sign. The number
displayed (dBu) should be less than or equal to the loss in dB calculated from
the following formula if the standard WDPF Remote I/O fiber-optic cables are
used.
Allowable optical insertion loss is less than or equal to:

((4 dB)*(length of cable tested in km) + 2 dB)
For example, if a 3A98763 fiber-optic cable assembly is 1000 feet in length, the
1000 foot length is converted into an equivalent length in km (0.305 km). The
loss formula yields a maximum allowable cable optical insertion loss of 3.22 dB
for a 1000 foot length of 3A98763 fiber-optic cable.
2/00 4-21 M0-0054 (Rev 2)

5. Reverse the ends of the optical fiber just tested and repeat Steps 3 and 4 so that
the light is transmitted in the other direction through the optical fiber being
tested.
6. Test the other optical fiber in the fiber-optic cable assembly under test by
repeating Steps 3, 4, and 5.
4-6.4. Fiber-Optic Cable Termination Procedure

Unterminated fiber-optic cable may be supplied with some WDPF Remote Q-Line
I/O Fiber-Optic subsystems. Routing unterminated fiber-optic cable is much easier
than routing terminated fiber-optic cable. If it is necessary to terminate the fiber-
optic cable, an ST connector that is equivalent to the AMP 501380-1 connector
must be used. The connector selected must be compatible with 62.5 micron/125
micron optical fiber.
The connector manufacturers should be contacted to determine what tools, material,

and termination procedures are required to terminate their ST optical connectors to
fiber-optic cable.
If use of an alternate fiber-optic cable is desired, this cabling must contain optical
fibers that are of glass construction, multimode, and have a 62.5 micron/125 micron
core/cladding diameter. The use of single mode fiber-optic cables is not allowed
with the WDPF Remote Q-Line I/O Fiber-Optic subsystem.
The optical specifications of any alternative fiber-optic cable must meet or exceed
those of the standard fiber-optic cable (attenuation & bandwidth) if the same
standard 62.5 micron/125 micron optical fiber is used. See Table 5-5.
If 50 micron/125 micron or 100 micron/140 micron multimode fiber-optic cable is

used, the maximum WDPF Remote I/O fiber-optic cable length specification may
no longer apply.
M0-0054 (Rev 2) 4-22 2/00

4-6.5. Fiber-Optic Cable Splicing

Splices should be avoided when possible. If a splice is required, various methods
may be employed.
Coupling Adaptor
The simplest method to terminate the two optical cable ends with ST optical
terminate the two optical cable ends with ST optical connectors joins the connector
ends with an optical coupling bushing (AMP 501381-1 or equivalent). This method
may result in additional optical link losses of up to 1.0 dB, reducing the maximum
allowable optical link length.
Fusion Splicing
In fusion splicing, a more efficient method of splicing, the two fibers are
micropositioned and then fused together using an electric arc. This method of
splicing typically results in additional link losses of 0.25 dB but requires special
equipment and a skilled equipment operator. One manufacturer of fusion splicing
equipment is Power Technology Incorporated.
For more information, contact:
Power Technology Incorporated

P.O. Box 9769
Little Rock, AR 72219
Telephone (501) 568-1995
2/00 4-23 M0-0054 (Rev 2)

4-6.6. Optical Power Loss Budget

The optical power loss budget (OPB) is the maximum amount of optical power loss
that can occur between a QFR card optical transmitter and a second QFR card’s
optical receiver. It is the difference between the coupled optical power (in dBm)
available from the optical transmitter and the coupled optical power (in dBm)
required by the optical receiver.
Note
Total link optical power losses must be less than the

optical power loss budget (OPB), to meet the system
underdrive requirement.
The link optical power loss budget is usually expressed in dB. Optical Power
Margin (OPM) describes the amount by which the optical power entering a QFR
cards’ optical receiver should exceed the required minimum input power. OPM
accounts for any decrease in the received optical power over the lifetime of the QFR
to QFR optical link.
The QFR to QFR OPB is 12.0 dB minimum. An OPM of 3 dB should be assumed.

Therefore, the maximum allowable QFR to QFR optical link loss is OPB - OPM
(12.0 dB - 3 dB = 9.0 dB).
Note
The QFR “optical transmitter receptacle to optical

fiber ST connector” and the “optical fiber ST
connector to QFR optical receiver” coupling losses
are accounted for by the optical component’s
manufacturer and do not have to be accounted for
when calculating a QFR to QFR optical link power
loss budget.
Optical Power Loss Budget (OPB) Example
A WDPF Remote Q-Line I/O fiber-optic subsystem has the following optical link:
• A one hundred-foot duplex 62.5/125 micron fiber optic jumper cable

(3A98763G05) links the first QFR card’s optical receptacles to a patch panel
that contains ST-to-ST optical couplers.
M0-0054 (Rev 2) 4-24 2/00

• Two of the patch panel optical couplers connect the jumper cable fibers to two
fibers that are part of a 1.1 km long multi-fiber optical cable assembly. This
multi-fiber optical cable is routed outdoors to another building in the customer’s
plant. There, the multi-fiber optical cable is connected to a second patch panel.
The two fibers used by the QFR card are terminated with ST optical connectors
and are connected to two of the patch panel’s ST-ST optical couplers.
• A one hundred fifty-foot duplex 62.5/125 micron fiber-optic jumper cable

(3A98763G07) interfaces these two patch panel optical couplers to the second
QFR card.
• The multi-fiber optical cable is an armored loose tube cable that contains
twenty-four 62.5/125 micron optical fibers. The QFR to QFR optical link uses
two of these fibers. Both of these optical fibers had been broken and each
required a single fusion splice to repair the breaks.
Optical Loss Specifications
The loss specifications due to cables and coupling are as follows:
3A98763 fiber-optic cable unit attenuation 4 dB/km @ 850 nm

Loose tube fiber-optic cable unit attenuation 3.5 dB/km @ 850 nm
ST-ST coupler loss 1 dB
Fusion splice loss 0.20 dB
The following are the calculations for the optical link loss:
Optical Link Loss =

{100 ft x (km/3280 ft) x 4 dB/km } + 1 dB +
{1.1 km x 3.5 dB/km

} + 0.20 dB + 1 dB +
{150 ft x (km/3280 ft) x 4 dB/km }

= 0.122 dB + 1 dB + 3.85 dB + 0.20 dB + 1 dB + 0.183 dB
= 6.355 dB
2/00 4-25 M0-0054 (Rev 2)

The optical link power loss of 6.355 dB is less than 9.0 dB, which means that the
optical link power loss is within acceptable limits. In fact, this optical link has
(9.0 dB - 6.355 dB) or 2.645 dB of extra margin above and beyond the 3 dB of OPM.
The total optical link power loss is a sum of the optical power losses due to optical
fiber, optical fiber splices, and couplings from optical connector to optical
connector through optical couplers. It may be estimated by the following formula:
x
 
Loss (dB) =  ∑ D n × L n + ( y × S f ) + ( z × S m ) + ( w × C )
n = 1 
where x = number of optical fibers connected in series

Dn = length (km) of an optical fiber
Ln = an optical fiber’s loss per unit length
(expressed as dB/km)
y = number of optical fiber fusion splices
z = number of optical fiber mechanical splices
w = number of ST-ST optical couplers
Sf = 0.2 dB
Sm = 0.25 dB
C = 1.0 dB
The optical fiber’s loss per unit length specification may be obtained from the fiber-
optic cable manufacturer.
Note
This specification must be for a nominal

optical wavelength of 850 nanometers, not
1300 or 1550 nanometers.
The formula assumes that all optical fibers involved are of the same diameter.
M0-0054 (Rev 2) 4-26 2/00

4-7. QFR Card
4-7. QFR Card

The RIO Fiber-Optic subsystem uses optical fiber as its communications media.
Duplex fiber-optic cable assemblies link the master node to remote nodes in a “star”
configuration. Each remote node has its own dedicated “point-to-point” link with
the master node.
The QFR (Remote I/O Fiber-Optic Interface) card (see Figure 4-10) provides signal
conversion from electrical to optical and optical to electrical for both the transmit
and receive signals housed within the link’s duplex fiber-optic cable. This master
node to remote node fiber-optic link may be made redundant by using a pair of
QFR’s at each end of the link and adding an additional fiber-optic cable. Each
master node to remote node fiber-optic link has a maximum length of one mile
(1,609 meters or 5,280 feet).
TFR Backplane
Connector Receive
R1
JS2
LE1 = PWR, Fuse OK
P1 LE2 = Fiber Optic Active
LE 3 = Twisted Pair Active
R3
JS1(3) JS3 JS4(3) JS6 JS7 JS9(3) JS8(3)

Transmit
(JS6 - JS9 Factory Set)
Figure 4-10. yQFR Card Plug-in Resistor and Jumper Locations
Note
When setting up a Remote I/O Fiber-optic

subsystem, refer to Table 3-2 for all necessary
MRC card jumper changes.
2/00 4-27 M0-0054 (Rev 2)

4-7. QFR Card
4-7.1. QFR Jumper Configuration

The QFR contains four 2-position headers and four 3-position headers. Plastic
plug-in jumpers are factory installed on some of these headers (see Figure 4-11).
The QFR application determines if some of these plug-in jumper positions need
modification. Table 4-6 is a guide to the QFR card’s user configurable plug-in
jumpers.
JS2
123
JS1
321
JS3 JS4
Figure 4-11. User Configurable Jumpers for QFR
Table 4-6. QFR User Configurable Jumpers
Fiber-Optic
RIO Subsystem JS1 JS2 JS3 JS4
Node Style Jumper Jumper Jumper Jumper
Master Posts 1 & 2 No jumper Installed Posts 1 & 2
772B480G01 OR
772B480G02
Master Remote Posts 2 & 3 Installed No jumper Posts 2 & 3
4256A51G01
Slave Remote Posts 1 & 2 No jumper Installed Posts 1 & 2
772B480G01
Fiber-Optic Master remote nodes are only used in the RIO Fiber-Optic extension
subsystem. Configured QFR cards (772B480G01) are used in the fiber-optic slave
remote node and in the master node (TFR slots 1 and 2). Configured QFR cards
(772B480G02) are used in master nodes (TFR slots 3, 4, 5, 6, 8, and 10).
Standard QFR cards (4256A51G01) are used in the fiber-optic master remote node.
M0-0054 (Rev 2) 4-28 2/00

4-7. QFR Card
Figure 4-12 shows the factory set jumpers. These are NOT to be changed.
1 2 3
JS8
JS6
1 2 3
JS7 JS9
Figure 4-12. Factory Set Jumpers for QFR
The factory set QFR plug-in jumpers are:
JS6: A plug-in jumper is installed.
JS7: A plug-in jumper is installed.
JS8: A plug-in jumper connects posts 1 and 2 together.
JS9: A plug-in jumper connects posts 1 and 2 together.
The QFR card (Revision level D or later) contains sockets at component locations
R1 and R3 (see Figure 4-10). Depending on the QFR configuration, 150 ohm 0.25
watt one percent metal film resistors (406A069211) are installed or removed from
these sockets.
Table 4-7. QFR Card Resistors Installed or Removed (QFR Revision Level D or Later)
QFR Configuration R1 Socket R3 Socket

4256A51G01 Resistor out Resistor in (Not used)
772B480G01 Resistor in Resistor in
772B480G02 Resistor out Resistor out
2/00 4-29 M0-0054 (Rev 2)

4-7. QFR Card
4-7.2. Slot Assignments

Since the RIO Fiber-Optic subsystem uses redundant optical fiber communications
channels, two QFR cards are required to interface the two optical fiber channels to
an RIO Fiber-Optic subsystem node. One QFR handles Channel A (1)
communications, the second QFR handles Channel B (2) communications. A
complete RIO Fiber-Optic subsystem master node to remote node redundant fiber-
optic link requires a total of four QFR cards.
QFR slot assignments are application dependent. TFR Panel Assembly QFR Card
Cage slot numbering convention has slot 1 being the left most slot when the card
cage is viewed from the front.
Table 4-8. TFR Panel Slot Assignments
QFR Card Responsibility Card Cage Slot No.

Master Node - 1st Remote Channel A 1
Master Node - 1st Remote Channel B 2
Master Node - 2nd Remote Channel A 3
Master Node - 2nd Remote Channel B 4
Master Node - 3rd Remote Channel A 5
Master Node - 3rd Remote Channel B 6
Master Node - 4th Remote Channel A 8
Master Node - 4th Remote Channel B 10
Fiber-Optic Slave Remote Node - Channel A 7
Fiber-Optic Slave Remote Node - Channel B 9
Note
Slot 10 is the right most slot of the TFR panel

card cage QFR assignments. See Figure 4-15.
M0-0054 (Rev 2) 4-30 2/00

4-7. QFR Card
4-7.3. Installation
The QFR (4256A51G01) printed circuit card interfaces an optical fiber
communications channel to an RIO Fiber-optic subsystem master node or fiber-
optic slave remote node. The QFR has optical transmit and receive ports which are
used to translate optical signals to electrical bipolar AMI signals and electrical
bipolar AMI signals to optical signals.
A metal plate mounted at the front of the QFR (see Figure 4-13) provides access to
the QFR card’s two ST optical receptacles. Three LED status indicators are visible
through cutouts. The QFR metal front plate is slotted top and bottom for fastening
to the TFR Panel Assembly metal card cage with two 0.112-40 X 0.375 (No. 4)
slotted binding head metal screws and two 0.112 (No. 4) internal tooth lockwashers.
J1
Fiber-Optic Receive
Connection
LE1 = Power OK, Fuse OK
LE2 = Fiber-Optic Receiver Active (OL ACT)
LE3 = Twisted Pair Link Active (TP ACT)
Fiber-Optic Transmit
Connection
J2
Figure 4-13. QFR Front Plate
When the QFR is installed in the TFR Panel Assembly card cage, the optical receive
port ST receptacle is at the top of the QFR front panel.
• LE1 - The POK LED indicator is lit if one or both of the QFR card’s DC power
supplies are active.
• LE2 - The OL ACT (Optical Link Active) LED indicator is lit when incoming
optical link message activity is detected by the QFR card’s optical receiver
circuit.
• LE3 - The TP ACT (Twisted Pair Link Active) LED indicator is lit when the
QFR card’s electrical line receiver circuit detects message activity generated by
either the MRC or QRC communications port transmitter circuit.
2/00 4-31 M0-0054 (Rev 2)

4-7. QFR Card
In fiber-optic slave remote nodes, the QFR card’s TP ACT LED may be dimly lit if
the fiber-optic slave remote node is not being accessed very often by the master
node. In master nodes, a specific QFR card’s OL ACT LED may be dimly lit if the
master node does not often access the fiber-optic remote node whose QFR is linked
to the master node’s QFR.
The QFR cards used in the remote node (fiber-optic slave remote node) and in the
master node are configured QFR cards (772B480G01). The configured QFR cards
have their electrical line receiver AGC/ALBO circuitry bypassed. In fiber-optic
slave remote nodes and in master nodes, the QFR cards are a short fixed distance
from the communications circuitry on the QRC or MRC cards. In addition, unlike
the MRC card, the QRC card’s transmitter circuit does not continuously transmit an
AMI constant carrier signal. No AGC (automatic gain control) or ALBO (automatic
line build-out) receiver functions are required for QFR cards used in fiber-optic
slave remote nodes or in master nodes.
Note
In master nodes, the QFR cards installed in

TFR panel slots 3, 4, 5, 6, 8, and 10 are
772B480G02 configured QFR cards.
In fiber-optic master remote nodes, the standard 4256A51G01 QFR card is used.
Since it is separated from the master node’s MRC card/TRC panel assembly by a
varying length of copper wire, the QFR card’s electrical line receiver AGC/ALBO
circuitry is required.
Connect both pairs of QFR cards together with optical fibers as shown below.
Always connect RCV to XMIT and XMIT to RCV.
Master Node or Fiber-optic Slave
Fiber-optic Master Remote Node Remote Node
Optical Fiber
J1-RCV J1-RCV
QFR QFR
J2-XMIT Optical Fiber J2-XMIT
Channel 1 (A)
Optical Fiber
J1-RCV J1-RCV
QFR QFR
J2-XMIT Optical Fiber J2-XMIT
Channel 2 (B)
Figure 4-14. QFR to QFR Optical Fiber Interconnection
M0-0054 (Rev 2) 4-32 2/00

4-8. TFR Panel Assembly
4-8. TFR Panel Assembly

The TFR Panel, used in Fiber-optic Remote Q-Line applications, is two rack units
high (88.9 mm (3.5 in)) and mounts in a 482.6 mm (19 in) rack. The panel provides
two functions. The left half is a card cage and backplane (TFR) with 76.2 mm (3.0
in) high by 266.7 mm (10.5 in) deep card slots for up to eight QFR cards. The right
half of the panel provides for rear mounting of the TRC board. The TRC provides
a transition between the ribbon cables coming from the MRC or QRC and the fiber-
optic backplane. The electrical signals are then presented to the QFR cards.
A TFR board backplane (4256A58) is mounted at the rear of the TFR Panel
Assembly’s card cage. The TFR board contains studs to permit 12.4 to 13.1 VDC
power to be provided to the QFR cards. In addition, the TFR board contains ten
34 position dual readout card-edge connectors to interface the QFR cards.
QFR signals and power are bussed across the TFR board to all ten of these card edge
connectors and to a pair of 14 position vertical 0.100 X 0.100 inch headers. A
fourteen conductor cable assembly contained within the TFR Panel Assembly
routes QFR signals to and from the TFR Panel Assembly’s TRC card. A twenty
conductor cable assembly, which is not part of the TFR Panel Assembly, links the
TRC board’s J2 communications header to an MRC (J1 or J2) or QRC (J3)
communications header.
QFR Card Edge Connector

J12
J1
Figure 4-15. TFR Backplane
2/00 4-33 M0-0054 (Rev 2)

4-9. Fiber-Optic Extension Subsystem

The WDPF RIO Fiber-Optic Extension subsystem uses both types of RIO
communications media (copper wire and optical fiber). The master node interfaces
one or more remote nodes using the standard RIO shielded twisted copper wire pair
cable assemblies. These assemblies are routed from the master node to the remote
nodes in a “daisy-chain” fashion.
At any of these “twisted wire pair” remote nodes, an optical link to a standard RIO
Fiber-Optic subsystem fiber-optic slave remote node may be added. The twisted
wire pair remote node containing an optical link to a separate fiber-optic slave
remote node is identified as a fiber-optic master remote node as shown in
Figure 4-16.
4-9.1. Remote Node Types

Unlike the RIO Fiber-Optic subsystem, the RIO Fiber-Optic Extension subsystem
may have up to eight remote nodes. These remote nodes may be combination of
three styles of remote nodes.
Table 4-9. Fiber-Optic Extension Subsystem Remote Node Types
QFR Card, Communications

Remote Node Type Part Numbers Position Media Interface
Fiber-Optic 3A98753G02 QFR, 4256A51G01 TFR
Master Remote Node (Quad Cabinet) Slot 1, 2 4D33764G01
3A59347G02
(486 Extended
DPU cabinet)
3A59333G02 QFR,4256A51G01 TFR
(RIO Enclosure) Slot 3, 4 4D33764G01
Fiber-Optic 3A98753G01 QFR, 772B480G01 TFR
Slave Remote Node (Quad Cabinet) Slot 7, 9 4D33764G01
3A59347G01
(486 Extended
DPU cabinet)
3A59333G01 QFR, 772B480G01 TFR
(RIO Enclosure) Slot 7, 9 4D33764G01
M0-0054 (Rev 2) 4-34 2/00

Table 4-9. Fiber-Optic Extension Subsystem Remote Node Types (Cont’d)
QFR Card, Communications

Remote Node Type Part Numbers Position Media Interface
Twisted Wire Pair 3A59328G01 No QFR Cards TRC
3A59328G02 4D33730G01 for
(Quad Cabinet) DIOB1
4D33730G03 for
3A59346G01 DIOB2
3A59346G02
(486 Extended
DPU cabinet)
3A59332G01
3A59332G02
(RIO Enclosure)
Fiber-Optic Master Remote Nodes
Unlike the other two types of remote nodes, these remote nodes are only found in
an RIO Fiber-Optic Extension subsystem. This remote node interfaces the master
node via copper wire serial communications channels. In addition, this node
interfaces a fiber-optic slave remote node using fiber-optic cable serial
communications channels. Like the fiber-optic slave remote node, the fiber-optic
master remote node contains a TFR Panel Assembly. Unlike the fiber-optic remote
node, the TFR Panel Assembly interfaces both copper wire pair cable assemblies
(via its TRC PC board’s TB1 terminal block) and duplex fiber-optic cable
assemblies (via a pair of QFR cards).
Note
If this node is not located at the end of the

copper wire serial communications channel,
resistors R4, R5, R6, and R7 must be
removed from their sockets on the node’s
TRC PC board (located in the TFR panel
assembly).
A pair of duplex fiber-optic cable assemblies link the two QFR cards with a pair of
QFR cards located in a fiber-optic slave remote node.
2/00 4-35 M0-0054 (Rev 2)

Fiber-Optic Slave Remote Nodes
This remote node type is also used in the RIO Fiber-Optic subsystem. A pair of
configured QFR cards are housed in the remote node’s TFR Panel Assembly’s QFR
card cage. A pair of duplex fiber-optic cable assemblies link the node’s two QFR
cards with a pair of QFR cards located in a fiber-optic master remote node.
Twisted Wire Pair Remote Nodes
This remote node type is also used in the standard RIO subsystem. The TRC PC
board’s TB1 terminal block interfaces the master node via a pair of shielded twisted
copper wire pair cable assembly serial communications channels.
The table below show all possible combinations of Fiber-Optic Master, Fiber-Optic
Slave and Twisted pairs:
Table 4-10. Remote Node Styles/Combinations:
Fiber-Optic Master
Quantity Fiber-optic Slave Quantity Twisted Pair Quantity
1 1 0 to 6
2 2 0 to 4
3 3 0 to 2
4 4 0
Note
Fiber-Optic Master and Fiber-Optic Slave

remote nodes are always used in pairs
A 62.5/125 micron optical fiber limits the maximum optical link length between
each Fiber-Optic Master/Fiber-Optic Slave remote node pair to 1609 meters (one
mile). This link length limitation is not dependent on the total number of remote
nodes or the total length of the copper wire cable assemblies in the RIO Fiber-Optic
Extension subsystem.
M0-0054 (Rev 2) 4-36 2/00

The number of remote nodes permitted in an RIO Fiber-Optic Extension subsystem

is dependent on the total length of all of the subsystem’s shielded twisted copper
wire pair cable assemblies. The remote nodes may be any combination of the three
types possible in an RIO Fiber-Optic Extension subsystem:
• Fiber-optic master remote node
• Fiber-optic slave remote node
• Twisted wire pair node
Table 4-11 provides the cable lengths permitted with various quantities of remote
nodes.
Table 4-11. Fiber-Optic Extension Subsystem, Maximum Copper Wire Cable Lengths
Remote Node Quantity Maximum Cable Length

1-4 1000 meters (3280 feet)
5-8 600 meters (1968 feet)
2/00 4-37 M0-0054 (Rev 2)

Master Node
Remote
TRC Node
Q-Line Q
I/O R
C
Redundant DPU/TCU
I/O
Termination
Copper TRC
Cable
M D M D
TRC F S H F S H
R R
P M P M
Q C C C C
Q-Line R
I/O C
I/O
Termination
FP=Functional
Fiber-Optic Processor
Master Remote SM=Shared
Memory
DHC=Data
TFR Panel
Q Q TRC
Highway
F F Controller
R R
Q-Line Q
I/O R
C
I/O
Termination
TFR Panel
Q Q TRC
F F
R R
Q
Q-Line I/O R
TRC Panel C
Q-Line Q
I/O R
C Fiber-Optic
Fiber-Optic Slave Remote
Duplex Cable Node
I/O
Termination Remote Node
Figure 4-16. Remote Q-Line Fiber-Optic Extension Subsystem
M0-0054 (Rev 2) 4-38 2/00

Section 5. Remote Q-Line Specifications

This section addresses the following topics:
• Operating temperature (Section 5-2).
• Power requirements (Section 5-3).
• Single crate remote I/O enclosure, weight and dimensions (Section 5-4).
• Cable (Section 5-5).
2/00 5-1 M0-0054 (Rev 2)

5-2. Operating Temperature
5-2. Operating Temperature

• Master Node (DPU or TCU quad Cabinet)
10°C to 45°C, 10% to 90% Relative Humidity, non-condensing
• Remote Node (quad cabinet)

10°C to 45°C 10% to 90% Relative Humidity, non-condensing
• Remote Node (Remote I/O Enclosure - Twisted wire-pairs) (3A59332)

• Remote Node (Remote I/O Enclosure - Fiber-optics) (3A59333)

M0-0054 (Rev 2) 5-2 2/00

5-3. Power Requirements
5-3.1. Master Node

The Master node electrical power requirements are the sum of the electrical power
requirements of a DPU or TCU drop plus the additional electrical power required
by the addition of the Remote I/O subsystem master node add-on kit.
Table 5-1. Power Requirements: DPU, TCU, Master Remote I/O
Steady-State Steady-State AC
AC Input Power Thermal
Device Input Power (Amps) 115/230 V Dissipation
Description (Watts) RMS (BTUs/Hour)
Redundant DPU Drop 255 3.05/1.63 870
7-Level (Dual coaxial
Data Highway, no local
DIOB).
Redundant TCU Drop 319 3.9/2.09 1089
7-Level (Dual coaxial
Data Highway, no local
DIOB.
Remote I/O Master 43 0.57/0.31 147
Node, Add-on Kit
(Twisted wire pairs,
redundant drops).
Remote I/O Master Node, Add-on Kit
(Fiber-optics, redundant drops.
1 Remote Node 60.5 0.81/0.44 207
2 Remote Nodes 78.0 1.04/0.57 266
3 Remote Nodes 95.5 1.28/0.69 326
4 Remote Nodes 113.0 1.51/0.82 386
2/00 5-3 M0-0054 (Rev 2)

5-3.2. Remote Node

There are two basic remote node styles.
1. Remote nodes with multiple Q-crates use standard quad cabinets. The Remote
I/O quad remote node add-on kit is added to a quad cabinet that contains
Q-crates, Q-Line I/O cards, and I/O power supplies.
Table 5-2. Power Requirements: Remote Node (Quad Cabinet)
Steady-State Steady-State AC
AC Input Power Thermal
Device Input Power (Amps) 115/230 V Dissipation
Description (Watts) RMS (BTUs/Hour)
Remote Node (Twisted 18 0.24/0.13 61.4
wire pairs, Add-on kit
(No Q-line I/O cards)
Remote Node (Fiber- 35 0.47/0.25 119.4
Optic, Add-on kit (No
Q-line I/O cards)
2. Remote nodes with one Q-crate that use the standard Remote I/O enclosure
(5D32134).
The AC to DC power supplies used within the standard Remote I/O Enclosure
assembly (5D32134G01) autoswitch between the 115 VAC RMS and 230 VAC
RMS ranges.
AC Input Voltage: 95 VAC RMS min. 132 VAC RMS max.

190 VAC RMS min. 264 VAC RMS max.
AC Line Operating Frequency: 47 Hz min. 63 Hz. max.
M0-0054 (Rev 2) 5-4 2/00

.
Table 5-3. Power Requirements: Remote I/O Enclosure
Steady-State AC Steady-State AC Thermal

Device Input Power Input Power (Amps) Dissipation
Description (Watts) 115/230 V RMS (BTUs/Hour)
Remote I/O enclosure 73 0.98/0.53 249
(Twisted wire pairs, Add-on
kit (3A59332) No Q-Line I/O
cards.
Remote I/O enclosure (Fiber- 90 1.2/0.65 307
Optic, Add-on kit (3A59333)
(No Q-line
I/O cards)
Worst Case Analog Q-Line I/ 306 4.09/2.22 1044
O Card Supply Load (12
cards)
Add this term to the Remote
I/O enclosure numbers).
If any of the Q-Line I/O cards require a DC contact wetting voltage, room is
available on the power supply tray for the addition of two auxiliary power supplies
(24 VDC or 48 VDC). The slide out tray permits easy access to the power supplies
and simplifies their removal or insertion. An auxiliary power supply add-on kit
(3A59337) is used to add these power supplies to the base Remote I/O enclosure.
To find the total AC input current and AC input power added to the master node
(local DIOB) or remote node due to Q-Line I/O card DIOB power supply current
requirements:
1. Determine the DC supply current required for each Q-Line I/O card.
2. Sum the currents obtained from Step 1.
3. Using the data from Step 2, determine the AC input power and current
requirements from Figure 5-1.
For additional information on Q-Line I/O card DIOB supply requirements, see the
“Q-Line Installation Manual” (M0-0053).
2/00 5-5 M0-0054 (Rev 2)

900 9
800 8
700 7
AC Current, 115 VAC RMS
AC Input Current requirements, Q-Line card (Amps)
AC Input Power requirements, Q-Line card (Watts)
600 6
500 5
AC Power (Watts)
400 4
300 3
200 2
AC Current, 230 VAC RMS
100 1
0 0
0 10 20 30 40
DIOB DC Supply Current Requirements for Q-Line Cards (AMPS)
Figure 5-1. Q-Line Current and Power Requirements
M0-0054 (Rev 2) 5-6 2/00

5-4. Single Crate Remote Enclosure, Weight and Dimensions
5-4. Single Crate Remote Enclosure, Weight and

Dimensions
Westinghouse 5D32134
Part Number
Weight: 91 kg (200 lbs) max.
Dimensions: 800 mm (31.5 inches) high
744 mm (29.3 inches) wide
432 mm (17.0 inches) deep (door closed)
1093 mm (43.0 inches) deep (door fully open)
These dimensions are nominal.
The 5D32134 Remote Enclosure Assembly is part of the 3A59332 (twisted- wire
pair) and 3A59333 (fiber-optic) Remote I/O remote node add-on kits.
2/00 5-7 M0-0054 (Rev 2)

5-5. Cable
5-5. Cable
This section provides tables that detail requirements for both copper and fiber-optic
cabling.
Table 5-4. Copper and Fiber-Optic Cable Specifications
Specification Copper Fiber-Optic

System Layout Redundant four-wire “Daisy Radially connected Duplex fiber-
Chained” channels, half duplex optic cable. Two duplex cables
operation required per redundant channel
Data Rate: 1.6 megabit/sec. 1.6megabit/sec.
Coding: Alternate Mark Inversion (AMI) Alternate Mark Inversion (AMI)
Cable Length: 1 kM (3280 ft) total length using up to 1609 meters (1 mile) max
four remote taps. This is the total
distance, not the distance between
remote taps.
Number of Eight (8) maximum - maximum cable Four (4) maximum
Remote Nodes length reduced to 600 m (1968 ft)
when implemented with more than 4
remote nods
Cable: 1 dB/100 M @ 1 MHZ to meet the The duplex fiber-optic cable used is a
“cable length” and “number of taps” graded index multi-mode cable
specifications. Cable quality, number consisting of two glass fibers
of taps and maximum cable length are surrounded by protective layers. One
related as follows: fiber is used to transmit data and the
(L2 * L) + N * L1 ≤14 dB other is used to receive data. Two of
where: these duplex fiber-optic cable must be
L2 = line loss in dB per unit length used to provide a redundant link.
L = maximum line length
N = number of remote nodes
L1 = insertion loss per
remote node tap (~1 dB)
Cable Temperatures from -30 to +75 Temperatures from -20 to +80
Temperature degrees C. degrees C. Relative Humidity from
Rating 5%-95% non-condensing
Fiber-optic and metallic remote Q-Line configurations are shown in Figure 4-4 and
Figure 4-7.
M0-0054 (Rev 2) 5-8 2/00

5-5. Cable
Table 5-5. Standard Fiber Optic Cable Specifications
Specifications for Cable 3A98763 or 3A98764

Specification Value/Range
Attenuation at 820/850 nm 4.0 dB/km
Bandwidth at 820/850 nm 160 MHz-km
Core Diameter 62.5 +/- 2 micrometers
Cladding Diameter 125 +/- 2 micrometers
Buffer Diameter (Secondary) 900 micrometers nominal
Numerical Aperture (NA) @ 2m 0.275 +/- 0.015
Proof Testing 100 kPSI (689 megapascals) min.
Index profile Graded
Fiber type Glass core/glass cladding
Construction Tight buffer, zero halogen jacket, water blocking,
flame retardant.
Tensile load (at installation) 1776 N (400 lbs) max.
Tensile load (long term) 300 N (66 lbs) max.
Bend radius (at installation) 12.5 cm (5 in) min.
Bend radius (installed) 7.5 cm (3 in) min.
Minimum crush resistance 437 N/cm (250 lb/in)
Number of optical fibers 2
Outer jacket color Green - 3A98763
Yellow - 3A98764
2/00 5-9 M0-0054 (Rev 2)

5-5. Cable
Table 5-6. Standard Remote I/O Subsystem

Copper Twisted Wire Pair Cable Specifications
Specification: Unterminated Cable 3A98645, Terminated Cable 3A98653

Made to IBM Part Number 4716748 IBM Type 1
Conductor 22 AWG (Solid) bare copper
Insulation Flame retardant polyethylene
Shielded Twisted Wire Pairs Two primary conductors described above are twisted together
with various left-hand lays. Each pair is foil shielded with
100% minimum coverage.
Color Coding
Pair Number Color combination
1 Black and orange
2 Red and green
Overall Shield 36 AWG braided tinned copper, 65% minimum coverage.
Two shielded pairs as described above shall be located under
one braid.
Jacket Flame retardant, black PVC
0.76 cm X 1.1 cm (0.300 in X 0.435 in) nominal diameter
Ripcord Nylon, located under jacket.
Flame Resistance UL 1581,CSA vertical cable tray flame test.
Applicable specifications CSA premises Communications Cable Type PCC FT4,
UL Type CM
Temperature rating ° Celsius
-30° to + 75
Maximum Pull Tension 369.2 N (83 lbs) max.
Nominal weight 96.8 Kg/Km (65 lbs./1000 ft)
M0-0054 (Rev 2) 5-10 2/00

5-5. Cable
Table 5-7. Electrical Specifications for Copper Twisted Wire Pair Cable
Specification: Unterminated Cable 3A98645, Terminated Cable 3A98653

Maximum Operating Voltage 30 V RMS
Maximum Continuous Current per 2.3 Amps
Conductor
Nominal Capacitance between 27.9 picofarad/M (8.5 picofarad/ft)
Conductor Pairs
Nominal Impedance of Pairs 150 ohms (@ 3-20 Mhz)
Nominal Conductor DC Resistance 57.07 ohms/Km (17.4 ohms/1,000 ft)
@ 20° Celsius
Nominal Velocity of Propagation 78% C
Capacitance Unbalance @ 1 KHz < 1,500 picofarad/Km (457 picofarad/1,000 ft)
Attenuation: 22 dB/Km (0.67 dB/100 ft) maximum @ 4 MHz.
45 dB/Km (1.37 dB/100 ft) maximum @ 16MHz.
Near-End Crosstalk < -58 dB at 3 to 5 MHz
< -40 dB at 12 to 20MHz
2/00 5-11 M0-0054 (Rev 2)

Appendix A. Invalid QRC Switch Settings
A-1. QRC Invalid Switch Setting Examples

Examples of different types of card edge address errors are shown below. While not
a complete list of all possible errors, these examples demonstrate the types of errors
to avoid.
A Bold font designates invalid QRC SW1 or QRC SW2 settings.
In Table A-1 , address 7FH is higher than the following “low” address.
Table A-1. Overlapping Card Edge Connector Addresses
Remote Node No. Low Address High Address

1 08H 3FH
2 40H 7FH (Invalid)
3 7EH (Invalid) FBH
In Table A-2 , the card edge addresses are NOT sequential:
Table A-2. Missing Card Edge Connector Addresses

1 08H 7FH
2 82H (Invalid) FBH
In Table A-3 , 82H the “low” address is higher than the preceding address, 7FH:
Table A-3. High Address < Low Address

1 08H 7FH
2 80H 7FH (Invalid)
3 82H FBH
2/00 A-1 M0-0054 (Rev 2)

The low card address in Table A-4 below is NOT the first available address:
Table A-4. Missing Low Card Edge Connector Address

1 09H (Invalid) 7FH
2 80H FBH
The high address in Table A-5 below is lower than the required high address:
Table A-5. Missing High Card Edge Connector Address

1 08H 7FH
2 80H AFH
3 B0H FAH (Invalid)
The low card address in Table A-6 below is lower than the first available address:
Table A-6. Too Many Card Edge Connector Addresses (Invalid Low Limit)

1 07H (Invalid) 7FH
2 80H AFH
3 B0H FBH
The number FCH in Table A-7 , exceeds the allowable limit of 244 addresses.
Table A-7. Too Many Card Edge Connector Addresses (Invalid High Limit)

1 08H 5FH
2 60H FCH (Invalid)
M0-0054 (Rev 2) A-2 2/00

Appendix B. MRC Status Algorithm
B-1. MRC Status Algorithm

MRCSTAT (MRC Card Status) provides up to 12 GX or GP records of status
information for a user selected remote station or node attached to an RIOB in a
DPU/TCU drop.
Improper mixing of DPU and MRC firmware levels will cause invalid data for
STAT, RSQ, FL12, FL34, FL56, FL78, and CTS functions (listed in Table B-1).
Proper performance of MRCSTAT requires the following DPU and MRC firmware
combinations:
DPU Revision MRC Firmware Revision MRC Card Revision

8.5L (F.JH or M.JH) or later MN010J or later SUB V or later
7.4G (M.GC) or later MN010J or later SUB V or later
7.2Z (M.FY) or later MN010J or later SUB V or later
The inputs and outputs for the MRCSTAT algorithm are listed in Table B-1 and
described in detail on the following pages.
Table B-1. Algorithm Function Definitions a
Function Description
PORT RIOB Selection
STN Remote node selection
STAT MRC status byte (low byte)
Drop/RIOB information (high byte)
LAST Remote port and node last tested (low byte)
RSQ MRC microcontroller firmware revision level (two ASCII bytes)
CS Port Communication Status Byte (low byte)
Initial Communication Status Byte (high byte)
OID1 Remote node On-Line Test Test-Read Message Transmission Attempts (low byte)
Remote node On-Line Test Test-Read Message Transmission Failures (high byte)
OID2 Remote node I/O address low limit (low byte)
Remote node I/O address high limit (high byte)
OID3 Master node’s MRC Line Receiver circuit DAC setting for the selected remote node
(low byte)
2/00 B-1 M0-0054 (Rev 2)

Table B-1. Algorithm Function Definitions a (Cont’d)
Function Description
FL12 Remote node Communications Fault counter (low byte)
FL34 Remote node MRC Channel 1 Line Receiver CRC Byte error counter (low byte)
Remote node MRC Channel 2 Line Receiver CRC Byte error counter (high byte)
FL56 Remote node QRC Channel 1 Line Receiver CRC Byte error counter (low byte)
Remote node QRC Channel 2 Line Receiver CRC Byte error counter (high byte)
FL78 Remote node Flag byte (low byte)
CTS Remote node Test Status register (low byte)
Remote node CRC_CHECKS register (high byte)
a. Examples of MRCSTAT display applications are presented in Table B-13 and Table B-14.
Descriptions of MRCSTAT Algorithm Inputs:
• PORT selects the RIOB (1 or 2) that the algorithm will access.
• STN selects the particular remote node or station (1...8) of the RIOB to access.
Descriptions of MRCSTAT Algorithm Outputs:
• STAT
Low byte = MRC card’s Status register (bits 7 through 0).

High byte = RIOB remote node quantity, RIOB quantity, and drop I/O
configuration.
The MRC Status register is shared by both MRC RIOBs (PORT = 1 or 2). STAT
bits 11 through 8 return the I/O configuration of the drop as indicated by the drop
overburn. This information is shared by both MRC RIOBs (PORT = 1 or 2).
STAT bits 15 through 12 return the remote node quantity (1...8) for the MRC RIOB
specified by the PORT input. The bit assignments (bits 15 through 0) of the STAT
output are defined in Table B-2, Table B-3, and Table B-4
M0-0054 (Rev 2) B-2 2/00

.
Table B-2. STAT - MRC Status Register (Bits 0 - 9)
Bit Number
Parameter Bit On (Logical 1) Bit Off (Logical 0)
Bit 0 (LSB) Either the MRC card’s ALIVE The MRC card’s ALIVE “One-
ALIVE “One-Shot” is regularly being Shot” was not triggered by the
updated by the drop’s Multibus regular assertion of the MRC card’s
Functional Processor pulsing the Control register ALIVE bit and the
MRC card’s Control register ALIVE “One-Shot” has timed out.
ALIVE bit,
OR
the ALIVE “One-Shot” output is
disabled by the removal of the
program from MRC card header JS1.
Bit 1 The drop has given the MRC card The MRC card does not have
CONTROL control of the RIOB. Accesses of control of the RIOB. Accesses of
the RIOB Q-Line I/O cards are the RIOB Q-Line I/O cards are not
permitted. permitted.
Bit 2 The partner drop’s MRC card Either the partner drop’s MRC card
PARTNER OK ALIVE “One-Shot” is not timed out has a timed-out ALIVE “One-Shot”
and the partner drop’s Multibus OR
Functional Processor has asserted its Control register I’MOK/ bit has
the I’MOK/ bit in the partner drop’s been disasserted.
MRC card Control register.
Bit 3 The partner drop’s MRC card has The partner drop’s MRC card does
CONTROL AVAIL/ control of the RIOB shared by both not have control of the RIOB shared
drops’ MRC cards. This drop’s by both drop’s MRC cards. This
MRC card cannot access the RIOB. drop’s MRC may have control of
the RIOB.
Bit 4 The Cross-Connect flat cable The Cross-Connect flat cable
CABLE IN assembly is properly installed assembly is absent or is not properly
between the MRC card’s J3 header installed.
and the partner drop MRC card’s J3
header.
Bit 5 A program jumper is not installed A program jumper is installed on
PRIMARY on header JS8. This bit is not used. header JS8.
2/00 B-3 M0-0054 (Rev 2)

Table B-2. STAT - MRC Status Register (Bits 0 - 9) (Cont’d)
Bit Number
Parameter Bit On (Logical 1) Bit Off (Logical 0)
Bit 6 The remote Q-Line I/O system is One or both drop (master node)
QFRVOK either non fiber-optic or both drop TFR panel assembly DC power
(master node) TFR panel assembly supply output voltage levels are
DC power supply output voltage below the minimum required level.
levels are above the minimum
required level.
Bit 7 When the drop attempted to access a No RIOB Q-Line I/O card access
RIOB-FAULT Q-Line I/O card located in one of fault has been detected since the last
the two RIOBs supported by the time the contents of the Status
MRC card, the MRC card failed to register were read by the drop’s
detect a remote node reply message Multibus Functional Processor.
with a valid CRC check byte on
either communications channel
(RIOB Q-Line I/O card access
fault). When the drop’s Multibus
Functional Processor reads the
contents of the MRC card’s Status
register, this bit is reset to a logical
zero “0" state.
Bits 8 and 9 of the STAT output will return the I/O configuration of the drop as indicated by the
drop overburn. The bit assignments are as follows:
Bit 8 DIOB1 is local DIOB1 is remote (RIOB1)
Bit 9 DIOB2 is local DIOB2 is remote (RIOB2)
Bits 10 and 11 of the STAT output will indicate the number of RIOBs (MBUs)
entered by the user as indicated on the drop configuration screen. The bits are
assigned as follows:
Table B-3. STAT - RIOB Bit Assignments (Bits 10 and 11)
Bit 11 Bit 10 Number of RIOBs

0 0 Invalid
0 1 1 RIOB
1 0 2 RIOBs
1 1 Invalid
M0-0054 (Rev 2) B-4 2/00

Bits 12 through 15 of STAT return the number of remote nodes associated with the
RIOB specified by the contents of the PORT input (1 or 2).
Table B-4. STAT - Remote Node Assignments (Bits 12 - 15)
Bit 15 Bit 14 Bit 13 Bit 12 Remote Node

Quantity
0 0 0 1 1
0 0 1 0 2
0 0 1 1 3
0 1 0 0 4
0 1 0 1 *5
0 1 1 0 *6
0 1 1 1 *7
1 0 0 0 *8
* = Not a valid number for fiber-optic Remote Q-Line I/O systems
• LAST
Low byte = RIOB port number and the remote node last tested (see Table B-5).
High byte = 00H.
Table B-5. LAST Register - LAST Bits 7 - 0
Contents of LAST RIOB Remote Node Just Tested

01H 1 1
02H 1 2
03H 1 3
04H 1 4
05H 1 5
06H 1 6
07H 1 7
08H 1 8
11H 2 1
12H 2 2
2/00 B-5 M0-0054 (Rev 2)

Table B-5. LAST Register - LAST Bits 7 - 0 (Cont’d)
Contents of LAST RIOB Remote Node Just Tested

13H 2 3
14H 2 4
15H 2 5
16H 2 6
17H 2 7
18H 2 8
• RSQ
Low byte = second ASCII character code of the MRC microcontroller firmware
revision level.
High byte = first ASCII character code of the MRC microcontroller firmware
revision level.
For an example, the MRC microcontroller firmware revision level is 0J. The RSQ
high byte equals 30H (the ASCII code for the number 0) and the RSQ low byte
equals 4AH (the ASCII code for the letter J).
• CS
Low byte = Current Communications Status of each remote node attached to the
RIOB.
High Byte = Initial Communications Status of each remote node attached to the
RIOB.
A value of 1 indicates remote node present; 0 indicates remote node not present.
Bit 0 (LSB) shows the current status of remote node 1. In like fashion, bits 1 through
7 provide the current status of remote nodes 2 through 8. The high byte of CS uses
the same bit format as the low byte, but shows the Initial Communications Status
following MRC card configuration (startup). Bit 8 shows the initial status of remote
node 1. In a like fashion, bits 9 through 15 (MSB) provide the initial status of remote
nodes 2 through 8. See Table B-6.
Table B-6. CS Bit Definition
Bit Number Parameter Bit On (Logical 1) Bit Off (Logical 0)

Bit 15 or 7 Remote node 8 present. Remote Node 8 not present
Bit 14 or 6 Remote node 7 present Remote Node 7 not present
M0-0054 (Rev 2) B-6 2/00

Table B-6. CS Bit Definition (Cont’d)
Bit Number Parameter Bit On (Logical 1) Bit Off (Logical 0)

The remaining eight MRCSTAT algorithm outputs provide information pertaining

to a specific remote node that is selected by the values of PORT and STN.
• OID1
Low byte = Remote node’s On-Line Test Test-Read Message Transmission

Attempts count
High byte = Remote node’s On-Line Test Test-Read Message Transmission
Failures count
A value of 03H is normal for the low byte and a value of 00H is normal for the high
byte. A high byte value of 03H indicates a failure of the most recent On-Line test.
The value of the LAST specifies the remote node for which the OID1 data applies.
• OID2
Low byte = Remote node's I/O address low limit (08H through FBH)
High byte = Remote node’s I/O address high limit (08H through FBH)
• OID3
Low byte = Master node’s MRC line receiver DAC setting

High byte = 00H
The master node's MRC line receiver circuit DAC setting is a six bit value that is
required for correct MRC line receiver operation when the drop’s Multibus
controller attempts to access a RIOB Q-Line I/O card whose hardware address lies
within the range of I/O card hardware addresses assigned to the selected remote
node. DAC settings will normally range from values of 08H (remote nodes located
~1000 meters from the master node - large amount of required MRC line receiver
preamplifier gain) to 20H (remote nodes immediately adjacent to the MRC - small
amount of required MRC line receiver preamplifier gain). The maximum DAC
setting value is 3FH.
2/00 B-7 M0-0054 (Rev 2)

Note
Note that a change in master node MRC cards

can yield different DAC settings for the same
remote node.
• FL12
Low byte = Remote Node’s Communications Fault Counter

High byte = 00H
An eight bit Communications Fault counter is maintained for each remote node.
All Communications Fault counters are zeroed during MRC RIOB startup
(configuration). A remote node Communications Fault counter is incremented
every time that a remote node DIOB I/O access yields no reply messages with valid
CRC check bytes on either communications channel after three attempts to access
the remote node. As time passes, if communications faults are detected during
remote node I/O accesses, the communications fault counter will increment up to a
value of FFH, then roll over and continue counting up from a 00H value.
Under normal conditions, the remote node’s Communications Fault counter should
not increment or else should increment very slowly. Rapid remote node
Communications Fault counter incrementing could indicate that the remote node is
powered-off, the remote node is disconnected from both communications channels,
the presence of large amounts of electrical noise, or a possible hardware problem.
• FL34
Low byte = Remote Node’s MRC Channel 1 Line Receiver CRC Byte Error
Counter
High byte = Remote Node’s MRC Channel 2 Line Receiver CRC Byte Error
Counter
Two 8-bit MRC Line Receiver CRC Byte Error counters are maintained for each
remote node. All MRC Line Receiver CRC Byte Error counters are zeroed during
MRC RIOB startup (configuration). The remote node’s MRC Channel 1 Line
Receiver CRC Byte Error counter is incremented every time that an On-Line Test
Test-Write remote node access results in a reply message with an invalid CRC
check byte at the Channel 1 MRC line receiver circuit.
M0-0054 (Rev 2) B-8 2/00

The remote node’s MRC Channel 2 Line Receiver CRC Byte Error counter is
incremented every time that an On-Line Test Test-Write remote node access results
in a reply message with an invalid CRC check byte at the Channel 2 MRC line
receiver circuit. As time passes, if MRC line receiver CRC byte errors are detected
during remote node On-Line test communication channel loopback tests, the
appropriate MRC Line Receiver CRC Byte Error counter will increment up to a
value of FFH, then roll over and continue counting up from a 00H value.
Under normal conditions, both remote node’s MRC Line Receiver CRC Byte Error
counters should not increment or else should increment very slowly. Rapid MRC
Line Receiver CRC Byte Error counter incrementing could indicate that the remote
node is powered-off, that the master node or the remote node is disconnected from
one of the communications channels, that there is a large amount of electrical noise
present, or that there is a possible hardware problem.
• FL56
Low byte = Remote Node’s QRC Channel 1 Line Receiver CRC Byte Error Counter
High byte = Remote Node’s QRC Channel 2 Line Receiver CRC Byte Error
Counter
Two 8-bit QRC Line Receiver CRC Byte Error counters are maintained for each
remote node. All QRC Line Receiver CRC Byte Error counters are zeroed during
MRC RIOB startup (configuration). The remote node’s QRC Channel 1 Line
Receiver CRC Byte Error counter is incremented every time that an On-Line Test
Test-Write remote node access results in the Channel 1 QRC Line Receiver circuit
processing a Test-Write message with an invalid CRC check byte.
The remote node’s QRC Channel 2 Line Receiver CRC Byte Error counter is
incremented every time that an On-Line Test Test-Write remote node access results
in the Channel 2 QRC Line Receiver circuit processing a Test-Write message with
an invalid CRC check byte. As time passes, if QRC line receiver CRC byte errors
are detected during remote node On-Line test communication channel loopback
tests, the appropriate QRC Line Receiver CRC Byte Error counter will increment
up to a value of FFH, then roll over and continue counting up from a 00H value.
Under normal conditions, both remote node’s QRC Line Receiver CRC Byte Error
counters should not increment or else should increment very slowly. Rapid QRC
Line Receiver CRC Byte Error counter incrementing could indicate that the remote
node is powered-off, that the remote node is disconnected from one of the
communications channels, that there is a large amount of electrical noise present, or
that there is a possible hardware problem.
2/00 B-9 M0-0054 (Rev 2)

• FL78
Low byte = Remote Node’s Flag byte

High byte = 00H
The bit definitions of the FL78 low byte (FLAG byte) are described in Table B-7,
Table B-8, and Table B-9.:
MSB LSB FL78 BIT POSITION

7 6 5 4 3 2 1 0
Table B-7. Communications Channel 1 (A) Quality Bits (FL78)
Bit Bit Bit

Number 2 Number 1 Number 0 Description
1 1 1 Good Channel 1 (A) quality
0 1 1 The most recent reply message received via Channel
1 (A) from the remote node contained an invalid CRC
check byte.
0 0 1 The two most recent reply messages received via
Channel 1 (A) from the remote node contained
invalid CRC check bytes.
0 0 0 The three most recent reply messages received via
Channel 1 (A) from the remote node contained
invalid CRC check bytes. The quality of Channel 1
(A) is judged to be bad.
M0-0054 (Rev 2) B-10 2/00

Table B-8. Communications Channel 2 (B) Quality Bits (FL78)
Bit Bit Bit

Number 5 Number 4 Number 3 Description
1 1 1 Good Channel 2 (B) quality
0 1 1 The most recent reply message received via Channel
2 (B) from the remote node contained an invalid
CRC check byte.
0 0 1 The two most recent reply messages received via
Channel 2 (B) from the remote node contained
invalid CRC check bytes.
0 0 0 The three most recent reply messages received via
Channel 2 (B) from the remote node contained
invalid CRC check bytes. The quality of Channel 2
(B) is judged to be bad.
Table B-9. Remote Node Power Supply Status Bits (FL78)
Bit Bit On Bit Off

Number (Logical 1) (Logical 0)
Bit 6 The remote node's primary I/O power The remote node's primary I/O power
UVP/ supply output voltage level is above the supply output voltage level is below the
minimum allowable level. minimum allowable level.
Bit 7 The remote node's secondary I/O power The remote node's secondary I/O power
UVS/ supply output voltage level is above the supply output voltage level is below
minimum allowable level. the minimum allowable level.
2/00 B-11 M0-0054 (Rev 2)

• CTS
CTS returns the remote node’s Test Status register contents from the latest On-Line
test of the remote node in the low byte. See Table B-10 and Table B-11 for the Test
Status register bit assignments. The CTS high byte contains remote node’s
CRC_CHECKS register contents from the latest On-Line test of the remote DIOB
node. See Table B-12 for the CRC_CHECKS register bit assignments.
Note that if any one of Bits 7, 6, 5, or 4 are set during a remote node On-Line test,
the remote node’s communications channels loopback tests are not attempted. Bits
3, 2, 1, and 0 will remain reset when the On-Line test concludes
If a remote DIOB configuration failed, the MRC will not conduct On-Line tests of
the remote nodes assigned to that remote DIOB. Instead of displaying On-Line test
status, the Test Status register for those remote nodes will either contain all zero
data, or it will contain data (bits 7 through 3) that describes the cause of the remote
DIOB configuration failure. See Table B-14 for examples of remote DIOB
configuration failures.
A remote DIOB configuration may fail for one of the following reasons:
• The RIOB MRC/TRC communications cable is not properly installed

(Bit 7 is set).
• A remote node is not powered, the remote node’s QRC card is defective or is
missing, the remote node’s QRC/TRC communications cable is not properly
installed, the remote node’s QRC SW2 DIOB address is set too high, or both
communications channels have failed (Bit 6 is set).
• The remote node’s QRC SW1 DIOB address switch is not properly configured
(Bit 5 is set).
• The remote node’s QRC SW2 DIOB address switch is not properly configured
(address is set too low) (Bit 4 is set).
• Too many remote nodes (>8) are present (Bit 3 is set).
MSB LSB CTS BIT POSITION

7 6 5 4 3 2 1 0
M0-0054 (Rev 2) B-12 2/00

Table B-10. Test Status Register Bit Assignments, CTS Bits 7 - 4
Bit Bit On
Number (Logical 1)
Bit 7 The RIOB MRC/TRC Communications cable was not properly installed at the start of
the most recent remote node On-Line test. The On-Line test failed.
Bit 6 Three Test-Read reply messages with invalid CRC check bytes were detected while
trying to access the remote node. The On-Line test failed. Possible causes are:
- remote node may not be powered.
- remote node’s QRC card may be missing or be defective.
- remote node’s QRC/TRC communications cable missing or improperly installed.
- remote node’s QRC SW2 DIOB address switch may no longer be properly set.
- both communications channels have failed.
Bit 5 The DIOB I/O address high limit obtained from the remote node did not match the
remote node's QRC printed circuit card’s DIP switch I/O address high limit obtained
during the RIOB configuration. The On-Line test failed.
Bit 4 The DIOB I/O address low limit obtained from the remote node did not match the remote
DIOB station's QRC printed circuit card’s DIP switch I/O address low limit obtained
during the RIOB configuration. The On-Line test failed.
.
Table B-11. Test Status Register Bit Assignments, CTS Bits 3 - 0
Bit Bit On
Number (Logical 1)
Bit 3 The Channel 2 MRC line receiver test failed. During the remote node MRC/QRC
Channel 2 communications channel loopback test, three successive Channel 2 MRC
line receiver Test-Write reply messages contained invalid CRC check bytes.
Bit 2 The remote node MRC/QRC Channel 2 communications channel loopback test failed
because of a potential remote node Channel 2 QRC line receiver error.
Bit 1 The Channel 1 MRC line receiver test failed. During the remote node MRC/QRC
Channel 1 communications channel loopback test, three successive Channel 2 MRC
line receiver Test-Write reply messages contained invalid CRC check bytes
Bit 0 The remote node MRC/QRC Channel 1 communications channel loopback test failed
because of a potential remote node Channel 1 QRC line receiver error.
Notes
If no On-Line Test faults are detected during a remote

node On-Line test, an F0H value is returned.
2/00 B-13 M0-0054 (Rev 2)

MSB LSB CTS BIT POSITION

15 14 13 12 11 10 9 8
Table B-12. CRC_CHECKS Register Bit Assignments, CTS Bits 15-8
Bit Bit On Bit Off

Number (Logical 1) (Logical 0)
Bit 15 MRC Channel 2 Line Receiver CRC MRC Channel 2 Line Receiver CRC
Check Byte OK - Channel 2 loopback Check Byte not OK or not examined -
test. Channel 2 loopback test.
Bit 13 QRC Channel 2 Line Receiver CRC QRC Channel 2 Line Receiver CRC
M0-0054 (Rev 2) B-14 2/00

Remote Node CTS Summary
1. No problems detected during the remote node’s latest On-Line test.
- CTS returns FFF0H
2. At the start of the remote node’s latest On-Line test, the MRC-TRC
communications cable was missing or not installed properly.
- CTS returns 0080H
3. During the remote node’s latest On-Line test, the Test-Read message access
resulted in three reply messages with incorrect CRC check bytes.
- CTS returns 0040H
4. During the remote node’s latest On-Line test, the remote node's address low
limit DIP switch setting was determined to have changed since the MRC RIOB
configuration.
- CTS returns 0010H
Note
If the remote node’s address low limit was increased

over its original value, CTS returns 0040H
5. During the remote node’s latest On-Line test, the remote node's address high
limit DIP switch setting was determined to have changed since the MRC RIOB
configuration.
- CTS returns 0020H
2/00 B-15 M0-0054 (Rev 2)

6. During the remote node’s latest On-Line test, the remote node failed its
communications channel loop back test.
- CTS may return one of the following data patterns
7708H = Master node MRC Channel 2 Line Receiver error

BB02H = Master node MRC Channel 1 Line Receiver error
DD04H = Remote node QRC Channel 2 Line Receiver error
EE01H = Remote node QRC Channel 1 Line Receiver error
550CH = Master node MRC Channel 2 Line Receiver and remote node
QRC Channel 2 Line Receiver error
AA03H = Master node MRC Channel 1 Line Receiver and remote node
6609H = Master node MRC Channel 2 Line Receiver and remote node
9906H = Master node MRC Channel 1 Line Receiver and remote node
Depending on the error conditions, the values of CTS high byte actually returned
by CTS may not always match the values shown above.
Table B-13 illustrates a typical MRCSTAT algorithm display with no RIO problems.
Table B-13. MRC Card Status (Display with No Problems)

DPU DIOB Sta- MRC MRC Station Comm Test QRC MRC Comm MRC QRC Flag Test
tion Status Firm- Test Stat Read Addr DAC Fault CRC CRC Byte Status
ware
PORT STN STAT RSQ LAST CS OID1 OID2 OID3 FL12 FL34 FL56 FL78 CTS
2 1 1 1657H 304AH 0001H 0101H 0003H FB08H 0010H 0000H 0000H 0000H 00FFH FFF0H
3 2 1 1857H 304AH 0011H 0101H 0003H FB08H 000FH 0000H 0000H 0000H 00FFH FFF0H
4 1 1 2857H 304AH 0002H 0303H 0003H 7B08H 0012H 0000H 0000H 0000H 00FFH FFF0H
4 1 2 2857H 304AH 0002H 0303H 0003H FB7CH 0013H 0000H 0000H 0000H 00FFH FFF0H
M0-0054 (Rev 2) B-16 2/00

Table B-14 illustrates a typical MRCSTAT algorithm display with examples of RIO problems.
Table B-14. MRC Card Status (Display with Problems)

DPU DIOB Sta- MRC MRC Station Comm Test QRC MRC Comm MRC QRC Flag Test
tion Status Firm- Test Stat Read Addr DAC Fault CRC CRC Byte Status
ware
PORT STN STAT RSQ LAST CS OID1 OID2 OID3 FL12 FL34 FL56 FL78 CTS
2a 1 1 1657H 304AH 0001H 0101H 0003H FB08H 0010H 0000H 0000H 0000H 007FH FFF0H
3 b
1 1 1857H 304AH 0011H 0101H 0003H FB08H 0011H 0000H 00A6H 0000H 00F8H BB02H
3 2 1 1857H 304AH 0011H 0101H 0003H FB08H 000FH 0000H 0000H 0000H 00FFH FFF0H
4c 1 1 2857H 304AH 0002H 0303H 0003H 7B08H 0012H 0000H 0000H 1F00H 00FFH DD04H
4 1 2 2857H 304AH 0002H 0303H 0003H FB7CH 0013H 0000H 0000H 0000H 00FFH FFF0H
6d 1 1 1657H 304AH 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0080H
7e 1 1 1857H 304AH 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0000H 0040H
7 f
2 1 1857H 304AH 0000H 0000H 0000H FB04H 0012H 0000H 0000H 0000H 00FFH 0010H
a. The station’s secondary I/O power supply is not connected.

b. The MRC Channel 1 line receiver is not connected.
c. The QRC Channel 2 line receiver is not connected.
d. The remote DIOB1 MRC-TRC cable is absent. Configuration failed.
e. The station’s QRC-TRC cable is absent, the QRC is absent, or the station is powered off.
Configuration of remote DIOB1 failed.
f. The station’s QRC low-limit address limit is incorrectly set to 04H. Configuration of remote DIOB2 failed.
2/00 B-17 M0-0054 (Rev 2)

Appendix C. Remote Node Temperature
Compensation
C-1. Section Overview

Currently, there are three methods of compensating thermocouples for cold junction
reference temperature in remote nodes. They are listed below in order of preference:
• Half-Shell/Terminal Assembly compensation (QAX,QAXT cards)
• RTD compensation (QRT card)
• On-card compensation (QAV card)
C-2. Half-Shell/Terminal Assembly Compensation

Half Shell compensation may be implemented for remote nodes that use B-cabinets
for I/O terminations. The QAXT Half Shell Assembly (Westinghouse Part No.
5D32162G01) is added to a QAX B-cabinet half shell as shown in Figure C-1.
Terminal Assembly compensation may be implemented for remote nodes
(3A59332 or 3A59333) that use the Remote I/O enclosure (5D32134). The QAXT
Terminal Assembly (Westinghouse Part No. 5D32164G01) is added to a Remote
I/O enclosure QAX terminal block located on the enclosure’s terminal assembly
(see Figure C-2).
The QAX card has 12 available channels. One channel is connected to an electronic
temperature sensing module which is mounted either at a B-cabinet QAX half-shell
or at a Remote I/O enclosure terminal assembly QAX terminal block. This module
provides the capability for compensating the other 11 channels on the QAX card.
As shown in Figures C-1 and C-2, a steel cover is placed over the QAX half-shell
or terminal assembly terminal block. This isolates the terminal blocks from the rest
of the B-cabinet or Remote I/O enclosure. To provide compensation, the QAXT is
mounted as indicated in Figures C-1 or C-2.
2/00 C-1 M0-0054 (Rev 2)

Ground Bar
Note:
Component side
of QAXT towards
terminal block.
20
19
QAXT 18
17
Card 16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Half-Shell
Protective Cover
Figure C-1. QAXT Half-Shell Mounting
M0-0054 (Rev 2) C-2 2/00

Ground Bar
Note:
Component side
of QAXT towards
terminal block.
20
19
QAXT 18
Card 17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1 Terminal Assembly
Terminal Block
Protective Cover
Figure C-2. QAXT Terminal Assembly Mounting
2/00 C-3 M0-0054 (Rev 2)

C-3. RTD Compensation
Benefits of this method include:
• No baffles of fans are needed within the termination cabinet or Remote I/O
enclosure.
• Minimal impact on compensation if cabinet or enclosure door is opened.
• Preferred with Remote Q-Line I/O remote nodes.
Refer to the QAX card section in the “Q-Line Installation Manual” (M0-0053) for
additional information on this method of compensation.

This method uses cabinet mounted Resistance Temperature Detectors (RTDs) to
determine an average temperature of an entire termination cabinet or a portion
(segment) of the cabinet. A maximum of two segments can be defined for each
termination cabinet, with two RTD temperatures in each segment. RTD cabinet
temperatures are fed into a QRT card that occupies four specific addresses (F8H -
FBH). The drop then averages the measurement and compensates the thermocouple
values terminated within that segment of the cabinet.
Only one remote node in any given RIOB may contain all four QRT card edge
connector addresses (F8H - FBH). Therefore, thermocouple temperature
compensation can be implemented in only one of an RIOB’s remote nodes. If
thermocouple temperature compensation is required for multiple remote nodes on
the same RIOB, half-shell/terminal assembly compensation or on-card
compensation may be used as a substitute for QRT RTD compensation.
Considerations for cabinet mounted RTDs include:
• Baffles and fans are used within the termination cabinet.
• QRT RTD input card and external circuitry are required.
• Compensation values are updated every one-half second. Compatible with

remote nodes that use “B” cabinets for I/O termination.
M0-0054 (Rev 2) C-4 2/00

A twisted-three-conductor shielded cable is recommended for RTD signal field

connections.
The preferred method to interface RTD signals is to use the QRT card, which can
have four isolated RTD bridges and A/D converters. An alternative method to
interface RTD signals in WDPF applications is to use an external bridge power
supply, an externally mounted bridge, and a QAV card (low-level A/D converter).
Note
When using 10 ohm copper RTDs, the

conversion coefficients may need to be re-
calibrated in the field. The lead resistance
varies greatly with the size and length of wire
for this type of RTD.
Refer to the QRT card section in the “Q-Line Installation Manual” (M0-0053) for
2/00 C-5 M0-0054 (Rev 2)

C-4. On-Card Compensation
C-4. On-Card Compensation

This method can only be used with card-edge terminations and Remote Q-Line I/O.
(For most applications, QAXT compensation is preferred). In operation, on-card
compensation uses an on-card temperature sensor on a QAV card. QAV cards
equipped with thermocouple temperature compensation feature use the seventh
channel for the sensor. The channel is read every time the card performs an auto-
calibration cycle. This eliminates the need for external sensor cards and ensures
field temperature accuracy.
• Compatible with card-edge terminations
• Compensation values updated every one-half second.
• Usable with Remote Q-Line I/O enclosures or similar cabinets where the I/O
cards and terminal blocks are housed within the same cabinet and the
temperatures within the entire cabinet are equalized.
Refer to the QAV card section in the “Q-Line Installation Manual” (M0-0053) for
M0-0054 (Rev 2) C-6 2/00

Index
A E
A cabinet 1-1 electrical noise 4-13
AC distribution center 4-3 electrical power requirements 5-3
AC input terminal block 4-3
add-on kits (hardware) 4-5 F
aerial suspension 4-17 fiber-optic cable
AMI 2-2 communication links 4-14
AMI coding 4-6 installing 4-17
AMI encoded serial data integrity test procedure 4-19
fiber-optic 4-15 splicing 4-23
Attachment Unit Interface (AUI) cable 3-30 termination 4-22
AX expansion cabinet 1-1 test equipment 4-18
fiber-optic master remote nodes 4-35
C fiber-optic slave remote node 4-32, 4-34, 4-36
cabinet 4-2, 5-7 FL12 output B-8
A cabinet 1-1 FL34 output B-8
AX expansion cabinet 1-1 FL56 output B-9
cable direct burial 4-17 FL78 output B-10
cabling 4-1, 5-8 FPGA 2-2
Card crate 4-5
communications 4-6 G
copper wire 4-7 grounding 4-3
fiber-optic wire 4-14
conduit ducts 4-17 H
configuration hardware 3-1
cable 2-4 add-on kit 4-5
DIOB 2-5 hexadecimal conversion (for QRC) 3-18
hardware 3-1 HW calculation
MRC card 3-6 analog point 3-3
QFR card 4-27 digital point 3-3
QOR card 3-24 HW record field 3-3
QRC card 3-14
TRC card 4-7, 4-13 I
copper wire communications channel 4-10 I/O enclosure 4-2
CS output B-6 installation
CTS output B-12 hardware 3-1
D J
daisy-chain configuration 2-4, 4-10 jumper configuration
DC contact wetting 5-5 MRC card 3-6
DIOB 2-2 QFR card 4-28, 4-29
Address Switch Settings 3-19 TRC card 4-13
card addresses 3-17
card addressing 3-3 K
configuration 2-5, 3-4 knockouts 4-3
DIOB cycle 4-6
DPU 1-1, 2-2
Drop 2-2
2/00 Index-1 M0-0054 (Rev 2)

Index
L PORT input B-2

LAST output B-5 power requirements (operating) 5-3
launch cable 4-20
LEDs Q
MRC card 3-8 QAV card C-6
QAX card 4-5
M QAXT compensation C-6
Master Node 2-2, 4-35 QBE 3-13, 3-26
maximum fiber-optic cable length 4-14 QFR card 4-27
Media Attachment Unit (MAU) 3-24 installation 4-31
migration 2-3, 3-24 jumpers 4-28
minimum recommended cable bend radius slot assignments 4-30
4-17 Q-Line 2-2
MRC card 3-5 QOR card 3-24
jumper configuration 3-6 QRC card 3-13, 3-26
LEDs 3-8 DIOB address setting examples 3-19
port connections 3-12 DIOB rules 3-17
serial to parallel data conversion 4-6 hexadecimal conversion 3-18
status algorithm B-1 invalid switch settings A-1
status display B-16 jumpers 3-14
MRCSTAT algorithm B-1 RIOB address setting examples 3-21
application examples B-17 tasks 3-13, 3-26
inputs B-2 QTB card 3-14
outputs B-2
Multibus Remote Controller R
See MRC card. read operation, DIOB 4-6
multimode glass graded-index fiber 4-14 record fields
HW 3-3
O redundant communication, fiber-optic 4-16
OID1 B-7 redundant controller applications 2-9
OID2 B-7 redundant serial communication 4-6
OID3 B-7 reference documents 1-3
Operating Temperature 5-2 remote I/O enclosure 4-2, 4-5, 5-7
optical Remote Node
link loss sample calculations 4-25 Addressing 3-32
loss specifications 4-25 remote node 2-2
power loss budget (OPB) 4-24 types 4-34, 5-4
power margin (OPM) 4-24 remote node power requirements 5-4
optical loss Remote Q-Line
insertion 4-21 configuration 2-4
specifications 4-25 features 2-4
total 4-20 purpose 2-3
Optical Time Domain Reflectometer (OTDR) specifications 5-1
4-18 Resistance Temperature Detectors
See RTD.
P RIO fiber-optic subsystem 4-15
Placing the MAU Module 3-27 RIO subsystem
Port Connection Guidelines (for MRC) 3-12 enclosure 4-2
M0-0054 (Rev 2) Index-2 2/00

Index
RIO subsystem implementation 3-4

RIOB 2-2
RSQ output B-6
RTD C-4
S
serial data conversion 4-6
serial data transmission 4-6
slave node 4-36
specifications
cable 5-8
optical link loss 4-24, 4-25
power 5-3
remote enclosure 5-7
temperature 5-2
ST bayonet plug, fiber-optic termination 4-14
ST optical connectors 4-19
standard Westinghouse fiber-optic cable 4-14
star configuration 2-4
STAT output B-2
STN output B-2
T
TCU 1-1, 2-2, 4-6
temperature
compensation C-1
operating 5-2
TFR PC board backplane 4-33
TRC panel 4-7
TRC, TB1 terminal block 4-11
twisted pair cable routing 4-10
twisted pair nodes 4-36
W
wiring 4-3
write operation, DIOB 4-6
2/00 Index-3 M0-0054 (Rev 2)


M0 0054 WDPF

Uploaded by

Copyright:

Available Formats

M0 0054 WDPF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M0 0054 WDPF

Uploaded by

Copyright:

Available Formats

Table of Contents

Section Title Page

Section 2. Remote Q-Line Overview

Section 3. Hardware Configuration and Installation

2/00 i M0-0054 (Rev 2)

Section 4. Cabinets and Cabling

Section 5. Remote Q-Line Specifications

Appendix A. Invalid QRC Switch Settings

M0-0054 (Rev 2) ii 2/00

Appendix B. MRC Status Algorithm

Appendix C. Remote Node Temperature Compensation

2/00 iii M0-0054 (Rev 2)

2/00 Changes-1 M0-0054 (Rev 2)

The WDPF Remote Q-Line I/O subsystem employs a serial, multi-node

2/00 1-1 M0-0054 (Rev 2)

1-2. Contents of this Document

Topics addressed include:

Section 3. Hardware Configuration and Installation covers setting jumpers and

Section 5. Remote Q-Line Specifications covers overall system power

Appendix C. Remote Node Temperature Compensation describes various

M0-0054 (Rev 2) 1-2 2/00

1-3. Additional Reference Documents

Table 1-1. Reference Documents

2/00 1-3 M0-0054 (Rev 2)

2-1. Section Overview

• Definitions of terms (Section 2-2).

• Purpose of remote Q-line (Section 2-3).

• Features of remote Q-line (Section 2-4).

• Remote I/O subsystem DIOB configuration (Section 2-5).

• Redundant applications (Section 2-6).

2/00 2-1 M0-0054 (Rev 2)

2-2. Definitions of Terms

M0-0054 (Rev 2) 2-2 2/00

2-3. Purpose of Remote Q-Line

Adding an RIOB to a DPU or TCU drop does

2/00 2-3 M0-0054 (Rev 2)

2-4. Features of Remote Q-Line

• Two styles of redundant serial communications medium are available:

— shielded twisted copper wire pairs

• Single or multiple Q-crate remote nodes.

M0-0054 (Rev 2) 2-4 2/00

2-5. Remote I/O Subsystem DIOB Configuration

2/00 2-5 M0-0054 (Rev 2)

TRC Panel TRC Panel

Remote Nodes Remote Nodes

M0-0054 (Rev 2) 2-6 2/00

2/00 2-7 M0-0054 (Rev 2)

Figure 2-3. Remote Q-Line Combination Local/Remote I/O

M0-0054 (Rev 2) 2-8 2/00

2-6. Redundant Controller Applications

2/00 2-9 M0-0054 (Rev 2)

3-1. Section Overview

• Hardware overview (Section 3-2).

• DIOB addressing (Section 3-3).

• MRC card (Section 3-4).

• QRC card (Section 3-5).

• QOR card (Section 3-6).

2/00 3-1 M0-0054 (Rev 2)

3-2. Hardware Configuration Overview