Testing firmware update function for Ford modules

[Click4]

There is a link to a copy of 2.4 beta at the link below. Make sure you read the warnings in the second post if you are planning on updating your APIM. Sound like a right pain in the ****

https://www.f150forum.com/f118/upgrade- ... ns-458828/

Thank you for posting this!

Can’t say how much I appreciated this link being posted as it got me out of a spot of bother.

Needed to update the firmware on a powershift transmission control module, because I replaced a clutch on one, new design had a new calibration... my version of IDS as it’s not up to date would not flash a calibration past 2015 even though newer one was available.

The consequence was that the first released calibration for the new design clutch while operating fine... it was too cautious with the power delivery and pulling away from a standing start felt restricted.

I tried to flash the newest 2017 tcm calibration with focccus instead, but my elm327 adaptor was not up to the task and it kept failing the upload at varying percentages and IDS would not recognise the module part number to flash the 2015 calibration again... kept asking for asbuilt file, downloaded as built file and it complained it was corrupt.

So essentially vehicle was immobilised.

Then I came across your link you posted, and was able to download the test version, and install the latest tcm firmware using my VCM II with forscan, it loaded the firmware quickly and first time without any issues. Now car starts and drives again perfectly fine.

So thank you for sharing this!

And despite my limited testing and feedback, it flashed the TCM perfectly first time no issues.

So also thank you to forscan team for making this test release.

[xd-data-ii]

If accepting new testers, I would be grateful to be accepted in to the program.
Bought an OBDLINK EX Cable and am keen to get more advanced with Forscan on my RS.

[jordancrane]

Hi,

I am looking into testing the beta version if available. I did a sync 2 to sync 3 upgrade on my 2013 C-Max Energi (fully loaded) this past Saturday and everything worked out great with Forscan. I am curious about what is possible with the PAM firmware updates and the beta version of Forscan. I just bought the OBDLink EX and it works much better than the previous adapter I had for the install.

Let me know if possible (I know this is at my own risk).

Jordan

[FORScan]

Version 2.4.0 has serious issues, so we have even stopped testing on it. We currently work on version 2.4.1 that will most likely be publicly available. We would recommend to wait until v2.4.1 release, unless it is a matter of urgency for you. But if you want to use the 2.4.0, you can request support and we will send a link to you.

Also please note firmware update function requires good quiality fast wired adapter.

[jordancrane]

I was able to find a link to 2.40 and played around with it a little (not attached to the car) and I can see there might be some instabilities. Right now I am just exploring options and learning how things work etc so I can wait until the public release is available (hopefully within a couple months).

I ordered the adapter recommended on this site, OBDLink EX (USB). I previously had an ELM327 with the switch on it. Should I get something different than the OBDLink EX if the eventual goal is a PAM firmware update?

Thanks for your time.

[Dragonheart]

Version 2.4.0 has serious issues, so we have even stopped testing on it. We currently work on version 2.4.1 that will most likely be publicly available. We would recommend to wait until v2.4.1 release, unless it is a matter of urgency for you. But if you want to use the 2.4.0, you can request support and we will send a link to you.

Also please note firmware update function requires good quiality fast wired adapter.

1. Are there any estimates on 2.4.1 release? And will it eventually merge the 2.3 and 2.4 branches into one with all latest updates + firmware flashing support?
2. What is the kind of issues with 2.4.0 you've mentioned? I was going to try to update every single module in Mustang 2015 Ecoboost, started with SODR/SODL modules and I'm not sure if it's due to the flashing issues, but I was not able to enable/disable audio - noise was coming out of speakers even after turning off the ignition and coming the car (central display, lighting, etc. were off). After multiple starts of car suddently audio started working normally. May it somehow be related to these issues? After flashing I resetted all errors just in case and reprogrammed module configuration even though I didn't have the U2100 error.
3. Main question: if I flash the PCM on mustang 2015 - will I have to reprogram the keys? I only have 1 key, so I won't be able to program it back.

Thanks!

[Lilrascal81]

Is it possible yet to get 2.4 to update apim yet?

[2B-4G10]

it is. but i almost bricked a module while updating with 2.4, the support team thankfully helped me out, but they advised me to wait for 2.4.1 as the current version is way too buggy.

i'd recommend waiting TBH.

[ddg71]

sent to me pm, please

[mschumiv]

it is. but i almost bricked a module while updating with 2.4, the support team thankfully helped me out, but they advised me to wait for 2.4.1 as the current version is way too buggy.

i'd recommend waiting TBH.

You can say that again.
I stopped testing till 2.4.1.
People should stop from requesting a download link, as version 2.4.1. could be made publicly available when released.