LabVIEW
VI Hierarchy
Solved!
VI Hierarchy shows the way the VIs are arranged within your program. To change this, change the way your main VI is written.
However, it seems like you're asking the wrong question. Usually the hierarchy windows are useful as a debugging/informational tool, but not considered a design input.
Probably calling the 4 VIs within the main VI will do what you want, but there may be complications depending on the design.
As a side note, attaching the actual VIs rather than an image with default icons would make it easier to give further help 🙂
1. Add all of your VIs into a project.
2. Drag a VI from your project onto the block diagram of your main VI.
You can also use the "Select a VI..." from the palettes to open a file browser to select the VI to put on your block diagram. Sounds like you should really check out the free online tutorials. Links are at the top of the LabVIEW forum.
I *think* what crossrulz wrote would work for you.
Looking at the code, I'd suggest you might make it easier to read if you could remove some of the seemingly duplicate globals/Network Variables - I guess probably the NVs are for physical channels so you need both in each case but I'm less sure about the duplicate NodeASG ON, NodeASG OFF etc, especially when they are doubles (why not boolean?). The "Off" channels appear to have inverted logic, which makes it a bit confusing...
Programmatic access for the Network Shared Variables would allow you to reduce the size of the Main Frame.vi even whilst retaining all of the variables by building a (reentrant) VI that takes a reference and does the =1, =0, current boolean and then timing circuit bit. You can see an example of this by right clicking on one of the nodes and choosing "Replace with Programmatic Access", and then you can wire the same reference into the second one.
As it is, changing the timing delay for any one circuit will affect all of the others because they're in the same outer While loop.
You could go further and make a subVI which takes the ON, OFF, Node boolean and the pair of Variables as inputs (perhaps using a cluster) and then had both of these instances of the subVI inside.
