12/17 Updates Released

[Kevin P]

That is worrisome. More waiting, I suppose. One of us may have to volunteer to take our GT to the dealer . Not it.

Sponsored

 

[breeves002]

Sam, I noticed that when my Paak completely disappeared, what appeared to bring it back was running RFA initialization, not configuration as I originally thought. I think I remember the three separate routines for some or all modules, regular update, configuration, and initialization. Is Initialization used mostly after a physical module replacement? Also, how much is FDRS reading our configuration (or similar) before operations, vs. looking up what our configuration should be based on our VIN?

Yes I did PMI (initialization) on the ABS and it flashed an incompatible configuration causing codes for incompatible configuration and ABS light enabled with various other systems inoperative. PMI is designed to be used when replacing a module. For some modules you're supposed to run PMI, it pulls data from the installed module, then you replace the module and finish the PMI.

I used FORScan and flashed the factory as built and it was incompatible (same thing FDRS forced onto the module). The module reverted to all 0's in the as built.

I used FORScan and put benk016's as built in and changed the vin to my vin (760-01-02 to 01-03). It worked. I then found out that the incompatible configuration was the very last block. One letter made it compatible vs. not.

So the as built is my factory as built except one change because it appears to not be compatible with the KE calibration but the other as built that Ford shows as correct factory is compatible with the ME calibration which was put on when we did the ABS update.

I'm pretty much at a loss now honestly. I'm going to start looking at other GTPE ABS firmware and as built with BC and see if I can spot any differences.

@louibluey or @DevSecOps if you want the KE file to try stuff for yourself feel free to ask I'll send it.

 

[breeves002]

Well. After hours of trying to figure this out.... I have blue cruise and lane centering back!

We were looking in the wrong place. It appears the ABS update was likely not the issue it was the IPC update. This isn't confirmed - it could be a compounding issue. However I cannot get the ABS module to flash again so I can't update it to confirm.

My steps to solve problem:
1. FORScan reflash of ABS to -KE strategy or calibration or whatever the last one is called.
2. In FORScan flash factory abs built except changing the VERY LAST block to 0Axx instead of 0Cxx. 0Cxx which is my factory as built config made the module report a configuration incompatibility with the -KE firmware file. FDRS would force flash this but set the DTC.
3. IPC as built in FORScan - load factory AsBuilt. This had several changes over what FDRS loaded into the module. It appears FDRS is loading a different as built into the IPC on the configuration than what you should have. Fords database is correct - FDRS just loads something entirely different. No idea why.

I may not have to have changed the ABS to -KE and do the custom as built. I haven't confirmed this since I can't with FORScan/the abs module not wanting me to flash it. @DevSecOps or @louibluey maybe you can try making the IPC as built changes only and see if both LC an BC come back before doing the KE firmware change?

I have attached my as built as it is in Fords database along with what FDRS flashed so you can compare.

FYI this is great to compare as built files: http://www.compulsivecode.com/Project_AsBuiltCompare.aspx

If the problem is only the IPC as built flashed by FDRS...Ford WTF. Why is it flashing something other than the As Built for the VIN in the database?!?! What is it downloading?!

 

[DevSecOps]

I will attempt factory IPC as built (alone) in a few hours and report back.

If it doesn't work I'll see you in a couple days ?

Edit: Because FORScan is stupid, I had to order a different adapter. Will update tomorrow when it arrives.

 

[breeves002]

I will attempt factory IPC as built (alone) in a few hours and report back.

You can tell if you get LC back at least by just turning on adaptive cruise. You should see the little steering wheel icon appear on the lane assist icon in the bottom of the IPC. You probably know this but a reminder

 

[louibluey]

Well. After hours of trying to figure this out.... I have blue cruise and lane centering back!

We were looking in the wrong place. It appears the ABS update was likely not the issue it was the IPC update. This isn't confirmed - it could be a compounding issue. However I cannot get the ABS module to flash again so I can't update it to confirm.

My steps to solve problem:
1. FORScan reflash of ABS to -KE strategy or calibration or whatever the last one is called.
2. In FORScan flash factory abs built except changing the VERY LAST block to 0Axx instead of 0Cxx. 0Cxx which is my factory as built config made the module report a configuration incompatibility with the -KE firmware file. FDRS would force flash this but set the DTC.
3. IPC as built in FORScan - load factory AsBuilt. This had several changes over what FDRS loaded into the module. It appears FDRS is loading a different as built into the IPC on the configuration than what you should have. Fords database is correct - FDRS just loads something entirely different. No idea why.

I may not have to have changed the ABS to -KE and do the custom as built. I haven't confirmed this since I can't with FORScan/the abs module not wanting me to flash it. @DevSecOps or @louibluey maybe you can try making the IPC as built changes only and see if both LC an BC come back before doing the KE firmware change?

I have attached my as built as it is in Fords database along with what FDRS flashed so you can compare.

FYI this is great to compare as built files: http://www.compulsivecode.com/Project_AsBuiltCompare.aspx

If the problem is only the IPC as built flashed by FDRS...Ford WTF. Why is it flashing something other than the As Built for the VIN in the database?!?! What is it downloading?!

I am still on a Job 1, FE, do you think it might enable/turn on BC? I guess if my FE does not like it, I should be able to just flash my original IPC file?

 

[breeves002]

I am still on a Job 1, FE, do you think it might enable/turn on BC? I guess if my FE does not like it, I should be able to just flash my original IPC file?

I believe you could likely get BC to work by changing the firmware and as built to a BC car. You will need all the new firmware including IPMA…but honestly I would just wait. It’s a lot of work!

 

[DevSecOps]

Well. After hours of trying to figure this out.... I have blue cruise and lane centering back!

We were looking in the wrong place. It appears the ABS update was likely not the issue it was the IPC update. This isn't confirmed - it could be a compounding issue. However I cannot get the ABS module to flash again so I can't update it to confirm.

My steps to solve problem:
1. FORScan reflash of ABS to -KE strategy or calibration or whatever the last one is called.
2. In FORScan flash factory abs built except changing the VERY LAST block to 0Axx instead of 0Cxx. 0Cxx which is my factory as built config made the module report a configuration incompatibility with the -KE firmware file. FDRS would force flash this but set the DTC.
3. IPC as built in FORScan - load factory AsBuilt. This had several changes over what FDRS loaded into the module. It appears FDRS is loading a different as built into the IPC on the configuration than what you should have. Fords database is correct - FDRS just loads something entirely different. No idea why.

I may not have to have changed the ABS to -KE and do the custom as built. I haven't confirmed this since I can't with FORScan/the abs module not wanting me to flash it. @DevSecOps or @louibluey maybe you can try making the IPC as built changes only and see if both LC an BC come back before doing the KE firmware change?

I have attached my as built as it is in Fords database along with what FDRS flashed so you can compare.

FYI this is great to compare as built files: http://www.compulsivecode.com/Project_AsBuiltCompare.aspx

If the problem is only the IPC as built flashed by FDRS...Ford WTF. Why is it flashing something other than the As Built for the VIN in the database?!?! What is it downloading?!

Flashing the As Built file you provided for IPC does resolve the BC issue on its own.

Thanks again to everyone who helped diagnose this issue. Behind the scenes there were a few people working on this, many thanks to them as well.

 

[breeves002]

Flashing the As Built file you provided for IPC does resolve the BC issue on its own.

Thanks again to everyone who helped diagnose those issue. Behind the scenes there were a few people working on this, many thanks to them as well.

Awesome glad it was just the IPC as built. Ford WTF. How can you have your own diagnostic tool flash a different as built than your public database has for the vin?!?! AND have it break the car!

I'm not going to bother updating my ABS again. My car works fine I'll wait for official updates to release to touch anything else.

I should have realized this earlier when I noticed the snowflake icon for low temp went away but it never clicked until Kevin P gave me the idea to look into the IPC when he gave me more information on what happened with his car.

Either way glad it is fixed and we can all enjoy BC again. To those reading...be warned about doing your own updates. Sometimes being on the bleeding edge means things break - even if they shouldn't.

Sponsored