LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Advantages/disadvantages to placing a folder of subvi's common to several rt and fpga targets under my computer in project tree?

For a project with several targets, each of which with RT and  FPGA components, what are the advantages/disadvantages to placing the folder of subvi's common to the the targets under the 'my computer' node in the project tree so you just have one copy vs. have a copy under each target RT/FPGA node?

 

This does seem possible as I was able to move RT/FPGA subvi's (with auto-population capability turned off) from one of the targets to the 'My Computer' branch.

 

I"m aware that all the virtual folders underneath each different target might point to the same folder, i.e. there would still be only one actual folder in the 2nd case, It just seems that the more copies of a folder you have, the more likely it is that later on you might accidentally delete a subvi that is in fact still used by some other target.

 

Thanks

0 Kudos
Message 1 of 5
(3,029 Views)

Why not place common VIs in your user.lib?

With separation of compiled code enabled, when using those VIs for different targets…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 5
(3,024 Views)

Thanks for the input - I'd started from one of the sample projects, i.e. the structure already existed. I was just wondering if there better overall organizations.

0 Kudos
Message 3 of 5
(3,001 Views)

aetc wrote:

I"m aware that all the virtual folders underneath each different target might point to the same folder, i.e. there would still be only one actual folder in the 2nd case, It just seems that the more copies of a folder you have, the more likely it is that later on you might accidentally delete a subvi that is in fact still used by some other target.


I don't understand the concern here, especially if you're using virtual folders. With a virtual folder you can remove an item from one target and it won't be deleted from disk, nor from other targets. Also, with a source control system (you're using one, right?) it would be trivial to recover a VI that you accidentally deleted without realizing that another target still needs it.

 

It doesn't make sense to put VIs in the project under targets on which you will never execute them. If you have VIs that are meant to run only on the RT system, I would find it confusing to see them under My Computer. Why would you put them there? You don't need to have every VI included somewhere in the project; it's reasonable for common VIs (such as those in vi.lib and user.lib) not to be referenced anywhere in the project.

0 Kudos
Message 4 of 5
(2,996 Views)

Good points - thanks for the input.

0 Kudos
Message 5 of 5
(2,989 Views)