NI Home > Community > NI Discussion Forums

LabVIEW

Showing results for 
Search instead for 
Do you mean 
Reply
Member
vgravel
Posts: 122
0 Kudos
Accepted Solution

Can't see block diagram of an auto-running VI

Hello,

 

I have an old and dirty VI that runs automatically when opened. I cannot see the block diagram because when I stop it, LabVIEW shuts down. There is probably that 'evil' function Stop LabVIEW at the end.

 

Is there a way to avoid that behavior?

 

The VI was written a while back in LabVIEW 7.0.

 

Thanks for the help!

 

Vincent

Knight of NI
Knight of NI
Ben
Posts: 16,133

Re: Can't see block diagram of an auto-running VI

Drag it into a the BD of another VI and double click it from there or...

 

Find one of the VIS it calls and break it first or

 

There may be other ways...

 

Ben

Ben Rayner
Who is NOT John Galt... yet... just building Rayner's Ridge
Scheduled to close on the new ridge next week!
Member
vgravel
Posts: 122
0 Kudos

Re: Can't see block diagram of an auto-running VI

It work!

 

I dragged it in anoother VI BD and opened it from there... I really can't think of a worst way to shut down a VI... It should be illegal!

 

Thanks!

 

Vincent

Knight of NI
Posts: 18,064

Re: Can't see block diagram of an auto-running VI

Well, some people think that the GOTO statement was evil and should be illegal. Some think that C pointers are evil and should be illegal. Some think that local variables are evil and should be illegal. Some think that sequences are evil and should be illegal. ....

 

Me? I think that "reality shows" are evil and should be illegal. Who's with me? :smileyvery-happy:

Knight of NI
Knight of NI
Ben
Posts: 16,133
0 Kudos

Re: Can't see block diagram of an auto-running VI

I'm with you 110%

 

I barely have enough time for my own life let alone watching some elses ahem life. I think Plato's Socrates would have thought similarly and advocated outlawing artist in general. I think it was book X of THe Republic or there abouts.

 

Ben

Ben Rayner
Who is NOT John Galt... yet... just building Rayner's Ridge
Scheduled to close on the new ridge next week!
Trusted Enthusiast
LV_Pro
Posts: 3,073
0 Kudos

Re: Can't see block diagram of an auto-running VI

[ Edited ]

One other possible trick to stop the vi without it exiting might be, on Windows machines, to do a "Ctrl ." (holding the CTRL control key while pressing the "period" key)

 

Not sure there was a "Book X", don't think the Greeks used Roman numerals! ;-)

Putnam
Certified LabVIEW Developer

Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5


LabVIEW Champion



Member
vgravel
Posts: 122
0 Kudos

Re: Can't see block diagram of an auto-running VI

Nice, didn't know the "Ctl" trick... I will remember this one for sure!

Thanks!

Knight of NI
Knight of NI
Ben
Posts: 16,133
0 Kudos

Re: Can't see block diagram of an auto-running VI

Brace yourself... Its all Greek to me.

 

From here

 

Socrates (Plato) focuses on Poets (They wrote the scripts) saying;

 

"

But worst of all, poetry weakens the mind by leading us to sympathise too deeply with the afflictions of others, and thus rendering us unfit to bear up under our own troubles.

"

 

Ben

 

 

Ben Rayner
Who is NOT John Galt... yet... just building Rayner's Ridge
Scheduled to close on the new ridge next week!
Knight of NI
Posts: 18,064
0 Kudos

Re: Can't see block diagram of an auto-running VI

 


vgravel wrote:

Nice, didn't know the "Ctl" trick... I will remember this one for sure!

Thanks!


It's all in the Quick Reference Guide. :smileywink:

 

Trusted Enthusiast
Mark_Yedinak
Posts: 3,055
0 Kudos

Re: Can't see block diagram of an auto-running VI

 


LV_Pro wrote:

One other possible trick to stop the vi without it exiting might be, on Windows machines, to do a "Ctrl ." (holding the CTRL control key while pressing the "period" key)

 

Not sure there was a "Book X", don't think the Greeks used Roman numerals! ;-)


I have actually seen cases where this doesn't work. Most of the time it happens when in a producer/consumer architecture where the exit logic is not correct and the loop with the event structure exits and the consumer is waiting for something to happen. I was aware of the "Ctrl ." abort but have been forced to kill LabVIEW because the abort wasn't processed.

 



Mark Yedinak

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot