davewill
Active Member
As a software engineer, it sounds like lunacy that they wouldn't fix this as the bug it is rather than just have people reset the counters.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Just wanted to post my experience... 2015 Model S, original owner... absolutely love the car and have not had any real issues thus far during 65,000+ miles apart from replacing the small 12V battery and a driver side door handle (both covered under base warranty)-- I did have a strange stretch of bad luck during my first couple years where I had multiple flat tires caused by screws, bolts, etc. on the original Michelin Primacies but after I replaced them with Michelin Pilot Sports about a year and half ago, no more flats... knock on wood.
But in the last few weeks I noticed that in order to start the car I would have to do a reboot (both scroll buttons) with alarming frequency.... seemingly every other day. I scheduled a service ranger appointment and thought I might have to replace the original MCU; the service technician texted me a few days before the appointment and asked me about the issue... they suggested clearing both Trip A and B histories (I had never touched either so both showed the same mileage as the odometer... over 65,000 miles. For good measure I also deleted all of my navigation destination history and the streaming music favorites I never use. Since I wiped these about a week ago, I haven't had to do a reboot (I cancelled the service visit). Anecdotal to be sure but clearing the Trip histories seems to have made a difference for me.
Hi David, can you please clarify... if it is failing chip, does that indicate that I will need to replace the MCU in the near future or is there some other fix? Currently it seems to be working like normal (after the Trip A/B reset)... are there any other indicators of a failing chip I should look out for? ThanksThat sounds more like a failing chip in the MCU. What you described sounds exactly like that.
Hi David, can you please clarify... if it is failing chip, does that indicate that I will need to replace the MCU in the near future or is there some other fix? Currently it seems to be working like normal (after the Trip A/B reset)... are there any other indicators of a failing chip I should look out for? Thanks