TestStand LV Run-Time Open VI Reference

[schm1347]

I have some code that was written in LabView that opens and runs VIs dynamically.  The LabView module is called by TestStand.  It works fine in development mode, but gives me error 7 when running with LabView Run-time engine.  I know that the issue is that the VIs which are being called dynamically are not getting loaded into memory before the test sequence starts.  If this was an application, I would make sure that they were added to the project.  Is there any workaround to assure that I can continue to call these VIs dynamically and utilize the LabView run-time engine?

Thanks,

Jeff

[Norbert_B]

Jeff,

error 7 in LV means "file not found". Are you sure that your paths are correct referencing to the dynamic subvis at deployment time?

Are there any files the dynamic subvi is going to load itself (like ini/cfg/txt files)? Are those in the correct place?

hope this helps,

Norbert

[John_M.]

Hi Jeff,

In addition to Norbert's suggestions, I wanted to ask you whether or not the VIs that you are calling are being called with absolute file paths or relative file paths? If they are being called relative to the calling VI, the base path is different when the VI is in debug mode vs when it is in an executable. The Application Directory VI can be used in LabVIEW 2009 to compensate for this difference. If you are using a previous version of LabVIEW, a simple VI can be setup to do the work of the Application Directory VI. If you think this may be what's going on, let us know and we can elaborate a bit more on this.

Best,

John M

[schm1347]

I should have posted something earlier.  I figured out that I wasn't generating the VI paths correctly, so I was missing a directory.  There is nothing special (short of making sure the path is correct that needs to be done).  Thanks for the help.

[MimiKLM]

Hi, I ve got very similar problem which I described here.

It looks like LV recognises path & VIs differently between RTE and Development Servers modes.

Why is that?

[John_M.]

MimiKLM, I've posted some comments on your other post.

John M