LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Subpanels and popup question (labview 7.0)

Solved!
Go to solution

I tried your option, it worked; but it opened in a popup windows and not in the subpanel window.

 

kinda beats the  purpose of the subpanel

Best regards,
Krispiekream
0 Kudos
Message 11 of 25
(1,237 Views)

You didn't include a couple of VIs (LimitChecker & Ref FGV) in you previous posts. So I made a VI to call the MSG vi in a sub panel. This works in LabVIEW 2017. You may need to modify it to work in your version.

 

main_caller.vi

main caller.png

 

PopUp Msg in Subpanel.vi

popup message in subpanel.png

 

 

Download All
Message 12 of 25
(1,229 Views)

thanks for the advices. I am downloading labview 2017 and see if I can run the vi you sent.

I cant see the labels of the invoke nodes so I don't know what it is.

 

Best regards,
Krispiekream
0 Kudos
Message 13 of 25
(1,216 Views)

Capture.PNG

 

I am not too sure if its possible to do so in labview 7.0

I am going to play with it and see.

Best regards,
Krispiekream
0 Kudos
Message 14 of 25
(1,213 Views)

i tried it on labview 7.0. it doesn't work for me 😞

Best regards,
Krispiekream
Download All
0 Kudos
Message 15 of 25
(1,202 Views)

Capture.PNG

i SAVED AS LABVIEW 8.0

Best regards,
Krispiekream
0 Kudos
Message 16 of 25
(1,184 Views)


Yeah. I don't think the Wait on Asynchronous Call was available in LabVIEW 8.0. Is there a Call by Reference node? If so, that should also work.

 

Capture.JPG

Message 17 of 25
(1,176 Views)

If you use the Call By Referecne node, read the help file. You need to use a Strictly Typed Reference to display connector pane of the taarget VI in order to access the input/output terminals.

 

Again, the snippet above worked in LabVIEW 2017. Hopefully, it will work for you in 7.0

Message 18 of 25
(1,171 Views)

 

Capture.PNG 

I am not sure how to get Call by Reference Node to work.

What do I need to? Sorry. I tried going through the help but with no luck 😞

Best regards,
Krispiekream
0 Kudos
Message 19 of 25
(1,157 Views)

I tried it a few different ways using the Call by Reference, but they all didn't work. The only way is to use a Static VI Reference that is Strictly Typed (located in Application Control).


You can't wire an absolute Path to the Open VI Ref. But instead you can browse for the VI by right clicking the VI reference. It looks like all your paths are hard coded anyways, so this should not be an issue to open multiple VIs.

 

capture.png

Capture1.PNG

Message 20 of 25
(1,122 Views)