Fernand
Active Member
This coming from a 2 year Model 3 owner and a robotics developer, namely me.
For best results and fewer mood-altering oddball anomalies. After every update:
Reboot the screen computer. Hold the 2 thumb salute until the logo appears.
Put phone in Airplane Mode, sit in your seat as you power off the car,
then wait 3 minutes. That's what it takes to reboot the control computer.
Don't forget to then re-enable your phone to avoid hassles with the alarm ;-)
Do a walk-around and wipe your cameras and sensors before the day's first drive,
or after driving through muck.
Now, as to why. The car does several initializations when installing an update.
But these are part of a complex sequence that overlays new code piece by piece,
reloads map data and copies user settings to finally put together an operating system.
There isn't, as far as I can tell, a complete reinitialization of the final "assembly".
That reset takes up to 10 minutes, and needs to remove the car from connection
w/ the controlling phone, and off the network. That puts the system in an "out of reach"
state. Makes sense that it's best left to the user, who can react if the system gets "looped".
Of course, it's a small inconvenience, but it's well worth the time. And "why not?"
As to the pre-flight inspection, any dirt on the cameras will obscure some detail,
and until you look, you don't know how much. As to the IR sensors etc, cleanliness
is next to godliness ;-) It can't hurt.
.
For best results and fewer mood-altering oddball anomalies. After every update:
Reboot the screen computer. Hold the 2 thumb salute until the logo appears.
Put phone in Airplane Mode, sit in your seat as you power off the car,
then wait 3 minutes. That's what it takes to reboot the control computer.
Don't forget to then re-enable your phone to avoid hassles with the alarm ;-)
Do a walk-around and wipe your cameras and sensors before the day's first drive,
or after driving through muck.
Now, as to why. The car does several initializations when installing an update.
But these are part of a complex sequence that overlays new code piece by piece,
reloads map data and copies user settings to finally put together an operating system.
There isn't, as far as I can tell, a complete reinitialization of the final "assembly".
That reset takes up to 10 minutes, and needs to remove the car from connection
w/ the controlling phone, and off the network. That puts the system in an "out of reach"
state. Makes sense that it's best left to the user, who can react if the system gets "looped".
Of course, it's a small inconvenience, but it's well worth the time. And "why not?"
As to the pre-flight inspection, any dirt on the cameras will obscure some detail,
and until you look, you don't know how much. As to the IR sensors etc, cleanliness
is next to godliness ;-) It can't hurt.
.
