executable does not open dynmanically loaded vis

[harene.pitter@tripointglobal.com]

I have an ATE that is in vi form and works fine in this manner. It runs tests that are chosen by the user but the tests are not subvi's with in the program, they are called dynmanically by a vi that locates, opens the vi being called and closes when comlete. I tried to create an executable for the ATE, including the dynamically loaded vis, but when I try to run it, the test in progress does not appear or execute. What could I possibly be forgetting?

[Photon_Dan]

You may be forgetting to tell the App Builder not to remove the front panels of your dynamic VIs. Otherwise, you may also be looking for those VIs at an incorrect path. When the App is built, the VIs are included in something very much like a LabVIEW Library (LLB). Depending on how you build the path to your dynamic VIs, when the App is built, it could be broken. I always call a dynamic with another VI that will ALWAYS be in the same folder. That way the calling (or reference opening) VI can examine its own path, strip one level, and build the name of the dynamic. It will work the same way in development or compiled executable form.

Alliance Members like us do this stuff every day. Contact us if you could use some more extensive help and support.


Daniel L. Press
PrimeTest Corp.
www.primetest.com

[Jim_Kring]

Dan's anwer is probably the solution that you are looking for. To prevent this problem from happening, you can place an owned "implicitly linked" property node, associated with a Front Panel Control, on the block diagram of your VI. This will cause the Application builder to automatically preserve the front panel during an App build. It is so hard to find and remember to change the individual VI build settings on a per build basis.

Best of luck,

-Jim

[harene.pitter@tripointglobal.com]

The second time I tried to create the executable, I tried to change the vi settings of the dynamically loaded vis.
After changing the "Show Panel" and "Open When Running"to "yes" on all the test vis, it seemed as if the settings didn't
change at all and it still did not work.
All of my test vi's and subvi's associated with the ATE are in the same folder.
I do have support text files that are loaded depending on the UUT type. Do I need to include those too?
And the vi that calls the dynamic vis is a part of the top level vi. Even though it is are you saying that I should include it as a top
level vi?

[Evan]

How are you creating the path to the dynamic VIs? Are you stripping the path 1 time or 2? You need to strip it twice in the exe and once as a development VI.

[Jim_Kring]

The setting that Dan recommended is an setting in your build file, not a setting in the VI. You need to tell the Application Builder to not remove the front panel of your dynamic VI.

[harene.pitter@tripointglobal.com]

Stripping my dynamic vi path? I selected the dynamic vi to be included after pressing the "Add Dynamic VI..." button. All my VI's associated with the top level vi are in the same folder, location,as the top level vi.
OK....I'm half way there. I was able to get the dynamic vi's to execute but now I have an issue with templates. The test result data is stored in two places, temporarily in globals, for the short term tests as well as in a designated network location for the, more time consuming, temp-cycle data. The data is retreived when requested by the user and inserted into a template, using bookmarks, then printed. I included the templates in the "Add Support Files" as well as other important text files associated
with my program.