Hi Lee, Thanks for your helpful comments. The vendor had e-mailed me directing me to the FTDI website to download the drivers - you were correct! I had opened the dongle and the chip is an FTDI 232BL. I run XP, so downloaded the driver 2.00.00 However, I still can't get it to run: Having plugged in the cable, On the VAG-COM options menu, selecting USB and 'Test' returnsPort status: OKInterface: Not Found!If I unplug the cable from the USB port, then the report says 'Ross-Tech Interface Not Found!' So, this seems to suggest something is working OK. Also, in the 'Add or Remove Programs' facility, the 'FTDI USB Serial Converter Drivers' is listed, so this looks encouraging.I've discovered that if I select COM3 and then press Test, the window says:Port Status: OKInterface: Found!Type: Serial Pass-ThroughOpto/ISo: NoRoss-Design: NoHowever, the above happens even if the cable is unplugged.With the dongle plugged in (the led lights up) and turning on the ignition to the first setting, clicking on the OBD-II returns 'Interface Not Found!' As I mentioned, the CD-ROM was cracked when delivered - although no sign of any damage to the Jiffybag or to the cable and dongle.Would be very grateful for any suggestions.

1. Autodia K409 Usb Treiber Windows Download

Autodia K409 Usb Treiber Windows Download

Hi Lee, Thanks for your helpful comments. The vendor had e-mailed me directing me to the FTDI website to download the drivers - you were correct! I had opened the dongle and the chip is an FTDI 232BL. I run XP, so downloaded the driver 2.00.00 However, I still can't get it to run: Having plugged in the cable, On the VAG-COM options menu, selecting USB and 'Test' returnsPort status: OKInterface: Not Found!If I unplug the cable from the USB port, then the report says 'Ross-Tech Interface Not Found!' So, this seems to suggest something is working OK. Also, in the 'Add or Remove Programs' facility, the 'FTDI USB Serial Converter Drivers' is listed, so this looks encouraging.I've discovered that if I select COM3 and then press Test, the window says:Port Status: OKInterface: Found!Type: Serial Pass-ThroughOpto/ISo: NoRoss-Design: NoHowever, the above happens even if the cable is unplugged.With the dongle plugged in (the led lights up) and turning on the ignition to the first setting, clicking on the OBD-II returns 'Interface Not Found!' As I mentioned, the CD-ROM was cracked when delivered - although no sign of any damage to the Jiffybag or to the cable and dongle.Would be very grateful for any suggestions.

Cheers, IanIan,mine did exactly the same. What you need to do is plug in the cable to your laptop. Now go into control panel open up or navigate to system/hardware/device manager/ports.It will probably say USB serial port (COM3 or somesuch) open up it by double clicking, go to the port settings tab and click on advanced.

This will allow you to set the com port to Com1 The cable should now connect to the car.If the cable is unplugged from the car and you try to find it with VAG-COM it 'finds' it at COM3 but it wont work. Try the above then connect to the car and test it at COM1 and it should work. It's a lot of buggering about but it should go. Try to ensure you use the same usb socket each time.Once you know it works it is time to buy the registered version, it's well worth the expense. I have to say their cable is a lot less aggro. I have been looking at the screenshots of the next version of VAG-COM which Uwe has posted.

I may have to shell out for one because it looks really pukka. Though I may get it shipped to friends in the US as I resent paying that Scottish oaf at the treasury all my hard earned cash!Let me know how you get on. Hi Lee,Again, thank you for your kind help. I've now persuaded the beast to work and it was exactly as you said.

I decided to call FTDI this afternoon and the guy there was massively helpful if walking me through the changes. He also advised another couple: In the 'Advanced settings for COM 1 (or other port that is selected), under:USB Transfer Sizes, change 'Receive (Bytes)' to 64BM Options, change 'Latency Timer (msec)' to 3As you say, I now need to register the software for $99 - I assume this will active more functions? Will this then operate as the KEY-USB product from Ross-Tech selling for $249, or does the KEY-USB from Ross-Tech perform other functions in addition?Thanks again for your time and patience - this site is a great concept!kind regardsIanVW Passat 2002 TDI 130 estate.

Thanks for the code and the info!I’m trying to use the project to use the “read blocks” part but with a ELM327 bluetooth adapter and a STM32 board running arduino code (STM32duino).I’m able to read the engine module with other library (OBD) but this one was failing. I found that, as I wasn’t using the RX/TX lines directly, I wasn’t able to do the “slow init”.As a workaround I tried to use the AT command “AT IIA xx” to do this but the BT adapter is a clone 🙂 and it doesn’t support this command.I’m going to gut the adapter and access the lines directly (on level converter) as you are doingThanks again!

Hello,thank you all for sharing your code and the development on this nice project.I have transformed an 2L engine of a Golf 3 (AGG) to a VW bus (T3) and get a lot of sensor data on a little display with this code. The ECU system is the Simos 4.Everything works fine with the code, so far. In the bus I use a OLED Display with GPS and other sensors to show the speed, the gear and the temperatures.Now I want to integrate some ECU Data (lambda and fuel consumption) and a check engine light for the case of an error. That for it is necessary to read out the errorlist and integrate this part to Alexanders arduino code. It is just an extension to read the errors.Does somebody has done it right now and want to share the code with me? Hi James,I was wondering, when using the SoftwareSerial.h library do you manage to successfully communicate with the ECU after the 5 baud init? By this I mean do you successfully receive the values 0x55 0x01 0x8A?Because I have tried the SoftwareSerial.h library and I cannot get a correct response from the ECU, instead I get 0x00 0x00 0x00 for the ADRDashboard and 0x00 0x00 0x55 for the ADREngineI believe the problem might be because the new SoftwareSerial.h library calculates the timings for the 10400 baud as opposed to the hardcoded timings in the NewSoftwareSerial.h library.

And I think the calculated timings and the hard coded timings are different. Hi James,I was wondering, when using the SoftwareSerial.h library do you manage to successfully communicate with the ECU after the 5 baud init? By this I mean do you successfully receive the values 0x55 0x01 0x8A?Because I have tried the SoftwareSerial.h library and I cannot get a correct response from the ECU, instead I get 0x00 0x00 0x00 for the ADRDashboard and 0x00 0x00 0x55 for the ADREngineI believe the problem might be because the new SoftwareSerial.h library calculates the timings for the 10400 baud as opposed to the hardcoded timings in the NewSoftwareSerial.h library. And I think the calculated timings and the hard coded timings are different. Hi Alexander,Brilliant piece of software, thank you!I’ve got a 1997 Audi A4 B5 as well (V6 ABC engine). I’m trying to do a throttle body alignment so I can get the car running nicely again, and I’ve found it almost impossible!I’ve got the blue 409.1 cable, as well as a couple of others including the ross-tech one, and can’t get anything to work properly.

Using your program is the closest I’ve come to getting it working.Below is my debug output. I think the group is correct, based on this:If you are able to help at all, I’ll gladly make a donation via paypal for your time. Hi Alexander,Just found your website. Great work!I wrote my 1st kw1281 piece of code for a Psion 3mx over a decade ago and used a “wired rs232 interface” to my Audi. I then rewrote the code to run on a Palm device using the same interface. The last rewrite was in 2014 which used a homemade Bluetooth OBD connector running kw1281 on an Arduino and the UI functions running on an Android device.I am able to connect to ALL my ECUs on my 97 A4 B5 Audi, including the Airbag.

Not being able to connect to an ECU is not a security reason, it is most likely the baud rate has not been set correctly after the 5-baud init to the ECU, or a timing issue.My Audi ECUs:01 9600 baud02 9600 baud03 10400 baud08 4800 baud15 10400 baud17 9600 baud35 10400 baud.