LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Saving permissions problem

Hello

I think this problem is specific to LabVIEW on Linux. I have created a VI that I am trying to save as a subVI for use in a bigger VI. This proposed subVI contains some instrument driver VIs that are saved in /usr/local/lv71/instr.lib, to which the user does not have write permissions (nor should it).

However, after I create the subVI and try to close the front panel (to bring up the save subVI dialog) and choose to save the subVI, the save process quits complaining that it cannot save any of the VI's from instr.lib. This IMO is braindead - I am not asking it save those VI's, only invocations to those VIs.

Fortunately, if I try to save the VI explicitly, it offers to save the unsaved subVIs and the process goes forward smoothly. I cannot understand what the difference between the two is, but looks like a LabVIEW bug that shows up only when it is running on an OS with some idea of what permissions mean.

0 Kudos
Message 1 of 2
(2,488 Views)

m-s,

When you open up your subvi and then open up those instrument driver vi's do you see stars (*) by the name of the vi?  It almost sounds like the instrument driver that you are using was compiled for a different version of LabVIEW and your program is compiling them for the current LabVIEW version when you open up your subvi.  This would be the case if you have LabVIEW 7.1.1 and your instrument driver was written with LabVIEW 7.1.  When you open up your subvi, it would recompile the instrument drivers for 7.1.1 and ask you to save them when you close your subvi.

Justin D
Application Engineer
National Instruments

0 Kudos
Message 2 of 2
(2,457 Views)