FORScan forum

Apologies if this is the wrong place to post.

I have a 2012 Focus MkIII Titanium. I am running FORScan 2.4.3 with an ODBLink EX.

While trying to upgrade the firmware on the PAM module, when I attempt to "Test Run SBL", it fails at 2%, simply saying "Service procedure has been interrupted".
I have tried resetting the PAM module, but it did not help.

"Test Run SBL" is successful on other modules.

Any suggestions?

Thanks,
Pete

wonko93 wrote: Sat Sep 25, 2021 5:38 am Apologies if this is the wrong place to post.

I have a 2012 Focus MkIII Titanium. I am running FORScan 2.4.3 with an ODBLink EX.

While trying to upgrade the firmware on the PAM module, when I attempt to "Test Run SBL", it fails at 2%, simply saying "Service procedure has been interrupted".

forscan.png

I have tried resetting the PAM module, but it did not help.

"Test Run SBL" is successful on other modules.

Any suggestions?

Thanks,
Pete

You may have just found the reason that there is an SBL test button. Usually when this question has been asked elsewhere on the forum, FORScan usually responds with words such as, "There is no way to predict what Modules a Service Procedure can be run with so it is included for all and that error message will throw when a module is encountered that does not have the provision to run that procedure built in".

That particular Module my not be Secondary Boot loadable and there for it could be Firmware Fixed and not up-gradable! A good question would be , Why are you running these procedures as this is not a service that should be run "Just because I can"! It should only be done if there is a Ford Service Advisory that requires updating Firmware in a module to fix a problem! This is the most risky procedure ever done on a vehicle. This has been known to "brick" modules and Vehicles even in a Dealer setting with Dealer equipment!

If this as any consolation I have PAM modules in two vehicles(2003 Expedition and 2010 Fusion) that this message throws if i try to run any service procedure and the only configuration that can be done is on the Fusion and it is only two digits(0 and 1) on the 736-01-01 address, one for body style(Set to Four door in this case) and number of channels( this one is set to unknown vehicle value). The Expy is not even configurable and throws that error on any procedure I run, including Configuration and AsBuilt, and both Forscan and IDS ask whether it is 2 Sensor or 4 sensor(this one has Four) when it is first connected as apparently it matters to what they read initially!

As you asked for suggestions that is all I have! If you hold a Paid license you can roll your Log and dump.bin file into a .zip file and send to https://forscan.org/contactus.html as per instructions at this page https://forscan.org/contactus.html and see what they say about it!

tractmec wrote: Sat Sep 25, 2021 9:03 pm That particular Module my not be Secondary Boot loadable and there for it could be Firmware Fixed and not up-gradable! A good question would be , Why are you running these procedures as this is not a service that should be run "Just because I can"! It should only be done if there is a Ford Service Advisory that requires updating Firmware in a module to fix a problem! This is the most risky procedure ever done on a vehicle. This has been known to "brick" modules and Vehicles even in a Dealer setting with Dealer equipment!

I have ordered a Sync 2 -> Sync 3 upgrade. From what I've read, once the APIM is replaced, there is a good chance that the parking assist, backup camera etc. may not function correctly, and that upgrading the PAM firmware should fix it. I was planning to be prepared, and upgrade the firmware while I wait for shipping.

As you asked for suggestions that is all I have! If you hold a Paid license you can roll your Log and dump.bin file into a .zip file and send to https://forscan.org/contactus.html as per instructions at this page https://forscan.org/contactus.html and see what they say about it!

I do have a paid license (1 year), and I will see what the team has to say. It sounds like I may be better off trying to source a newer PAM module and replace it. I guess I should wait until the Sync upgrade is complete, and see what is what before I take any further action

Thanks for your help!

So, I just got one of those Vgate vLinker FS USB adapters in today, when this programming function comes out of beta will it be able to update modules like the gem? also, what is the most recent beta with firmware programming still included?

edit just saw a new version was posted last month, I guess I missed its release.

wonko93 wrote: Sun Sep 26, 2021 1:01 am

As you asked for suggestions that is all I have! If you hold a Paid license you can roll your Log and dump.bin file into a .zip file and send to https://forscan.org/contactus.html as per instructions at this page https://forscan.org/contactus.html and see what they say about it!

I do have a paid license (1 year), and I will see what the team has to say.

FYI, I did send my debug info to the FORScan support team. They provided me with a test build, and it resolved the issue. I was able to successfully update the PAM firmware.

Wonderful support!

I have a 2011 Ford raptor 6.2 svt.
Had the (pos+) cable come lose on a wash board road.
Lost all power, restarted just fine with no knowledge of the cable. Drive mabie 30yrs and again, pop good realize the issue reconnected tight, restarted ran then went dead.
No restart possible, had a issue with wire harness melted fixed it, no start, checked all fuses relays ect, ran power probe to each of the bcm pcm and fuse boxes, no issues,
Only codes popped were down hilldecent , breaks, off-road mode not functioning,.
Reset all systems only code or warning was Starting system fault and would not turn...Found a burn spot on pcmecm board, found exact match pcm online same everything, connected it and no start only warning is starting sys fault. Bypassed the start relay with bcm awake and it turns over but no start or run,. Please help

changing the BCM requires your asbuilt data putting to it and calibration files , then pats reprogramming

wonko93 wrote: Tue Oct 12, 2021 12:36 am FYI, I did send my debug info to the FORScan support team. They provided me with a test build, and it resolved the issue. I was able to successfully update the PAM firmware.

Happy to say that after my Sync 2 - Sync 3 upgrade, my backup camera and parking assist are still working nicely!

Hello. How is the ELS27 St. Petersburg developer adapter friendly and how does it work on software updates?

Hi guys. Who used the VXdiag nano ford-mazda adapter? How is he at work. I diagnosed a couple of cars, everything seems to be fine, but I didn't check for firmware updates