- Jablotron Port Devices Driver Device
- Jablotron Port Devices Drivers
- Jablotron Port Devices Driver Updater
TL-USBNet Device Driver for Windows 10, 8.1, 8 and 7
1, Download the driver file onto your PC hard drive into a special folder 2, Unpack the driver file using the program Win Rar into the same folder (don´t use Windows or any other commanders for unpacking!!!) 3, Now you can open the device manager COMPUTER/PROPERTIES/DEVICE MANAGER and then connect the JA-80T interface to the PC. Apart from updating your PCI Drivers, installing a Driver Update Tool gives: Up to 3 times faster internet connection and download speeds; Better PC performance for games and audio applications; Smooth-running of all your PC devices such as printers, scanners etc. Better all-round performance of your PC due to automatic driver updates which will. Go to the device manufacturer's website and see if there is a Windows driver available. If you there is, download and install the driver. If that won't solve the problem, accept that you've got a. Installing the drivers ComLink software and its drivers can be found on the enclosed CD-ROM. The latest version can also be found on website www.jablotron.com in the download section. Insert the CD into your CD drive. Connect the JA-80T cable to the control panel and to a free USB socket on your PC as described above.
Thesycon’s TL-USBNet driver provides a network adapter emulation on Windows operating systems by implementing the specific network protocol on USB.
TL-USBNet device driver works with USB devices that are compliant to the following CDC subclasses:
- Ethernet Control Model (CDC/ECM)
- Network Control Model (CDC/NCM)
- Ethernet Emulation Model (CDC/EEM)
The driver implements a network adapter based on Microsoft's network driver model NDIS (Network Driver Interface Specification).
- Supports USB 2.0 full speed and high speed, and USB 3.0 super speed or higher
- Supports devices that are compliant with one of the following device class specifications: CDC/ECM, CDC/NCM, CDC/EEM
- Compatible with device implementations based on the Linux USB gadget framework
- Supports devices that implement a subset of the specification only, i.e. a subset of the required class requests
- Implements an NDIS 6.20 compliant network adapter for Windows 7.
- Implements an NDIS 6.30 compliant network adapter for Windows 8 and Windows 8.1.
- Implements an NDIS 6.50 compliant network adapter for Windows 10.
- USB communication based on WDF (KMDF)
- Optionally the driver supports advanced USB power management including selective suspend (Windows 10 only)
- Driver behavior is highly configurable via customization settings
- Custom features or optimizations can be implemented on request
- Source code is available on request (subject to a separate license agreement)
- 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.
Windows Server 2012 R2
Windows Server 2012
Windows Home Server 2011
Windows Server 2008 R2
Windows Embedded 8 Standard
Windows Embedded Standard 7 (WES7)
Windows Embedded Enterprise
Windows Embedded POSReady
Our software is purely designed and implemented by our team in Germany - no outsourcing. Technical support is provided directly by the developers.
This driver is a replacement for the former USB CDC/ECM, USB CDC/NCM and USB CDC/EEM drivers. Latest version of these drivers is 2.56. Licensees can upgrade to the new TL-USBNet driver.
Current version of TL-USBNet driver: 3.40
The free evaluation version of the TL-USBNet driver works for an interval of 60 days without any limitation. After that evaluation period has expired, the driver stops working.
Current version of driver for Windows CE and Embedded Compact: 1.13
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 is intended for OEMs who want to build a Windows 10 system with USB Type-C connector and want to leverage OS features that allow for faster charging, power delivery, dual role, alternate modes, and error notifications through Billboard devices.
A traditional USB connection uses a cable with a USB A and USB B connector on each end. The USB A connector always plugs in to the host side and the USB B connector connects the function side, which is a device (phone) or peripheral (mouse, keyboard). By using those connectors, you can only connect a host to a function; never a host to another host or a function to another function. The host is the power source provider and the function consumes power from the host.
The traditional configuration limits some scenarios. For example, if a mobile device wants to connect to a peripheral, the device must act as the host and deliver power to the connected device.
The USB Type-C connector, introduced by the USB-IF, defined in the USB 3.1 specification, addresses those limitations. Windows 10 introduces native support for those features.
- Allows for faster charging up to 100W with Power Delivery over USB Type-C.
- Single connector for both USB Hosts and USB Devices.
- Can switch USB roles to support a USB host or device.
- Can switch power roles between sourcing and sinking power.
- Supports other protocols like DisplayPort and Thunderbolt over USB Type-C.
- Introduces USB Billboard device class to provide error notifications for Alternate Modes.
USB Type-C connector is reversible and symmetric.
The main component are: the USB Type-C connector and its port or PD controller that manages the CC pin logic for the connector. Such systems typically have a dual-role controller that can swap the USB role from host to function. It has Display-Out module that allows video signal to be transmitted over USB. Optionally it can support BC1.2 charger detection.
Consider recommendations for the design and development of USB components, including minimum hardware requirements, Windows Hardware Compatibility Program requirements, and other recommendations that build on those requirements.Hardware component guidelines USB
Choose a driver model
Use this flow chart to determine a solution for your USB Type-C system.
|If your system...||Recommended solution...|
|Does not implement PD state machines||Write a client driver to the UcmTcpciCx class extension.|
Write a USB Type-C port controller driver
|Implements PD state machines in hardware or firmware and support USB Type-C Connector System Software Interface (UCSI) over ACPI||Load the Microsoft provided in-box drivers, UcmUcsiCx.sys and UcmUcsiAcpiClient.sys.|
See UCSI driver.
|Implements PD state machines in hardware or firmware, but either does not support UCSI, or support UCSI but requires a transport other than ACPI||Write a client driver for the UcmCx class extension.|
Write a USB Type-C connector driver
Write a USB Type-C Policy Manager client driver
|Implements UCSI but requires a transport other than ACPI||Write a client driver to the UcmUcsiCx class extension.|
Use this sample template and modify it based on a transport that your hardware uses.
Write a UCSI client driver
Bring up drivers
USB Function driver bring-up is only required if you support USB Function mode. If you previously implemented a USB Function driver for a USB micro-B connector, describe the appropriate connectors as USB Type-C in the ACPI tables for the USB Function driver to continue working.
For more information, see instructions about writing a USB Function driver.
USB Role-Switch driver bring-up is only required for devices that have a Dual Role controller that assumes both Host and Function roles. To bring-up the USB Role-Switch driver, you need to modify the ACPI tables to enable the Microsoft in-box USB role-switch driver.
For more information, see the guidance for bringing up the USB Role Switch Driver.
A USB Connector Manager Driver is required for Windows to manage the USB Type-C ports on a system. The bring-up tasks for a USB Connector Manager driver depend on the driver that you choose for the USB Type-C ports: The Microsoft in-box UCSI (UcmUcsiCx.sys and UcmUcsiAcpiClient.sys) driver, a UcmCx client driver, or a UcmTcpciCx client driver. For more information, see the links in the preceding section that describe how to choose the right solution for your USB Type-C system.
Perform various functional and stress tests on systems and devices that expose a USB Type-C connector.
Test USB Type-C systems with USB Type-C ConnEx - Run USB tests included in the Windows Hardware Lab Kit (HLK) for Windows 10.
Jablotron Port Devices Driver Device
Run USB function HLK tests with a C-to-A cable (search for Windows USB Device in the HLK
Jablotron Port Devices Drivers
Certification/ComplianceAttend Power Delivery and USB Type-C compliance workshops hosted by the standards bodies.