I-o Data Multifunction Devices Driver Download

i. Selecting a DAQ Board

I-o Data Multifunction Devices Driver Download Windows 10
I-o Data Multifunction Devices Driver Download

NIMH MonkeyLogic works with any NI board that is supported by the NI-DAQmx driver. It may be advantageous to see if you already have a usable NI board. If you purchase a new board, it is best to obtain one that can handle all the I/O needs in one board. NIMH ML can use multiple boards, but it does not require two NI boards unlike the original MonkeyLogic. Be aware that older (PCI bus) cards cannot be used if your new computer does not have any PCI slot. The following table lists some current NI board models that are suitable for general I/O requirements.

The DAQ software helps to diagnose hardware with complete I/O drivers. It also includes DAQ SDK and DAQ utility application software to control specific hardware interface. The Multifunction I/O Device features I/O with varying channels, sample rates, output rates, and other features to meet many common measurement requirements. You can use the device for industry applications such as laboratory automation, research, and design verification. All devices have a minimum of 16 analog inputs, 24 digital I/O lines, and two counter/timers. Low-cost M Series multifunction DAQ is ideal for applications including data logging, control, and sensor and high voltage measurements when used in conjunction with NI signal conditioning.

Model	Analog Input (SE / DIff)	Analog Output	Digital I/O
PCIe-6320	16 / 8	0	24 (P0: 8, P1: 8, P2: 8)
PCIe-6321	16 / 8	2	24 (P0: 8, P1: 8, P2: 8)
PCIe-6323	32 / 16	4	48 (P0: 32, P1: 8, P2: 8)

ii. Device Pinouts

Connecting external devices to the NI board requires knowing which pin is mapped to which signal. Locate the necessary information in the product's datasheet or by right-clicking on installed devices in the NI Measurement & Automation Explorer (NI MAX) software.

Inputs from external devices can be connected to NI boards via NI terminal blocks. Unshielded screw terminal blocks, such as CB-68LP and CB-68LPR, are low-cost and good for designing a custom interface box. There are also BNC terminal blocks, like BNC-2090A, for a ready-made solution. For the details, please refer to the NI DAQ Multifunction I/O Accessory Guide.

iii. Analog Input Ground Configuration

The grouding scheme of analog input of an NI data acquisition board must be wired and configured correctly in NIMH ML. There are typically three ground configurations available for NI devices; differential (DIFF), referenced single-ended (RSE) and nonreferenced single-ended (NRSE).

For a signal source referenced to the earth or building ground, try the RSE mode. In a typical lab environment, many devices run on custom power supplies or batteries and their voltage output may not be referred to an absolute reference. For those signals, try DIFF or NRSE. For more information, see Field Wiring and Noise Considerations for Analog Signals.

The [AI configuration] option on the MonkeyLogic main menu must be set to match the configuration.

Differential mode (DIFF)

In the differential mode, the potential difference is measured between two terminals seperated by 8 channels, for example, AI 0 (+) and AI 8 (-). This mode can deliver more accurate measurements with less noise but takes twice as many channels of the NI board as the other modes.

(Referenced) Single-Ended mode (RSE)

In this mode, the measurement is made with respect to a single common ground node, AI GND. Connect the (+) input to an AI channel pin (AI 0, AI 1, ..) and the (-) input to AI GND.

Nonreferenced Single-Ended mode (NRSE)

The NRSE mode also makes all measurements with respect to a single node (AI SENSE), but the potential at this node is not an absolute reference and can vary. If you have many custom devices and it is uncertain whether they are properly grounded or not, use NRSE. Connect the (+) input to an AI channel pin (AI 0, AI 1, ..) and the (-) input to AI SENSE.

-->

The topics in this section provides information about USB pipes and URBs for I/O requests, and describes how a client driver can use the device driver interfaces (DDIs) to transfer data to and from a USB device.

A transfer takes place every time data is moved between the host controller and the USB device. In general, USB transfers can be broadly categorized into control transfers and data transfers. All USB devices must support control transfers and can support endpoints for data transfers. Each type of transfer is associated with the type of USB endpoint (a buffer in the device). Control transfer is associated with the default endpoint and data transfers use unidirectional endpoints. The data transfer types use interrupt, bulk, and isochronous endpoints. The USB driver stack creates a communication channel called a pipe for each endpoint supported by the device. One end of the pipe is the device's endpoint. The other end of the pipe is always the host controller.

Before sending I/O requests to the device, the client driver must retrieve information about configurations, interfaces, endpoints, the vendor, and class-specific descriptors from a USB device. In addition, the driver must also configure the device. Device configuration involves tasks such as selecting a configuration and an alternate setting within each interface. Each alternate setting can specify one or more USB endpoints that are available for data transfers.

For information about device configuration, see How to Select a Configuration for a USB Device and How to select an alternate setting in a USB interface.

After the client driver has configured the device, the driver has access to the pipe handles created by the USB driver stack for each endpoint in the currently selected alternate setting. To transfer data to an endpoint, a client driver creates a request by formatting an URB specific to the type of request.