Innovation and collaborative, synchronized program management for new programs
Enter the summary here - no longer than 75 - 150 words. Use two paragraphs if the text is over 75 words. This is the full version of the summary text which will appear on the full version of the capability page.
The AUTOSAR standard is founded on the ability to bring software vendors together to co-operate so they can efficiently produce ECU software. The software is made up of applications, software components (SW-Cs), hardware support through MCAL and the ECUs custom device drivers, which are all joined together by the basic software (BSW). Capital VSTAR adheres very closely to the AUTOSAR methodology and includes native support for the AUTOSAR model. Tool features like configuration splitability greatly simplifies the separation of concern between ECU SW developers.
Enabling a 'shift-left' in product development is essential for delivering the final product on a tight schedule. A correct-by-construction strategy is supported by design tool features such as configuration consistency checks. The built-in design rule checks (DRC) will highlight if there is missing data from inputs to the ECU configuration generator from upstream tools. The DRCs can be extended through the open scripting API to enforce specific design needs. The guided development flow in the Capital VSTAR Integrator dashboard, that adapts to the user persona, provides the design team with a streamlined approach to achieving a complete ECU configuration. Supported by the tool, developers can produce high-quality output eliminating issues that are expensive to resolve later in the ECU software design and verification process.
The configuration of the AUTOSAR BSW enables the correct execution of applications in the vehicle system, where data and resources may be either on the same ECU or on distributed ECUs around the vehicle or even in the cloud. The definition of the application’s data and execution requirements, as well as the data exchanged with the system, is described in the configurations provided by the application and network design tools. Capital VSTAR Integrator fuses the input data from these sources and, through the rules-based generation process, the tool resolves the system dependencies and generates the basic software configuration. For the parts of the ECU configuration that cannot be described in the exchange format, and to complete possibly missing data from upstream tooling, our solution provides additional wizards, smart panels, and guided workflow to help engineers finalize the ECU configuration. It also has the necessary features to do application authoring in case applications are provided without the required AUTOSAR descriptions. In the situation that software components (SW-C) are to be coded by hand or by a tool that does not support AUTOSAR, the Capital VSTAR run-time environment generates the SW-C API based on the provided SW-C description.
With the ECU software generated for the physical ECU, the Capital VSTAR tooling has the capability to generate the functional digital twin. Depending on the fidelity necessary for the digital twin, it is possible to replace the MCAL for the physical ECU with an MCAL generated for the virtual platform. This enables the digital twin of the ECU to be connected to a virtual environment based on the FMI standard and existing communication modeling technologies.
Subskrybuj najnowsze informacje o [[global-preference-center-interest-placeholder]]
Securing vehicle communication networks with firewalls
Improve automotive cybersecurity with TLS and firewall technologies
Implement a multi-layered approach to solve EV complex challenges