Acces to usb port for com interface

[perco]

Hello,

I have just purchased an OBD cable for the diagnosis of VW group cars.
The software communicates with the interface via an USB cable.
The installation of the software (which exists only on Windows) went well with playonlinux.
The software launches but during the connection test, it sends me an error.

"Interface ross-tech not found !
USB library version : 03.02.07
Interface not found"

RMQ : lsusb detects well the ross-tech chip of the interface.
"Bus 001 Device 009: ID 0403:fa24 Future Technology Devices International, Ltd Ross-Tech HEX-USB".

The interface and software are ok with a Win7 on virtualbox.

On the forum "Playonlinux" I found USB support was lacking.
in 2011: https://www.playonlinux.com/fr/topic-41 ... e_USB.html
in 2014: https://www.playonlinux.com/fr/topic-12 ... LINUX.html

Has it evolved since then?
In the page : https://wiki.winehq.org/Building_Wine ; They say "libusb library needed if you use an application that needs to access the usb port directly."

The problem is that there are a lot of " libusb* " librairies.
Has Someone an idee.

Thank you in advance for your answer.

Perco.

[fargodwe]

What does lsusb -t show?

[perco]

Code: Select all

perco@perco-OHR2:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 1: Dev 9, If 0, Class=Vendor Specific Class, Driver=, 12M
    |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 6: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 7: Dev 5, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M

[fargodwe]

I'm a novice at this myself. What I do see is that your output lists bus 1 device 9. Looking at the lsusb -t output shows

Code: Select all

    |__ Port 1: Dev 9, If 0, Class=Vendor Specific Class, Driver=, 12M

I *think* that means there is no driver loaded for the device at the linux level. I believe wine is still directing the i/o through the linux device, so with no driver it can't communicate with the device. I think you'll need some sort of linux driver for the device.

Depending on the device it might also need virtual serial device drivers. I think they are used when you have a device that plugs into a USB port but emulates a serial device. Do you have the model name/number for the device?

[perco]

Hello,

The usb/rs232 interface chip is an FTDI 232 R.

Thanks for your help.

[fargodwe]

I did find this page https://www.fir3net.com/UNIX/Linux/how- ... linux.html for how someone got it working for their device.

Based on that and the output you provided, I would try:

Code: Select all

sudo modprobe usbserial vendor=0x0403 product=0xfa24

Then, following that page, do

Code: Select all

dmesg

and see if it shows the device as registered. Then, again following that page, do

Code: Select all

sudo minicom -s

to set the parameters for your serial device.

After that you might need to set some sort of parameter in your software for what device it should use.

Keep in mind I'm just a novice here and also don't have access to such a device or the software so I can only go by what I saw on the net. There are some extremely knowledgable people here on the forums and hopefully one of them will see this thread and be able to help more.

[fargodwe]

It's too late to edit the above, but by "it" I didn't mean your same device but rather getting a serial device on usb working.

[perco]

Hello,
After having proceeded as said, here it is:

Code: Select all

perco@perco-OHR2:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 8087:07dc Intel Corp. 
Bus 001 Device 002: ID 10f1:1a63 Importek Webcam HD
Bus 001 Device 006: ID 0403:fa24 Future Technology Devices International, Ltd Ross-Tech HEX-USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

perco@perco-OHR2:~$ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=usbserial_generic, 12M
    |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 6: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 7: Dev 4, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M

[code]perco@perco-OHR2:~$ dmseg
[ 1591.886277] usb 1-2: new full-speed USB device number 6 using xhci_hcd
[ 1592.044637] usb 1-2: New USB device found, idVendor=0403, idProduct=fa24, bcdDevice= 6.00
[ 1592.044639] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1592.044641] usb 1-2: Product: Ross-Tech HEX-USB
[ 1592.044643] usb 1-2: Manufacturer: Ross-Tech
[ 1592.044644] usb 1-2: SerialNumber: RT000001
[ 2015.603810] usbcore: registered new interface driver usbserial_generic
[ 2015.603884] usbserial: USB Serial support registered for generic
[ 2015.603909] usbserial_generic 1-2:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 2015.603911] usbserial_generic 1-2:1.0: Tell [email protected] to add your device to a proper driver.
[ 2015.603913] usbserial_generic 1-2:1.0: generic converter detected
[ 2015.604088] usb 1-2: generic converter now attached to ttyUSB0

After that, I de-reinstall the software with playonlinux.
I select "USB" in the software.

But the error is the same :
"interface Ross-Tech usb not found
library version usb: 03.02.07
Interface not found"

It seems that the .EXE doesn't make the link with "ttyUSB0"...

Any idea?

[fargodwe]

Looks like I may have been on a red herring. According to https://www.ross-tech.com/vag-com/old-i ... es/huc.php, which matches the device you show, it does not use the usb/serial device drivers, but instead has separate drivers for Windows itself. Any support it seems you have to pay a registration fee for first at their site.

I hate to say it, but I'm out of ideas. Perhaps one of the experts on the forums might be able to help.

[perco]

Thank you for your help,
A lot of windows drivers are provided with the software package but it seems that "playonlinux" doesn't use them...
In the meantime, I keep looking and use the software in a windows 7 in virtualbox.
Making it work with playonlinux would be a plus...
To be continued...
Perco.