Drivers Auto-intern Port Devices

Posted By admin  On 23.04.21



  1. Drivers Auto-intern Port Devices Gigabit
  2. Drivers Auto-intern Port Devices Replicator
  3. Drivers Auto-intern Port Devices Lucie
-->

The package provides the installation files for FTDI USB Serial Port Driver version 2.12.16.0. 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.

Versions supported

  • Windows 10
  • Windows 8.1
  • Install the Latest Drivers. There’s a small chance you may need to update your USB 3.0 drivers. First, you must find out which drivers your PC actually needs. You can visit the device manager to find out. Follow the steps below for guidance. Press the Windows Key; Search for Device Manager; Click Device Manager once it appears.
  • If your port is a combo eSATA/USB port, it might only be offering enough power to drive USB devices, not necessarily SATA drives. If you have a way to test with an enclosure or adapter that uses a regular SATA cable and then a wall AC adapter, I'd be curious if that worked.
  • Windows may install drivers for select devices, say the graphics card, under certain circumstances. This happens by default for instance when the device is setup, but may also happen when Microsoft pushes driver updates through Windows Updates.
  • These are the newest CH Drivers for CH Game Port devices. These new drivers will work with the CH F-16 Combatstick, CH F-16 Flightstick, CH Fighterstick, CH Flight Sim Yoke PC, CH Flightstick Pro.

Applies to

  • Device manufacturers of CDC Control devices

Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.

  • Improved PnP and power management by the driver (such as, handling surprise removal).
  • Added power management features such as USB Selective Suspend.

In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.

Usbser.sys installation

Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.

Note

GigabitDrivers

If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.

Windows 10

In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.

USBClass_02

USBClass_02&SubClass_02

  • If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
  • If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
  • If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.

Note

Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.

Windows 8.1 and earlier versions

In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.

Drivers

The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.

For more information, see this KB article.

Configure selective suspend for Usbser.sys

Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:

To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:

  • '0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.

  • '0x00000000': Enters selective suspend only when there are no open handles to the device.

That entry can be added in one of two ways:

  • Write an INF that references the install INF and add the registry entry in the HW.AddReg section.

  • Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.

    For more information, see Microsoft OS Descriptors.

Develop Windows applications for a USB CDC device

If you install Usbser.sys for the USB CDC device, here are the application programming model options:

  • Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.

  • In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:

    Win32 programming model:

    • .NET framework programming model:

Devices

Related topics

Virtual COM Port Drivers for Ross-Tech USB Interfaces

Older Ross-Tech RS-232 Serial interfaces can be set to power up as 'dumb K-Line pass through' interfaces. This allowed those old Serial interfaces to be compatible with a wide variety of third-party applications which expect a 'K-line pass-through' serial interface. However, our USB interfaces present additional challenges. Early in their development, we found a number of technical advantages to using a 'direct' USB driver which bypasses the Windows Serial drivers entirely. Hence the USB drivers that ship with VCDS do not emulate a serial COM port and cannot be used with applications that expect to communicate via a serial port.
NOTE: The following applies to our legacy USB interfaces (HEX-USB, KII-USB and HEX-USB+CAN). It does NOT apply to our current HEX-V2 or HEX-NET interfaces. These new interfaces do not use a USB UART chip and cannot be be used for 'dumb K-line pass-through'!

In order to facilitate the use of third-party applications which expect to communicate with a serial interface, drivers that emulate a COM port are available. However, anyone thinking about using them needs to be aware of the following points:

  • We do not offer installation support for these drivers. They should be used only by someone who is competent/comfortable installing (and possible uninstalling) USB drivers on his PC.

  • We cannot offer any support for third-party software, nor any guarantee that it will work correctly with these drivers. Of course, the same would apply with a serial interface as well.

That said, here some installation notes:

Drivers

Drivers Auto-intern Port Devices Gigabit

  • These drivers are compatible with Windows 2000 and newer. They should work with W2K, XP-32, XP-64, Vista-32 and Vista-64. We do not have any VCP drivers for Windows 98!

  • Unzip the contents of the download into a new folder.

  • With an interface plugged in, find it in Device Manager, right-click it, and select Update Driver.

  • Depending on what drivers your system already has installed, you may have to 'force' these by telling the wizard not to search, but to let you specify what driver to install, then doing the Have Disk and Browse thing.

  • There's also the possibility that the Virtual COM Port won't install automatically. We've found no real pattern why it does on some systems and not on others. If it does not, find the interface in Device > Manager. The name should show '... with VCP'. Open the properties sheet, click the Advanced tab, and make sure Load VCP is checked. Once checked, disconnect and re-connect the interface.

  • Once the USB Serial Port is installed, you may need to change the COM Port Number (depending on how high a number the applications supports). Device Manager, Properties sheet for the USB Serial Port, Port Settings tab, Advanced button. The COM Port Number may change if you plug the interface into a different USB port, so I'd recommend always using the same USB port.

  • VCDS should continue to work fine with these drivers installed. Leave VCDS set to USB, not a Virtual COM Port!

Drivers Auto-intern Port Devices Replicator

Assuming you've read and understand all of the above, you can download the 'Virtual COM Port' drivers here:

Drivers Auto-intern Port Devices Lucie

Home
Products
 VCDS
Product Information
Interfaces
TWIN-USBKII-USB HEX-USB+CAN
Virtual COM Port Drivers