Where is the configuration information for each ExpressVI instance stored? Is it available in TestStand Steps? How can I access it?

[Caribe]

Where is the configuration information for each ExpressVI instance stored?

Is it available in TestStand Steps?

How can I access it?

Note:
(INSTANCE != "Configuration dialog box VI")
(INSTANCE != "Souce VI")


Thanks a lot! I think this one is tough!


- Caribe -

[Watermann]

hello Caribe,

I don't think there is a way to get access to the configuration of express VIs; especially not via teststand.
but there is the Express VI Development Toolkit where you can have a look at... perhaps this will help you in another way...

LabVIEW Express VI Development Toolkit User Guide

greets!

[Caribe]

Thanks Watermann!

I have already the LabVIEW ExperessVI Development Toolkit...
And read the user Guide...

In the User Guide, there is a Paragraph:

"Express VIs do not provide run-time interactive configuration for VIs. If you need run-time reconfiguration, build an application with a user interface that contains features similar to a configuration dialog box."

Well, I think accessig the configuration of each instance from an LabVIEW application is maybe a secret... for example, some of the subVIs that come with the toolkit are password protected...

The question is why? Why is it not possible the run-time reconfiguration of instances?
That would help me a lot in my project an would make it possible to develop high flexible
Code Modules for TestStand with express VIs.

Maybe there is another way to do it?

Do you know a reference, id, or reNum that is common on both configuration instance and executing instance?

Thanks a lot! I hope you can still give me some help...

Best regards,

- Caribe -

[Scott_Richardson]

Caribe -
Here is some background information that might be useful.

LabVIEW requires that an express VI must reside on the diagram of an existing VI. An express VI cannot be saved to disk as a top level VI.

Because of this restriction, TestStand is required to create a wrapper VI to hold the express VI. When you configure or reconfigure the express VI, the connector pane may change, so TestStand must reqbuild the wrapper VI to ensure that the inputs and outputs on the wrapper VI mirror the inputs and outputs on the express VI.

TestStand stores the wrapper VI which contains the express VI in the TestStand step. When TestStand executes the step it caches the wrapper VI to disk and instructs LabVIEW to execute the VI on disk.

You can create a copy of the VI stored in the step by calling the LabVIEWModule.ExportVI API method.

From a LabVIEW perspective, the wires that an express VI exposes to its connector pane is the way to perform programatic "run-time configuration" of the VI.

Now I am aware of some Express VI developers that use TestStand that have created a dual purpose Configure dialog box that can be displayed when the express VI is run. The dialog box is written in a way to allow the user to interact with the test step while it is running. This is a custom design that they were implementing.

[Caribe]

Now thats what I call an Expert answer! :-))))

Thanks a lot!

I will work on the information you gave an try to
work out the best solution for me! I understand
things better now!

Thanks again and Best regards,

- Caribe -