Clearing ECU (CEL/DTC) Errors

[camel_landy]

Hi All,

OK, so how do you do it... I've got the Check Engine Light (CEL) on and now I've fixed the cause of the problem, I want to clear the error.

How?

It's a 2005 Impreza WRX (Blobeye) and I simply want to read & clear the codes, without having to re-flash the ECU (which appears to be the common solution).

These are the tools I've got:

• Genuine Tactrix OpenPort 2.0
• Carly Universal Adapter & Application
• StreetWize Wireless OBDII Dongle
• Windows 10 Laptop
• OSX Laptop
• iPhone

I've had a look at the following apps, without any luck:

• EcuFlash
• ecuExplorer
• Learning View
• CAN Data Miner
• FreeSSM

I've also tried to get ROMRaider up and running but gave up.

What can you suggest?

M

[p4cks]

A £6 OBDII reader will do it

https://www.ebay.co.uk/itm/Car-Fault-Code-Reader-E...

[R12many]

https://sourceforge.net/projects/freessm.berlios/

[camel_landy]

R12many said:

https://sourceforge.net/projects/freessm.berlios/

Thanks but I've already tried that one.

M

[R12many]

That will clear the codes and reset the CEL. You say you've had a look at it but have you tried it?

Edited by R12many on Friday 27th March 21:40

[camel_landy]

R12many said:

That will clear the codes and reset the CEL. You say you've had a look at it but have you tried it?

Yep, tried it. Which is a pity coz it looked ideal.

The problem with FreeSSM is that it's old. It only connects via a COM port but all that's available these days is USB or WiFi.

M

[R12many]

Yes, you'll need a laptop with USB port and then a USB to OBD2 cable. The newer cables will allow you to reset the CEL but you will need an older one with a different chipset if you want to do any flashing of the ECU. I needed to switch off the secondary air system check by reflashing the ECU and it took a long time to find the right cable. Ended up buying one if a chap on Forester.org.

[camel_landy]

R12many said:

Yes, you'll need a laptop with USB port and then a USB to OBD2 cable.

I've got that (Tactrix)...
...but because the applications are so old, FreeSSM, etc... will only communicate via a COM port (i.e. they don't recognise USB).

M

[Liamsaid]

I believe freessm needs a vagcom cable, which are USB. It connects from my win 10 laptop to my 2007 legacy.

[camel_landy]

Liamsaid said:

I believe freessm needs a vagcom cable, which are USB. It connects from my win 10 laptop to my 2007 legacy.

OK... I've got the last version of FreeSSM (IIRC - 1.2.5) and it only has the option to connect using a COM (serial) port.

Although it's USB, does the VAGCOM cable present itself as a COM port? If it does, that'll explain why you can connect.

M

[R12many]

My laptop is as old as the car which probably helps

Just tried both my cables on my daughter's 2019 Dell with Windows 10 and they both show as COM ports if that's any help?

Edited by R12many on Saturday 28th March 11:49

[camel_landy]

R12many said:

Just tried both my cables on my daughter's 2019 Dell with Windows 10 and they both show as COM ports if that's any help?

Ah ha... Yes, that does help.

Do you have a part number for them?

M

[R12many]

No part numbers on either of them unfortunately. The first I bought off eBay back in 2015 but could only pull the file from the ECU and not flash back the modified file. It still allowed me to reset the CEL with FreeSSM though. The second I bought from another forum member as it had the older chipset and would allow me to flash back the file.
Here's the thread from back then:

https://www.subaruforester.org/threads/2005-second...

[TEKNOPUG]

What was the error for and what did you do to fix it?

Edited by TEKNOPUG on Saturday 28th March 18:13

[camel_landy]

R12many said:

No part numbers on either of them unfortunately. The first I bought off eBay back in 2015 but could only pull the file from the ECU and not flash back the modified file. It still allowed me to reset the CEL with FreeSSM though. The second I bought from another forum member as it had the older chipset and would allow me to flash back the file.
Here's the thread from back then:

https://www.subaruforester.org/threads/2005-second...

OK, ta... I'll have a look and maybe get one of those VAGCOM type cables.

M

[camel_landy]

TEKNOPUG said:

What was the error for and what did you do to fix it?

The error was for the turbo waste solenoid...
...and after a quick rummage, I found the pipe had popped off.

M

[camel_landy]

For sake of completeness and incase someone else is in the same position, here's how I've managed to close this one off:

I ended up purchasing the 'ScanTool OBDLink SX' cable from Amazon. The cable came with a free utility called "OBDwiz", which I downloaded from their (OBDLink) website and installed onto my Windows 10 laptop.

The cable plugs into the USB port and can be configured to behave as a serial (COM) port if required.

My first couple of attempts at using it, failed. However, as soon as I changed the "OBD-II Protocol" setting from "Automatic" to "ISO 9141-2 (5 baud init, 10.4 Kbaud)", it immediately jumped into life and connected. Once connected, I was able to scan and clear the CEL & DTC Codes.

It's also worth noting that I did not need to do anything with the jumpers under the dashboard.

TL/DR:

• Windows 10
• OBDLink SX cable
• OBDwiz
• OBD-II Protocol: ISO 9141-2 (5 baud init, 10.4 Kbaud)
• Diagnostic Jumpers: Not required

HTH

M

[R12many]

Good to hear you got there in the end.