2017.50 2275226 is out

[daktari]

Anyone else have the bug with "service wipers"?
Mine don't stop but continues wiping.

 

[TrevTremaine]

So, the 50 failure disables Autopilot but changes the easy entry...hmmm. Not a good trade off but once they get it fixed hopefully it'll stabilize again. I'll be curious to know how many others were impacted.

I'm with daktari, glad they pulled it so others aren't impacted.

 

[Asterix187]

Mine updated perfectly fine around 9 hours ago (uk September 27 build) from 44 to 50. However, my Spotify no longer works and won’t connect to the tesla account.

 

[TrevTremaine]

Mine updated perfectly fine around 9 hours ago (uk September 27 build) from 44 to 50. However, my Spotify no longer works and won’t connect to the tesla account.

What's the configuration of your car? It may be related to AP2 or 2.5.

 

[Asterix187]

2.5. My autopilot worked straight away as was available the moment I moved off.

 

[daktari]

Mine updated perfectly fine around 9 hours ago (uk September 27 build) from 44 to 50. However, my Spotify no longer works and won’t connect to the tesla account.

Do a scroll wheel reset, usually fix that issue on mine.

 

[Chad Meyer]

I had 2017.50.1 pushed to me 50 min ago. Installed successfully.

Kudos to Tesla for the quick turn around on this.

Hoping there are unannounced AP improvements, now that AP is usable again.

 

[Snowstorm]

Maybe this update sets up the code for some new AP feature which will get activated on Christmas as a special bonus.

 

[rpm001]

Wow, is this the fix to the one that kept failing? That would be impressive turnaround if true.

 

[pilotSteve]

Wow, is this the fix to the one that kept failing? That would be impressive turnaround if true.

... yeah they just changed some 1s into 0s and other 0s into 1s. Voila! All better....

 

[S100D]

I had 2017.50.1 pushed to me 50 min ago. Installed successfully.

Kudos to Tesla for the quick turn around on this.

Hoping there are unannounced AP improvements, now that AP is usable again.

The latest release on Ev-FW.com is:

2017.50.1 ceae3b8

 

[croman]

The latest release on Ev-FW.com is:

2017.50.1 ceae3b8

I think that's his p100D on both TeslaFi and EV fw.

 

[sharpgator]

I’m interested to read the stories of failures. Yesterday, while still on .48, I spent the day without AP and without auto headlights and a couple of other glitches. This was completely out of the blue. Spent hours on the phone with Tesla to no avail. Finally parked the car for a while and when I came back, all was normal. This morning, I had the .50 update which I installed. So, I’m wondering if I had a failed update yesterday as my car’s behavior is similar to that of those with failed updates.

Here’s what I can say about .50....highway AP is silky smooth.....substantial reduction in ping-ponging.

 

[Stephan]

AP2.5. Updated from .44 to .50 with no fail.

However, I can't login to my personal Spotify account AND front sensors still working intermittently.

 

[massterty]

2017.50.1update over WiFi fixed my broken 2017.50 update! No need to go to the service center.

 

[Asterix187]

Do a scroll wheel reset, usually fix that issue on mine.

Worked perfectly thanks for the tip!

 

[SucreTease]

I got nailed by this this morning. I received delivery of my new S100D with .48 installed. This morning, I received notice that an update was available, which I assumed was the 2017.50.1 (I must not have paid close attention) that was pushed out yesterday. Unfortunately, it was the .50 release and I got an update failure notice; yet, it now shows my current installed version as .50. I hope I haven't lost functionality as a result. I am hoping that Tesla pushed .50.1 to me as soon as my car reports that it has .50. I don't know why Tesla would push .50 to my car AFTER it had already been replaced with 50.1.

 

[croman]

I got nailed by this this morning. I received delivery of my new S100D with .48 installed. This morning, I received notice that an update was available, which I assumed was the 2017.50.1 (I must not have paid close attention) that was pushed out yesterday. Unfortunately, it was the .50 release and I got an update failure notice; yet, it now shows my current installed version as .50. I hope I haven't lost functionality as a result. I am hoping that Tesla pushed .50.1 to me as soon as my car reports that it has .50. I don't know why Tesla would push .50 to my car AFTER it had already been replaced with 50.1.

There is no way to tell which firmware your car has staged.

 

[viper2ko]

Does this update give the option to preheat the battery from the app?

 

[SucreTease]

There is no way to tell which firmware your car has staged.

Thanks for that clarification. It's nice to know I wasn't foolishly unobservant. Not very nice to not know whether you want it or not.