LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with user defined alarms in DSC

I'm trying to manage User Defined Alarms in DSC (LabVIEW 2011). I have two problems:

- I can Set and Clear an UDA from the development environment, but the Set VI takes 500 ms to finish, which seems a lot of time

- as soon as I create an executable, the Clear operation fails with error -1967362020 (IAK_SHARED: (Hex 0x8ABC701C) The provided refnum is invalid)

Do you have any suggestions?

Paolo
-------------------
LV 7.1, 2011, 2017, 2019
0 Kudos
Message 1 of 3
(139 Views)

Hi,

 

I believe by default, a project has the shared variable deployment set to autodeploy.

When the first app using them starts running, they are deployed and should remain deployed until the last vi using them is stopped.

I would suggest trying turning auto-deploy off, manually deploy the variables (as a network shared), and run the applications.

As I understand them, the shared variables should remain available until you undeploy them or exit Labview.

 

Best regards.

0 Kudos
Message 2 of 3
(86 Views)

Thank you for the answer.

I tried first with the DSC Alarms Demo project (copied to another location), then with my original project.

In the first case, shared variables are deployed and undeployed programatically. In the second case, they are already deployed and active at computer start. I can easily verify those conditions using the Distributed System Manager.

On the other hand, I can always set the User Defined Alarm the first time with no error. It's the subsequent Clear operation that fails.

 

Some more details. When the error occurs, this message appears at program termination:

pincpanter_0-1619595550038.png

Furthermore, if I use the same alarm name in subsequent tests, also in the development environment, the error occurs and the Runtime Error appears at program termination or closing the project (LabVIEW stops responding and is abruptly terminated by the OS). In other words, the used name becomes "forbidden" forever.

To successfully run the test again, I need to use a brand new alarm name.

 

Paolo
-------------------
LV 7.1, 2011, 2017, 2019
0 Kudos
Message 3 of 3
(67 Views)