LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any drawback of using "Subvi" or "Local variable"?



andre.buurman@carya wrote:
Hello,

Is all your functinality handled in 1 VI?

Your description would result in multiple parallel operation VI's.

One doing UI handling
One doing AI and AO
One doing DI and DO
One control
Etc.

In that way each parallel task only has a specific function, which is more easily maintained.


Actaully all my job is done in 2 VIs. The main.vi is common and handles all DI related tasks and passes the state of DIs in an array via a Functional Global.

The next VI is a sub.VI which gets "contained" in the subpanel of main and handles  all of  the other jobs.  I have not told you  one more thing - the test stand has  22 unique  test patterns  and they have nothing in common  between them. So I have  that many  sub.VIs which are called up based on user demand.

This being the case if I further divide the VIs based on functions as mentioned by you, passing data between them, prioritizing the loops and such will be an eloborate thing to figure out. Anyway its another line of thinking and maybe I can check that ( with some more brain storming like this ) for my next project.

Regards

Raghunathan.
Raghunathan
LabVIEW to Automate Hydraulic Test rigs.
0 Kudos
Message 31 of 31
(403 Views)