MentalNomad
Member
Yep. This is my single biggest complaint. How do you make a car drive itself but you can't make a camera turn on instantly?
Easy.
----------------
Step 1: Make a car with multiple computers.
One computer manages car systems and does self-driving; it controls steering, acceleration, brakes, blinkers, and monitors the camera feeds..
Another computer shows an infotainment screen; it gives users a way to interact with non-critical systems, to enter new map destinations, etc.
Step 2: Give the primary computer (the one that drives the car) priority at all times.
----------------
How does this lead to a problem? When you shift into reverse, the infotainment checks in with the primary computer to get wheel position and to turn on a direct feed form the steering wheel/sensors so that it can draw the travel lines on to the image. It may even run the camera feed through the primary computer (I don't know.) The infotainment computer's request gets queued by the primary computer, because other stuff it does has to be programmed to take priority; it will enable the infotainment feed when it's ready.
On the other hand, if you just hit the on-screen button for the rear view, it pops up instantly. It doesn't ask the primary computer for permission for anything, or for information - it just taps into the camera feed and puts it up. Teh end.
Simply remembering that this thing has more than one computer explains a LOT of things people complain about. (It's also why it drives perfectly fine, even on autopilot, while the infotainment computer reboots... because your two-thumbs reboot ONLY reboots the infotainment computer, not the primary computer.)