Ford Focus ST Forum banner

Focccus PC app as-built editor AND all around reprogrammer

1.1M views 2.1K replies 273 participants last post by  ad33b  
could be. As I understand it, communicating directly with the bcm causes it to not to be able to communicate with the other modules on the can (controller area network). As a result all the other modules basically throw a dtc because they can't talk to the bcm while you're talking to it. They will all clear with forscan. And as jdub1981 stated, you'll need to use forscan because you will have to scan both high and medium speed can and clear the dtc's on both networks. When you scan both networks, you'll probably find a lot more. You may see one about the sunroof that wont go away, just ignore it.
 
Depending on the application the car should be off. Doing global open/close can be done with it running. Stuff like headlights the headlights need to be turned off or you will fault out.

Sent from my SCH-I535 using Tapatalk
Maybe that explains the P2610 ECM/PCM Internal Engine Off Timer Perf error I got both times it died. I will definitely be KOEO from now on.
 
I dot the OBDLink MX, and Focccus says "cannot connect to ECU when I "read from BCM.

Also, the file from As-built seems corrupt.
Focccus cannot read it, and says "error while reading config"

I can get connected using forscan and OBDwiz.

Any help?
Focccus will not work with a Fiesta. I tried it just for kicks a few months ago. Besides, the USDM 2014 Fiesta doesn't have the ability to do the global open/close. I wish it did.
 
This isn't the checksum I'm speaking of, I should have been more explicit. There is that file checksum, but as far as I'm aware (and maybe Ford doesn't use it, I haven't actually tried it!), Bosch MED17 Units have a tamper protection system in place. At least supposedly according to this.

This is separate from the normal checksum, and while it's fine and dandy, it would be neat to have the method to calculate these checksums so that custom software could be written. As someone who programs full-time, but in a different field, I definitely would love to tinker around in the area.

I totally agree on the whole "hacking" crap too. It's pathetic. It's not hacking. You're just sending messages over the bus after you have gotten actual physical access to it. If you get actual physical access to a computer, you could do whatever the hell you wanted. It's sensational bullcrap, plain and simple.
But it makes for such a good "story"!!!!
 
Well, it's not the mod itself that creates the errors, it's the disconnection between the BCM and all the other modules that happens when you write to the BCM that causes the error. You interact with the BCM through the HS-CAN bus, but the BCM interacts with all the other modules however it does, and that's where it happens.
Thanks but I was already aware that the mod in and of itself didn't create the errors. I had mentioned ^^this^^ in an above post. I was just commenting on the irony of it. Plus some folks have done the global open/close without a modified elm327 and then don't have a way to clear the errors immediately.

The BCM and the IPC act as gateways to the other modules. Whenever a user specifically communicates with an individual module all communication stops between the other modules so priority can be given. This inadvertently causes the DTC's. Its not a big deal but it does cause many many false DTC's in the process. If you dont have the ability to erase them on the MS Bus it isnt a big deal, they will erase themselves after a 10 or so key turns.

Sent from my GT-N7105 using Tapatalk
I did not know this, Thanks!
 
Trying Forscan. My OBD scanner does not have the switch for the SW and MS can. It was $9. And when I try to reset the DTC, it tells me it is unable to and then won't read the DTC anymore either.

Now I'm thinking I broke something...
Most likely not, You'll just have to buy a usb ELM327 and add the switch per instructions here. Or purchase the OBDlink MX as jdub1981 suggested. It's kinda ironic in that you don't have to have access to the ms can to perform the global open close mod but you do in order to clear the errors that performing it can create.
 
Thanks for the info. I'm a total noob to a lot of this so I don't know what "clearing your DTCs" is.
Sorry to be obtuse! When I did this there were a bunch of Diagnostic Trouble Codes, that were a result of talking to the BCM. I tried clearing them with Torque but as I found out here you have to use the forscan utility to do that. It's mentioned at the beginning of this thread I think.
 
If global open/close is all you wanted then you don't need to change anything else. Mine had some existing options as unknown/without also. Did you clear all the dtc's with forscan afterwards?

Edit: sorry jdub, I didn't refresh before I posted
 
Today I cleared the list of dtcs with forscan. One keeps coming back. I assume it's becuase the global open close doesn't apply to north american cars?

===DTC B113D:14-2F===
Code: B113D - Sunroof Global Open/Close Control

Additional Fault Symptom:
- Circuit Short To Ground Or Open

Status:
- DTC Present at Time of Request
- Malfunction Indicator Lamp is Off for this DTC

Module: Body Control Module===END DTC B113D:14-2F===