Can you list in bullet points the pros and cons to Labview and LabWindows/CVI? Which one is better for test automation?

[Dennis_Knutson]

Can you possibly use the message body instead of trying to cram everything into the subject line?

Either one is suitable for test automation. What do you have experience with?

[smercurio_fc]

You can also put in a little effort and actually do a search, as this question has been covered many times over the years.

[Papi]

I have experience with LabWindows/CVI and prefer looking at the code vs. graphical representations of the code, but there are other things to consider ...

I am having a test stand built, which will have the capability to test various circuit boards.  The following equipment will be used to test these boards:  switching, oscilloscope, D/A, mux relays, function generators, power supplies, electronic loads.  Now, cost and resources must be weighed into my decision.  All the potential suppliers that I talked to say that they can do CVI, but all our most of their employees have experience with LabView.  I am considering LabView for those reasons (cost and resources).  Is there anything LabView can't do over CVI? 

[Papi]

I have but wanted to hear what others had to say.  In hindsight, I shouldn't have even bothered.  I expected helpful advice, not a smart ass.

[Dennis_Knutson]

There are some differences in what addons/toolkits are available. If you have a list of instruments, you could look to see what drivers already exist.

I use TestStand to control our test stations and the great thing about TestStand is that you can freely mix LabVIEW code with CVI code, with VB code, with C++ code, etc. so you can choose whatever language is the most appropriate.

[smercurio_fc]

---

Papi wrote:
I have but wanted to hear what others had to say.  In hindsight, I shouldn't have even bothered.  I expected helpful advice, not a smart ass.

---

I did provide helpful advice by providing a link to a search result on such a vague question.

And calling people a "smart ass" is a sure way of showing your level of professionalism and making sure you don't get any more help, at least from me.

[F._Schubert]

I'm big fan of LV and would go nowhere without it, but as you're used to text based programming and especially CVI, I see nothing wrong with sticking to it. You would need to abandon a lot of your coding practices to embrace data flow (have a look at the breakpoint forum in the thread of 'why local variables are bad').

On the driver side, most of the drivers I got LV-ready where wrappers of dll's or VISA calls. And poorly written by LV standards (missing or wrong error handling, not functional because of wrong dealing with pointer, or simply nasty connector panes). Most of the time I wrapp them up or even rewrite them on my own.

If you have both licenses available, maybe you might try to write a smaller Test in LV to experience graphical programming. Then you can choose on your own to continue with LV or even rewrite that code in CVI.

Felix

[Ben]

We used to have a Certified CVI instructor on staff. He would do estimates for projects using LV or CVI. it was easy. He would estimate what it would take in LV then double it to get the CVI estimate.

Ben