LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Darren's Occasional Nugget 01/05/2018

Thank you Darren for bringing that up to the community.

 

And re-starting the debate on "Wait with Error Functionality"

 

I've had a fairly bullet-proof routine around for a long, long time. available in the code sharing repo.  

I took the time to publish an update over here as their have been some improvements made over the years.

Cosmetically, its nicer Seconds to Wait is now a DBL, and the original was never "In-lined" since that was not available back then.Delay.png


"Should be" isn't "Is" -Jay
0 Kudos
Message 11 of 24
(2,740 Views)

How difficult would it be to add a Boolean input into the bottom of the Stall Data Flow.vim ?  Have the Boolean if unwired, resume the current state of 'delay regardless of error' ; otherwise, on the change of the Boolean state have it skip delay on error.

 

Just my $0.02

Help the Community (and future reviewers) by marking posts as follows:
If it helped - KUDOS
If it answers the issue - SOLUTION
0 Kudos
Message 12 of 24
(2,662 Views)

@Minions wrote:

How difficult would it be to add a Boolean input into the bottom of the Stall Data Flow.vim ?  Have the Boolean if unwired, resume the current state of 'delay regardless of error' ; otherwise, on the change of the Boolean state have it skip delay on error.

 

Just my $0.02


So, do it!  Rename it and place it in your personal reuse library.  No need to muck up a perfectly functional and well documented vim in vi.lib


"Should be" isn't "Is" -Jay
0 Kudos
Message 13 of 24
(2,659 Views)

True!  And you don't have to include it in your Project, as it's on the Quick Drop menu.

 

BS

0 Kudos
Message 14 of 24
(2,499 Views)

How's this?

Separate data flow and error flow.

If you want unconditional wait, wire to "Data In", leaving "error in" unwired.

If you want to wait only if there is no error, wire to "error in"

Also, time value is independent of units.

"If you weren't supposed to push it, it wouldn't be a button."
Message 15 of 24
(2,455 Views)

@paul_cardinale wrote:

How's this?

Separate data flow and error flow.


I would probably go the route of just not waiting on an error and use the new Type Specialization functions.  Only one set of controls instead of 2.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 16 of 24
(2,429 Views)

@crossrulz

 

I like your mod, but why not take it one step further and also use the other new Type Specialization function. That way you can use an error wire or any other wire if necessary.

 

mcduff

snip1.png

 

snip2.png

 

 

 

 

 

0 Kudos
Message 17 of 24
(2,383 Views)

@mcduff wrote:
I like your mod, but why not take it one step further and also use the other new Type Specialization function. That way you can use an error wire or any other wire if necessary.

I did.  Did that not come through when you opened my VIM?  I did do a save for previous to get it into 2017, so it is possible it was lost.  Just checking really quick, and I see it in the VIM I posted.

 

EDIT: Ok, I see it now.  The Save For Previous changed the Type Specialization Structure into a Diagram Disable Structure.  Attached is my original 2018 version.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 18 of 24
(2,365 Views)

I was wondering why that disable structure was there, good to know Save for Previous changes some things about VIMS.

 

mcduff

0 Kudos
Message 19 of 24
(2,356 Views)

@FabiolaDelaCueva wrote:

Where do we start the campaign and signature gathering to convince Jeff K that we should make it not wait if there is an error in?


Here: Stall Data Flow should be a no-op in the event of an error


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 20 of 24
(2,017 Views)