03-15-2012 05:26 AM
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?
03-15-2012 06:08 AM
This seems weird. Did you check again with the same way and is it happening consistently? If yes try copying the code to a new vi and repeat the same. I don't have the answer for that but am also curious to know what is the reason behind this.
03-15-2012 08:49 AM
@P Anand wrote:
This seems weird. Did you check again with the same way and is it happening consistently? If yes try copying the code to a new vi and repeat the same. I don't have the answer for that but am also curious to know what is the reason behind this.
I initially noticed it happening in a different VI but it happens in any VI instance I open i.e. the one shown in the attachments. It is as though once I launch the probes from the main probe window they are no longer are part of Labview. I haven't installed anything new recently on my PC and I use probes in this manner all the time so I can't think why this problem is occurring.
03-15-2012 09:26 AM - edited 03-15-2012 09:27 AM
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:
