AUTOSAR published its new Release 4.0

The development partnership AUTOSAR (AUTomotive Open System ARchitecture) has published a new release of its specifications on December 18, 2009. With Release 4.0 the AUTOSAR Partnership has successfully ended its second Phase. The basic architecture of Release 4.0 is a logical development of the well-established architecture of Release 3.0. The new release contains a large number of new features that were demanded by the different applications of domains the AUTOSAR standard is covering. New concepts introduced in Release 4.0 add technical and functional improvements and extensions to the main areas including functional safety, architecture, communication stack, methodology & templates and application interfaces.

“One of the main goals for Phase II was to massively broaden the support for new hardware technologies such as multicore processors,” AUTOSAR Spokesperson Simon Fürst says. “Release 4.0 provides all features ECUs of the next generation of cars will need. Among many others this includes support for functional safety, multi core microcontrollers, LIN 2.1 and FlexRay 3.0 support as well as a timing model.” In addition, the number of Application Interfaces is increasing by approximately 320 to a total number of 540 Application Interfaces.

Release 4.0 contains a large set of application interfaces, which are standardised by AUTOSAR for the following five vehicle domains: Body and Comfort, Powertrain, Chassis, Occupant and Pedestrian Safety as well as Human Machine Interface (HMI). A major focus in this respect was on interface specification of well established applications in order to emphasize software reuse and exchange. The deployment of AUTOSAR Standardized Application Interfaces is a key factor for the reuse of applications. Therefore the application interfaces description contains a large amount of data standardised by experts of all partners and members.

A major focus of the development partnership was on maturing methodology and templates. Regarding the improvements particularly the harmonisation of ECU configuration parameters, the enhancements on measurements and calibration, the rework of the ECU Resource Template as well as the further alignment with FIBEX (Field Bus Exchange Format) play a key role. “The FIBEX standard has been harmonized with AUTOSAR and now former gaps between both standards have been bridged successfully," says Simon Fürst.

Furthermore Release 4.0 also implements the support of large data types and dynamic length signals, while the previous Release 3.0 has restricted signals to 8 bytes due to the CAN and LIN frames format. In addition the methodology and templates are able to describe timing requirements.

As the quality of Release 4.0 should be guaranteed from the very beginning, AUTOSAR conducted an intense validation process. While in previous releases the specifications out of one development were validated on hardware platforms the results of the validation of Release 4.0 has been mainly incorporated into the standard before its release.

For the first time the development partnership has also realised the validation of methodology and templates, ensuring a high quality. The validation of methodology is based on the new release, whereas the validation of templates is partly based on Release 3.0 due to tool availability.

“While the existing releases will be maintained during AUTOSAR Phase III, development will continue,” AUTOSAR Spokesperson Simon Fürst explains. “New or extended features will be introduced selectively during the next years and will always have to follow the rules of backwards compatibility.”

Comments

[coach outlet]

Um...like the style of your writing.

[BafEquatauI]

Насчет тонкого юмора поняли... А бывает толстый юмор?
видео голых русских актрисс

[Jamewallace]

ADB Consulting helps small and medium-sized businesses with the resources, expertise, and labor required to launch products using printed circuit boards (PCBs).http://www.automateandvalidate.com/