LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Modular architecture LabView

Hello!

 

 I am trying to develop a modular architecture for Labview, but not just some functions o simple programs, I want to modulate all the program and make easier to add or remove some external instruments, without having to change the program, just adding some SubVis.

 

This is a schematic image what I want to do:

Labview architecture.png

I want to have completely different instruments, but be able to control all of them with the same input and outputs, in order to make it easier to add new instruments. All the instruments should be previously created in a SubVi with all the same input and outputs normalized, just adding the subvi to the code they should work without changes.

This is where the problems start, because every instrument is completely different between them, may one is a IP camera, other one is a motor and another is a spectrometer that has completely different inputs and outputs.

 

I'm not a veteran expert in labview and I do not how to start, may I'm not focusing the solution correctly or maybe this idea is not possible. So I would like to get some help.

 

Thank you so much.

0 Kudos
Message 1 of 3
(3,082 Views)

It looks like you're onto a mix of Measurement Abstraction Layer and Hardware Abstraction Layer.

 

https://www.ni.com/en/shop/pxi/don-t-let-obsolescence-cause-your-test-system-to-flatline/the-ni-inst...

https://education.ni.com/center-of-excellence/resources/1171/hal-mal-ni-test-engineering-how-we-buil...

 

There are a few more on YouTube.

 

Santhosh
Soliton Technologies

New to the forum? Please read community guidelines and how to ask smart questions

Only two ways to appreciate someone who spent their free time to reply/answer your question - give them Kudos or mark their reply as the answer/solution.

Finding it hard to source NI hardware? Try NI Trading Post
Message 2 of 3
(3,070 Views)

Here's what I have done. In my case I have several test systems. All have AC and DC power sources, AD and DC loads, Power analyzers, and a DAQ/Switch unit. I use an XML file for each system that is parsed on start up. My program contains all of the VI's for each instrument and the proper VI is selected by the instrument type in the XML file.

 

BDCCapture.PNG

 

Although we have attempted to standardize our test equipment. There are still several differences present across the test systems.

Despite these differences, the validation platform software can run on any the test system located in the lab without making any modifications to the test script or LabVIEW program. 

 

 The Validation Platform software currently supports this test equipment:

  1. AC power sources
    1. California Instruments Ci5001iX 
    2. California Instruments CSW5550
    3. Elgar SW5250 (Deprecated)
  2. DC power sources 
    1. Sorensen DHP series
    2. Sorensen DLP series
    3. Sorensen XGI series
    4. Agilent N87xx series
    5. Keysight N89xx series
  3. AC Loads
    1. California Instruments 3091LD
    2. NHR 3200
  4. DC Loads
    1. TDI Dynaload RBL series
    2. NHR 4700 series
  5. Yokogawa power analyzers
    1. WT-1800
    2. WT-1600
    3. WT-500
    4. WT-230 
    5. WT-130 (Deprecated)
  6. HP/Agilent/Keysight DAQ/Switch unit
    1. 3497xA Series
    2. DAQ97x Series
  7. Test system DC switching relays controlled by 3497xA/DAQ97x using:
    1. Multifunction card DIO (Deprecated)
    2. Actuator card
========================
=== Engineer Ambiguously ===
========================
Message 3 of 3
(3,012 Views)