04-27-2011 01:22 PM
I am using the DSC module to create alarms. I can successfully configure an alarm for a shared varaible. I use the read alarms.vi to read current alarms. I am able to acknowledge them and clear them which removes them from the list. I can also see a history of them when using the "Alarm & Event Query.vi". Now I am doing the same thing with user defined alarms. I create the alarm using the "Set User Defined Alarm.vi". The alarm then shows up in the list (read alarms.vi). I can acknowledge the alarm and it disappears from the list. Now when I use the "Alarm & Event Query.vi" the user defined alarm doesn't show up in the list. Only the shared variable alarms show up. Is this correct? Is there a good example of what I am doing? The "DSC User Defined Alarms Demo.vi" example doesn't give an example of reading historical user defined alarms from the database.
Solved! Go to Solution.
04-28-2011 09:49 AM
Here is a basic program I created to try to figure out how to use these tools. Very simply, the code does the following:
-Creates a database if it doesn't exist (called Alarms Database)
-Create a new process called: Process Name
-Starts event structure which you can:
-Create a user defined alarm
-Query the database for the alarm created (Get History)
I am very simply using the DSC tools. I get an error when querying the database for alarming history. The I pass the reference of the multi-column list box to the "Alarm and Event Query.vi". What I expect to see is the multi-column list box fill with alarm data. It returns an error saying . The given Citadel database is not currently configured to log alarms to a relational database. I am trying to do a simple thing here. This shouldn't be difficult. I tried the suggestion on this post:
Which was to install Microsoft's SQL Server Desktop Engine 2000 (MSDE 2000). This made no difference.
I am sure you will get the same results when you run this VI on your system.
04-28-2011 10:39 AM
I can definitely vouch that your code works properly. I can create, acknowledge, and clear alarms with your VI, and DSM/MAX historical traces are consistent with their alarm data.
I attempted to view the history, and the listbox on my computer populates with the alarm history correctly, so the code there is also working.
If you're getting that error when retrieving the history, then there's likely something wrong with the SQL Server 2005 Express component of the DSC installation. I think our best first step will be to repair the DSC module installation.