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.
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.
10-13-2021 08:54 AM
Hi,
I need to convert a LabVIEW block diagram(code) into a simple flowchart. The LabVIEW code is rather complicated algorithm to find a true peak from array obtained from an acquisition. I have two VIs(one is calling for a sub-VI). I can attach the VIs if needed.
Can you help?
Thanks.
10-13-2021 09:34 AM - edited 10-13-2021 09:35 AM
There is no way to just "convert" a block diagram to a flow chart.
If you understand how the program works then flow charting it should be relatively easy.
BTW: Most programmers make a flowchart of their program before they start programming
10-13-2021 09:57 AM
Are you requesting this because you have a hard time understanding the LabVIEW code and want someone else to translate it to a simpler flow chart that you can understand better?
10-13-2021 10:10 AM
I was hoping there is an easy way to reverse-engineer other people "spaghetti" LabVIEW code, but obviously there is no way.
Thanks.
10-13-2021 10:15 AM
@tzantzai wrote:
I was hoping there is an easy way to reverse-engineer other people "spaghetti" LabVIEW code, but obviously there is no way.
Thanks.
Nope, sorry you are on your own here...
10-13-2021 11:20 AM
@tzantzai wrote:
I was hoping there is an easy way to reverse-engineer other people "spaghetti" LabVIEW code, but obviously there is no way.
It is easy to reverse-engineer well written LabVIEW code. It often very logically organized and is self-documenting.
Not so much for "spaghetti code". It's like asking to reverse-engineer a plate of spaghetti marinara back into grains of durum wheat and fresh tomatoes.
Still, what might seem like an intractable mess to some, could be quite easy to figure out for a LabVIEW programmer with decades of experience. Feel free to post it.
Also remember that the DFIR step of the LabVIEW compiler itself will internally deconstruct and simplify the diagram into a dependency graph that is much better organized, but that is not something that is exposed to the user. I am always amazed how gigantic and horribly written LabVIEW code still almost instantly compiles into perfectly running machine code. Amazing! 😄