The native communication mode of most of our newer USB data acquisition (USB DAQ) products is LibUSB, a cross-platform standard that supports many USB products. LibUSB is supported out-of-the-box by our WinDaq data acquisition and .Net class software that is included with the hardware, so there’s little need to change USB modes. However, for those who want to program these new USB products themselves (especially from the protocol level), the so-called USB CDC mode may offer some advantages. Not the least of these is simply communicating with the device over a COM port instead of through the LibUSB library. The Communication Device Class (CDC) allows the USB port of supported devices to appear like a traditional RS-232 port, which is ubiquitous across OS platforms and development languages. Fortunately, our USB data acquisition products can be configured for either standard. The following procedure explains how you can transition from the default LibUSB to the CDC mode and back again for all the products you’ll find here (except model DI-245, which lacks LibUSB support and always hooks a COM port.)
- Disconnect and reconnect the USB cable to the device.
- Immediately begin pressing the button on the side of the instrument about twice per second. Stop when the Active LED turns RED.*
- The LED begins flashing yellow indicating that it’s in the CDC mode, or green indicating the LibUSB mode.
- Disconnect and re-connect the USB cable. The instrument will hook a COM port if the LED is yellow, or be an active LibUSB device if green.
* The DI-2008’s LED never turns RED. It transitions directly to YELLOW for the CDC mode, or GREEN for LibUSB, at which point you can stop pressing the button.
The instrument remembers its configuration, so you only need to perform this maneuver once. Repeat it to revert to previously active mode: CDC to LibUSB (active LED flashes GREEN), or LibUSB to CDC (active LED flashes YELLOW.) Also, when in the CDC mode COM port interface variables (aside from port name) are “don’t care:” Baud, Data bits, Parity, etc.
Here’s how Windows Device Manager detects the presence of model DI-1100 (for example) for each supported mode: