05 Legacy GT: 1.2 or 1.3M cable

[zuczek]

I know both will work. I won't be flashing anything other than my Legacy. IS the 1.3M cable better for future upgrades? Is it capable of faster transfers, or other things that the 1.2 cable can't do.

Anyone?

[zuczek]

Anyone? I just want to know if the extra $10 for the 1.3M (over the 1.2)gives me anything other than the Mits connector which I won't use.

Is the 1.3M any faster?

[zuczek]

Anyone? I just want to know if the extra $10 for the 1.3M (over the 1.2)gives me anything other than the Mits connector which I won't use.

Is the 1.3M any faster?

[Evo4Mad]

As far as I know they are the same except for the additional connector. both use the same ftdi chipset, so wont run any faster nor slower.

[ahains]

I don't think they could be identical since the 1.3M will not work on a 2001-2005 wrx.

Personally I recommend the 1.2 because you are most likely going to get together with wrx owners more often than mitsu owners (just because you own a Subie) and with the 1.2 you'd be able to spread the openecu love

[Evo4Mad]

I will investigate the schematics on the two cables, but I think they wont be far off.. I'll let you know what I find...

[Freon]

http://www.openecu.org/index.php?title= ... cleSupport

[zuczek]

I will investigate the schematics on the two cables, but I think they wont be far off.. I'll let you know what I find...

Any luck with that?

[Evo4Mad]

1.3M is fine.. it is better.

[ahains]

1.3M is fine.. it is better.

I guess that "better" is always a good thing, but surely any improvements in the design will have zero impact on the functionality with all existing software right?

I still suggest the 1.2 because of the aforementioned openecu love for your fellow subies. I have the 1.2 for my wife's Outback XT and my 2004 wrx. I'm getting an up/dp swapped into my car on Sunday which happens to be a BBQ at this shop, so there will be a bunch of subies there. I'll have my family with me, but I'm hoping I'll have time to hand out a few free stage 1 or stage 2 open source reflashes to anyone who wants them. If I had bought the 1.3M I wouldn't be able to help my brethren driving my03 or earlier.

Of course if you meet up with evo's as much or more, then the same suggestion works the other way

[LGTspore]

While I've been able to read the ROM off my Legacy GT using the 1.3 cable, I haven't been able to do data logging...

It's the software that other legacies I know have been using, but with the 1.0 and 1.2 cables...

I'm the only one using the 1.3, mainly coz I thought it'd be useful for my friends driving mitsus as well..

You fellas reckon it's a cable issue?

Thks!

[Jon [in CT]]

While I've been able to read the ROM off my Legacy GT using the 1.3 cable, I haven't been able to do data logging...

You fellas reckon it's a cable issue?

Thks!

No. It's most likely a device driver issue. EcuFlash for Mitsubishis and drive-by-wire Subarus needs to use FTDI's D2XX device driver, so that's what is shipped and installed when you order a 1.3 cable. The ecuExplorer datalogger needs to use FTDI's virtual COM port (VCP) device driver. FTDI now has a new driver for Windows, called Common Driver Model (CDM), which can support both EcuFlash and ecuExplorer.

The new CDM device driver can be downloaded from:
http://www.ftdichip.com/Drivers/D2XX.htm

Installation instructions are at:
http://www.ftdichip.com/Documents/InstallGuides.htm

[imprezarsx]

I was datalogging just fine on the wife's LGT with the 1.2 cable. Didn't have to do anything special, just install the open source software. I have both cables and have never installed anything for the 1.3M cable. Everything has worked great.

[LGTspore]

Thks guys!

I'll go try this out... hopefully this will work with the newer driver!

Cheers!

[Cabal]

While I've been able to read the ROM off my Legacy GT using the 1.3 cable, I haven't been able to do data logging...

You fellas reckon it's a cable issue?

Thks!

No. It's most likely a device driver issue. EcuFlash for Mitsubishis and drive-by-wire Subarus needs to use FTDI's D2XX device driver, so that's what is shipped and installed when you order a 1.3 cable. The ecuExplorer datalogger needs to use FTDI's virtual COM port (VCP) device driver. FTDI now has a new driver for Windows, called Common Driver Model (CDM), which can support both EcuFlash and ecuExplorer.

The new CDM device driver can be downloaded from:
http://www.ftdichip.com/Drivers/D2XX.htm

Installation instructions are at:
http://www.ftdichip.com/Documents/InstallGuides.htm

Is there a trick to getting these installed? I have the latest install of EcuFlash that included drivers, and my cable shows up as an "OpenPort 1.3 Subaru" (which seems kinda strange since I ordered from this link). Flashing with EcuFlash works great, but I can't log with ecuExplorer. When I try to install those CDM drivers, it tells me they don't match my hardware. Any ideas?

Edit: I also tried using the VCP driver posted in this thread, but WinXP reported it didn't match my hardware (1.3M vs 1.3-that-should-be-1.2?).

Edit 2: Per the installation guide, it looks like I'll need to add the OpenPort VID and PID to the CDM install INF files, there's nothing that matches 0xCC49 in there.

Final edit: I took the easy way out and adjusted all the INF files in the VCP driver in the first edit to use CC49 instead of CC48. Logging works and I'll worry about the new driver later.