cr08

You likely have climate settings configured for remote start in the vehicle. On the IPC/gauge cluster, the left side screen under Vehicle Settings there should be a menu for Remote Start and it has various options. Applies to both remote start via the fob and the app. For the settings with Auto or 'Last Setting', Auto will automatically run the HVAC at desired internal automatic settings, regardless of what you previously had your HVAC controls set to, even if they were off. I believe it aims for a set temp of 72f and whatever the preferred vent configuration would be (usually foot vents for heat, face for A/C, front defrost kicks in below freezing out). These cannot be changed. The settings it aims for on Auto mode are hardcoded. 'Last Setting' is obvious and will simply follow what you had the HVAC controls set to previously. As far as firmware updates are concerned, I think the general consensus is to not do them unless you have a specific thing you are trying to fix that has been documented as needing an update. Especially on the more mission critical modules like the PCM, BdyCM/BCM, IPC, and the hybrid related modules. A failed update on any of those will make the car entirely inoperable. Less critical modules like the TCU/Modem we've been dealing with here, APIM, ACM, and others will just cause an inconvenience but the car will still -usually- be drivable.

You might want to try having ForScan re-scan the modules without using a saved profile if you haven't already. If that doesn't do it, you may want to see if you can track down the latest beta build. Mine still gives me the firmware update option after this. ForScan for me wasn't even aware that UN was available or a current version. It still assumes UM is the latest available. In reality I don't think it cares and should not be hiding the firmware update function even if you are current because these modules can usually be downgraded without issue.

No changes that I can tell so far with two mixed EV+Gas trips this evening. Everything that has been functioning is still ok. Nothing new added. Still waiting for the EV Trip Data to populate. I've yet to have that show so far in all of this. That said, the update was successful and is functioning so there is that. Go Times and Value Charging are still there and functional. EDIT: One thing I guess I should note is the secret little JSON aggregate on Ford's site that has all the FordPass data mysteriously is missing like half of the data, though I believe this occurred right before I initiated the calibration update. Still missing a chunk after the fact. I'll document the process for that below for those interested in checking it out: 1) Access Ford Owner Support from a Chromium based browser for best results (Edge works here as an example). 2) Log in and once the page loads, open the developer console. F12 should do the trick here. 3) In the developer console, choose the Network tab and in the filter box, enter 'countrycode' 4) In the listing that has been pared down with that filter, you should have two 'status?countryCode=us&vin=....' entries. One will be 0B in size, the other will probably be a couple KB. This second one is the one we want. Select it and a bunch of data should show.

DSFM File Download (dealerconnection.com) Basically lets you download calibration files from Ford as long as you know what filenames you're looking for. In this case I just incremented it from UM to UN on a whim. Nothing else past that up through UZ. Curiously enough the timestamp on the UM calibration was dated for 8/27/2021, well before a lot of this stuff started rolling out to the public. UN is dated 3/9/22 so definitely very recent. Unfortunately no clue what changes there are. EDIT: Looks like there's a matching strategy file out there as well. Same timestamp. I'll definitely be giving this a go sometime this weekend and will report back. Calibration: HJ5T-14G139-UN (Dated 3/9/22) Strategy: HJ5T-14G144-UP (Dated 3/9/22)

If you don't mind being a guinea pig, maybe go through with it and see what they end up doing? I'd be interested if they have a new calibration update. Did they by any chance give an idea how long this update would take? Checking the DSFM site, there does appear to be a new UN calibration level out there. HJ5T-14G139-UN. I may give a go at doing this update on mine either tomorrow or Sunday.

Hard to say the cause without pulling codes. It could be any number of things especially being a Hybrid/EV as it has a lot of various checks ensuring it's safe to connect the traction battery and make the car drivable. If the check engine light is on, it'll have something stored to help narrow it down. If you can get these (Either from your dealer, Autozone/Auto parts store, or your own scantool/OBD tool), it'll greatly help in diagnosing the issue. Personal preference is a cheap Bluetooth OBD adapter and ForScan (either the mobile app or Windows PC app). ForScan can pull 'hidden' Ford specific codes that generic scan tools wont, though if the CEL is on there will be something there that a generic scan tool can provide but it may not be detailed.

This. Mine was about $200 out the door at my dealer. Around $130 for the battery itself, the rest was labor and other fees/taxes. Won't find it too much cheaper at the normal auto parts stores for the battery alone.

Something must have reset your settings in the IPC. I believe if you drill down in the Vehicle settings on the left screen there, there's an option somewhere to show Gas+Battery mileage which will return the MPGe numbers.

Something I've noticed happening with mine recently. First is the fuel level updates seem to be delayed by a tip or two. This has been consistent over the past week or two. Multiple refreshes in the app do nothing. Only seems to update on susequent trips. Battery/EV range and other data updates fine, however. Nothing new to speak of otherwise. Interesting tidbit I did fine and not sure if this was how things functioned with the old 3G modem: If the vehicle is already locked and you hit the lock button in FordPass, the lights don't flash. Only if the vehicle is unlocked and you lock it, do the lights flash. I need to test again and see if the locks actually audibly trigger or not. I was inside the house when I saw this happen last time. OT note since it's been brought up here, I did start a separate thread with a brand new spreadsheet covering possible software modifications for the C-Max: EDIT: Confirmed if already locked and if you hit the lock button in FordPass, the car makes no indication visibly or audibly that another lock attempt was made. The locks do not 'click'. So probably a good bit of useful info considering FordPass doesn't give lock/door/window statuses at this time.

I know a few member here have been jonesing for this. I started putting together a spreadsheet specifically tailored towards the C-Max. Short version: This will cover potential tweaks or modifications that can be done entirely in software through the use of ForScan (primarily, other tools like UCDS optional). These will either add new functionality or change existing functionality. All information is posted for use at your own risk. The linked spreadsheet has plenty of warnings and links to information on learning how to use ForScan. If you aren't familiar with using it, please read everything thoroughlly. I will not be responsible for any damage caused trying to implement these. While basic AsBuilt modifications are USUALLY harmless and can easily be reversed, it's not a guarantee. Another note that is in the document but I will also reiterate here: BACKUP! BACKUP! BACKUP! ForScan provides the option to save your existing module configurations/AsBuilt's that you can revert to or reference later. Ford does provide a page to pull your factory AsBuilt but it only has information for a handful of modules, not all! https://docs.google.com/spreadsheets/d/1Tir9hvuLDii0yonGJR3FoyfKzNODT_PZCPZH6Ph9dz8/edit?usp=sharing I'm leaving the document read only. If anyone has any additions to suggest, feel free to post here or PM me. More documentation the better. Document has been switched to comments allowed. I am unable to actively put work/research into this but will happily take suggestions to add. If anyone wishes to take over the document, let me know.

Glad you managed to get it all sorted! As far as these missing items, it looks like this is one of a small handful of things missing for everyone still I'm assuming. I know they don't show on mine either. The actual charging log stuff has limited data still. Charging network may also never show for us and is probably there for newer EVs like the Mach E and Lightning where they can communicate with public chargers and directly identify them. But this is just an educated guess on my part. We'll have to see as Ford continues to work on getting features working in FordPass.

You did it incorrectly then if the ICE started. You want it in 'Accessory' mode. ie: The green 'Ready to Drive' light should not be on. For the keyed ignition it should be the first position from Off/lock.

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.