How i am able to connect my device?

[DanielNowak98]

Hey, thanks for your work! I would like to connect my device (HEX-V2) and would like to use it over wine. I run into the problem, that the device could not be found USB-Bibliothek: 03.02.07

Do you know any way to fix this ? You got the device running ?

[cryinkfly]

@DanielNowak98 Unfortunately, I haven't been able to test it myself because I don't have the hardware to do it.

And are you a member of the following groups with your Linux user:

• lp
• tty
• dialout

More information about these groups can you find here: https://wiki.debian.org/SystemGroups

... because that's the only way you'll have access to the advice.

[DanielNowak98]

yes, i am member of your mentioned groups.

[davidbitterlich]

Device connection support would be really awesome, but I doubt that it is possible. As far as I know this software, it requires a Windows-only driver to connect to the device and afterwards the software is able to connect to cars and read from the OBD2 interface.

For this purpose, I always use a Windows VM and pass the USB device through. This even works on VirtualBox.

[PMKrol]

Few things to do to connect to Your car (despite installation script): link your ttyUSBx device to com1 of wine. chmod 777 ttyUSBx, set baud to 9600 by stty.

I have script which fires up stty constantly. Works for me for most of subdevices - unfortunately not all. I installed VCDS by PlayOnLinux.

[davidbitterlich]

Hi, I just wanted to give it a try with installing the software in wine and passthrough the hardware dongle via com. Unfortunately I cannot see the device as ttyUSB something. All I have in /dev is usb and vboxusb when it comes to USB... However the device is plugged in and I can see it via lsusb:

Bus 001 Device 002: ID 0403:fa24 Future Technology Devices International, Ltd MFT HEX-USB

Seems like my Kernel does not have a driver for it?

Well, in /sys/kernel/debug/usb/devices I can read the following regarding my device: S: Product=MFT HEX-USB S: SerialNumber=RT000001 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 50mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

Driver=(none), I can find an entry in /dev/bus/usb/001/002 but I guess this does not help me.

I have no clue what's wrong on my side, I'm using Ubuntu with Kernel 6.5

May you tell more in detail how you managed to setup the connection?

Sincererly David

[PMKrol]

List Your /dev before and after attaching USB. Check for differences.

---

Od: David Bitterlich @.> Wysłane: piątek, 29 marca 2024 11:16 Do: cryinkfly/VCDS-VAG-COM-Diagnosis-system-for-Linux @.> DW: Patryk Król @.>; Comment @.> Temat: Re: [cryinkfly/VCDS-VAG-COM-Diagnosis-system-for-Linux] How i am able to connect my device? (Issue #4)

Hi, I just wanted to give it a try with installing the software in wine and passthrough the hardware dongle via com. Unfortunately I cannot see the device as ttyUSB something. All I have in /dev is usb and vboxusb when it comes to USB... However the device is plugged in and I can see it via lsusb:

Bus 001 Device 002: ID 0403:fa24 Future Technology Devices International, Ltd MFT HEX-USB

Seems like my Kernel does not have a driver for it?

Well, in /sys/kernel/debug/usb/devices I can read the following regarding my device: S: Product=MFT HEX-USB S: SerialNumber=RT000001 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr= 50mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms Driver=(none), I can find an entry in /dev/bus/usb/001/002 but I guess this does not help me.

I have no clue what's wrong on my side, I'm using Ubuntu with Kernel 6.5

May you tell more in detail how you managed to setup the connection?

Sincererly David

— Reply to this email directly, view it on GitHubhttps://github.com/cryinkfly/VCDS-VAG-COM-Diagnosis-system-for-Linux/issues/4#issuecomment-2027024950, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVENA2UKRVGHKY6ZLG5Q7QTY2UWOTAVCNFSM6AAAAAAUGFEUPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXGAZDIOJVGA. You are receiving this because you commented.Message ID: @.***>

[davidbitterlich]

That's what I did, but there were no differences. As the log from /sys/kernel/debug/usb/devices indicates, the Kernel does not know which driver it should use for this device and so it does not use any driver and therefore I do not have a device file in /dev directly (such as ttyUSB0). I took a look whether I could manually try to load a device driver for this device, but I did not have much success on this, yet.

[PMKrol]

According to this: https://forum.winehq.org/viewtopic.php?t=34864, it seems that it is not „normal” serial interface ;(.

[davidbitterlich]

Yes you're right and it's pretty sad. I've found out that the manufacturer provides a driver which provides a virtual com port, but still it's windows-only: https://www.ross-tech.com/vag-com/usb/virtual-com-port.php

Maybe the whole topic is a dead-end on Linux. There's a tool called scantool, which can be used with different OBD-II compliant USB devices if they provide a com port ( https://github.com/kees/scantool ). However, I'm not sure if this software requies specific devices (on the scantool.net page I can see that they offer different adapters) and if it is compatible with particular car manufacturers and their cars (like the VAG stuff with its compatibility to Seat, VW, Audi etc. which is the reason why I want to use the adapter and the software...).

If we would like to have support for those adapters, we would need someone who can disassamble the windows driver and create a Linux compatible driver based on his findings...