openecu.org

I have tried to find a way to get rid of the CEL light on my 2006 WRX (DBW), but nothing works. I can not connect wiht Ecuexplorer and OBD scan tech http://forums.openecu.org/viewtopic.php?t=1225 does not work either

Is it not possible to reset the ECU on DBW cars

To reset you just need to disconnect the negative battery terminal and turn on a light (hit the brakes), then leave it for a few seconds. Same as any car.

Can you take it to Autozone and have them pull the code?

Freon wrote:To reset you just need to disconnect the negative battery terminal and turn on a light (hit the brakes), then leave it for a few seconds. Same as any car.

Can you take it to Autozone and have them pull the code?

I think I now the code (over boost and fuel cut). I have removed the trouble code with enginuity, but CEL is still on. I will try the battery method then, thanks!

That did not work

I will try to leave the batteri disconnected for a longer time (20 minutes) to see if that helps...

Twinturbo wrote:I can not connect wiht Ecuexplorer and OBD scan tech http://forums.openecu.org/viewtopic.php?t=1225 does not work either

Your FTDI device drivers aren't installed properly.

Delete your current FTDI device drivers using Add/Remove Programs. Install fresh ones from http://www.ftdichip.com/Drivers/VCP.htm.

Twinturbo wrote:That did not work

I will try to leave the batteri disconnected for a longer time (20 minutes) to see if that helps...

Then you have different CEL other than overboost fuel cut. Resetting the ecu would get rid of this CEL until you overboosted again.

Jon [in CT] wrote:

Twinturbo wrote:I can not connect with Ecuexplorer and OBD scan tech http://forums.openecu.org/viewtopic.php?t=1225 does not work either

Your FTDI device drivers aren't installed properly.

Delete your current FTDI device drivers using Add/Remove Programs. Install fresh ones from http://www.ftdichip.com/Drivers/VCP.htm.

I see my Open Port 1.3 in the right com port (COM 4), but can not connect to my ECU. I have the latest drivers which is included in Ecuflash 1.29 (works fine) , but I will try to remove them and install the new ones then...

merchgod wrote:

Twinturbo wrote:That did not work

I will try to leave the batteri disconnected for a longer time (20 minutes) to see if that helps...

Then you have different CEL other than overboost fuel cut. Resetting the ecu would get rid of this CEL until you overboosted again.

Maybe, but I do not know what code, because I can not read the codes with any program I know of

Twinturbo wrote:

Jon [in CT] wrote:

Twinturbo wrote:I can not connect with Ecuexplorer and OBD scan tech http://forums.openecu.org/viewtopic.php?t=1225 does not work either

Your FTDI device drivers aren't installed properly.

Delete your current FTDI device drivers using Add/Remove Programs. Install fresh ones from http://www.ftdichip.com/Drivers/VCP.htm.

I see my Open Port 1.3 in the right com port (COM 4), but can not connect to my ECU. I have the latest drivers which is included in Ecuflash 1.29 (works fine) , but I will try to remove them and install the new ones then...

I already had the latest driver (2.00.00), so that was not the problem either

Has anyone with 2006 WRX ECU been able to read codes and reset the ECU?

Twinturbo wrote:I already had the latest driver (2.00.00), so that was not the problem either

Did you uninstall the drivers in the manner described at http://www.ftdichip.com/Support/Knowledgebase/index.html?xpuninstallingcdmdrivers.htm?
Did you download and install the drivers using the process described at http://www.ftdichip.com/Support/Knowledgebase/index.html?xpinstallingdriversviafnhw.htm?

Jon [in CT] wrote:

Twinturbo wrote:I already had the latest driver (2.00.00), so that was not the problem either

Did you uninstall the drivers in the manner described at http://www.ftdichip.com/Support/Knowledgebase/index.html?xpuninstallingcdmdrivers.htm?
Did you download and install the drivers using the process described at http://www.ftdichip.com/Support/Knowledgebase/index.html?xpinstallingdriversviafnhw.htm?

No, I did not try to uninstall because both Ecuflash and Ecuexplorer see my open port 1.3 in the right COM port and Ecuflash works just fine (I have pulled my stock rom file and reflashed my ECU with new tunes many times now without any problem). If Ecuflash works fine and I see my open port 1.3 in Ecuexplorer I do not think the driver is the problem. The problem is that I can not connect to my ECU in Ecuexplorer (maybe it is because it contains an older version of Ecuflash that don't support 32-bit ECU?)

You're not willing to spend $0 and ten minutes of your time to test whether your EcuExplorer problem is due to a half-installed driver?

Twinturbo wrote:Has anyone with 2006 WRX ECU been able to read codes and reset the ECU?

Yes, and yes.

It works fine. You have an issue with your computer and/or hardware, methinks.

wall of tvs wrote:

Twinturbo wrote:Has anyone with 2006 WRX ECU been able to read codes and reset the ECU?

Yes, and yes.

It works fine. You have an issue with your computer and/or hardware, methinks.

OK

Then I will try to remove the "old" driver and reinstall the ones proposed above

I removed all USB com drivers and installed the ones proposed above and now nothing works. Not Enginiuty, Ecuflash OR EcuExplorer

Before Ecuflash and Enginuity worked without any problem

wall of tvs, which Tatrix cable and what version of Ecuflash do you use?

I have Open Port 1.3 and Ecuflash 1.29...

Did you use Ecuexplorer to read the codes and reset the ECU?


I had to uninstall and reinstall Ecuflash to get it to work again.

Still same problem. Ecuexplorer (uninstalled and reinstalled again) recognises my Open Port 1.3 cable at the right COM port, but I can not connect to my ECU