Alarms Abstract

Usage  : ALARMS processes alarms (events and exceptions).
         ALARMS and FrontEnd communicate via ACNET, task name is "AEOLUS"
	 ALARMS and alarms daemon communicate via multicast, task name is "ALARMR"
         alarms daemon communicates with clients via TCP/IP
        
Restart: ALARMS restarts when CENTRA restarts.
	 To restart manually, type "acnet restart alarms".

	 See here  for a more detailed document on the alarm system.

	 See here  for a block diagram of the alarm system.

______________________________________________________________________________

ALARMS is also the name of an Open Access Client front-end. This abstract is
actually defined by name for this OAC. 
______________________________________________________________________________

Usage  : ALARMS supports alarm devices with a client controlled interface as
    	 well as alarm properties for devices belonging to front-ends that 
	 do not support alarms.  Finally, it supports alarms to be sampled
	 on a specific Tevatron clock event similar to MOOC front-ends.
	 
	 Use D80 to add an analog or digital alarms block of 20 bytes long
	 with the node of the alarm block property being ALARMS.  The reading
	 or status property will be scanned at 1 Hertz unless the event #1
	 field contains a -1, then the reading or status will be sampled on
	 the Tevatron clock event in field event #2.  When a device is going
	 bad or good the tries needed accumulate at 1 Hertz.  This OAC must
	 download by scanning all the properties in the database to find the
	 ones it must monitor.  Consequently, the scan job to monitor readings
	 and status will not begin until about 5 minutes after the last 
	 database addition, and this OAC takes 10 minutes or more to 
	 initialize since it runs on a slow Netra and the autotune servlet
	 shares the CPU.
	 
	 ALARMS also has a client interface for posting and clearing software
	 alarms.  See gov.fnal.controls.daq.oac.clients.alarms Java code and
	 Charlie King for details.
	 
	 ALARMS is a Java Open Access Client (OAC) process which runs on DCE32.  
	 You can view log files for ALARMS in the directory
	 'daesrv\\engines\files\oac'.

Restart: ALARMS is restarted its DAE is restarted.

______________________________________________________________________________

Keeper: Seung-Chan Ahn

OAC Node: dce32

Now: Fri Aug 29 21:38:37 2008