cr08

Crossing fingers maybe we see something with the EV Driving data soon? It did originally have the wording about enabling the connected services in vehicle but now it just says there's no previous trip events to view. I did have a couple drives today but nothing recorded outside of the 'Journey' data. Seems like Ford may be finally getting on top of things. Excited to see all these functions start populating again. EDIT: And just as a reminder, this is on a 2013 that wasn't originally on the CSP, and DIY'd to boot. Really happy to see that it has basically been fully functioning to the extent that everyone else so far has had functionality show up, both in the 'supported' model years as well as the official dealer installed upgrades.

Scheduled Charge Times seem to work now. FordPass recognized my home location and I was able to set it up as a Home profile and configure accordingly and it's reflected as such in Sync. Switched the default profile back to Charge Now and that worked at a public charger earlier while my Home profile set up for Value Charge (in Sync) is now waiting to start. Small little glitch I did notice is I had set my charge times for 12am-8am weekdays and weekends. When I go back in to check, it has it split up with a 12am-7:55am and a 7:55-8am slot. Not a big deal since it will essentially do the same thing, but just thought it was yet another interesting FordPass glitch. ?

As has been well discussed previously on these: The noted fuse pull workaround should do the trick every time. The proper fix is to get the ACM updated with a current calibration. This has been documented in TSBs for other Ford models. If you're comfortable with using ForScan and have a license and good adapter, you can do the calibration update yourself easily and it's about 10-15 minutes of time to do.

Yeah. I had all those features start showing up today including having the little bar at the bottom showing an active charge session. Nothing yet in the EV driving data though. As far as the modem issue, I'd say wait and see what we can find out through ForScan once you get the new OBD adapter. We can provide more immediate confirmation and advice on the whole situation.

$2000 is insanely overkill. Even 4dTech costs less with their kits and they're generally considered expensive. Most people these days sell full plug and play and reprogrammed kits for around $500-$700 depending whether you get factory nav or not.

Something I think both @bookemdano and I forgot about and is likely the issue here: Stock non-Ford specific OBD adapters only speak with the HS-CAN bus in Ford vehicles. The TCU is on the I-CAN/MS-CAN bus. You can look for other cheap OBD adapters and look for ones that can do Ford MS-CAN. Some have physical switches to flip between HS and MS and ForScan will let you know when to do so when it needs to. If you don't mind bumping your budget a small bit, the OBDLink EX is a highly recommended adapter and will automatically switch between HS and MS as needed. They sometimes go on sale but I think the normal pricing is $59.99. That said, the OBDLink EX is overkill unless you plan to get into module firmware updates. The cheap adapters are more than enough for basic AsBuilt and diagnostic stuff.

Thanks for the extra info. So seems like POTENTIALLY something being enforced across all dealers and not an isolated incident. Makes me curious exactly what software issues they're concerned about and if it's just the missing features those of us here are already seeing and Ford wants to make sure everything is 100% for those going through the official process. If that's the case, maybe there's hope that they're actively getting this all sorted out now.

So far my EVSE power usage has been quiet. I had the spike from yesterday morning around 6AM with the Go Times I had set. Deleted those. Vehicle has been plugged in and sitting at a full charge since then and my power usage graph is relatively flat. There's small spikes of up to 30-50W or so that that seem to last for maybe half a minute. They seem to correlate to my manual app refreshes, but no longer seeing the full 1200w spikes as if the whole car woke up like what I noticed before. Not sure if the conditions just changed or if something Ford changed on their end. Just thought I'd add that small update.

This is definitely something I've been wanting to do and start playing with the various options in the vehicle some more. For me it will probably have to wait until summer starts so its warmer out and I'm out of busy season at work and can focus on this stuff more. One other feature I did add a few months back (and I believe I briefly mentioned it in this forum in another thread) is displaying the set cruise speed on the IPC which has been VERY handy. Hint: It's actually an option in the non-AsBuilt IPC configuration menu in ForScan so a piece of cake to find. I just can't remember off the top of my head what specific option it was. lol

Looking good on my Android phone this morning, no issues connectivity-wise. In fact, I got the charge complete notification which is the first time I've gotten that so far! No charge logs or anything I can find in the app just yet. I can also confirm the Departure Times worked as expected. Set for 6:30 this morning and somewhere around 5:30-5:45 it started doing stuff, my EVSE power usage started and held at the expected ~1200w til shortly after 6:30 and the HVAC blower was clearly going.

More details on the Go Times/Departure Times stuff after playing around with it: Added a few more times in FordPass and they passed over to Sync and this time it turned on Go Times in the vehicle. I'll let it go and see if it operates the way it should. Temperature translations: Cool: 65F Medium: 72F Warm: 85F

Virtually nothing when it comes to the TCU. At worst if some of the AsBuilt is configured incorrectly, the TCU just won't work. The rest of the car should (under 99.9% of cases, there could always be that 0.1%) remain functional and unharmed. As well, a misconfigured AsBuilt shouldn't brick the TCU. If it's misconfigured, just go back in and reconfigure it and try again. There's a reason most of us here have been experimenting with these seemingly blindly. For the most part there's no harm in doing so. That said, ALWAYS back up your AsBuilt programming to start with. ForScan provides a simple 'Save All' button to save this to file somewhere and you can go back and reload it later to restore it back to the way it was.

Another fun little thing I discovered: Although I work from home now so have no need for the Departure Times/Go Times, I did set it up just for fun through the app. This started with no Go Times information set in the car. It appears that it added the data into Sync as I was able to confirm everything showed, but Go Times were still turned off despite the Departure Times toggled on in FordPass. Should have went off at 6AM this morning but I can confirm nothing happened at that time. Also, unfortunately, FordPass doesn't offer specific temps and just has Cool/Medium/Warm/Off for the cabin temp options. 'Cool' seems to set it to 65F in Sync per my own findings. I'll have a play with the others.

One additional piece of info discovered regarding the TCU AsBuilt stuff, specifically those 754-03-xx blocks: 754-03-06: ****-xxxx-xxxx This is unique from the others in that it specifies some form of HEV/Hybrid data update/polling frequency. It appears to be in either seconds or minutes? The default that others have seen with their official upgrades (per their AsBuilt's already documented in this thread) is 0078 which is 120 (sec/mins). 7D7D would put this up to like 31000 or so. Also a new AsBuilt DB for these H TCU's has been posted over on the CyanLabs site: TCU-H Database - CyanLabs

Awesome to hear. Glad it was something simple. ?

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.

Interesting! Strange thing is that I've been messing with these for a while and they haven't made a difference. I have had the sensor 'blocks' on the rear view camera since the beginning without issue. Just no overhead car display. In addition to these, I have had the following set: 7D0-02-02: xxxx-1xxx-xxxx 7D0-04-02 xx03-xx (I did have this set to 08 at one point while trying to sort this out, though this will be different for yours only having the rear sensors) Similarly in the BCM I have this set, but it will obviously vary with your feature set: I've refreshed everything so will do a few drive cycles and see what happens.

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.

Very strange. Communication errors and some lighting circuit errors. A few things I'd try: Try clearing the DTCs and see what returns. Maybe for good measure try disconnecting and reconnecting the battery and see what changes. Go back in and double check the wiring and harnesses where you were working (the harness under the driver side rear door may be a very good one to check) and verify no wires are pinched or cut. What did you do with the pulled wires on the rear lamp? If you left them as is or taped them off, I'd see if you can try to repair it. It could potentially be freaking out the BCM and causing erroneous codes. Last ditch effort: Temporarily return the old G TCU and see what changes there. If things return to normal, there may be some fault or incorrect programming on the new TCU? Just a hunch here. If reinstalling the old one works, I'd reach back out to flvpmods since they would have done all the setup and programming work ahead of time for you for the new TCU. Also, during any of these steps, it may be worth clearing out any visible DTCs and re-reading them. Various modules can be unhappy when messing around and throw DTCs that can stick around even after the initial cause is resolved. Those that are still active will, of course, stick around after. I may recommend doing the DTC read step a couple times to make sure you pick up everything. I know the antenna circuit code on the TCU on mine if I clear DTCs and re-read, it doesn't pop up immediately but maybe 10-15 seconds later if I re-read it shows. Just an FYI.

Only gotcha with that and why I have avoided inquiring people with other Ford models is with the C-Max being Focus based, it uses a 'Central Configuration' system vs AsBuilt modifications for some modules. Basically the BCM has a Central Configuration page to adjust various parameters and it disseminates these to other modules in the vehicle that need them. My best guess is this is why my PAM doesn't have an AsBuilt config which seems like it may be key to getting everything properly functioning with the Sync 3 retrofit. To the best of my knowledge, none of this applies to the Fusion and you guys can just modify the PAM AsBuilt normally and be good to go. Hence why I'm reaching out to 2016+ C-Max owners here. Those came from the factory with Sync 3 and will give me a much better idea how theirs are configured in this area.

A bit off topic, but this thread seemed apt to ask this considering a number of you have access and are comfortable with using ForScan. Those of you who have 2016+ models, especially with the full front/rear parking sensor and parallel park assist features equipped, I wonder if I could bother you to post the PAM (Parking Aid Module) part #'s as well as calibration levels? Also interested if ForScan provides an AsBuilt config option for the PAM for you. I've been digging back into the parking stuff with the Sync 3 retrofit on my '13. One feature I've been trying to add is the 'overhead sensor' display (example image below) but potentially a roadblock I may be dealing with is ForScan is not providing an option to modify the PAM AsBuilt which may have options that need to be changed. So far the parallel parking feature seems to work, although it's very rare for me to have the opportunity to use it here. I've only ever been able to mess with it once since my retrofit.

I'll have to pay closer attention to mine and see if that's the same. I HAVE been fiddling with the app and refreshing it a lot and that also seems to trigger the vehicle to wake up and start pulling power briefly from the EVSE. Here's my power usage graph since Mar 27th: I'll try not to mess with the app and see what shows up going forward. EDIT: Probably a better link since the forum likes resizing these: https://imgur.com/zrHPqXR

The only issue I ran into was the actual side panel (the final piece of the puzzle to remove) wouldn't come out easily. It is wedged under a lip of metal on the top of the battery casing in the back corner right behind the seat. I had to essentially 'rock out' the panel from the top. This is different than what the WSM suggests sliding it straight out. Other than that, the rest of the process was straightforward. Once I was able to get the side panel off, I basically followed the same exact instructions laid out in the CSP for the TCU installation including placement, use of velcro strips, etc.. Since the DIY modules are essentially identical to the official ones, that process is no different. EDIT: As an FYI for the thread as a whole, I'll work on updating and cleaning up the initial post of the thread with the new and relevant info we have so far. Will try and get this done in the next day or two.

TL;DR: Despite some old threads either here or on the defunct Energi forum and some other communities saying Global Close wouldn't be an option, it looks like it actually is on our vehicles! Just as an explainer what 'Global Open' and 'Global Close' are for those unaware: This allows rolling your windows down and back up via the keyfob outside the vehicle. The process is as simple as pressing the lock/unlock button once and then immediately press and hold it for about 3-5 seconds and the windows will roll up or down (unlock for down, lock for up). Unlike the Global Open function, Global Close only requires pressing and holding the lock button once to engage. Global Open will continue to require pressing the unlock button once and then pressing and holding it again to operate. At any time you can press lock or unlock to stop the windows while they are opening/closing. NOTE: It appears newer models years like the 2017 and newer already have this enabled and specifically detail it in the owners manual. Before changing this willy nilly, confirm yours does not already have this enabled using the fob operation noted above. There was a thread that popped up on the CyanLabs forum from a Fiesta owner who was trying to tackle enabling Global Close and the always helpful F150chief pointed out a thread for Kuga's (European Escape, essentially the same platform as the C-Max) on doing a relearn process on the auto-up/down functions on the windows to try and get it working. Not exactly sure what specific step finally solved it, but here's the process: WARNING! You are making changes to the Body Control Module. This module is crucial to vehicle operation and manages functions like interior and exterior lighting as well as ignition operation. If you are not comfortable messing with this and/or ForScan, please don't. Following these instructions is at your own risk and I am not responsible for any damages or malfunctions incurred as a result. As always with changes like these, please back up your AsBuilt/module configurations before making changes! Also follow all notes and warnings given to you by ForScan and their own resources. In ForScan, go into the module configuration screen and choose the 'Central Configuration' (NOT AsBuilt!) for the BdyCM module. Locate the Global Open/Global Close configuration entry and change it to the 'Global open/close doors enabled (3 seconds)' option. I think this is listed as 02? Write this to the module. Follow all directions ForScan gives you in this process. For completeness sake, I relearned the auto-up/down functions on all four windows. This is as simple as rolling a window both down AND up completely and holding the switch in those positions for about 5 seconds to learn the extent of travel. NOTE: If the one touch up/down on your windows does not work immediately, it will impact the Global Open/Close functionality. Messing with some modules like the BdyCM/BCM can do this and the relearn process noted here will need to be done. Once the one touch up/down works, you should be fine. And that was it! I can now confirm the windows now can also roll up via the keyfob. I'll try and get screenshots from the options in ForScan for later to add here. Quick short video with proof of functionality: C-Max Global Close feature enabled and functional (video proof) - YouTube

Regarding the core charge bit, I'd definitely push back on your dealer if that comes to pass since Ford is the one delaying things. That said, not too surprised with the quirks and bugs and how haphazard things have been on the official end of things. I'm curious what model year C-Max you have though? I know in some later bulletins they had started holding off for some model years due to compatibility issues.