Front panel booleans disconnected from block diagram

[PiMaster]

This is very odd behavior that I've never seen before.

I've opened a program that I've used before that is working, after replacing some DLLs that are called.  I don't know if that's relevant, but just in case.

Anyway, I have an event structure in a loop.  The events are to toggle some output values in a bitmap, and to update some inputs.  As you can see in the screenshot of the timeout loop, the values from the input bitmap are being fed directly into the boolean indicators.  The problem is that even when the wire is true, the front panel doesn't update.  Also, when I click on the stop button, the boolean value on the wire doesn't update.  You can see that from the screenshot of the probes and the front panel.

At no point have I explicitly stopped front panel updates.  Indeed, the Status indicator updates appropriately.  But it does that from a subVI.  If you pass a reference to a front panel indicator into a subVI, does it lock the front panel for any reason?  I thought for sure I'd done this multiple times in the past without a problem.

I'd rather not post the VI publicly without further redactions.  Just company proprietary stuff.  I wouldn't be against sending them to an NI person, though.

Thanks for any assistance.

[JÞB]

Sound like a race.  are there any referances to the control or Locals?  (possibly a property is reseting the bool so fast you can't see it)

[PiMaster]

I'll double-check when I'm back at work, but I'm almost certain I didn't create any property nodes or local variables.

[JÞB]

Thats OK, Hieracahy view> Find select VI

And Right click on the object >Find...term, refeances, P-nodes.... will disprove my hypothisys.................You are pretty sure?   let us see some code!

[bradyAE]

hi pimaster,

    if you could post the VI i will try debug it if incase of any problem with the program. Else we will look for the proper solution.  

[PiMaster · Accepted solution]

It was apparently a transient condition.  I came in, opened LabVIEW and the VI, and everything is fine now.  I know how that looks, like I came back and found some property nodes overwriting values.  I promise that I did not change anything.  I should have tried doing that yesterday, but it was the very end of my day at that point and I had somewhere to be.

If you want, bradyAE, you can send me your email address and I'll send you the VI, if you think there's value in investigating it.  Like I said before, I'd rather not post it publicly.

[JÞB]

Sounds like you are running.  (Perhaps the equivallent of a BD artifact?)  If you ever can repeat the "glitch" let us know..... (I'd love to see it fixed if it can be reproduced)

[PiMaster]

Will do.  Thanks for the help.

[bradyAE]

hi pimaster

Its good your problem got resolved. Continue to be active in DF.

thankyou

bharathwaj

[Yamaeda]

My guess is that the Stop button has been activated thus you never get into the timeout. 🙂

If it's a subvi it wont reset causing future calls to fail.

I always use a Stop:Value change-event and place the button there.

/Y