LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Updating old programs from Labview v8 to 2016

Hi all,

 

I'm new to Labview but am tasked with updating all the old programs from v8, 2012 to the latest version, in our case 2016.

Most have progressed fine but I have one which has 8 VIs.

 

Once the executable is deployed and unpacks, it appears fine.

When I run the program executable it opens all 8 VIs filling the screen.

 

The v8 executable opens only 3 VIs, so how can I duplicate that behaviour???

 

I have checked each VI and they all look like this in the VI properties of the VI

Greg1956_0-1582514030509.png

 Any help would be gratefully appreciated.

 

thanks

Greg

0 Kudos
Message 1 of 24
(2,895 Views)

Hi Greg,

 

so there are 8 VIs giving you problems and you want help for them.

What about attaching them? (How should we help otherwise?)

 

Why do you show the execution options when you have problems with the window appearance of those VIs?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 24
(2,845 Views)

Hi Greg

 

You need to look in the Window Appearance category not Execution.

 

Set the VI's you do not wish to appear at run time to 'Default'

 

Niatross_0-1582531658559.png

See this page for more details on the other options, especially those in Custom

 

https://zone.ni.com/reference/en-XX/help/371361R-01/lvdialog/window_properties/

 

0 Kudos
Message 3 of 24
(2,842 Views)

The Execution category is not relevant.

You should rather check the Window Appearance one (especially the Open Front Panel when called option in the Customize dialog). Also, if vi's are called statically (as icons on the  Block Diagram), the SubVi Node Setup should be checked too (right-click on the sub-vi icon).

There may be other subtle effects too, for example in the Build specifications. May you upload project and vi's?

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 4 of 24
(2,841 Views)

Hi Gerd,

 

as I'm very new to Labview I'm unable to attach anything as I don't know what I should have attached.

that is half of my problem.

 

Anyway I'm now off to look at Windows Appearance instead of Execution as pointed out by Niatross and Pincpanter.

 

thanks for yor help.

Greg

0 Kudos
Message 5 of 24
(2,799 Views)

Ok, checked all the other VIs, they are all set to default.

 

the 3 other VIs are set to Custom with these parameters

Greg1956_0-1582595895978.png

Hope that is helpfull.

 

Greg

0 Kudos
Message 6 of 24
(2,796 Views)

Thanks Paolo,

 

some of that I understood but I'm unable to check.

 

Do I just attach my project or all the VIs so you can see them??

 

Sorry way out of my depth here.

 

Greg

0 Kudos
Message 7 of 24
(2,795 Views)

If your VIs are in a Project, and if your Project (and all of its VIs) are all in the same folder, then the usual thing to do is to compress the Folder (which makes a .zip file) and attach that single file.  In your Reply, however, do mention which VI is the "Main" (it is not always obvious).

 

Bob Schor

0 Kudos
Message 8 of 24
(2,787 Views)

thanks Bob,,the main VI is Lab_Monitor_main.vi.

 

The other ones that should be visible are Flowmeter_Main_v2 and Monitor_remote

 

Hope this helps

Greg

0 Kudos
Message 9 of 24
(2,783 Views)

Hi Greg,

 


@Greg1956 wrote:

Once the executable is deployed and unpacks, it appears fine.

When I run the program executable it opens all 8 VIs filling the screen.

The v8 executable opens only 3 VIs, so how can I duplicate that behaviour???


It's nice you finally attached your full project!

 

The problem is: in your AppBuilder Build spec to create this executable you included ALL of those VIs as "startup VIs". No wonder they all open up when you start the executable!

You should only set the main VI as startup VI… (In case you need more than that mainVI you need to include all VIs which should open on start, but this is more a "dirty hack" than "intended design decision"!)

 

Recommendation: The whole program should be rewritten from scratch, it's written in a very bad way…

 


@Greg1956 wrote:

Hi Gerd,

 

Anyway I'm now off to look at Windows Appearance instead of Execution as pointed out by Niatross and Pincpanter.


Didn't I mention the window appearance too in my first message?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 10 of 24
(2,760 Views)