It is true that some of the APIs for our modular instruments use
components from the DAQ driver to talk to the hardware. This is
primarily for efficiency of development; for certain tasks, the
low-level programming of one of our DAQ boards and one of our
oscilloscope boards is very similar.
At th
Thanks a lot Brian!!!
Another little question to finish:
NI-SCOPE(API) can use both NI-DAQ(driver) and NI-DAQmx(driver). Then
why NI-SCOPE(API) and not NI-DAQmx(API) or NI-DAQ(API)? Why use
NI-SCOPE and NI-FGEN (APIs), in my case, and not NI-DAQ(API) and
NI-DAQmx(API)? Which are they advantages? Ju
Hmm. You're right that we often use those terms interchangeably.
Technically, the driver is the piece of code that runs in the
operating system kernel that does the low-level programming of the I/O
hardware.
This low-level programming is somewhat complicated, so we create a
higher-level Applicat
Hello.
I'm already a bit confused when reading about drivers and APIs...
What's the difference between an API and a driver???(because sometimes
texts refers to some of them without distinction).
Once known the difference, which is which? NI-DAQ is a... driver or
API???
And this for NI-DAQ, NI-DAQ
