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.
Not sure what you mean. I was asking for the amount of time needed to install either one of those service work.Mcu1 may be the cockroach, still hanging in there after the info-mercials crash the others.
A bit off-topic, but ... which one requires more work done by the SC: The MCU2 upgrade or the HV battery replacement?
I'm just curious.
Does anyone know?
I'm betting MCU2 upgrade. They need to backup certain settings/certificates, dismantle the dashboard, remove the old MCU and 2 screens, reinstall, restore settings and then redeploy firmware (2 hour process) which doesn't always (according to a local engineer the right term was "hardly ever") work the first time.A bit off-topic, but ... which one requires more work done by the SC: The MCU2 upgrade or the HV battery replacement?
I'm just curious.
Does anyone know?
Thanks for response. I understand your question about certs, but they are totally fine, were migrated from old MCU1, Tesla app works just fine. So there's something different.That's an interesting thought. We do have one person at least here (but I am not going to be the one that says his name) that did his own MCU2 upgrade before Tesla even admitted it's possible. So, he would know what he had to do to make it work.
But since you brought it up, could be that the car's security certificates need updating to a set that recognize MCU2 and we have no way of getting those from a Tesla server. Hmmm, interesting discussion. Mr @advert.
A bit off-topic, but ... which one requires more work done by the SC: The MCU2 upgrade or the HV battery replacement?
I'm just curious.
Does anyone know?
I'm betting MCU2 upgrade. They need to backup certain settings/certificates, dismantle the dashboard, remove the old MCU and 2 screens, reinstall, restore settings and then redeploy firmware (2 hour process) which doesn't always (according to a local engineer the right term was "hardly ever") work the first time.
Definitely the MCU2 upgrade. Remember the short-lived battery swap station demo? WIth the proper equipment setup, a battery replacement could take just a few minutes. The MCU2 upgrade as mentioned above, they have to take apart the entire dashboard, install the MCU and IC, re-install, and then do (one or more) firmware updates. Takes several hours.
When I dropped off my car for the MCU2 upgrade back in Sep'21 I was told before they started that reloading the firmware takes several hours and didn't always work, meaning they might have to repeat the long reload process again from the start, possibly several times . Therefore predicting how long they'd have my car might be difficult. In the end it took them 3 full business days to successfully complete the upgrade because of issues trying to reload the FW. Maybe they've ironed out the kinks in the process by now but anyhow my experience last year matches the comment above. BTW zero regrets getting the upgrade - feels like a new car, so glad to be rid of that crappy MCU1.I'm betting MCU2 upgrade. They need to backup certain settings/certificates, dismantle the dashboard, remove the old MCU and 2 screens, reinstall, restore settings and then redeploy firmware (2 hour process) which doesn't always (according to a local engineer the right term was "hardly ever") work the first time.
I would have thought ICU1 would be the last thing standing, but with the eMMC recall only for the MCU1, no way my ICU1 makes it to the end.Mcu1 may be the cockroach, still hanging in there after the info-mercials crash the others.
It really depends. Generally, I suspect MCU2. However, my MCU2 took a day. My battery swap took ten days. Seven days for the battery to arrive and three days to retrofit the 90kWh pack into my P85D. Most of the time was retrofitting firmware.A bit off-topic, but ... which one requires more work done by the SC: The MCU2 upgrade or the HV battery replacement?
I'm just curious.
Does anyone know?
Confirmed. Tesla recently changed logic that if you try to use MCU1 certificates on an MCU2, tesla will no longer send your car firmware updates. All cars upgraded prior to this change still get updates, but they’re effectively shutting down DIY retrofits (if any one is still able to do that with all the other cracking down they’re doing) as no mcu2 will get firmware updates if mcu1 certificates talk to mothership. Only way to get mcu1>mcu2 is to do so officially now.That's an interesting thought. We do have one person at least here (but I am not going to be the one that says his name) that did his own MCU2 upgrade before Tesla even admitted it's possible. So, he would know what he had to do to make it work.
But since you brought it up, could be that the car's security certificates need updating to a set that recognize MCU2 and we have no way of getting those from a Tesla server. Hmmm, interesting discussion. Mr @advert.