Download I-o Data USB Devices Driver

I-o

Here at ACCES we pride ourselves on our commitment to service. If you can't find what you're looking for below, please, contact us.

Drivers & Software

The best way to find your updated driver and software package is to navigate to the specific product page (starting with the product category, in the menu / navigation side-bar to the left.)

  • The package provides the installation files for Microsoft Xbox 360 Controller USB Driver version 2.1.0.1011. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version.
  • Download ADATA HDD / SSD / NAS / USB Flash drivers, firmware, bios, tools, utilities.

The packages are listed on each product's page, both in the 'Manuals / Software' tab, and in the navigation side-bar to the left.

You can also use the Latest Driver / Software Package Installer List.

USBPCIPCIemPCIeWirelessPC/104
MiscSerial ConverterDAQ PACKEthernetPCMCIARemote ACCES

Download I-o Data Usb Devices Driver Windows 7

MTP or (Media Transfer Protocol) is a set of custom extensions to the Picture Transfer Protocol (PTP) devised by Microsoft, to allow the protocol to be used for devices other than digital cameras, for example digital audio players such as MP3 players, and other portable media devices, for example portable video players. USB-related requests such as URBs and structures used by USB device drivers. I/O Request Packets (IRPs) used by PnP subsystem. Kernel-mode and user-mode device I/O control requests (IOCTLs) used by USB client drivers and user-mode applications. Incoming and outgoing data traffic of the USB devices. Trace USB requests that the user-mode.

The Software Packages include Windows Drivers (32- and 64-bit), Samples, Utilities, Documentation, etc.

We also provide a Driver Only package, for production deployment.

All of these packages are redistributable .EXEs, and don't require an internet connection to be installed (nor during use).

Supported Windows Versions

ACCES supports every version of Windows we can. The packages described above support retail and OEM versions of every edition of Windows from XP through 10 including the Embedded Standard editions (XPe, Win7ES, Win8ES, etc.) and all the related Server editions (Windows 2008R2 etc), in both 64-bit and 32-bit. The packages also include limited support for Windows 98se, Windows 95, Windows 3.11 for Workgroups, and DOS, for older products.

We also provide macOS, DOS, and VxWorks 7 software and drivers, for some products or product families — as well as others upon request, just ask us. Keep scrolling down for more details about our non-Windows software.

Operating Systems Supported

All our software supports both 32-bit (x86) and 64-bit ('x64', AMD64) versions of the following Windows operating systems.

Supported Windows desktop / client versions

  • Windows 10
  • Windows 8, 8.1
  • Windows 7*
  • Windows Vista*
  • Windows XP*

Supported Windows Server versions

  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2008 R2*
  • Windows Server 2008*
  • Windows Server 2003 R2*

* Note: Windows versions prior to the NT6.2 kernel (prior to Windows 8 and Server 2012) are not recommended for use in new applications due to lack of support from Microsoft. ACCES will continue supporting them, until we cannot.



Linux, macOS, and more

ACCES provides Linux drivers primarily via our git repositories. The following are just a few examples of what's available:

  • AIOUSB library and documentation, including how to use .rules files to get fxload to automatically load the device's firmware when the USB cable is connected
  • APCI library and documentation, including support for register and IRQ access from userland applications
  • PCI Express Serial documentation, including how to configure individual ports for RS232/422/485 modes (on supporting hardware)

    The Linux software for some products is available on those product pages (under the Manuals / Software tab, and in the navigation column to the left.)

    If you would like the Linux software package for any product and do not see it on the specific product's page, please call us


VxWorks

Among the many RTOS only one stands above the rest: VxWorks by Wind River® — 'Wind River VxWorks is an embedded Real Time Operating System (RTOS) that focuses on scalability and modularity. Kernel profiles allow customization specific to the needs of an organization whether it be safety, security or graphics. Kernels can be 32-bit or 64-bit and can be built to provide Symmetrical Multiprocessing (SMP) or Asymmetrical Multiprocessing (AMP) where supported.

Visit our Wind River partner page for more information about our VxWorks offerings.


LabVIEW

ACCES has VIs for LabVIEW 5 through 7, and 8.5, for most of our products, and USB boards have VIs demonstrating use in LabVIEW 8.5 through 2013. You can find the drivers for LabVIEW 5 through 7 in the /Drivers/LabVIEW directory on the Software Master CD. The LabVIEW 8.5+ drivers are available in the /Drivers/LabVIEW 8.5+ directory on the CD, and on the products' pages, both in the Manuals / Software tab, and in the navigation column to the left.

For your convenience, the two major LabVIEW packages are available here:

  • USB devices (other than serial ports)
  • Register-based cards (other than serial ports). This includes ISA, PC/104, PCI, PCI Express, and all related devices with I/O register address ranges.
  • Serial devices are supported directly by the Operating System and LabVIEW itself.

Download I-o Data Usb Devices Driver Download

Supported Legacy Versions

  • 7.9 Driver Package

    This is primarily useful for USB products. The later USB drivers are mainly not a bugfix, but exist to add 64-bit Windows support. Further, it can be tricky to move from 7.x to 8.x or 9.x. So, you can continue using 7.x drivers via this package, which does include any bugfixes.

    Please note: ACCES USB devices invented after January 2001 are not supported by this package. (contact us if you need support added. We're here to help you succeed.)
  • 8.10 Driver Package

    This is the oldest supported driver with 64-bit support. Notably, USB products use Microsoft WinUSB.dll in this version, instead of CyUSB.dll (in the 9.x drivers), or CyUSB3.dll (in the 10.x, current, driver package)

  • 9.63 Driver Package

    This is the most recent driver using CyUSB to interface to USB devices (the current '10.x' drivers use CyUSB3 instead). Some customers have reported problems installing the 10.x drivers on some Windows XP systems: the 9.63 Driver Package should be used in those situations.


Datasheets / Manuals

To find your updated manual and/or datasheet, please navigate to the specific product page (starting with the product category, in the left NAV bar).

The manuals and datasheets are listed on each product's page, both in the 'Manuals / Software' tab, and in the navigation column to the left.


Download I-o Data USB Devices Driver

Download I-o Data USB Devices Driver

Devices

Other, Unusual, or Rare Downloads

The following software applies to just a few models we produce. Most customers looking for software for our cards should click the product packages link, or download the software from the product's page, itself.

USB Serial Adapter Drivers for Windows

This section applies to the following serial communication models:

  • USB-485
  • USB-422
  • USB-232
  • USB-COM-4S
  • USB-COM-4SM
  • USB-COM232-4
  • USB-FLEXCOM4
  • USB-COM232-4A

Our 9.x Driver release supports all relatively recent revisions of these devices.

Significantly older versions of the hardware may require older versions of the driver, which can be downloaded here, here, here and here.
To install the older, '.zip' driver package:

  • Unzip the package.
  • Uninstall the card from Device Manager if it's already installed. To get to Device Manager in 98 / ME, right-click on My Computer, choose Properties, then choose the Device Manager tab. To get to Device Manager in 2000 / XP, right-click on My Computer, choose Properties, choose the Hardware tab, then click Device Manager. The card will be in the Multifunction Adapters and/or Ports categories.
  • Click Refresh in Device Manager to re-detect the card. Choose Search For The Best Driver, then check only Specific Location, and enter the location to which you unzipped the package.

-->

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.

Download I-o Data Usb Devices Driver Updater

In this section

TopicDescription

This topic explains the structure of a control transfer and how a client driver should send a control request to the device.

This topic provides an overview of USB pipes and describes the steps required by a USB client driver to obtain pipe handles from the USB driver stack.

This topic describes the WDF-provided continuous reader object. The procedures in this topic provide step-by-step instructions about how to configure the object and use it to read data from a USB pipe.

This topic provides a brief overview about USB bulk transfers. It also provides step-by-step instructions about how a client driver can send and receive bulk data from the device.

This topic discusses static streams capability and explains how a USB client driver can open and close streams in a bulk endpoint of a USB 3.0 device.

This topic describes how a client driver can build a USB Request Block (URB) to transfer data to and from isochronous endpoints in a USB device.

In this topic, you will learn about the chained MDLs capability in the USB driver stack, and how a client driver can send a transfer buffer as a chain of MDL](/windows-hardware/drivers/ddi/wdm/ns-wdm-_mdl)'>MDL structure.

This topic provides information about steps you can try when a data transfer to a USB pipe fails. The mechanisms described in this topic cover abort, reset, and cycle port operations on bulk, interrupt, and isochronous pipes.

This section provides guidance concerning the careful management of USB bandwidth.

Related topics