Leaderboard

Awesome! Will definitely work on getting the parking overlay enabled. I haven't done a whole lot of asbuilt tweaks, but the two that have been most useful to me: Adding global close (automatically closing all windows by holding the lock button on the fob for 5 seconds). Of course we already had global open from the factory, but this is a lot more useful as it avoids the need to get back in and start the car just to roll up a window that was left down. Disabling the SUPER-annoying double honk when trying to exit the car with the key while it's running. I understand why it's good to notify the driver in a situation like that, but Ford should have used a beep or something more subtle--honking the horn is obnoxious. I've felt the need to apologize numerous times to people that I wasn't intending to honk at them. Pretty much the only other change I made recently was removing Sirius from the sources list. I don't subscribe and never intend to, so it's nice to not have to see it when cycling through audio sources. It would be great to get a spreadsheet of *working* asbuilt tweaks for the C-max. There are some very comprehensive ones out there for other Ford models but a lot of the tweaks won't work for our cars. Edit: Got the parking overlay working per the asbuilt changes posted by @cr08 and @David_Tucker4. Just experimented pulling into and back out of my garage and seems to work great. Cool! Edit 2: After some weirdness last week (only successfully synced 1 out of 10+ times I tried), I was able to sync two charging locations to the car from FordPass this morning with zero issues.

Holy crap... That did it. That C1MCA threw me given I know this is a CGEA vehicle. Thanks for that! Will definitely be adding this to my notes. I'm still planning on trying to get a rundown of features that can be enabled on these vehicles with simple software tweaks such as this one.

Thanks to you and cr08, most of the issues are resolved. I did everything you all suggested, and spent a few hours going over the car looking for anything I might have screwed up. Disconnected battery even. In the end it was a fuse. So I reconnected the new TCU, and just going to leave the car disassembled for a while until I start putting it back together again. Then I will tackle these last few things few DTCs that are APIM and TCU related. Thanks again!

Yeah, asbuilt code is still pretty mysterious to me. Always interesting to learn from folks who know a lot more about how it all fits together. @oldbeyondmeasure likely already has 7D for all those bits, since I copied his asbuilt in total when programming mine (figuring that his is configured exactly how Ford intended for the C-Max). Still, this is good info to have posted here for future reference, as I'm sure we'll have other folks working on DIY TCU swaps in the future. Great job summarizing it!

This is 100% where mine is at as well. I just went through and compared notes on what I see with my app vs what you mentioned here and it's all identical. The assumption so far from multiple people is it is all on Ford's end and they still need to get FordPass fully functioning with these new features for us ( @bookemdano and I had a brief discussion on this stuff with F150chief over on the CyanLabs boards and that seems to be his thoughts as well. Did get some new and useful info on that front which I'll post below.). So it's largely a waiting game. Once again thanks goes out to F150chief over at CyanLabs for providing some more useful knowledge concerning these TCU's and the AsBuilt configs. You can read the whole thread as it is currently here: TCU HJ5T Asbuilt Discussion - Ford / AsBuilt Configuration - CyanLabs Official Community We had originally assumed the 754-03-xx blocks were just garbage or storage bits. But apparently these are additional configuration options to tell the TCU what various bits of data to pull from the vehicle and send back to Ford. 7D indicates the data should be pulled and sent back. 7C ignores that bit of data. Unfortunately there's no insight to what each individual bit corresponds to. Based on the discussion, it seems like it is harmless just to set everything to 7D to enable ALL THE THINGS and send it to Ford. It is still then up to them to populate and display this data on their end in the app. I have went ahead on mine and did just this and enabled all those bits. No new data just yet but as always I'll keep you posted if anything changes on this front. Just as a quick FYI on the AsBuilt stuff that I've briefly mentioned here previously: With ForScan, the last two bits in each individual block are checksum bits. So in the case of these changes to the 754-03-xx blocks, they won't show or even be able to be set to 7D. You can enter anything in these bits and ForScan will just recalculate what should be there when you go to write it to the module.