I would like to thank Scott Serlin, Ben A. Rayner, Stephen Mercer, Paul F. Sullivan,
Simon Whitaker and Torben Laursen for replying to my question so far. Thanks also to
any I may have missed. I look forward to making use of the info shortly.
Best wishes,
Matt Rhys-Roberts.
Matt,
You wrote:
...We have chosen LabView over Visual Basic as we think
that LV ought to ... allow
later modifications to be made more simply (by non-programmers) than
having to wade through reams of hostile-looking code! --- Right or wrong??
RIGHT! The graphic nature of LabVIEW allows most
You might look into National Instrument's teststand v3.0. It's somewhat expensive but
would fit in very nicely with your automated testing environment. Otherwise, you will
need to come up with the code for your own test executive which would govern your
tests (initializing equipement, setting
It's a pretty general list, but I'll take a stab at some of these. Though
I'll do it in my own order...
First, read the Getting Started manual. It walks through simple programs.
The manual is on your CDs. From the LabVIEW 7.0 Navigation Dialog, select
HelpSearch the LabVIEW Bookshelf. The
