Hello! A couple of days ago I replaced my Ford Focus mk3 battery and I thoughtbthis would be an easy 30min job, but....

After installing it I went to start the car and I got greeted with lot of errors, mainly Engine failure. I hooked up my obd2 cable and opened Forscan to see that the TCM and the PCM can't be accesed, while all the other modules worked properly. Could I have completely bricked the 2 most expensive modules in my car with a simple battery replacement?? No fuses are blown though..

 

I'd say it's worth contacting Forscan support and sending them the 'bin' and 'txt' files (they'll ask for them anyway) from the forscan log folder (search in windows search bar). They were fantastic when I thought I'd bricked a couple of my modules and very patient with me!!

Does your horn and blower motor work?

14 minutes ago, Dan62 said:

Does your horn and blower motor work?

Yes, everything works except that the car doesn't know what gear is selected as I can freely change them but none will show up highlighted in the instrument panel and that it doesn't try to crank.

I've hooked up Focccus to it and it can successfully read data from every module except the PCM and TCM, to which it gives me an "Can't read module" error

18 minutes ago, Marcgr said:

Yes, everything works except that the car doesn't know what gear is selected as I can freely change them but none will show up highlighted in the instrument panel and that it doesn't try to crank.

The only other suggestion I can offer is to check you have battery voltage at F30 in the battery junction box, don't remove the fuse just probe the pins on the top of the fuse either side of the fuse rating.

AFTER CHECKING FUSES

Turn ignition on

leave key in vehicle (if keyless)

open driver's window (in case of accidental lock)

open bonnet

disconnect battery negative for 10 minutes

press brake pedal a few times whilst disconnected

ENSURE positive cable is fully secure

reconnect negative cable

turn ignition off (if key was in ignition still)

start engine without pressing throttle.

See if that works

 

 

23 minutes ago, DaveT70 said:

AFTER CHECKING FUSES

Turn ignition on

leave key in vehicle (if keyless)

open driver's window (in case of accidental lock)

open bonnet

disconnect battery negative for 10 minutes

press brake pedal a few times whilst disconnected

ENSURE positive cable is fully secure

reconnect negative cable

turn ignition off (if key was in ignition still)

start engine without pressing throttle.

See if that works

 

 

Thanks! It didn't work though, I get the same issues as before.. I guess this was done to reset PCM's memory?

 

 

1 hour ago, Dan62 said:

The only other suggestion I can offer is to check you have battery voltage at F30 in the battery junction box, don't remove the fuse just probe the pins on the top of the fuse either side of the fuse rating.

That's a great suggestion to check the junction box.. But what do you mean by "at F30"? The 3rd fuse? As they're labeled as MEGA 1...10

That's the high current fusebox with the MEGA fuses.
See attached

Oh you meant the fuse box, my bad. F30 is not used in my car, but I checked visually all the PCM and TCM related fuses and they are not split

29 minutes ago, Marcgr said:

Oh you meant the fuse box, my bad. F30 is not used in my car, but I checked visually all the PCM and TCM related fuses and they are not split

I was looking at diagrams for 2013 model, did find a 2014 diagram and equivalent fuse seems to be F38

3 minutes ago, Dan62 said:

I was looking at diagrams for 2013 model, did find a 2014 diagram and equivalent fuse seems to be F38

The fuse is ok sadly..

 

I'll attach below a short video (30 sec) of what the car does when I try to start it

youtube link

If you haven't already, you really need to contact Forscan support. Forscan wouldn't even find the modules I thought I bricked and the Forscan team wrote new software to resolve the issue. Admittedly, it was different modules, but it's got to be worth a try.

16 minutes ago, Nathan Buffery said:

If you haven't already, you really need to contact Forscan support. Forscan wouldn't even find the modules I thought I bricked and the Forscan team wrote new software to resolve the issue. Admittedly, it was different modules, but it's got to be worth a try.

Forscan no longer offers engineering support due to the russian sanctions.. I tried to recover / update the modules with forscan but it didn't work

I guess my best bet is to contact a service with IDS and let them try revive the modules..

13 hours ago, Marcgr said:

I tried to recover / update the modules with forscan but it didn't work

Don't try to recover/update the modules.

"Reset" each module in Forscan in maintenance.

Does Forscan see all the modules?

Have you got DTCs?

Also, what adapter are you using? When I bricked my modules, in desperation I plugged my older Tunnelrat adapter to see if it worked, but I had a message come up saying 'using this adapter is not recommended'. Im guessing the newer versions of Forscan dont like the older adapters. 

There is also an option in settings, you might want to try. Change the 'ISO 17565' support from 'Auto' to 'application'. 

I'm not 100% sure what this does, but this is what Forscan support advised me to do. As you are not getting a response from them....its worth a try!! 

1 minute ago, Nathan Buffery said:

I plugged my older Tunnelrat adapter to see if it worked, but I had a message come up saying 'using this adapter is not recommended'. Im guessing the newer versions of Forscan dont like the older adapters. 

That's a generic warning they give now, in case you try to do updates with it. They're OK for DTCs and programming etc

5 hours ago, DaveT70 said:

Don't try to recover/update the modules.

"Reset" each module in Forscan in maintenance.

Does Forscan see all the modules?

Have you got DTCs?

I got DTCs in all the modules, mainly "can't connect to ecu" or "can't connect to tcm", but the DTCs in the tcm and pcm can't be read. 

 

4 hours ago, Nathan Buffery said:

Also, what adapter are you using? When I bricked my modules, in desperation I plugged my older Tunnelrat adapter to see if it worked, but I had a message come up saying 'using this adapter is not recommended'. Im guessing the newer versions of Forscan dont like the older adapters. 

There is also an option in settings, you might want to try. Change the 'ISO 17565' support from 'Auto' to 'application'. 

I'm not 100% sure what this does, but this is what Forscan support advised me to do. As you are not getting a response from them....its worth a try!! 

I have their reccomended OBDLink EX. I'll try that

Just another thought..... have you tried connecting to the vehicle without using the stored profile? 

Have you had it remapped?

5 hours ago, Nathan Buffery said:

Just another thought..... have you tried connecting to the vehicle without using the stored profile? 

yes and it fails

5 hours ago, DaveT70 said:

Have you had it remapped?

what exactly?

forgive the obvious but.. why did you replace the battery and which battery have you replaced it with?

13 hours ago, Marcgr said:

what exactly?

Have you had the car remapped? 

Did you say earlier that you've tried 'recovery mode' in forscan? 

https://forscan.org/forum/viewtopic.php?f=13&t=18751&p=70631#p70631