Using The Ebay/VAG-COM Cable To Datalog

Got my new 2.0 from Tactrix... same shit different day

I hate to say it, but I told you so... there's some sort of anomaly with the electrical system in the car causing this...

 

What kind of battery do you have? Any corrosion on the battery terminals?

 

Check the grounding straps up front under the engine bay also.

Ok, I have tried a few things here. So far this is where I am at. I have 3 ferrite clips on the OBD harness. I cleaned the ground straps from the exhaust manifolds to the frame rails along with the large starter ground on top of the tranny bellhousing. I disconnected my phone charger and my boost gauge. I also turned my radio and A/C off. I am getting the same results. I also changed my parameters to 2 byte instead of the 4 that I had. I even tried SDcard logging on the Tactrix and its doing almost the same thing. One thing that does seem to be odd is that I can get a full log into the higher rpms if I kind of feather the throttle (see log 1). I only hit 100% throttle for a brief second. Right after that, I tried to slowly roll into WOT but it cut out just the same (see log 2). Log 3 is the first pull with the Tactrix 2.0 today.

 

I'm just running a standard battery from advance auto. The terminals are perfect and have never had a hint of corrosion on them in their lifetime.

Log 1.csv

Log 2.csv

Log 3.csv

Ugh, I'm clueless at this point... The worst part is I have no idea why my car doesn't have this problem anymore or else I'd be able to tell you exactly what I did...

 

I can tell you that I'm not longer using the same battery as when I had this problem. But I think I've changed batteries twice now so...

 

It also wasn't a consistent problem when I used to get it. Sometimes it would disconnect at WOT, sometimes I'd luck out and it'd continue to log. It was definitely sporadic....

Very odd. I see that the last guy in this thread with this problem fixed it by using the Tactrix 1.3. This might get a bit confusing but I will try to explain. I bought a used Accessport last year and it was the original v2 with the silver dongle w/metal clip on the port connector identical to the Tactrix 2.0 setup. I could not log with that AP for some reason. It would always say something like "dropped comms". So I sold it and picked up the newer v2 with the 1 piece cord, very similar to the Tactrix 1.3. If I remember correctly, that AP logged just fine all of the time. I may just need a Tactrix 1.3

This is the AP v2 I used to have and also the one that I used to sporadically lose communications at WOT on. Pictures in the thread:

http://legacygt.com/forums/attachment.php?attachmentid=75270&stc=1&thumb=1&d=1319104197

 

I definitely did use to have a problem with my vagcom cable, but it seems to have disappeared on its own. At one point in time, I had both the vagcom cable AND the AP in my possession and they were both exhibiting the problem sporadically.

Thats the one I couldn't log with.

 

 

This is the one I could.

 

http://i105.photobucket.com/albums/m219/born2race94/2012-10-23_10-58-52_843.jpg

Edited February 27, 2013 by Cone_Killer

Small update: On the way to work this moring, I tried to log with the vagcom again. This time though, I changed all of my 4 byte parameters to 2 byte. It is logging further into the high rpms for some reason. Take a look at the logs labeled accordingly.

Old vagcom log.csv

New vagcom log.csv

What version ECU is yours? 510N or 522N or whatever it is?

On another note, I have to ask. Why does your spool/boost suck so much? You're never even close to your target according to your boost error.

My ecu version is A2WC521C. I'm not sure about the boost. These are 2nd gear logs on my initial base map from Cryo.

Oh okay, that's why. You're in 2nd gear and on a base map... makes sense. Thought it was a 3rd gear pull on a final map.

 

I thought maybe it was an old ROM issue but I guess probably not since you're not on 510N.

I am completely clueless now and I have no idea what I'm going to do about finishing my tune that I just paid for... I may swing by an auto store on my way home and have them load test the battery.

Load tested the battery today, 597 out of 600 cca and 12.97v.... yet another dead end.

Just going to chime in on this last series of posts... Just checking to make sure that you guys have adjusted the communications (BAUD) rate in the driver's properties, it should be backed down to 4800. Also if you go into the "advanced" section of the driver properties, you can adjust the sliders that control the data transfer rate too. I always back both sliders down by one notch. That and if you are using a newer version of the RR software, check to see how you have the "enable fast polling mode" option set. Try it with and without this option selected and see if it makes any difference.

 

In other news. I've got the newest versions of ECUFlash and all the Romraider programs/functions working on my new laptop that is running WINDOWS 8. I just plugged in the my usb to serial cable and then chose which driver to use and then I selected the "ftdibus.inf" file from the "cdm v2.08.28 certified" driver from the ftdi webpage. Or, if you already have a driver installed, be sure to choose the device as a "usb to serial adapter" and not the "prolific device". Works great so far. I've used it to pull my rom of my OutbackXT and to do a little logging.

Got my Amazon VAG COM cable in the mail today, was eager to try it out and check up on my fuel trims. Been banging my head against the wall for hours, at this point that may be due in part to sleep deprivation. I can get the cable to show up in the device manager and have installed latest FTDI driver, I can't get the cable to connect in Learning View or RomRaider. All the definitions are updated in RR. I've backed the baud rate down to 4800.

 

I've also tried the Openport 1.3 and 2.0 drivers that come with EcuFlash, no luck.

 

At this point I'm thinking that it may be my laptop...

Same here on Windows 8. Get the code 10 failure notice and can't get it to connect.

 

Got my Amazon VAG COM cable in the mail today, was eager to try it out and check up on my fuel trims. Been banging my head against the wall for hours, at this point that may be due in part to sleep deprivation. I can get the cable to show up in the device manager and have installed latest FTDI driver, I can't get the cable to connect in Learning View or RomRaider. All the definitions are updated in RR. I've backed the baud rate down to 4800.

 

I've also tried the Openport 1.3 and 2.0 drivers that come with EcuFlash, no luck.

 

At this point I'm thinking that it may be my laptop...

I got mine to log with RR and it works with learning view. What i cant seem to make work is reading/flashing with ecuflash.

I have ecuflash version 1.44 installed and ftdi driver 2.08.30 but at the start of this thread it says to use 2.04.06 and i cant seem to find it. My cable obviously works if can log and work with learning view but why cant i read my ecu?

 

Sent from my LG-E970 using Tapatalk 2

I saw the front post large letter warning, but I thought that Datalogging was possible with a VAG-COM cable on a CANBUS car, but flashing was impossible? Am I mistaken here?

I can get RR working.. that's it.. LV wont work and ecuflash wont either. not sure if I have the wrong drivers. main page most of the links are out dated. I have ecuflash 1.29 as it stated but cant manually update to the drivers as seen here.. http://legacygt.com/forums/showpost.php?p=3792501&postcount=138 when I search for the drivers only the openport folders open and I get the "No Vehicle Interface,"

 

this is what LV gives me:

[03:39:40.6783320] Learning View version 0.6a

[03:39:44.8591393] PassThruOpen returned 8 and DeviceID 0

[03:39:44.8747394] PassThruGetLastError returned 8, Message: no devices available

[03:39:44.9215394] COM5 open

[03:39:45.0151396] ECU Init

[03:39:45.0307396] WRITE 6 bytes: 80 10 F0 01 BF 40

[03:39:45.1711399] READ 38 bytes: 80 10 F0 01 BF 40 80 F0 10 39 FF A2 10 11 2F 12 50 52 06 73 FA CB A6 2B 81 FE A8 00 00 00 60 CE 54 F9 B1 E4 00 0C

[03:39:49.0399467] ECU supported (ECUID:xxxxxxx CALID:xxxxxxx DESC:05 USDM Legacy GT AT)

[03:39:49.1179468] FLKC load

[03:39:49.1491469] WRITE 11 bytes: 80 10 F0 06 A0 00 0C 96 B4 0F 8B

[03:39:49.2271470] READ 33 bytes: 80 10 F0 06 A0 00 0C 96 B4 0F 8B 80 F0 10 11 E0 3F 59 99 99 3F 8C CC CC 3F AC CC CC 3F CC CC CC C4

[03:39:49.2739471] FLKC RPM

[03:39:49.2895471] WRITE 11 bytes: 80 10 F0 06 A0 00 0C 96 C4 17 A3

[03:39:49.3831473] READ 41 bytes: 80 10 F0 06 A0 00 0C 96 C4 17 A3 80 F0 10 19 E0 44 CE 40 00 45 22 80 00 45 48 00 00 45 7A 00 00 45 96 00 00 45 B5 40 00 13

[03:39:49.3987473] IAM

[03:39:49.3987473] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 26 7C 03 CA

[03:39:49.4611474] READ 21 bytes: 80 10 F0 06 A0 00 FF 26 7C 03 CA 80 F0 10 05 E0 3F 60 00 00 04

[03:39:49.5079475] A/F Learning airflow

[03:39:49.5079475] WRITE 11 bytes: 80 10 F0 06 A0 00 0C 6F 4C 0B F8

[03:39:49.5859476] READ 29 bytes: 80 10 F0 06 A0 00 0C 6F 4C 0B F8 80 F0 10 0D E0 40 B3 33 33 41 20 00 00 42 20 00 00 89

[03:39:49.6015477] A/F Learning #1

[03:39:49.6015477] WRITE 11 bytes: 80 10 F0 06 A0 00 FF 26 18 1F 82

[03:39:49.6951478] READ ERROR: The operation has timed out.

[03:39:49.7575479] Unhandled Exception: The operation has timed out.

[03:39:52.1443521] COM5 closed

Try the newer version of LV I linked you in the other thread.

 

Do you have a vagcom or a tactrix cable? Tactrix cable should work with everything. Vagcom is very hit or miss. Seems that the internals of some vagcom cables are different. I have 2 vagcom cables - one works with EVERYTHING flawlessly. I swap cables (no change in my software) and it doesn't work. Others have had the same problems.

Following this looks like the cable may be different.. and this don't say what one of the drivers to use.. or are the drivers I have to new?

2.08.30 WHQL Certified Walk threw stated use FTDI 2.04.06 Anybody have the FTDI 2.04.06 drivers?

 

Cant get cpuflash to work says No Vehicle Interface not what its supposed to I mat need the FT232R USB UART A400fMIA. drivers>? or is it a cable issue>?

 

Here is what I found there are 2 cables..

 

 

I have the CH340 chip instead of the far superior FTDI one everyone's software is written for. It will not be detected by most software. Or maybe I just need the FTDI drivers...

Edited October 3, 2013 by Evnldr

When in 2nd or 3rd gear I have difficulty loggin anything above 4500RPM. Romraider just cuts out. I even removed all but 4 parameters logged and same behavior. Some folks say It's interference. Some say ECU is busy. I have no idea whats happening here as it never really used to happen!

JMLegacy, check here regarding your logging issue. Try splicing in a capacitor.

http://legacygt.com/forums/showthread.php/cannot-log-wot-pulls-202559.html?p=4561779

Everyone else considering buying a VAGCOM cable, please note this thread:

legacygt.com/forums/showthread.php/vag-com-cables-chipsets-ft232rl-ch340-214994p2.html

 

Only certain VAGCOM cables work. FT232BL seems to be a winner. The others either don't work at all, or only work partially.