Page 1 of 1

Communication ISSUES ECUFLASH

PostPosted: Sat Nov 20, 2010 10:55 pm
by turbofied
Hi Open ECU.

I have been flashing subaru ecu's for quite a while the laptop hasn't had any issues with any ecu (forrester/Liberty/B4/Outback/WRX/STI)

Except for this 0ne 04 WRX

It had ecutek on it then got pulled back to standard(aparently)

Laptop has latest software and updates + openport 2.0

I get this messge when trying to read from ecu

[09:35:59.171] denso02_bootloader_cmd_start
[09:36:00.406] denso02_bootloader_cmd_start
[09:36:01.625] denso02_bootloader_cmd_start
[09:36:02.843] denso02_bootloader_cmd_start
[09:36:04.078] denso02_bootloader_cmd_start
[09:36:04.515] kernel get version
[09:36:04.843] interface close
[09:36:04.859] interface close


Its a little strange the diagnostics jumper makes the fuel pump and fans cycle yet the check engine light doesn't pulse...

I have tried different timing sequences

Romraider logging and learning view work.

I have the 4 pin flash block on

Any ideas?

Thanks

Re: Communication ISSUES ECUFLASH

PostPosted: Sun Nov 21, 2010 3:37 pm
by radsdau
Unfortunately in all cases that I know of, an ecutek 'unlock' doesn't unlock at all; it just puts the stock file back in (a little unethical IMO). The symptom you're seeing is consistent with this.
If you're sure everything else is working (hardware and software) and it still doesn't work, the option you're left with is an ECU unlock. Search this forum for people who can help.

Re: Communication ISSUES ECUFLASH

PostPosted: Sun Nov 21, 2010 10:47 pm
by turbofied
Spot on!

Well this was mean't to have been completely unlocked

after 2hrs of pinout tracing then comparing this to a sti with a locked ecutek ecu it reacted the same.

5 more calls to old tuning shop and the owner and ahah the ecu was only put back to a factory map and ecutek not removed!

There was a place that can do them that the two ecu's are being sent away!