11-10-2009 01:47 PM
I need to set a filter on the Alarm and Event Query based on the alarm's set time. It seems that the "start timestamp" setting in the filter cluster sets up the query to filter by ack/clear time, not by set time. (You can figure this out by trial and error, as I did.)
Running the equivalent query in the MAX A&E view returns the same result - it filters by ack/clear time rather than set time.
Is this a bug?? Is there a way to filter the query based on set time? This poses a major limitation to my application.
Thanks,
Charlie
11-12-2009 01:43 PM
11-12-2009 02:28 PM
The Alarm and Event Query vi allows for querying the alarm/event database using a filter. One possibility is to filter the query based on "start timestamp" and "stop timestamp", which is are elements of the cluster going into the filter input to the Alarm and Event Query vi. I've found that this filter queries the database based the alarm's ack/clear time, rather than the alarm's set time. So, for instance, if an alarm is set now but it is not acknowledged or cleared until next year, the filter will register the "start timestamp" as next year. If I need to query the database for all alarms that were set today, it seems that there's no way for me to do this.
And as I pointed out, running a query with the equivalent filter in the MAX A&E view returns the same result: the "start time" and "end time" filter settings seems to filter based on the ack/clear time rather than the set time.