Tesla is among the world’s largest electric car manufacturers. The company is very popular with the performance and autonomous driving technologies it offers to its customers. In this way, the company can easily reach good sales figures around the world.
Although Tesla works hard on its vehicles, some problems may occur. Due to these troubles, the company organizes recalls and fixes the faults of vehicle owners free of charge. Tesla is in trouble again with a recall. The company had to recall nearly 600 thousand vehicles.
Tesla is recalling 600 thousand vehicles due to the problem with the Boombox feature!
In February, Tesla decided to recall 578,607 electric cars due to a problem with the Boombox feature. This recall affected all 4 car models. The reason for this call was that the Pedestrian Warning System sounds, which were mandated by the state, did not work when the feature was active.
Although the company tried to solve this problem with software, unfortunately it was not successful. Now, the company has decided to recall slightly more cars than in February. 594,717 cars are affected by this call, and there are 4 different models among them. The new recall will happen in software, not physically.
The recall will cover 2020-2022 Model S, Model X and Model Y, and 2017-2022 Model 3 cars, according to a new announcement and related documents from the National Highway Traffic Safety Administration. The boombox feature allows users to play different sounds to other drivers thanks to an external speaker.
This feature can block the output of sounds designed to alert pedestrians to the vehicle’s position. This increases the risk of possible accidents. Affected vehicles will receive a new update regarding this situation and this risk will be removed. In this way, errors in the vehicle can be easily corrected without going to a dealer.
So, what are your thoughts? Do you think cars should get updates over the internet? Would you like your vehicle to update while you are not using it? Do not forget to share your views with us in the comments section or on the SDN Forum.
6859
