VindictivePantz
Well-Known Member
- Joined
- Oct 7, 2022
- Threads
- 28
- Messages
- 434
- Reaction score
- 426
- Location
- Arlen, TX
- Vehicles
- 2021 Mustang MACH-E Premium AWD w/ Ext. Battery
- Thread starter
- #1
I think I am haunted by a software bug and curious if anyone else has seen similar behavior. (2021, Job 1)
TLDR; version: Departure times locally and via FordPass are not working, but they sometimes start but never finish, and the car charges or attempts to charge instead, and not sure which fuse might be best to clear out what I suspect is a faulty memory value condition somewhere in the system.
Per this thread, I was having annoying PaaK issues with a new phone and have them mostly sorted.
Description:
When setting departure times from the phone OR the car itself, they do not function. They functioned with the "old" phone and from the car before my phone switch, but either causally or coincidentally ceased functioning when I moved to a new phone (both Android.)
I thought it was just not working, but that would make it easier to understand what's going on. It sometimes acts like it's working, but it's not really.
Here is what I am able to consistently reproduce:
To reproduce:
1) Set a departure time from the phone OR car
2) Watch FordPass approximately 15-30 minutes before the targeted departure time (depending on ambient temperature)
3) FordPass will sometimes say "Preparing cabin for departure"; other times, it says nothing
4) After a few minutes, if it did say "Preparing cabin for departure", it stops saying it when it should very well be preparing, and will sometimes indicate that it's charging to its target charge even when I am outside my charge window
5) In either situation, I generally get a notification that the car has reached its target charge, despite the time of day (I charge to 80% in an 11PM to 6AM window; this all occurs outside that window)
Since I was relying solely on FordPass to tell me what's going on, I decided to watch the car's physical behavior a couple of days ago. It starts preparing the cabin (or sometimes I hear the battery warming) for a minute or two, but then it stops and starts a charge cycle and stops when it hits its target (sometimes.)
As the car is usually near 80%, the charge cycle is pretty short. In the cases where it's not close to 80%, I have had it try to get to its target, and in some cases, charge for a few minutes and stop.
I have had no issues with Target Charging.
From what I understand of the software architecture, departure times and status communication to/from FordPass go through Ford's servers and the car's TCU, but once a departure time is set, outside of notifications, everything should happen locally within the vehicle.
The fact that I can see the departure times in the car, and the fact that I've cleared them and set new ones from the car without having the phone involved and I still have an issue leads me to believe that it's not phone-related, but that there's some bug in the car itself.
Which fuse? I have performed multiple Sync and phone reboots, but I have NOT pulled a fuse yet (as I am not sure which ones make the most sense for this.) Since I suspect it's an in-car software bug, perhaps a fuse pull will clear some latent memory value condition in one of the modules?
The oddest thing about this is the attempted or actual charging that takes place after it decides to abort departure preparation.
?‍
TLDR; version: Departure times locally and via FordPass are not working, but they sometimes start but never finish, and the car charges or attempts to charge instead, and not sure which fuse might be best to clear out what I suspect is a faulty memory value condition somewhere in the system.
Per this thread, I was having annoying PaaK issues with a new phone and have them mostly sorted.
Description:
When setting departure times from the phone OR the car itself, they do not function. They functioned with the "old" phone and from the car before my phone switch, but either causally or coincidentally ceased functioning when I moved to a new phone (both Android.)
I thought it was just not working, but that would make it easier to understand what's going on. It sometimes acts like it's working, but it's not really.
Here is what I am able to consistently reproduce:
To reproduce:
1) Set a departure time from the phone OR car
2) Watch FordPass approximately 15-30 minutes before the targeted departure time (depending on ambient temperature)
3) FordPass will sometimes say "Preparing cabin for departure"; other times, it says nothing
4) After a few minutes, if it did say "Preparing cabin for departure", it stops saying it when it should very well be preparing, and will sometimes indicate that it's charging to its target charge even when I am outside my charge window
5) In either situation, I generally get a notification that the car has reached its target charge, despite the time of day (I charge to 80% in an 11PM to 6AM window; this all occurs outside that window)
Since I was relying solely on FordPass to tell me what's going on, I decided to watch the car's physical behavior a couple of days ago. It starts preparing the cabin (or sometimes I hear the battery warming) for a minute or two, but then it stops and starts a charge cycle and stops when it hits its target (sometimes.)
As the car is usually near 80%, the charge cycle is pretty short. In the cases where it's not close to 80%, I have had it try to get to its target, and in some cases, charge for a few minutes and stop.
I have had no issues with Target Charging.
From what I understand of the software architecture, departure times and status communication to/from FordPass go through Ford's servers and the car's TCU, but once a departure time is set, outside of notifications, everything should happen locally within the vehicle.
The fact that I can see the departure times in the car, and the fact that I've cleared them and set new ones from the car without having the phone involved and I still have an issue leads me to believe that it's not phone-related, but that there's some bug in the car itself.
Which fuse? I have performed multiple Sync and phone reboots, but I have NOT pulled a fuse yet (as I am not sure which ones make the most sense for this.) Since I suspect it's an in-car software bug, perhaps a fuse pull will clear some latent memory value condition in one of the modules?
The oddest thing about this is the attempted or actual charging that takes place after it decides to abort departure preparation.
?‍
Sponsored