LabVIEW Instrument Library class

[YavannaKementári]

I have designed a bunch of LVClasses based on instrument functionality, that dynamically call specific instruments. However, I would like to have these LVClasses outside my built EXE, so that I can add new instruments to my library without having to re-build my EXE code. There's a "generic" LVClass layer in the EXE code that would be part of the library, and what specific instruments are dynamically dispatched are chosen at runtime based off of a config file.

So that's the background. I will attempt to attach a small dummy LVProj to illustrate what I'm trying to do. The "Instrument Example EXE.vi" would be the code in the EXE, and the classes in the LVProj would be the "library".

Here's my question: What's the best way to contain that LVClasses "library", so that the EXE code can easily call it, and the library can be updated with new instruments? I know there are llbs, and lvlibs, but I'm curious in any of your opinions on what would be the best architecture for managing this.

[_Tim]

You may want to look into using packed project libraries. This example walks through the process of creating these libraries, which can be modified and updated independently of the main application.

It may also be worth posting this question to the LAVA OOP forums as well. There are a lot of active members over there who work quite frequently with LVOOP and may have some further suggestions on architecting your application.

Good luck with your project!

[GregFreeman]

You can try a plugin architecture also