passhard
Member
so true!!!They kind of struggle to come to terms with replacing items that are IN warranty.
why is it such a fight?
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.
so true!!!They kind of struggle to come to terms with replacing items that are IN warranty.
I'd read this... Any Parts repaired or replaced under the Tesla New Vehicle Limited Warranty, Tesla Used Vehicle Limited Warranty, or an active Tesla Service Plan is covered for the duration of that applicable warranty or plan, and does not extend beyond that duration.
When my eMMC failed, I was able to drive, despite not being able to enter a PIN (and P2D being set).
my screen has bubbles now....do they have to change the MCU when 17 inch screen is replaced?
gawd i hope so!!!
both my displays have bubbles
drivetrain is so noisy--- like a fast n furious Honda Civic exhaist--- ya, it's embarrassing!!!!
now my battery died!!!! 5 year old car & it seems like everything is going at once!
very interesting indeed.So I was in the same boat as you. My screen lost probably half of it's goo before I finally got it fixed. Tesla offers the option to just replace the screen but after reading about all the issues with the MCU, I went ahead and replaced the whole unit. For $700 more, it was worth it for the peace of mind of having a newer MCU and 4 year unlimited mileage warranty. Good luck!
That's interesting that your P2D wasn't stopping you from driving the car. Would you elaborate a bit more? Was your MCU just unresponsive or blank (dead)?
I'm concerned about my MCU1 dies and my P2D stops me from driving the car to SC or home.
My MCU went through periods when it was unresponsive - initially for a few minutes but later, for about two hours. During this period, I would get messages about authorisation. I am guessing that when the MCU was booting up, it spent some time running file system checks on the partitions on the eMMC and these took longer as more elements of the eMMC were failing. In the end, the MCU was completely dead. I was able to drive the car but unable to operate lights and notably, the sunroof.
I was blocked from driving in the periods when the MCU was trying to boot (from minutes to a couple of hours) but once past that, I was always able to drive. I was also able to charge at home (I had not set any charging schedule) but I didn't try at a supercharger.Thanks for the feedback. And, all that time your P2D was bypassed?
I'm long out of warranty (175,000km) and just waiting for the MCU to fail. The Telstra 3G network (used by Tesla) here is being switched off in 2024 too, so I'm expecting that it'll fail so that I end up with another full price MCU1 replacement, then have to pay to upgrade the 3G SIM to 4G, then wait 4 years for the EMMC chip to fail again, then pay full price, hopefully for a MCU2, or maybe 3 by then
For people concerned about not being able to charge in case of MCU failure, you can turn off scheduled charging and the car will charge if the MCU fails. The workaround for not being able to set a charging schedule is to use the Stats app, which allows you to schedule charging and is very flexible, among other useful things.
very interesting indeed.
i have approx 11 months left of extended warranty.
i think I'm gonna get out of this vehicle in May 2020.....so i can sell it with almost 5 months of warranty and new battery pack and prolly drivetrain.
I don't think I wanna be an owner without warranty.
hopefully i can arrange a convenience trade for a new Model 3 at my Tesla store.
if i go with a new M3 with the 2 years extended I'll be able to sleep tight for 6 years
i just wanna get as many broken things fixed as possible b4 i get rid of it
Can someone explain in layman terms why the read/write behavior that causes the memory failure hasn’t been stopped or reduced to a sustainable amount by a software update? It seems like this problem has been understood by Tesla almost as long as it has been understood by the forum...so why does the issue still remain?
Depending on how badly the MCU has failed, app may not be able to control it. Best to disable schedule before total failure. Even better to have recovery/replacement before failure.