Bailey infi 90 IMHSS03, Instruction

Page: 54 / 93

TROUBLESHOOTING
ALARM AND EXCEPTION REPORTING
6 - 4 I-E96-322A
®
For a group test (nine), tests two through eight run in numeri-
cal order. On a failure, the test number that failed is displayed
if the test number display mode is selected. A failure of a test
within the group terminates the group test at that point if the
halt on error feature is selected. All tests after the failing test
will not execute until the fault is removed.
To invoke the IMHSS03 diagnostics:
1. Set dipswitch S1 pole 1 to position 1 (off) to select the diag-
nostic mode (see Figure
6-2 ).
2. Set dipswitch S2 pole 1 to select the LED display mode.
Figure
6-2 shows the display mode settings.
3. Set dipswitch S2 pole 2 to select the halt on error feature
(see Figure
6-2 ).
4. Set dipswitch S2 poles 8 through 5 to select a test number.
Table
6-1 lists the diagnostic tests and their ID number.
5. After correctly setting the dipswitches, reset the module to
start diagnostics.
Observe the test results on the IMHSS03 LED display (see Fig-
ure
6-1 ). The selected tests will run repeatedly until the
IMHSS03 module is reset. The module will halt diagnostics if
an error occurs while the module is in halt on error mode.
ALARM AND EXCEPTION REPORTING
IMHSS03 function codes do not directly generate alarm or
exception reports. If exception reporting is required, send the
required outputs to standard exception reporting blocks. For
more information, refer to the instruction for the operator
interface in use.
FUNCTION CODE 55 PROBLEM REPORTS
Function code 55 generates I/O module error reports. These
problem reports are report type 12. Function code 55 gener-
ates five module problem report error types (refer to Table
6-2 ).
•
Error type 1 - no response/wrong type.
•
Error type 2 - calibration error.
•
Error type 3 - channel failure/out of range.
•
Error type 9 - input failure.
•
Error type 12 - output fixed.
Problem reports are broken down into two categories: Major or
fatal errors, and minor or nonfatal errors. Fatal errors indicate
that the given mode of operation will not function. Fatal errors
generate module problem reports having error types one, two