You guys know you can flash with a VAG COM cable...right? - Page 2 - EvolutionM - Mitsubishi Lancer and Lancer Evolution Community



You guys know you can flash with a VAG COM cable...right?

Reply
 
 
 
Thread Tools Search this Thread
Old May 8, 2014, 07:50 AM   #16
Evolving Member
Thread Starter
 
Broke4speed's Avatar
 
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 1989 Dodge Colt GT Turbo w/2003 Sonata A/T ECU flashed with 9653 V7

Ok, you didn't say that it was a Mirage in your PM.

Unless you are using a 2001+ lancer or 3G eclipse ECU, it won't work. Also, I've said above that I can't confirm it works with ECUFlash 1.29, but that it DOES work with EVOScan's flashing utility.
Offline
 
Reply With Quote
Old May 9, 2014, 05:26 AM   #17
Evolving Member
Thread Starter
 
Broke4speed's Avatar
 
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 1989 Dodge Colt GT Turbo w/2003 Sonata A/T ECU flashed with 9653 V7

Ok. I'm getting too many PMs from people who have apparently never learned to read. Unless it's a question about getting the PROPER software and hardware to work, I'm going to delete any PM that I get. EVERYTHING you need to know is in the first post, in regards to what hardware and what software will work. DO NOT PM ME ASKING ME WHY ECUFLASH 1.44 WON'T CONNECT WITH THE VAG COM CABLE.

I have also said that I can't confirm whether or not 1.29a will work either. If some people have made it work, ask them, because I can only comment on what I've worked with: FTDI VAG COM CABLES and EVOSCAN'S FLASHING UTILITY.

Sorry, but this is getting out of hand, I may just delete all the info. It's more trouble than it's worth.
Offline
 
Reply With Quote
Old May 10, 2014, 10:11 PM   #18
Newbie
 
Join Date: May 2010
Location: Canberra, Australia
Posts: 38
Thanked 1 Time in 1 Post

Drives: 2002 Mitsubishi Magna AWD

I recently bought one of these cables to test purely for logging (I have an OP 1.3U for flashing), but I can't even get it to log with Evoscan - it just tries to connect repeatedly.

The USBVIEW utility reports the correct vendor and product IDs for a FTDI serial device, and the drivers included with Evoscan do get loaded.

Even though I disassembled the unit and checked the chip markings (the main chip is marked with the FTDI logo and the FT232RL identifier), having come across recent reports of suspect FTDI chips I wouldn't be too surprised to find its a fake chip with the attendant compatibility issues
Offline
 
Reply With Quote
Old May 12, 2014, 09:11 AM   #19
Evolving Member
Thread Starter
 
Broke4speed's Avatar
 
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 1989 Dodge Colt GT Turbo w/2003 Sonata A/T ECU flashed with 9653 V7

Try altering the latency settings for the COM port that the cable 'becomes'. I find that the stock 16ms setting is sometimes wayyyyyy too high for some cables.
Offline
 
Reply With Quote
Old May 13, 2014, 06:42 AM   #20
Newbie
 
Join Date: May 2010
Location: Canberra, Australia
Posts: 38
Thanked 1 Time in 1 Post

Drives: 2002 Mitsubishi Magna AWD

Quote:
Originally Posted by Broke4speed View Post
Try altering the latency settings for the COM port that the cable 'becomes'. I find that the stock 16ms setting is sometimes wayyyyyy too high for some cables.
Thanks for the suggestion - unfortunately it hasn't seemed to help. I dropped the value first to 8ms then to 4ms with no change in behaviour .

It appears not to be getting the echoed INIT response, and is stuck in the init loop until stopped.

I did wonder about the difference between the FT232B and FT232R versions of the KKL cable, at least in terms of how Evoscan might be attempting to use them, based on the circuit differences between the early OpenPorts (1.2 & earlier) which used the FT232B chip and the later OpenPort 1.3 variants which use the FT232R chip.

Do you know specifically which FTDI chip is in your cable, or failing that, by what name the system identifies it? (eg "USB Serial" or "FTDI USB UART")
Offline
 
Reply With Quote
Old May 13, 2014, 08:59 AM   #21
Evolving Member
Thread Starter
 
Broke4speed's Avatar
 
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 1989 Dodge Colt GT Turbo w/2003 Sonata A/T ECU flashed with 9653 V7

I'm not exactly sure, and my cable doesn't read right anymore due to some experimenting with FTProg, lol. It also only connects for logging and not for flashing...see previous comment about experimenting . I completely forgot to save the stock settings, sigh. I do recall that it showed up as FTDI USB UART though. I believe the only differences between the B and R chipsets is that the R is reflashable, although I can't be sure off the top of my head.

I am expecting another cable at some point, hopefully in the next week or two.
Offline
 
Reply With Quote
Old May 14, 2014, 06:41 AM   #22
Newbie
 
Join Date: May 2010
Location: Canberra, Australia
Posts: 38
Thanked 1 Time in 1 Post

Drives: 2002 Mitsubishi Magna AWD

Quote:
Originally Posted by Broke4speed View Post
I'm not exactly sure, and my cable doesn't read right anymore due to some experimenting with FTProg, lol. It also only connects for logging and not for flashing...see previous comment about experimenting . I completely forgot to save the stock settings, sigh. I do recall that it showed up as FTDI USB UART though. I believe the only differences between the B and R chipsets is that the R is reflashable, although I can't be sure off the top of my head.
Oops on the settings... I did remember to save the info when I also had a fiddle with FT_Prog - if you like, PM me and I can arrange some screenshots of what my cable looks like (restored to original state) in FT_Prog.

FTDI USB UART indicates an R series chip, which are much more common in these cables - probably due to not requiring a separate crystal and associated components in addition to an EEPROM, thus reducing manufacturing cost.

Compared to the B chips, as well as an internal EEPROM for the identity stuff the R chips have 5 additional pins with programmable functions - several of which are used in the OpenPort 1.3 cables for controlling some behaviour (though I'm not sure to what extent this affects Mitsu usage).
Offline
 
Reply With Quote
Old Jun 12, 2014, 01:02 PM   #23
Evolved Member
iTrader: (7)
 
charlie.tunah's Avatar
 
Join Date: May 2010
Location: Maine
Posts: 836
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 2005 MR

Will this also work on an evo x?
Offline
 
Reply With Quote
Old Jun 12, 2014, 05:38 PM   #24
Evolving Member
Thread Starter
 
Broke4speed's Avatar
 
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Thanks: 0
Thanked 0 Times in 0 Posts

Drives: 1989 Dodge Colt GT Turbo w/2003 Sonata A/T ECU flashed with 9653 V7

Nope, since the freebie flashing utility inside evoscan is only 8/9. The communication protocols are also different in the X, so the cable won't connect.
Offline
 
Reply With Quote
Old Aug 6, 2017, 07:57 PM   #25
ZMX
Newbie
 
Join Date: May 2010
Location: Indiana
Posts: 16
Thanks: 0
Thanked 0 Times in 0 Posts
When I put 12v to pin 79, the VAG COM FTDI cable wouldn't connect, and the car wouldn't start.

I am able to use the cable to datalog.

After looking at the pinout and seeing that pin 80 provides 12v power, I ran a jumper between pin 79 and pin 80. Did I do something wrong?

Offline
 
Reply With Quote
 
 
Reply

Related Topics
Thread Thread Starter Forum Replies Last Post
HOW TO: Recover your EvoX ecu after a failed reflash. evoscan Evo X Engine Management / Tuning Forums 52 Jun 20, 2017 01:46 AM
Connection Error silex EcuFlash 15 Mar 15, 2010 04:47 PM
Tactrix cable fault? Detailed troubleshooting! silver_evo EcuFlash 6 Apr 2, 2009 09:40 PM
Mut Monitor V1.9 Release 31/1/2009 CLaNZeR General Engine Management / Tuning Forum 0 Jan 31, 2009 02:26 PM
Tactrix cable and PDA/Pocket PC - working logger evo828 EcuFlash 13 Feb 21, 2008 02:56 PM


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



All times are GMT -7. The time now is 12:23 PM.


 
  • Ask a Question
    Get answers from community experts
Question Title:
Description:
Your question will be posted in: