boolean property node problem - doesnt save

[B Harrington]

I have a sequence in my VI. In each sequence there is a for loop and while loop. In each loop is a sub VI that checks the values I am collecting to see if they are above a certain value. The while loop will run until I turn it off, then it goes to a do loop to collect 100 values and take an average. If the values are too high my sub VI puts out a true or false reading. The true or false I have connected to a property node of a Boolean round LED (I have a property node in each loop for the LED so I can constantly monitor these numbers), which makes the LED visible and flash. This runs fine until I hit the save button, then LV doesn’t respond and I have to restart LV. To work around this I put in a case structure that respo
nds to the true or false... and the response is simply a true or false to the property nodes. If I do this it saves and works fine... Why does it do this? I don’t like having case structure that simply takes a true or false and puts out a true or false. Any reply would greatly be appreciated, thanks in advance
BLH

[mikeporter]

Sounds like a bug to me... Have you called NI?

Mike...

[B Harrington]

nope... i havent called NI... i figured i was making a dumb mistake and someone could put me on the correct path

thanks for taking the time to read my post

[arussell]

"B Harrington" wrote in message
news:506500000008000000B07E0000-1042324653000@exchange.ni.com...
> I have a sequence in my VI. In each sequence there is a for loop and
> while loop. In each loop is a sub VI that checks the values I am
> collecting to see if they are above a certain value. The while loop
> will run until I turn it off, then it goes to a do loop to collect 100
> values and take an average. If the values are too high my sub VI puts
> out a true or false reading. The true or false I have connected to a
> property node of a Boolean round LED (I have a property node in each
> loop for the LED so I can constantly monitor these numbers), which
> makes the LED visible and flash. This runs fine until I hit the save
> button, then LV doesnR
17;t respond and I have to restart LV.

Why are you saving while the vi is running? I think you should always save
first, and then run it.

> To
> work around this I put in a case structure that responds to the true
> or false... and the response is simply a true or false to the property
> nodes. If I do this it saves and works fine... Why does it do this? I
> don’t like having case structure that simply takes a true or
> false and puts out a true or false. Any reply would greatly be
> appreciated, thanks in advance
> BLH

[B Harrington]

i guess i worded that wrong, i have ran the program before saving it.. and it works fine... then i try to save... and LV hangs on me.. i have never considered saving a vi when it is running, but i guess people do strange things some times.. thanks for the reply

[mikeporter]

Bottom line is that nothing you do during development should stop LV from being able to save the VI--even doing a save while the VI is running (which by the way works fine...).

Mike...

[arussell]

"B Harrington" wrote in message
news:5065000000050000003FE00000-1042324653000@exchange.ni.com...
> i guess i worded that wrong, i have ran the program before saving it..
> and it works fine... then i try to save... and LV hangs on me.. i have
> never considered saving a vi when it is running, but i guess people do
> strange things some times.. thanks for the reply

I kind of suspected that, but it's also too weird that the vi would save
with an extra case statement but not without it. OK, here is another idea.
Is there any wiring (or functions or structures) that you delete before you
add the case statement? Sometimes pieces of diagrams get corrupted somehow.
If that's the case then try deleting that part and reconstructing it.