LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

alarm timer

Just change the comparison (replace [GREATER than ALARM limit] with [LESS than EMPTY limit] or [EQUAL EMPTY]).

Good Luck
0 Kudos
Message 11 of 14
(1,018 Views)
thanks, but I dind't explain me well, this is a good solution, but I want that the alarm display after the time goes by, and not when the watter gets the minimum level.
Thanks again
HDLP
0 Kudos
Message 12 of 14
(1,018 Views)
The delay before alarm will be the same, is just that the condition is different - instead of monitoring the time the level is greater than limit, it will wait same time for level to be less than (or equal) limit.

From the DELAY BEFORE ALARM point of view, the only important thing is a change in comparison result (TRUE/FALSE).
0 Kudos
Message 13 of 14
(1,018 Views)
(I applogize if this takes your solution in another direction, but I didn't have time to review all of the otehr correspondance.)

In a similar situation, I'm monitoring a process temperature and when the temperature exceeds a maximum value for more than one minute, then an alarm is sounded (i.e., lights and sirens).

I simply note the system time when the temperature first exceeds the max and then pass this value to the next loop with a shift register

The vi checks during each loop to see if the temperature is still high and if the elapsed time is more than 60 seconds (my loop is on a two second delay to reduce the number of data points).
When the elpased time (current time minus first alarm state) exceeds the allowable time limit, the alarm is triggered.


MEANWHILE, the vi continues to loop, monitor, and update the other 95 temperature and gas sensor displays every two seconds.

Works pretty well - the timing is accurate enough and all of the temperature and gas displays continue to update "live".

(This works equally well for maximum and minimum time and temperature limits.)
0 Kudos
Message 14 of 14
(1,018 Views)