Ok, from halog 344616 I think I see why the DAQ alarm was disabled. Sorry I missed that.
Because the trigger rate can drop to zero with beam trips, presumably. Will be fixed tomorrow, it says.
However, note that beam-trip-related false alarms are suppressed because the DAQ file has to be not updated for > 2 minutes, as well as the L1A rate zero 3 times in a row. Even if the L1A rate is zero, the file tends to be updated by EPICS or Scaler data (if the DAQ has not crashed) which informs the script that the "DAQ is ok" -> no alarm.
But ... if you get false alarm, disable this way
cd ~a-onl/scripts/dtalarm ; rm enable.dat ; echo "0" > enable.dat