First, learn LabVIEW! Here are some things that "seem elementary" (because they are similar to Text-based Languages) and don't make use of the strength of the Data Flow Programming concepts that LabVIEW affords. Here are some things to avoid:
- Never (until you have 3-5 years experience in LabVIEW programming) use a Sequence Structure.
- Especially (until you have maybe a decade of LabVIEW experience) never use a Stacked Sequence Structure.
- Always use (and connect) the Error Line when possible. If you have two sequences running in parallel, you need two Error Lines.
- Rarely (for you, never) use Local Variables. [Note you never write to the "millisecond" local variable, so you can replace it with its default value, 0, and replace the subtraction of, say, the Millisecond Timer and Local Variable "millisecond" with just using the "Millisecond Timer" (because subtracting 0 from something is the same as the first argument to the subtraction). [I'm assuming you knew this ...].
My first exposure to LabVIEW was to learn and maintain a LabVIEW Real-Time system that tested large Primates and their ability to localize a sound source in complete darkness. I had more than a decade of experience with text-based languages (Pascal was my favorite) and a good instructor (and students who helped me when needed), so I was able to keep the existing code running while redesigning and recoding it based on Structured Programming concepts.
About five years into my LabVIEW experience, a colleague asked for my help with a study that used Vision to record behavior (in the light, of course). I was grateful for having learned standard DAQmx routines for data acquisition and control, because IMAQdx was a whole (and more complicated) learning experience! My advice would be to find a LabVIEW Guru who (especially if you can find one with LabVIEW Vision experience) and get some help with learning better LabVIEW development techniques.
Bob Schor
