SM-6408E

SM-6408E
IUNION SWITCH & SIGNALI~
A member of the ANSALDO Group
5800 Corporate Drive, Piaaburgh, PA 15237
SERVICE MANUAL 6408E
Description, Installation and Operation
PRCCl1"
PROGRAMMABLE REMOTE CODE TO COMPUTER INTERFACE
US&S DDL-601/A/B APPLICATION
February, 1993
A-2193-2916-1
COPYRIGHT Hl93, UNION SWITCH & SIGNAL INC.
PRINTEO IN USA
ANSALDO
Trasporti
This document contains information which is proprietary to
Union Switch & Signal Inc., furnished to you on the following
conditions: no right or license in respect of this document
or its contents is given or waived in supplying this document
to you. This document or its contents are not to be used or
treated in any manner inconsistent with the rights and
interests of Union Switch & Signal Inc., or to its detriment
and are not to be copied, reproduced, disclosed to others or
disposed of except with prior written consent.
i
Revised and new pages of this manual are listed by page number and date:
Date
Date
ii
SECTION I
1.1
1.2
1.3
1.4
SECTION II
2.1
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.4
2.5
2.6
2.7
SECTION III
3.1
3.2
3.3
3.4
3.5
3.6
SECTION IV
GENERAL INFORMATION
INTRODUCTION • • . . •
OVERVIEV • • . . . .
ARCHITECTURE . . . • .
FLOV OF INFORMATION
...
•
. •
• ••
• • . •
1-1
1-1
1-1
1-2
INSTALLATION
APPLICATION FIRMVARE . . . .
. ••• 2-1
CPU A CONFIGURATION . . . .
2-1
PRCCI Address Select ion • . . • • • • •
. • 2-2
Office Baud Rate Selection • . . • . •
. • 2-2
Office Transmit Key-on Delay Selection.
. 2-2
Office Transmit Key-off Delay Selection
. 2-2
CPU B CONFIGURATION • • • . . • • • . •
. 2-5
Code System Type • . . • • • • • • • .
• • • 2-5
Baud Rate Selection . . • . • . • • •
2-5
Receive Data Accept Delay Selection • • .
• 2-5
No Response Timeout Selection . • • • •
.• 2-6
Transmitter Key-On/Off Delay Selection
2-6
CTC OFFICE INTERFACE. . . . .
. , •.
2-10
CODE LINE INTERFACE , , . • • .
2-13
TRIGGER OUTPUT . . . . . . . ,
2-14
LOCAL CONTROLS AND INDICATIONS
2-14
OPERATION
OVERVIEV • . • . . . . • •
FUNCTION LED DESCRIPTIONS
OUTPUT LED DESCRIPTIONS . . , •
INPUT LED DESCRIPTIONS.
OPERATIONAL MESSAGES.
ERROR MESSAGES . . . . . . . . •
.
. • •
.
...
.
. • • .
3-1
3-1
3-2
3-3
3-3
3-4
.•
• • •
•
•.•.•••
• .•.
.••.•.
.
•
. • •
.
• • • •
.
.
••••.•
.•
• •••.•
.•••••
• • •
•
••.•.
•
4-1
4-1
4-3
4-3
4-3
4-4
4-6
4-6
4-6
4-7
4-7
4-7
4-7
4-8
4-8
4-8
4-8
4-9
OFFICE INFORMATION EXCHANGE
OVERVIEV • . . . . . . , . •
4.1
PHILOSOPHY AND SECURITY •.
4.2
OFFICE GENERATED MESSAGES
4.3
Poll . . . . . . . . . . .
4.3.1
Acknowledge And Poll . •
•
4.3.2
PRCCI Initialization . .
4.3.3
Set Status Control Register
4.3.4
Status Indication Register Request
4.3.5
Indication Database Request . . •
4.3.6
Local Control Request
.
4.3.7
Execute Local Control
• • . .
4.3.8
Local Indication Recall
4.3.9
Control Request
4.3.10
Execute Control
. . • .
4.3.11
Indication Recall
4.3.12
Master Recall . . . • . • • • • •
4.3.13
Common Mode Request
4.3.14
PRCCI GENERATED MESSAGES.
4.4
iii
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
4.5
4.5.1
4.5.2
4.5.3
4.5.4
SECTION V
5.1
5.2
5.2.1
5.2.2
5.2.3
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.4
5.4.1
5.4.2
5.5
SECTION VI
6.1
6.2
6.3
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
6.4.8
6.4.9
6.4.10
6.4.11
6.4.12
6.5
SECTION VII
7.1
7. 2
Local Control Checkback • • • • •
. • • 4-9
Control Checkback . . • . • . .
. . . . . . 4-9
Status Indication Register Data
• 4-9
Indication
.....•.•...
• 4-9
Local Indication . . • . • • • • .
•• 4-9
Acknowledge . . • . • . • • • .
4-10
STATUS CONTROL AND INDICATION REGISTERS
4-10
Status Control Register O . • . . •
4-10
Status Indication Register O . . • • . . . • • 4-10
Status Control/Indication Register 1
4-11
Status Control/Indication Register 2.
4-12
FIELD INFORMATION EXCHANGE
OVERVIEV . • . . . . . . • • . • . . • • .
• •
CODE FORMAT • . . • • • .
•
Office To Field Transmissions
Field To Office Messages . • • . . • . . • • • .
Error Detection And Security • • • • .
PRCCI GENERATED MESSAGES.
• •••
Poll. • .
. ••.
•
Master.
• • •
Control
.....
Execute
• • • .
.
Priority .
. • • .
.
Common.
•
FIELD GENERATED MESSAGES
.
Co.ntrol Checkback . . •
• • •
Indication . . • . . . •
POLLING CYCLE DESCRIPTION
..••.
5-1
5-1
5-1
5-2
5-2
5-2
5-3
5-3
5-3
5-4
5-4
5-4
5-4
5-5
5-5
5-5
MAINTENANCE SESSION
-
OVERVIEV • • . . . . . . . • •
. . . . . . 6-1
NUMERIC CODE LINE INFORMATION
. • . • 6-1
OPENING A MAINTENANCE SESSION . . . . . .
. 6-2
COMMAND DESCRIPTIONS
. . . . . . . 6-3
CLEAR . . • . . . . •
, • • • 6-4
DISCONNECT . . . . . . •
6-4
HELP • • .
. . . . . . 6-4
HISTORY
. . . . . . 6-5
LOGIN • • .
6-6
LOGOUT ••
. . . . . . . . . . . . 6-6
MONITOR
• 6-6
RECALL •.
. 6-8
RESET .
. . 6-8
. . . . . . 6-8
SET
SHOY . • .
6-12
SUPPRESS
6-15
ERROR MESSAGES
6-15
SUPPLEMENTAL INFORMATION
CONVENTIONS . . . . . .
. • • • .
• •• , 7-1
OFFICE TO PRCCI MESSAGES • . • • • • • • • • • • • 7-1
iv
.................
... ......
7.2.1
Poll
7.2.2
Acknowledge And Poll
PRCCI Initialization (DDL-601B Only)
7.2.3
PRCCI Initialization (DDL-601/A Only)
7.2.4
Set Status Control Register
7.2.5
Status Indication Register Request
7.2.6
7.2.7
Indication Database Request
7.2.8
Local Control Request
7.2.9
Execute Local Control
7.2.10
Local Indication Recall
7.2.11
Control Request
7.2.12
Execute Control
7.2.13
Indication Recall
7.2.14
Master Recall .
7.2.15
Common Mode Request
7.3
PRCCI TO OFFICE MESSAGES
7.3.1
Local Control Checkback
7.3.2
Control Checkback
7.3.3
Status Indication Register Data
.
7.3.4
Indication
7.3.5
Local Indication
Acknowledge
7.3.6
....
. 7-1
..
. . . . 7-2
7-2
. . . . . 7-3
. 7-3
7-3
7-4
. . 7-4
. 7-4
. . 7-4
. 7-5
.
. .. 7-5
7-5
7-5
. 7-6
.. .. 7-6
7-6
....
.........
.......
......
..
.....
.......
. . . 7-6
7-6
....
...
.
.
.
7-7
.....
7-7
......
7-7
v
ILLUSTRATIONS
Figure
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
2-14
2-15
2-16
2-17
2-18
2-19
2-20
4-1
4-2
4-3
4-4
4-5
4-6
5-1
5-2
5-3
5-4
5-5
15!
Binary Yeights For Switch Positions
PRCCI Address Examples
sva Switch Assignments (CPU A)
Office Baud Rate Options
Office Transmit Key-on/off Delay Options
SY7 Switch Assignments (CPU B)
Code System Type options
Baud Rate Options
SYS Switch Assignments (CPU B)
Receive Data Accept Delay Options
No Response Timeout Examples
SY9 Switch Assignments (CPU B)
Transmitter Key-on/off Delay Options
Bit Time Table
Asynchronous Character Format (Office)
RS-232C Compatible Interface Specifications
Remote Installation Using Multiple PRCCI Units
Line/Local Interface Assignments
Typical RFL Type Carrier Interface
Typical DCS Type Carrier Interface
Office Generated Messages
PRCCI Generated Messages
SCRO Flags
SIR O Flags
SCR/SIR 1 Flags
SCR/SIR 2 Flags
DDL-601/A/B Address Word
DDL-601/A/B Control Word
DDL-601/A/B Indication Word
DDL-601/A/B Bit Identification
DDL-601/A/B Address Word Structure by Mode
vi
2-3
2-3
2-4
2-4
2-5
2-7
2-7
2-8
2-8
2-8
2-9
2-9
2-10
2-10
2-11
2-12
2-13
2-14
2-15
2-16
4-2
4-3
4-10
4-10
4-11
4-12
5-6
5-6
5-6
5-6
5-7
SECTION I
GENERAL INFORMATION
1.1
INTRODUCTION
This manual describes the installation and operation of the Union Switch
& Signal Programmable Remote Code to Computer Interface (PRCCI) applied
as an office code unit to a US&S DDL-601/A/B code system.
The
information in this manual supplements service manual 6408, Hardware
Description and Installation, with information on firmware installation,
DIP switch programming, communications, and general operation.
The term "application", as used by this
applied to any DDL-601/A/B code line. The
a PRCCI applied to a specific code line at
"office" refers to the CTC office computer
1.2
manual, refers to a PRCCI
term "installation" refers to
a specific site.
The term
system.
OVERVIEV
The PRCCI is a microprocessor based device whose primary purpose is to
logically interface a CTC office computer system to a single field code
line. The unit serves as the mechanism by which the office delivers
control information and receives indication information. The unit, once
initialized, functions independently of the office and may directly
manipulate the code line interface without intervention from the office.
Manipulation of the code line interface to transmit and receive
information is transparent to the office. The office itself is only
conc~rned with the buffered information that represents code line data.
Control information from the office is buffered by the PRCCI until such
time that it can be transmitted on the code line. Likewise, indication
information from the code line, as well as certain types of status
information, is buffered by the PRCCI until such time that it can be
transmitted to the office.
1.3
ARCHITECTURE
The PRCCI design incorporates a dual-microprocessor architecture. These
microprocessors reside on separate but identical printed circuit boards
(CPU A and CPU B). The two processor boards communicate with each other
over an internal, asynchronous, serial data channel. CPU A is the
master on this circuit and CPU B is permitted to respond only when
addressed.
CPU A is primarily responsible for communication with the
office. This includes the implementation of the office protocol on both
the normal (Jl) and standby (J2) channels, as well as the interactive
6408E, p. 1-1
maintenance session. CPU B is primarily responsible for code line
communication and control of the front panel display. A ribbon cable
connects CPU B with the interface board. The interface board physically
provides the processor access to the line/local inputs and outputs as
well as the discrete LEDs and alphanumeric display on the front panel.
This configuration allows for optimum utilization of each processor
while minimizing inter-processor communication.
1.4
FLOY OF INFORMATION
Information from an office is first received by CPU A and subjected to
lower level hardware and protocol level verification. CPU A informs CPU
B that information has been received and determines if the message is
addressed to the unit and requires further processing.
Certain classes of messages are processed directly by CPU A.
The
responses to these messages are determined by CPU A. Most classes of
messages however, require that CPU A pass the received message to CPU B
for additional verification and subsequent processing. In general, for
these messages, the response of CPU B determines the response of CPU A
to the office. CPU B may typically respond to CPU A with any buffered
information that it has at the time. This excludes certain maintenance
session messages that require specific responses and cases where
Regardless of the level of
messages fail verification by CPU B.
activity in office communication, CPU A regularly polls CPU B for
information. This allows to unit to detect internal failures and, to a
certain extent, function independently of office communication.
6408E, p. 1-2
SECTION II
INSTALLATION
2.1
APPLICATION FIRMYARE
All PRCCI applications require specific Erasable Programmable Read Only
Memory (EPROM) sets to be installed in each CPU board. Each set is
assigned a part number and is ordered separately from the PRCCI unit
itself.
Each EPROM within a set is identified by an individual part
number for manufacturing and distribution purposes.
A label on each
EPROM specifies individual EPROM part number, revision level, IC socket,
and CPU board (A or B) assignments.
Yhen installing or removing an EPROM, keep the device aligned squarely
with the socket to prevent bending and breaking the pins. Do not
install an EPROM with bent, broken, or severely fatigued pins.
They
could break off within the socket, possibly requiring removal and
replacement of the socket. The notches in the socket and EPROH must be
aligned to avoid damage to the device when power is applied.
Random Access Memory (RAM) IC devices are necessary for operation of
each cpu board.
The exact number required varies with each EPROM set
and may change from one revision to the next. As a general rule, any of
the IC sockets IClO, ICll, IC12, IC13, IC14, and IC15 that are not used
for the EPROM set, should contain RAM devices.
IC socket IC9 must
always contain a RAM device while IC socket IC16 must always contain the
designated EPROM from the set.
2.2
CPU A CONFIGURATION
The DDL-601/A/B application of the PRCCI requires EPROM set number
N451800-0114 installed in CPU A. This is a general purpose set, also
used in other PRCCI applications. It primarily supports communication
with the office computer system and provides the maintenance session
capability.
Unless dictated by the installation, all jumpers on the board should be
placed in the standard positions. Switches SYl, SY2, SY3, SY4, SYS, and
SY6 must be placed in the EPROM position.
Refer to the Hardware
Description and Installation service manual for information on the
standard positions of these items. Any variations from the standard
positions should be reflected in site specific plans.
6408E, p. 2-1
DIP switch packs SY7 and SYS are used to select various parameters that
affect communication with the office computer system. Programming of
these switches is dictated by the installation and should be reflected
in site specific plans.
SV9 is not used and all switches should be
placed in the closed position. The PRCCI must be reset for any switch
changes to take effect.
2.2.1
PRCCI Address Selection
The address assigned to the PRCCI must be programmed into SY7.
It is
entered as an eight bit, binary value between 1 and 255 (decimal). An
address of zero (all switches closed) is illegal. Figures 2-1 and 2-2
give the binary weighted values of the switches in SY7 and some examples
of address selections.
2.2.2
Office Baud Rate Selection
The baud rate used to communicate with the office must be programmed
into SY8.
The rate selected is used on both the normal (Jl) and
standby/maintenance (J2) channels. Figures 2-3 and 2-4 list the switch
assignments and their options.
2.2.3
Office Transmit Key-on Delay Selection
The key-on delay time used in communication with the office must be
programmed
into
SY8.
The delay time selected is used in the
transmission of responses to the office on the both the normal (Jl) and
standby/maintenance (J2) channels.
This parameter, measured in bit
times, determines the time between the assertion of request to send
(RTS) and the beginning of data transmission. A nominal 4 bit times is
recommended to compensate for carrier turn-on delay. The key-on delay
may have to be lengthened to compensate for any additional delays
imposed by modems, repeaters, leased circuits, or microwave equipment.
Figures 2-3 and 2-5 list the switch assignments and their options.
A typical repeater characteristically delays and shortens the carrier
key-on signal (RTS) by some pre-determined time. This time is typically
measured in bit times and is specific to the type of repeater used.
Consult documentation on the specific repeater(s) in use for the delay
times imposed. If that information is not available allow a nominal 3
bit time delay for an amplifier repeater and a nominal 7 bit time delay
for a regenerative repeater.
2.2.4
Office Transmit Key-off Delay Selection
The key-off delay time used in communication with the office must be
programmed
into
SYS.
The delay time selected is used in the
transmission of responses to the office on the both the normal (Jl) and
standby/maintenance (J2) channels.
This parameter, measured in bit
times, determines the time between the end of data transmission and the
de-assertion of request to send (RTS).
A nominal 4 bit times is
recommended to ensure that all data bits have transmitted on the carrier
circuit and to help prevent transients that could reduce data integrity.
The key-off delay may have to be lengthened to compensate for any
6408E, p. 2-2
additional delays imposed by modems, repeaters, leased circuits, or
microwave equipment. Figures 2-3 and 2-5 list the switch assignments
and their options.
A repeater, particularly a regenerative as opposed to an amplifier, may
tend
to
buffer and
delay the transmission of data,
Consult
documentation on the specific repeater(s) in use for the delay that it
may impose. If that information is not available allow a nominal 7 bit
time delay for a regenerative repeater. Allow a nominal 4 bit times for
carrier modulation/demodulation delay in an amplifier repeater.
8
7 6 5
4
3 2 1
OPEN= 1
CLOSE= 0
128 64 32 16 8
4 2 1
<-- BINARY WEIGHT
IN DECIMAL
Figure 2-1.
Binary 'Weights For Switch Positions
SY7:
8 7 6 5 4 3 2 1
PRCCI
ADDRESS
cccccccc
ILLEGAL
CCCCCCCO
C C C C CC OC
CCCCCCOO
CCCCCOCC
C C C C C OC O
CCCCCOOC
C C C CC OOO
CCCCOCCC
...
0 0 0 0 0 0 CO
0 0 0 0 0 0 0 C
0 0 0 0 0 0 0 0
Figure 2-2.
1
2
3
4
5
6
7
8
...
253
254
255
PRCCI Address Examples
6408&, p. 2-3
8 7 6 5 4 3 2 1
SVS
~~~~8888
I
OPEN= 1
CLOSE= 0
~ F I C E BAUD RATE
~ OFFICE TRANSMIT KEY-OFF DELAY
OFFICE TRANSMIT KEY-ON DELAY
Figure 2-3.
sva
Switch Assignments (CPU A)
SV8:
4 3 2 1
OFFICE
BAUD RATE
SV8:
4 3 2 1
OFFICE
BAUD RATE
cccc
1200
1200
1200
1200
1200
150
300
600
OCCC
OCCO
OCOC
OCOO
0 0 CC
0 0 CO
0 0 0 C
0 0 0 0
1200
2400
4800
9600
1200
1200
1200
1200
CCCO
CCOC
CCOO
COCC
COCO
COOC
COOO
Figure 2-4.
Office Baud Rate Options
6408E, p, 2-4
SYS:
8 7
OFFICE TRANSMIT
KEY-ON DELAY
SYS:
6 5
cc
4 BIT TIMES
8
16
32
cc
4 BIT TIMES
CO
OC
8
CO
OC
0 0
Figure 2-5.
2.3
0 0
OFFICE TRANSMIT
KEY-OFF DELAY
16
32
Office Transmit Key-on/off Delay Options.
CPU B CONFIGURATION
The DDL-601/A/B application of the PRCCI requires EPROM set number
N451800-0104 installed in CPU B. This is a special purpose set, unique
to this application, that enables the PRCCI to communicate with a
DDL-601/A/B code system.
Unless dictated by the installation, all jumpers on the board should be
placed in the standard positions. Switches SVl, SY2, SV3, SV4, SYS, and
SV6 must be placed in the EPROM position.
Refer to the Hardware
Description and Installation service manual for information on the
standard positions of these items. Any variations from the standard
positions should be reflected in site specific plans.
DIP switch packs SV7, SYS, and SV9 are used to select various parameters
associated with field communication. The PRCCI must be reset to affect
any switch changes.
2.3.1
Code System Type
The code system type must be programmed into SV7. Figures 2-6 and 2-7
list the switch assignments and options for the supported code systems.
2.3.2
Baud Rate Selection
The baud rate used by the PRCCI to communicate with the field code
equipment must be programmed into SY7. Programming is dictated by the
installation and should be reflected in site specific plans.
Figures
2-6 and 2-8 list the switch assignments and their options.
2.3.3
Receive Data Accept Delay Selection
The receive data accept delay must be programmed into SV8.
This
parameter, measured in bit times, determines when the PRCCI will begin
to accept received data after carrier has turned on.
The purpose of
this delay is to provide the PRCCI with immunitiy from transients caused
6408E, p. 2-5
by the carrier circuit turning on. For proper operation, this time must
be shorter than the field key-on delay selected for any field code unit.
Figures 2-9 and 2-10 list the switch assignments and their options.
2.3.4
No Response Timeout Selection
The no response timeout, also refered to as the mean time before
response, must be programmed into SVB. This parameter, measured in
milliseconds, determines the length of time that the PRCCI waits for a
response to each message that it transmits. For proper operation, the
time selected must be equal to or greater than the time between key-off
of office carrier and receipt of field carrier (carrier detect) at the
PRCCI. Figures 2-9 and 2-11 list the switch assignments and their
options.
To calculate this time, consider the possible delay factors listed below
and determine the time associated with each. Select a DIP switch option
that exceeds the total time of all delay factors. For factors measured
in bit times, refer to figure 2-14 to convert a single bit time to
milliseconds at the selected baud rate. Factors to be considered in the
no response timeout calculation include:
1. Carrier modulation/demodulation delay. The signal modulation and
demodulation circuits internal to medium speed (300 to 1200 BPS)
FSK modems and repeaters typically impose a delay on
data
throughput.
This delay is typically measured in bit times and is
specific to the type of equipment used. Consult documentation on
the particular type of equipment in use. If information is not
available allow a nominal 4 bit time delay for each time that the
carrier signal must be (re-)modulated and demodulated.
2. Carrier propagation delay. On open line wire a carrier signal
propagates at approximately 179,000 miles/second or about 0.56
milliseconds for every 100.miles. In #19 cable a carrier signal
propagates at approximately 46,900 miles/second or about 2.13
milliseconds for every 100 miles.
3. Leased telephone circuits may impose additional delays.
The
characteristics and magnitude of such delays may be specific to the
supplier. Under normal circumstances this calculation should be
based on the maximum allowable delay as prescribed by current
tariff regulations.
4. Any other possible source of carrier delay, such as a microwave
link, that is unique or specific to the installation. If such a
source exists, be sure to consider the maximum delay that could be
imposed, not just an average delay.
2.3.5
Transmitter Key-On/Off Delay Selection
The transmitter key-on and key-off delays imposed by the PRCCI in
communication with the field equipment must be programmed into SY9.
Key-on delay, measured in bit times, determines the time between
carrier key-on and the beginning of data transmission. Its primary
purpose is to compensate for carrier turn-on delay. Key-off delay,
also measured in bit times, determines the time between the end of
6408E, p. 2-6
data transmission and carrier key-off. Its primary purpose is to
ensure that the carrier remains turned on until all data bits have
been transmitted on the circuit and to help prevent transients that
could reduce data integrity.
A nominal 4 bit times is recommended for the selection of the
key-on/off delays.
However, the delays may have to be lengthened
to compensate for any additional delays imposed by
modems,
repeaters, leased circuits, or microwave equipment. Repeaters
characteristically delay and shorten the carrier key-on signal by
some pre-determined time and may also tend to buffer and delay the
transmission of data, requiring a longer key-off delay to complete
transmissions.
Consult documentation on the specific repeater(s)
in use for the delay times imposed. Figures 2-12 and 2-13 list the
switch assignments and their options.
8
SV7
7
6 5
3
4
2
1
BBBB~~B~
tDE
OPEN== 1
CLOSE= 0
I
[ CODE SYSTEM TYPE
LINE BAUD RATE
Figure 2-6.
SV7 Switch Assignments (CPU B)
SV7:
5 4 3 2 1
CODE SYSTEM TYPE
COOCO
OCOOO
DDL-601/A
DDL-601B
Figure 2-7.
Code System Type Options
6408E, p. 2-7
SY7:
8 7 6
CODE LINE
BAUD RATE
c c c
RESERVED
100
200
400
600
1200
1600
2400
CCO
C OC
COO
OCC
OCO
0 0 C
0 0 0
Figure 2-8,
8
SW
7 6 5
4
Baud Rate Options
3
2 1
88888888
I
l
~
cccc
CCCO
CCOC
CCOO
C OC C
COCO
COOC
COOO
CLOSE= 0
RESPONSE TIMEOUT
RECEIVE DATA ACCEPT DELAY
Figure 2-9,
SV9:
8 7 6 5
OPEN• 1
SY8 Switch Assignments (CPU B)
RECEIVE DATA
ACCEPT DELAY
(BIT TIMES)
0
1
2
3
4
5
6
7
SV9:
8 7 6 5
CC
CO
OC
OO
0 0 CC
0 0 CO
0 0 0 C
RECEIVE DATA
ACCEPT DELAY
(BIT TIMES)
OC
OC
OC
OC
11
OOOO
12
13
14
15
6408E, p. 2-8
8
9
10
Figure 2-10.
Receive Data Accept Delay Options
SV9:
8 7 6 5
NO RESPONSE
TIMEOUT (MS)
SV9:
8 7 6 5
cccc
10
20
OCCC
OCCO
OC OC
OC OO
CCCO
CCOC
CC OO
COC C
COCO
COOC
COOO
so
100
150
200
250
300
Figure 2-11.
8
7 6 5
0
0
0
0
0
0
0
0
C
C
0
0
NO RESPONSE
TIMEOUT (MS)
C
O
C
0
350
400
450
500
750
850
1000
1250
No Response Timeout Options
4 3 2 1
OPEN• 1
CLOSE= 0
T
~TRANSMITTER KEY-ON DELAY
TRANSMITTER KEY-OFF DELAY
Figure 2-12.
SV9 Switch Assignments (CPU B)
6408E, p. 2-9
SV9:
4 3 2 1
KEY-ON DELAY
(BIT TIMES)
SV9:
8 7 6 5
KEY-OFF DELAY
(BIT TIMES)
cccc
4
cccc
4
8
12
16
20
24
28
32
36
40
44
48
52
56
60
64
CCCO
CCOC
CCOO
COC C
COC O
COOC
COOO
OC C C
OCC O
OC OC
OCOO
0 0 CC
0 0 CO
0 0 0 C
0 0 0 0
CCCO
C C OC
CCOO
COCC
COCO
COOC
C OOO
OCC C
OC C O
OCOC
OC OO
0 0 CC
0 0 CO
0 0 0 C
0 0 0 0
8
12
16
20
24
28
32
36
40
44
48
52
56
60
64
Figure 2-13.
Transmitter Key-On/Off Options
BAUD RATE
(BITS/SEC)
BIT TIME
(MS/BIT)
100
200
400
600
1200
1600
2400
10.0000
5.0000
2.5000
1.6667
0.8333
0.6250
0.4167
Figure 2-14.
2.4
Bit Time Table.
CTC OFFICE INTERFACE
The CTC office system communicates with a PRCCI over either a normal or
standby asynchronous, serial channel. Both are available at connectors
Jl (NORMAL) and J2 (STANDBY/MAINT), located at the rear of the unit.
The office protocol is only permitted to be active on one channel at a
time. The standby channel, when not active with the office protocol,
may be connected to an ANSI standard terminal to access the maintenance
session. This channel functions in only one mode at a time. The office
protocol, regardless of whether a maintenance session is opened or not,
always takes precedence.
6408E, p. 2-10
Both channels utilize a word format of 1 start bit, 8 data bits, no
parity, and 1 stop bit. The baud rate is selectable with DIP switches
and both operate at the same speed.
The transmission of a character requires that the circuit transition
from an idle HARK state to the SPACE state for one bit time. This first
transition is called the start bit. During the next eight bit times,
the circuit transitions between MARK and SPACE, as required, to
represent the character. The least significant bit of the character is
transmitted first.
The circuit is then forced to the MARK state for a
minimum of one bit time. This final state is called the stop bit.
Its
primary functions are to frame the transmitted character and to ensure
that the next start bit may be recognized as a MARK to SPACE transition.
Figure 2-15 depicts the asynchronous character format utilized on the
circuit.
8 DATA BITS
1
MARK -V ~ - T
(IDLE)
LSB
SPACE +V
I-
L___J
-
T -
T -
T -
T -
I
T -
T -
MSB
I
~- ~- ~-~- ~- ~- ~-;
START
BIT
r 1
--1. 0
L___J
L___J
STOP
BIT
START
BIT
TIME>
Figure 2-15.
Asynchronous Character Format (Office)
As discussed in the Hardware Description and Installation service
manual, these channels are .RS232C compatible. Figure 2-16 provides
interface specifications for the available signals. In figure 2-17, a
typical office interface is shown using multiple, remotely located PRCCI
units connected, through an EIA bridge, to a modem.
6408E, p. 2-11
PIN
STATE
VOLTAGE
TXD
TRANSMIT DATA
2
MARK
SPACE
-3 TO -15
+3 TO +15
OUTPUT
RXD
RECEIVE DATA
3
MARK
SPACE
-3 TO -15
+3 TO +15
INPUT
RTS
REQUEST TO SEND
4
OFF
ON
-3 TO -15
+3 TO +15
OUTPUT
CTS
CLEAR TO SEND
5
OFF
ON
-3 TO -15
+3 TO +15
INPUT
DSR
DATA SET READY
6
OFF
ON
-3 TO -15
+3 TO +15
INPUT
SIGNAL GROUND
7
---
0
---
DCD
DATA CARRIER DETECT
8
OFF
ON
-3 TO -15
+3 TO +15
INPUT
DTR
DATA TERMINAL READY
20
OFF
ON
-3 TO -15
+3 TO +15
OUTPUT
SIGNAL
NOTES:
DIRECTION
1) VOLTAGES REFERENCED TO SIGNAL GROUND
2) DATA STATE IS UNDEFINED IN TRANSITIONAL REGION
BETVEEN -3 AND +3 VOLTS.
Figure 2-16.
RS-232C Compatible Interface Specifications
6408E, p. 2-12
PRCCI 1
2
>>
3
>>
>>
4
>>
7
>>
8
TXD
RXD
RTS
SG GND
DCD
«
«
«
«
«
>>
>>
>>
»
>>
TXD
RXD
RTS
SG GND
DCD
«
«
«
NORMAL
MODEM
<<
«
NORMAL
EIA
BRIDGE
Jl
PRCCI 2
2
>>
3
>>
4
>>
7
>>
8
>>
TXD
RXD
RTS
SG GND
DCD
«
«
«
«
<<
Jl
NOTES:
1)
A STANDBY MODEM AND EIA B~IDGE MAY BE VIREO IN A
SIMILAR FASHION TO THE J2 CONNECTOR(S).
2) ONLY TXD, RXD, AND SIGNAL GROUND ARE REQUIRED FOR
MINIMAL INTERFACE, OTHER INPUT SIGNALS ARE
INTERNALLY ASSERTED VHEN NOT VIREO.
Figure 2-17.
2.5
Remote Installation Using Multiple PRCCI Units
CODE LINE INTERFACE .
The interface to external code line communication equipment is provided
by the line/local outputs and inputs available through CONNECTOR A and
CONNECTOR C, located at the rear of the unit.
Transmitter channel
outputs are provided for carrier KEY ON and KEY SPACE through line
outputs 1 and 2 respectively. The speed of the communication circuit
dictates the use of solid-state output modules. Indication channel
6408E, p. 2-13
inputs are provided for DATA CARRIER DETECT (DCD) and SPACE through line
inputs 1 and 2 resp~ctively. The input and output assignments for the
code line interface are summarized in figure 2-18. Figure 2-19 is an
example of a typical BIA-level interface to an RFL type carrier unit. A
typical TTL-level interface to a US&S DCS type carrier unit is shown in
figure 2-20.
2.6
TRIGGER OUTPUT
A trigger output is provided by line/local output 3, available through
CONNECTOR A, located at the rear of the unit. This output serves as a
diagnostic tool for indication channel maintenance.
Yith minimal
external wiring, either a solid-state or relay output module may be used
to provide a trigger signal to test equipment, such as a storage
oscilloscope.
2.7
LOCAL CONTROLS AND INDICATIONS
A maximum of five local control outputs are available to the office.
These are provided by line/local outputs 4, 5, 6, 7, and 8, available
through CONNECTOR A and CONNECTOR B, located at the rear of the unit. A
maximum of six local indication inputs are available to the office.
These are provided by line/local inputs 3, 4, 5, 6, 7, and 8, available
through CONNECTOR C, located at the rear of the unit. The use of these
is dictated by installation requirements and should be reflected in site
specific plans.
Detailed information and specifications of the
line/local interface are available in the Hardware Description and
Installation service manual.
LINE/LOCAL
INTERFACE
FUNCTION
OUTPUT 1
OUTPUT 2
TRANSMITTER KEY ON
TRANSMITTER KEY SPACE
OUTPUT 3
TRIGGER OUTPUT
INPUT 1
INPUT 2
RECEIVER DATA CARRIER DETECT
RECEIVER SPACE
Figure 2-18.
Line/Local Interface Assignments
6408E, p. 2-14
PRCCI
CARRIER
KEY ON
A-10
«
>>
KEY SPACE
A-4
DCD
C-1
SPACE
>>
<<
»
«
C-3
»
«
A-7
A-1 _J
»
«
A-5
A-11 _J
»
«
C-2
C-4 _J
»
«
»
A-22
KEY-ON
XMTR
KEY-HI
CD
RCVR
REC-HI
-12V
+12V
POVER
SUPPLY
COM
O TRIGGER
CONNECTOR A, CONNECTOR C
NOTES:
1) TRIGGER OUTPUT SHOYN WIRED FOR SOLID-STATE
OUTPUT MODULE.
2) OUTPUT MODULES CONFIGURED FOR EIA OPERATION.
Figure 2-19.
Typical RFL Type Carrier Interface
6408E, p. 2-15
PRCCI
CARRIER
KEY ON
A-10
«
»
KEY SPACE
A-4
DCD
C-2
SPACE
C-4
A-5
A-11
C-1
C-3
-
»
<<
»
«
»
«
>>
«
-
A-2
A-8
A-14
D
«
»
>>
A-22
KEY-ON
XMTR
KEY-HI
CD
RCVR
REC-HI
+SV
ov
POVER
SUPPLY
O TRIGGER
CONNECTOR A, CONNECTOR C.
NOTES:
1) TRIGGER OUTPUT SHOYN WIRED FOR SOLID-STATE
OUTPUT MODULE.
2) OUTPUT MODULES CONFIGURED FOR TTL OPERATION.
Figure 2-20.
Typical DCS Type Carrier Interface
6408E, p. 2-16
SECTION III
OPERATION
3.1
OVERVIEV
Vhen power is first applied or the master reset switch is pressed, each
cpu board independently executes self-tests to verify the integrity of
the EPROH set and RAH. Following successful completion of these tests,
the DIP switches are read, the code type being emulated is displayed on
the front panel (Ex. EMULATE DDL601), and the PRCCI waits for the
office to establish communication.
In the event that one of the self-tests fail, the watchdog timer is
allowed to trip and reset the cpu board. This is indicated by LEDl
flashing on the failed cpu board. Should an error message be displayed,
refer to section 3,6 for corrective action.
Briefly, the office should initialize the PRCCI and configure it to the
installation, The office then requests indications from all stations on
the code line through a sequence of individual recall, or master mode,
requests.
Vhen there are no pending control or master mode requests to·
transmit the PRCCI independently polls the field code units in a round
robin fashion. This is indicated by only a station address displayed on
the front panel.
3.2
FUNCTION LED DESCRIPTIONS
Seven of the eight LEDs in this group are software controlled status
indicators for various functions under software control of the PRCCI.
The remaining LED is a hardware driven power indicator.
A brief
description of each LED and its associated function is given below.
FUNCTION XMT
This LED denotes a FIELD TRANSMIT function.
Vhen illuminated it
indicates that the PRCCI is transmitting data to the field
communication equipment.
FUNCTION REC
This LED denotes a FIELD RECEIVE function.
Vhen
indicates
that the PRCCI is receiving data
communication equipment.
6408E, p. 3-1
illuminated, it
from the field
FUNCTION GM
This LED denotes a GOOD MESSAGE function.
It reflects message
traffic between the cpu boards. A flash rate of once per second
indicates normal internal polling of CPU B by CPU A. A faster rate
indicates message traffic between the PRCCI and the office.
FUNCTION ERR
This LED denotes a HOST ERROR function.
Yhen illuminated, it
indicates that an error has been detected in communication with the
office.
It
remains
illuminated
until
communication
is
re-established with the office.
FUNCTION A
This LED denotes an ADDRESS ACCEPT function. Yhen illuminated,
indicates that the PRCCI is being addressed by the office.
it
FUNCTION B
This LED denotes a STANDBY PORT ACTIVE function. Vhen illuminated,
it indicates that the office is communicating with the PRCCI over
the standby channel.
FUNCTION C
This LED denotes a MAINTENANCE SESSION ACTIVE function.
Yhen
illuminated, it indicates that a maintenance session is opened.
FUNCTION D
This LED is a hardware indication of the S volt output
PRCCI power supply and should be illuminated constantly.
3.3
from
the.
OUTPUT LED DESCRIPTIONS
The LEDs in this group are state indicators for each of the line/local
outputs. Yhile the outputs themselves are under software control, these
LEDs reflect the actual hardware state of the output module control
circuits.
OUTPUT 1
This LED reflects the state of the KEY ON output to the carrier
transmitter.
Vhen illuminated, it indicates that the output is
active.
OUTPUT 2
This LED reflects the state of the KEY SPACE output to the carrier
transmitter.
Vhen illuminated, it indicates that the output is
active.
6408E, p. 3-2
OUTPUT 3
This LED reflects the state of the trigger output.
It should
normally remain dark and flash only when the trigger is activated.
OUTPUTS 4, 5, 6, 7 and 8
These LEDs reflect delivery of the available local control outputs.
They should normally remain dark and flash only when the associated
local control is delivered.
3.4
INPUT LEO DESCRIPTIONS
The LEDs in this group are hardware driven state indicators for each
the line/local inputs.
of
INPUT 1
This LEO reflects the state of the DATA CARRIER DETECT (DCO) input
from the carrier receiver. When illuminated, it indicates that DCD
is present.
INPUT 2
This LED reflects the state of the SPACE input from the carrier
receiver. When illuminated, it indicates that the input is active.
INPUTS 3, 4, 5, 6, 7, and 8
These LEDs reflect the state of the available local indication
inputs,
When illuminated, they indicate that energy is applied to
the associated input.
3.5
OPERATIONAL MESSAGES
EMULATE DDL601
EMULATE DDL601B
This message is displayed upon power-up, reset, and initialization
from the office computer system. Following initialization, this
message is normally replaced with other operational messages or
station addresses are displayed as the polling cycle progresses.
CONTROL NN
This message indicates that the PRCCI is transmitting a control
station address NN.
to
CHKBAK NN
This message indicates that the PRCCI has processed a control
checkback from station address NN and is transmitting an execute
mode to that station. This capability is supported only by the
DDL-601B code system.
6408E, p. 3-3
MASTER NN
This message indicates that the PRCCI is transmitting a master mode
to station address NN to recall all current indications from that
station.
PRIORITY NN
This message indicates that the PRCCI is transmitting a priority
mode to station address NN to acknowledge any priority indication
bits.
COMMON
This message indicates that the PRCCI is transmitting a common mode
to all stations on the code line.
KEY MARK
This message indicates that the PRCCI is in line maintenance mode,
transmitting a rest state of MARK to the code line communication
equipment.
This capability is
only
provided
through
the
maintenance session.
KEY SPACE
This message indicates that the PRCCI is in line maintenance mode,
transmitting an inverted rest state (norest) of SPACE to the code
line communication equipment. This capability is only provided
through the maintenance session.
KEY DUTY CYCLE
This message indicates that the PRCCI is in line maintenance mode,
transmitting a 50% duty cycle to the code line communication
This capability is
only
provided
through
the
equipment.
maintenance session.
CODE LINE NORMAL
This message indicates that line maintenance mode has just been
turned off and that normal code line operation has not yet resumed.
This message will remain on the front panel if the PRCCI is not
initialized.
3.6
ERROR MESSAGES
E
This error flag may appear on the front panel immediately to the
right of the station address. It indicates either that the carrier
receiver turned off prematurely or that a BCH error was detected in
a response from the field.
A limited number of these errors over a period of time is to be
expected and does not necessarily indicate improper operation of
the code line.
Should the number of these errors reach an
unacceptable level, it should be considered an indication of poor
6408E, p. 3-4
line quality,
failure.
communication equipment
failure,
or
field
unit
M
This error flag may appear on the front panel immediately to the
right of the station address.
It indicates that a monitor
condition has been declared for the station due to repeated errors.
A limited number of these errors over a period of time is to be
expected and does not necessarily indicate improper operation of
the code line.
Should the number of these errors reach an
unacceptable level, it should be considered an indication of poor
line quality, communication equipment failure, or field unit
failure.
F
This error flag may appear on the.front panel immediately to the·
right of the station address. It indicates that a failed condition
has been declared for the station due to repeated errors.
This
condition indicates either a failure of the communication circuit
or equipment or a failure of the field unit.
INVALID !NIT
An incorrect initialization message was received from the office.
The message passed communication hardware checks and protocol level
checks, but the contents of the message do not
meet
the
requirements of the DDL-601/A/B application.
Once the PRCCI
receives an invalid initialization message, it ceases normal code
line operation and requests initialization from the office.
This may reflect a possible problem in the office or that the PRCCI
is not connected to the.office through the correct communication
channel.
This error should never occur with an
in-service
installation.
"WRONG CODE TYPE
No code type has been programmed into DIP switch SY7 on CPU B. The
PRCCI allows the watchdog timer to trip and reset CPU B until the
condition is corrected. Refer to section 2.3 (CPU B Configuration)
for programming information.
CHECKSUM ERROR
The checksum calculated by CPU B for the installed EPROM set does
not match the checksum physically programmed into the set. Verify
that the correct EPROMs are installed in the appropriate sockets.
This could also indicate a defective EPROM set or CPU board. The
PRCCI allows the watchdog timer to trip and reset CPU B until the
condition is corrected.
6408E, p. 3-5
BAD RAM
The self-test of RAM performed by CPU B failed to complete
successfully.
Verify that sockets IC9 through IC14 contain RAH
devices unless required to contain an EPROH.
This could also
indicate an improperly installed or defective RAM device or a
defective CPU board. The PRCCI allows the watchdog timer to trip
and reset CPU B until the condition is corrected.
6408E, p. 3-6
SECTION IV
OFFICE INFORMATION EXCHANGE
4.1
OVERVIEV
The scheme for communication with the office computer system is similar
to that used on a half duplex code lirie circuit where the office is the
master to one or more slave PRCCI units. The protocol is designed to
complement that used by the Union Switch & Signal GENISYS Non-vital
Logic Emulator. This permits multiple PRCCI and GENISYS units to
co-exist on the same communication circuit. Any GENISYS units must
appear as slaved field code units.
All conversations on this circuit are initiated by the office and only
the addressed unit is permitted to respond. If the unit detects an
error in decoding a message, the error is implied by the lack of a
response.
The office attempts a limited number of retries on messages
when no response is seen or an error is detected in the response.
4.2
PHILOSOPHY AND SECURITY
The protocol uses modified binary characters to frame messages that are
designed to lend themselves to hexadecimal interpretation. Characters
in the range of $FO through $FE are reserved as unique control
characters.
The character $FF is illegal since it is commonly created
on noisy data channels. Data security is provided in the form of a
CRC-16 checksum.
The generator polynomial is the standard CRC-16
polynomial:
x16 +xis+ x2 + 1
Characters in the range of $00 to $EF are sent as is, in a single byte.
A character in the range of $FO through $FF is sent as a sequence of two
bytes. This sequence consists of the data escape character $FO followed
by the low order nibble (right hex digit) of the original character.
The receiver of any message containing this sequence must always
logically OR the two characters and treat the result as a single
character.
Every message starts with a function specific header character (in the
range of $Fl through $FS or $F7 through $FE) followed by a unit address.
Any data, if applicable to the function, then follows. The data portion
is function specific and may vary in length. Following the data is the
CRC-16 then a $F6 terminator character (End-of-Text or ETX). The CRC-16
is generated from the header, address, and data portion prior to a~y
possible data escape sequences being introduced.
Only the message
6408E, p. 4-1
header and terminator
escape sequence.
characters
are excluded from any possible data
In general, messages are classified according to function with a unique
header
character for each class.
Certain classifications employ
auxiliary header characters appearing after the address.
These denote
specific functions within a classification which. contains multiple
messages. Figure 4-1 summarizes, by classification, the messages sent
by the office to the PRCCI. Figure 4-2 summarizes those sent by the
PRCCI to the office.
MSG
HOR
AUX
HDR
FUNCTION
AO
PRCCI INITIALIZATION
Al
INDICATION DATABASE REQUEST
A4
STATUS INDICATION REGISTER REQUEST
AS
SET STATUS CONTROL REGISTER
A6
MASTER RECALL
F7
A7
RESERVED
A8
A9
COMMON MODE REQUEST
AA
RESERVED
F8
AB
AC
CONTROL REQUEST
AD
INDICATION RECALL
AE
EXECUTE CONTROL
AF
RESERVED
F9
--
RESERVED
FA
ACKNOYLEDGE AND POLL
FC
----
FD
--
LOCAL INDICATION RECALL
FE
--
EXECUTE LOCAL CONTROL
FB
POLL
LOCAL CONTROL REQUEST
Figure 4-1.
Office Generated Messages
6408E, p. 4-2
MSG
HOR
AUX
HOR
FUNCTION
Fl
--
ACKNOYLEDGE
F2
--
LOCAL INDICATION
F3
---
LOCAL CONTROL CHECKBACK
A2
INDICATION
A3
CONTROL CHECKBACK
F4
STATUS INDICATION REGISTER DATA
FS
Figure 4-2.
4.3
PRCCI Generated Messages.
OFFICE GENERATED MESSAGES
This section discusses the function and implementation of messages
exchanged between an office computer system and a DOL-601/A/B PRCCI.
The possible responses are given for messages generated by an office.
These are listed in order from the highest priority to the lowest.
Each message must pass a variety of hardware and protocol level checks
before it may be processed. The lower level hardware checks verify the
line integrity, character framing, and that no data overrun has occured
(loss of data),
A series of protocol checks progressively verify any
CRC-16, the message header, unit address, and any auxiliary header.
Each message is then subject to specific edit checks to verify that the
contents meet the requirements of the application and the installation.
4.3.1
Poll
The poll message is generated to allow the PRCCI to return any new or
changed information from its database. This message has both a secure
and non-secure format, The secure format contains a CRC-16 while the
non-secure does not. The format used is determined by the SENSEC flag
in Status Control Register 1. Valid responses from the PRCCI include:
1.
2.
3.
4.
4.3.2
SIR data
Indication
Local indication
Acknowledge. (ACK)
Acknowledge And Poll
The acknowledge and poll message is generated to acknowledge data from
the PRCCI and to poll for any additional information. All messages from
the PRCCI that contain data must be acknowledged by the office.
Until
acknowledged, the PRCCI assumes the office failed to receive the last
6408E, p. 4-3
response, and will re-transmit it in subsequent conversations.
In
subsequent conversations a higher priority response may take precedence
but no loss of data occurs.
4.3.3
PRCCI Initialization
The PRCCI initialization message is the primary mechanism used by the
office
to
configure
a PRCCI to a specific installation.
The
capabilities of a PRCCI are limited until the unit is initialized by the
office.
This message supplies the unit with parameters to be used in
communication with both the office and field.
These parameters are
described in the following sections. Valid responses from the PRCCI
include:
1.
2,
4.3.3.1
SIR data
Acknowledge (ACK)
Maximum Indication Records Per Message
This parameter determines the maximum number of buffered indication
records that may be returned to the office in a single indication
message. A record represents a single indication message from a field
code unit.
Adjustment of this parameter not only affects operation of
the PRCCI but may also affect the perceived performance of the office,
This parameter must be set between 1 and 8. In general, the slower the
effective rate at which the PRCCI is polled the higher this parameter
should be. A single unit connected directly to the office through a
dedicated channel may have this parameter set relatively low (1 or 2).
Multiple units that share a communication channel to the office should
have this parameter set higher to compensate for the effectively slower
polling rate.
4.3.3.2
Maximum Control Queue Entries
This parameter determines the maximum number of control and recall
requests that may be buffered by the PRCCI at any one time. Normally
the office is capable of generating such requests at a faster rate than
which the PRCCI is able to transmit them to the the field. This
parameter must be set between 1 and 8.
4.3.3.3
Maximum Station Address
This parameter determines the highest station address polled by the
PRCCI. The PRCCI also uses this parameter to verify the station address
in control and recall requests from the office. This parameter must be
set between 1 and 127.
4.3.3.4
Number Of Station Retries Per Set
This parameter determines the number of single retries in a retry set.
Primarily, it dictates the number of times that the PRCCI may retry a
transmission before declaring an error monitor condition for a field
6408E, p. 4-4
code unit.
4.3.3.5
This parameter must be set between 1 and 5
Number Of Station Retry Sets
This parameter determines the number of retry sets that the PRCCI must
exhaust before declaring a failure condition for a field code unit. It
must be set between 1 and S.
4.3.3.6
Transmit Key-On Delay Time.
This parameter allows the office to override the DIP switch selected
key-on delay used in field communication. A non-zero value for this
parameter selects the key-on time in bit times. Valid values are 1 thru
64.
A zero value for this parameter specifies use of the actual DIP
switch selected option.
4.3.3.7
Transmit Key-Off Delay Time.
This parameter allows the office to override the DIP switch selected
key-off delay used in field communication. A non-zero value for this
parameter selects the key-off time in bit times.
Valid values are 1
thru 64.
A zero value for this parameter specifies use of the actual
DIP switch selected option.
4.3.3.8
No Response Timeout.
This parameter allows the office to override the DIP switch selected
timeout for no response. A non-zero value for this parameter selects
the no response timeout in milliseconds I a. This allows the selection
of no response timeouts between 8 and 2032 milliseconds. A zero value
for this parameter specifies use of the actual DIP switch selected
option.
4.3.3.9
Receive Data Accept Delay Time.
This parameter allows the office to override the DIP switch selected
option for the receive data accept delay time. A non-zero value for
this parameter selects the receive data accept delay in bit times.
Valid values are 1 thru 15. A zero value for this parameter specifies
use of the actual DIP switch selected option.
4.3.3.10
Common Mode Interval
The common mode interval parameter specifies the time in seconds between
common mode transmissions.
Common mode is used in some DDL-601/A/B
installations to verify communication system integrity. If a field code
unit fails to receive the common mode message for a predetermined period
of time the field unit falls back to a communication failure mode.
Valid values for this parameter are between 5 and 255 seconds.
6408E, p. 4-5
4.3.3.11
Checkback Vord List {DDL-601B Only)
The checkback word list contains a one byte entry for all possible
stations on the code line line from one up to the maximum station
address. Each entry contains a mask that specifies which words, if any,
are configured for checkback.
Up to six checkback words may be
specified in a mask where bit O {the least significant bit) represents
word address 1 and bit S represents word address 6. A zero entry for a
station indicates that the station is not configured with any checkback
words.
4.3.3.12
Priority Vord List (DDL-6018 Only)
The priority word list contains a two byte entry for all possible
stations on the code line from one up to the maximum station address.
Each entry contains a mask that specifies which words, if any, are
configured for priority. Up to nine priority words may be specified in
a mask where bit O (the least significant bit) represents word address 1
A zero entry for a station
and bit 8 represents word address 9.
indicates that the station is not configured with any priority words.
4.3.4
Set Status Control Register
The set status control register (SCR) message is a secondary mechanism
used by the office to initialize, dynamically alter, or otherwise
maintain certain operating
characteristics.
The
characteristics
determined by the status control registers may be altered without
re-initialization of the PRCCI. Section 4.5 describes the registers and
the characteristics that they control. Valid responses from the PRCCI
include:
1.
2.
3.
4.
4.3.S
SIR data
Indication
Local indication
Acknowledge (ACK)
Status Indication Register Request
The status indication register (SIR) request message is generated to
examine the current contents of all such registers defined by the
DDL-601/A/B PRCCI application. Valid responses from the PRCCI include:
1.
2.
4.3.6
SIR data
Acknowledge (ACK)
Indication Database Request
The indication database request message is generated by the office to
update
its own indication database.
This function provides the
capability for the office to update itself without having to place
recall and unchanged indication traffic on the field code line.
Indication data generated in response to this request appears to the
office as normal indication messages. Valid responses from the PRCCI
include:
6408E, p. 4-6
1.
2.
3.
4.
4.3.7
SIR data
Indication
Local indication
Acknowledge (ACK)
Local Control Request
The local control request message is generated to request that the PRCCI
deliver local controls. If control checkback is enabled the only legal
response is a local control checkback message.
Yhen checkback is
disabled, valid responses from the PRCCI include:
1.
2.
3.
4.
4,3.8
SIR data
Indication
Local indication
Acknowledge (ACK)
Execute Local Control
The execute local control message is generated to execute a local
control request that had been previously verified with a local control
checkback message from the PRCCI. This message must immediately follow
the local control checkback or the office must repeat the sequence
beginning with a retry of the local control request.
This message is
illegal if control checkback is disabled. Valid responses from the
PRCCI include:
1.
2.
4.3.9
SIR data
Acknowledge (ACK)
Local Indication Recall
The local indication recall message is generated to request the current
local indications from the PRCCI.
The PRCCI is only permitted to
respond with:
1.
2.
4.3.10
SIR data
Local indication
Control Request
The control request message is generated to request that the PRCCI
transmit a control message to the field, This message specifies the
field code unit address, the number of control words in the request, as
well as each control word address and current control data. If control
checkback is enabled the only legal response is a control checkback
Yhen checkback is disabled, valid responses from the PRCCI
message.
include:
1.
2.
SIR data
Indication
6408E, p. 4-7
3.
4.
4.3.11
Local indication
Acknowledge (ACK)
Execute Control
The execute control message is generated to execute a control request
that had been previously verified with a checkback message from the
PRCCI. This message must immediately follow the control checkback or
the office must repeat the sequence beginning with a retry of the
control request. This message is illegal if control checkback is
disabled. Valid responses from the PRCCI include:
1.
2.
4.3.12
SIR data
Acknowledge (ACK)
Indication Recall
The indication recall message is generated to request that the PRCCI
recall current indications from the specified field code unit. The
indications received by the PRCCI in response to the recall, or master
mode, are always returned to the office regardless of whether or not
there is a change in state. Valid responses from the PRCCI include:
1,
2.
3.
4.
4.3.13
SIR data
Indication
Local indication
Acknowledge (ACK)
Master Recall
The master recall message is generated to request that the PRCCI return
current indications from all stations on the code line. This function
is actually implemented by the PRCCI using a series of individual recall
or master mode transmissions. Subsequent indications received from each
station are returned to the office regardless of whether or not there is
a change in state.
Such indications appear to the office as normal
indication messages. Valid responses from the PRCCI include:
1.
2.
3.
4.
4.3.14
SIR data
Indication
Local indication
Acknowledge (ACK)
Common Mode Request
The common mode request message is generated to request that the PRCCI
transmit the common mode control message. This function is used in some
installations to monitor the integrity of the communication medium.
Valid responses from the PRCCI include:
1.
SIR data
6408E, p. 4-8
2.
3.
4.
4.4
4.4.1
Indication
Local indication
Acknowledge (ACK)
PRCCI GENERATED MESSAGES
Local Control Checkback
The local control checkback message is generated as part of the
· verification procedure for local control delivery. It is only legal in
response to a local control request from the office when checkback is
enabled.
A proper checkback response returns the same control byte
number and control byte data as requested.
4.4.2
Control Checkback
The control checkback message is generated as part of the verification
procedure for control transmission to the field. It is only legal in
response to a control request from the office when checkback is enabled.
A proper checkback response returns the same field code unit address,
and control information as requested.
4.4.3
Status Indication Register Data
The SIR data message is generated to return SIR information to the
office.
SIR information is returned only when changes occur or upon
request from the office.
4.4.4
Indication
The indication message is generated to return field indication data to
the office.
Normally, indications are returned only when a change in
state is detected or when the office has requested a recall.
This
message may contain multiple indication records where each record is
associated with a particular field code unit. The PRCCI initialization
message specifies the maximum number of records that may appear in a
message. An indication record specifies the field code unit address,
the number of indication words in the record, as well as each indication
word address and current indication data.
The indication message is also used to report field code unit status
information to the office.
Such information includes monitor and
failure conditions that may be declared or automatically cleared up by
the PRCCI,
4.4.5
Local Indication
The local indication messsage is generated to return local indication
data to the office. Local indications are returned only when a change
in state is detected or in response to a recall from the office.
6408E, p. 4-9
4.4.6
Acknowledge
The acknowledge message is generated as a response when the PRCCI has no
data to return to the office. This message has only a non-secure format
that does not contain a CRC-16.
4.5
STATUS CONTROL AND INDICATION REGISTERS
Certain operating characteristics
internal status registers. These
computer system and allow the
characteristics as well as sense
detected by the PRCCI.
are controlled and indicated through
registers are accessible by the office
office to dynamically maintain the
and/or clear possible error conditions
There are sixteen registers available; addressed O through 15.
Yhile
the
function
of
each register is consistent across all PRCCI
applications, not all registers are used by all of the applications.
This section describes each register implemented by the DDL-601/A/B
PRCCI application. Those not described are accessible but perform no
function.
4.5.1
Status Control Register O
Figure 4-3.
SCRO Flags
SNOIDB - Clear the no indication database flag.
SCTBSY - Clear control queue busy flag.
control request queue.
Forces the PRCCI to
SINQOV - Clear indication queue overflow flag.
not cleared of data.
clear
The indication queue
its
is
SDETER - Clear PRCCI detected error flag.
4.5.2
Status Indication Register O
SNOIDB SHAINT SCTERR SCTBSY SINQOV SDETER SLNERR SRCINI
Figure 4-4.
SIR O Flags
SNOIDB - No indication database. This flag is cleared by the office to
signify that indications from all stations on the code line
have been received. The PRCCI normally sets this flag upon
reset or initialization.
6408E, p. 4-10
SMAINT - Maintenance session open. This flag is set to indicate that
maintenance session is opened.
a
SCTERR - Control request error. This flag is set to indicate that an
error was detected while performing edit checks on a previous
control request from the office.
It remains set until the
office generates an acceptable control request.
SCTBSY - Control queue busy. This flag is set to indicate that the
maximum number of control requests have been queued by the
office. The flag is cleared automatically once the control
queue is sufficiently emptied to accept additional requests.
SINQOV - Indication queue overflow. This flag is set to signify that
the field indication queue has overflowed. Previous indication
data is lost since the queue is automatically cleared and the
most recent indication is inserted. The flag is cleared on
reset, initialization, or by request of the office.
SDETER - PRCCI detected error.
Reserved flag.
SLNERR - Code line error. This flag is set to indicate that an error
was detected on the code line. This flag is automatically
cleared once communication is re-established on the code line.
SRCINI - PRCCI initialization request. This flag is set to request
initialization from the office. It may only ever be cleared by
the office with a valid initialization message.
4.5.3
Status Control/Indication Register 1
SPLDED SFLTRI SENCOD SENSEC SENCBC SALNRT SATPAR SRBADI
Figure 4-5.
SCR/SIR 1 Flags
SPLDED - Poll dead stations. This flag is set to instruct the PRCCI to
poll dead field code units. If cleared, the PRCCI polls only
live stations during the polling cycle and sequentially recalls
a single dead station between cycles. It is cleared on reset
and initialization.
SFLTRI - Enable indication change filter. This flag is set to filter
only changed indications to the office.
If cleared, all
indications, as received, are passed to the office. It is set
on reset and initialization.
SENCOD - Enable code line communication.
This flag is
primarily
intended for use on polling code systems. Only when this flag
is set is the PRCCI permitted to communicate with the fields.
It is cleared on reset, initialization, and during certain
maintenance functions.
SENSEC - Enable secure poll.
This flag is set to
6408E, p. 4-11
force
the
PRCCI
to
accept only secure poll messages from the office. If this flag
is cleared, the PRCCI will accept either secure or non-secure
polls. It is cleared on reset and initialization.
SENCBC - Enable control checkback. This flag is set to enable control
checkback mode for all control and local control requests from
the office. It is cleared on reset and initialization.
SALNRT - Enable alternate line rate.
Reserved flag.
SATPAR - Enable alternate timing parameters.
SRBADI - Return bad indications.
4.5.4
Reserved flag.
Reserved flag.
Status Control/Indication Register 2
Figure 4-6.
SCR/SIR 2 Flags
SAUTCM - Enable automatic common mode. This flag is set to instruct the
PRCCI to automatically output a common mode transmission on a
regular interval. It is cleared on reset and initialization.
6408E, p. 4-12
SECTION V
FIELD INFORMATION EXCHANGE
5.1
OVERVIEV
The DDL-601/A/B PRCCI communicates with one or more field code units
over a half duplex code line.
DDL-601/A/B requires a carrier type
The rest
communication circuit with 2 frequencies in each direction.
state of the circuit is mark with a transition to space signifying the
beginning of a transmission. Office carrier may be continuous or keyed.
Field carrier must be keyed. DDL-601/A/B operates at data rates between
100 and 2400 bits per second. The PRCCI is the master on this circuit
and initiates all conversations. The field code units are sequentially
polled by address and only the addressed unit is permitted to respond.
5.2
CODE FORMAT
All DDL-601/A/B messages are composed of strings of 31 bit frames
preceded by a message synchronization pattern. Office to field messages
consist of a 31 bit address word preceded by a 7 bit message
synchronization pattern.
The address word is optionally followed by a
string of control frames each containing a 31 bit control word.
Field
to office messages consist only of 31 bit indication or checkback
(DDL-601B only) frames preceded by a 3 bit synchronization pattern. The
maximum number of frames in an office to field message is 16 (one
address frame and 15 control frames). A field to office message may
contain 1 to 15 indication frames. All bit groups in all frames are
transmitted least significant bit first and most significant bit last.
5.2.1
Office To Field Transmissions
There are 6 types of office to field messages supported by the
DDL-601/A/B PRCCI.
These include polling, control, master, priority,
common, and execute messages. All messages except the control message
consist of a single address frame. The office to field message type is
identified by the mode bits in the address word.
The first 31 bit frame in all office to field messages is the address
word shown in figure 5-1. It consists of a 7 bit field station address,
a 3 bit mode ID, a 4 bit word address, a word following bit, 6 fixed
bits, and 10 BCH check bits. The acceptable values for field station
address, mode ID, word address, and the word following bit are shown in
figure 5-5. The values for the fixed bits are shown in figure 5-1.
6408E, p. 5-1
All other 31 bit frames in an office to field message are control words.
They are present only when the control mode IO is set in the address
word and the word following bit is set to 1. Vhen present, the control
words are transmitted immediately following the address word. The
control word consists of 16 control data bits, a 4 bit control word
address, a word following bit, and 10 BCH check bits. The control word
format is shown in figure 5-2. An office to field message may contain
up to 15 control words for DDL-601 and DDL-601A. An office to field
message for DDL-601B may contain up to 6 control words.
The word
following bit is set to 1 in every control word except the last. The
control words included in a control message need not have sequential
word addresses. Normally only control words containing changed data are
transmitted.
5.2.2
Field To Office Messages
The only valid field to office message is the indication message.
An
indication message may contain ind-ication frames, control checkback
frames or both and consists of 1 to 15 frames.
Indication frames
consist of a 31 bit indication word. The indication word consists of 16
·indication data bits, 4 indication word address bits, a word following
bit, and 10 BCH check bits. The indication word format is shown in
figure 5-3. Control checkback frames consist of a 31 bit control
checkback word (ODL-601B only).
The format of the control checkback
word is identical to the indication word except that the indication data
bits are replaced by control checkback data bits. Vhen checkback
control delivery is implemented the field code unit supports only 6
control words and 9 indication words. This allows word addresses 1 thru
9 to be indication word addresses while word addresses 10 thru 15 are
control checkback word addresses. Vord address 10 is the checkback data
for control word 1 while word address 15 represents the checkback data
for control word 6. The word following bit is set to 1 in all but the
last frame of the message. The indication and control checkback words
included in an indication m.essage need not have sequential word
addresses. Normally only indication words containing changed data are
transmitted.
Note that indication and control checkback responses do
not include the address of the originating field station. The protocol
assumes that any received response came from the field station currently
being addressed.
5.2.3
Error Detection And Security
Message security is provided by 10 BCH check bits included in every 31
bit frame and fixed bits included in the address frame. The BCH bits
are checked during the processing of each frame. If the BCH check for
any frame fails the entire message is discarded. Information on BCH
calculation is included in service manuals SM-5986, SM-6142, and
SM-6200.
5.3
PRCCI GENERATED MESSAGES
This section discusses the function and implementation of messages
exchanged between a DOL-601/A/B PRCCI and a DDL-601/A/B field code unit.
Vhen received by a DDL-601/A/B field unit each message must pass a
variety of hardware and protocol level checks before it may be
6408E, p. 5-2
processed.
The
lower
level
hardware
checks
verify
message
synchronization and framing. The protocol level checks verify message
structure and the BCH check bits.
5.3.1
Poll
The poll message is generated to allow a DDL-601/A/B field unit to
return any new or changed indication information. This message consists
of a single 31 bit frame. This frame consists of the address word
containing the polling mode ID. An indication message is the only valid
response to this message but a response is not required if no indication
changes are waiting to be sent.
5.3.2
Master
The master (recall) message is generated to request all current
indications from the addressed DDL-601/A/B field code unit. This
message consists of a single 31 bit frame. This frame consists of the
address word containing the master mode ID. A full indication message
is the only valid response to the master message and a response is
required.
5.3.3
Control
The control message is generated to request that a DDL-601/A/B field
code unit deliver the specified control data. The PRCCI is only capable
of transmitting a control message upon request from the office and does
not attempt to filter changes in control data. It transmits all control
data requested by the office, regardless of whether or not there is
actually a change of state. The control message consists of one 31 bit
frame containing the address word and one 31 bit frame for each control
word transmitted.
Up to 15 control words may be transmitted in the same message to a
DDL-601 or DDL-601A field code unit.
The only valid response to a
control message for a DDL-601/A field code unit is any indication,
The
indication message does not have to include all of the field code units'
indication words but a response is required. If no indication changes
are waiting to be sent to the office the response consists of indication
word 1,
Up to 6 control words may be transmitted to a DDL-6018 field code unit.
A response is required. If the controls transmitted to the field code
unit are not to be delivered by checkback control delivery boards the
required field response is any indication message as described above for
DDL-601/A, If the control words are bound for checkback delivery boards
the only valid response is a checkback response containing the current
control image for each checkback control delivery board addressed.
If
the control image returned matches the control image transmitted control
delivery is enabled by the execute message.
6408E, p. 5-3
S.3.4
Execute
The execute message is generated to request that a DDL-6018 field code
unit execute the control request that has been previously verified with
a checkback message from the addressed unit.
The execute message
consists of a single 31 bit frame. This frame consists of the address
word containing the execute mode ID.
This message must immediately
follow the control checkback or the PRCCI must repeat the sequence
starting with a retry of the control request. This message is illegal
when addressed to DDL-601 or DDL-601A field code units. This message is
ignored by DDL-601B field code units which contain no checkback control
delivery boards.
The only valid response to an execute message for a
DDL-601B field code unit is any indication message.
The indication
message does not have to include all of the field code units' indication
words but a response is required. If no indication changes are waiting
to be sent to the office the response is composed of indication word 1.
If the DDL-601B field code unit contains no indication input boards the
response contains an indication word address of O.
5. 3.5
Priority
The priority message is generated to reset certain indication bits which
are designated as priority indication bits. It consists of a single 31
bit frame. This frame consists of the address word containing the
priority mode ID.
Priority indication bits are indication bits which
are asserted for a short period of time and could be missed without
special
handling.
The function of the priority message is to
acknowledge receipt of the priority indication bits by the PRCCI so that
the field coding unit may initiate the priority indication reset
sequence. When the priority message is received by the field code unit
all priority indication bits previously transmitted to the PRCCI are
reset. Any indication response is permitted.
A response is not
required.
5.3.6
Common
The common control message is generated to send a single bit of
information to all field code units on the communication circuit at the
same time. It consists of a single 31 bit frame. This frame consists
of the address word containing the common mode ID and a field code unit
address of O. The field code unit is not permitted to respond to the
common mode message.
5.4
FIELD GENERATED MESSAGES
This section discusses the function and implementation of messages
exchanged between a DDL-601/A/B field code unit and a DDL-601/A/B PRCCI.
When received by the PRCCI each message must pass a variety of hardware
and protocol level checks before it may be processed. The lower level
hardware checks verify message synchronization and framing.
The
protocol level checks verify message structure and the BCH check bits.
6408E, p. 5-4
5.4.1
Control Checkback
The control checkback message is generated by DDL-601B field code units
as part of the verification procedure for control delivery. It is the
only legal response when controls are delivered to checkback control
delivery boards in a DDL-601B field code unit. The checkback message is
composed of a variable number of 31 bit frames.
The response may
include indication frames as well as control checkback frames if
indication changes have recently been detected. Indication frames have
word addresses between 1 and 9. Control checkback frames have word
addresses between 10 and 15 with 10 corresponding to control word 1 and
15 corresponding to control word 6.
5.4.2
Indication
The indication message is generated to return indication data to the
PRCCI.
The indication message is composed of a variable number of 31
bit frames each containing an indication word.
An indication message
may contain up to 15 indication words for DDL-601 and DDL-601A and up to
9 indication words for DDL-601B. Indications are normally returned only
when a change of state is detected or in response to a master
transmission from the PRCCI.
5.5
POLLING CYCLE DESCRIPTION
The PRCCI polls a pre-determined number of stations in a round robin
fashion.
To minimize delays in the polling cycle, due to errors or no
response timeouts, failed stations are not normally polled. At the end
of each polling cycle a recall, or master mode, is transmitted for a
failed station in an attempt to eventually establish communication with
all possible stations. Office requests for controls take priority and
may interrupt the normal polling cycle.
Yhen all such requests are
satisfied
the
polling resumes from the point at which it was
interrupted.
Any time that an error is detected for a live station the PRCCI re-tries
the transmission a limited number of times before it skips to the next
station in the polling cycle. Subsequent retries are performed the next
time .that station is to be polled.
A station error, or monitor
condition, is reported to the office only after a complete retry set has
been performed. A station failure is reported to the office only after
a pre-determined number of retry sets have been exhausted.
6408E, p. 5-5
BIT
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17
FUNCTION B9 B8 B7 B6 BS B4 B3 B2 Bl BO VF V3 V2 Vl VO
BIT
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
FUNCTION 0 1 M2 Ml 0 MO A6 1 AS A4 0 A3 A2 1 Al AO
S6 SS S4 S3 S2 Sl so
BIT
FUNCTION 1 0 1 0 0 0 0
Figure 5-1.
31
B9
BIT
FUNCTION
30 29 28
BS B7 B6
DDL-601/A/B Address Vord
27 26 25 24 23 22 21 20 19 18 17
BS 84 B3 B2 Bl BO VF \13 \12 Vl VO
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
BIT
FUNCTION C16 ClS Cl4 C13 C12 Cll ClO C9 CB C7 C6 cs C4 C3 C2 Cl
Figure 5-2.
BIT
FUNCTION
BIT
FUNCTION
31
B9
30 29
B8 B7
52 Sl
0 1
26
84
25 24 23 22 21 20 19 18 17
B3 B2 Bl BO VF \13 V2 Vl VO
so
0
Figure 5-3.
DDL-601/A/B Indication Vord
DESCRIPTION
BIT
A6
89
C16
I16
M2
so - 56
VO - V3
VF
0
1
27
BS
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
I16 IlS I14 !13 I12 Ill IlO I9 I8 I7 I6 IS I4 I3 I2 I1
BIT
FUNCTION
AO
BO
Cl
I1
MO
28
B6
DDL-601/A/B Control Vord
-
ADDRESS BITS
BCH CHECK BITS
CONTROL DATA BITS
INDICATION DATA BITS
MODE IDENTIFICATION BITS
MESSAGE SYNCHRONIZATION BITS
VORD ADDRESS BITS
VORD FOLLOWING BIT
(1 IF MORE DATA FOLLOWS - 0 OTHERWISE)
FIXED OBIT
FIXED 1 BIT
Figure 5-4.
DDL-601/A/B Bit Identification
6408E, p. 5-6
STATION ADDRESS
BITS
10 8 7 5 4 2 1
MODE
BITS
14 13 11
VORD ADDR.
BITS
20 19 18 17
VF
BIT
21
POLLING
0 0 0 0 OO1
TO
1 1 1 1 1 1 1
0 0 1
0 0 0 0
0
CONTROL
0 0 0 0 0 0 1
TO
1 1 1 1 1 1 1
1 0 0
0 0 0 0
1
MASTER
0 0 0 0 0 0 1
TO
1 1 1 1 1 1 1
1 1 1
0 0 0 0
0
PRIORITY
0 0 0 0 0 0 1
TO
1 1 1 1 1 1 1
o.
0 0
0 0 0 0
0
COMMON
0 0 0 OOOO
0 1 1
0 0 0 1
0
EXECUTE
0 0 0 0 0 0 1
TO
1 1 1 1 1 1 1
1 0
0 0 0 0
0
MODE
Figure 5-5.
1
DDL-601/A/B Address Vord Structure by Mode
6408E, p. 5-7
SECTION VI
MAINTENANCE SESSION
6.1
OVERVIEV
The maintenance session provides the capability, through an ANSI
standard terminal, to monitor message traffic and performance of both
the office communication channel and field code line.
Interactive
diagnostic tools allow the user to locally generate a limited number of
code line messages, review various reports, as well as examine or
temporarily
alter
certain operating characteristics.
Access is
restricted by two protection mechanisms. The address of the unit and a
password must be properly specified in order to open a session. All
units employ the same password which may not be altered.
A maintenance command consists of one or more words possibly followed,
depending upon the command, by one or more numeric values. Only one
command may be entered on a line and each line must be terminated with a
carriage return.
Numeric values may typically be entered in decimal,
hexadecimal, binary, or the native language of the coding equipment. In
general, the format is selectable by the user but restrictions do apply
to certain commands. These restrictions are noted in the respective
command descriptions.
Prior to entering the carriage return at the end of a command line,
characters on the line may be corrected through the use of the delete
(RUBOUT) or backspace key. The delete causes the character immediately
to the left of cursor to be ignored by the PRCCI. The resulting display
is determined by the SET CRT command~ A partially entered command line
may timeout and be ignored by the PRCCI after approximately twenty (20)
seconds of inactivity.
The maintenance session recognizes control-Q and control-$ as XON/XOFF
flow control characters. This provides a "hold screen" feature that is
useful for reviewing reports that scroll off a CRT screen. Control-C is
recognized as an interrupt character.
It may be used to abort any
command or report and return the user to the command line prompt.
For
compatibility with the office protocol, these features are only enabled
while a session is opened.·
6.2
NUMERIC CODE LINE INFORMATION
Decimal, hexadecimal, binary, and various native formats are available
for the entry and display of numeric fields that represent code line
address, control, and indication information. The native formats are
6408E, p. 6-1
essentially binary except that specific alphabetic characters replace
the usual "1" and "0". The formats are selected with the SET FORMAT
command.
Fields for numeric code line information are divided into
groups of eight bits or 1 byte and may be represented by a value from O
Certain commands may further restrict the value of
to 255 (decimal).
some fields, such as a station address.
Control and indication
information is displayed such that it corresponds, left to right, with a
typical code and function assignment sheet.
The decimal format allows code line information to be represented with
the digits O through 9.
When entering fields, leading zeroes are
typically permitted but ignored.
The hexadecimal format allows code line information to be represented
with the digits O through 9 and A through F, In the specification and
display of station addresses, leading zeroes are always significant.
Some application independent commands use four hexdecimal digits to
represent a station address, Within these fields, address information
is left justified and interpreted left to right. Fields entered with
fewer than four digits are padded on the right with zeroes. For correct
operation of these commands under this PRCCI application, only two
digits should ever be used to specify a station address.
Only the
leftmost two digits in these fields should be affected. The rightmost
two digits should always remain zeroes.
The binary and native formats allow code line information to be
represented with the digits 1 and O or two other appropriate characters.
In the specification and display of station addresses, leading zeroes
(or equivalent) are always significant. Some application independent
commands use sixteen digits to represent a station address.
Yithin
these fields, address information is left justified and interpreted left
to right. Fields entered with fewer than sixteen digits are padded on
the right with zeroes (or equivalent). For correct operation of these
commands under this PRCCI application, only eight digits should ever be
used to specify a station address. Only the leftmost eight digits in
these fields should be affected.
The rightmost eight digits should
always remain zeroes (or equivalent).
6.3
OPENING A MAINTENANCE SESSION
A proper login and password sequence is necessary to open a maintenance
session on any PRCCI. The LOGIN command must be spelled correctly and
specify, in decimal, the address of the PRCCI. For compatibility with
the office protocol, a PRCCI does not generate any responses or echo
characters until a LOGIN command has been accepted. For this reason, no
prompt is ever generated for a LOGIN command. Upon receipt of a proper
LOGIN command the PRCCI prompts the user for a password.
The password
is not echoed and if it is entered incorrectly, the login sequence is
aborted without any warning or error messages.
Once a maintenance session is opened, a brief welcome message and a
command line prompt are displayed. Any legal maintenance command may
now be entered. A HELP command is available that displays a summary of
maintenance commands and their options. The HELP command accepts, as an
option, a command name and provides detailed information on the
command's syntax or format.
6408E, p. 6-2
A maintenance session is normally closed with a LOGOUT command and a
brief termination message is displayed. A valid office protocol message
may override an open session.
This forces the
session
closed
immediately and no termination message is displayed.
In the example below, a maintenance session is opened on a PRCCI with an
assigned address of two. Underscored text is entered by the user.
LOGIN 2
Password:
Maintenance session opened on PRCCI 2.
PRCCI> HELP
CLEAR option [argl}
ERRORS
HISTORY
PRCCI> HELP CLEAR
CLEAR option [argl)
ERRORS
HISTORY [type]
FIELD
OFFICE
TIME
PRCCI> LOGOUT
Maintenance session closed on PRCCI 2.
6.4
COMMAND DESCRIPTIONS
This section describes the syntax and use of the maintenance session
commands. Any command element that appears in upper case is referred to
as a key-word and is considered part of the command syntax. A key-word
may be entered in either upper or lower case, using enough characters to
make it unique from any other key-word allowed in the particular command
line.
Elements that appear in lower case indicate either that one of
several key-words or a numeric argument is to be used in the command
line,
Key-words to be substituted in this manner are listed below the
element in the syntax description. Elements enclosed in square brackets
([]) may be considered optional and need not be entered for the command
to be accepted. These may include key-words or numeric arguments.
All
elements entered in a command line must be separated by at least one
space.
6408E, p. 6-3
6.4.1
CLEAR
Syntax:
CLEAR option {argl]
ERRORS
HISTORY [type]
FIELD
OFFICE
TIME
The CLEAR command purges specific report and historical information that
is maintained by the PRCCI.
6.4.1.1
CLEAR ERRORS
Syntax:
CLEAR ERRORS
The CLEAR command entered with the ERRORS option zeroes
station error counters and the line error counter.
6.4.1.2
the
indication
CLEAR HISTORY
Syntax:
CLEAR HISTORY [type]
FIELD
OFFICE
TIME
The CLEAR command entered with HISTORY option causes
information to be purged from the specified history queue.
type is specified, all history queues are purged.
6.4.2
historical
If no queue
DISCONNECT
Syntax:
DISCONNECT
The DISCONNECT command typically performs a code line disconnect
function.
The DDL-601/A/B code systems do not provide this capability
and therefore this command has no function in this PRCCI application.
6.4.3
HELP
Syntax:
HELP [command]
6408E, p. 6-4
The HELP command provides a summary of the syntax for all maintenance
commands and their associated options.
This command accepts, as an
option, a command name and provides detailed help on that command's
syntax.
If the command name is abbreviated, help is provided on all
commands that match.
6.4.4
HISTORY
Syntax:
HISTORY option
FIELD
OFFICE
TIME
The HISTORY command generates a historical report on various types of
information exchanged through and obtained by the PRCCI. All historical
information is stored in circular queues.
In this type of storage
structure, the oldest information stored is discarded as new information
is inserted.
These queues are continuously updated and function
independently of any monitor or trace functions.
6.4.4.1
HISTORY FIELD
Syntax:
HISTORY FIELD
The HISTORY command entered with the FIELD option generates a historical
report of the most recent field requests and indications exchanged
between the PRCCI and the field code units.
For each transmission
reported, the message type is displayed followed by any applicable
station address and control or indication data. Station addresses and
data are always displayed in the currently selected format.
6.4.4.2
HISTORY OFFICE
Syntax:
HISTORY OFFICE
The HISTORY command entered with the OFFICE option generates
a
historical report of the most recent messages exchanged between the
office computer system and the PRCCI.
Direction and contents are
reported for each historical message. Direction is indicated by the
symbols XMT and RCV. XMT denotes a PRCCI transmission to the office
while RCV denotes reception from the office. The message contents are
always displayed in hexadecimal.
6408E, p. 6-5
6.4.4.3
HISTORY TIME
Syntax:
HISTORY TIME
The HISTORY command entered with the TIME option performs no function in
this PRCCI application.
6.4.5
LOGIN
Syntax:
LOGIN prcci_address
The LOGIN command is used to gain the attention of a specific PRCCI to
open a maintenance session. The PRCCI address must be specified as a
No· prompt is generated for this
decimal value between 1 and 255.
command.
Upon receipt of a proper LOGIN command, the PRCCI prompts the
user for a password. The password is not echoed and if it is entered
incorrectly, the login sequence is aborted without any warning or error
messages.
If a LOGIN command is entered during an open maintenance session, the
open session is automatically closed.
This is to prevent multiple
maintenance sessions on a channel.
6.4.6
LOGOUT
Syntax:
LOGOUT
The LOGOUT command closes the current maintenance session.
6.4.7
MONITOR
Syntax:
MONITOR option
[NO]AUTOMATIC
FIELD
OFFICE
The MONITOR command allows either office or field message traffic to be
monitored on the maintenance terminal. Yhile this function is active
the terminal operates in a captive mode and maintenance commands are
inhibited.
Only control characters entered from the terminal keyboard
are processed and echoed.
Printable characters entered from the
keyboard result in a warning bell. This feature allows carriage return
(RETURN, ENTER, or control-M) and form-feed (control-L) characters to be
entered to manipulate a printer carriage from the terminal keyboard.
The monitor function is terminated with the control-C interrupt,
6408E, p. 6-6
6.4.7.1
MONITOR AUTOMATIC
Syntax:
MONITOR AUTOMATIC
MONITOR NOAUTOMATIC
The MONITOR command entered with the AUTOMATIC or NOAUTOMATIC option
selects whether or not the PRCCI may automatically activate the field
monitor function when a RECALL command is entered by the user.
The selection of AUTOMATIC allows the PRCCI to automatically activate
the field monitor function upon successful completion of a RECALL
command. This feature requires that an indication or time message trace
must be previously selected with the SET TRACE command. The monitor
function operates in the normal fashion and may be terminated with the
control-C interrupt.
The selection of NOAUTOMATIC inhibits the PRCCI from automatically
activating the field monitor, regardless of any message traces selected.
6.4.7.2
MONITOR FIELD
Syntax:
MONITOR FIELD
The MONITOR command entered with the FIELD option specifies that field
message traffic is to be monitored on the maintenance terminal. The
types of messages to be monitored and any station address trace filter
must be previously specified with the SET TRACE command, For each
transmission reported, the message type is displayed followed by any
applicable station address and control or indication data. Station
addresses and data are always displayed in the currently selected
format.
6.4.7.3
MONITOR OFFICE
Syntax:
MONITOR OFFICE
The MONITOR command entered with the OFFICE option specifies that office
message traffic is to be monitored on the maintenance terminal. Only
messages addressed to the PRCCI are monitored. Direction and contents
are reported for each monitored message. Direction is indicated by the
symbols XHT and RCV. XMT denotes a PRCCI transmission to the office
while RCV denotes reception from the office. The message contents are
always displayed in hexadecimal.
6408E, p. 6-7
6.4.8
RECALL
Syntax:
RECALL option
ALL
control address
The RECALL command allows the user to manually request
recalled from either all stations or a specific station.
6.4.9
indications
RESET
Syntax:
RESET
The RESET command typically causes a master reset function to be applied
to the code line.
The DDL-601/A/B code systems do not support this
capability and therefore this command performs no function in this PRCCI
application.
6.4.10
SET
syntax:
SET option [argl] (arg2]
(NO]CRT
FORMAT format code
BINARYDECIMAL
HEXADECIMAL
LS
HL
LH
MS
SM
LINE state
CYCLE
NORMAL
[NO]REST
SCR scr number mask
SIR sir-number mask
NOTRACE-[argl)
CONTROL
INDICATION
TIME
TRACE argl [arg2]
CONTROL {control address]
INDICATION [indication address}
TIME [indication address]
TRIGGER station number-
6408E, p. 6-8
The SET command allows the user to customize the maintenance session
environment as well as review or modify various parameters and operating
characteristics.
6.4.10.1
SET CRT
Syntax:
SET CRT
SET NOCRT
The SET command entered with either the CRT or NOCRT option selects
whether the PRCCI treats the maintenance terminal as an ANSI standard
CRT or a hardcopy terminal. This affects the display of the current
line when a character is deleted.
The selection of CRT mode allows the delete (RUBOUT) or backspace key to
erase a character from the terminal screen by echoing the sequence of
backspace, space, backspace. The NOCRT mode causes the delete sequence
to echo backslash, deleted character(s), backslash.
6.4.10.2
SET FORMAT
Syntax:
SET FORMAT format code
BINARY
DECIMAL
HEXADECIMAL
LS
HL
LH
MS
SM
The SET command entered with the FORMAT option allows the user to
specify the format used for entering and the display of numeric code
line information. The two character key-words used to select the native
formats are designed so that the left character represents a binary "1"
while the right represents a "0".
Mark/space terminology is selected with the key-words MS or SM while
high/low terminology is selected with HL or LH. Long/short terminology
is selected with the key-word LS. For proper representation of control
and indication data in a native format, the selection of either MS or HL
is recommended.
6408E, p. 6-9
6.4.10.3
SET LINE
Syntax:
SET LINE state
CYCLE
NORE ST
NORMAL
REST
The SET command entered with the LINE option allows the user to apply
various carrier frequency shifts to the code line for the purpose of
line maintenance.
The key-word CYCLE specifies that a 50% duty cycle is to be transmitted
for an indefinite period of time. This duty cycle consists of shifts
between MARK and SPACE at the current baud rate.
The key-word REST specifies that a MARK is
indefinite period of time.
to
be
transmitted
for
an
The key-word NOREST specifies that a SPACE is to be transmitted
indefinite period of time.
for
an
The key-word NORMAL specifies that normal operation is to be resumed.
If initialized, the PRCCI delays briefly before it resumes the polling
cycle and transmits any pending requests.
6.4.10.4
SET SCR
Syntax:
SET SCR scr number mask
The SET command entered with the SCR option may be used to alter the
contents of a status control register. Both the SCR number and the mask
to be loaded into the register must be entered in hexadecimal.
6.4.10.5
SET SIR
Syntax:
SET SIR sir number mask
The SET command entered with the SIR option may be used to alter the
contents of a status indication register. Both the SIR number and the
mask to be loaded into the register must be specified in hexadecimal.
6408E, p. 6-10
6.4.10.6
SET TRACE
Syntax:
SET TRACE argl [arg2]
CONTROL [control address]
INDICATION [indication address]
TIME [indication_address]
The SET command entered with the TRACE option turns on the message trace
associated with
the specified message type.
The message trace
determines whether or not a particular message type is monitored by the
field monitor function.
The second argument specifies an optional address filter mask.
The
address filter is used to selectively monitor messages containing
certain station addresses. Up to eight masks may be specified for a
message type using individual commands. If the mask is omitted from the
command line, the filter is disabled and all messages of the given type
are monitored.
The filter mask must be specified in the currently selected format.
This function accepts, in binary or a native format only, an "X" as a
"don't care" address bit. Other formats inhibit the use of any "don't
care" bits and ignore those that may have previously existed.
The tracing of time performs no function in this PRCCI application.
6.4.10.7
SET NOTRACE
Syntax:
SET NOTRACE [argl]
CONTROL
INDICATION
TIME
The SET command entered with the NOTRACE option turns off the message
trace and disables any address filters associated with the specified
message type. The message type is optional and if omitted, all message
types are affected.
6.4.10.8
SET TRIGGER
Syntax:
SET TRIGGER station number
The SET command entered with the TRIGGER option is used to enable or
disable a trigger for received data from a specific station. The
trigger output serves as a diagnostic tool for indication channel
maintenance and is normally activated after the receiver turns on when
the selected station is to answer.
6408E, p. 6-11
The station number refers to the address and must be entered as a
decimal number between O and 255. A station number within the range of
the polling cycle enables the trigger for the specified station.
A
station number outside the range of the polling cycle enables the
trigger only when an error is detected in a response. A station number
of O disables the trigger.
6.4.11
SHOV
Syntax:
SHOV option [argl] [arg2]
ADDRESS
CONTROL [control address]
ERRORS [indication address]
FORMAT
INDICATION [indication address]
LINE
REVISION
SCR [scr number]
SIR [sir-number]
TIME [inaication address]
TRACE [argl]
TRIGGER
The SHOV command generates various reports and
operating parameters and characterstics,
6.4.11.1
displays
a
variety
of
SHOY ADDRESS
Syntax:
SHOV ADDRESS
The SHOV command entered with the ADDRESS option displays the number of
address steps used for control and indication stations. This function
is primarily intended for use in relay code system applications.
In
this application the number of control and indication address steps is
fixed· at eight.
6.4.11.2
SHOY CONTROL
Syntax:
SHOY CONTROL [control_address]
The SHOY command entered with the CONTROL option displays current
control images stored by the PRCCI. If the optional control address is
specified, only the image for that station is displayed. If omitted, a
report containing the current image for all stations is displayed.
6408E, p. 6-12
6.4.11.3
SHOW ERRORS
Syntax:
SHOW ERRORS [indication_address]
The SHOV command entered with the ERRORS option displays the current
number of code line errors detected by the PRCCI. If the optional
indication address is specified, only the error counter associated with
that station is displayed. If omitted, a report containing the error
counters for all stations and a total number of code line errors is
displayed.
6.4.11.4
SHOV FORMAT
Syntax:
SHOV FORMAT
The SHOV command entered with the FORMAT option displays the current
format selected for the entry and display of numeric code line
information.
6.4.11.5
SHOV INDICATION
Syntax:
SHOV INDICATION (indication_address]
The SHOV command entered with the INDICATION option displays current
indication images stored by the PRCCI.
If the optional indication
address is specified, only the image for that station is displayed.
If
omitted, a report containing the current image for all stations is
displayed.
6.4.11.6
SHOV LINE
Syntax:
SHOV LINE
The SHOV command entered with the LINE option displays the current
maintenance state selected for the field communication channel,
6.4.11.7
line
SHOV REVISION
Syntax:
SHOV REVISION
The SHOV command entered with the REVISION option displays the current
revision level of the firmware installed on both CPU A and CPU B, Also
displayed is the code system type being emulated and a checksum of the
EPROM set installed in each cpu board.
6408E, p. 6-13
6.4.11.8
SHOY SCR
Syntax:
SHOY SCR [scr_number]
The SHOV command entered with the SCR option displays the contents of
one or all status control registers. If the optional SCR number is
specified, only the contents of that register are displayed.
If
omitted, a report is displayed containing the contents of all status
control registers defined by this PRCCI application. The SCR number is
always entered and displayed in hexadecimal. The contents of a SCR are
displayed in both hexadecimal and binary.
6.4.11.9
SHOW SIR
Syntax:
SHOW SIR [sir_number]
The SHOV command entered with the SIR option displays the contents of
one or all status indication registers. If the optional SIR number is
specified, only the contents of that register are displayed.
If
omitted, a report is displayed containing the contents of all status
indication registers defined by this PRCCI application. The SIR number
is always entered and displayed in hexadecimal. The contents of a SIR
are displayed in both hexadecimal and binary.
6.4.11.10
SHOW TIME
Syntax:
SHOW TIME [indication_add~ess]
The SHOW command entered with the TIME option displays
current
indication timing stored by the PRCCI.
If the optional indication
address is specified, only the timing for that station is displayed. If
omitted, a report containing the current timing for all stations is
displayed. This command performs no function in this PRCCI application.
6.4.11.11
SHOV TRACE
Syntax:
SHOW TRACE [argl)
CONTROL
INDICATION
TIME
The SHOV command entered with the TRACE option displays the types of
field messages selected for monitoring when the field monitor function
is active. If enabled with the MONITOR AUTOMATIC command, the automatic
field monitor feature is indicated with any associated message types.
Any address filter masks associated with a traced message type are
6408E, p. 6-14
displayed in the current format.
If the optional message type is
specified, only information on that particular message
type
is
displayed.
6.4.11.12
SHOV TRIGGER
Syntax:
SHOV TRIGGER
The SHOV command entered with the TRIGGER option displays the station
number selected for the trigger.
The station number refers to the
station address and is displayed in decimal.
6.4.12
SUPPRESS
Syntax:
SUPPRESS
The SUPPRESS command typically causes a station suppression function to
be performed.
The DDL-601/A/B code systems do not provide this
capability and therefore this command performs no function in this PRCCI
application.
6.5
ERROR MESSAGES
The maintenance session reports error conditions to the user in textual
messages.
An error message is a brief explanation of the condition
which was detected. Messages that point out specific mistakes made by
the user typically begin with the prefix "ERROR-". In general, they
refer to command line errors such as improper syntax or use of numeric
formats.
Other messages are intended to inform the user of conditions
that may prevent the successful completion of a command.
Each error
message is described below along with a brief explanation of the typical
causes.
ERROR - Ambiguous command or option.
A key-word, representing a command name or command
abbreviated too short. The command line could not be
interpreted because one or more key-words could not
identified within the context of the command. Supply
in the abbreviated key-word(s).
option was
successfully
be uniquely
more letters
ERROR - Illegal argument.
A command line argument was not entered correctly and
the
associated command could not be processed. For example, a numeric
field may exceed a particular range or not entered in the currently
selected format.
Verify proper use of formats and that the value
of the field does not exceed a limit that may imposed by the
particular command.
6408E, p. 6-15
ERROR - Request rejected.
A code line request made by the user was rejected.
Code line
requests include the DISCONNECT, RECALL, RESET, and SUPPRESS
commands. A request that is not supported by the application
causes this error.
If the request is supported, verify that any
address specified in the command line, if applicable, is legal for
the code line and that the proper format is being used.
This error may be occassionally generated if the office computer
system has a number of code line requests queued. Normally, this
is a temporary condition that lasts for only a brief period and is
indicated by messages displayed on the front panel of the PRCCI.
Simply enter the request after the queued requests have been
transmitted.
ERROR - Required option or argument is missing.
An key-word or argument required by the command syntax was omitted
from the command line. Check the syntax of the particular command
by using the HELP command or refer to this manual.
ERROR - Unrecognized command or option.
Characters entered on the command line could not be identified as
any known command or option to a particular command. Check the
syntax of the particular command by using the HELP command or refer
to this manual.
No free address slots for trace.
The maximum number of address filter masks have already been
entered for a particular message type. All previous filter masks
associated with the message type must first be removed with the SET
NOTRACE command.
The new mask may then be entered with the SET
TRACE command.
No help for that command.
The HELP command could not identify the command name entered as an
option.
Enter the HELP command by itself to check the spelling of
the command name or refer to this manual.
No trace selected.
An attempt was made to activate the field monitor function but no
field message types have been selected with the SET TRACE command.
Use the SET TRACE command to select the message types to be
monitored.
Output buffer overflow.
Data lost.
The amount of information sent to the maintenance terminal exceeded
the capacity of the internal buffer. The oldest information in the
buffer was purged and any pending XOFF (hold screen) canceled.
This typically occurs if the hold screen feature is used to freeze
the display for a prolonged period of time.
6408E, p. 6-16
SECTION VII
SUPPLEMENTAL INFORMATION
7.1
CONVENTIONS
This section contains reference information on message formats for those
messages exchanged between a DDL-601/A/B PRCCI and an office. Certain
messages may contain multiple blocks of similar data. These blocks may
be repeated a limited number of times within the message. Such blocks
are denoted by square brackets in the description column.
Yhere
repeatable blocks may occur within blocks, this is denoted with multiple
square brackets.
The range of each field in a message is given in hexadecimal. A single
hexadecimal number (two digits) indicates that only that specific value
is permitted. Multiple numbers separated by a comma(,) indicate that
only those specific values are permitted. Two numbers separated by a
dash(-) indicate the lower and upper limits for the field.
Any
restrictions within the given limits are noted in the description of the
field.
7.2
7.2.1
OFFICE TO PRCCI MESSAGES
Poll
Secure format:
{3yte
1
2
3
4
5
Range
Descri2tion
FB
01-FF
00-FF
00-FF
F6
message header
PRCCI address
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Non-secure format:
Byte
1
2
3
Range
Descri2tion
FB
01-FF
F6
message header
PRCCI address
ETX
6408E, p. 7-1
7.2.2
Acknowledge And Poll
Description
Byte
1
2
3
4
5
7,2.3
FA
01-FF
00-FF
00-FF
F6
message header
PRCCI address
CRC-16 (low byte)
CRC-16 (high byte)
ETX
PRCCI Initialization (DDL-6018 Only)
Byte
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Description
F7
01-FF
AO
17
01-08
01-08
Ol-7F
01-05
01-05
00-40
00-40
00-FF
00-0F
00-FF
00-3F
I
message header
PRCCI address
auxiliary header
code system type
maximum indication records per message
maximum control queue entries
maximum station address
number of station retries per set
number of station retry sets
transmit key-on delay
transmit key-off delay
no response timeout (index)
receive data accept delay (index)
common mode interval (seconds)
checkback word list
00-3F
00,01
00-FF
I
priority word list
00-FF
00-FF
F6
CRC-16 (low byte)
CRC-16 (high byte)
ETX
00,01
00-FF
n-2
n-1
n
6408E, p. 7-2
7.2.4
PRCCI Initialization (DDL-601/A Only)
Byte
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
7.2.S
Description
F7
01-FF
AO
OD
01-08
01-08
01-7F
01-05
01-05
00-40
00-40
00-FF
00-0F
00-FF
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
code system type
maximum indication records per message
maximum control queue entries
maximum station address
number of station retries per set
number of station retry sets
transmit key-on delay
transmit key-off delay
no response timeout
receive data accept delay
common mode interval (seconds)
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Set Status Control Register
Byte
1
2
3
n-2
n-1
n
7.2.6
Range
Range
Description
F7
01-FF
AS
message header
PRCCI address
auxiliary header
00-0F
00-FF
[ SCR number]
[ SCR flags 1
00-FF
00-FF
F6
CRC-16 {low byte)
CRC-16 (high byte)
ETX
Status Indication Register Request
Byte
1
2
3
4
5
6
Description
F7
01-FF
A4
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
CRC-16 (low byte)
CRC-16 (high byte)
ETX
6408E, p. 7-3
Indication Database Request
1.2.1
Byte
Range
Description
1
2
F7
01-FF
Al
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
CRC-16 (low byte)
CRC-16 (high byte)
ETX
3
4
5
6
7.2.8
Local Control Request
Byte
Rans:e
Description
1
2
FC
01-FF
00
00-FF
00-FF
00-FF
F6
message header
PRCCI address
control byte nijmber
control byte data
CRC-16 (low byte)
CRC-16 (high byte)
ETX
3
4
5
6
7
7.2.9
Execute Local Control
Byte
1
2
3
4
5
7.2.10
Range
Description
FE
01-FF
00-FF
00-FF
F6
message-header
PRCCI address
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Local Indication Recall
Byte
1
2
3
4
5
Range
Description
FD
01-FF
00-FF
00-FF
F6
message header
PRCCI address
CRC-16 (low byte)
CRC-16 (high byte)
ETX
6408E, p. 7-4
7.2.11
Control Request
Byte
1
2
3
4
5
n-2
n-1
n
Range
Description
F8
01-FF
AC
01-7F
01-0F
message header
PRCCI address
auxiliary header
station address
control word count
01-0F
00-FF
00-FF
[ control word address ]
]
[ control word data
]
[ control word data
00-FF
00-FF
F6
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Execute Control
7.2.12
Byte
1
2
3
4
5
6
7
Range
Description
F8
01-FF
AE
01-7F
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
station address
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Indication Recall
7.2.13
Byte
Range
Description
1
2
3
F8
01-FF
AD
Ol-7F
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
station address
CRC-16 (low byte)
CRC-16 (high byte)
4
5
6
7
7.2.14
ETX
Master Recall
Byte
Range
Description
1
F8
01-FF
A6
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
CRC-16 (low byte)
CRC-16 (high byte)
2
3
4
5
6
ETX
64088, p. 7-5
7.2.15 Common Mode Request
Byte
Range
Description
1
2
3
F8
01-FF
A9
00-FF
00-FF
F6
message header
PRCCI address
auxiliary header
CRC-16 (low byte)
CRC-16 (high byte)
ETX
4
5
6
7.3
PRCCI TO OFFICE MESSAGES
7.3.1
Local Control Checkback
Byte
Range
Description
1
2
3
4
F3
01-FF
00
00-FF
00-FF
00-FF
F6
message header
PRCCI address
control byte number
control byte data
CRC-16 (low byte)
CRC-16 (high byte)
ETX
5
6
7
7.3.2 Control Checkback
Byte
1
2
3
4
5
n-2
n-1
n
7.3.3
Range
Description
PS
01-FF
A3
01-7F
01-0F
message header
PRCCI address
auxiliary header
station address
control word count
01-0F
00-FF
00-FF
[ control word address ]
[ control word data
1
[ control word data
)
00-FF
00-FF
F6
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Status Indication Register Data
. Byte
1
2
n-2
n-1
Range
Description
F4
01-FF
message header
PRCCI address
00-0F
00-FF
[ SIR number]
[ SIR flags ]
00-FF
00-FF
CRC-16 (low byte)
CRC-16 (high byte)
6408E, p. 7-6
n
F6
ETX
7.3.4 Indication
Byte
Range
Description
1
2
3
FS
01-FF
A2
message header
PRCCI address
auxiliary header
01-06
[
[
[
[
[
[
[
[
01-7F
00-0F
...
n-2
n-1
n
7.3.5
01-0F
00-FF
00-FF
[[ indication word address )
[[ indication word data
]
([ indication word data
1
00-FF
00-FF
F6
CRC-16 (low byte)
CRC-16 (high byte)
ETX
Local Indication
Range
Description
1
F2
2
01-FF
00
00-FF
00-FF
00-FF
F6
message header
PRCCI address
indication byte number
indication byte data
CRC-16 (low byte)
CRC-16 (high byte)
Byte
3
4
5
6
7
7.3.6
record type:
01 - good indication record
02 - bad indication record
04 - station in monitor
06 - station failed
station address
indication word count
ETX
Ack.now ledge
Byte
1
2
3
Range
Description
Fl
01-FF
F6
message header
PRCCI address
ETX
6408E, p. 7-7
)
]
)
]
]
)
]
1
]
1
1
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising