For the records there have been LabVIEW versions (5.1 and also 6.01 and others that had some rather obscure and nasty overoptimizations of the shift register resulting in wrong execution of the code.) Considering this I think it is better to introduce a new feature not optimized to the max than having it create wrong code due to a corner case not covered where it does a to agressive optimization. From the function palette select structures and then select while loop and place it on the block diagram.

and pass it back through the shift register to the loops next iteration. Labview program to use shift registers Let’s move to the LabView and try to understand the work king of shift registers in depth.

This is not inherent to the feedback node as it is in fact just a different thing for the same functionality but probably a oversight or time pressure issue, where the optimizations applied to the shift register over the last 4 or so LabVIEW versions haven't been implemented fully yet. CLISP, Haskell, OCaml, LabVIEW, and PHP interfaces. With the feedback node you have to branch your wire and therefore most probably producing (somewhere in the deep background of LV) a copy of your data, and therefore lost of time.Īt least in LabVIEW 7.x the Feedback node has some dramatic non-optimizations in comparison to shift registers. It's disadvantage might appear, when you need the data after the loop finished. For myself I'm used to the shift register, I seldom use the feedback node.Īs Neville mentioned, the advantage of feedback node is, that you don't have to route wire through the whole diagram.

Labview shift registers