-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Firmware 5.12
- Thread starter Alfafoxtrot1
- Start date
I didn't know that. The range is still plenty for me but not a good feeling when the range shows a decrease after all these months. Guess it could be worse and be in the mid-120s like before
Using visible Tesla it does the charge percent. When they fixed the vampire drain they dropped or max charge.
The change from 72% to 66% was because the formula for percentage calculation was changed. Amount of reserve below 0 was also reportedly modified at that time. This time, Tesla altered the algorithm again, and the % charge limit for 40s bumped up to 68% (as of my logs), but this was not enough to match the 5.11 range estimate.
We had the same issue. 3 reboots needed since the update 7 days ago. The sceen flashing was impressive, the car has not been used for more than a day and the flashing light in the car created by the screen going to with and black got my attention. Rebooted both screens. Next morning the center console had to be rebooted again...
Slacker goes catatonic
Hmmm, this could be an issue with 5.12 or perhaps predating it. Not sure. I got 5.12 (.26) about a week earlier.
We did a road trip last weekend to the Methow Valley in the North Cascades in Washington. With the chargers that PI-NCW put in, it is a really easy EV road trip. We went through the mountains and had no cell service for about an hour. Slacker stopped work as expected. We got the message "slacker needs connectivity" (or some such). But when we got back to AT&Ts version of civilization, slacker still didn't work. No error messages, no buffering circle thingy, just nothing. Tune In and maps worked ok so we had connectivity. Rebooting the console (multiple times) didn't help. I've been out of cell service range before and haven't seen this problem so it could well be new in 5.12.
I called Tesla and they gave me a sequence that restored slacker. Basically the voodoo is: log out of slacker, reboot the console, factory restore slacker settings and then log back in. That worked and we had slacker once again. For the first time in a long while, I was actually glad to have slacker...
Hmmm, this could be an issue with 5.12 or perhaps predating it. Not sure. I got 5.12 (.26) about a week earlier.
We did a road trip last weekend to the Methow Valley in the North Cascades in Washington. With the chargers that PI-NCW put in, it is a really easy EV road trip. We went through the mountains and had no cell service for about an hour. Slacker stopped work as expected. We got the message "slacker needs connectivity" (or some such). But when we got back to AT&Ts version of civilization, slacker still didn't work. No error messages, no buffering circle thingy, just nothing. Tune In and maps worked ok so we had connectivity. Rebooting the console (multiple times) didn't help. I've been out of cell service range before and haven't seen this problem so it could well be new in 5.12.
I called Tesla and they gave me a sequence that restored slacker. Basically the voodoo is: log out of slacker, reboot the console, factory restore slacker settings and then log back in. That worked and we had slacker once again. For the first time in a long while, I was actually glad to have slacker...
Updated today at my overdue annual service to 1.64.38. I don't know what it does differently as its my first 5.12 build.
Chuck Lusin
Chuck P10548 Jenny P10614
I got the 5.12 (1.64.38) update. I was having a problem with one of the three battery coolant pumps, even have the new part on order, but since the new update the error cleared. I'll see if the error comes back after drive to work.
I was told by service that the coolant pump issue would be solved with a forthcoming software update.
Chuck Lusin
Chuck P10548 Jenny P10614
My coolant pump threw an error a few weeks ago and they have been postponing service until 6.0 rolls out, saying that the fix was in 6.0 and due by 9/1. It looks like they also may have rolled that fix into 5.13. The issue is with the sensitivity of the pump's sensors, not its function. In the meantime, service had engineering clear my error remotely and it hasn't reappeared since.
Many in Arizona are having this issue due to the heat. The coolant pumps are erroneously reporting errors to the mothership.
NigelM
Recovering Member
I'm to what sort of daytime temps your car is showing right now? We are experiencing some record highs here and I parked my Roadster in the sun for an hour yesterday - got back in and it showed 122F on the center screen. Model S has shown exterior temps up to 109F but fortunately no error messages on coolant pumps. (We're on 5.12).
Chuck Lusin
Chuck P10548 Jenny P10614
I also have a problem with my passenger window, when it is 100 and over, it takes 5 or more times to go back up. Costa Mesa looked at it and it always works there (the weather is always perfect there), I'm thinking of taking it to Cathedral City SC, and let it bake for a bit in the sun, so I can replicate the problem.
I was updated to v5.12 this Monday at the service center and have noticed a change not captured on the forum's change log. I was previously on 5.9, so this change may have taken effect with 5.10 or 5.11. Previously when I engaged the AC via the remote app, the car switched off of recycle and onto outside air (I always use recycle here in LA). So I would always have to switch back to recycle upon getting into the vehicle. With 5.12, the car remembers my air recycle setting.
NigelM
Recovering Member
First odd behaviors here (been on 5.12 for 1 week); my wife called as the center console is blank, I'll do a reboot when she gets home (she prefers not to do it while she's driving).
I think I've only rebooted twice in almost two years, I wonder why Tesla is still installing buggy FW v5.12?
I think I've only rebooted twice in almost two years, I wonder why Tesla is still installing buggy FW v5.12?
Similar threads
