Probe windows disappear on Block Diagram

Hi all,
I came across an odd issue yesterday using the probes in Labview 2011. When I attach a probe to a wire and leave the probes inside the probe window they seem to work fine, however as soon as I launch the probes as separate windows, then click the title bar to move it to a convinient place they seem to disapear from the block diagram. Once this happens the probes no longer function and simply retain the values they had before they removed themselves.
I have attached a couple of images to show what I mean:
probe-window.jpg shows everything working as normal with the values in each probe acquired correctly.
separate-window.jpg shows what happens when I launch the probe windows and try and move them. They disappear from the BD and no longer function as probes.
Not a major issue I know but one I find very annoying as I like to move the windows to meaningful positions to clearly tell me which wire the values are coming from on the BD. I couldn't find anything similar on the forum so I don't know if I'm the only one with this problem, but it definitely did used to work!
Any ideas?
Attachments:
probe-window.jpg ‏81 KB
separate-window.jpg ‏98 KB

I can't replicate the condition. Have you tried to run a repair on your LabVIEW installation?
By the way, there is a much simpler way (and more scalable) approach to accomplishing what you are trying to do:
Attachments:
string to array.png ‏18 KB

Similar Messages

My scrollbars disappear when resizing my LabView8.6 Block Diagram window

My design can't be seen in it's entirety within the Block Diagram window so I need to use the vertical and horizontal scrollbars to navigate the design. The scrollbars disappear if I resize the Block Diagram window past "some point". If I shrink the window very small, the scrollbars reappear. Other programs I've generated don't seem to have this problem. Any suggestions?

Hi,
Check the scrollbars settings, right click on vertical/horizontal scrollbars and change the settings. If the problem still exists, U can send me ur vi, let me have a look to know the exact problem.
regards
sunil

Front panel / Block diagram sometimes disappear

Hi, I am running LV7 on Windows XP. When I have a few windows open
with front panel and corresponding diagrams, some of those windows
disappear after being minimized or put in the background. When I try
to restore the window,Ctrl-E or task bar, only the function- and tool
palettes get focus.
This is very annoying! please help
/Pelle
PS. I hade the same problem with LV6.1"

Here is the answer.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Labview: Null Window ... stopped at unknown on the block diagram

Hi,
I have a fairly large program that was written in Labview 6.0. Recently we upgraded to Labview 9.0 and this program was exported to an executable with the new version.
When running the executable I sometimes get the following error as seemingly random places. I have not been able to make it crash when not using the executable. Labview: Null Window. The top-level VI ".vi" stopped at unknown on the block diagram of ".vi"
I apologise for having to blank out the vi names but i cannot give vi names, say what the software is used for or give over code. I can say that it uses NI USB 6212 IO cards, interfaces with Rhode and Swartz instruments and uses alot of file IO.
I was hoping that someone could give me a hint on how to debug such an error. I have noticed that When this error occurs, the memory use almost doubles.
Thankyou
James
Solved!
Go to Solution.

I think you open the front panel of a VI that has it's front panel removed during the build. Try to adjust the built settings of that specific VI to include the front panel.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Fit block diagram to window

This might be a stupid question, but how do I fit the block diagram of my vi to fill the screen (kind of like a "zoom out" feature)? I want to take a screenshot of my current block diagram in its entirety, but the vi is fairly large. I can't seem to find the option to do this.

You could also use a tool such as discussed in the following thread to save an image of your BD:
http://forums.ni.com/ni/board/message?board.id=170&message.id=124219&query.id=0#M124219
(I beleive there is also a similar thread to show how to add this as a custom tool to the LabVIEW menu.)
Message Edited by altenbach on 06-23-2006 10:02 AM
LabVIEW Champion . Do more with less code and in less time .

Mathscript Probe Window (LV 2009) Not listing all variables

Please see the screenshot below. The Mathscript probe window is shown on the right of the VI block diagram. The execution is at the breakpoint on the last line (blue arrow).
Why is input variable "a" not listed in the probe window? I see this behavior that some variables are not listed in the probe window.
Thanks,
AJ

Hi AJ,
There are a couple of things that may be going on when variables fail to appear in the MathScript Probe. The first is a bug with the MathScript Probe in 2009. Sometimes input variables either fail to appear or briefly appear then immediately disappear. The good news is that this bug (CAR #182784) is scheduled to be fixed in the next service pack release of LabVIEW. I'm not sure if Nickerbocker's workaround will work. If it doesn't, you could also try adding "a = a+0;" to the top of your script.
Another occasion where variables will fail to appear is if they are defined within your script but never used. This case is analagous to placing a constant on a LabVIEW block diagram and not wiring it to anything. In this situation, there is no wire to probe; the only way to see the value at run-time is to look at the code itself. It's a similar situation when you define a variable in MathScript without using it; the MathScript Probe cannot report the variable because it doesn't have a corresponding "wire" so you have to look at your MathScript node to see the value.
Please let us know if you notice missing variables in situations other than the above two cases.
Thanks,
jattas
LabVIEW MathScript R&D

Unresponsive block diagram

When I run my VI, a traditional State Machine, I cannot use any of the buttons on the block diagram toolbar, or probe the block diagram. Nothing on the block diagram is accessible, so I opened each state in a separate VI to see if the problem followed, but it goes away. This issue seems to only occur with this particular VI, but I have no idea how to troubleshoot it. I am currently running 8.5. Thank you.
Solved!
Go to Solution.

NIPEN wrote:
Seems that my FP was modal not default, which caused all my problems. Thank you very much to those that tried to help me.
That makes some sense. Modal FP means that no other LabVIEW window will be allowed to get focus unless the window is minimized. Hence, although your mouse can move over the BD you get no clicks just bongs. Thanks for posting the solution!
Jeff

Show block diagram programmatically?

I'm almost sure that I did this once and then took it back out. (the "show block daigram" case in the Menu Selection choice of an event structure is still in my code).
Anyway, I often start a program that runs for hours and then realize that I need to open subVIs or probe some wires. Since these programs have run-time menus I don't have the option to open the diagram once the VI is running. Is there a way to programmatically open the block diagrams window when a VI is running?
Thanks,
K
Message Edited by NIquist on 09-20-2007 03:39 PM
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Shhhh......
Its a secret.
But now that you know then you can appreciate the beauty of these items.
The ini used is one of the few time that LabVIEW programmer cares about proper syntax.
OR (to take this analogy way to far)
It is THE "G-String"
Ben
Discalimer: I am a Premium LAVA Member
Message Edited by Ben on 09-21-2007 07:26 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Attachments:
G-String.jpg ‏40 KB

Block diagram wont open properly

I have written a big labview program for my application. I have been workig on it for 6 months. I keep adding the peice of code every day and save it with a new name every week.
At one point when I added some code into my program, the block diagram started acting weird and wont let me work on the program easily. For If I add an add function, it would take time and insert this function a couple of inches away where I pionted my cursor. Another issue was that; if I add a while loop or for loop or any other structure it would take time and one added it would add a couple of inches away and expand the main program window (Block Diagram) too.
since then, I started using my company's laptop to develop the code. I have no issues with that lap top till today.
But now when I tranfer this program back to my desk top. It wont open the Block Diagram and wont let me edit it. When I try to open the block diagram. the window appear black out and the LabView stops working.
Is this issure ralted to the graphics of my compute or any thing else? Please help me. Thanks
Mansoor

There is a maximum size that a VI can be. What that exact size is I don't know. It does sound like you have one HUGE VI. If that is the case you really need to think more about using subVIs. It will make your program much easier to maintain and extend.
Also, rather than renaming it once a week you should consider using source code contol. Even if you are the only developer it is a much better way to manage your code. SVN is free and very easy to set up. If you do use source code control make sure you separate the compiled code from the source code. This is an option in the VI properties.
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

How to add text to the block diagram

How do you add plain text to the block diagram for documentation and can I change the background color to yelllow or something else that may be helpful? see image below
Windows is a 64 bit extension to a 32 bit graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. Byte that Microsoft!
Solved!
Go to Solution.

Just double-click in an emtpy area and start typing. Use the coloring tool to color the text background.
(there is also a "free label" in the decorations palette, but that seems like a detour )
LabVIEW Champion . Do more with less code and in less time .

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
Solved!
Go to Solution.

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

Can I just open block diagram only

Like I can have only front panel opened. Reason is when I have bunch of VIs
open, I get too many windows to manage even while using 2 monitors. It will
be nice if I can just have the window for block diagram open, if I need the
front panel while editing, I can use Ctrl+E to open it. I know I can
minimize but then all LV windows look same on task bar. Would be nice if
icon of the VI showed up on taskbar buttons of each VI.
vishi

You can use lvwutil/Hide window.vi to hide the front panel.
This method has been around for years.
vishi anand wrote:
> Like I can have only front panel opened. Reason is when I have bunch of VIs
> open, I get too many windows to manage even while using 2 monitors. It will
> be nice if I can just have the window for block diagram open, if I need the
> front panel while editing, I can use Ctrl+E to open it. I know I can
> minimize but then all LV windows look same on task bar. Would be nice if
> icon of the VI showed up on taskbar buttons of each VI.
>
> vishi

Automatically open block diagram on extended monitor?

Hello,
I was wondering if anybody know how to pop-up the block diagram on an extended monitor automatically so that ctrl+E need not be pressed to shift between FP and BD. It would be nice to see FP on monitor 1 and BD on monitor 2(ext). applicable to opening any number of VI/subVIs. (not needing to drag window to ext monitor either)
Thanks in advance,

See page 2 of this thread: http://forums.ni.com/ni/board/message?board.id=170&thread.id=102680&view=by_date_ascending&page=2

Nugget: Open block diagram programatically

There are a way to open a block diagram programatically. Exists a undocumented function located in
"%Program Files%\National Instruments\LabVIEW 8.6\vi.lib\Utility\sysinfo.llb\Set Block Diagram Open.vi"

My good old 7.1. (ok, I run that in hyper-boost mode ) has a property node 'VI.Block Diagram Window.Open'. Should be available for anyone and documented in 2010.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Is Block Diagram Open

Is there a way to tell if the Block Diagram is open when a VI is started? I have a subVI that is set to modal when open. When trouble-shooting, if I run my application, but forget to disable modal for the subVI it causes the system to lock up.
It would be nice if I could set the property of the VI to not be modal if the block diagram was open.
Any suggestions?
Solved!
Go to Solution.

I would attempt this by doing several things:
1) Go to the VI Properties>Window Appearance and click on the Customize button. From there uncheck the "show front panel when called" box.
2) When the VI starts, read the VI Property "Front Panel Window.State" - this will tell you if the window is already openned (ie if the window is openned the window state will be "standard", "Maximized" or "Minimized"). Note: this is the visibility of the front panel, not the block diagram
3a) If the VI is not already opened, set the "Front Panel Window.Behaviour" property to modal and then open the front panel using the VI Invoke Node of "Front Panel.Open". This is basically mimicking the behaviour you describe right now.
3b) If the VI is already opened, set the behaviour property to default or Floating to allow you to click other windows.
4) When finished, if the VI was not already openned, manually close it using the Front Panel.Close invoke node (if it was already openned, leave it openned)
I've attached a screen shot of this kind of thing. I hope this helps,
Shaun
Attachments:
Reading and Changing Front Panel Behaviour.png ‏39 KB

Probe windows disappear on Block Diagram

Similar Messages

Maybe you are looking for