unable to read 2005 subaru STI UK Spec Advice please

User topics relating to hardware that interfaces PCs to ECUs

Moderator: Freon

unable to read 2005 subaru STI UK Spec Advice please

Postby japerformance » Wed Apr 25, 2007 7:31 am

Hello Peeps, wonder if someone could kindly help me out here. I have a 2005 sti uk spec , have connected the two green connectors under the steering wheel to go into diagnostics mode and also the 4 prong attachemtn that came with the kit. I hook up to the laptop and try to read ecu and keeps coming up with an error and says to read log.

[00:37:47.484] Version 1.30.1095
[00:37:47.484] 8 memory models read.
[00:37:49.875] 148 ROM metadata models read.
[00:37:49.875] checksum module "subarudbw" loaded.
[00:37:49.875] flashing tool "wrx02" loaded.
[00:37:49.875] flashing tool "wrx04" loaded.
[00:37:49.875] flashing tool "sti04" loaded.
[00:37:49.875] flashing tool "sti05" loaded.
[00:37:49.875] flashing tool "mitsukernel" loaded.
[00:37:49.875] flashing tool "mitsukernelocp" loaded.
[00:37:49.875] flashing tool "mitsubootloader" loaded.
[00:38:03.640] SSM2 init
[00:38:03.828] [FF] A2 10 0F 3D 44 59 30 05 73 FA EB 80 2A 43 FE AA
00 10 00 60 CE 54 FC B0 00 00 00 00 00 00 00 00
00 DC 00 00 55 1F 00 00 00 02 00 00 00 00 00 E0
00 00 00 00 00 00 00 00
[00:38:03.828] SSM2 ECU ID is 3D 44 59 30 05
[00:38:03.828] SSM2 cmd_0x81

i get that far when the error comes up. can anyone shed some light on the problem or if they have encountered it.

Regards
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby bendalyn » Wed Apr 25, 2007 7:42 am

hi there,

try this sequence:

1. connect the green connectors
2. plug in the white connector
3. press 'read ecu'
4. key on
5. press ok

try to do 4 & 5 within a second of each other.

hope this helps...
bendalyn
 
Posts: 8
Joined: Tue Feb 20, 2007 4:53 pm
Location: UK

Postby japerformance » Wed Apr 25, 2007 7:50 am

worth mentioning it is an AJ 840 ecu
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby blue.taxi » Thu Apr 26, 2007 5:06 pm

this also happen to my MY05 WRX uk spec. Now try to do a switch for the green connectors.

[01:12:46.088] Version 1.30.1095
[01:12:46.098] 8 memory models read.
[01:12:48.932] 146 ROM metadata models read.
[01:12:48.932] checksum module "subarudbw" loaded.
[01:12:48.932] flashing tool "wrx02" loaded.
[01:12:48.932] flashing tool "wrx04" loaded.
[01:12:48.932] flashing tool "sti04" loaded.
[01:12:48.932] flashing tool "sti05" loaded.
[01:12:48.932] flashing tool "mitsukernel" loaded.
[01:12:48.932] flashing tool "mitsukernelocp" loaded.
[01:12:48.932] flashing tool "mitsubootloader" loaded.
[01:12:54.690] SSM2 init
[01:12:54.870] [FF] A2 10 0F 3D 44 58 30 05 73 FA EB 80 2B C3 02 AA
00 10 00 60 CE 54 FC B0 60 00 00 E0 00 00 00 00
00 DC 00 00 55 1F 00 00 02 02 00 00 00 00 00 E0
00 00 00 00 00 00 00 00
[01:12:54.890] SSM2 ECU ID is 3D 44 58 30 05
[01:12:54.890] SSM2 cmd_0x81

said if we can read the rom, when we flash in the remaped file do we need to do the "fast way" or "slow way"?

TQ
blue.taxi
 
Posts: 61
Joined: Sun Jul 23, 2006 8:38 am

Postby japerformance » Fri Apr 27, 2007 12:28 am

yep i tried that sequence but still no joy. can it have anything to do with an ecutek remap, what error comes up when it has already been ecutek mapped.

regards
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby blue.taxi » Fri Apr 27, 2007 4:16 am

if there is a ecutek in the ecu this may not work for the ecuflash, but my is just a stock ecu w/ a AFR controller. Can be the AFR controller is the 1 that cause this problem?
blue.taxi
 
Posts: 61
Joined: Sun Jul 23, 2006 8:38 am

Postby japerformance » Sun Apr 29, 2007 12:28 am

the ecutek is just a reflash of the stock ecu. I am told if it has been reflashed using ecutek that there is a lock on the ecu so openecu wont work.

I am still not able to read the rom and keep getting the same log as above can someone shed light if they have encountered this problem before.

regards
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby Hyper » Sun Apr 29, 2007 7:52 pm

sorry m8, but if you have the newer ecutek with lock, you won't be able to use opensource
Hyper
 
Posts: 51
Joined: Mon Jul 11, 2005 7:38 pm

Postby japerformance » Sun Apr 29, 2007 8:38 pm

yep got that bit mate cheers, what i was asking was is there anyway i can tell for sure if it has been ecutek'd or is it a comms error etc. the log details above is all i get everytime. Has anyone else encountered the error with the same log and if so what was the cure.

Regards

Simon
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby japerformance » Sat May 12, 2007 11:30 am

anyone with the same problem found solution yet,
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire

Postby JonnyM » Sun May 13, 2007 4:23 am

As far as I can remember from another thread here about a year ago, all UK Subaru's are EcuTek mapped by the importer.
JonnyM
 
Posts: 20
Joined: Mon May 30, 2005 9:23 pm

Postby japerformance » Sun May 13, 2007 8:37 am

Hello Jonny,

thanks for your mail, my question now is with the above log that i pasted at the begining of the post, is it that screen you get when trying to read an ecutek rom file. if so is it possible to take it to a ecutek dealer to get the lock taken off.

Regards
japerformance
 
Posts: 42
Joined: Mon Jul 31, 2006 2:50 am
Location: aberdeenshire


Return to Interface Hardware

Who is online

Users browsing this forum: No registered users and 10 guests