SubVI appearance problems when upgrading to LV 7 Express

[Panthera395]

I'm updating a LV 6 VI to run with LV7 and a new DAQ card, and when my main VI calls the subVIs the windows are supposed to appear, then disappear once the user is finished. Now with LV 7, either the window doesn't disappear or the program keeps bouncing back and forth between the main VI and the subVI and locks up.

This program works fine on the other computers with LV 6. What's changed?

[chrisger]

hi

there have been changes with the "Frontpanel open" and "Is frontmost" properties of vi-references. also i would check the settings "Open front panel when loaded/called" of your vis. there's more info in the Upgrade notes and the online help of the properties mentioned above in the labview bookshelf.

best regards
chris

[Dennis_Knutson]

I've updated a lot of v6 to v7 and 7.1 without any issues of my pop-up subVIs. It's possible that the recompile exposed an issue with data flow that you were able to get away with before. Are you using any local variables or property nodes to control subVI appearance? Can you post the VI and subVIs so someone can actually look at your code?

[Panthera395]

I don't have a copy of the code with me, but I will get something ASAP.

The basic algorithm is:
executive VI acts as a menu-type window with while loop structure controlled by a "done" button. User uses buttons to select function (such as setting DAQ parameters) The subvi is called in a case structure controlled by the boolean button. Once the subVI finishes execution it disappears and user returns to executive window.

This program will be used by non-Labview-literate engineers, so it has to be bombproof. Is there a better way to do this?

Thanks for your help!

[Ben]

Maybe,

Post some code at let the gang take a peek.

Ben

[Panthera395]

Okay... here's a piece of the whole program. I took out some of the subVIs but left the ones I'm having problems with. The subVI runs fine when you first go into it, but it won't return to the main. It seems like the boolean gets stuck.

Thanks!

[Ben]

OK to start out, try changing the mechanical action of your boolean switches to "Latch When Released".


That will get you started.

I would be out of character if I did not mention that the code you have provided is littered with race conditions. My head was spinning when I was trying to follow the functionality of the sub-VI.

I suggest you post a new question and include your sub-VI and ask,

"ow can convert this VI such that it no longer uses global variables?"

Sorry but I do not have the time this AM to wander into the details.

Trying to help,

Ben

[johnsold]

Try changing mechanical action to Latch when pressed on the booleans.

Lynn

[Dr._Imad]

Hello,

I had to change the mechanical action of the Done buttons in the Set Daq Parametrs...and Confiure DSA Modules vi' s to "Latch when Pressed " or " Latch When Released" to Make it work . Opened it in LV 7.1



Any way, the first thing that got into my mind is having the called vi's being maximized (this is an issue in 7.0/7.1 at times and has been reported to NI). But this is not the case here

[Panthera395]

Thanks to everyone! Switching the button action fixed that problem. I know the subvi's are confusing, but the engineer that wrote them has left and I haven't had time to redo them. Thanks again!!!

-Panthera395