• Usb Passthru Driver ( Multi-instance ) Driver Installer
• Usb Passthru Driver ( Multi-instance ) Driver Download
• Usb Passthru Driver ( Multi-instance ) Drivers

If you plan to attach USB devices that use MTP drivers, such as Android-based Samsung smart phones and tablets, configure Horizon Client so that it automatically connects USB devices to your remote desktop. Otherwise, if you try to manually redirect the USB device by using a menu item, the device is not redirected unless you unplug the device. I tested on a peugeot 407 2009, with passthru 1G, no module detected with pp2000 (because the vci1 needs obd1n adapter to swtich pins from 6+14 to 3+8, same for multi-diag software), but last i flashed the 1.6.6 firmware that was in that tutorial to make some more tests. If you flash that firmware, the vci will power on directly to 'usb. When use I-2016.1 multi diag access to diagnose vehicle, please ensure the “USB PassThru Driver (Multi-instance)” is read out (see following pic). Access a USB device in a VirtualBox Guest. VirtualBox 5.0 provides support for USB 3.0 devices if you install its Extension Pack.After the extension pack is in place, start your Virtual Machine whether running as a guest on a Linux or Windows computer.

Since 4.0.2, Dolphin has the ability to passthrough USB HID devices designed for use with Wii software. 5.0-2352 enables USB passthrough for all devices. This gives emulated Wii software full control of a hardware device connected to your PC. This is very useful for devices not currently emulated by Dolphin and games that highly depend on extra hardware.

• 2Setting up
  • 2.2Windows
    • 2.2.1Install Dedicated Driver
• 3Configuring Dolphin

List of Wii Devices and IDs

Setting up

Linux

Linux support does not require any special drivers. However, a udev rule must be created to allow access to the devices. Note, the Vendor ID and Product ID SHOULD be verified from the device itself before creating the rule.

1. Paste the following into /etc/udev/rules.d/52-dolphin.rules (/lib/udev/rules.d/52-dolphin.rules if making a package). Do not forget to replace the XXXX with the appropriate Vendor and Product IDs.

SUBSYSTEM'usb', ENV{DEVTYPE}'usb_device', ATTRS{idVendor}'XXXX', ATTRS{idProduct}'XXXX', MODE='0666'

2. Reload udev rules with:sudo udevadm control --reload-rules

3. Reinsert the accessory.

Windows

For users wishing to use the USB Microphone, USB Camera, or Wii Speak, it is highly recommended to use 5.0-10617 or newer. It contains important fixes to both libusb and Dolphin that fix crashes and fix support in devices across many games.

Install Dedicated Driver

Single Interface Devices

Download and open Zadig, then:

1. In the 'Options' menu in Zadig, make sure 'List All Devices' is enabled.

2. Look through the devices for the device to passthrough.

3. On the right column, select 'libusbk' then click 'Replace Driver'. Select 'Yes' to modify the system driver.

Multi Interface Devices

For Microphone, Wii Speak, and USB Camera Passthrough, installing over the composite parent device is required.

Download and open Zadig, then:

1. In the 'Options' menu in Zadig, make sure 'List All Devices' is enabled and 'Ignore Hubs or Composite Parents' is disabled.

2. Look through the composite parent of the device you wish to passthrough.

3. On the right column, select 'libusbk' then click 'Replace Driver'. It may warn you that you're modifying a kernel driver, but, this is normal. Select 'Yes' to modify the kernel driver.

Uninstalling Dedicated Driver

If for some reason you wish to restore the default driver to the device, open up 'Device Manager.' In the last, expand 'libusbK devices' and find the device you wish to restore. Uninstall the device, then unplug the device and plug it back in. It will now be restored to its original state.

If you were using the WinUSB driver, the device will be located under 'Universal Serial Bus Devices' instead, but the instructions are identical otherwise.

usbdk driver

usbdk is no longer supported nor recommended. While it provides the ability to simply install a driver without any further instructions, usbdk suffers severe instability issues. For legacy purposes, you can still use the x64 usbdk driver in older builds.

macOS

While this can be done in macOS, there is currently no easy to use guide for it. A modified variant of the Native GameCube Adapter for Wii U guide should work, but what needs to be changed is not immediately apparent.

Android

This feature is not supported on Android.

Configuring Dolphin

In 5.0-2352, an additional step was added for USB Passthrough. Because some devices being plugged into your computer can potentially hang or crash a game, you now must whitelist the emulated Wii so it can access this device. This is not required for Bluetooth Passthrough.

Guide to Whitelist a USB Device in Dolphin

1. Open Dolphin's configuration dialog.

2. Click on the Wii tab.

3. In the 'Whitelisted USB passthrough devices', click on the 'Add...' button.

4. Select the device you wish to passthrough.

Topic: VAS5054A PassThru Driver for Xentry PassThru on Windows 10 x64

Xentry PassThru needs to be installed on Windows x64 to support new models, such as Euro5/6, W205, W213, W222 … However, VAS5054A didn’t work on 64bits as passthru. There was 64bits device driver for VAS5054A but there was no PassThru driver working on 64bits.

This is a 64bit device drivers along with a patched PassThru API files working on Windows 10 x64. Xentry recognizes it and works with W205 (confirmed), etc.

WARNING: Use it on your own risk, only for test purpose.

What you need:

(1) VAS5054A hardware.
(2) (option) VAS5054A EDIC_PDU_API 1.20.4x driver installation file. You can find it somewhere on this forum (see below).
(3) (option) New firmware. The firmware included here is version 1.20.41 for better compatibility, not 1.20.42.
(4) Softing_VAS5054A_PassThru_Driver_x64_v3.zip (attached here)
(5) 64bit Windows 10
(6) (option) DC 12V 1A power adapter, 2 jumper wires for temporary power.

Pre Installation:

(1) Install Xentry PassThru and all patches.
(2) (option) Install EDIC_PDU_API 1_20_42 driver (or EDIC_PDU_API 1_20_41). It’s for installing .NET framework or VC++ redistribution files.

If you are going to do clean install on fresh Windows 10, you might want to install the EDIC_PDU_API driver. It installs .NET framework, VC++ files, some EDIC DLLs on /Windows/System32 or SysWow64. Other files will be overwritten by the following manual installation. If you don’t know where to find it, one version is https://mega.nz/#!Q9QGQYaQ!CrilUUH-IS8QJqoWPfVkHeYai8C6QxX3EB8j_Ta4Uz8 (your own risk).

Installation:

Usb Passthru Driver ( Multi-instance ) Driver Installer

(1) Copy “Program Files (x86)Softing*” to your HDD “C:Program Files (x86)Softing*”
(2) Copy “Program DataD-PDU API” to your HDD “C:Program DataD-PDU API”.
(3) Double click on “Softing_VAS5054A_PassThru_1_20_042.reg” and install it.
(4) Make a shortcut of “SftngCM.exe” on Desktop.
(5) Right click on “C:Program Files (x86)SoftingEdicDriverwin7softingedic7_ntamd64.inf” and install.
(6) Connect the VAS5054A hardware using an USB cable. Connect it to a temporary power(12V DC adapter) or OBD-2 port of your vehicle.
(7) Check “Control Panel/Devices Manager/Softing…”. If it’s not installed correctly, update the device driver manually.
(8) Make a shortcut of “EDICConfig.exe” on Desktop.
(9) (option) If you have newer version than EDIC_PDU_API 1_20_42 driver and genuine VAS5054A hardware, you may install the API driver now.

Post Installation:

(1) Connect the VAS5054a to a temporary power(12V DC adapter) or ODB-2 port of your vehicle.
(2) Run “SftngCM.exe” on desktop as administrator. Make a “C:Temp” directory if not exists. This is for saving log files. If not exists, SftingCM.exe will cause error when doing test.
(3) Choose “VAS5054A” and type the serial number (maybe 0821xxxxx).
(4) Select “Test” and click on “Start Test”.
– RED dot : PC <-> VAS5054A does not communicate. Something wrong on your driver.
– YELLOW dot : PC <-> VAS5054A communicates.
– GREEN dot : PC <-> VAS5054A <-> Vehicle communicates.

Tip:

(1) “.NET Framework 2.0/3.0/3.5” needs to be installed if not installed automatically. You can install it by selecting on “Control Panel/Programs and Features/Turn Windows features on or off/.NET Framework 3.5(includes .NET 2.0 and 3.0)”. You also need to install VC++ redistributions if not done yet. (MSVCR100.dll, mfc100.dll, … errors)

Usb Passthru Driver ( Multi-instance ) Driver Download

(2) Temporary power to VAS5054A for test purpose : Ground to either pin 4 or 5. 12V DC to pin 16.

(3) You can upgrade the EDICDriver in “Program Files (x86)SoftingEDICDriver” if you have newer version. Update the device driver on control panel.

(4) If you installed newer version EDIC_PDU_API driver than 1.20.42, edit the *.reg and change the number 1_20_42 to your number (for example, “EDIC_D_PDU_API_1_20_042” to “EDIC_D_PDU_API_1_20_0XX”). After editing, double click on it and install it again.

(5) If your device has different serial number but SftngCM.exe doesn’t allow the change, edit the *.reg file with text editor, double click on it and install it again.

Note: How to set up bluetooth connection for VAS5054a

1.Pairing device and assign for COMport from windows.
(note. Device need disconnect via USB when pairing device)
2.Run “EDIC Hardware Installation.exe” and ADD device.
(see picture)
[attachment=84460]
3.Run “EDIC Configuration Manager.exe” and confirm assigned COM port in bluetooth.
(see picture)
[attachment=84461]

4.Run “SftngCM.exe” and connection test. So green signal is OK.

Again, it’s on your own risk! No one holds any responsibility of it.

Usb Passthru Driver ( Multi-instance ) Drivers

For sake of security, you’re advised to use Xentry with sd connect c4 mux and odis with vas5054a head.

I’m hoping that this will be helpful.

(Credits to medianjoe)