LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does my main VI open some subVIs and not another?

Dear anyone,
 
I have a main menu that has three buttons that open three separate subVIs. The first two open their repective subVIs however the third pop-up and runs it, but is not clickable. The opening options are exactly the same for all subVIs and all are in the same event structure. Im using value change events for all three where the "new Value" is suppose to execute its subVI. I just dont understand why two work and not the third. This is the last thing I need to do finish this project. Please help.  
You wanted the best; you got the worst. Srry.
0 Kudos
Message 1 of 13
(3,280 Views)
It sounds like to me, that is a problem with the sub vi. If it opened, then it is called.  Does it crash on you?  Can you attach your code so we can take a look?
0 Kudos
Message 2 of 13
(3,278 Views)
What do you mean when you say it's not "clickable"? Are you saying it doesn't respond to you pressing buttons on the front panel? Can you post your code?
0 Kudos
Message 3 of 13
(3,277 Views)
I can only guess before you post some code...but do you use some decorations in your sub-vis? If you place a decoration like a border around a button after you created that button, the button is still visible but behind that decoration. Try selecting the decoration and select "move to back"...

Christian

THINK G!! 😉
------------------------------------------------------------------------------------------------
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)
0 Kudos
Message 4 of 13
(3,272 Views)
I can't send you my code but I can send you screen shots. Attached is the screen shot of code for all 3 events. "Search" and "enter test data" events pull their subVIs fine. However calibrate does not. I dont believe it is calibrate's code itself because it is able to open when I try it on a blank VI. I'm sure someone is going to say "make it a dynamic subVI instead of static' however I am unsure of doing so. As well, the path coming in is an UDL path (not a problem).
 
Thanx.
 
P.S. I have also attached the what it what the Cal FP looks like not interactive (not clickable = unable to interact with the FP). And yes it crashes, with no error, everytime I execute the calibrate button.
PSSThe Testlog button is grayed out because it is stipulated that way in the code.
You wanted the best; you got the worst. Srry.
0 Kudos
Message 5 of 13
(3,246 Views)
Please don't screenshots embedded in a word document, it makes a huge file to download.  Post the screenshot as a .png file instead.
 
Check the properties for each of your events.  Is it possible you have the "Lock Front Panel until event completes" for the event that handles the nonclickable VI?
0 Kudos
Message 6 of 13
(3,232 Views)
Hi guy,

can you attach block diagrams without rotating them (I already have neck-aches), without putting them in proprietary file formats and without scaling them?
A simple nice PNG will do it perfectly!

Ok, you want us to help you:
-without supplying enough information
-showing a block diagram using vis by (or programmed for) "Edwards" - we don't know them
-talking about "crashes, when calibrating" - you seem to run some hardware access which we can't analyze from a doc file...



Message Edited by GerdW on 07-29-2008 10:52 PM
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 13
(3,231 Views)
Ok, so after I printed it to pdf and rotated the view.. I can see them.  I can see that you are launching all three vi's pretty much the same way.  Therefore I would start debugging here:  I would probe all of the inputs, make sure everything that is going in is expected.  I would close all of my VI references you made, to clean up loose ends.  Finally, I still would check durring run, that there is not something reacting unexpected in your Calibrate2.vi.  I would turn on highlight execution inside it, and watch it recive the data and see how it handles it.   I'm afraid that's all I can suggest looking at pictures.  Good Luck!
0 Kudos
Message 8 of 13
(3,212 Views)

oK, I'm leaving for today. Tomorrow I will post my VI(s). Does eveyone want me to post all four (main menu, Test, Search and Cal.)? The VIs will still not work however because I have other subVIs inside of those VIs but I post them anyway. 

Thanks drew. All my inputs look fine. I deleted the reference nodes like you said (I found out I really dont need those) and the same problems occur. I cant check during run because I am unable to interact with Cal2.vi and the system crashes. I check the event properties and my FP isn't locked. I'm still lost. But I'll get those for you and everyone tom.

Oh and GerdW, your not obligated to help me. Just tell me what you want and I'll try to comply. No need to give a newbie a hard time. 

As well, I wont ever send ScreenShots like that again. For that I am sorry.

You wanted the best; you got the worst. Srry.
0 Kudos
Message 9 of 13
(3,204 Views)
Hi guy,

I'm not obligated, but I'm willing to helpSmiley Wink

"No need to give a newbie a hard time." - That wasn't my intention. But as you read from other reply too using Word to show pictures isn't much appreciated here in the forum. And the sooner you can supply helpful information to describe your programming problems the better for you!

Back to topic:
How does your system crash? Is the problem in the subvi?
Is there a reason to call those vis using vi server instead of putting them as subvi in the main vi? You only set some properties which can be set in the vi too...
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 13
(3,170 Views)