Siemens Saturn Iie Epabx General Description Manual

							A30806X5130-DllO-l-8920 
Issue 1, May 1986 
Table 4.02 Alarm Reporting and Processing (Continued) 
ALARM TYPE 
(1) If eeee = 1405 CORRECTIVE ACTION 
Correctable memory parity error on a MEM3 or MEM4 PCB. 
A parity error was detected and corrected on the MEM3 or 
MEM4 PCB as identified by the slot number in this error 
message. If the problem occurs more than once in a single 
week, the identified memory PCB should be replaced. 
NOTE: The slot number identity of the faulty memory PCB 
is provided in the following error message: 
“MEM PAR 1405(pp) STAT=aaaa 
ADDR=bbbb MEMc mm/dd hh:mm” 
c = slot number identity of of faulty memory PCB. 
(2) If eeee = 1410 Uncorrectable memory parity error in control memory on a 
MEM3 or MEM4 PCB. 
An uncorrectable parity error was signaled by the MEM3 
or MEM4 PCB as identified by the slot number in this error 
message. If the problem occurs more than once in a single 
month, the identified memory PCB should be replaced. An 
automatic system reload is triggered. 
NOTE: The slot number identity of the faulty memory PCB 
is provided in the following error message: 
“MEM PAR 141O(pp) STAT=aaaa 
ADDR=bbbb MEMc mm/dd hh:mm” 
c = slot number identity of faulty memory PCB. 
(3) If eeee = 1411 Uncorrectable memory parity error in dynamic memory on 
a MEM3 or MEM4 PCB. 
An uncorrectable parity error was signaled by the MEM3 
or MEM4 PCB as identified by the slot number in this error 
message. If the problem occurs more than once in a single 
month, the identified memory PCB should be replaced. A 
hard restart is triggered. 
NOTE: The slot number identity of the faulty memory PCB 
is provided in the following error message: 
“MEM PAR 1411(pp) STAT=aaaa 
ADDR=bbbb MEMc mm/dd hh:mm” 
c = slot number identity of of faulty memory PCB. 
(4) If eeee = 1414 Correctable memory parity error on a memory PCB. 
The correctable error threshold for this memory PCB has 
been reached, no further correctable error will be reported. 
Immediately replace the identified memory PCB. 
NOTE: The identity of the memory PCB is provided as indi- 
cated in the error message shown for error number 1405. 
* = For Siemens field service use only. 
I 
- 
SATURN IIE EPABX 
Maintenance and Troubleshooting 
4-9  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting 
Table 4.02 Alarm Reporting and Processing (Continued) 
ALARM TYPE CORRECTIVE ACTION 
i. MEM PROT (pp) LOC=aaaa:bbbb The main processor attempted to write into protected 
ADDR=cccc:dddd mm/dd hh:mm memory. 
(PP)’ = ID of process If problem is repetitive, consult Siemens field service 
aaaa: representative. 
bbbb’ = error information 
cccc: 
dddd’ = error information 
mmldd = date of error 
hh:mm = time of error 
NOTE: For reference only, the error number for this 
error message is 1406. 
i. MEMORY SUPPORT FAILURE (18) The automatic equipment test routines have detected a 
mm/dd hh:mm failure of the system memory support hardware. 
(18)’ = ID of process The error indicates a missing, failed or discharged MSM 
mm/dd = date of error memory support battery-in the PSU. 
hh:mm = time of error 
NOTE: For reference only, the error number for this 
error message is 1426. 
k. PIMD OVERCUR (pp) PEN=wxyz PIMD or SLMD overcurrent error. 
mmldd hh:mm 
The identified digital device has drawn too much current 
(PP)’ = ID of process from the associated PIMD or SLMD PCB causing a device 
wxyz = PEN shutdown. The device has been taken out-of-service and 
mm/dd = date of error must be manually placed back in-service. Possible trouble 
hh:mm = time of error sources are: 
NOTE: For reference only, the error number for this (1) Faulty console (if PIMD); faulty SDT or DCI (if SLMD). 
error message is 143.5. 
(2) Faulty cabling between console and PIMD PCB; faulty 
cabling between SDT or DCI and SLMD PCB. 
(3) Faulty PIMD or SLMD PCB. 
(4) Possible short on line. 
NOTE: The affected digital device is identified by the PEN 
provided in the error message shown above. 
I. PIMD ERR eeee(07) PEN=wxyz 
mm/dd hh:mm 
eeee = error number 
(07)’ = ID of process 
wxyz = PEN 
dd/mm = date of error 
hh:mm = time of error 
(1) If eeee = 1464 PIMD or SLMD failure. 
An excessive number of PIMD or SLMD error events (PIMD 
or SLMD failure or loss of synchronization) were detected 
on the identified port. The device has been taken out-of- 
service and must be manually placed back in-service. 
* = For Siemens field service use only. 
4-10  
						

							SATURN IIE EPABX A30808-X5130-DllO-l-8920 
Maintenance and Troubleshooting Issue 1, May 1986 
Table 4.02 Alarm Reportinq and Processinq (Continued) 
- . 
ALARM TYPE CORRECTIVE ACTION 
NOTE: This error also occurs when a PIMD or SLMD PCB 
is removed without first taking it out-of-service. 
Possible trouble sources: 
(1) Faulty console, SDT, or DCI. 
(2) Faulty cabling 
between apparatus and PIMD or SLMD 
PCB. 
(3) Faulty PIMD or SLMD PCB. 
(4) Faulty SMXTG PCB if PEN indicates Basic Shelf; faulty 
LTUC PCB (first), then faulty SMXTG (second) if PEN in- 
dicates LTU Shelf. 
(2) If eeee = 1465 PIMD or SLMD response error. 
The identified port has repeatedly failed to respond to restart 
commands issued by the common control. The digital device 
has been taken out-of-service and must be manually placed 
back in-service. 
Possible trouble sources: 
(1) Faulty console, SDT, or DCI. 
(2) Faulty cabling between apparatus and PIMD or SLMD 
PCB. 
(3) Faulty PIMD or SLMD PCB. 
(4) Faulty SMXTG PCB if PEN indicates Basic Shelf: faulty 
LTUC PCB (first), then faulty SMXTG (second) if PEN in- 
dicates LTU Shelf. 
(5) Digital device not connected. 
m. PRESENCE (pp) PEN=wxyz 
mm/dd hh:mm 
(PP)’ = ID of process 
wxyz = PEN number 
mmldd = date of error 
hh:mm = time of error 
NOTE: For reference only, the error number for this 
error message is 1408. The central processor has detected the removal of a sub- 
scriber line module (SLMA-0, SLMA-S, or .%A16 PCB). Each 
defined line circuit on the PCB should generate a presence 
error when the PCB is removed. 
A large number of unexplained presence errors may indj- 
cate the following: 
(1) A blown BASIC or LTU shelf fuse on the PSU front 
panel. 
(2) A faulty LTUPS or a fault in the PSU. 
(3) A faulty LTUC PCB on the affected shelf. 
(4) A faulty SMXTG PCB. 
Intermittent unexplained presence errors may indicate any 
of the previous mentioned problems, or a failure of the power 
supply ring synchronization circuitry contained in the PSU. 
* = For Siemens field service use only. 
4-11  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting A30808-X5130-DllO-l-B920 
Issue 1, May 1986 
Table 4.02 Alarm Reporting and Processing (Continued) 
r ALARM TYPE CORRECTIVE ACTION 
1. RELOAD : MANUAL RESET (pp) A system reload,-initiated via the CIOP Reset pushbutton, 
mm/dd hh:mm has been completed. 
(PP)’ = ID of process 
mm/dd = date of error This message is followed by a ‘S&V TRAP” message in- 
hh:mm = time of error dicating the type of recovery (i.e., a reload). 
NOTE: For reference only, the error number for this 
error message is 1488. 
C 1. RELOAD : MEM4 REFRESH A hardware fault on the MEM4 PCB caused a loss of 
FAILURE (pp) mm/dd hh:mm memory refresh. An automatic system reload has been in- 
itiated and completed as a result of the fault. 
(PP)’ = ID of process 
mm/dd = date of error 
hh:mm = time of error This message is followed by a “S/W TRAP” message in- 
dicating the type of recovery (i.e., a reload). 
NOTE: For reference only, the error number for this 
error message is 1485. If the problem is repetitive, replace the MEM4 PCB. 
F 1. RELOAD : RECOVERY ACTION Software has initiated and completed a system reload either 
(PP) mm/dd hh:mm automatically due to excessive restarts or manually through 
(PP)’ = ID of process a RECOVERY CMU Procedure (BEG RECOVERY). 
mm/dd = date of error 
hh:mm = time of error This message is followed by a “S/W TRAP” message in- 
dicating the type of recovery (i.e., a reload). 
C 
NOTE: For reference only, the error number for this 
error message is 1486. If system reload due to excessive restarts is repetitive, con- 
sult Siemens field service representative. 
1. RELOAD : POWER FAILURE (pp) A system reload has been initiated and completed due to 
mm/dd hh:mm a primary power loss and loss of +SVdc power input to the 
memory PCBs. 
(PP)’ = ID of process 
mm/dd = date of error 
hh:mm = time of error (1) In systems equipped with an MSM, the capacity of the 
MSM battery to provide power to the memory PCBs was ex- 
NOTE: For reference only, the error number for this 
error message is 1489. ceeded or an MSM battery failure has occurred. The MSM 
battery will be recharged to capacity during normal system 
operation. If a battery failure is suspected, perform the MSM 
Test provided in Table 4.04. 
(2) In systems without an MSM, a primary power failure has 
occurred and resulted in the loss of +5Vdc input to the 
memory PCBs. Restoration of primary power returns the sys- 
tem to operation. 
The message shown above is followed by a “S/w TRAP” 
message indicating the type of recovery (i.e., a reload). 
If system reloads due to excessive power failures are repeti- 
tive, consult Siemens field service representative. 
r. RELOAD : WATCHDOG TIMING 
FAILURE (pp) mm/dd hh:mm CIOP watchdog timing logic has initiated and completed a SF- 
tern reload due to excessive watchdog timeouts or because 
(PP)’ = ID of process 
mm/dd = date of error 
hh:mm = time of error software failed to acknowledge a watchdog timeout interrupt. 
This message is followed by a “S/W TRAP” message in- 
dicating the type of recovery (i.e., a reload). 
NOTE: For reference only, the error number for this If problem is repetitive, replace the CIOP PCB. If problem 
error message is 1487. persists, consult Siemens field service representative. 
* = For Siemens field service use only. 
4-12 .  
						

							SATURN IIE EPABX A30808-X5130-DllO-l-8920 
Maintenance and Troubleshooting Issue 1, May 1986 
Table 4.02 Alarm Reporting and Processing (Continued) 
ALARM TYPE CORRECTIVE ACTION 
s. RESTART : POWER FAILURE (pp) In an MSM equipped system, a hard restart has been in- 
mm/dd hh:mm itiated and completed due to a momentary power loss. The 
rn!ZZ = ID of process MSM maintained the +SVdc power input to the memory 
= date of error PCBS. 
hh:mm = time of error 
This message is followed by a “S/W TRAP” message in- 
NOTE: For reference only, the error number for this dicating the type of recovery (i.e., a hard restart). 
error message is 1470. 
If problem is repetitive, check lbcal power source and con- 
sult Siemens field service representative. 
t. SMXTG CLOCK FAILURE (pp) The automatic equipment test routines have detected a pos- 
mmldd hh:mm sible failure of the SMXTG master system clock. 
(PP)’ = ID of process A system reload is automatically initiated. 
mm/dd = date of error 
hh:mm = time of error If the master clock has actually experienced a hard failure, 
the failed common control equipment will be unable to 
NOTE: For reference only, the error number for this process telephone calls until it is corrected. 
error message is 1425. 
If problem is intermittent, the system reload may clear the 
intermittent condition. 
If a hard failure (or repetitive intermittent failures) occurs, 
the following are the possible trouble sources: 
(1) Faulty SMXTG PCB. 
(2j Faulty clap Pm. 
u. S/W LOOP ERROR x (pp) A system watchdog detected a possible software loop er- 
LOC=aaaa:bbbb mm/dd hh:mm ror. If problem is repetitive, consult Siemens field service 
representative. 
X = watchdog identity; 
(PP)’ = ID of process NOTE: The watchdog identity (x) is provided in the follow- 
aaaa: ing list: 
bbbb” = error information 
mmtdd = date of error 
1 = foreground (interrupt) watchdog 
hh:mm = time of error 
NOTE: For reference only, the error number for this 
error message is 1407. 2 = background (idle time) watchdog 
V. S/W TRAP eeee (pp) aaaa bbbb 
cccc dddd mmldd hh:mm 
eeee = error number 
(PP)’ = ID of process 
aaaa’ = error information 
bbbb’ = error information 
cccc* = error information 
dddd’ = error information 
mm/dd = date of error 
hh:mm = time of error 
(1) If eeee = 1039 Service terminal timeout error. 
A service terminal operation did not complete in the allo- 
cated time period. 
If the problem is repetitive, replace the CIOP PCB. 
* = For Siemens field service use only  
						

							SATURN IIE EPABX 
Maintenance and Troubleshooting 
Table 4.02 Alarm Reporting and Processing (Continued) 
ALARM TYPE 
(2) If eeee = 1300 CORRECTIVE ACTION 
System restart marker. 
This error entry logs the date and time whenkver the system 
goes through a system restart (recovery). Analyze the errors 
preceding this error to determine the cause of the restart. 
NOTE: The type of restart is identified in the following error 
message: 
“SNV TRAP 1300 (05) aaaa bbbb 
cccc dddd mmldd hh:mm” 
aaaa = type of restart, as follows: 
If aaaa = 0000; soft restart (calls preserved) 
If aaaa = 0001; hard restart (calls dropped) 
If aaaa = 0002; system reload from disk (calls dropped) 
(3) If eeee = 1403 Spurious memory interrupt. 
A memory error interrupt occurred, but the main processor 
could not identify the memory PCB which signaled the er- 
ror. If the error is repetitive, systematically replace each of 
the memory (MEMS and MEM4) PCBs until the faulty PCB 
is located. 
(4) If eeee = 1404 Invalid memory interrupt. 
A memory error interrupt occurred, but the memory PCB 
which generated the error cannot correctly identify the er- 
ror type. If the error is repetitive, replace the faulty memory 
(MEMB or MEM4) PCB. 
NOTE: Slot identification of the faulty memory PCB loca- 
tion (in the COMMON EQUIPMENT section of the Basic 
Shelf) is indicated in the error message below: 
“SNV TRAP 1404 (pp) aaaa 0000 
0000 0000 mm/dd hh:mm” 
aaaa = Memory slot identification number 
aaaa SLOT NAME 
---I-- 0000 MEMO 
0001 MEMl 
0002 
l MEM2 
0003 l MEM3 
l Not currently used. 
(5) If eeee = 1409 System clock failure. 
System software has detected a possible master clock 
failure, resulting in a loss of clock interrupts. 
A system reload is automatically initiated. 
If the master clock has actually experienced a hard failure, 
the failed common control equipment will be unable to 
process telephone calls until it is corrected. 
4-14  
						

							I 
- 
SATURN IIE EPABX 
Maintenance and Troubleshoohng 
Table 4 rXJ Alarm Reoortino and Processino (Continued) 
A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
_____ ..__ _.._.... .._r _..... ~ -..- ----- . .._ ,-- ---, 
ALARM TYPE CORRECTIVE ACTION 
If the prpbtem is intermittent, the system reload may clear 
the intermittent condition. 
If a hard failure (or repet&e intermittent failures) occurs, 
possible sources of the trouble are: 
(1) Faulty SMXTG PCB. 
.  (2) Faulty CIOP PCB. 
(6) If eeee = 1444 Disk write error during data base save operation. 
A disk error was detected during a data base save opera- 
tion (via CMU procedure SAVE CUSTDATA). The disk save 
operation was aborted and the contents of the disk are now 
questionable. This error stack entry is accompanied by an 
immediate error message to craft personnel who attempt- 
ed the save operation. 
Craft personnel should reattempt the save operation until 
successful. if the problem is repetitive, the disk, disk drive 
(FDD) module, or the CIOP PCB may be faulty. 
NOTE: The system should not be left unattended with a 
questionable disk in the disk drive (FDD) module, since this 
could result in a lengthy outage if a reload from disk should 
become necessary for any reason. 
(7) if eeee = 1445 Disk directory error during data base save operation. 
A disk error was detected during a data base save opera- 
tion (via CMU procedure SAVE CUSTDATA). The disk save 
operation was aborted and the contents of the disk are now 
questionable. This error stack entry is accompanied by an 
immediate error message to craft personnel who attempt- 
ed the save operation. 
Craft personnel should reattempt the save operation until 
successful. If the problem is repetitive, the disk, disk drive 
(FDD) module, or the CIOP PCB may be faulty. 
NOTE: The system should not be left unattended with a 
questionable disk in the disk drive (FDD) module, since this 
could result in a lengthy outage if a reload from disk should 
become necessary for any reason. 
(8) If eeee = 1446 Data table checksum error detected during system load. 
The system data base load software detected a checksum 
error during the system start-up operation. No recovery ac- 
tion is initiated. 
This error may indicate a memory problem, disk corruption, 
or a faulty CIOP PCB. However, this error will occur on the 
first reload after a software upgrade procedure, and on each 
succeeding reload until the CMU procedure SAVE CUSTDA- 
TA is performed. In this instance, no corrective action (other 
than the CMU procedure SAVE CUSTDATA) is necessary. 
(9) If eeee = 1490 A power failure has occurred with MSM present and appar- 
ently operating, but software has detected that memory is 
not valid. An automatic system reload has been initiated and 
completed as a result. 
. 4-15  
						

							SATURN IIE EPABX A30808-X5130-DllO-l-8920 
Maintenance and Troubleshooting Issue 1, May 1986 
Table 4.02 Alarm Reporting and Processing (Continued) 
AI ARM TVPF CORRECTIVE ACTION . .-. . . . . . . . - 
This message is followed by “RELOAD : POWER FAILURE” 
and “S/W TRAP” messages (1489 and 1300) respectively, 
indicating the type and time of the recovery. 
If system reloads resulting in these error messages are 
repetitive: 
1. Replace MEM3 and MEM4 PCBs. 
2. Verify MSM operation. 
3. Consult Siemens field service representative. 
(10) If eeee = 2133 tt MSL number mismatch in main satellite network. 
The software detected that a serious data base inconsistency 
exists within the main satellite network. For proper main 
satellite network operations, both ends of each MSL trunk 
must correctly know the identity of the trunk (MSL number). 
The MSL number audit has determined that two ends of the 
identified trunk do not agree regarding the trunk identity. 
Lost calls will occur until the inconsistency is corrected. 
NOTE: The trunk identity is provided as indicated in the er- 
ror message below. 
“S/W TRAP 2133 (pp) OOaa OObb 
occc 0000 mm/dd hh:mm” 
aa = trunk group number 
bb = trunk member number 
ccc = MSL number sent from the distant PABX 
w. TONE GENERATOR FAILURE (18) The DTMF receiver audit routine has detected a failure of 
mmldd hh:mm the tone generator. A soft restart is initiated ?o restart the 
(18)’ = ID of process tone generator. If the problem is repetitive, the SMXTG PCB 
should be replaced. 
mm/dd = date of error 
hh:mm = time of error 
NOTE: For reference only, the error number for this 
error message is 1432. 
x. TRACE REQUEST BY EXT=aaaa 
ON EXT=bbbb mmldd hh:mm 
aaaa = station which requested the trace 
bbbb = connected station . The identified station dialed a call trace request access code. 
This information is printed on the SMDR alarm channel if 
equipped and simultaneously logged in the failure history 
memory. 
NOTE: For reference only, the error number for this 
error message is 1609. Contact the requesting party and determine the reason for 
the request. The most common reasons are: 
(1) A nuisance call was in progress. 
(2) A bad connection was experienced. 
Y. TRACE REQUEST BY EXT=aaaa The identified station dialed a call trace request access code. 
ON TRUNK=bb/cc mm/dd hh:mm This information is printed on the SMDR alarm channel if 
equipped and simultaneously logged in the failure history 
aaaa = station which requested the trace 
bb = trunk group number memory. 
cc = trunk member number 
Contact requesting party and determine the reason for the 
NOTE: For reference only, the error number for this request. The most common reasons are described above. 
error message is 1609. 
l = For Siemens field service use only. 
tt - Applies to MS software feature package only. 
( 
1 
I  
						

							I 
- 
SATURN IIE EPABX 
Maintenance and Troubleshooting A30808-X5130-DllO-l-8920 
Issue 1, May 1986 
Table 4.03 Failure Indications on LTUC Printed Circuit Board 
LED 
PUS 
PRS 
ALMO 
ALMO LED STATUS 
Dark 
Lighted 
l 
Dark 
Lighted 
l 
ALMl Dark PROBABLE CAUSE 
No failures are detected 
LTUC is not communicating with common control: 
+12Vdc undervoltage, -5Vdc undervoltage, or 
-48Vdc undervottage 
NOTE: When the system is reloading and common 
control is inactive, the PRS LED on each LTUC 
PCB lights steadily as a normal system function. If 
no failures are detected after the system reloads, 
the LEDs extinguish. 
No failures are detected. 
Loss of CLKA (2.048 MHz clock, 4ms timing pulse), 
or SYNR (ring synchronization) from common 
control. 
Not used in SATURN IIE. CORRECTIVE ACTION 
None. 
1. Proceed to paragraph 4.06 
Power Failures. 
2. Replace associated LTUC 
PCB. 
3. Check cabling between 
SMXTG and LTUC. 
4. Replace SMXTG PCB. 
5. Replace CIOP PCB. 
6. Call Siemens field service 
representative. 
None. 
1. If all LTUC PCBs have this 
alarm LED lighted, replace 
SMXTG PCB in CE section of 
Basic Shelf. 
2. Check cabling between 
SMXTG and LTUC. 
3. If only one LTUC PCB has 
this alarm LED lighted, 
replace the LTUC PCB. 
Not applicable. 
l If PRS and ALMO indicators are lit, check power supply voltages before replacing PCB modules. If -48Vdc is lost, PRS 
and ALMO indicators will be lit on all shelves affected. 
Table 4.04 Memory Support Module (MSM) Battery Test 
CAUTION 
Do not depress the BAsTEFlY TEST switch if the ON BATTERY POWER (red) indicator is already lighted. This indicate 
lights when commercial power is interrupted and the MSM battery is powering the system memory. Depression of the 
BATTERY TEST switch under this condition will disconnect the MSM battery cause the loss of system memory, and 
necessitate a memory reload when commercial Dower is restored. 
STEP 
1 
2 
PROCEDURE 
Press in and hold the BATTERY 
TEST switch on the front of the PSU. 
The associated green LED indicator 
lights steadily. 
Release the BATTERY TEST switch. VERIFICATION 
If the green LED indicator remains 
extinguished, the MSM battery pack 
is below acceptable voltage limits 
and requires replacement. 
The green LED indicator extin- 
guishes. CORRECTIVE ACTION 
Replace MSM battery pack 
4-17  
						

							A30808-X5130-DllO-l-6920 
Issue 1, May 1986 
I 
-- 
SATURN IIE EPABX 
Maintenance and Troubleshooting 
4.06 Power Failures. When a loss of power is suspected 
to be the cause of failures in the system, the craftsperson 
should follow the guidelines described below. (Refer to para- 
graph 2.15, Power Distribution and Failures, for descriptive 
information on the power supplies.) 
l Visually check the PSU front panel (Figure 2.01) for 
blown fuses and tripped circuit breakers. Refer to para- 
graph 4.06a. 
. If PSU fuses and circuit breakers are normal but all 
LEDs on the cabinet(s) are extinguished (i.e., the sys- 
tem is not processing calls), check the ac input vol- 
tage(s) to the Basic Cabinet, the PSU, and the -48PS 
module(s) (-48PS0 and, -48PSl if applicable). (When 
an Expansion Cabinet is included in the system, a se- 
cond ac input is wired to the Basic Cabinet and feeds 
the two -48 Vdc power supplies (-48PS0 and -48PSl) 
via PSU connector, J2.) If ac is measured, check the 
dc output voltages from the PSU in the Basic Cabi- 
net. Refer to paragraph 4.06b. 
0 If PSU fuses and circuit breakers are normal and the 
system is processing some calls (i.e., status indicators 
on the CIOP PCB are decrementing), check the dc in- 
put voltages to the Basic Shelf or ac input voltage to 
the LTUPS(s) on the LTU shelf or shelves, if applica- 
ble, in which problems are being experienced. Refer 
to paragraph 4.06~. 
l If the ac input voltages to the Basic Cabinet, PSU, 
-48PS module(s). and LTU shelf or shelves‘are correct. 
. ,. check the dc output voltages of the PSU, -48PS mod: 
ule(s), and the LTUPS module(s) on the LTU shelf or 
shelves, if applicable. Refer to paragraph 4.06d. 
When voltages are to be checked, the voltages must be with- 
in the ranges specified in Table 4.05. 
WARNING 
Hazardous voltages exist within the equipment cabinet. 
Be extremely careful when performing maintenance and 
troubleshooting procedures with the equipment panel(s) 
removed. 
CAUTION 
Before disconnecting or connecting power cables lead- 
ing to and from system power supplies, switch the as- 
sociated circuit breaker on the PSU front panel to the off 
(down) position. 
a. Visually check the PSU front panel for blown fuses 
(grasshopper-type) and tripped circuit breakers (refer 
to Figure 2.01). 
1. If a -488 fuse has blown, 
NOTE: If it is known or believed that a previous 
event or action by the craftsperson may 
have caused a transient fault condition 
which caused the fuse to blow, proceed to 
step (a) below; otherwise proceed to step 
(b) below. 
(a) Replace the -488 fuse. If the fuse blows again, 
proceed to step (b) below. (b) Remove all subscriber line modules (SLMA-0, 
SLMA-S, and SLAl6 PCBs) and E&M trunk 
modules (TMBA-2 and TMBA-4 PCBs) from the 
shelf protected by the blown fuse. Do not re- 
move the DTMF, SLMD, and PIMD PCBs from 
the shelf. 
(c) Replace the fuse again. 
(1) If the fuse does not blow, one of the mod- 
ules removed in step (b) is probably at fault. 
Reinsert the subscriber line and trunk mod- 
ules one at a time and recheck the fuse af- 
ter each module is inserted. If the fuse 
blows after reinserting a module, the mod- 
ule is defective. Replace the module. 
(2) If the fuse blows again, the most probable 
location of the fault is the PSU. Replace the 
PSU. (If optional MSM is installed, adjust 
PSU +SVdc output versus MSM output as 
specified in Table 4.05.) 
2. If a -48P fuse has blown, 
NOTE: If it is known or believed that a previous 
event or action by the craftsperson may 
have 
caused a transient fault condition 
which caused the fuse to blow, proceed to 
step (a) below; otherwise proceed to step 
(b) below. 
(a) Replace the-48P fuse. If the fuse blows again, 
proceed to step (b) below. 
(b) Remove all SLMD and PIMD PCBs in the as- 
sociated shelf. Do not remove the subscriber 
line modules (SLMA-0, SLMA-S, or SLAl6 
PCBs), DTMF modules, trunk modules 
(TMBAQ, TMBA4, TMBM, or TMIE PCBs) or 
common control modules (CE PCBs) in the 
shelf. 
(c) Replace the fuse again. 
(1) If the fuse does not blow, an SLMD or PIMD 
PCB is at fault. Reinsert the SLMD and/or 
PIMD PCB(s) in the shelf, one at a time and 
recheck the fuse after each module is in- 
serted. If the fuse blows after reinserting a 
module, the module is defective. Replace 
the module. 
(2) If the fuse blows again, the most probable 
location of the fault is the PSU. Reolace the 
PSU. (If optional MSM is installed, adjust 
PSU +SVdc output versus MSM output as 
specified in Table 4.05.) 
3. If the RGEN fuse has blown, 
NOTE: If it is known or believed that a previous event 
or action by the craftsperson may have caused 
a transient fault condition which caused the 
fuse to blow, -proceed to step (a) below; other- 
wise proceed to step (b) below. 
4-18