We are happy to announce that our latest Qt Safe Renderer (QSR) 2.0 is certified and available as of today, addressing the need to build UI applications with Functional Safety in mind.
Certifications
For each major release, we always intend to certify against the latest functional safety standards and requirements. For the 2.0 release, we have been certified by TUV NORD to meet the following safety standards:
- ISO 26262:2018-6; ASIL D:
- Road vehicles — Functional safety — Part 6: Product development at the software level
- ISO 26262:2018-8 section 11; ASIL D
- Road vehicles — Functional safety — Part 8: Supporting processes - Chapter 11: Confidence in the use of software tools
- IEC 61508:2010-3 – 7.4.4; SIL 3 and IEC 61508-3
- Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 3: Software requirements – and Requirements for support tools – 7.4.4
- EN 50128:2011 6.7.4; SIL 4
- Railway applications – Communication, signaling, and processing systems – Software for railway control and protection systems; Software-Tools
- ISO 25119-3 AMD 1:2020 AgPL e
- Tractors and machinery for agriculture and forestry – Safety-related parts of control systems - Part 3: Series development, software, and hardware - AMENDMENT 1
- IEC 62304:2015 (2006+A1) C.7, fit-for-use
- Medical device software – Software life cycle processes [relationship to IEC 61508 - best practice]. Up to Class C application
Feature highlights
- Qt Safe Renderer Monitor
- With QSR 2.0, we introduced a brand new module to called Qt Safe Renderer Monitor. It is designed and implemented under MISRA-C to ensure the integrity of display content for safe items. For more detail, you can find out the details from https://www.qt.io/blog/qt-safe-renderer-monitor and https://www.qt.io/blog/qt-safe-renderer-monitor-debugging-the-safety-application
- Rendering output verification for Qualcomm Snapdragon SA8155P
- We have added explicit support for Qualcomm Snapdragon chip sets, so that the onboard Display processor unit (DPU) CRC calculation is used for output verification. On how the Output Verification is achieved, see https://doc.qt.io/QtSafeRenderer/qtsr-outputverification.html
- Localization support
- With location support, developers can conveniently design, implement, and verify safety-critical user interfaces for many languages. The localization support also works with Qt Safe Renderer Monitor, so the verification of the display content output applies also to needed locales. You can read more from https://www.qt.io/blog/create-safe-uis-for-global-use
- With location support, developers can conveniently design, implement, and verify safety-critical user interfaces for many languages. The localization support also works with Qt Safe Renderer Monitor, so the verification of the display content output applies also to needed locales. You can read more from https://www.qt.io/blog/create-safe-uis-for-global-use
- Compliance with WCAG 2.1 guidelines
- We have added the new fillColor feature, which provides a solid background color for Safe QML elements. This ensures visibility and readability by checking contrast against WCAG 2.1 guidelines. More detail can be found in https://doc.qt.io/QtSafeRenderer/qtsr-outputverification.html#using-fillcolor-property
- Safe touch support enabler.
- We added a new API for SafeTouch, so it is possible to enable touch in a reliable way as part of the safety-critical application. You can read further from our Q&A as well as the SafeTouch API documentation
There are other improvements made in QSR 2.0, you can find the full details at https://doc.qt.io/QtSafeRenderer/qtsr-release-note.html
To learn more, check out online documentation https://doc.qt.io/QtSafeRenderer/index.html
How to get QSR 2.0
Existing Qt commercial users can now get the QSR 2.0 from the Qt installer with a Device Creation Enterprise license.
