whitex
Well-Known Member
On the contrary, if FSD works flawlessly while the MCU is in a reboot loop, that would help regulatory approvals - proof that MCU failures will not affect FSD safety.This would be the end of any regulatory approval.
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.
On the contrary, if FSD works flawlessly while the MCU is in a reboot loop, that would help regulatory approvals - proof that MCU failures will not affect FSD safety.This would be the end of any regulatory approval.
I see your point. If navigation happens in the autopilot hardware ,sure. My experience is that it restarts everything while a reboot happens. Let's see if they can demonstrate it can be safe if there is a reboot.On the contrary, if FSD works flawlessly while the MCU is in a reboot loop, that would help regulatory approvals - proof that MCU failures will not affect FSD safety.
On the contrary, if FSD works flawlessly while the MCU is in a reboot loop, that would help regulatory approvals - proof that MCU failures will not affect FSD safety.
On the contrary, if FSD works flawlessly while the MCU is in a reboot loop, that would help regulatory approvals - proof that MCU failures will not affect FSD safety.
SHOULD is the operative word here, let's see if Tesla DOES.That's not a farfetched concept because an Autonomous Vehicle should have a redundancy system so even when one computer is broken, the other one can take over seamlessly.
...I'm thinking MCU is just the screen...
If it's just a non-touched screen then MCU and HW3 can be independent of each other but since MCU is a touchscreen so you can input HW3 parameters (enable/disable, configures some features) so there's a controlling gateway between the 2 but the main functional FSD is not at the MCU even if MCU won't be able to cope with overflowing data into visual graphics.
So in theory, HW3 FSD will drive the car fine even if MCU1 is crippled.
But FSD relies on Nav on autopilot it appears, which is controlled by the MCU
Does anyone on here know one of the beta testers that currently have the new FSD to suggest they try this & make a YouTube video about it? This is a fantastic idea to test what the car would do. Ideally this should be a beta tester with an S or X with the FSD beta since those are the cars with MCU1 and also they have 2 screens being run by the MCU.Let's wait until someone with the new FSD Beta does this reboot experiment and let us know whether the car continued to navigate lights, roundabouts, lane, etc with the MCU rebooting. Maybe some brave soul will even do a continuous MCU rebooting to see whether FSD is affected if MCU is constantly rebooting.
Remember that HW3.0 does not need MCU to continue to function.
You can do an experiment right now. Drive and put on your autopilot on a known reliable freeway for an experiment (in case you need to take over). Now reboot the MCU and its instrument cluster. The Autopilot will continue to work and even brakes for obstacles without the need of a blackout MCU.
MCU is a convenience and not a must for HW3.0
This is false. According to some reports, HD Maps are being heavily used for current FSD beta, if MCU is down - GPS, Maps and other functionality supplemented by MCU is down including current speed limit.(this can be seen by rebooting MCU while driving, until the MCU comes back up, the street speed limit is missing). If MCU is down or too slow to provide all necessary inputs for FSD Computer, then MCU1 is not compatible with FSD.
Any Model S/X Videos on FSD Beta feature?