According to the π¨π³ portal 36kr, Mercedes Benz delays the Start of Production (SOP) of the π¨π³ version of their CLA by 3 months.
According to 36kr, the delay is caused by software problems in the area of E/E Architecture related software. But no reason to start laughing maliciously now.
Mercedes combined a platform for electric and combustion engine vehicles, 800 V battery + charging, level 2+ driver assistance and their MB.OS. If they release with only 3 months delay, this is a big success considering the high complexity and variety.
Taking the burden from software development
Modern vehicles based on new vehicle platforms are always very complex and software development is usually the cause for delays and quality problems. But why?
Software is made the garbage bin for all kinds of new vehicle system challenges:
- Commodity component purchase
- Vehicle design constraints
- Adaptions to competitor offerings
- Heterogenous and limited hardware
To enable future vehicle innovations, hardware engineers must take some burden from the software development by taking over more complexity in:
- Safety
- Security
- variant management
- heterogenous networks
and others.
MACSec is a good example to take software complexity by implementing security features in hardware.
But there’s nothing comparable for safety. That’s what we are working on at SILICONALLY. Stay tuned until we can disclose more.
