Siemens Saturn Iie Epabx General Description Manual

							SATURN IIE EPABX 
Maintenance and Troubleshooting 
RMTE - 
ACT 
LED 
(Green) 
TTY0 - 
Connector 
TTY1 - 
Connector 
Figure 2.03 Remote Access Unit/Ports Printed Circuit Board (RAUP)  
						

							I 
- 
SATURN IIE EPABX 
Maintenance and Troubleshooting 
2.08 Manual On-Line Diagnostic Tests. The SATURN IIE 
EPABX software includes a group of system diagnostic and 
apparatus diagnostic test programs which are used via the 
maintenance phone. Resulting visual and/or audible 
responses from these tests make it possible to verify correct 
operation or detect and isolate system and apparatus mal- 
functions. 
2.09 System Diagnostic Tests. The system diagnostic pro- 
grams permit calls and procedures to be initiated into and 
through the system to verify the correct operation of the call 
processing functions of the system equipment. 
In order to access the system diagnostic tests, the main- 
tenance diagnostic test access code (customer assignable 
via a CMU procedure) must first be dialed by using the main- 
tenance phone. Once the maintenance diagnostic test access 
code has been entered into the system, the following listed 
tests and procedures can be performed: 
a. 
l Tone Generator Test (Refer to Table 4.06) 
0 Outgoing Trunk Test (Refer to Table 4.08) 
l DTMF Receiver Test (Refer to Table 4.09) l Placing Circuits in Service (Refer to Table 4.10) 
0 Taking Circuits Out of Service (Refer to Table 4.11) 
Tone Generator Test. This test verifies each tone 
produced by the tone generator, located in the SMXTG 
PCB, either individually or in a circular sequence. This 
test is performed, either locally or remotely, by dialing 
test select code 1 from the maintenance phone. After 
the digit 1 is dialed, two more digits are dialed to select 
the individual tone to be tested or to initiate the auto- 
matic circular sequencing of all tones. If an individual 
tone is selected, the maintenance phone is connect- 
ed to that tone (through the MTS) as long as it remains 
off-hook. If the automatic circular sequence is initiat- 
ed, each tone is connected to the maintenance phone 
(through the MTS) for approximately 2 seconds with 
an intertone silence period of 0.25 to 0.5 second. The 
test automatically advances to the next tone in a cir- 
cular sequence as long as the maintenance phone re- 
mains off-hook. 
Outgoing Trunk Test. This test verifies the supervisory 
and transmission capabilities (in the outgoing direc- 
tion) of any individually selected outgoing or two-way 
trunk circuit on either a TMBM, TMBA-2, or TMBA-4 
PCB. The test also checks the connection path through 
the MTS. This test is performed either locally or remote- 
ly, via the maintenance phone by dialing the test select 
code 2. After the digit 2 is dialed, the trunk group num- 
ber (00 to 31) followed by the trunk number within the 
particular trunk group (00 to 99) is dialed. The main- 
tenance phone is then cut-through to the specific trunk 
circuit selected, seizing it in the outgoing direction. Sei- 
zure is confirmed when dial tone is returned to the 
maintenance phone. The transmiss’ion quality of the 
trunk can be checked by dialing the CO milliwatt test 
tone number or the test tone access code of the EPABX 
(if provided). The milliwatt test tone frequency and level 
(1004 Hz @ OdBm) may be measured by means of a 
Transmission Measuring Set (TMS). 
DTMF Receiver Test. This test verifies any individual- 
ly selected DTMF receiver circuit on a DTMF PCB. The 
test also checks the connection path through the d. 
e. A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
Memory Time Switch (MTS). This test is performed, 
either locally or remotely, via the maintenance phone 
by dialing test select code H. After the # is dialed, the 
Port Equipment Number (PEN) of the particular DTMF 
:eceiver circuit under test is dialed. The pushbuttons 
on the DTMF keypad of the maintenance phone are 
then depressed in a fixed sequence. If the telephone 
has a 12-button keypad, the buttons are depressed in 
the following sequence: 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, *, 
and #. If the telephone has a 16-button keypad, the 
buttons are depressed in this sequence: A, B, C, D, 
1, 2, 3, 4, 5, 6, 7, 0, 9, Oi *, and #. After depressing 
the pushbuttons in the applicable fixed sequence, a 
test tone (1004 Hz) is returned if the DTMF receiver cir- 
cuit under test recognized all the tones associated with 
the pushbuttons. If the pushbuttons are depressed in 
the wrong sequence or the DTMF receiver circuit un- 
der test failed to recognize a particular tone, intercept 
tone is returned. 
Placing Circuits In Service. This procedure allows 
maintenance personnel to place an assigned circuit 
in service from an out-of-service state. This procedure 
is performed, either locally or remotely, via the main- 
tenance phone by dialing test select code 7. After 7 
is dialed, the PEN of the particular circuit to be placed 
in service (in either an- SLMA-0, SLMA-S, SLA16, 
SLMD. PIMD. DTMF. TMBM. TMBA-2. TMBA-4. or 
TMIE PCB) is’dialed.‘Note that all circuiis on a pahic- 
ular PCB (with exception of the SL416 PCB) are placed 
in service by entering the digit 8 as the circuit location 
of the PEN (e.g., 0028 places all circuits in the basic 
shelf, designated as shelf 0, channel group 0, slot 2, 
in service). If all 16 circuits of an SLAl6 PCB are to 
be placed in service, they are placed in service eight 
circuits at a time. The first sight circuits for an SLA16 
(in the same shelf, channel group, and slot as above) 
are placed in service as described, i.e., by entering 
0028. The second eight circuits are placed in service 
by dialing 0038 (a 1 is added to the basic slot number 
to designate the second eight circuits on an SLAl6 
PCB). If the procedure fails, either due to entry of an 
invalid circuit number or because the slot number is 
unassigned, reorder tone is returned. Successful com- 
pletion of the procedure is indicated by the return of 
confirmation tone. 
Taking Circuits Out of Service. This procedure allows 
maintenance personnel to take an assigned circuit out 
of service from an in-service state. This procedure is 
performed, either locally or remotely, via the main- 
tenance phone by dialing test select code 8. After the 
digit 8 is dialed, the PEN of the particular circuit (in 
either an SLMA-0, SLMA-S, SLA16, SLMD, PIMD, 
DTMF, TMBM, TMBA-2, TMBA-4, or TMIE PCB) to be 
taken out of service is dialed. Note that all circuits on 
a particular PCB (with exception of the SLA16 PCB) 
are taken out of service by entering the digit 8 as the 
circuit location of the PEN (e.g., 0208) places all cir- 
cuits in the basic shelf (0), channel group 2, slot 0 out 
of service). If all 16 circuits of an SLA16 PCB are to 
be taken out of service, the procedure is performed 
eight circuits at a time. The first eight circuits for an 
.%A16 (in the same shelf, channel group, and slot num- 
ber as above) are taken out of service as described, 
i.e., by entering 0208 The second eight circuits are 
taken out of service by dialing 0218 (a 1 is added to 
2-7  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting 
I 
--. 
A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
the basic slot number to designate the second eight 
circuits on an SLA16 PCB). When this procedure is 
enabled, it allows existing calls on the circuits to be 
completed before being taken out of service. If the 
procedure fails, because the selected circuit is either 
invalid or unassigned, reorder tone is returned. Suc- 
cessful completion of the procedure is indicated by the 
return of confirmation tone after the circuit is taken out 
of service (i.e., after calls in progress are completed). 
In addition, maintenance personnel are not required 
to wait for confirmation tone before placing the main- 
tenance phone on-hook to take the circuit out of serv- 
ice. Once this procedure is enabled, it automatically 
takes the pariicular circuit out of service as each call 
is completed. 
2.10 Apparatus Diagnostic Tests. The apparatus diagnos- 
tic tests permit testing of the various types of telephones and 
consoles that may be interfaced with the SATURN IIE EPABX. 
These tests verify proper operation of Single Line Telephones, 
Siemens Digital Telephones (DYADs and JR-DYADs), and At- 
tendant Consoles connected to the EPABX. 
In order to test a SATURN apparatus, the craftsperson must 
enable the apparatus test program via the maintenance 
phone, by dialing the maintenance diagnostic test access 
code, followed by the test select code 3. Note that this proce- 
dure is not required if the apparatus test program has been 
permanently enabled as a SATURN System option. Once the 
apparatus test program is enabled, the following listed ap- 
paratus tests can be performed: 
0 Station Line Tests (Refer to Tables 4.12 and 4.13) 
l Attendant Console Test (Refer to Table 4.14) 
0 Siemens Digital Telephone - DYAD Button Test 
(Refer to Table 4.16) 
0 Siemens Digital Telephone - JR-DYAD Button Test 
(Refer to Table 4.17) 
l Siemens Digital Tetepnone - DYAD Display Test 
(Refer to Table 4.18) 
a. Station Line Tests. The following tests can be per- 
formed on a SATURN EPABX station instrument: 
1. Dial Pad Test. This test checks the transmission 
capabilities and DTMF keypad performance of any 
DTMF instrument. This test can only be enabled 
after dialing the apparatus diagnostic test select 
code 3 from the maintenance phone, if required, 
and the dial pad test access code (customer as- 
signed via a CMU procedure) from the station in- 
strument under test. After the dial pad test access 
code is dialed, recall dial tone is returned and the 
dial pad keys are depressed in a fixed sequence. 
If the telephone has a 1Bbutton keypad, the but- 
tons are depressed in the following sequence: 1, 
2, 3, 4, 5, 6, 7, 8, 9, 0, *, and #. If the telephone 
has a 16-button keypad, the buttons are depressed 
in this sequence: A, B, C, D, 1, 2, 3, 4, 5, 6, 7, 8, 
9, 0,. * and ft. 
As each key is depressed, data are sent from the 
instrument to the test program. If a data error or 
an incorrect sequence is detected, busy tone is 
returned. Successful completion of this test is in- 
dicated by the return of a test tone (1004Hz @ 
-16dBm). The transmission quality of the station can then be verified by measuring the test tone frequen- 
cy and level by using a TMS. 
2. Ringback Test. This test checks the supervisory 
and transmission capabilities of any station instru- 
ment (rotary dial, DTMF and Siemens Digital Tele- 
phone). This test can only be enabled after dialing 
the apparatus diagnostic test select code 3 from 
the maintenance phone, if required, and the ring- 
back test access code (customer assignable via a 
CMU procedure) from the station instrument un- 
der test. After the ringback tesi access code is di- 
aled, confirmation tone is returned, and the user 
places the station instrument on-hook. When the 
station instrument rings, its supervisory capabili- 
ties are verified. Upon answering the ringing (go- 
ing off-hook), a test tone (1004 Hz @ -16dBm) is 
applied to the station line. The transmission quali- 
ty of the station can then be verified by measuring 
the test tone frequency and level by using a TMS. 
b. Attendant Console Test. This test checks the data and 
speech highways to and from an attendant console, 
its LED indicators, display module, and audible alert- 
ing device. The test can only be enabled after dialing 
the apparatus diagnostic test select code 3 via the 
maintenance phone, if required, and the attendant con- 
sole test access code (customer assignable via CMU 
procedure) from the attendant console under test. Af- 
ter the attendant console test access code is dialed, 
the console keys are depressed in a fixed sequence. 
As each is depressed, data are sent from the console 
to the test program. If a data error occurs or an incor- 
rect sequence is depressed, busy tone is returned to 
the console. Display module and LED indications are 
provided to verify correct operation of the transmit and 
receive circuits of the console. Successful completion 
of this test is indicated by the returning of ringback tone 
to the console handset or headset and the sounding 
of an audible alerting device in the instrument. 
c. Siemens Digital Telephone - DYAD Button Test. This 
test checks the signaling highways to and from a DYAD 
Telephone, its LED indicators, and audible alerting 
device. The test can only be enabled after dialing the 
apparatus diagnostic test select code 3 via the main- 
tenance phone, if required, and the Siemens Digital 
Telephone button test access code (customer assiq- 
nabte via a CMU procedure) from theDYAD Telephole 
under test. After the Siemens Diaital Telephone but- 
ton test access code is dialed, the DYAD’Telephone 
keypad and feature buttons are depressed in a fixed 
sequence. As each button is depressed, data are sent 
from the DYAD Telephone to the test program. If a data 
error or an incorrect sequence is detected, busy tone 
is returned to the DYAD Telephone. LED indications are 
provided to verify correct operation of the transmit and 
receive circuits of the DYAD Telephone. Successful 
completion of the test is indicated by the returning of 
ringback tone to the DYAD Telephone handset and the 
sounding of an audible alerting device in the telephone. 
d. Siemens Digital Telephone - JR-DYAD Button Test. 
This test checks the signaling highways to and from 
a JR-DYAD Telephone, its LED indicators, and audible 
alerting device. The test is very similar to that for the 
DYAD Telephone described above with the exception 
2-8  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting A30808-X5130-DllO-l-6920 
Issue 1, May 1986 
that the operation of certain buttons (and 
SuCCeSSful test completion) is indicated at the end of the test by 
the return of ringback tone and actuation of the audi- 
ble alerting device in the JR-DYAD Telephone. 
e. Siemens Digital Telephone - DYAD Display Test. This 
test checks the signalinghighways to and from a DYAD 
Telephone, its display module, and audible alerting 
device. The DYAD Telephone display test can only be 
enabled after dialing the apparatus diagnostic test 
select code 3 via the maintenance phone, if required, 
and the Siemens Digital Telephone display test access 
code (customer assignable via a CMU procedure) from 
the DYAD Telephone under test. After the Siemens Dig- 
ital Telephone display test access code is dialed, the 
DYAD Telephone alphanumeric display and its address 
signaling scheme are tested. These tests consist of 
shifting the entire alphanumeric character set through 
each character position on the display module. Suc- 
cessful completion of the test is indicated by the return- 
ing of ringback tone to the DYAD Telephone handset 
and the sounding of an audible alerting device in the 
DYAD Telephone. The pass/fail status of the test is 
based on observation by maintenance personnel of the 
characters displayed. 
2.11 Automatic On-Line Diagnostic Testing and Report- 
ing. The SATURN EPABX System is provided with software 
self-test routines and audit test routines which check for 
failures occurring in the system. When a failure is detected, 
pertinent data regarding the failure is recorded in an area of 
memory called “Failure History” and the appropriate major 
or minor alarm is enabled. Recovery programs are automati- 
cally executed as necessary on the failing equipment. The 
failure history memory can record 32 system failures (error 
messages) along with the identity of the failing equipment and 
the date and time of occurrence for each failure. When the 
failure history memory is full, new failures push-off the oldest 
failure of the failure history memory. The MIN ALM key on 
the attendant console is used to display the failures record- 
ed in the failure history memory. The failure history memory 
can also.be accessed from a local or remote service terminal. 
2.12 Self-Test Routines. The SATURN EPABX is provided 
with software self-test routines which verify that certain call 
processing operations, initiated by the main controller have 
been successfully completed by the peripheral circuits. If a 
call processing error occurs, the error(s) is recorded in the 
failure history memory and the appropriate major or. minor 
alarm is enabled. Recovery programs are automatically ex- 
ecuted as necessary on the faulty equipment. 
a. Connect Test. When a trunk is seized outgoing, a 
3-second (nominal) timer is set. If the CO or distant 
equipment does not acknowledge the seizure (e.g., 
ground return on tip lead, loop current, dial tone de- 
tection, or wink-start signal) before the timer expires, 
a connect error message is recorded in the failure his- 
tory memory and the minor alarm indicators are light- 
ed. An attempt is made to reroute the call over another 
trunk. 
b. Disconnect Test. When a trunk is released by the 
SATURN EPABX. a 20second (nominal) timer is set. 
If the CO does not release the trunk (e.g., ground re- 
moved from tip lead, open-loop condition on DID trunk 
or E lead) before the timer expires, a disconnect error message is recorded in the failure history memory and 
the minor alarm indicators are lighted. The trunk is left 
in the idle off-hook state (not disconnected, i.e., it is 
usable). 
c. Fuse Alarm Test. W’henever a fuse on the PSU front 
panel fails, a fuse failure message is recorded in the 
failure history memory and the minor alarm indicators 
are lighted. The SATURN IIE System continues to 
process calls normally for the circuits still reporting 
events. If a fuse failure occurs affecting a major por- 
tion of the system (e.g., common equipment), the major 
alarm indicators are lighted by virtue of other failures 
that will result from the blown fuse. 
d. Input/Output Processor Tests. The CIOP and RAUP 
provide return codes for each command to indicate 
whether or not the requested operation was success- 
ful. If the return code indicates an error or the CIOP 
or RAUP detects an internal failure, an error message 
is recorded in the failure history memory and the minor 
alarm indicators are lighted. If the CIOP detects an er- 
ror that prevents the initialization of the system when 
an initialization is required, the major alarm indicators 
are lighted. 
e. LTU Clock Test. Hardware monitors built into the Sig- 
nal Multiplexernone Generator (SMXTG) PCB are used 
to detect loss of principal clock, clock synchronization, 
or ring synchronization. If a failure is detected, an LTU 
Clock error message is recorded in the failure history 
memory and the minor alarm indicators are lighted. 
The location of the failure is indicated’ in the error 
message. 
f. Mainbus Timeout Test. The system watchdog timer is 
set each time the mainbus receives a command. If the 
timer expires before an acknowledgement is returned, 
a mainbus timeout error message is recorded in the 
failure history memory and the minor alarm indicators 
are lighted. 
g. Memory Parity Test. If a word is addressed that has 
incorrect parity, the parity detector on the addressed 
memory module generates an interrupt. A memory par- 
ity error message is recorded in the failure history 
memory and the minor alarm indicators are lighted. 
h. Memory Protect Test. If a write is attempted to a word 
in write protected memory, the write protect detector 
on the addressed memory module generates an inter- 
rupt. A memory protect error message is recorded in 
the failure history memory and the minor alarm indi- 
cators are lighted. 
i. Memory Support Test. A voltage level detector circuit 
provides a software testable signal that indicates when 
the memory support battery voltage is below an ac- 
ceptable voltage level. This signal is sampled once per 
hour by software. If the software testable signal indi- 
cates that the battery is low or disconnected, a memory 
support failure message is recorded in the failure his- 
tory memory and the minor alarm indicators are lighted. 
j. PIMD or SLMD Synchronization Test. When a PIMD 
PC6 loses synchronization with an attendant console 
or an SLMD PCB loses synchronization with an SDT 
2-o  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting 
or DCI, a PIMD error message is recorded in the failure 
history memory and the minor alarm indicators are 
lighted. 
k. Presence Alarm Test. The scan data returned for each 
port circuit contains a presence bit. If the presence bit 
goes inactive for 3 seconds or changes state (active/in- 
active) six times in 3 seconds, a presence alarm mes- 
sage is recorded in the failure history memory and the 
minor alarm indicators are lighted. The presence alarm 
is not generated for ports marked as out-of-service. 
I. SMXTG Clock Test. When the SMXTG 1 kHz clock fails, 
an SMXTG clock failure message is recorded in the 
failure history memory and the major alarm indicators 
are lighted. 
m. Software Loop Test. When a software loop error exists, 
a software loop error message is recorded in the failure 
history memory and the minor alarm indicators are 
lighted. If the number of errors is excessive, the major 
alarm indicators are lighted. 
n. Software Trap Test. When an event occurs for a given 
circuit type, the state/event table for that circuit type 
is accessed to determine what software action is to be 
taken in response to the event. If the event is illogical 
in regard to the state of the circuit, a software trap er- 
ror message is recorded in the failure history memory 
and the minor alarm indicators are lighted. 
2.13 Audit Routines. The SATURN IIE EPABX software in- 
cludes a repertoire of audit routines which are executed dur, 
ing processor idle time. These routines provide automatic 
testing of system equipment. Each audit routine is designed 
to be individually enabled (activated) or disabled (inactivat- 
ed) from the automatic routining sequence. This enable/dis- 
able capability is only accessible by maintenance personnel 
via a service terminal. When an auditing routine is enabled, 
detected failures are recorded in the failure history memory 
and the appropriate major or minor alarm is enabled. All 
failures are identified by the AUDIT error message (refer to 
Table 4.02). Recovery programs are automatically executed 
as necessary on faulty equipment. Additionally, each audit 
routine is designed to be executed on demand by main- 
tenance personnel via a local or remote service terminal. Im- 
mediate results (reasonable execution time considered) of 
pass or fail conditions are provided upon completion of each 
audit routine. The failure indication can be displayed by ac- 
cessing the failure history memory. The following listed audit 
programs are described in subsequent paragraphs. 
l Memory Parity Audit Test l Memory Content Audit Test l Input/Output Loop-Around Audit Test 
0 Speech Highway Audit Test 
* DTMF Receiver/Tone Generator Audit Test 
l MTS Memory Control Audit Test l Digital Apparatus Audit Test l Trunk Activity Audit Test 
a. Memory Parity Audit Test. The memory parity audit test 
checks each memory address for correct parity of its 
contents. If a parity error is detected, the error is record- 
ed in the failure history memory, the MINOR alarm in- 
dicator on the PSU is lit, and recovery is automatically 
attempted. This audit routine is intended to be used b. 
C. 
d. 
e. A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
by maintenance personnel as a demand-executed au- 
dit routine only to be run when memory is first installed 
or suspected faulty. This routine should normally be 
disabled from automatically running on an in-service 
system, since it may unnecessarily disrupt service if 
it detects ah error in a normally unused portion of the 
memory. The standard system data base has this au- 
dit routine disabled. 
Memory Content Audit Test. Verifies the check sum of 
control memory areas. If a conflict of data is detected, 
the error is recorded in the failure history memory, the 
MINOR alarm indicator on the PSU is lit, and recov- 
ery is automatically attempted. 
Input/Output Loop-Around Audit Test. The input/output 
loop-around audit test provides verification of the in- 
put/output interface circuits for the equipped CIOP and 
RAUP PCBs. This audit routine checks the comolete 
l/O interface of each PCB. This audit routine is not in- 
tended to provide a test of the peripheral equipment 
accessing the interfaces. If the loop-around test fails, 
the failure is recorded in the failure history memory and 
the MINOR alarm indicator on the PSU is lit. 
Speech Highway Audit Test. The speech highway au- 
dit test checks the individual port’s codec operation, 
speech highway, and MTS switching elements for cor- 
rect data/voice transfer. This audit routine transmits a 
DTMF tone to a selected idle line or trunk port in the 
loopback mode. It then receives the results via a DTMF 
receiver. If the DTMF tone is not properly received, the 
failure is recorded in the failure history memory and 
the MINOR alarm indicator on the PSU is lit. 
DTMF Receivernone Generator Audit Test. The DTMF 
generator/receiver audit test checks the tone genera- 
tor’s DTMF outputs and each equipped DTMF receiver 
in the system by connecting each DTMF tone output 
from the tone generator to the input of the DTMF 
receiver. The DTMF receiver is then scanned for proper 
decodinq of the tones. Each idle DTMF receiver is cv- 
, 
cled through all DTMF tones. Detected failures are 
recorded in the failure history memory. If an individual 
DTMF receiver is faulty, it is placed in an out-of-service 
state and the MINOR alarm indicator on the PSU is 
lit. If the tone generator is faulty, the MAJOR alarm in- 
dicator on the PSU is lit. 
MTS Memory Control Audit Test. The MTS memory 
control audit test provides verification of the MTS 
memory on the MCA printed circuit board. A series of 
values are written to and then read from each MTS 
memory location. If a mismatch occurs between the 
data written and the data read, the failure is recorded 
in the failure history memory and the MINOR alarm 
indicator on the PSU is lit. 
Digital Apparatus Audit Test. The digital apparatus audit 
test is used to verify the operation of data devices 
(DCls) connected to the system and used either as ter- 
minal controllers or for pooled modems. When the test 
is initiated, the system maintenance channel is 
checked first. If the maintenance channel is function- 
al, then an idle data device is looped-back (at the 
device) and a fixed data pattern is written to the main- 
tenance channel. After a short delay, the data is read 
2-10  
						

							I 
_-. 
SATURN IIE EPABX 
Maintenance and Troubleshooting 
back and, if it matches the original data, the data 
device is considered to be fully operational and other 
idle data devices are located for testing. If the first loop- 
back test fails, the associated SLMD is looped-back 
and the data pattern test is repeated. If the second test 
fails, an SLMD fault is suspected; if the second test 
passes, a DCI failure or wiring fault is suspected. When 
either or both tests fail, the PEN of the failed device 
and the test(s) failed is recorded in the failure history 
and the MINOR alarm indicator on the PSU is lit. 
h. Trunk Activity Audit Test. The trunk activity audit test 
checks each assigned trunk in any prerequested trunk 
group for possible abnormal activity. Activity is moni- 
tored by maintaining attempts event and occupancy 
usage counts for each trunk in the trunk group. Sig- 
naling problems will be indicated by seizures of either 
excessively short or extremely long duration, as evi- 
denced by the events and usage counts. One-way in- 
coming trunks experiencing signaling problems may 
remain idle for long periods when traffic density is high. 
2.14 Alarm Indicators and Classification. Major alarm 
(MAJOR) and Minor alarm (MINOR) indicators are provided 
in the ALARMS indicator area of the PSU front panel and at- 
tendant console. These alarm indicators provide an indica- 
tion of one of three possible system alarm conditions: 
a. No Alarm (MAJOR and MINOR alarm indicators dark) 
- No detectable failures are present in the system. 
b. Minor Alarm (MINOR.alarm indicator lighted) - At least 
one of the automatic on-line diagnostic tests has de- 
tected a failure in the system and maintenance per- 
sonnel attention is required when possible. 
c. Major Alarm (MAJOR alarm indicator lighted) - The A30808-X5130-DllO-l-6920 
Issue 1. May 1986 
system is in a non-operative state and the system’s 
failure transfer relays are active, if provided. Immedi- 
ate maintenance personnel attention is required. Note 
that certain major alarm conditions could prevent the 
major alarm (MAJ ALM) indicator on the attendant con- 
sole from being lighted. Examples are primary power 
failure. console power failure, and -48PS failure. 
2.15 Power Distribution and Failures. Each SATURN IIE 
EPABX Basic Cabinet is provided with the following power- 
related assemblies and modules (refer to Figures 2.04 and 
2.05): 
0 
. 
0 Power System Unit (PSU) containing: 
Circuit Breaker (and Fuse) Panel Basic Power Sup- 
DIV Board Rina Generator IRGEN) Module Control 
Logic Board Memory Support Module (MSM), op- 
tional 
-48 Vdc Power Supply (-48PSO). 
Line/Trunk Unit Power Supply (LTUPS), optional. 
When the Basic Cabinet is equipped with an LTU 
shelf, an LTUPS is required in the LTU shelf. 
If an Expansion Cabinet is added to the Basic Cabinet, the 
following power supplies are added (refer to Figures 2.06 and 
2.07): 
. 
-48 Vdc Power.Supply (-48PSl). A -48 Vdc Power 
Supply is added in the space adjacent to -48PS0 
in the Basic Cabinet. 
0 Line/Trunk Unit Power Supply(s) (LTUPS). An 
LTUPS is required in each LTU shelf in the Expan- 
sion Cabinet. 
2-11  
						

							SATURN IIE EPABX A30808-X5130-DllO-1-5920 
Maintenance and Troubleshooting Issue 1, May 1986 
. 
Q 
: : 
LTU 
PS 
0 
It. -00~1~-2-~3~-4---7r5~r6~ 
-COMMON EOUIPMENT- 
LTU 
Shelf 
Basic 
Shelf 
Figure 2.04 SATURN IIE EPABX Basic Cabinet (Front View)  
						

							I - 
SATURN IIE EPABX 
Maintenance and Troubleshooting A30808-X5130-DllO-1-6920 
Issue 1, May 1986 
LTU 
Shelf 1 
Basic 
Shelf 
A5?56-I-4/21186 Figure 2.05 SATURN IIE EPABX Basic Cabinet (Rear View) 
2-13  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
[df SATIIRN II F 
P, c3 
LTU LTU Shelf 3 
PS2 
0 
0 B 
c? Q 
LTU 
PSI LTU Shelf 2 
LTU Shelf 1 
11 Basic Shelf 
1 
I 1 i 
Expansion 
Cabinet 
’ 
Basic 
Cabinet 
Figure 2.06 SATURN IIE EPABX Basic and Expansion Cabinets (Front View) 
.  
						

							1 
- 
SATURN IIE EPABX 
A30808-X5130-DllO-l-8920 
Maintenance and Troubleshooting 
Issue 1. May 1986 
LTU 
Shelf 3 
LTU 
Shelf 2 
LTU 
Shelf 1 
Basic 
Shelf 
Figure 2.07 SATURN IIE EPABX Basic and Expansion Cabinets (Rear View) 
2-15