Troubleshooting Resources, Tools, and Equipment
3-8
STEP #3: Evaluate the Breadth of the Problem
Decide whether this is a single branch problem or a multiple branch
problem. Find out how many branches are unable to communicate
properly on the SDN; how many branches are unable to receive data from
any other instrument and/or unable to transmit data to any other
instrument.
Test the reception of the bedside with the OVERVIEW mode or with the
NETWORKTEST. Test the reception of ICs under normal monitoring.
Test the transmission of the bedside with the NETWORK TEST at another
bedside or with the OVERVIEW mode at another bedside.
If multiple instruments were missing from the NETWORK TEST display
(STEP #2) or gave status codes other than 001 C normal operation or 0030
self-test, then a multiple branch problem is indicated.
Action
• If more than one branch cannot receive at all or transmit at all, then
troubleshoot the ACC. Refer to the ACC Troubleshooting section.
Other possible sources of multiple branch problems (lower
probability) are given on page 3-12.
• If only 1 branch cannot receive at all or transmit at all, then go to
STEP #4.
Other possible sources of single branch problems (lower probability)
are given on page 3-12.
STEP #4: Self-Test Check of SDN Interface Circuitry
The problem has now been isolated to a system communication problem
on one branch. The problem could reside in the SDN interface board, SDN
cabling, or branch specific circuitry in the ACC. Refer to Figure 3-3.
Note
The SDN interface residing in the bedside/mainframe or IC is more likely to
be the cause of the problem than the branch specific circuitry in the ACC.
Each instrument’s self-test routine checks a portion of its own SDN interface
circuitry (SIC chip, buffer RAM, signature RAM).
To Next Page
Loading...
Need help?
General
