LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is Execution Property not reporting correctly?

I read the Execution property but it does not seem to report the setting correctly.

What am I doing wrong?

The next question I have will be how to set it programmatically.  

 

Capture.PNG

0 Kudos
Message 1 of 6
(2,936 Views)
If you look at the help for the ReentrancyType property, it says that it returns either:
0 - Share clones between instances
or
1 - Preallocate clone for each instance

This means that non-reentrant isn't even an option. There is an additional boolean property for whether the VI is reentrant (and if enabled, one of those options above applies to determine the type).

See here: http://zone.ni.com/reference/en-XX/help/371361R-01/lvprop/vi_exeis_reentrant/


LabVIEW Champion, CLA, CLED, CTD
(blog)
Message 2 of 6
(2,927 Views)

Excellent.  Thank you. 

 

Next, I need to figure out how to script changing the Execution Type for all the VIs in a directory.  

 

0 Kudos
Message 3 of 6
(2,889 Views)

In addition to what Sam said, you may notice that this property is not settable while the vi is running.

To change it, you need to open a reference to the vi (while not running) in another vi, where you are allowed to use this property in Write mode.

Of course, you can do this only at development time and not in an exe, where this property is always Read Only.

 

Execution:Reentrancy Type Property

Remarks

The following table lists the characteristics of this property.

Data type
Permissions Read/Write
Available in Run-Time Engine Yes (Read Only)
Available in Real-Time Operating System Yes
Settable when the VI is running No
Loads the front panel into memory No
Need to authenticate before use No
Loads the block diagram into memory No
Remote access allowed Yes
Must wait until user interface is idle No
Available with control VIs No
Available with global VIs No
Available with strict type definitions No
Available with polymorphic VIs No
 

 

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 4 of 6
(2,887 Views)

Ok, I did not seen your last reply.

Build a list of all vi paths and open them with Open VI Reference.

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
Message 5 of 6
(2,883 Views)

It works. 

Thank you very much to both of you.

 

Here is my example if it is helpful for others.  

 

Download All
0 Kudos
Message 6 of 6
(2,873 Views)