Vag com для linux

Сообщение SinnerLike » 07 апр 2015, 06:02

Добрый день!
Хочу снести винду; до сих пор она у меня на ноуте только из-за программы для диагностики, при том что пользуюсь я ею очень редко.

Кто нибудь пробовал запускать нашу программу?
Например под Wine или быть может на виртуальной машине kvm?
Получится это сделать или не тратить время и силы?

Re: ubuntu + Avtoadapter

Сообщение ilia2108 » 09 апр 2015, 00:04

Re: ubuntu + Avtoadapter

Сообщение SinnerLike » 09 апр 2015, 13:56

Спасибо за информацию.
Тоже по макам мне сказали что там можно жестко отдать устройство и с драйверами никаких проблем не возникнет.

А вот в убунту написали что можно всю шину отдать если возникнет проблема.
В общем буду пробовать, если заработает отпишусь

Re: ubuntu + Avtoadapter

Сообщение LittleTOXA » 15 апр 2015, 01:21

Re: ubuntu + Avtoadapter

Сообщение SinnerLike » 17 апр 2015, 06:57

Re: ubuntu + Avtoadapter

Сообщение SinnerLike » 17 апр 2015, 10:10

Источник

VAG-COM (OBD-II USB FTDI) using Wine on Linux

This article explains how to install and set up VAG-COM in Linux using Wine via a Serial Port USB ODB Dongle (FDTI RS232 to USB to ODB industry standard male plug).

A common method is to use a virtual-machine, install Windows and then do all work from there, but that is quite time-consuming and VAG-COM is working just fine using Wine with minimal configuration (Depending on version of software. My setup is listed below)

This should also work for old-fashioned Serial cables, but I have not tested this (But I’ve read elsewhere that this is confirmed).

Introduction:

I own an Audi A4 and needed to do some diagnostics because of some problems with the engine. Doing this in an auto-shop would cost me about $100, so that was out of the question.

After doing some searching on-line i found a OBD-II cable with software for about $20 (incl. freight) . It was bought from a dealer in my country, but these things can be found all over Ebay in the same price-range. There are even wireless dongles with bluetooth available (More on that in an upcoming article).

I got Ross-Tech VCDS Lite software on a CD, but latest version is available for free at Ross-Tech’s website. This is essentially a demo-version that has some restrictions (a full version license is really expensive).

Computer Setup:

A Lenovo R400 Laptop, running Gentoo/Funtoo linux. Should work on just about anything, including 32- and 64- bit architectures.

My setup: 2.6.35-gentoo-r1+ and wine from GIT (revision cc945706a4933cda0d204ba07a13e93fccb66d18 2010-09-01)

UPDATE Sep. 2011: Running 3.0.3 x64 Gentoo (Funtoo) Linux, Wine 1.3.27, VCDS-Lite Free

UPDATE Jul. 2012: Running 3.4.4 x64 Gentoo (Funtoo) Linux, Wine 1.5.6, VAG-COM 302 Registered

Kernel Module

Most distributions has built-in support for this, so if you are running Ubuntu or any other automatically maintained distribution you can skip this section 🙂

Since I use a Gentoo-derived distro, some kernel configuration and compiling was required. Support for these cables is added with the option CONFIG_USB_SERIAL_FTDI_SIO

No difference if you compile this into the kernel instead of creating a module.

Check if driver is loading (Optional)

You should see something like this when plugging in the cable (in syslog):

Setup COM device in Wine

Create a symlink to let Wine know which USB Serial-Device we are using. In this case COM1 using the device ttyUSB0 (This is the default name if you only have one device connected)

More information can be found in Wine User Guide.

Install VAG-COM

NOTE: If you can’t get the installer working try to extract the contents of the executable. Some of the installers is just a zipped file or a InstallShield archive (these can be extracted using ‘unshield’).

Run installer with ‘wine ‘. After Install is completed you can run VAG-COM from your applications menu or manually by ‘wine

/.wine/drive_c/Program Files/Rosstech/VAG-COM/vag-com.exe‘ (or something similar).

VAG-COM Setup

Plug the cable into the ODB port (in my case it was located in the rear ash-tray, under a plastic lid) in and set your ignition to ON .

In VAG-COM’s main menu click the Options button, select COM1 (or which ever port you created a symlink for, as seen above) and run the tests. If the resulting dialogs says everything is fine, you can now run diagnostics etc.

NOTE: Some of these cables comes with a LED-indicator that will light up when connection to computer is active.. If the indicator does not work, don’t fear…. there are a LOT of after-market cables are behaving differently. This is not critical.

Results

Everything works with my setup. No crashes, and every function works fine.

Alternate Software

There are some open-source alternatives for VAG-COM. These also work under Linux. I’ve yet to try these, but I plan to (and create articles).

About the Cars tested:

1996 Audi A4 (B5, Imported from Germany)
- ODB Protocol KW1281 (ISO 9141-2 ?)

Like this:

About this entry

You’re currently reading “VAG-COM (OBD-II USB FTDI) using Wine on Linux,” an entry on Anders Evenrud’s Blog

14 Comments

good joob! can you instal vag-com on Android 2.2.

The USB dongle should be compatible with android devices since it’s just a serial-adapter. But as far as I know there is no Wine or VAG-COM compatible with android devices (since it’s not running on GNU linux libs).

What version of Wine was used ?

What version of Wine was used?

I think it was 1.1.x series. It was compiled from source in Gentoo Linux.

following your steps I was hoping to get this sorted but unfortunately my USB cable is not recognized correctly. I also have another FTDI cable (which serves a completely different purpose) which does work a charm.

My FTDI Cable:
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.300143] usb 2-2: >new full-speed USB device number 8 using uhci_hcd
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.498205] usb 2-2: >New USB device found, idVendor=0403, idProduct=6001
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.498217] usb 2-2: >New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.498225] usb 2-2: >Product: FT232R USB UART
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.498233] usb 2-2: >Manufacturer: FTDI
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.498239] usb 2-2: >SerialNumber: AHVU5ZM8
Jan 2 10:18:17 jacco-vaio mtp-probe: checking bus 2, device 8: “/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2”
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506269] ftdi_sio 2-2:1.0: >FTDI USB Serial Device converter detected
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506355] usb 2-2: >Detected FT232RL
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506362] usb 2-2: >Number of endpoints 2
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506369] usb 2-2: >Endpoint 1 MaxPacketSize 64
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506376] usb 2-2: >Endpoint 2 MaxPacketSize 64
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.506383] usb 2-2: >Setting MaxPacketSize 64
Jan 2 10:18:17 jacco-vaio mtp-probe: bus: 2, device: 8 was not an MTP device
Jan 2 10:18:17 jacco-vaio kernel: [ 4081.508696] usb 2-2: >FTDI USB Serial Device converter now attached to ttyUSB0

My VAG-COM:
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.712244] usb 2-2: >new full-speed USB device number 7 using uhci_hcd
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.913241] usb 2-2: >New USB device found, idVendor=0403, idProduct=fa20
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.913253] usb 2-2: >New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.913262] usb 2-2: >Product: Ross-Tech HEX-USB
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.913270] usb 2-2: >Manufacturer: Ross-Tech
Jan 2 10:17:33 jacco-vaio kernel: [ 4037.913276] usb 2-2: >SerialNumber: RT000001
Jan 2 10:17:33 jacco-vaio mtp-probe: checking bus 2, device 7: “/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2”
Jan 2 10:17:33 jacco-vaio mtp-probe: bus: 2, device: 7 was not an MTP device

Any clue on how to fix this?? I am running Linux Mint with kernel 3.5.0 32 bit

Are you sure the RossTech cable is an FTDI cable ?

Try to load the FTDI module with these parameters:

modprobe ftdi_sio vendor=0x0403 product=0xfa20

Tried that and got the following:

Jan 2 11:20:58 jacco-vaio kernel: [ 729.628136] usb 2-2: >new full-speed USB device number 3 using uhci_hcd
Jan 2 11:20:58 jacco-vaio kernel: [ 729.828219] usb 2-2: >New USB device found, idVendor=0403, idProduct=fa20
Jan 2 11:20:58 jacco-vaio kernel: [ 729.828230] usb 2-2: >New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 2 11:20:58 jacco-vaio kernel: [ 729.828239] usb 2-2: >Product: Ross-Tech HEX-USB
Jan 2 11:20:58 jacco-vaio kernel: [ 729.828246] usb 2-2: >Manufacturer: Ross-Tech
Jan 2 11:20:58 jacco-vaio kernel: [ 729.828252] usb 2-2: >SerialNumber: RT000001
Jan 2 11:20:58 jacco-vaio mtp-probe: checking bus 2, device 3: “/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2”
Jan 2 11:20:58 jacco-vaio mtp-probe: bus: 2, device: 3 was not an MTP device
Jan 2 11:21:13 jacco-vaio kernel: [ 744.791270] usbcore: registered new interface driver ftdi_sio
Jan 2 11:21:13 jacco-vaio kernel: [ 744.791973] USB Serial support registered for FTDI USB Serial Device
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793280] ftdi_sio 2-2:1.0: >FTDI USB Serial Device converter detected
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793361] usb 2-2: >Detected FT232BM
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793367] usb 2-2: >Number of endpoints 2
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793372] usb 2-2: >Endpoint 1 MaxPacketSize 64
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793377] usb 2-2: >Endpoint 2 MaxPacketSize 64
Jan 2 11:21:13 jacco-vaio kernel: [ 744.793382] usb 2-2: >Setting MaxPacketSize 64
Jan 2 11:21:13 jacco-vaio kernel: [ 744.796288] usb 2-2: >FTDI USB Serial Device converter now attached to ttyUSB4
Jan 2 11:21:13 jacco-vaio kernel: [ 744.796327] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
Jan 2 11:21:13 jacco-vaio modem-manager[813]: (ttyUSB4) opening serial port…
Jan 2 11:21:25 jacco-vaio modem-manager[813]: (ttyUSB4) closing serial port…
Jan 2 11:21:25 jacco-vaio modem-manager[813]: (ttyUSB4) serial port closed
Jan 2 11:21:25 jacco-vaio modem-manager[813]: (ttyUSB4) opening serial port…
Jan 2 11:21:31 jacco-vaio modem-manager[813]: (ttyUSB4) closing serial port…
Jan 2 11:21:31 jacco-vaio modem-manager[813]: (ttyUSB4) serial port closed
Jan 2 11:21:31 jacco-vaio modem-manager[813]: (ttyUSB4) opening serial port…
Jan 2 11:21:43 jacco-vaio modem-manager[813]: (ttyUSB4) closing serial port…
Jan 2 11:21:43 jacco-vaio modem-manager[813]: (ttyUSB4) serial port closed
Jan 2 11:21:43 jacco-vaio modem-manager[813]: (ttyUSB4) opening serial port…
Jan 2 11:21:49 jacco-vaio modem-manager[813]: (ttyUSB4) closing serial port…
Jan 2 11:21:49 jacco-vaio modem-manager[813]: (ttyUSB4) serial port closed

Now I created a symlink to com1 but VCDS still not seeing the linked cable…

You symlinked /dev/ttyUSB4 right ? Some stuff you should check out:
* Most Linux distros have a group you need to be a member of to access serial devices
* Check output of ‘setserial -a /dev/ttyUSB4’
* Maybe modem-manager or network-manager locks the device so it becomes unavailable in Wine.

turns out it is not a FTDI chip in there and many have tried, but none succeeded 😦

Источник

Vag com для linux

Электро-диагностика авто

А вы работаете в этой сфере?

полез

Помнится под нокии n800/810/900 было, с сорцами, для OBD-II

может и интересная софтина