What form LabVIEW deliverable should be in ?

[Edicia]

(Given) I have 5 different types test rigs . 5 LabVIEW programs (VI sets) to control 5 non-identical rigs.

RIG1
RIG2
RIG3
RIG4
RIG5

(Given) I have one "PARENT.EXE".; Blackbox- I am not supposed to worry what PARENT is built in.
When PARENT.EXE is called, it has list of 5 rigs.

Following is given requirement:

If operator clicks 'RIG1', PARENT.EXE shall launch "LabVIEW deliverable1" within a chosen area.
(Here, LabVIEW deliverable1's GUI shall control RIG1. PARENT.EXE shall control generic functions such as operator password)

If operator clicks 'RIG2', PARENT.EXE shall launch "LabVIEW deliverable2" within a chosen area.
(Here, LabVIEW deliverable2's GUI shall control RIG2. PARENT.EXE shall control generic functions such as operator password)

If 2 months later group6 adds RIG6 , then "LabVIEW deliverable6" must be written such that it does not require re-write of "PARENT.EXE".

What must be requirement on "LabVIEW deliverable" to be a plug-in part of above mechanism,
(EXE is out of picture...since it's an independent process)

Can the form be a RIG1.DLL and still be able to retain the GUI ?
Or is there something else (some kind of assembly?)

(Given)PARENT.EXE (not labVIEW) is capable to support plug-n-play / dymnamic, but it needs to know what format LabVIEW deliverable will be.

Thanks.

[jareds]

Hi Edicia,

Either a LabVIEW dll or executable will allow you to use a GUI with it.  And either can be called through another application, but that would be easiest with a dll.  However, either way there will still need to be some way of letting the PARENT.EXE know about this new exe or dll.  You could do that with a configuration file or through user input without modifying PARENT.EXE.