Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

[adcpc]

Hi,

My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.

Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?

Thanks,

Alex

[Julien_De_Freitas]

Hi Alex,

First, thank you for using the National Instruments discussion forum.

I was wondering if you can tell me which LabVIEW and TestStand version you use.

I will help you with this issue when I will have these information.

[adcpc]

Hi Julien,

I'm using LabVIEW 12.0.1f4 and TestStand 5.0.0.262.

Thanks,

Alex

[Julien_De_Freitas]

Hi Alex,

thanks for your reply.

Could you send me the code in Teststand and in LabVIEW?

I need to know exaclty how you programmed.

Thanks.

Regards,

[adcpc]

Here is a simple example which shows the issue.

[Julien_De_Freitas]

Hi Alex,

thanks for the files.

I understood now the problem.

You cannot call a single VI with the Run-Time Engine. You need to build an executable.

Regards,

[adcpc]

Hi Julien,

Thanks for your reply.

But I can call other VIs with the Run-Time engine without having to create an executable.

Why is this needed when a call to "system exec.vi" is done ? I'm using this a lot in my library and I don't want to build an exe for each VI using it.

Regards,

Alex

[dug9000]

Have you tried mass compiling "system exec.vi"? To use a VI in the runtime engine, it must match the version of the runtime engine you are using and all of its dependencies must be found in locations where they were when the vi was last compiled and match the version of the runtime as well.

Keep in mind that if you are on vista or newer you might need to run labview as admin to have permission to overwrite the system exec.vi to resave it (not sure though).

-Doug

[Julien_De_Freitas · Accepted solution]

Hi Alex,

In you case, you are getting a -18002 error.

The reason is explained in the following link:

-18002 Errors in TestStand

http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument

Please have a look at the 2nd reason. This is your case.

Hope it helps,

Regrads

[adcpc]

I mass compiled the top vi (which calls system exec.vi) but it did not worked.