Getting started - help with general concepts?

[Matt Moose]

Dear Group,

Please can anyone tell me roughly how to achieve the following, before
I obtain LabView:

We have a GPIB instrument that takes many measurements; we need to
create an automated test routine using it. I'm assuming it's easy
enough to set up 2-way comms between our PC and the instrument.
(Sending GPIB mnemonics to it, reading bulk data from it.)

We need to create numerous flat spreadsheet (CSV) files, with columns
of different data from the instrument, plus comments entered by the
test person.

Can LabView generate dialog boxes to get data from the tester, then
insert the data into specific positions in the CSV file?

Can LV also perform different sequences of measurements (ie. send
different GPIB command strin
gs) and put up different prompt messages
to the tester, depending on various conditions?

Finally, why (if at all) would using LabView be advantageous over
trying to use Visual Basic for all the above?

Many thanks in advance - please reply to this newsgroup.

Matt

[Dennis_Knutson]

Yes, LabVIEW can do all of those things and for an experienced programmer, they're quite easy. Note that I say for an experienced programmer. Imho, LabVIEW is much simpler to learn than say C++, but that doesn't mean that it doesn't require some training so figure on taking some classes to become effecient in the shortest possible time.

One reason to use LabVIEW for instrument control, is that's what is was designed for in the first place. A simple and powerful language that engineers and scientists could use without requiring a degree in computer science. There are thousands of existing instrument drivers available in LabVIEW and there's a good chance you won't have to write any code for your instruments. Most instrument manufacturers create LabVIEW
drivers because they know it helps sell their instruments.

[tbob]

I have used both VB and Labview to do what you are asking. In my opinion, Labview is far easier to use and maintain. Non-programmer design engineers have picked up on my Labview programs quite easily for minor modifications. They could not have done so as easily with VB. Also, if you use Labview instrument drivers, you will not have to look up any GPIB SCPI commands (like READ? or :FUNC:VOLTS DC), the drivers have all of this built in. This makes it much quicker to write your program. Also easier to create and write CSV files. Dialog boxes for testers are no problem either. Try it, you'll like it.

[Jim_Cavera]

Having used LabVIEW, VB and C/C++, I can say that the first tool I reach for is _always_ LabVIEW. Nothing else comes close in terms of ease of use, maintainability, and user-friendliness. That said, I don't consider LabVIEW a silver-bullet. If you need your application to to complex 3D rendering, fast database access, or similar highly specialized tasks, you may need to look elsewhere.

Your requirements are fairly strait-foward and all are common things for a LabVIEW program to do. Were I in your position (and I was, once 🙂 I would get a copy of the demo version of LabVIEW and play with it for a few days. It isn't disabled (much) so you can see the bulk of LabVIEW's capabilities.

If you like it, and I'm sure you will, I would reccommend taking a Lab
VIEW Basics class. They are well worth the time and cost and will have do doing full development work in a matter of days. Hope this helps and please post here if you need anything further.

- Jim Cavera