PEAK-System Forum

I have the following setup:

Lenovo Thinkpad x201 running Win 7 64 bit. Due to 64 bit hassles with some of the development software I use, I do all my development on a virtualised 32 bit WinXP instance and everything works well.

Today I received my PCAN USB device and tried to get it running in this virtualised environment. The installation went well, however the problems started when I tried to mount/attach the PCAN USB device in the virtualised environment:
The first time I tried mounting the PCAN USB device nothing seemed to happen. I waited a bit as it normally takes a few seconds for the virtualised environment to see new USB devices. Nothing happened. I then tried mounting the device again and received the following error:
I've used Virtualbox long enough to know that when you get these types of messages, the best thing is to just reboot both the guest and host operating systems. I did this twice and still the same thing happens.

Naturally, when I fire up PCAN-View in my 32 bit WinXP instance there are no available CAN devices.

Having browsed through the forums I can see that a few others are using the PCAN USB device in Virtualbox virtualised environments so I would really appreciate some help to get this working.

As an aside, mounting other USB devices in my 32 bit WinXP instance works fine, so I know the problem isn't with Virtualbox passing through the USB messages to the guest system.

As I have to use the PCAN USB device this coming Monday for an important project, I decided to install it on my Win 7 host system where it works fine.

Hi,

normally the usage of the PCAN-USB adaptor inside a virtual enviroment is not a problem. But it can not be guaranteed by us. It looks that something block the device. In the past i had an similar problem with an AMD-PC (AMD Phenom processor + AMD chipset @ Win7 64 host + Win XP guest). The problem was the "AMD usb filter driver" (for audio devices and so on). After uninstalling the "AMD usb filter driver" everythings work as expected. Maybe it´s a similar problem with your Intel powered PC. Sometimes it helps to create an empty USB filter.
It hope this infos are useful.

regards
Gunther

Hi roy.emmerich.

I'm having the same problems with VirtualBox (v4.1.16) with VirtualBox extension pack installed.
Did you ever get the PCAN-USB adapter working with WinXP virtualbox?

Hi ,

there´s a PCAN-USB adaptor running @Win XP 32bit under a Win 7 64bit host on my desk.

here are some details:

host: Windows 7 64bit
guest: Windows XP 32bit
CPU: AMD Phenom X6
VirtualBox version: 4.1.18
VirtualBox extension pack : 4.1.18
VirtualBox USB-2.0-Controller: not active
PCAN-USB driver version: pcan_usb.sys version 3.6.3.9864 (out of date)
AMD usb filter driver: not installed

But note: we cannot guarantee the proper function
regards
Gunther

HI all, I have an ASUS K53S and I'm having problem using pcan-usb with a virtual box.

Although I could use it from Ubuntu:
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 004: ID 04b3:310b IBM Corp. Red Wheel Mouse
Bus 001 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 002: ID 0c72:000c PEAK System PCAN-USB

the oracle virtual box version 4.1.12 does not show the driver among the ones available.

Do you have any idea why?

Thanks
Vincenzo

Problem solved whatching other users screen shot. Thanks

Found this solution on Mac thread, worked fine for me:

1) "Add filter from device"
2) Edit the filter entry and clear everything except the "Name:" field.
3) Reboot and connect the device (evtl. also reboot the host).

The method recommended by neuweiler (remove everything but the Name field in the filter for the PEAK device) *almost* worked for me, except that the next time I closed and restarted the VM, it captured *all* of my USB devices, including a USB mouse and keyboard, which was not at all desirable.

What *did* finally work for me was removing only the information from the "Product" field, as recommended in a comment on the VirtualBox forums: https://www.virtualbox.org/ticket/10309#comment:5

So far, VirtualBox has successfully captured the device under every use case I've tested (dock/undock my laptop, close/reopen the VM, etc.). I think I've *finally* got this fully solved (fingers crossed!), after at least two full days of tearing my hair out in frustration!