Enabling and disabling of VeriStand alarms

[h_yong]

Hello, I would like to know if there is a way to enable/disable alarms via controls in the workspace. For example, under some conditions, I'd like to disable a set of alarms. It'd be more convenient to do so by toggling a boolean control, for example, than opening up the alarm monitor panel and disabling each one of a batch that way. Alternatively, I was thinking if I could have a boolean mapped to another procedure that could systematically go through to disable a batch of alarms. However, I do not see a system channel to set that could enable/disable specific alarms. I am using VeriStand 2009. Thanks.

[StephenB]

There isn't any built in workspace controls to interact with alarms, but one could be created. NI VeriStand's execution API has several functions for interacting with alarms... including enabling and disabling. Note if you had LabVIEW installed when you installed NI VeriStand, there will be a palette with NI VeriStand functions.

You would have to create a custom workspace object and use the execution API inside that object. Good example to start with would be the channel fault object.

If you don't have the time or training to do the LabVIEW work yourself, I can provide reccomendations for an alliance partner to contract the work out to if you don't already have one.

[h_yong]

Hello, I am not familiar with custom workspace objects but have used the Custom Device template to create simple custom devices. I tried to use the workspace execution API's from within the custom device, but that did not work. Is there a blank custom workspace object template that I could work with other than starting with the channel fault object? Thanks.

[Devin_K]

The best place to start for a blank template custom workspace control is to make a copy of "Decoration - Free Label.vi" in the "<Documents>\National Instruments\NI VeriStand 2010\Display Templates" directory.  This shows the basic functionality of a custom workspace control, including getting/setting custom data for the control (to save data between when the workspace is opened and closed), and registering for an event which is fired when a user right-clicks on your control.

However, the Channel Fault control is also worth looking at because it shows an example of using some of the .NET APIs (Workspace and Fault Manager).  It also shows some optional specially-named controls that automatically get populated with the correct values by NI VeriStand.  The optional controls supported are:

NIVS.Gateway IP Address (string)
NIVS.Workspace event (event)
NIVS.Project File Path (path)
NIVS.INI File Path (path)
NIVS.System Definition Root (.net ref)

•NIVS.Gateway IP Address (string)

•NIVS.Workspace event (event)

•NIVS.Project File Path (path)

•NIVS.INI File Path (path)

•NIVS.System Definition Root (.net ref)