INTRODUCTION
I-E96-607A
4 - 1
SECTION 4 - OPERATING PROCEDURES
INTRODUCTION
After completing the procedures in
, the INFI-NET to
INFI-NET communication interfaces are ready to be put into
operation. This section explains information for daily operation
of these interfaces.
INNIS01 MODULE START-UP PROCEDURES
On power up, the network interface slave (NIS) module micro-
processor stays in reset until its associated transfer module
(INIIT02 or INIIT03 module) removes the reset and allows the
firmware to execute self-diagnostics. The interface module
determines when the NIS module will go on-line. The NIS mod-
ule comes on-line in the loop mode set by dipswitch SW3 poles
seven and eight, with the event or error counter display set by
dipswitch SW4, poles four through eight.
Use the event or error counter display (CPU LEDs) to check the
NIS module operation. If communication errors occur, the host
module sets the NIS communication status bits in the module
status report. View the module status report by using a moni-
toring device on the loop (i.e., operator interface station, engi-
neering work station, etc.).
Event Counters
Internal counters maintain a count of events such as the num-
ber of messages transmitted, retries, and number of messages
lost. Table
has a complete list of event counters and the
dipswitch settings required to select a particular event counter.
The 16 CPU LEDs on the module faceplate display a count (in
binary) of the event counters (see Figure
). CPU LED B8 is
the most significant bit; CPU LED A1 is the least significant bit.
Error Counters
Errors such as receive errors, messages with circulation count
errors, etc., are maintained in internal counters. Table
has
a complete list of error counters and the dipswitch settings
required to select a particular error counter. Table
lists the
error codes that appear on the NIS module CPU LEDs.
