storage *.vi-driver in custom file

[CoertvandenBors]

hello,

In my project I work with a plugin principle. Each plugin reach to a measurement sensor. The plugin contains all info about the manufacturer, all equations for a m-file that communicates with matlab, and further parameters like visualizations etc. The plugin is build around a cluster. The structure refers to the plugin-version, and the content of the plugin has been stored in a file (the plugin).

Lately I noticed that some measurement sensors need some labview drivers to interact with the program for the right values. I would like to add these drivers to the plugin so that the whole system would be universal and flexibel. But i don't have any idea to combine the plugin data with a *.vi so that I have 1 object. Or is there an other way?

Greetz,

Coert

[josborne]

An interesting design/architecture question.

From what I gather, you store some information about a sensor in a file.  And then retrieve this information into a cluster.  And now you want to add a VI to this bundle of information.  I think the best solution is to store the path to the VI (either relative or local) inside your plugin file.  Then you can add this path to your cluster and call the VI dynamically.  Here is an example of how to call VIs dynamically:

http://zone.ni.com/devzone/cda/epd/p/id/3806

[CoertvandenBors]

Hello,

Thanks for your solution but that was my backup for my problem 

I had my system analysed and it is possible. But the problem is, that there are 2 kinds of programs: a plugin program (this one creates the plugins and runs on a normal pc/laptop) and a measure program (this one is running on a Industrial PC, and there is a transfer needed by USB or FTP).

The idea of using plugins is to make the system flexibel. But if I implement your solution I must create a driver library, because my measure program can contain all measurement sensors and each sensor has an other driver.

Sow, thanks for your answer, but is there not another way to get the plugin info and a vi-file(s) combine to one file?

I hope this would help...

Thanks again.

greetz,

Coert

[josborne]

Hmmm.  Could you just ZIP the vi and the plugin into one file?  And then modify the software on your Industrail PC to unzip and process the two files separately?  That might provide enough flexibility.

[CoertvandenBors]

Hello,

Yeah thats the solution. Stupid that i didn't think about that.

Thanks again.

greetz,

Coert