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.
07-27-2018 11:07 AM
thanks!
The rest could probably be removed if you used the Error Cluster to force sequential execution like you are supposed to do.
this does not make sense to me.. do you have an example?
have a nice weekend
07-27-2018 11:34 AM
Have a look at this NI newsletter. It covers the overuse of stacked and sequence frame structures and how to replace them.
07-27-2018 11:45 AM - edited 07-27-2018 11:52 AM
@idjuven1 wrote:
thanks!
The rest could probably be removed if you used the Error Cluster to force sequential execution like you are supposed to do.
this does not make sense to me.. do you have an example?
have a nice weekend
Here's an example...
The error cluster forces sequential execution because of DATA FLOW!
07-30-2018 02:14 AM
@Kyle97330 wrote:
Have a look at this NI newsletter. It covers the overuse of stacked and sequence frame structures and how to replace them.
Even one SSS or FSS is overuse...
07-30-2018 07:17 AM
thanks so much!
07-30-2018 08:29 AM
wiebe@CARYA wrote:Even one SSS or FSS is overuse...
I (mildly) disagree -- one sometimes needs to "tie" a Timing function (such as Wait, or Clock Read) to a specific point in the code, often between two functions connected by an Error Line. "Wrapping" the Time function in a single Frame Sequence and forcing the Error Wire to "tunnel" at least into the Frame is an "obvious" and "intuitive" way to say "Do this now".
Bob Schor
07-30-2018 09:06 AM
@Bob_Schor wrote:
wiebe@CARYA wrote:Even one SSS or FSS is overuse...
I (mildly) disagree -- one sometimes needs to "tie" a Timing function (such as Wait, or Clock Read) to a specific point in the code, often between two functions connected by an Error Line. "Wrapping" the Time function in a single Frame Sequence and forcing the Error Wire to "tunnel" at least into the Frame is an "obvious" and "intuitive" way to say "Do this now".
Sure, but a sub VI would be a better option. Or a case structure, so the wait is skipped when there is an error. I use them (rarely), but usually they get refactored out sooner or later.
07-30-2018 09:16 AM
Agree 100%. My "Delay (ms)" function follows me around "like a little puppy" (quick, who says that?).
Bob Schor
07-30-2018 09:54 AM
@Bob_Schor
@Bob_Schor wrote:
Agree 100%. My "Delay (ms)" function follows me around "like a little puppy" (quick, who says that?).
Even that google will find (first hit at the moment).
07-30-2018 11:38 AM
@Bob_Schor wrote:
Agree 100%. My "Delay (ms)" function follows me around "like a little puppy"
Not really needed now since LabVIEW 2017 with the introduction of the Stall Data Flow.vim.