-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Software Update 2019.8.x
- Thread starter f205v
- Start date
Mike, that's interesting. I was cruising through the fleet update data in TeslaFi and found this. What are your thoughts?
Bill Price
Active Member
It appears to me that running on 2018.50.6 is the way to go at this time since everyone is having problems with the newer firmware. Not going to complain about not getting newer firmware at this time. Waiting for stability seems to be the best option?
plumazul
Member
Yeah, I certainly do have that option on the car and it was working perfectly fine prior to 8.3. I fully understand that they have a new tab called Ludicrous + which I have, however when that is selected, underneath it's supposed to say Max Battery Power and the time it will take for the battery to reach optimal temperature. That is missing on my car. When that is activated, it enables Launch Mode. That is not working on my car either.
Here are two screenshots. The first one is my car with the Max Battery Power option missing. The second is someone else's with it shown.
Did you try it with the light gray background color (in case it's some weird font color issue, yes I've seen bugs like that)
Yeah, I had been messing with it all day. That pic was taken at night when it had gone into dark mode. The reason I know it's not working is prior to the firmware update, when I enabled Max Battery Power, I could hear the fans kick on and it was pretty loud while the battery was heating. There was no mistaking when I was in Max Battery Power mode. On top of that, when that mode is enabled, Launch Mode worked. When I go through the Launch Mode sequence now, all I get is the two pedals pressed warning, so it is definitely not working.
Litigate28
Member
Grumble I have the same problem. When I go into Insane+ nothing happens. No max battery heating notification and no loud battery whine as it was heating. Let me know if 8.4 fixes that for you.
nyb, sorry to hear that but glad that I'm not the only one experiencing this. Hopefully this fixes it. I have an appointment scheduled for next Monday at the service center so if 8.4 doesn't fix it, I'm sure they'll figure it out. Will definitely report back on how things go.
‘Everyone’ is a bit of an overstatement, I’m very happy with the improvements over 18.50.6, I certainly wouldn’t want to go back...
ahkahn
Active Member
Yeah, I second that. 8.3 has been good for me. I did have 1 MCU crash, but I'd still take this over 2018.50 any day.
markn455
Member
Check your browser. I bet it does not work either. I had this issue the entire time I was on 8.3. As soon as I was updated to 8.4, release notes appeared and the browser started working again.
Update on your service appointment? I'm at PDX Service & the only guy here I can talk to w/o an appointment says he hasn't seen the screen message error prior to me showing it to him..
Was there anything that stood out in your logs at the SC that indicated it was a specific camera, or more?
-TechVP
I am no buttershrimp. The first 3 months of AP2 trained me to be an excellent safety supervisorYou must have nerves of steel
Blitz3RS
Member
I'm on the road but wanted to post an update. After a nearly 2.5 hour long service visit, my blindspot detection problem has been remedied! After just over an hour into the service appointment the tech and service writer wrapped up and said it was my driver's side side marker camera unit and swapped it out and said that cleared the error.
So the family and I got into the car, I put my foot on the brake, shifted to drive and.... The error was back!!!
Not wanting to make this visit worthless, I got out and said "The error is still there, would you like to see it?" the tech was right there and was bamboozled because he just cleared it and said everything was working.
So he said he would take it back in, and was he was getting in it, I said that maybe Tesla at large figured something out and released 8.4 as a hot fix to correct the bugs.
He took it back for another hour and worked on pulling the logs and was able to stage and force the update to download to 8.4
I didn't have the time to stick around to wait for 8.4 to install but whatever he did, I was still on 8.3 and no longer has the blindspot detection warnings anymore and could even see all the lane markings on a multi lane highway.
So now I sit at this hotel with my car in the parking lot showing the update notification at the top of the MCU screen letting me know it's ready for 8.4...
The service center (Richmond) is really curious to see if 8.4 is going to fix my issue (blindspot) but I don't know how to tell them that whatever they did, it's fixed... For now. Going to wait to install 8.4 until tomorrow because I have a bit of driving to do tomorrow and I'm loving having the blindspot stuff working again.
Do you mind sharing a snippet of the service receipt that indicates the parts that were replaced?
Thank you for the informative update. I will probably have to call a technician and have them remotely diagnose -- so I get an idea which marker camera issue I have prior to my service appointment.
Good call staying w/ 8.3 for your trip. Send us any results, good or bad.
Curious, since you're driving, did you notice anything w/ your sound system? After several Nov/Dec updates where audio quality sounded muffled & not punchy... Mine appears to sound better w/ 8.3 and Dolby Stereo on.
Could be anecdotal... but worth a comment.
Also curious if you think 8.3 AP has improved and smoothed out? On my drive today... AP seemed slightly more cautious, and a smoother ride.
-TechVP
That is what I am still on (and happy to stay there I think), does anyone know if I get a notification for an update but choose to ignore it for months does that mean the next update cycle I'd get the latest or do you just get what they originally notified you for until it is intalled?
s1rk
Member
My guess is you will update to whatever latest firmware is pushed to your VIN.
It seems in the last software update that they disabled the auto dial when you issue a voice command. There used to be a bar that would count down after the voice command giving you a chance to cancel if the voice heard you wrong. Now you HAVE to hit the right scroll wheel to accept. Annoying.
