top - download
⟦13f650c91⟧ Wang Wps File
Length: 65694 (0x1009e)
Types: Wang Wps File
Notes: PC/TCM/001
Names: »3168A «
Derivation
└─⟦2b05c95ac⟧ Bits:30006158 8" Wang WCS floppy, CR 0067A
└─ ⟦this⟧ »3168A «
WangText
@…00……00……00……00…1…0a……00……00…1…0b…1…0d…1…0f…,…01…+…0b…+…05…*…0b…*…0f…*…01…*…07… …02……1f……08……1f……0a……1f……0d……1f……0e……10……0a……10……0b……10……00……10… …0f……09……0f……0d……0f…
…0e……08……0e……0f……0e… …0d……0b……0d……0c……0d……01……0d… …0c……0a……86…1 …02… …02… …02…
3168A/ktd …02…
…02…PLN/830115…02……02…
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL
PC/TCM/001
Peter Licht Nielsen
B]rge Hermansen
SHAPE (12), GJ, BHE, DL, KPL, KJL, PLN,
SN[, ALP, OWE, KM, EV, LT.
1
830115…86…1
…02… …02… …02…
3168A/ktd …02…
…02…PLN/830115…02……02…ii
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
Her inds`ttes First Aid
3168A/ktd …02…
…02…PLN/830115…02……02…iii
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
830115 All Original issue of
document
3168A/ktd …02…
…02…PLN/830115…02……02…iv
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…821222…02… PC
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
TITLE PAGE .....................................
i
FIRST AID FOR ELECTRICAL SHOCK ................. ii
REVISION RECORD ................................ iii
TABLE OF CONTENTS .............................. iv
LIST OF ILLUSTRATIONS .......................... vii
LIST OF TABLES .................................viii
ABBREVIATIONS .................................. ix
REFERENCED DOCUMENTS ...........................
x
1 INTRODUCTION .................................
1
1.1 SCOPE ....................................
1
1.2 MAINTENANCE MANUAL, OVERVIEW .............
1
1.3 PHYSICAL DESCRIPTION AND LAYOUT ..........
2
1.4 EQUIPMENT CONFIGURATION ..................
3
2 OPERATING PROCEDURE ..........................
5
2.1 INTRODUCTION .............................
5
2.2 MAINTENANCE MODE .........................
7
2.3 LOCAL MODE ...............................
8
2.4 OPERATIONAL MODE .........................
9
2.5 TEST MODE ................................ 11
3 PREVENTIVE MAINTENANCE ....................... 13
3.1 INTRODUCTION ............................. 13
3.2 PREVENTIVE MAINTENANCE SCHEDULE .......... 13
3.3 PREVENTIVE MAINTENANCE PROCEDURES ........ 14
3.3.1 EMI-Rack ............................. 14
3.3.2 CR80 Equipment ....................... 14
4 CORRECTIVE MAINTENANCE ....................... 15
4.1 INTRODUCTION ............................. 15
4.2 ERROR DETECTION .......................... 17
4.2.1 Unrecoverable Errors ................. 18
4.2.2 Frame Transmission Errors ............ 19
4.2.3 Message Control Errors ............... 19
4.2.4 Error Statistics ..................... 19
4.3 TROUBLESHOOTING .......................... 20
4.3.1 System Troubleshooting Tree .......... 20
4.3.2 Off-line Troubleshooting Tree ........ 20
4.4 REPLACEMENT PROCEDURE .................... 21
4.4.1 Processor Crate Replacement .......... 21
4.4.2 Processor Crate Module Replacement ... 22
4.4.3 Adapter Crate Module Replacement ..... 23
4.4.4 S-Fan Replacement .................... 24
3168A/ktd …02…
…02…PLN/830115…02……02…v
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
4.5 CONTROL, INDICATORS, AND SWITCHSETTINGS .. 25
4.6 ON-LINE TROUBLESHOOTING .................. 26
4.6.1 Completion Codes ..................... 26
4.6.2 Software Packages .................... 27
4.6.3 On-line Troubleshooting .............. 32
4.7 OFF-LINE TEST PROGRAM .................... 34
4.7.1 The Off-line Troubleshooting Tree .... 34
4.7.2 Maintenance Mode ..................... 34
4.7.2.1 CPU-SCM Test ..................... 37
4.7.2.2 EPROM Test ....................... 37
4.7.2.3 RAM Test ......................... 37
4.7.2.4 LTU TEST ......................... 37
4.7.2.5 DUMP ............................. 38
4.7.2.6 MAC Error Codes .................. 38
4.7.3 Off-line Troubleshooting Procedure ... 39
5 SOFTWARE MAINTENANCE ......................... 48
5.1 INTRODUCTION ............................. 48
5.2 S/W FAILURE .............................. 48
5.3 MEMORY DUMPS ............................. 48
5.4 NEW S/W LOADING AND VERIFICATION ......... 48
6 FAILURE REPORTING SYSTEM ..................... 49
6.1 LOGBOOK .................................. 49
6.1.1 Logbook Form ......................... 49
6.1.1.1 Heading .......................... 49
6.1.1.2 Time-Of-day ...................... 49
6.1.1.3 Start/Stop Time .................. 49
6.1.1.4 Symptom .......................... 51
6.1.1.5 Action Group ..................... 51
6.1.1.6 Action ........................... 51
6.1.1.7 Initials ......................... 51
6.2 FAILURE REPORTS .......................... 52
6.2.1 Failure Report Form .................. 52
6.2.1.1 Failure Report No. ............... 52
6.2.1.2 Identification ................... 54
6.2.1.3 Physical Location ................ 54
6.2.1.4 Type of Error .................... 54
6.2.1.5 Site Level Identification ........ 54
6.2.1.6 Repair Time ...................... 55
6.2.1.7 Error Description ................ 55
6.2.1.8 Environmental Conditions ......... 55
6.2.1.9 Type ............................. 56
6.2.1.10 Enclosure ...................... 56
3168A/ktd …02…
…02…PLN/830115…02……02…vi
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
6.3 FIELD CHANGE NOTICES (FCN) ............... 56
6.3.1 General .............................. 56
6.3.2 Registration of FCNs ................. 57
6.3.3 Description of FCNs .................. 57
6.3.3.1 Heading .......................... 57
6.3.3.2 Identification ................... 57
6.3.3.3 Parts Disposition ................ 57
6.3.3.4 Classification ................... 57
6.3.3.5 Type of Information .............. 58
6.3.3.6 Related Information .............. 58
6.3.3.7 Field Change Description ......... 58
6.3.3.8 Affected Documents ............... 58
6.3.3.9 Approval Authority ............... 58
6.3.3.10 Succeeding Pages ............... 59
6.4 CONFIGURATION CONTROL .................... 59
6.4.1 Introduction ......................... 59
6.4.2 CRAS Modules ......................... 60
6.4.3 Peripherals .......................... 64
6.4.3.1 VDU, Delta Data, Model 7260TC .... 64
7 TOOLS AND TEST EQUIPMENT ..................... 65
7.1 STANDARD TOOLS AND TEST EQUIPMENT ........ 65
7.2 SPECIAL TOOLS AND TEST EQUIPMENT ......... 65
3168A/ktd …02…
…02…PLN/830115…02……02…vii
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
L̲I̲S̲T̲ ̲O̲F̲ ̲I̲L̲L̲U̲S̲T̲R̲A̲T̲I̲O̲N̲S̲
F̲i̲g̲u̲r̲e̲ T̲i̲t̲l̲e̲ P̲a̲g̲e̲
1.3-1 PC Equipment
2
1.4-1 PC Hardware Configuration
4
2.1-1 Command Included Mode Transition
6
4.6.2-1 Software Packages and Interfaces 28
4.6.2-2 Logon sequence 29
4.6.2-3 CAMPS/SCARS to CCIS Transfer 30
4.6.2-4 CCIS to CAMPS/SCARS Transfer 31
4.6.3-1 On-line Troubleshooting Tree 33
4.7.1-1 Off-line Diagnostics and PC corelation 35
4.7.3-1 Off-line Troubleshooting Flow Chart 40
6.1.1-1 Logbook 50
6.2.1-1 Failure Report 53
6.4.3-1 Field Change Notice, front page 62
6.4.3-2 Field Change Notice, subsequent page 63
3168A/ktd …02…
…02…PLN/830115…02……02…viii
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
L̲I̲S̲T̲ ̲O̲F̲ ̲T̲A̲B̲L̲E̲S̲
T̲a̲b̲l̲e̲ T̲i̲t̲l̲e̲ P̲a̲g̲e̲
3.2-1 Preventive Maintenance Schedule 13
4.1-1 Corrective Maintenance Tasks 16
4.6.1-1 Completion Codes 26
3168A/ktd …02…
…02…PLN/830115…02……02…ix
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
The following lists the abbreviations as used throughout
the maintenance manual.
M̲n̲e̲m̲o̲n̲i̲c̲s̲ E̲x̲p̲l̲a̲n̲a̲t̲i̲o̲n̲
CAMPS Computer Aided Message Processing System
CCIS Command and Control Information System
CPU-SCM Central Processing Unit - System Control
Module
CRAS Christian Rovsing A/S
CSA CPU-SCM Adapter
CTS Clear To Send
DINDAC Auto DIN-WWMCCS Direct Access Communications
Module
ECO Engineering Change Order
EPROM Erasable Programable Read Only Memory
FCN Field Change Notice
H/W Hardware
IC Integrated Circuit
LED Light Emitting Diode
LIA-N Line Interface Adapter, Non Switching
LTU Line Termination Unit
L/L ADAPT V.24/V.28, Low level Long distance driving
Adapter
M&D Maintenance & Diagonostics
NO Number
N.A. Non Applicable
OPTO-T/R Optical Transmitter and Receiver
PC Protocol Converter
PCB Printed Circuit Board
PMM Processor Memory Module
PSAT Provisional Site Acceptance Test
PU Processor Unit
RAM Random Access Memory
RST Resident Site Technician
RTS Ready To Send
SCARS II Status and Control Altering and Reporting
System
S/W Software
TBD To be defined
VDU Visual Display Unit
3168A/ktd …02…
…02…PLN/830115…02……02… x
PROTOCOL CONVERTER
SITE MAINTENANCE MANUAL…02…PLN/821222…02… PC
R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
a. Protocol Converter Equipment Handbook
PC/HBK/001
b. Protocol Converter Hardware Assembly Break-down
PC/HBK/002
c. Technical Manual for EMI/RFI Shielded Enclosures
CPS/TCM/018
d. Protocol Converter Installation Manual
PC/.../...
e. Protocol Converter Inventory Manual
PC/.../...
f. CAMPS Site Maintenance Manual
CPS/TCM/005…86…1 …02… …02… …02… …02…
1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
1.1 S̲C̲O̲P̲E̲
This manual together with the Assembly Break-down and
the Inventory Manual, makes up the Maintenance Handbook,
which is the reference manual for the complete site
maintenance of the Protocol Converter between CAMPS/
SCARS II, and CCIS .
1.2 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲M̲A̲N̲U̲A̲L̲,̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
In addition to this present section, the site maintenance
manual is divided into 6 sections, each covering a
well defined part of the Protocol Converter site maintenance.
The contents of the sections are described shortly
below.
a. The O̲p̲e̲r̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲ (section 2) is
a description of all normal procedures
operated from the maintenance position.
b. The P̲r̲e̲v̲e̲n̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ (section 3)
describes the scheduled preventive maintenance
to be carried out on the Protocol Converter
Equipment.
c. The C̲o̲r̲r̲e̲c̲t̲i̲v̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ (section 4)
describes the actions to be taken from
the moment an error is detected until the
equipment is brought back to normal operation.
d. The S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ (section 5) describes
the tasks at site level to be carried out,
whenever a software failure occurs.
e. The F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲i̲n̲g̲ ̲S̲y̲s̲t̲e̲m̲ (section 6)
contains a description of the paperwork
related to site maintenance of the Protocol
converter.
f. The T̲o̲o̲l̲s̲ ̲a̲n̲d̲ ̲T̲e̲s̲t̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲ (section 7)
lists the tools and test equipment required
for site maintenance.
1.3 P̲H̲Y̲S̲I̲C̲A̲L̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲L̲A̲Y̲O̲U̲T̲
The Protocol Converter equipment is shown in Figure
1.3-1.
For detailed information, refer to Protocol Converter
Hardware Assembly Break-down, PC/HBK/002 and Protocol
Converter Equipment Handbook, PC/HBK/001.
Her inds`ttes figur 1.3-1
Figure 1.3-1
1.4 E̲Q̲U̲I̲P̲M̲E̲N̲T̲ ̲C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲
The Protocol Converter Hardware Configuration is shown
in Figure 1.4-1.
From a corrective maintenance point of view, it is
important that the system is broken down into well-defined
subsystems. The isolation of a detected error to a
subsystem is the first step when tracing an error to
a replaceable module/unit.
The subsystems are:
a) Processor Units
b) Adapter Crate Units
c) Distribution Equipment
Each unit of the subsystems are described in details
in Protocol Converter Handbook, PC/HBK/001, section
3.3.
Figure 1.4-1
2 O̲P̲E̲R̲A̲T̲I̲N̲G̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
2.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The system will at any time be in one of four modes,
each mode defining a state with certain capabilities.
The system modes are:
a) Maintenance Mode
b) Local mode
c) Operational mode
d) Test mode
The system is controlled by an operator who - via the
maintenance VDU - communicates with the system giving
commands and receiving responses. The execution of
a command may change the current mode of the system
and the current mode defines which commands are accepted.
The system will display a prompt on the VDU when ready
to receive a command. This prompt will also show the
current mode of the system.
Once the system is brought into operational mode, the
VDU may be dis-patched from the converter which will
continue operating unaffected.
The relationship between modes and commands is depicted
in Figure 2.1-1 and further described in the following
sections.
Figure 2.1-1…01…Graph Showing Command Induced Mode Transitions
2.2 M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲M̲O̲D̲E̲
This is the initial mode entered as a result of a 'power
up' or 'restart button activation'.
This mode provides the means to check out the functioning
of the hardware modules by running test programs. The
test programs are activated by commands entered from
the maintenance VDU. Included is also a command for
dumping out memory.
In maintenance mode, the requirements to the functioning
of the software is kept at a minimum. Neither the application
software nor the operating system is required when
running maintenance mode. The CPU communicates directly
with the VDU not involving the driver.
Commands accepted:
a̲)̲ C̲h̲e̲c̲k̲
Format:
CHECK module name
where: module name ::= CPU EPROM RAM
LTUA LTUB
Function:
A test program checking the indicated module is
activated and the result is displayed on the VDU.
Resulting mode: MAINTENANCE
b̲)̲ D̲u̲m̲p̲
Format:
DUMP page ̲ start addr ̲ stop addr
where: start addr ::= hex integer
stop addr ::= hex integer
page ::= hex integer
Function:
A hexadecimal memory content dump within the limits
specified (is displayed on the VDU). Upper limit
may be specified as either stop address or number
of words from start address.
Resulting mode: MAINTENANCE
c̲)̲ I̲n̲i̲t̲.̲
Format:
INIT
Function:
The system is initialised, i.e. the operating system
is started up and the application system is generated
and initialised. The system will still be offline
(end systems not connected).
Resulting mode: if ok LOCAL
otherwise MAINTENANCE
2.3 L̲O̲C̲A̲L̲ ̲M̲O̲D̲E̲
In this mode, the system is generated and initialised
but offline.
Commands accepted:
a̲)̲ L̲o̲g̲o̲n̲
Format:
LOGON CAMPS SCARS S= speed ; CCIS S=
speed
where: speed ::= 2400 4800 9600
System responds by following text on next line:
ID$PASSWORD=
and operator continues the line by entering:
userid $ password
This information will not be visible on the VDU since
blanks will be echoed following '='.
Example:
LOGON CAMPS S=4800; CCIS S=4800
ID$PASSWORD=
Function:
Logon to the end systems specified is performed. Outgoing
baud rates may be specified. If omitted the default
value 2400 will be used.
The userid and password is passed on for logon
to the CCIS side.
The distinction between CAMPS and SCARS is verified
when messages are received from CAMPS/SCARS by comparing
SCI of incoming message with prestored table of possible
values for CAMPS and for SCARS. For messages in the
opposite direction no check is performed.
If both ends are opened successfully, transactions
may start flowing. If one side fails, the other is
closed again. The result is displayed on the VDU.
Resulting mode: if ok OPERATIONAL
otherwise LOCAL
b̲)̲ M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
Format:
MAINTENANCE
Function:
The system is brought into maintenance mode.
Resulting mode: MAINTENANCE
2.4 O̲P̲E̲R̲A̲T̲I̲O̲N̲A̲L̲ ̲M̲O̲D̲E̲
In this mode, the system is on-line with end systems
connected and transcation flow open.
Commands accepted are:
a̲)̲ S̲h̲o̲w̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Format:
SHOW STATISTICS
Function:
For each side, the accumulated values of the following
statistics counters are displayed:
No. of frames transmitted
No. of frames retransmitted
No. of frames received error free
No. of frames received with error
Resulting mode: unchanged
b̲)̲ R̲e̲s̲e̲t̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Format:
RESET STATISTICS
Function:
The statistics counters are all reset to 0.
Resulting mode: unchanged
c̲)̲ L̲o̲g̲o̲f̲f̲
Format:
LOGOFF
Function:
The end systems are disconnected from PC.
Resulting mode: LOCAL
d̲)̲ T̲e̲s̲t̲
Format:
TEST
Function:
The system is brought into test mode.
Resulting mode: TEST
2.5 T̲E̲S̲T̲ ̲M̲O̲D̲E̲
In this mode, the system is on-line with end systems
connected.
This mode provides the means for testing each link
individually.
The test is performed by applying a loop-back procedure
to testmessages built into PC. Since PC in test mode
will violate the rule of end-to-end acknowledgement
and treat each link individually, and furthermore will
disturb the the Transmission Serial Number numbering,
this mode requires the cooperation of the operator
of the CAMPS/SCARS system. When receiving a test message,
the operator at the CAMPS/SCARS side shall send it
back to the channel identifying the other end system.
The operator must also make sure that normal transaction
is suspended during test. This manual supervision of
test mode is necessary since the CAMPS/SCARS systems
have no facilities in the form off special service
messages to support an automated test procedure.
For test of the PC-CCIS link, the DINDAC reflect mode
will be used for automatic loop-back. This requires
the DINDAC utilities named KEN and SAM to be available
in CCIS.
Commands accepted are:
a̲)̲ V̲e̲r̲i̲f̲y̲
Format:
VERIFY desrination L= message length
where: destination ::= CCIS CAMPS SCARS
message length ::= integer
Function:
One of three prestored standard messages in E1
format (level 4 format) is selected in accordance
with the destination specified, i.e. CCIS, CAMPS,
or SCARS. The message is modified to contain the
number of bytes indicated by message length .
This is done by truncation or repetition of the
standard contents of the message. The message is
transmitted to the destination and when acknowledged,
PC will wait to receive a message from the same
side. When this happend, PC will acknowledge the
reception and compare in length and content the
message received with the message transmitted.
If equal, the test was successful, otherwise the
test failed. The result is displayed on the VDU.
Resulting mode: TEST
b̲)̲ S̲h̲o̲w̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
See 2.4 a)
c̲)̲ R̲e̲s̲e̲t̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
See 2.4 b)
d̲)̲ L̲o̲g̲o̲f̲f̲
See 2.4 c)
Note that is not possible to reenter operational mode
directly. However, a logoff followed by a logon will
bring the system into operational mode.
3 P̲R̲E̲V̲E̲N̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
3.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
This section contains all information and references
necessary to perform the required preventive maintenance
(PM) routines.
The prime objective of any preventive maintenance activity
is to provide maximum equipment availability to the
user.
Electronic equipment is relatively free from preventive
maintenance. Equipment with electro-mechanical parts
must, however, frequently be examined to insure optimal
operation as outlined in the procedure and objectives
of the preventive maintenance described in this section.
The schedule and procedures mentioned in the following
paragraphs are identical to those of the equivalent
CAMPS equipment.
3.2 P̲R̲E̲V̲E̲N̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲
The main factor in setting maintenance intervals is
the cleanliness of the installation site. The intervals
assumes that the equipment is installed in a computer
room environment and as such has scheduled maintenance
consistent with this fact.
Table 3.2-1 provides the preventive maintenance index.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲R̲A̲C̲K̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲C̲R̲8̲0̲ ̲S̲-̲F̲A̲N̲ ̲ ̲ ̲ ̲
MONTHLY Clean Filter
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
QUARTERLY Clean Filter
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
ANNUALLY Replace Filter
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Table 3.2-1…01…Preventive Maintenance Schedule
3.3 P̲R̲E̲V̲E̲N̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
Visual inspection is the first step in every scheduled
maintenance operation. Always look for corrosion, dirt,
lint, wear, binds, and loose connections. Correcting
these items duting preventive maintenance may save
down-time later.
3.3.1 R̲a̲c̲k̲
Monthly: Remove dust and dirt from filters by vacuuming.
Technical Manual for EMI/RFI Shielded Enclosures, section
3.4 describes in detail the procedures to be performed.
3.3.2 C̲R̲8̲0̲ ̲E̲q̲u̲i̲p̲m̲e̲n̲t̲
All CR80 equipment except the S-Fans is free of preventive
maintenance.
S-Fans
Quarterly: Clean filters
Annually: Replace filters
Refer to PC/HBK/002 Protocol Converter Hardware Assembly
Breakdown Figure .... for the location of the S-Fan
units.
Gain access to the filter cushions by removing the
front plate.
Remove excess dust and lint from filters by vacuuming.
If filters are extremely dirty or linted, remove filters.
Replace Filters
Close Fan Unit.
4 C̲O̲R̲R̲E̲C̲T̲I̲V̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
4.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The objective of the corrective maintenance is to detect
whenever an error has occurred, perform the necessary
repair, and bring the system back to normal operation.
An overview of the corrective maintenance tasks is
given in Table 4.1-1.
The tasks are shortly explained below.
The completion code displayed on the maintenance VDU
will normally provide an entry point to a particular
troubleshooting procedure and by following the description
outlined, the error is isolated to a particular module.
A verification test is performed prior to returning
to normal operation procedure and bringing the Protocol
Converter back into on-line mode.
The structure of chapter 4 is as follows:
- Section 4.2 describes how errors might be detected
depending on whether or not the maintenance VDU
is connected.
- Section 4.3 contains an overview of the troubleshooting
procedures in which the strategy of tracing a detected
error to a module is described. The troubleshooting
procedures are described by a system troubleshooting
tree and an off-line troubleshooting tree.
- Section 4.4 contains the replacement procedures
of the modules/crate to be followed when an error
has been isolated to be within a particular module/crate.
- Section 4.5 described the controls, indicators,
switchsettings, and addresses of the modules within
the Protocol Converter and is considered as a reference
to the troubleshooting procedures and replacement
procedures.
Table 4.1-1…01…Corrective Maintenance Tasks
- Section 4.6 describes briefly the tasks of the
completion code program and describes the type
of completion codes and their interpretation.
- Section 4.7 provides a description of activating
commands and interpretation of error codes for
each of the off-line M&D programs.
The off-line M&D test sequences are used in the off-line
troubleshooting procedures.
4.2 E̲R̲R̲O̲R̲ ̲D̲E̲T̲E̲C̲T̲I̲O̲N̲
Three types of errors may be encountered:
a. unrecoverable errors
b. frame transmission errors
c. message control errors
Errors of category a. will cause the PC to perform
an orderly closing of the links if feasible.
Errors of type b. or c. are handled according to the
level 2 and 3 protocols, respectively. The operator
will not be notified about these errors except through
the use of the SHOW STATISTICS command.
In case of an unrecoverable error the PC will attempt
to write an error message to the VDU. If the VDU is
not connected, the PC continues sensing the V24 Terminal
Ready signal until it is set by the VDU being patched
on.
In the following, it is assumed that the maintenance
VDU is connected to the PC.
4.2.1 U̲n̲r̲e̲c̲o̲v̲e̲r̲a̲b̲l̲e̲ ̲E̲r̲r̲o̲r̲s̲
These are errors due to PC internal malfunctioning,
link failure, and failure of an end system. If PC detects
an unrecoverable error, it will close down the system
and an error message will be sent to the VDU. Close
down will bring the system from on-line operational
mode to off-line local mode.
The error message displayed is shown below. The interpretation
of the completion code is described in section 4.6.
CLOSE DOWN EXECUTED, RESULT = X0YY
L
4.2.2 F̲r̲a̲m̲e̲ ̲T̲r̲a̲n̲s̲m̲i̲s̲s̲i̲o̲n̲ ̲E̲r̲r̲o̲r̲s̲
These errors are detected as frame check sequence errors
on CAMPS/SCARS side and subsequent check errors on
the CCIS side. The protocols in question will perform
recovery in terms of retransmission requests on occurrence
of these errors.
No message will be displayed.
4.2.3 M̲e̲s̲s̲a̲g̲e̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲E̲r̲r̲o̲r̲s̲
These are errors detected as inconsistency or invalidity
in content of the message control field of CAMPS/SCARS
level 3 frames or segment header of CCIS segments.
Errors detected as excessive message length are also
included in this category. Message control errors are
detected and reported by PC, but end systems are responsible
for recovery.
No message will be displayed.
4.2.4 E̲r̲r̲o̲r̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
PC has implemented a facility for collecting statistics
concerning frame transmission/reception to/from both
end systems. The data collected for each side is the
number of:
- frames transmitted
- frames retransmitted
- error-free received frames
- frames received with error
The statistics can be displayed on the maintenance
VDU on demand and a separate command for resetting
the counters is implemented.
The commands are as follows:
SHOW STATISTICS
- for each side the accummulated values of the
statistics counters are displayed
RESET STATISTICS
- the statistics counters are all reset to 0.
4.3 T̲R̲O̲U̲B̲L̲E̲S̲H̲O̲O̲T̲I̲N̲G̲
The troubleshooting procedures of the Protocol Converter
equipment are described by two troubleshooting trees:
- System Troubleshooting Tree
- Off-line Troubleshooting Tree
4.3.1 S̲y̲s̲t̲e̲m̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The troubleshooting of the Protocol Converter equipment
starts whenever an error is reported either at the
maintenance VDU or by the operator/technician of the
end systems.
The system troubleshooting tree identifies the next
step to be followed, either by identifying the first
step in the off-line troubleshooting procedure or the
next step in the system troubleshooting tree.
The system troubleshooting is described in detail in
section 4.6.
4.3.2 O̲f̲f̲-̲l̲i̲n̲e̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The off-line troubleshooting tree describes the relations
between the H/W module or string of modules in the
Protocol Converter equipment and the entry point in
the off-line test procedure to be executed.
The off-line troubleshooting is described in detail
in section 4.7.
4.4 R̲E̲P̲L̲A̲C̲E̲M̲E̲N̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
This section describes the replacement procedures of
the modules and crates mounted in the Protocol Converter
rack.
For the replacement of power distribution panel, signal
and power cables, line filters, and patch panel refer
to INSTALLATION MANUAL.
4.4.1 P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲C̲r̲a̲t̲e̲ ̲R̲e̲p̲l̲a̲c̲e̲m̲e̲n̲t̲
The Processor Crate with modules is replaced using
the following steps.
S̲T̲E̲P̲ ̲ ̲ ̲ ̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
1 Turn power OFF on the power switch at the rear
of the PU crate
2 Disconnect all V.24 cables from the modules
in the PU crate
3 Disconnect power and ground cable from the
PU crate
4 Unscrew the crate screws on the front and remove
the crate
5 Insert the spare PU crate. Tighten the crate
screws
6 Connect ground and power cable to the crate
7 Connect the V.24 cables to the modules in the
PU crate
8 Turn power ON on the power switch at the rear
of the crate
9 Check the LEDs on the front of the modules
in the crate (refer to section 4.5)
10 Close the doors to the PC
4.4.2 P̲r̲o̲c̲e̲s̲s̲o̲r̲ ̲C̲r̲a̲t̲e̲ ̲M̲o̲d̲u̲l̲e̲ ̲R̲e̲p̲l̲a̲c̲e̲m̲e̲n̲t̲
The following module replacement procedures are described:
- CPU/SCM - CSA
- LTU - LIA-N
- RAM
- EPROM
S̲T̲E̲P̲ ̲ ̲ ̲ ̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
1 Turn power OFF on the power switch at the rear
of the PU crate
2 Unscrew the module fingerscrews. Disconnect
the cables from the module, if any. Remove
the actual module from the crate.
3 Verify that switchsetting in the spare module
are correct (refer to section 4.5)
4 Insert the spare module in the crate. Connect
the cables to the module, if any. Tighten the
module fingerscrews
5 Turn power ON on the power switch at the rear
of the crate
6 Check the LEDs on the front of the module (refer
to section 4.5)
7 Close the doors to the PC
4.4.3 A̲d̲a̲p̲t̲e̲r̲ ̲C̲r̲a̲t̲e̲ ̲M̲o̲d̲u̲l̲e̲ ̲R̲e̲p̲l̲a̲c̲e̲m̲e̲n̲t̲
The following module replacement procedures are described:
- OPTO T/R Adapter
- V28 L/L Adapter
S̲T̲E̲P̲ ̲ ̲ ̲ ̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
1 Turn power OFF on the Adapter Power Supply
mounted on the rear of the Adapter Crate
2 Unscrew the module fingerscrews. Disconnect
the cables from the module, if any. Remove
the actual module from the crate.
3 Verify that strapsettings in the spare module
are correct (refer to section 4.5)
4 Insert the spare module in the crate. Connect
the cables to the module, if any. Tighten the
module fingerscrews.
5 Turn power ON on the Adapter Power Supply mounted
on the rear of the crate
6 Check the LEDs on the front of the modules
(refer to section 4.5)
7 Close the doors to the PC
4.4.4 S̲-̲F̲a̲n̲ ̲R̲e̲p̲l̲a̲c̲e̲m̲e̲n̲t̲
IMPORTANT
It is important that the replacement time of the fan
does not exceed 3 minutes, otherwise the rack temperature
may increase to a critical level. Therefore, read this
procedure before actual replacement of the fan begins.
S̲T̲E̲P̲ ̲ ̲ ̲ ̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲
1 Open the doors to the PC
2 Verify that a spare fan is situated on the
floor near the rack
3 Unscrew the fan unit screws on the front
4 Turn power OFF on the switch placed on the
rear of the fan unit
5 Disconnect the fan power cable from the Power
Distribution Panel
6 Remove the fan unit
7 Insert the spare fan unit
8 Connect the fan power cable to the power distribution
panel
9 Turn power ON on the switch placed at the rear
of the fan unit
10 Tighten the fan unit screws
11 Close the doors to the PC
4.5 C̲O̲N̲T̲R̲O̲L̲,̲ ̲I̲N̲D̲I̲C̲A̲T̲O̲R̲S̲,̲ ̲A̲N̲D̲ ̲S̲W̲I̲T̲C̲H̲S̲E̲T̲T̲I̲N̲G̲S̲
This section describes the controls, indicators, addresses,
and switchsettings of the modules, units, and crates
mounted in the PC rack.
In the following, only the normal indications are described.
For detailed information about control, indicators,
strap- and switchsettings, refer to PC Equipment Handbook
PC/HBK/001.
C̲O̲N̲T̲R̲O̲L̲/̲I̲N̲D̲I̲C̲A̲T̲O̲R̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲N̲O̲R̲M̲A̲L̲ ̲I̲N̲D̲I̲C̲A̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
POWER SWITCH ON Green "Power ON"
FAN SWITCH ON Fan running
PU CRATE SWITCH ON Blowers running
Green "Power ON"
Power LED on modules to be
lit
ADAPTER CRATE PS ON Power LEDS on modules to be
lit
CPU/SCM Power LED ON
RAM Power LED ON
EPROM Power LED ON
LTU Power LED ON
OPTO T/R Power LED ON
RTS & CTS yellow LED ON
V28 L/L ADAP Power LED ON
4.6 O̲N̲-̲L̲I̲N̲E̲ ̲T̲R̲O̲U̲B̲L̲E̲S̲H̲O̲O̲T̲I̲N̲G̲
This section describes briefly the tasks of the completion
code program and describes the types of completion
codes and their interpretation. This section also gives
the system troubleshooting tree which identifies: the
entry-point in the off-line troubleshooting tree, or
the next step to be followed.
4.6.1 C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲s̲
The purpose of the Completion Codes is to give the
maintenance personnel an identification of which program
package that detected an irregularity.
Each Software Package has its own completion code identifier.
Table 4.6.1-1 lists the various completion code groups.
C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲ ̲ ̲ ̲ ̲I̲D̲ ̲ ̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲ ̲ ̲ ̲ ̲ ̲ ̲
#90XX CI Command Interpreter
#A0XX TRC Traffic Controller
#B0XX CPA CCIS Protocol Adapter
#C0XX CSPA CAMPS/SCARS Protocol Adapter
#D0XX MAC Maintenance Controller
#E0XX SGI System Generator # Initializer
#F0XX CSLP CAMPS/SCARS Low Level Protocols
#F1XX CLP CCIS Low Level Protocols
Table 4.6.1-1
4.6.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲P̲a̲c̲k̲a̲g̲e̲s̲
In the following figures, the software packages, their
interfaces and control flow are shown.
Figure 4.6.2-1 shows the software packages and their
interfaces. Furthermore, the underlaying hardware is
indicated (note that CSLP and CLP each reside in a
dedicated LTU).
Figure 4.6.2-2 shows the control flow resulting from
a logon command from the operator.
Figure 4.6.2-3 shows the control flow involved in transaction
transfer from CAMPS/SCARS to CCIS.
Figure 4.6.2-4 shows the control flow involved in transaction
transfer from CCIS to CAMPS/SCARS.
Figure 4.6.2-1…01…Software Packages and Interfaces
Figure 4.6.2-2…01…Inter Package Control Flow …01…Logon Sequence
Figure 4.6.2-3…01…Inter Package Control Flow …01…CAMPS/SCARS to CCIS Transfer
Figure 4.6.2-4…01…Inter Package Control Flow…01…CCIS to CAMPS/SCARS Transfer
4.6.3 O̲n̲-̲l̲i̲n̲e̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲
All errors encountered during change in mode from LOCAL
to OPERATIONAL, OPERATIONAL to TEST and the command
VERIFY performed in TEST MODE, is in the following
defined as on-line errors.
Actual on-line unrecoverable errors will always cause
the PC to clear the message buffers and put the system
in LOCAL MODE.
Loss of power will have the same effect as "Master
Clear", resulting in "Maintenance Mode".
Figure 4.6.3-1 shows the on-line troubleshooting tree.
represents the Mode Prompt
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ represents the Command
represents the Software Package Process
Figure 4.6.3-1…01…On-line Troubleshooting Tree
4.7 O̲F̲F̲-̲L̲I̲N̲E̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲G̲R̲A̲M̲
4.7.1 T̲h̲e̲ ̲O̲f̲f̲-̲l̲i̲n̲e̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲T̲r̲e̲e̲
The off-line troubleshooting tree specifies a method
of isolating a detected error to a module.
Section 4.7.3 contains step-by-step procedures to be
executed when an error is to be isolated down to a
module.
Figure 4.7.1-1 shows the relation between the off-line
troubleshooting tree and the Protocol Converter system.
The figure specifies for each module (or string of
modules) in the configuration the off-line test sequence
in the step-by-step procedure which tests the module
or modules.
4.7.2 M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲ ̲M̲o̲d̲e̲
All off-line troubleshooting is performed in the Maintenance
Mode.
This is the initial mode entered as a result of a "power
up" or "master clear button activation". The Maintenance
Mode can also be reached from Local Mode.
From Local Mode, Maintenance Mode is reached by entering
the command:
MAINTENANCE (C̲R̲) (return carriage)
The VDU will display:
M -
In Maintenance Mode, the Maintenance Controller (MAC)
Software Package is responsible for off-line hardware
module test facilities.
The function of MAC is to:
- decode test commands from operator (VDU)
- start hardware module test programs
- communicate result of test to operator (VDU)
Figure 4.7.1-1
OFF-LINE DIAGNOSTICS AND PC CORELATION…86…1 …02… …02… …02… …02… …02… …02… …02…
Command keywords accepted by MAC are:
CHECK module name
DUMP page start addr stop addr
INIT
Errors in the command are indicated by:
UNKNOWN COMMAND
UNACCEPTABLE COMMAND
PARAMETER ERROR
Immediately following the error message, the system
will prompt for a new command.
Commands accepted by MAC are executed using procedure
calls, except for the INIT command. This command copies
all other PC programs from the EPROM into RAM. MAC
then loads the System Generator and Initializer (SGI)
process which transfers the VDU control to the Command
Interpreter (CI) process. The resulting mode is Local
Mode.
H/W tests and dump facilities performed by MAC are
described in sections 4.7.2.1 through 4.7.2.5. Upon
completion of commands, MAC presents a result line
to the operator:
(command keyword) EXECUTED, RESULT = (hex number)
If an error has occurred, MAC sets the leftmost of
the four digits in the result code to "D" which is
reserved for MAC error codes. The error is further
described in the two rightmost digits.
The possible MAC error codes are listed in section
4.7.2.6.
A successfully completed command is indicated by the
result code #0000.
Furthermore a CHECK EPROM command will cause the following
line to be displayed on the VDU following the result
line:
CHECKSUM = (hex number)
where the hex number represents the checksum accummulated.
The results are followed by a mode prompt for a new
command. When output by MAC, the prompt is M -
4.7.2.1 C̲P̲U̲-̲S̲C̲M̲ ̲T̲e̲s̲t̲
The CPU-SCM test computes a checksum of the SCM prom
and compares the result to a given value.
If the result of checksumming is ok, a selected set
of CPU instructions are executed and checked.
4.7.2.2 E̲P̲R̲O̲M̲ ̲T̲e̲s̲t̲
An EPROM checksum is generated assuring that the EPROM
is accessible, and that the contents of the EPROM is
unaltered.
4.7.2.3 R̲A̲M̲ ̲T̲e̲s̲t̲
The RAM accessibility and addressing logic is tested
by reading and writing the address of all memory locations
into the locations themselves. The result is verified
by reading the address for each memory location. The
original RAM contents is restored. The RAM configuration
to be tested is described in an array of 64 entries.
Each entry specifies the address space of a 4K RAM
segment. Only memory segments specified in the array
will be tested.
This way, the SCM prom, the MAC program/process areas,
as well as unavailable memory in the 256k address space
are excluded from the read/write test.
4.7.2.4 L̲T̲U̲ ̲T̲e̲s̲t̲
The specified LTU is checked for accessibility by exercising
the LTU/CR80 shared RAM area. The test is performed
using CR80 I/O instructions activating the prommed
part of the LTU firmware.
4.7.2.5 D̲u̲m̲p̲
The DUMP command will dump the requested amount of
RAM or PROM within page boundaries. Message buffer
areas may be dumped as well. However, MAC clears these
buffers whenever it is invoked. The dump consists of
lines such as:
FE08: ABCD ABCD ABCD ABCD ABCD ABCD ABCD ABCD
where FE08 is the absolute address of the first word
dumped within the specified address, and ABCD is an
example of the contents of the following 8 memory locations.
4.7.2.6 M̲A̲C̲ ̲E̲r̲r̲o̲r̲ ̲C̲o̲d̲e̲s̲
MAC error codes are declared as a sequence of hexadecimal
constants.
The possible results are:
00 - ok
01 - illegal ̲name
02 - illegal ̲mac ̲function
03 - scm ̲error
04 - cpu ̲error
05 - eprom ̲not ̲responding
06 - eprom ̲checksum
07 - ram ̲not ̲responding
08 - ram ̲addressing ̲error
09 - ltu ̲ram ̲compare
0A - ltu ̲ram ̲timeout
0B - eprom ̲ram ̲copy
4.7.3 O̲f̲f̲-̲l̲i̲n̲e̲ ̲T̲r̲o̲u̲b̲l̲e̲s̲h̲o̲o̲t̲i̲n̲g̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
The off-line troubleshooting procedures are described
in step-by-step procedure, i.e. each step contains
a test and the result of the test specifies the next
step to be executed. The next step contains the next
test to be executed. The result of this test specifies
the next step ....... and so on until the error is
traced to a faulty module.
Each step is presented in a three column format:
STEP PROCEDURE OBSERVATION/ACTION
-̲S̲T̲E̲P̲
Each test is identified by a three digit step number.
First digit specifies the module or string of modules
to which the test applies. Refer to Figure 4.7.1-1.
-̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
The activating procedure of the test is specified in
the PROCEDURE column. The types of test can be of either
a command activated test, a manual activated test,
or a visual test and inspection.
-̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲
In the OBSERVATION/ACTION column are listed all possible
results of the test activated in the procedure column.
When a test is activated and finished, the result is
compared with the different results listed in the OBSERVATION/ACTION
COLUMN. The option which is identical to the result
of the test, contains a pointer to the next step in
the troubleshooting procedure or the action to be taken.
Figure 4.7.3-1 shows the OFF-LINE TROUBLESHOOTING FLOW
CHART as represented in the following step-by-step
procedure.
Figure 4.7.3-1…01…Off-line Troubleshooting Flow Chart
C̲P̲U̲/̲S̲C̲M̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
100 Check CPU a) Result = 0000
Go to step 200
b) Result = D003
indicates an SCM error
Replace CPU/SCM
c) Result: D004
indicates a CPU error
Replace CPU/SCM module
E̲P̲R̲O̲M̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
200 Check EPROM a) Result = 0000
Go to step 300
b) Result = D005
indicates that EPROM is
not responding
Replace EPROM
c) Result: D006
indicates an EPROM checksum
error
Replace EPROM module
R̲A̲M̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
300 Check RAM a) Result = 0000
Go to step 400
b) Result = D007
indicates that RAM is not
responding
Replace RAM
c) Result: D008
indicates a RAM addressing
error
Replace RAM module
L̲T̲U̲A̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
400 Check LTUA a) Result = 0000
Go to step 500
b) Result = D009
indicates LTU RAM error
(LTU RAM compare)
Replace LTUA
c) Result: D00A
indicates a LTU interrupt
(LTU RAM TIME OUT)
Replace LTUA module
L̲T̲U̲B̲ ̲T̲E̲S̲T̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
500 Check LTUB a) Result = 0000
Go to step 600
b) Result = D009
indicates LTU RAM error
(LTU RAM compare)
Replace LTUB
c) Result: D00A
indicates an LTU interrupt
(LTU RAM TIME OUT)
Replace LTUB module
I̲N̲I̲T̲I̲A̲L̲I̲S̲A̲T̲I̲O̲N̲
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
600 INIT a) Result = 0000
L
indicates that initialisation
has been completed. Proceed
with the OPERATION PROCEDURE.
b) Result = D005
or
Result = D006
indicates an EPROM error
Go to step 200
c) Result = D00B
indicates an EPROM ro LTU-RAM
copy error
Go to step 400
d) Result = Dxxx
indicates other MAC errors.
Go to step 100
e) Result = Exxx
indicates a System Generation
and Initialisation (SGI)
error
Replace complete processor
crate
f) Result = 9xxx
indicates an Command Interpreter
(CI) error
Replace complete processor
crate
S̲T̲E̲P̲ ̲ ̲ ̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲O̲B̲S̲E̲R̲V̲A̲T̲I̲O̲N̲/̲A̲C̲T̲I̲O̲N̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
600 g) Result = Axxx
(cont'd) indicates a Traffic Controller
error
Replace complete processor
crate
h) Result = Cxxx
indicates a CAMPS/SCARS
Protocol Adaptor (CSPA)
error
Replace complete processor
crate
i) Result = Bxxx
indicates a CCIS Protocol
Adaptor (CPA) error
Replace complete processor
crate
5 S̲O̲F̲T̲W̲A̲R̲E̲ ̲M̲A̲I̲N̲T̲E̲N̲A̲N̲C̲E̲
5.1 I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
TBD
5.2 S̲/̲W̲ ̲F̲A̲I̲L̲U̲R̲E̲
TBD
5.3 M̲E̲M̲O̲R̲Y̲ ̲D̲U̲M̲P̲S̲
TBD
5.4 N̲E̲W̲ ̲S̲/̲W̲ ̲L̲O̲A̲D̲I̲N̲G̲ ̲A̲N̲D̲ ̲V̲E̲R̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
TBD
6 F̲A̲I̲L̲U̲R̲E̲ ̲R̲E̲P̲O̲R̲T̲I̲N̲G̲ ̲S̲Y̲S̲T̲E̲M̲
6.1 L̲O̲G̲B̲O̲O̲K̲
A logbook is issued to be used from the date of acceptance
(PSAT) of the equipment. In the logbook, all deviations
from the normal operation of the Protocol Converter
equipment is logged. Thus, the logbook must at all
times reflect the status of the equipment and the place
where the history record of the equipment is found.
A copy of the logbook may be enclosed a failure report
in case of an error.
6.1.1 L̲o̲g̲b̲o̲o̲k̲ ̲F̲o̲r̲m̲
A logbook sheet is shown in Figure 6.1.1-1 and the
use of the logbook is explained in the following.
6.1.1.1 H̲e̲a̲d̲i̲n̲g̲
The date is written as year-month-day. In case the
day's event cannot be described on one page, subsequent
pages may be added.
6.1.1.2 T̲i̲m̲e̲-̲o̲f̲-̲D̲a̲y̲
The time to be filled in is the one at which the event
occurred. The time is filled in as hour-minute, e.g.
14-40.
6.1.1.3 S̲t̲a̲r̲t̲/̲S̲t̲o̲p̲ ̲T̲i̲m̲e̲
The time when an action is commenced is written in
the start column; similarly, the time when the equipment
is returned to normal operation or when action is terminated
is written in the stop column.
Figure 6.1.1-1
LOGBOOK…86…1 …02… …02… …02… …02…
6.1.1.4 S̲y̲m̲p̲t̲o̲m̲
A brief description of the event is written here.
6.1.1.5 A̲c̲t̲i̲o̲n̲ ̲G̲r̲o̲u̲p̲
The Action Group Column divides the events into different
categories. The following groups are defined:
A: Errors
B: Preventive Maintenance
C: Verification of repairs from depot
D: Loading of new S/W
E: On-Job-Training
F: Equipment Expansion
G: Other access to the equipment
6.1.1.6 A̲c̲t̲i̲o̲n̲
A brief description of the actions performed is written
here.
6.1.1.7 I̲n̲i̲t̲i̲a̲l̲s̲
The originator must write his initials here.
6.2 F̲A̲I̲L̲U̲R̲E̲ ̲R̲E̲P̲O̲R̲T̲S̲
Whenever a failing item is identified and returned
to the next level of repair, a Failure Report must
be issued as identification. The failure report will
serve as a cover sheet for other enclosed documentation
and insure that all errors can be centrally registrated.
It should be noticed that it is important to fill in
the failure report accurately and detailed (if necessary,
with enclosures) as this may ease the troubleshooting
at the next level.
During the warranty phase of the equipment, a record
of all failure reports will be maintained by the manufacturer
(CRAS), but each site should keep a copy for information.
6.2.1 F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲ ̲F̲o̲r̲m̲
The Failure Report is shown in Figure 6.2.1-1 and the
instructions for filling in the report is outlined
in the below subparagraphs.
6.2.1.1 F̲a̲i̲l̲u̲r̲e̲ ̲R̲e̲p̲o̲r̲t̲ ̲N̲o̲.̲
Each site (and depot) has been provided an identification
No. which must be applied followed by a serial No.
Figure 6.2.1-1
FAILURE REPORT
6.2.1.2 I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
Sufficient information necessary for identification
of the failing item must be provided. In case a H/W
or a firmware error is reported, the following identification
must be completed:
- Name of failing item
- Type No.
- Serial No. (if any)
- Revision No. (if any)
In case a S/W error is reported, the following identification
should be completed as applicable:
- Name of failing item (package, module, procedure)
- Version No. (if any)
- Release No.
6.2.1.3 P̲h̲y̲s̲i̲c̲a̲l̲ ̲L̲o̲c̲a̲t̲i̲o̲n̲
Sufficient information for identification of the failing
item and its position must be provided.
This part is not completed in case of a S/W error.
6.2.1.4 T̲y̲p̲e̲ ̲o̲f̲ ̲E̲r̲r̲o̲r̲
The appropriate fields must be marked.
6.2.1.5 S̲i̲t̲e̲ ̲L̲e̲v̲e̲l̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The following information must be provided:
a) Site name (abbreviation)
b) Originator's initials
c) Date of completion of the failure report
6.2.1.6 R̲e̲p̲a̲i̲r̲ ̲T̲i̲m̲e̲
The following information should be provided:
a) Date of Failure
The Time-Of-Day (TOD) must be the same which appears
in the logbook. The date of failure is written
in case of the date is not the same as the date
of completion of the Failure Report above.
b) Repair Start
Fill-in the TOD when the repair was initiated.
c) Repair Stop
Fill-in the TOD when the repair was stopped.
d) Equipment Operation Restored
Indicate as appropriate.
e) Elapsed Time
If the equipment operation has been restored, this
field will indicate the time for which the equipment
was failing. Notice that this is not necessarily
indicated to the time spent on the repair of the
fault.
6.2.1.7 E̲r̲r̲o̲r̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
Provide a brief, but thorough description of the failure
indications. Support the descriptions with enclosure
where convenient. Also describe the means which remedied
the failure, if possible.
6.2.1.8 E̲n̲v̲i̲r̲o̲n̲m̲e̲n̲t̲a̲l̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲s̲
If the environmental conditions were normal at the
time of failure, it should be indicated in this field.
6.2.1.9 T̲y̲p̲e̲
Indicate the process which was in progress at the time
of failure. Tasks like:
- Retrieval of date (ROD)
- Preventive maintenance (PM)
- Test of repaired modules (TEST)
- On-Job-Training (OJT)
may be indicated in the "Other" field.
6.2.1.10 E̲n̲c̲l̲o̲s̲u̲r̲e̲
Mark as appropriate. Enclose as much information as
possible in order to ease faultfinding at the next
level.
6.3 F̲I̲E̲L̲D̲ ̲C̲H̲A̲N̲G̲E̲ ̲N̲O̲T̲I̲C̲E̲S̲ ̲(̲F̲C̲N̲)̲
6.3.1 G̲e̲n̲e̲r̲a̲l̲
Whenever a modification is necessary, a Field Change
Notice (FCN) will be issued and 2 copies will be provided
to SHAPE and 1 copy to each site affected.
The FCN will contain detailed information describing
the:
- Type of information
- Tools, Parts, and Time required
- Equipment to be modified
- Instructions for implementing the modifications
Where the FCN indicates use of materials, they will
be enclosed. If a modification neccessitates amendment
of documentation, new pages will be provided sufficient
to amend all affected documentation.
Generation of FCNs by CR will commence after the Site
Provisional Acceptance and take place during the H/W
or S/W warrnaty periods whichever is applicable.
6.3.2 R̲e̲g̲i̲s̲t̲r̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲C̲N̲s̲
A reference or Master List of all modifications will
be issued and concurrently updated. Herein the FCNs
are listed consecutively indicating the equipment modified
and the reason for modification.
6.3.3 D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲F̲C̲N̲s̲
The Field Change Notice Sheets shown overleaf are explained
by the following subparagraphs (1-10). Refer to Figures
6.4.3-1 and -2.
6.3.3.1 H̲e̲a̲d̲i̲n̲g̲
The FCNs are issued consecutively commencing with number
1. The number of pages included in the FCN in question
is indicated.
6.3.3.2 I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The part addressed by the FCN is identified by Type,
Parts No., Nato Stock No., if available, and description
as well as the next higher level are indicated.
6.3.3.3 P̲a̲r̲t̲s̲ ̲D̲i̲s̲p̲o̲s̲i̲t̲i̲o̲n̲
A checkmark indicates the disposition of parts, "N.A."
means "Not Applicable".
6.3.3.4 C̲l̲a̲s̲s̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The checkmark indicates the urgency by which the modification
must be executed. "Desireable" means earliest convenient
opportunity while "Mandatory" means immediately. "Mandatory"
classification is typically employed when the equipment
may malfunction without the modicifation or if the
operation of the system is endangered.
6.3.3.5 T̲y̲p̲e̲ ̲o̲f̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
This section is checked as appropriate. The three main
groups existing are:
- Rework (H/W change)
- Spares Change
- Software Change
6.3.3.6 R̲e̲l̲a̲t̲e̲d̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲
This section cross references related documents to
the FCN. Engineering Change Order (ECO) is the reference
No. for a CR in-house document, while the Failure Report
No. indicates that the FCN is originated by an error
occurred at a site or depot.
6.3.3.7 F̲i̲e̲l̲d̲ ̲C̲h̲a̲n̲g̲e̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲
The description includes a reason for action, that
is, a brief explanation of why that particular FCN
is necessary. It also describes the change in detail
or, if the space is insufficient, provides a summary
of the modification. It is always described as "Is"
or "Was".
6.3.3.8 A̲f̲f̲e̲c̲t̲e̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲
If a modification implies that the documentation is
revised, the applicable documents are listed with the
new revision level. Also reference documents are mentioned,
if any.
6.3.3.9 A̲p̲p̲r̲o̲v̲a̲l̲ ̲A̲u̲t̲h̲o̲r̲i̲t̲y̲
The author of the FCN must sign together with the approval
authorities and the RST which implemented the modification.
Upon completion, a signed copy of the front page of
the FCN must be returned to CR to indicate the status
of the equipment. The equipment is considered modified
upon receipt of this copy.
6.3.3.10 S̲u̲c̲c̲e̲e̲d̲i̲n̲g̲ ̲P̲a̲g̲e̲s̲
The succeeding pages provide the detailed information
about the modification. First the tools, parts, and
time required for the modification are indicated, mext
step-by-step instructions illustrated as "Is" and "Was",
if applicable.
6.4 C̲O̲N̲F̲I̲G̲U̲R̲A̲T̲I̲O̲N̲ ̲C̲O̲N̲T̲R̲O̲L̲
6.4.1 I̲n̲t̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
The objective of the PROTOCOL CONVERTER Configuration
Control procedures is to ensure configuration control
from fabrication and on. Thus, the procedures set forth
herein are derived from CRAS's Configuration Management
Plan QA/PLN/0005. The organization and methods are
based on the baseline principle and the three functional
areas of configuration managements:
- Identification
- Status Accounting
- Change Control
A unique identification of modules will contribute
to keep track of the individual modules. Therefore,
major modules will have a serial No. although it must
be expected that minor peripheral subassys and modules
are not equipped with serial numbers.
The Installation Manual contains a list of all modules
and their serial Nos. delivered to the site.
A status accounting in the form of revision levels
will contribute to keep track of Engineering Changes
and their implementation.
Change control is achieved through a Change Control
Board (CCB) which will be responsible for all changes
which are impeded onto the CAMPS and PROTOCOL CONVERTER
equipment. The main contributuion to field changes
will be Failure Reports generated at sites or depots,
but Engineering Change Proposals (ECP) may also be
suggested from other parties involved. As soon as an
ECP is approved, an Engineering Change Order (ECO)
will be generated. ECOs are issued under cover of a
Field Change Notice (FCN) to a focal point within CAMPS.
During the warranty, a completion information must
be returned to CRAS which will then in turn keep a
status accounting.
The following described the configuration control of
the individual modules within the CAMPS project.
6.4.2 C̲R̲A̲S̲ ̲M̲o̲d̲u̲l̲e̲s̲
a) Modules are identified as a product of Type Nos.,
Version Nos., Print Revisions, and Revision Levels.
E.g., a specific LTUX module may be identified
as
CRAS PART NO 4̲.̲0̲4̲1̲4̲1̲ 0̲8̲ SER. NO. 3̲2̲8̲ Rev 2̲ -
D̲
Family Name ̲ ̲ ̲ ̲ ̲
Version No. ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Module's Serial No. ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Print Version ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Latest Revision ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲
where
- The CRAS Part No., Version, and Serial NO.
are coherent identification which may be either
in form of a metal label or directly etched
into the PCB. In the latter case, the version
and serial No. are handwritten directly on
the PCB.
The family name and version No. identify a
module with respect for Form, Fit, and Function
(FFF). The FFF is established through a base-
line documentation.
Note that all modules employ product code 4.
- The serial No. refers to the production sequence.
- The print version No. is derived from the PCB
layout number. E.g. the LTUX module
4̲7̲4̲ A̲ - 2̲
PCB Type No. ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Side A of PCB ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
PCB Revision ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
The PCB revision will always remain the same
on both the A side and B side of the PCB.
- The Revision Level is a matrix which indicates
the ECO status of the board. E.g.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
A B C D E
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
means that Revisions A, B, and D have been
implemented while Revision C is N.A. for this
module. This implies that in the first issue
of the print version the matrix is left blank.
Updates per revision level will not affect
Form, Fit, and Function.
The Revision Matrix may be found either as
a metal label or etched into the PCB.
b) Firmware is identified by CRAS Part No. and Version
Code marked by a label on the top of the PROM.
Any changes to the PROM will be indicated by an
updated version code, but configuration control
is maintained at module level. "Make wash" changes
will be reflected as new revision levels while
other major changes will cause a new module version.
c) Diagrams and Parts Lists are issued as baseline
documentation. New revisions will be reflected
as "pen and ink" changes until the revisions are
incorporated in a new PCB version. At that time,
a new diagram and parts list will be issued.
d) Field Changes are issued as Field Change Notices.
Refer to section 6.3 for details.
Figure 6.4.3-1…01…Field Change Notice, Front Page
Figure 6.4.3-2…01…Field Change Notice, Subsequent Pages
6.4.3 P̲e̲r̲i̲p̲h̲e̲r̲a̲l̲s̲
Peripherals and modules in the PC program which are
not being manufactured by CRAS are generally controlled
by commercial standards. This means that configuration
control will be ensured by revision levels rather than
by serial Nos. A brief description of each individual
product is provided below.
6.4.3.1 V̲D̲U̲,̲ ̲D̲e̲l̲t̲a̲ ̲D̲a̲t̲a̲,̲ ̲M̲o̲d̲e̲l̲ ̲7̲2̲6̲0̲T̲C̲
a) Units are identified by Type and Serial Nos. found
at the rear of the unit.
b) Modules and subassemblies are identified by Type
Nos., Version Codes, and Revision Codes. E.g.,
the PMM module, Version 2, Revision 1 is provided
with the following identification code:
7̲8̲5̲ A̲3̲0̲2̲ 4̲0̲2̲ R̲e̲v̲.̲ ̲1̲
Group Code (module) ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Product Code ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Version Code ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Revision Code ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
c) Firmware is identified separately by labels on
the ICs. E.g.,
E̲3̲2̲7̲ U̲0̲3̲0̲
Product Code ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Version Code ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
d) Documentation
e) Field Changes are issued as Revision Notices. Upon
completion of the modification, the alphanumeric
revision code must be scratched out and replaced
by the next number in succession. Detailed information
will appear from the Revision Notice.
7 T̲O̲O̲L̲S̲ ̲A̲N̲D̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
This section contains a list of tools and test equipment
necessary for maintenance of the Protocol Converter
equipment, with reference to the CAMPS SITE MAINTENANCE
MANUAL, CPS/TCM/005 whenever appropriate, since the
PC is located next to the CAMPS equipment and that
the PC is maintained by CAMPS RST and Maintenance Technicians.
7.1 S̲T̲A̲N̲D̲A̲R̲D̲ ̲T̲O̲O̲L̲S̲ ̲A̲N̲D̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
No other standard tools and test equpment than those
listed in CPS/TCM/005 tables 7.2-1 and 7.3-1, respectively,
are needed for normal site level maintenance.
7.2 S̲P̲E̲C̲I̲A̲L̲ ̲T̲O̲O̲L̲S̲ ̲A̲N̲D̲ ̲T̲E̲S̲T̲ ̲E̲Q̲U̲I̲P̲M̲E̲N̲T̲
Table 7.4-1 of CPS/TCM/005 lists the special tools
and test equipment available on a CAMPS MAIN SITE.
Line Item No. 2-6 and No. 8 are extender boards and
loop-back adaptors used in conjunction with troubleshooting
on the CR equipment. These can all be used in the PC
equipment whenever troubleshooting beyond module replacement
on site level is to be exercised.
In the PC rack, a Dynatech Communication Breakout Test
Panel is mounted.
The breakout test panel is a completely self-contained
test panel designed to aid in the troubleshooting of
V24 interface.
Refer to Breakout Test Panel Instruction Manual for
the detailed description of operation.
