The first part of the article covers the structure of AUTOSAR-conformant ECU software, the AUTOSAR development method and helpful auxiliary tool support. The second part of the article presents realistic scenarios illustrating how AUTOSAR ECU software is maintained over its life cycle.
The introduction of AUTOSAR changes the cooperation between OEM, TIER1, HW manufacturer and software deliverer. This first part of a two part series describes the basics of a successfull cooperation - the AUTOSAR specific exchange formats and tools.
The FlexRay communication bus and the FIBEX database exchange format represent the current state-of-the-art of in-vehicle networking. In this context, the FlexRay bus must fulfill requirements related to remaining bus simulation, diagnostics and higher protocols, testing and AUTOSAR development methodology, over the entire development process. These requirements are fulfilled by FlexRay development tools quickly and extensively, sometimes in completely new ways. This article discusses the requirements that need to be met for an effective development platform. It addresses special requirements of the FlexRay bus for remaining bus simulations, higher-level protocols, diagnostics, highly specialized tests and AUTOSAR development methodology.
In the automobile, airbags are among the safety-critical systems whose reliability can be a matter of life or death. The airbag control unit is responsible for proper operation of the entire occupant restraint system, consisting of all sorts of airbags, belt tensioners, sensors and switches. Even during product development, numerous validation tests are indispensable at all development stages. A new test system at the Robert Bosch company increases efficiency in early test phases in development; it shortens test times while simultaneously increasing testing depth. It also reduces the number of test iterations for system tests on existing HIL test benches.
The required “unlimited compatibility” of components on the ISOBUS cannot be attained by performing conformity tests at the end of device development alone. Rather, sound and continual tests over the entire development phase are necessary. Efficient use of such tests can only be achieved by using tools with domain knowledge that cover a large number of tasks ranging from simulation to analysis tests as well as conformity tests. Developers of implements and tractors need a tool that covers conformity testing, cycles through the tests independently, yet offer the freedom to only test certain sections and can be extended to test the application.
In the development of complex ECU applications, there are greater and greater quantities of data to be processed, more signals to be measured, and a growing number of parameters to be optimized. Previous methods for measuring, calibrating and flashing are increasingly encountering limits with regard to the necessary data throughput. It was in this context that Robert Bosch GmbH initiated a search for a more powerful and future-robust measurement concept for the next generation of its ECUs, in particular for the development of a new long-range radar sensor.
Emerging from the Crisis: Improving Engineering Efficiency in Tough Times.
Increasing cost pressure, shortening innovation cycles, global competition and grow-ing saturation in many markets demand efficiency improvement in product develop-ment. Successful organizations consider efficiency improvements an investment in their future – and in the current crisis of the world economy this need is even stronger. Many of our clients ask us whether the current situation with lots of cost cutting measures is the right time for process improvement. If done well and with good guidance on the necessary change management, process improvements will lead to quick wins and improved efficiency. Profound process improvement helps to trim RD&E specifically for the crisis. This article provides experiences and empirical evidence from such improvements in different context and companies.
Our world and society are shaped and governed by embedded systems. It’s difficult to imagine day-to-day life without such systems. IEEE Software and IEEE Computer present insight from Vector Consulting Services, Siemens and world-renown Capers Jones on trends and evolution in embedded software. Read this intro article to get the opinion of the leading experts in the field on how embedded software will evolve.
The focus in ECU function development is always on finding the best possible control algorithms and parameter combinations. A new solution now offers users a single measurement and calibration tool with universal application – from initial model design to the production level ECU.
Software-Messung stellt sicher, dass wir bei unserer Arbeit und in unseren Projekten die Kontrolle behalten und erfolgreiche Ergebnisse wiederholen können. gemessen werden Produkte (z.B., Leistung und Qualität), Prozesse (z.B. Verbesserung der Effizienz), Projekte (z.B. Lieferunggenauigkeit), und die beteiligten Personen (z.B. Entwicklung der Kompetenz). Dieser Artikel beschreibt, wie praktisch gemessen wird. Er bietet eine konkrete Anleitung und Beispiele für Projekt-und Prozess-Messung.
Software measurement is the discipline that ensures that we stay in control and can replicate successful processes. It applies to products (e.g., ensuring performance and quality), processes (e.g., improving efficiency), projects (e.g., delivering committed results), and people (e.g., evolving competence). This article discusses software measurement and provides practical guidance for project and process measurement.
In the future, data communications in the automobile will also take place beyond the vehicle`s boundaries. New requirements are evolving, especially in the development of applications such as Car2x and remote diagnostics. These challenges are best solved with relevant tool support, where CAN messages are tunneled via the wireless air interface.
Functional testing of automotive ECUs, besides testing for basic functionality, must also test the most significant faults at the ECU’s communication interfaces and the I/O interfaces. By using the VT System, a modular test system by Vector that is tailored to automotive industry requirements, you can efficiently execute functional tests during early development phases.
Test case generators that implement the concepts of model-based testing in functional model development have been commercially available since 2007. The automatically generated test cases simplify regression tests during iterative
development of complex models. Transformations make it possible to re-use the test cases that are generated, e.g. in ECU acceptance testing, so that test cases do not need to be recreated manually. This results in considerable savings in time and
cost for functional developers.
ECU networking in heavy-duty vehicles is characterized by the same challenges as in the automobile. Added difficulties are caused by the large numbers of variants with low production volumes and longer product life cycles, requiring a suitable architecture layout. Specially modified development methods are indispensable in handling cost pressure and sending reliable vehicles onto the street.
Besides testing actual functionality, a modern test system for ECUs must also permit testing of the most important fault cases. This applies to the ECU`s communication interfaces as well as to its I/O interfaces. Suitable test systems can be implemented early in the development process using special test strategies tailored to the needs of the automotive industry. The new compact test hardware VT System from Vector meets the various challenges that face such a test system.
CANopen established itself as a standard for cost-effective and flexible networking of components in numerous application fields ranging from industrial automation to commercial vehicles. Standardized device profiles simplify communication between bus nodes and facilitate smooth interplay between the ECUs, sensors and actuators from different manufacturers. A specialized prototyping and test tool not only performs valuable services in developing complex CANopen projects, but also in providing a fundamental introduction to the subject area.
More and more electronic functions for safety and convenience are finding their way into the modern automobile. Since the number of ECUs is being held in check, however, this means that the complexity of individual devices must grow to compensate. Making an important contribution toward rationalization of the development process for these distributed systems is the XCP communication protocol, whose main tasks include measurement and calibration of ECU-internal variables at runtime. A tremendous advantage of this successor protocol to CCP is its independence of the physical transport layer.
CANopen has become an accepted standard for cost-effective networking of components for many types of applications. Systems networked by CANopen offer ample flexibility at well-defined costs. Nevertheless, as with any other new technology the initial implementation of such a system is always associated with high technical risks for the system producer. What potential challenges must a developer of CANopen systems overcome? A majority of the development tasks within the framework of the V-Model can be ascribed to the areas of verification and validation. Comprehensive testing conducted as early as possible allows the developer to nearly exclude errors that might otherwise be discovered too late.
Contact
