differential analog inputs

[JÞB]

---

@Hooovahh wrote:

---

Jeff·Þ·Bohrer wrote:

Now lets get some terminology corrected here about DAQmx Stuff:

---

Thanks for your clairification.  My terms were incorrect.

I also vote TDMS, and the Excel conversion is nice.  Here is my wrapper I wrote a while ago.

---

No Problem

Spoiler

(At least I wasn't placed "On Hold")  <---- inside joke

[Bob_Schor]

Jeff,

     That has to be one of the clearest explanations of the What, Why, and How of DAQmx Tasks in all its Gory Detail.  I typically use Project-defined Tasks and am the only one using the Device (since it has been rebooted), so I usually can get away with a simple "Start", but you gave a wonderful explanation for the "other pieces".  The explanation of Logging was also excellent (but doesn't apply to my situation, I don't think, since my samples are gathered by a PXI-RT system, but saved on a PC after being Network-Streamed over).

Bob Schor

[andy_kennaugh]

Cheers! man thanks a lot, I am going to adopt your suggestions in my vi.

[andy_kennaugh]

What if I make a task in MAX with all the channels and input max/min values for each physical channel

[Hooovahh]

Historically I've used MAX in this way.  Make the channels, tasks, and scales in MAX.  Save them in MAX and then use them in LabVIEW, then you don't need to setup the task each time.

The downside to this is the settings are saved on the PC, and deploying to other PCs can be an issue.  You'll need to export the settings from MAX and then import them in the new PC some how.  There are manual and automatic operations but this is extra work to get things working.  The benefit of this is the end user if familiar with MAX is able to change things like what physical channels are wired, and adusting scales and calibration if needed.

That is why the project method was mentioned, where you make the channels, tasks, and scales, and save them in the project.  Then that information goes along with the EXE and shouldn't need to be imported on a new PC.

[JÞB]

---

@andy_kennaugh wrote:

What if I make a task in MAX with all the channels and input max/min values for each physical channel

---

Very Good!  You can even rename the channels in the DAQmx Wizard (That framework that you use to create Tasks in MAX or in the Project)

I Have to admit to being a huge fan of the DAQmx Wizard!  It really does make it easy to write DAQmx stuff (It verifies Tasks as you go rather than waiting for LabVIEW to attempt to run your code).