How do I choose between LabView and LabWindows?

[Thayer79]

We have been using LabView for a project, but are considering migrating to LabWindows/CVI as part of an upgrade.  How do I choose between the two?

We have a LabView app. written by a grad student (but out-of-date and not that well documented) and modified by someone with little programming experience of any kind.  Now it's my turn.  The hardware is getting a major upgrade and we're trying to decide whether to patch the current program, extract only the vis we need and do a new LabView app, or migrate to LabWindows.

I have many years' experience with a variety of languages, but am not proficient in any. I've used LabView a little, and think I could pick up either LabView or LabWindows.

The project involves  motion control, data acquisition and analysis. The outside contractor doing the major hardware upgrade recommends LabWindows, but they have more experience in C programming than in LabView. LabWindows is attractive because although I don't know C well, I have much more experience in command line languages than in GUIs.  I'm also big on documentation and writing well-structured code - both those seem difficult in LabView.

I've looked on the web and haven't found much about LabWindows, so I'm concerned it's a bit of a dead-end and maybe not used much, or won't be supported in the future.  There's also a cost factor - we have LabView 8 (current version) even tho the app is written in 7.1, but we'd have to buy LabWindows which is not cheap.

[Joe_H]

---

 I have much more experience in command line languages than in GUIs.  I'm also big on documentation and writing well-structured code - both those seem difficult in LabView.

---

As for the documentation you can do this in labview with comments and description tips and vi documentation. well structured code can be accomplished in any language and it depends on the programmer and how well they knows the tools. If you enjoy C style programming then go for Lab windows, but for ease of learning, functionality labview will do an outstanding job of this and you will be back up and running in no time.

Besides it's much more fun to program in G.

[Dennis_Knutson]

I started using LabWindows with version 1.0 when it only ran on DOS and still use CVI occasionally now. I agree with Joe that it's all up to the programmer in documenting and writing well structured code. I think LabVIEW tends to attract more individuals who have had no previous programming experience and that can result in some pretty poor programs. I do believe that an untrained programmer can pick up LabVIEW faster than an untrained programmer can pick up LabWindows. There can be some differences in execution speed between LabVIEW and LabWindows but that really depends on what you are doing. LabVIEW and LabWindows share the same code for DAQmx, GPIB, VISA, and the analysis routines you call in LabVIEW are all dlls that are probably similar (if not the same) that LabWindows uses. So, it boils down to the experience of your existing programmers, who might be using it in the future, and the cost of buying new licenses.

[tbob]

If you are not well versed in C++, you should choose Labview.  There will be a learning curve no matter which one you pick, but it will be very much less with Labview.  Besides the training classes and other support offered by NI, you can get a wealth of information right here on this forum and you get personalized service from us volunteers on any particular problem you may run into.  As far as proper structuring goes, be sure to read the Labview Style Guide for tips on how to properly structure your code. This will also make it easier to maintain and easier for anyone else to pick up in the future.