National Instruments LabVIEW vs. National Instruments SystemLink

Most of the time, I am using LabVIEW to develop automated controls for lab-scale and pilot-scale systems. LabVIEW is great for its graphical programming interface, which is easy to learn and understand. The program also has a lot of built-in VIs to perform different complicated I/O, data processing, controls, and graphing tasks which are extremely useful and convenient to use. My only problem with LabVIEW is how hard it is to clean up and debug the program, due to its being a graphical interface. It is hard to search for specific variables when debugging, and some of the online debugging features don't function well in real-time.

Incentivized

There are definitely scenarios where NI SystemLink will be useful but just didn't work out well for us. I needed to be able to replace an EXE file on a computer with a new EXE to do the upgrades but I was not able to do that through SystemLink. You had to work with packages in order to perform this and I didn't want to revamp my distribution plan. We also didn't need to do any asset management or calibration documentation through SystemLink. I was excited about being able to view data from the test stations through a browser but our engineers need historical data available and everything resets to a live view when you click back to the UI.

Incentivized

• real-time data visualization
• implementation of modern control strategies
• integration of languages such as python and c++, for various applications
• data acquisition through microcontroller cards

Incentivized

• Setup
• User Interface
• LabVIEW Integration

Incentivized

• Barrier to entry is large
• Install times are crazy
• Just in time help needs to be more apparent (most students do not know about the examples section)

• Licensing
• Not able to see data from all test stations on one UI
• Lack of data history

Incentivized

We have used MatLab's data acquisition toolbox in the past which was not too bad either, especially if you prefer the text-based programming format. The only problem with that was that the library of compatible data acquisition hardware was somewhat limited and if your hardware is not from one of the more popular brands like NI there is a good possibility that you won't be able to use it with your MatLab script. LAstly, the amount of supporting material (tutorials, etc.) is very limited as it is not a very popular tool

Incentivized

• We are able to save money by writing our own programs instead of outsourcing.
• We recently bought a new force test stand and we are able to use LabVIEW to write a program that fits our needs exactly instead of making due with what came with the stand.
• When our customers ask us to do data acquisition, we know that we can always make a solution.

Incentivized

• Availability to monitor multiple test stations remotely
• Was quick to integrate into existing LabVIEW codebase
• Ultimately did not justify the licensing cost for the benefit

Incentivized