How can I run dynamic reentrant VIs in EXE Applications?

[CleanerTM]

I want to run a dynamic loaded, reentrant untyped VI in an LabVIEW application, generated with the application builder.
I must use the VI function "Run VI" because the VI is used untyped, but when trying to run, LabVIEW returns the error 1013:

    "Cannot load front panel. Make sure you include the front panel of the VI when building a stand-alone application. "

I allready made shure, that the dynamic VI is part of the Application and inside the EXE File. It is definitly loaded into memory.
Curious, in development eniroment, this works fine.

Does anyone know a conclusion or is this a bug? Thanks a lot !

[Ben]

You wrote

"

It is definitly loaded into memory.
Curious, in development eniroment, this works fine.
"

I will assume the VI path is correct and the VI that is supposed to load the dynamic VI is working correctly and that "False" constant you have wired to your case selector is really true in the EXE.

Because the two fragments of code A) The reentrant loader, and B) The reentrant runner are not tied together via data dependancies, LV can and will compile these two fragments as distinct and attempt to optimize performance by allowing them to execute in paralel. As such, there is no guarentee the loader will run before the runner.

So...

1) Make sure your path is correct in your loader,

2) Make sure your false is true,

3) Use datat dependacies to ensure the loader runs before the runner.

Ben

Message Edited by Ben on 10-15-2005 02:34 PM

[Ben]

Also check the remove FP setting in the builder.

Ben

Message Edited by Ben on 10-15-2005 07:42 PM

[CleanerTM]

Thanks for the tipp, I tried to turn the "Remove Panel" option to "No", but after starting the exe application, it hangs up now... don't know why

The Case structure is correct, it was meaned to load the VI into memory (because the subvi becomes part of the hierachy and gets automatically loaded into memory) but I removed it now to avoid side effects and used conventionell ways with a path.

I did more testing and found out, that this problem occurs only on untyped Refs., reentrant VIs, when using the "Run VI" function.

I put the test results and some explaination to the case structure ;) into the attachment, please watch it, i put some time on it.

I currently have no clue how to get along with this problem.

Karlos.

[CleanerTM]

Ups... i found some mistakes in the attachment, sorry about that. Here is the correction.

[Ben]

Hi CleanerTM,

I read through your doc and from what you said "I tried to turn the "Remove Panel" option to "No", but after starting the exe application, it hangs up now... don't know why
" that you are no longer dealing with 1013 error.

Since you have a true wired to the "wait until done" the hanging could be correct if the dynamic VI is hung.

Ben

[Ben]

The following was posted to Info-LabVIEW about 2 years ago.

This may help.

"

Michael,

As far as I can see, you have problem similar to one I met during beta testing. I reported it to NI staff and got rather good clarification. By default, LV7 AppBuilder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. If some VI in your exe calls a VI outside (that was not planned by AppBuilder) and uses a type definition in order to pass parameters, you will meet such kind of problem for sure.

I was offered a few ways to solve the problem but I really like only one. There is undocumented ini setting that disables this new feature. Put the following line to your labview.ini file:

BldApp.RemovePolyVIsandTypedefs=False

Then restart LV and rebuild your application.

[ another ways assume explicit including of all VIs into a build project, but it is unapplicable if you need support  plug-ins, for example ]

Hope this helps.

regards,

Konstantin Shifershteyn

"

I do not read german (?) but the error message you showed was a result of you doing a "ctrl-alt-del" or did it crash on its own? I am confussed because you used the word "hung" and not crash.

Ben

[CleanerTM]

Sorry, i meaned "crash". This screen appeared by itself.

[Ben]

Ouch!

Well try the switch mentioned in my previous post.

Otherwise try stripping things down to a minimum and posting a zip of the files required to demo this issue.

Trying to help,

Ben

[CleanerTM]

Thank you a lot, I'm thankfull for any help 🙂
I think the programm is mostly stripped down now, ... Files are included into the attachment.

You need to modifiy the .bld files, if you want to play with the options.

I have two tests included: one for typed vi refs (Test 2) and one for untyped vi refs. (Test 1)