dsc alarm control bug?

[User002]

Hi all,

The alarm list control retains the process watch list when a VI is copied between computers. This will make the VI both load and execute very slowly when a program starts, presumably as it will try to connect or located the processes on the other computer. It seems also not possible to set the process watch list to be listening on 'localhost' processes. Clearing the processes and then closing the VI does not work properly either, as the processes from the other computer will be back in the configuration after labview is restarted.

However I found a way to clear the process list. 

1. Clear the process list.

2. Set the alarm control list in 'design mode' and then back again.

3. Save the vi.

It is quite bothersome if there are several instances of the alarm control? Is there a better way to deal with this?

Am I maybe missing something obvious?

/Roger Isaksson

[Zekasa]

Hi,

I faced the same probelm with the "Alarm and event control", in order to get the alarms that related to your precess only, you hav e to remove the "Subscribe All Local Precesses.vi" from the block diagram, then right click on the control on the front panel and select your process. check the image below

 

Hope this helps

[User002]

The alarm control will store the process list when the control is modified and saved. It is therefore important to shut down the calling vi cleanly and calling clean up procedures before anything is saved.

This is a workaround and a proper fix is in the works I presume?

/Roger

[JimMacD]

Rois,

A couple of questions for you:

1) I presume that you made the "UnSubscribe Processes.vi"; I've been playing aroudn with the Event View property/invoke nodes and am wondering why you used "Remove All Processes" followed by "Delete Process".

2) I am using the Alarm and Event Viewer in a dynamically called VI (an Alarm Page that the user brings up to check alarms). I do not use the "Subscribe all local Processes.VI", instead I use the invoke nodes to add only the processes I want in the viewer. Since I am loading/unloading this VI that the Alarm/Event viewer is a part of, what clean-up activities should I be doing when the Vi is closed (user navigates away fromt hat dynamic VI)?

-JimM   

[User002]

Jim,

I got this proposed solution from NI. I put it forward here for the benefit of other people. It is mysterious why they didn't answer my forum post instead of having to scramble the whole support chain?

My guess, I haven't tested it, is that the "Delete Process" will cause a "dirty star" on the vi front panel. And a subsequent save of the vi will make the change permanent in the control? Give it a try and report your findings here?

I think I would call the vi I provided in an earlier post, with the string array of the processes you added, every time the dynamically called vi ends execution. That way you can safely save your alarm vi's that have a dirty star when the vi ends execution (and pops up the "save vi" dialogue)

/Roger

[JimMacD]

I guess I was wondering more why it was not enough to just call "Remove All Processes"

[JoeHill · Accepted solution]

Hello,

For all interested, there is a CAR for this to make the VI load faster: CAR # 333897. It was not implemented in LabVIEW 2012 though and the recommended workaround is the one described in post 3.

Best regards

Johan