Universal USB Development Kit for Windows 10, 8.1, 8 and 7

Secret Labs Usb Devices Drivers

Trouble connecting Assistant AS-5433 Secret to Computer? Download and Install Official Assistant AS-5433 Secret USB Driver for Windows 7, 10, 8, 8.1 or XP PC. Also, download Assistant AS-5433. USB 2861 Device and related drivers. If you used to like to fix your Touchmate android device with the computer, then you will need to download Touchmate USB drivers given here and install it. Download USB Driver for Android Devices - USB Drive for Android phones, moreover contains software links, from manufacturer, Samsung Kies, Sony PC Companion, Lg Pc Suite.You can find the.

FeaturesSupported PlatformsDemoPrices

Standard USB devices are normally supported by class drivers included in the Windows operating system. In many cases, a particular USB device cannot be assigned to a device class because it has to fulfill different requirements, or because implementing the class specification in the device firmware is too time-consuming. This makes a custom USB device driver development necessary; a kernel-mode driver which conforms to the Windows Driver Model (WDM).

The development and debugging process of such a kernel-mode driver is very time-consuming, especially if the driver has to support different Windows versions. For this reason, Thesycon has developed the generic USB device driver USBIO. The USBIO software components can be integrated into a final product with product-specific adaptations (e.g. file names, installation paths, copyright messages). The result is a customized version that can be shipped as part of an end user product.

• Complete USB functionality is supported. The driver is optimized for maximum efficiency. The USBIO driver supports USB 3.0, USB 2.0 and USB 1.1. It supports low, full, high speed and super speed mode.
• The USBIO driver supports all current 32 bit and 64 bit Windows operating systems.
• Supports the USB transfer types Control, Interrupt, Bulk, and Isochronous.
• Provides an interface to USB endpoints (pipes) that is similar to Win32 file I/O interface.
• Provides full support for asynchronous (overlapped) data transfer operations.
• Fully support for hot plug and play. It supports Plug&Play notifications for applications.
• Supports the Windows power management model.
• Optionally the driver supports advanced USB power management including selective suspend (Windows 10 only)
• Provides an interface to USB devices that can be used by any Windows 32/64 bit applications. Multiple applications can use the USBIO driver at the same time.
• Can be used with devices that implement multiple USB configurations. It supports switching between different USB configurations.
• Can be used with devices that implement multiple USB interfaces. In this case a multi-interface driver is required.
• Multiple USB devices can be controlled by USBIO at the same time.
• Provides a Windows programming interface for use in C, C++ and Java programs. A high-level programming interface, the USBIO COM interface, is also available.
• Several source code examples demonstrate usage of the programming interfaces and show how an application controls a USB device.

Secret Labs Usb Devices Driver Updater

• The driver will be delivered fully customized for licensee’s product.
• Customization includes USB VID/PID, file names, text strings, etc.
• Windows 10 version of the driver is signed with Microsoft Attestation signing.
• Windows 7/8 version of the driver is signed with Thesycon’s code signing certificate.
• Driver Customization Kit add-on: The Driver Customization Kit enables licensee to customize the driver by themselves.

• Supported scenarios: first-time installation, driver update, removal of driver software
• Interactive mode with graphical user interface
• Silent mode without user interface, enables integration into surrounding software installers
• Supports popup-free installation

The driver is conform with current WHQL and Hardware Lab Kit (HLK) requirements. To get a WHQL certification, HLK tests must be executed with licensee's device which can be done by licensee or Thesycon. If you are interested in a WHQL certification, please contact Thesycon for a quotation.

Our software is purely designed and implemented by our team in Germany - no outsourcing. Technical support is provided directly by the developers.

Current version: 3.40

To receive a free demo, prices or license agreement, please fill out the contact form.

The free evaluation version of the USBIO driver works for an interval of 60 days without any limitation. After that evaluation period has expired, the driver stops working.

NOTE: The driver described on this page is *not for use by end users*. It will not help solve any problems you may experience with a consumer device such as a webcam, camcorder, card reader, external sound card, etc. Thesycon’s device drivers are software components intended to be used by hardware or software manufacturers to create end products.

For each USB device model an official USB vendor ID (VID) is required. Vendor IDs must be unique and will be assigned by the USB Implementers Forum (www.usb.org). Registration fees will be charged.

Thesycon owns a USB vendor ID and provides a subset of product IDs (PID) to licensees of Thesycon drivers.

© 2021 THESYCON

-->

This topic describes best practices about implementing the remote wakeup capability in a client driver.

USB devices that can respond to external wake signals while suspended are said to have a remote wakeup capability. Examples of devices that have a remote wakeup capability are mice, keyboards, USB hubs, modems (wake on ring), NICs, wake on cable insertion. All of these devices are capable of producing remote wake signaling. Devices that are not capable of generating remote wake signaling include video cameras, mass storage devices, audio devices, and printers.

Drivers for devices that support remote wakeup signaling must issue an IRP_MN_WAIT_WAKE IRP, also known as a wait wake IRP, to arm the device for remote wakeup. The wait wake mechanism is described in the section Supporting Devices That Have Wake-Up Capabilities.

When Does the System Enable Remote Wakeup on a USB Leaf Device?

In USB terminology, a USB device is enabled for remote wakeup when its DEVICE_REMOTE_WAKEUP feature is set. The USB specification specifies that host software must set the remote wakeup feature on a device 'only just prior' to putting the device to sleep.

For this reason, the USB stack does not set the DEVICE_REMOTE_WAKEUP feature on a device after receiving a wait wake IRP for the device. Instead, it waits until it receives a IRP_MN_SET_POWER request to change the WDM device state of the device to D1/D2. Under most circumstances, when the USB stack receives this request, it both sets the remote wakeup feature on the device and puts the device to sleep by suspending the device's upstream port. When you design and debug your driver, you should keep in mind that there is a loose relationship between arming a USB device for wakeup in software, by means of a wait wake IRP, and arming the device for wakeup in hardware by setting the remote wakeup feature.

The USB stack does not enable the device for remote wakeup when it receives a request to change the device to a sleep state of D3, because according to the WDM power model, devices in D3 cannot wake the system.

Why Does Attaching or Detaching My Device Produce a Different Wakeup Behavior in Windows XP and Windows Vista and later versions of Windows?

Another unique aspect of the USB implementation of the WDM power mode regards the arming of USB hubs for remote wakeup. In Microsoft Windows XP all hub devices between host controller and the USB device are armed for wakeup whenever the USB device is armed for wakeup. This produces the surprising consequence that when sleeping devices are detached they will wake up the system.

In Windows Vista and later versions of Windows, if a USB leaf device on the bus is armed for wake, the USB stack will also arm the USB host controller for wake, but it will not necessarily arm any of the USB hubs upstream of the device. The USB hub driver arms a hub for remote wakeup only if the USB stack is configured to wake up the system on attach and detach (plug/unplug) events.

Note UHCI (Universal Host Controller Interface) USB host controllers do not distinguish between remote wake signaling and connect change events on root hub ports. This means the system will always wake from a low system power state if a USB device is connected to or disconnected from a root hub port, if there is at least one device behind the UHCI controller that is armed for wake.

Related topics