Jump to content
LegacyGT.com

knfevg

Members
  • Posts

    6
  • Joined

Posts posted by knfevg

  1. I tried today several things:

    ECUFlash 1.42

    ECUFlash 1.29a

    With shorting the pins of the white terminal

    without shorting the pins

    clicking OK after switching the key to ON

    Clicking OK BEFORE switching the key to ON

     

    Here are the results:

    1.29a DIDNT WORK AT ALL. Here is the error I got:

    [01:12:01.640] Version 1.29.906

    [01:12:01.656] 8 memory models read.

    [01:12:02.921] 140 ROM metadata models read.

    [01:12:02.921] checksum module "subarudbw" loaded.

    [01:12:02.921] flashing tool "wrx02" loaded.

    [01:12:02.921] flashing tool "wrx04" loaded.

    [01:12:02.921] flashing tool "sti04" loaded.

    [01:12:02.921] flashing tool "sti05" loaded.

    [01:12:02.921] flashing tool "mitsukernel" loaded.

    [01:12:02.921] flashing tool "mitsukernelocp" loaded.

    [01:12:02.921] flashing tool "mitsubootloader" loaded.

    [01:12:07.312] unable to open OpenPort device [ Serial ].

    [01:12:07.312] unable to connect to vehicle interface.

     

    With version 1.42 more luck. When I choose 2003-2005 NONUSDM, I get this error:

    [12:40:59.718] Using interface USB <-> Serial

    [12:41:01.875] denso02_bootloader_cmd_start

    [12:41:03.109] denso02_bootloader_cmd_start

    [12:41:04.343] denso02_bootloader_cmd_start

    [12:41:05.578] denso02_bootloader_cmd_start

    [12:41:06.812] denso02_bootloader_cmd_start

    [12:41:07.250] kernel get version

    [12:41:07.578] interface close

    [12:41:07.578] interface close

     

    When I choose 2004-2005 USDM WRX, here is what I get:

    [12:40:48.875] Using interface USB <-> Serial

    [12:40:50.000] kernel get version

    [12:40:50.390] SSM2 init

    [12:40:50.546] SSM2 ECU ID is 29 44 59 61 05

    [12:40:52.578] interface close

    [12:40:52.578] interface close

     

     

    The white block has no effect at all.

    Any ideas? I have the ProDrive kit (including ECU flash). I know that some have a problem reading it. What error should I get if it's locked?

  2. O.K. so you've got an EDM(European? help me out) 2003 STi that you would like to READ the ECU off of. Correct?

     

    Sounds like the cable is working fine as it is currently working with all other applications. So from here it looks like you need to also get another piece of hardware from what I can gather. If your STi isn't drive by wire; then you will need a "port initiator" that will pass the flashing voltage and end-line signal to the ECU. At least this is the case for USDM vehicles of the same year and model. Yours may be different, so you might want to scan the OpenECU forum for more info on your specific model.

     

    Here is a link to the part that is needed for USDM vehicles:

    http://www.tactrix.com/product_info.php?products_id=33

     

    Check it out and let us know what you find...

     

    Just got back to trying this.

    Two questions:

    1. Do I need this plug just to READ the ECU? I'm not trying to flash yet, just reading...

    2. Any way I can make this plug in DIY method?

  3. I've got a EDM Impreza STi 2003 with ProDrive kit (including a new map).

    Using the VagCom cable I managed to datalog with RR, EcuExplorer and LearningView.

    Now I want to READ ONLY the current map (not writting yet).

    For this I've connected the green plug under the steering wheel, connected the USB to the computer and turned the key to ON.

    The yellow engine light was flashing and the pump was switching on and off. But, ECU FLASH couldn't read the ECU.

    I'm working with the latest ECUFLASH version.

    Any ideas?

×
×
  • Create New...

Important Information

Terms of Use