openecu.org

by **steve_s13** » Sun Sep 21, 2008 8:35 am

Guys tried to connect to my JDM Subaru STI December 2002 Model and I keep continually getting this Error message.

[13:03:03.811] Using interface OpenPort 1.3 Universal TX26pE0Ea4c537d57e2918bf4c251c0bc385cf707e34640a
[13:03:11.482] denso02_bootloader_cmd_start
[13:03:12.714] denso02_bootloader_cmd_start
[13:03:13.935] denso02_bootloader_cmd_start
[13:03:15.177] denso02_bootloader_cmd_start
[13:03:16.409] denso02_bootloader_cmd_start
[13:03:16.870] kernel get version
[13:03:17.220] interface close
[13:03:17.240] interface close

I never had this problem when flashing/tuning my EVO 7 or EVO 8

So i know ive definitely not got a problem with my cable as ive used it on several occasions on the EVO

I basically....
1. joined the 2 GREEN Test connectors together
2. plugged in the 4 Pinnned jumper plug
3. tried to connect
4. computer displayed the above log

Can someone tell me if im being and idiot and missing something here

I looked around the loom underneath and couldnt find anything

Im using v.1.34 as ive always done on the EVO and my mates EVO's

can anyone help....

Thanks in advance....

by **steve_s13** » Tue Sep 23, 2008 5:25 am

anyone???? BUMP

is it my cable perharps

Ive read somewhere that the cables are different? is this true?

If I buy the new OPENPORT 2 setup will this work for me instead as well as allow me to possibly flash newer model vehicles alternative to Subaru?

Anyone help on this topic?

Cheers people!

by **steve_s13** » Tue Sep 23, 2008 11:15 am

bump.... anyone!!

by **steve_s13** » Thu Sep 25, 2008 2:15 am

34 views but no answers??

by **greg** » Tue Sep 30, 2008 1:22 am

first post here hello :wink:

I have this exact same problem with a 2003 european wrx

by **steve_s13** » Tue Sep 30, 2008 2:06 am

what cable are you using mate? Are you using the open port universal cable? Or the Subaru specific cable or you using the new Openport 2.0

by **greg** » Tue Sep 30, 2008 2:20 am

open port universal and ecuflash 1.38 iam currently trying everthing to get this to work, have been reading through other no comunications posts, possibly this ecu type will just not read or possibly been ECUT**'ed

by **steve_s13** » Tue Sep 30, 2008 6:05 am

that's what I thought but they guys insists that it has definitely not been ecutekked or locked and that it had been programmer with openecu. I did some hunting around and apparently tactrix Did do a specific cable for individual manufacturers. I'm beginning to think that it's my cable and maybe even the wiring communication being different.

I've just ordered a openport 2 bundle but I'd still like to know. Getting pissed of with this Scooby now . I assume you have your jumpers plugged in?

Can anyone else shed some light on this?

by **steve_s13** » Tue Sep 30, 2008 6:08 am

Anyone else other than myself or greg had or is experiencing this problem that could perhaps please point us in the right direction?

by **greg** » Tue Sep 30, 2008 7:34 am

I believe the car i have may have been ECU**K'd
I have the jumper plugged in

12:19:26.109] Using interface OpenPort 1.3 Universal TX25LzyCb044f6c914e91098ab240fa7ea9d25d750e713e9
[12:19:30.671] denso02_bootloader_cmd_start
[12:19:31.593] denso02_bootloader_cmd_start
[12:19:32.828] denso02_bootloader_cmd_start
[12:19:34.062] denso02_bootloader_cmd_start
[12:19:35.296] denso02_bootloader_cmd_start
[12:19:35.734] kernel get version
[12:19:36.062] interface close
[12:19:36.062] interface close

I think this message is just basically no comunication
you can get the same with the ignition turned off

The car is a euro 2003 wrx
but if i select 2002-2003 usdm impreza wrx
i get this which i think at least has the ecu id

12:19:46.718] Using interface OpenPort 1.3 Universal TX25LzyCb044f6c914e91098ab240fa7ea9d25d750e713e9
[12:19:49.781] kernel get version
[12:19:50.171] SSM2 init
[12:19:50.343] SSM2 ECU ID is 1B 44 58 04 05
[12:19:52.359] interface close
[12:19:52.375] interface close

this is the first car ive tried to comunicate with (sods law

) with flash ecu so it s a bit confusing diagnosing the issue

by **steve_s13** » Wed Oct 01, 2008 7:47 am

i know how you feel mate, had intiial issues with an EVO but once i got through it it made some nice power and drivability was Much improved once I cracked on with logging

ive bitten the bullet and gone and bought openport 2. im praying ive not wasted my cash....

im gonna forward the thread onto Colby, apparently one of the main guys on here and see if he can shed some light.

by **steve_s13** » Mon Oct 13, 2008 6:50 am

got it finally working with openport 2.0 in the end. just thought id let you know.

gonna try and flash tonight n see what happens.

by **KanScooby** » Mon Oct 13, 2008 8:35 am

Hi all, I initially had issues connecting to a 05 JDM STi just like you did. It seems the timing of hitting the OK button to read the ROM has to be before the car goes into test mode, ie. the fans don't start cycling on and off. With that in mind, I have been able to read and write into the 05 JDM STi with no probs at all with the Tactrix Openport 1.3U and ecuflash 1.38.

by **steve_s13** » Tue Oct 14, 2008 2:14 am

yeah i figured that, i think its MORE to do with the timing on the Subaru.
On the EVO you dont have to do that.

Basically you his READ and then literally catch the ignition straight away for it to download the map.

not had time to upload yet.

anyone got a STOCK JDM 2003 Sti Map or know where i can find one..

openecu.org

Reflashing a JDM Subaru 2002/2003 sti

Reflashing a JDM Subaru 2002/2003 sti

!

Who is online