In particular, implementing a safe rendering solution – which helps keep drivers safe in today’s future cars in case other components fail – is very cost-intensive. Parts that drive these costs may include:
• Certification (one-time or multiple payments)
• Safe OS (royalties)
• Safe Hypervisor (royalties)
• The safe rendering solution itself (royalties)
So…what can OEMs do to cut costs while still meeting the technological demands of the modern customer?
Luxoft Safe Renderer – Opening Doors to Open Source
Introducing Luxoft Safe Renderer, which is a unique program thanks to its code being rooted in open source. Some have even said it’s the first of its kind, due to uniquely utilizing some of the strengths only open source can provide.
First and foremost, using open source is a major cost saver, eliminating the royalties that normally would have to be paid for a safe rendering solution (unless developed internally – which also comes with a price). Open source software also supports continuous innovation, allowing for rapid bug fixes and the addition of new features whenever necessary. Lastly, if you’re using open source, the software’s source code is completely visible to online visitors, and the software quality is higher overall (for more information on open source, look forward to our future blog that will be dedicated to it!)
The Safe Renderer can be seamlessly integrated into all sorts of systems with a wide range of complexities, accommodating anything from Browser, to Qt, to Populus. It also can act either as the ASIL-only HMI renderer or as a backup renderer in case the main HMI fails. Either way, automakers can use the customizable solution for what best suits their needs. Besides the main target of the solution (instrument clusters), it can be used for a variety of use cases – such as to boot up a logo, enable a rearview camera or activate parking distance control.
Here Are Some of the Safe Renderer's Capabilities:
• Works both with or without
• Renders ASIL Level B (ISO 26262) complaint-safe content (telltales, gearshift indicator, etc.)
• Handles hardware safety mechanisms (such as the display output checker)
• Displays the graphics engine’s status, notifying the system when issues arise and how to resolve them
• As a result, can either go into a safe state, alert the watchdog timer or reset the system depending on the needs of the customer
• Safe Renderer is designed as a Safety Element out of Context (SEooC)
• Can obtain on-demand ASIL Level B (ISO 26262) certification
• Dynamic text rendering support for Latin script languages
The future of the automotive industry is becoming more and more complex, and automakers need to be ready for that change – by embracing innovation and cutting costs as much as they can.