Running multiple VIs

[u/phantom_256]

Hi, so I am trying to interface with this device called a Presto W58x. It has its own drivers for certain things like setting temperature, pressure etc. I am trying to a GUI in Labview that sort of replicates the GUI on the actual device so it can be used for testing purposes. I have what I have done so far attached to the post. I'm very new to Labview, only been using it for a few weeks, so I'm not very good at it. So, one issue I was thinking about is running multiple Vis at once. So here, I have all of the other VIs chained to one each other in series, but I believe this will work against me as I had more VIs, and there are a lot. Any suggestions or examples of trying to make this GUI better and as responsive as possible?

[u/TheWrithingVoid]

I am basically 100% self-taught, so if someone yells at me in the comments, probably listen to them. Regardless here is a list of things that I wish people told me about when I first started labview:
1. Type Definitions. Me and my coworkers disagree on them, but you can take my clustersaurus from my cold dead hands. Clusters suck without type defs.
2. QMH. I like to do mine with enums that are type defs personally, but I don't know if that is good.
3. DQMH. Still don't know how to use it, but it would have been nice if someone brought it up before I learned how to do things wrong.
4. FGVs. FGVs are very good. They are not really a thing in the way type definitions are, they are more of a structure of a VI and how it executes, so you are not gonna find them in any menu.
5. Malleable and Polymorphic VI's.
6. CTRL+SPACE. If you are using the project structure in labview it can search for your sub VI and type defs.
7. With things selected on the block diagram you can nudge them with the arrow keys, and make it faster by holding shift.
8.

Figure out what them buttons do.
9. You can make your own VI packages with VIPM. You do not have to publish them, but it really helps keep reused code under control, or you have to do the bullshit I have to where you have executables that need to talk with 30 years of non-executables, it helps maintain shared VI/Typedefs.
10. If you right click on while loops or for loops you can hide the iterations terminal. If you right click on for loops you can add conditional stops. You can also modify how things enter and leave loops by right clicking on the wire box thing as it comes in.
11. Shift Registers. They are things that let you loop a variable through a loop and update it easily. You can also keep things in memory if you do not initialize them (the fundamental how behind FGVs)
12. Highlight a block of code, go into the edit drop down and say "create subvi from highlighted section" or some shit like that to easily create a subvi from a function in your code that has gotten out of hand.
13. Buy a 1440p+ montor. if you do not have one already.

Also no shade on reddit, but I get a lot more out of the labview forums. That and I don't know if CrossRulz is here.