1. Driver Downloader
2. Horiba Scientific Usb Devices Driver Download For Windows 7
3. Horiba Scientific Usb Devices Driver Download For Windows 8.1

Frequently Asked Questions

Watch a brief video of HORIBA Scientific's beautiful opening cermony in Piscatway NJ. 60 guests and HORIBA executives from around the world were treated to speeches, a building tour showcasing the bright open office concept, tour of the new 6,400 sq. Application labs, new OEM facilities, a gala luncheon, and a cake cutting ceremony. Support is for Windows XP/Vista/7/8/10 32 & 64 bit. This driver is not compatible with the SC-USB Interface. Note: Install the driver before plugging the cable into your computer. Once the driver has been installed, plug the cable into the computer to finish the installation.

Number of FAQs related to 17394: 7

Expand AllCollapse All

1. A USB-to-serial cable has electronic components in it to interface the USB to the RS-232. There is no pin correlation between USB and DB9.

2. The combination of the USB to serial (17394) and the SC32B is basically the same as the SC-USB. Both options enable communication between a computer and a data logger with a CS I/O port.

3. See the table for a detailed comparison:

   17394 USB-serial cable	SC32B	SC929	SC-USB
   Useful for Connecting	PC USB port to data logger RS- 232 port	Data logger CS I/O port to laptop COM port	Data logger CS I/O port to laptop COM port	Data logger CS I/O port to PC USB port
   Connectors	USB A male – 9-pin male	9-pin male – 9-pin female	9-pin male – 9-pin female	USB B female – 9-pin male
   Length	6 ft	3 in.	6 ft	1.6 in.
   Power Consumption	N/A	Active <200 a=' --200--='>	8 mA continuous	Active <20 ma=' --20--='>
   Optically Isolated	No	Yes	No	Yes
   Operating Temperature	N/A	-25° to +50°C	-25° to +50°C	-25° to +50°C
   Maximum Data Transfer Rate	1 Mbps USB	115200 bps	9600 bps	1 Mbps USB

4. Many of our more recent data loggers have a Micro B USB port. Simply use a Type A to Micro B, male-to-male cable. Although any USB cable, with the correct connectors and drivers, should work, there is a better chance of success using a cable supplied by Campbell Scientific.

   For data loggers with an RS-232 port, only a serial or USB to RS-232 cable (sometimes called a USB-to-serial-adapter cable) is needed. Although any USB to RS-232 cable should work with the appropriate drivers, there is a better chance of success using the USB to RS-232 cables sold by Campbell Scientific.

   There are several options for data loggers that don’t have an RS-232 port but have a CSI/O port:

   1. Use the SC-USB connector/interface instead of the SC32B.
   2. Use the SC32B with a 17394, USB-to-9-pin male RS-232 cable.
   3. Use a user-supplied USB interface with the SC32B.

   For data loggers with a CSI/O and RS-232 or USB port, it is not necessary to use the SC32B unless there is another device connected to the RS-232 port or there are concerns about low-level noise from a permanently connected, ac-powered computer.

5. Some possible causes include the following:

   • The result of a hardware condition in the data logger or the port driver
   • Incorrect USB drivers (Even if the correct drivers have been successfully installed, the errors may still be related to the cable.)
     • Note: Not all USB-to-serial cables are the same. Although any USB to RS-232 cable should work with the appropriate drivers, there is a better chance of success using the USB to RS-232 cables sold by Campbell Scientific. Cables that are not purchased from Campbell Scientific have not been tested and may result in errors when connecting to a data logger. Furthermore, USB-to-serial cables with the FTDI chipset are easier to use and seem to perform better than cables with the Prolific chipset.
   • Power supply or grounding issues on the data logger
   • The port configuration of the data logger (If the data logger RS-232 port is configured at a fixed baud rate other than 115200, it might cause the error messages.)

   The Device Configuration Utility, under its Unknown device type, has an Identify Logger Type button. This button will attempt to identify the device type, protocol, or both used for the data logger and will attempt to do so at various baud rates. If the data logger is synchronized with a different baud rate or is set up at a fixed baud rate, this feature may provide the means of determining what baud rate should be used for successful communication.

6. Communication through the data logger’s CS I/O port requires an interface that converts the computer’s RS-232 voltage levels to the CMOS levels of the data logger. Typically, that interface is an SC32B. The SC32B connects to the data logger’s CS I/O port via an SC12 or serial cable and connects to a computer’s 9-pin serial port via a serial cable. When the computer does not have a serial port, a 9-pin serial-to-USB cable, such as pn 17394, can be used with the SC32B. Alternatively, instead of the SC32B, use the SC-USB.

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

This topic lists the Microsoft-provided drivers for the supported USB device classes.

• Microsoft-provided drivers for USB-IF approved device classes.
• For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
• For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).

If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.

If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.

USB Device classes

USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.

Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.

For general information about USB-IF approved device classes see the USB Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

Device setup classes

Windows categorizes devices by device setup classes, which indicate the functionality of the device.

Driver Downloader

Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.

Two important device setup classes for USB devices are as follows:

• USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.

• USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.

The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.

Horiba Scientific Usb Devices Driver Download For Windows 7

Microsoft-provided USB device class drivers

Horiba Scientific Usb Devices Driver Download For Windows 8.1

Related topics