LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Authors
Showing results for 
Search instead for 
Did you mean: 

Parallel Execution Structure as opposed to Sequence Structure

I would like to propose the use of a stacked parallel execution structure.  Especially in FPGA applications, this will solve the problem of diagrams running off the screen.  All execution pages will run simultaneously as if independent while loops were scattered across the BD.  This idea potentially leads into a 3 dimensional visuallization of coding LabVIEW. Note: In the image, the pages are offset but should look similar to a stacked sequence structure.



Parallel Execution Structure 3.JPG



Parallel Execution Structure 4.JPG
Knight of NI

Many years ago something similar came up: Basically a tab structure on the BD as a way to layer parallel code that has no data dependency.


The tabs could be freely named. For example, one tab could be named UI loop, one DAQ loop, etc. Instead of scrolling to edit different parts, we could just flip to a different tab. Smiley Happy More tabs could be added as needed.

There could be shared input tunnels, e.g. for a queue that is configured outside the tab structure on the left and later accessed on multiple code tabs.


Note that this is just a way to arrange code and is purely cosmetic. It does not add anything algorithmic. Smiley Happy The code would behave exactly the same as if the code from the various tabs were placed next to each other on the BD.


LabVIEW Champion Do more with less code and in less time
Active Participant
Normally if there are too many parallell loops I would say it's better to make them sub-VIs instead...
Check out ClampOn CAN Monitor on the LabVIEW Tools Network.
I agree that it is best to use a subvi when applicable.  However, it is more of a mess when you have many controls/indicators needing to be updated on the front panel during execution of that loop.  You could pass references but sometimes it doesn't make sense, especially when programming FPGA.  Thanks for posting.

I think I like the tab option as suggested by altenbach

Trusted Enthusiast
Trusted Enthusiast

There also was a recent suggestion of "layers" on the BD, although I never managed to get the OP to clarify what he meant by that...

Active Participant

Kudos if that structure looks like a tab with labels 



Basically a tab structure on the BD as a way to layer parallel code that has no data dependency +1

Zafer DEPE
R&D Proje Lideri
Elektronik Müh.