Do you need a LabVIEW monitor program or a Teststand/LabVIEW sequence? The answer to these questions will determine what type of architecture to employ. The images below show an example of an advanced architectural design used as a wrapper for a number of subvi functions. This type of high level structure could be compiled into an executable installer.
Alternatively, simpler vi functions like the final image showing a producer/consumer could be included in a Teststand sequence. All code will be written neatly and legibly based around an agreed LabVIEW Style Sheet. Software Engineers will comply with this approach and peer review of code helps to maintain consistency.
When your project requires a sophisticated LabVIEW program in order to comply with a demanding set of requirements we will provide our in-house LabVIEW architect to build the high level software framework needed to cover the requirements set. The architectural framework will include a set of pointers for what & where specific code fragments need to be inserted. Typically a team of Certified LabVIEW Developers (CLD) will be assigned a requirements list for specific vis under guidance from the architect.
For a complex system this high level structure removes the need for many wires and instead sends messages between modules and writes to user interface objects at memory level. The image above intialise.vi shows a cluster of references for these messages and data values.
Each module registers for each event it wants to receive messages for. Receiving a message triggers an event case resulting in producer/consumer response.
The above image shows a straight forward queue driven Producer/Consumer snippet which could capture a button press leading to code executing in the Consumer loop.
Created with
Website Builder Software