matt Posted September 6, 2011 Share Posted September 6, 2011 So I just read through this whole thread. I may try ECUFlash 1.42 because I thought VAG-COM wasn't supported after 1.29, but I guess that's not the case? EcuFlash 1.42 with its included drivers worked great for me with two different eBay VAG-COM cables. First I'll try the drivers that came on the CD with the cable. STOP! DO NOT DO THAT! Driver disks included with unbranded knockoff hardware are notorious for containing viruses. That's been the case since before we were all on the internet. The hardware, i.e. VAG-COM cable in this case, is typically fine, but you should throw the driver disk straight in the trash. Link to comment Share on other sites More sharing options...
Ridgeracer Posted September 7, 2011 Share Posted September 7, 2011 My Tactrix cable decided to die last month. Seems like I'll give this a try seeing how you all are doing well with it. "Gimme mines Balboa...Gimme mines".....Clubber Lang - Mr. T Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 7, 2011 Share Posted September 7, 2011 EcuFlash 1.42 with its included drivers worked great for me with two different eBay VAG-COM cables. STOP! DO NOT DO THAT! Driver disks included with unbranded knockoff hardware are notorious for containing viruses. That's been the case since before we were all on the internet. The hardware, i.e. VAG-COM cable in this case, is typically fine, but you should throw the driver disk straight in the trash. Thanks for the heads up, saved me some headache! But I still have some serious issues with ECUFlash. I installed 1.42.2595 and I can't get it to work. Running Win7 Pro; I've deleted the port, reinstalled, tried running as Admin, tried running in XP mode, rebooted etc etc as directed in the other pages, still nothing. Screen shot of the action below: Does ECUFlash require the green connectors to be hooked up to connect at all? I can get LV and RR logger to connect and even reset the ECU without the green connectors, in the same session that ECUFlash won't work. I'm about to pull my hair out here, this is driving me nuts. Any help is greatly apprecaited. Link to comment Share on other sites More sharing options...
bmx045 Posted September 7, 2011 Share Posted September 7, 2011 ecuflash requires green connectors Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 7, 2011 Share Posted September 7, 2011 ecuflash requires green connectors Sooooo OK... Guess that's my next step... (need facepalm smiley) I was under the impression that just to read the ECU, even with ECUFlash, the green connectors were not needed. Apparently I was sorely mistaken. Now I just gotta wait for my Infamous tune and I can finally start to open this pig up. 90 miles left on clutch break-in. Link to comment Share on other sites More sharing options...
bmx045 Posted September 7, 2011 Share Posted September 7, 2011 (edited) ECU flash needs to access the rom to read it (download). Thankfully for 07+, there are no connectors so this all happens without getting off the seat BTW that's the nicest stock map LV I've ever seen. No timing being pulled, almost unheard of. though your fuel trims are off at idle Edited September 7, 2011 by bmx045 Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 7, 2011 Share Posted September 7, 2011 It's unheard of because I just reset it. Had to clear the bothersome P0420. Prior do doing so though, the only pull was in the far left column, row 2600-3200 at -1.05 This is what it looked like today before I reset the ECU: Any better? Link to comment Share on other sites More sharing options...
bmx045 Posted September 7, 2011 Share Posted September 7, 2011 either way, you're at an IAM of 1 so still, just reset or not, clean. Though the ranges are wacked, you must be taking it reaaaal easy. Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 7, 2011 Share Posted September 7, 2011 Yeah, pussyfooting around town to break in the new clutch. No higher than 3200RPM, no more than maybe 35-40% throttle (estimated) for fear of BOOM while driving untuned. It's my DD, so I need it to work Link to comment Share on other sites More sharing options...
bmx045 Posted September 7, 2011 Share Posted September 7, 2011 well you're not knocking this far, and those trims take a little while to settle in so give it some time.... Link to comment Share on other sites More sharing options...
Ridgeracer Posted September 11, 2011 Share Posted September 11, 2011 (edited) Well with this cable and both the FTDI or latest Tactrix drivers I was able to use LV and RR logger. However I can't get ECUflash to communicate. Anyone with a link for Tactrix v1.29 drivers? Found the link in the sticky below this. Sorry...Works great now.. Edited September 12, 2011 by Ridgeracer "Gimme mines Balboa...Gimme mines".....Clubber Lang - Mr. T Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 13, 2011 Share Posted September 13, 2011 Finally got a snapshot of my ROM from Ecuflash. Had to use 1.29a with the recommended drivers and everything worked first time. 1.42 did not work, no matter what I tried. Link to comment Share on other sites More sharing options...
matt Posted September 13, 2011 Share Posted September 13, 2011 Interesting, sounds like some VAG-COM cables really do need 1.29a. Or maybe it's a Windows 7 thing. XP is the newest version of Windows I've used. I think most of the problems people have with EcuFlash 1.42 are from trying to use the FTDI-branded drivers with it, which doesn't work. But clearly there's more to it than that. Link to comment Share on other sites More sharing options...
BigTDogg MA Posted September 13, 2011 Share Posted September 13, 2011 Interesting, sounds like some VAG-COM cables really do need 1.29a. Or maybe it's a Windows 7 thing. XP is the newest version of Windows I've used. I think most of the problems people have with EcuFlash 1.42 are from trying to use the FTDI-branded drivers with it, which doesn't work. But clearly there's more to it than that. Yeah, this was on a Win7 laptop. My only XP laptop is a 9" netbook. I installed 1.42, canceled the driver section, deleted the com cable, rebooted, directed it to the 2.08.14 drivers, and tried to connect; nothing. Learning View worked fine. I uninstalled 1.42 and installed 1.29a with the same driver package, no problem. I'll rehost ECUFlash 1.29a so people can find it. Took me a while to find a good link. This link should work, if not let me know and I'll edit it Link to comment Share on other sites More sharing options...
limequat Posted March 6, 2012 Share Posted March 6, 2012 Just wanted to post in this thread to add my experience, since this thread helped me so much. There's a lot of different combinations of software/hardware/vehicles, so every data point helps. Here is what works for me: Car: 2005 SAABARU 9-2x Laptop: Dell Latitude, Windows 7 Pro Drivers: Latest FTDI downloaded from website, set to 4800 Baud rate Cable: Ebay with power jumped from 11 to 16 ECUFlash: Current Romraider: Current Logging: I can't log as many parameters as I could with a Tatrix cable, but other than that logging seems fine (20 vs 24 or so) Flashing: My ebay cable is jumpered interally, so I don't have to worry about jumping power. However, I do get a voltage out of range error 99% of the time. I turn on my headlights and it works. Link to comment Share on other sites More sharing options...
ktmrider Posted March 31, 2012 Share Posted March 31, 2012 Interesting, sounds like some VAG-COM cables really do need 1.29a. Or maybe it's a Windows 7 thing. XP is the newest version of Windows I've used. I think most of the problems people have with EcuFlash 1.42 are from trying to use the FTDI-branded drivers with it, which doesn't work. But clearly there's more to it than that. Yeah, this was on a Win7 laptop. My only XP laptop is a 9" netbook. I installed 1.42, canceled the driver section, deleted the com cable, rebooted, directed it to the 2.08.14 drivers, and tried to connect; nothing. Learning View worked fine. I uninstalled 1.42 and installed 1.29a with the same driver package, no problem. I'll rehost ECUFlash 1.29a so people can find it. Took me a while to find a good link. This link should work, if not let me know and I'll edit itUpdate based on my recent experience. Was using OSE 1.29 on a VAG cable bought 2 years ago, no problems. Due to some non-relevant issues I had to buy another VAG cable a few weeks ago. New cable wouldn't connect with OSE but could log with Enginuity?!? LED is on, all seems Ok, OSE just won't connect. FYI my laptop is XP and worked fine with the older ebay cable. Also another note I bought two cables, one for a co-worker, same problem with other one. Decided to download OSE 1.42 today and try again. All works fine now. Guess the cables can be sensitive to OSE version.... Link to comment Share on other sites More sharing options...
SCASEYS Posted April 6, 2012 Share Posted April 6, 2012 [13:10:45.094] EcuFlash Version 1.42.2595 [13:10:45.094] OS Version Windows Vista [13:10:45.094] Qt Version 4.5.0 [13:10:45.109] 56 memory models read. [13:10:45.109] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata [13:10:45.671] 343 ROM metadata models scanned. [13:10:45.671] checksum module "subarudbw" loaded. [13:10:45.671] checksum module "mitsucan" loaded. [13:10:45.671] flashing tool "wrx02" loaded. [13:10:45.671] flashing tool "wrx04" loaded. [13:10:45.671] flashing tool "sti04" loaded. [13:10:45.671] flashing tool "sti05" loaded. [13:10:45.671] flashing tool "mitsukernel" loaded. [13:10:45.671] flashing tool "mitsukernelocp" loaded. [13:10:45.671] flashing tool "mitsubootloader" loaded. [13:10:45.686] flashing tool "shbootmode" loaded. [13:10:45.733] flashing tool "shaudmode" loaded. [13:10:45.733] flashing tool "subarucan" loaded. [13:10:45.733] flashing tool "mitsucan" loaded. [13:11:55.566] Using interface USB <-> Serial [13:12:08.635] kernel get version [13:12:09.009] SSM2 init [13:12:09.430] SSM2 init [13:12:09.462] readback mismatch [13:12:09.462] SSM2 init [13:12:09.477] readback mismatch [13:12:09.477] SSM2 init [13:12:09.493] readback mismatch [13:12:09.493] SSM2 init [13:12:09.508] readback mismatch [13:12:09.508] SSM2 init [13:12:09.945] SSM2 init [13:12:10.366] SSM2 init [13:12:10.413] readback mismatch [13:12:10.413] SSM2 init [13:12:10.429] readback mismatch [13:12:10.429] SSM2 init [13:12:10.975] interface close [13:12:10.975] interface close [13:12:50.010] Using interface USB <-> Serial [13:12:54.231] kernel get version [13:12:54.605] SSM2 init [13:12:55.026] SSM2 init [13:12:55.463] SSM2 init [13:12:55.510] readback mismatch [13:12:55.510] SSM2 init [13:12:55.526] readback mismatch [13:12:55.526] SSM2 init [13:12:55.962] SSM2 init [13:12:56.384] SSM2 init [13:12:56.430] SSM2 init [13:12:56.446] readback mismatch [13:12:56.446] SSM2 init [13:12:56.883] SSM2 init [13:12:56.914] readback mismatch [13:12:57.023] interface close [13:12:57.023] interface close [13:13:09.021] Using interface USB <-> Serial [13:13:22.431] kernel get version [13:13:22.805] SSM2 init [13:13:23.226] SSM2 init [13:13:23.258] readback mismatch [13:13:23.258] SSM2 init [13:13:23.289] readback mismatch [13:13:23.289] SSM2 init [13:13:23.710] SSM2 init [13:13:23.741] readback mismatch [13:13:23.741] SSM2 init [13:13:23.757] readback mismatch [13:13:23.757] SSM2 init [13:13:24.194] SSM2 init [13:13:24.615] SSM2 init [13:13:24.662] SSM2 init [13:13:24.677] readback mismatch [13:13:24.786] interface close [13:13:24.786] interface close I donated to LegacyGT.com which allows me to have this nifty signature. If anything SCASEYS posts ever becomes a sticky i'm gonna light this whole place on fire Link to comment Share on other sites More sharing options...
Legaroo Posted July 7, 2012 Share Posted July 7, 2012 So... I may have missed it but is there a solution for fifth gen? Link to comment Share on other sites More sharing options...
qikslvr Posted December 3, 2012 Author Share Posted December 3, 2012 Hey guys just thought I'd let you know that I'm back and will be working on an 05 OBXT project this time, so I should be around more often now and I will try my best to keep this tread up to date and help out wherever I can. Let's kick this pig! Link to comment Share on other sites More sharing options...
lieutenantcolumbo Posted December 3, 2012 Share Posted December 3, 2012 Welcome back! Link to comment Share on other sites More sharing options...
mikeklacy Posted December 11, 2012 Share Posted December 11, 2012 Recently started working for this company: http://www.tableausoftware.com/ and saw one of our users make a cool visualization for OBD2 codes: http://ryrobes.com/tableau/cars-computers-and-software-quick-tableau-of-data-from-my-vws-on-board-diagnostic-obdii-port/ Anyone interested in having me make one specific for an LGT? Last time I collected some logs for my car something like this would have been helpful. If I make a template all you have to do is connect it to your logged data and everything will work, no need to do excel manipulations. Best part is the software and hosting is free so you can post your logs to our servers so others can help you diagnose. Link to comment Share on other sites More sharing options...
qikslvr Posted April 16, 2013 Author Share Posted April 16, 2013 Just an FYI. I have been able to get all software and drivers to work in WINDOWS 8. Let's kick this pig! Link to comment Share on other sites More sharing options...
chimera Posted May 18, 2013 Share Posted May 18, 2013 is there anyway, other than using ecuflash, to read ecu rom thats compatible with tweaking in romraider? tried ecuexplorer but doesnt have my jdm lgt defs. vag-com clearly sux if you have 2007+ (canbus) lgt (altho my lgt is '07, reading via learning view says its an '08 model?). well i guess vagcom doesn't suck, moreso tactrix and their post v1.29 lockdown shit does. unless there is some other way of getting ecuflash to read via vag-com cable on canbus? i see some get this working on jdm fine, and some don't. i'm in 2 minds, i understand that money has to be made in any business venture, but $170 for a cable? and then an e-tune on top? i guess coming from an i.t. background myself i know ridiculously overpriced everything i.t./electronic is lol. Link to comment Share on other sites More sharing options...
scoobyworld Posted May 23, 2013 Share Posted May 23, 2013 Has anyone seen this issue before? ECU Flash only Recognises my cable when the driver has been set to USB Serial Converter and not as a COM port (also tried changing the baud rate), however ECU Flash is unable to publish the cables ID or connect to the ECU. I've tried several different drives, all appear to behave the same. Restarts and fresh installs do not fix the issue. Photo's attached. Thanks in advance. OS: Windows 7 enterprise x64 (Driver signature enforcement has been disabled) Cable: KKL VAG-COM for 409.1 ECU Flash: ecuflash_setup129a http://www.ebay.co.uk/itm/VAG-OBD2-OBDII-409-1-KKL-USB-Car-Diagnostic-Cable-Lead-Interface-Tool-for-Audi/261205621565?ssPageName=WDVW&rd=1&ih=016&category=30921&cmd=ViewItem http://s10.postimg.org/n96h9txbd/ECUFlash.png http://s10.postimg.org/cq6hknund/Com_Port.png http://s10.postimg.org/effksqacp/Driver_Model.png http://s10.postimg.org/qikwgalex/Drivers.png Link to comment Share on other sites More sharing options...
chimera Posted May 25, 2013 Share Posted May 25, 2013 (edited) There are 2 different drivers. One device is under "Universal Serial Bus controllers" and should use "USB Serial Converter" the other is under "Ports (COM & LPT)" and should be the actual VAG-COM driver for the COM port. The latter won't work unless the USB Serial Converter is installed and working first. I'm actually on my notebook right now trying to get the cable to work - although its supposedly able to read CANbus. Issue i got is it shows the COM port driver as Tactrix and loads ok, but when I run ECUFlash and try and read I get this (immediately closes after attempting to open)... [15:11:45.937] EcuFlash Version 1.42.2595 [15:11:45.937] OS Version Windows Vista [15:11:45.937] Qt Version 4.5.0 [15:11:45.968] 56 memory models read. [15:11:45.968] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata [15:11:46.907] 343 ROM metadata models scanned. [15:11:46.907] checksum module "subarudbw" loaded. [15:11:46.907] checksum module "mitsucan" loaded. [15:11:46.907] flashing tool "wrx02" loaded. [15:11:46.907] flashing tool "wrx04" loaded. [15:11:46.907] flashing tool "sti04" loaded. [15:11:46.907] flashing tool "sti05" loaded. [15:11:46.907] flashing tool "mitsukernel" loaded. [15:11:46.907] flashing tool "mitsukernelocp" loaded. [15:11:46.907] flashing tool "mitsubootloader" loaded. [15:11:46.923] flashing tool "shbootmode" loaded. [15:11:46.923] flashing tool "shaudmode" loaded. [15:11:46.923] flashing tool "subarucan" loaded. [15:11:46.923] flashing tool "mitsucan" loaded. [15:12:02.391] Using interface FT232R USB UART A601O9GQ [15:12:02.391] interface close [15:12:02.453] unable to connect to vehicle interface. [15:12:02.453] interface close Edited May 25, 2013 by chimera Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now