CAT EMCP 4 - Page 60

Application and Installation Guide EMCP 4 SCADA Data Links
©2013 Caterpillar
All rights reserved. Page 56
4. Low oil pressure warning
5. High coolant temperature warning
6. High coolant temperature shutdown
7. Low battery cranking voltage warning
8. ECS not in automatic warning
First of all, note that these events must be enabled (i.e. they will show up in the event log when the event
occurs) in order for them to show up in the alarm group data registers. Some of these events may not be
enabled by default. Refer to the EMCP 4 Application and Installation Guide for instructions on enabling
events and setting thresholds to the appropriate levels for triggering them.
A quick explanation of how the alarm group data is arranged. The data is grouped into “columns”, which
indicate which column and row (LED Pair #) would be lit on the RS-485 Annunciator module. There is
also a “horn” register, which indicates which row(s) would trigger a horn on the RS-485 Annunciator
module. E.g., if the Alarm Group 2 Column 1 register has a 1 in the bit 2 position (defined as Row 3), then
an RS-485 Annunciator module configured for Alarm Group 2 would have the third row left LED lit.
In this case, there are only eight events that we want to read. However, they can be placed in a
row/column position only if the correct color LED is available for that position. For example, for row 1,
column 1 is red and column 2 is amber. Therefore a shutdown event on row 1 will turn on column 1,
whereas a warning event on row 1 will turn on column 2.
All event types are not valid on all row/column positions. Table 7-1 indicates which event types are
available on which row/column position. Note that events with a severity level of “specific diagnostic” are
available on any row/column, and events with a severity level starting with “condition exists” or “condition
does not exist” indicate the color (which specifies the column) that will activate upon event activation.
T
ABLE 7-1: RS-485 ANNUNCIATOR EVENTS ALLOWED BY ROW/COLUMN
Row Col1 Col2
1 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
2 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
3 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
4 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
5 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
6 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Green)SpecificDiagnostic,ConditionExists
7 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
8 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
9 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
10 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
11 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
12 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
13 (Green)SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
14 (Green)SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
15 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Green)SpecificDiagnostic,ConditionExists
16 (Red)Shutdown,SpecificDiagnostic,ConditionExists (Amber)Warning,SpecificDiagnostic,ConditionExists
One possible configuration for Alarm Group #2 is given in Figure 7-7. Note that row 6 was skipped,
because it cannot contain warning-type events, whereas all the desired events included warnings.