1-3s? That could really lead to serious problems for such features. Normally such stuff must be guaranteed to be displayed in less than 200ms or something around that.
I'm currently wondering if this a safety relevant feature (according to ASIL/ISO26262) and whether it would be even allowed to run such a feature on a component that is not designed for safety related environments which require realtime behavior (a QT UI running on Linux certainly doesn't provide that, and even lots of other automotive software stacks including Autosar give only limited guarantees).
Yeah, I did a bit more testing and I could actually get ~5s if I kicked off a navigation right before summon(I've also seen similar slowdowns on canceled nav).
The hazards do flash at the same time but that also happens when you lock the car.
You do need to opt-in but I'm hoping they make a change to have it a bit more defensive. In my opinion the right thing to do here is to admit it is possible to accidentally kick off and remedy it(much like with the battery shield).
>The hazards do flash at the same time but that also happens when you lock the car.
When activated from the stalk, the hazards lights don't flash continuously like the key fob or mobile app. They only flash once, because the car immediately and "automagically" selects the forward direction, transitioning away from the flashing state. And the only auditory indication when the driver is still in the car is a single chime.
>You do need to opt-in but I'm hoping they make a change to have it a bit more defensive.
The Autopark dialog is opt-out not opt-in, unlike other Tesla automatic features which require manual confirmation on the touch screen to activate.
A single additional press of the park button brings up the Summon dialog, with arrows to move the car forward and backward. The flaw is that forward is the default. You don't have to press it. The default should be "do nothing," making the driver confirm their intent to Autopark.
I'm currently wondering if this a safety relevant feature (according to ASIL/ISO26262) and whether it would be even allowed to run such a feature on a component that is not designed for safety related environments which require realtime behavior (a QT UI running on Linux certainly doesn't provide that, and even lots of other automotive software stacks including Autosar give only limited guarantees).