@mittly wrote:
Hi, guys!
I am a freshman.
Welcome to the Forums. I'm glad that at least some Freshmen are learning LabVIEW (at my University, they "allow" me to give a single LabVIEW talk to the BME Seniors, usually in their final semester as they are rushing to finish their Capstone project. Too little, too late ...).
Because you are new, you probably haven't heard my "Attach code, not pictures" rant. If you attach an actual VI, if there's a Broken Arrow, we can find the problematic function, and we can "investigate" more thoroughly. One drawback is if you have lots of VIs and attach just one, there will be "missing" functions, but that can often be overcome by compressing the folder containing your Project and attaching the entire .zip file.
Another (minor) point, but might as well start off on the right track -- some very accomplished LabVIEW Gurus might frown on being called a "guy".
OK, a Very Good Point in your favor -- you did not use the DAQ Assistant, but rather tried to dive right into DAQmx. Good for you! Go to the Web and search for "Learn 10 Functions in NI-DAQmx", read the excellent NI White Paper, and use some of those techniques. In particular, take your device, open it using MAX (NI's Measurement and Automation eXplorer), and see if you can configure the channels as you want. If so, you can save this configuration as a Task in MAX, and, even better (in my opinion), you can create a Task in the LabVIEW Project associated with your code. [If you don't know about LabVIEW Project, look it up and start using it!].
Bob Schor
