From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
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.
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. 🙂 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. 🙂 The code would behave exactly the same as if the code from the various tabs were placed next to each other on the BD.
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.