INTRODUCTION
I-E96-613A
4 - 1
SECTION 4 - OPERATING PROCEDURES
INTRODUCTION
After completing the steps detailed in
, the INFI-NET
to Plant Loop remote interface modules are ready to be put into
operation. This section provides the necessary information for
daily operation of the INFI-NET to Plant Loop remote interface
modules.
INNIS01 NETWORK INTERFACE SLAVE MODULE START-UP PROCEDURES
On power up, the INNIS01 Network Interface Slave Module
(NIS) microprocessor stays in reset mode until its associated
transfer module (INIPT02) removes the reset mode and allows
the firmware to execute self-diagnostic routines. The IPT mod-
ule determines when the NIS module will go on-line. The NIS
module comes on-line in the loop mode set by poles seven and
eight of dipswitch SW3, with the counter display set by poles
four through eight of dipswitch SW4.
Use the counter display (faceplate LEDs) to check the NIS mod-
ule operation. If communication errors occur, the host module
sets the NIS module communication status bits in the module
status report. View the module status using a monitoring
device (console, computer, etc.) on the loop.
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. The group
A and B LEDs on the module faceplate display a binary value of
the event counters (LED B8 is the most significant bit, LED A1
is the least significant bit). Figure
shows the location of the
group A and group B LEDs.
Error Counters
Errors such as receive errors, messages with circulation count
errors, etc., are maintained in internal counters just like the
event counters. Refer to Table
for a listing of error
counters. Table
lists the error codes that appear on the NIS
module faceplate LEDs.
