LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem building a simple 2x VI application

Hello,
 
After 5 years of pause (LV version 6.1) I tried to build a simple application under version 8.2. the application is consisted of 2 simple VIs - the 1st gathers some keyboard input and passes some strings and a VISA Resource (COM port ID) to the 2nd that should capture single chars from a specified COM port and executes simple command lines. The 1st VI triggers the 2nd by passing the corresponding parameters. The problem is when I build the standalone EXE with the 1st VI as a top - the 2nd one fails to open its window allthough its instance shows up on the task bar!?
 
I guess I am messing with the build-settings but can't find a sollution. Can anybody suggest one?
 
Thanks in advance,
0 Kudos
Message 1 of 6
(2,801 Views)
Hi golu...,

have you set the vi properties correctly? The 2nd vi is probably called as simple subvi...
So in the window appearance properties you have to enable 'show front panel when called' and 'close front panel when finished'!


Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 6
(2,800 Views)

Hi Gerd,

Thank you for the prompt response. I did look for those two as I am used to them for the previous LV versions. However I see no such in the LV 8.21  build wizards?! Can you check it out?

 

0 Kudos
Message 3 of 6
(2,797 Views)
Hi golu...,

normally it's sufficient to set the properties in the vi.
In LV8.20 build dialog it's the tab 'source file settings' where you may change the vi properties again.
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 4 of 6
(2,794 Views)

Gerd,

You were right, thank you so much! I have another question - how can I make the 1st VI (the caller) to shut down after the 2nd becomes active? I'd like the 1st to go away since it only passes input parameters and is not needed afterwards.

Thanks again,

0 Kudos
Message 5 of 6
(2,790 Views)
Hi golu...,

as the 1st vi will call the 2nd as sub-vi it will stay in memory as long as the 2nd vi is running.
Solution:
When the 2nd vi is called, wire the needed constant to a property node 'Front panel window: State' of the vi!
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 6 of 6
(2,778 Views)