LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Property Node causing lockup in 6.0.2

Among other things, my application has a spectrum analyzer loop responsible for setting the parameters and reading back the traces. It has been working fine for months. This morning I added an addition property node inside a case statement within the loop and it caused the loop to hang up, giving me the "resetting the vi" message when I tried to stop the program with the abort button so I had to kill the task with the task manager (windows xp). If I replace the property node with the terminal node everything works fine. With the property node, it even locks up if the property node is not wired to anything but it is just sitting inside the case statement. I havent had any problems in the past using property nodes so I was
wondering if anyone has any ideas about what the problem could be. I have attached an image file showing the case statement in question wired in the non-working and working configurations. thanks
0 Kudos
Message 1 of 3
(2,769 Views)
First, this is a very bad use of a property node. The control itself, or a local variable is what you want to use. A property node for the value is primarily used to communicate between VIs, and not as a substitute for a local variable.

Second, I think that this may be your problem. The alternative certainly fixes it. You may have encountered a bug, or it may be how they work.

Try using a local variable instead. The local variable will allow you to locate the control outside the loop (make it an indicator, and wire a default state to the control) and really makes your program neater.
0 Kudos
Message 2 of 3
(2,769 Views)
I agree. Local variables are definitely better than property nodes for changing values of the objects in the front panel. Although, excessive use of LVs can lead to max memory usage and slow down the program. The only problem I see is: what if one wants to change properties other than the value of the FP objects, say the background color of a temperature control?
I've found out that the best thing to do is to avoid using numerous property nodes (multi-channel read)in case and sequence structures which are embedded inside FOR or While loops.
0 Kudos
Message 3 of 3
(2,769 Views)