Experimental Physics and
Industrial Control System

[email protected] (Steve Lewis) · Mon, 4 May 1998 11:34:09 -0700

As a follow-up to the discussion last week, included is the
text file with combining all additional details I got from
Janet Anderson over the last several years.

(Also at:  http://csg.lbl.gov/EPICS/alh-new.txt)

Alarm Handler: supplementary documentation
------------------------------------------

o A new ALIAS feature which allows a user to define an alternate name for
an alarm group or channel has been implemented and can be defined in
the alarm configuration file.

     Input Format:

	 $ALIAS <any valid text>

     Description:

	 The line starting with $ALIAS is optional. It is required only
	 when a user wants to define an alternate name for an alarm
	 group or channel.

o A new feature which allows a user to define a unix process to be
started when the alarm severity for an alarm group or channel changes
value has been implemented and can be defined in the alarm
configuration file.

     Input Format:

	 $SEVRCOMMAND sevrChangeValue <any valid Unix command syntax>

     Description:

	 The line starting with $SEVRCOMMAND is optional. It is
	 required only when a user wants to start a Unix process when
	 the alarm severity value for a group or channel changes. A
	 single group or channel may have multiple $SEVRCOMMAND lines.
	 This line defines the change in the severity necessary to
	 start the process and defines the process to be started. Valid
	 severity change values are -
	   UP_INVALID    UP_MAJOR      UP_MINOR         UP_ANY
	   DOWN_MAJOR    DOWN_MINOR    DOWN_NO_ALARM    DOWN_ANY

o A new feature which allows a user to define a unix process to be
started when the alarm status for an alarm channel becomes a specified
value has been implemented and can be defined in the alarm
configuration file.

     Input Format:

	 $STATCOMMAND alarmStatusStringValue <any valid Unix command
	 syntax>

     Description:

	 The line starting with $STATCOMMAND is optional. It is
	 required only when a user wants to start a Unix process when
	 the alarm status becomes a specified value for a group or
	 channel changes. A single group or channel may have multiple
	 $STATCOMMAND lines. This line defines the status value
	 necessary to start the process and defines the process to be
	 started. Valid alarmStatusString values are defined in the
	 alarmString.h header file. Example alarm status string values are -

         NO_ALARM   READ      WRITE   HIHI      HIGH   READ_ACCESS
         LOLO       LOW       STATE   COS       COMM   WRITE_ACCESS
         TIMEOUT    HWLIMIT   CALC    SCAN      LINK
         SOFT       BAD_SUB   UDF     DISABLE   SIMM

o A new feature which allows alarm count filtering has been implemented
for any alarm channel and can be defined in the alarm configuration
file.

     Input Format:

	 $ALARMCOUNTFILTER <inputCount> <seconds>

     Description:

	 The line starting with $ALARMCOUNTFILTER is optional. It is
	 required only when a user wants the alarm handler to filter
	 the registration of alarms for a group or channel. This line
	 defines alarm count and seconds required for alarm
	 registration.  To register as an alarm, an alarm channel must
	 remain in alarm state for more than <inputSeconds> seconds OR
	 the alarm channel must enter into an alarm state from a
	 no-alarm state more than <inputCount> times within
	 <inputSeconds> seconds.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System