eb tresos product line introduction - hanser...

Company confidential / Copyright Elektrobit Corporation 2011

EB tresos® product lineIntroduction

Copyright Elektrobit Corporation 2011www.elektrobit.com, 09 September 2011, Slide 2Company confidential

Agenda

EB tresos

• EB tresos product line

• Success Stories


•EB delivers a complete AUTOSAR standard core

EB provides an integrated and open tool environment

EB supports major automotive microcontrollers

EB supports all automotive communication standards e.g. FlexRay, CAN or LIN

EB's AUTOSAR Mission


• Understand OEMs‘ requirements and…

• Cooperate with semiconductor manufacturers…

• Support Tier1s in delivering mass production readyECUs to meet OEMs demand.

Our Mission


EB ECU Software & Tools

• EB tresos DesignerAutomotive network design tool

• EB tresos StudioBasic software configuration tool

• EB tresos AutoCoreAUTOSAR compliant basic software

• EB tresos Debug & TraceAUTOSAR runtime analysis

• EB tresos InspectorFR, CAN and LIN measurement and analysis tool

• EB tresos BusmirrorFlexRay and CAN cluster emulation tool

• EB 61x0, EB 2100, EB 5100Bus interfaces for cluster emulation and measurement

EB tresos® – One product family for ECU software development


• Workflow-based network system design tool, including the following • working steps:

• Hardware architecture- ECUs + network

• Protocol configuration- FlexRay configuration parameters

• Communication planning- signals, PDUs, frames- schedule

• Import/export functionality- FIBEX, CSV-files- AUTOSAR EPC-files

EB tresos Designer


• Configuration, validation and generation of an AUTOSAR-compliant standard core

• Eclipse based, open API

• Framework extensible viaplug-ins, based upon:

- XML- Java

• Extensible with customer-specific software modules(e.g. complex drivers, application modules)

• Standard input/output formatssupported:

- AUTOSAR: XML + Schema - others: FIBEX, DBC, LDF, OIL

EB tresos Studio


MicrocontrollerAbstraction Layer

Mode Management

ComMEcuMNm

FirmwareWdglf

Runtime Environment

Spi, RamTstGpt, Mcu, Wdg, IcuPort, Dio, Pwm, Adc

CANCanSmCanNmCanTp

CanIf

CanTrcvCan

Memory

NvMCrc

MemlfFee / Ea

FIs / Eep

SWC ApplicationLayer

ApplicationAbstraction Layer

ServiceLayer

ECUAbstraction Layer

LIN

Linlf

Lin

CDDs

FlexRayFrSmFrNmFrTp

Frlf

FrTrcvFr

Diagnostic

Det

COM ServicesComPduR

IPduM

Generic AUTOSAR 3.1 modules

WdgM

DemDcm

OS

OsSchM

OEM OEM

OEM

OEM

LinSm

OEM OEM

OEM OEM OEM

OEM

AUTOSAR 3.1 modules with OEM extensions

OEMSWCOEM

SWCOEM

EB tresos AutoCore with OEM specifics


EB tresos Debug & Trace

Features

• Debug and trace the behavior of an AUTOSAR software stack during run-time

• Transmission of Debug & Trace data via standard bus interfaces, e.g. CAN or FlexRay

• Buffering of data in ECU memory• Switching traced data on/off during run-

time• Tracing of signal information that is

transmitted via the RTE

• Activation tracing of runable entities

Benefits• Reduce AUTOSAR complexity ⇒

Easily find problems during system integration

•EB tresos Studio •EB tresos Inspector

•trace

•analyze

•optimize

•configure


EB tresos BusmirrorTool for specifying FlexRay & CAN cluster

emulation:

• Allows stand-alone ECU development• 3-step cluster emulation configuration

for FlexRay and CAN• Check out fault scenarios

• Support of OEM specific extensions(e.g. alive counter)

• Cluster emulation solution which can be integrated in user environments due to various driver support

• NI/LabVIEW and NI/LabVIEW RT driver• ETAS LabCar HIL system driver

• LINUX and Windows VISTA driver

• MATLAB/Simulink xPC driver available

• FlexRay-FlexRay Gateway extension available

Used in combination with EB 5100, EB 6100 & EB 2100


• Monitoring and analysis solution for bus communication and ECU software debugging:

• Versatile analyzing andmeasurement tool for FlexRay,CAN, LIN and ADIO channels

• Log, edit and replay of measurement data

• ECU stack analysis and debugging

• WinCore Runtime support (AutoCore on Win32 system)

EB tresos Inspector

Used in combination with EB 5100, EB 6100 & EB 2100


EB tresos WinCore & EB tresos Inspector

• Virtual ECU software development on a standard Windows PC

• Debugging of WinCore• Sending and receiving of virtual bus data

e.g. CAN, LIN, FlexRay• Sending and receiving of ‘real’ data e.g.

CAN busMost appropriate for: • Function developers

• Integrators

• Test departments Benefits: • Reduced turn around times• Earlier testing

• Each engineer can test on his PC

Windows PC

EB tresos AutoCore on WIN32 EB tresos Inspector

SW-C

WIN

32 Os

Services

WIN32 MCAL

Rte

Interfaces

SW-C

Can

Can + Fr Virtual Bus


EB Hardware InterfacesOverview

EB 6100 EB 2100 EB 5100

Ethernet & USB 2.0Ethernet & USB 2.0

400 MHz CPU on-board400 MHz CPU on-board400 MHz CPU on-board

PMC standard board with adaptorboards for PCI, PXI, cPCI, PHS, VME, …

•Destop housing with DSUB9 connectors•Temp. Range: 0 … +50°C

• Robust automotive housingwith ODU/Lemo connectors• Temp. Range: -30 … +70°C

5x PhysicalLayerModule slots forFlexRay, CAN, LIN and ADIO

2x FlexRay, 4x CAN, 2x LIN2x FlexRay, 2x CAN, 1x LIN


Agenda

EB tresos

• EB tresos Product Family

• Success Stories


EB's AUTOSAR History

Feb. 2004 EB becomes AUTOSAR Premium Member

Jun. 2005 First AUTOSAR OS SC4

Dec. 2005 First AUTOSAR-compliant Standard Core

May 2006 First integration in a production vehicle

Aug. 2006 First modules selected for production

Dec. 2006 AutoCore for AUTOSAR 2.0Apr. 2007 First two ECU series projects started

2007 JasPar evaluation

Mar. 2008 AutoCore for AUTOSAR 2.1May 2008 Full AUTOSAR project started

2008 First AutoCore modules scheduled for production

Dec. 2008 AutoCore for AUTOSAR 3.0


Awards 2009

Frost & SullivanEuropean Automotive Telematics and InfotainmentProduct Line Strategy Award

recognizes EB's outstanding ability to address customer needs and product demands

MicrosoftWindows Embedded EMEA Partner Excellence Award

recognizes EB's outstanding efforts in driving Windows Embedded designs


The CompanyHeadquartered in Ingolstadt, Germany, AUDI AG is one of the major manufacturers of luxury cars and is a 99%-owned subsidiary (as of 2004) of Volkswagen, the largest car manufacturer in Europe. Audi produces more than 960,000 cars per year with several renowned models in its line-up of A-series cars, which include the A4, A6, and A8.

Success StoryElectronic Fault Information System (ELFIS) for Audi

The BenefitWith the new system Audi is able to address fault handling for electronic and mechanical parts in production in a single unified process for several German as well as international plants and production lines. A central component is the joint capture of faults and their causes based on a single object naming terminology.

The SolutionBetween 2005 and 2009, EBdeveloped in successful cooperation with Audi production planning, line and IT departments an all-in-one IT system with advanced functionality to succeed the existing ones. EBprovided the entire application software, using up-to-date Java Spring web application and Oracle database technology, as well as the overall development lifecycle based on agile methods.

The ChallengeIn 2005 Audi faced 7 autonomous IT systems for 2 plants with 5production lines. These systems were used for electronics and mechanical fault documentation, cause analysis and reporting. Each system by itself did not cover all aspects of fault/cause data handling. Missing interoperability and scalability, divergent user interfaces and insular databases also posed a challenge.


The BenefitEB‘s expertise in OSEK and AUTOSAR software developmenthas helped make efficient projectspecific integrations and portingsof the BMW Standard Core.

The SolutionEB has become the main supplier of the BMW Standard Core in 1997. EB has developed most of basic software and has integrated the complete Standard Core versions SC3, SC4, SC5, SC6 and BAC2.1 on a great variety of hardwareplattforms.

The CompanyHeadquartered in Munich, Germany, the BMW AG is one of the major manufacturers of performance and luxury cars. It owns and produces the MINI brand, and is the parent company of Rolls-Royce Motor Cars. BMW produces more than one million cars per year.

The ChallengeBMW started using standardsoftware in series production as early as 2001. The Standard Coreincludes up to 56 basic softwaremodules. In addition, BMW substituded selected standardmodules with ones developed on their own. BMW searched for a company to take over the integrationwork.

Success StoryOSEK and AUTOSAR compliant standard core for BMW


The BenefitEB‘s expertise in FlexRay softwaredevelopment has enabled BMW to create software assets that are fit to its environment. This will allow BMW to differentiate from other car OEMs.

The SolutionEB has become a main supplier of FlexRay software for this project. EB developed and integrated the FlexRay-software as well as the FlexRay-bootloader for the five ECUs controlling the suspension. Furthermore, EB supplied the protocol-logic design for the Freescale MFR4200 FlexRayController..

The CompanyHeadquartered in Munich, Germany, the BMW AG is one of the major manufacturers of performance and luxury cars. It owns and produces the MINI brand, and is the parent company of Rolls-Royce Motor Cars. BMW produces more than one million cars per year.

The ChallengeThe 2007 BMW X5 was the first production vehicle to use FlexRay.

Five ECUs interconnected via a FlexRay bus system were to control the stabilizers and electromagnetic valves of the dampers in order toenable BMW’s Adaptive Drive to eliminate the effect of body roll on the vehicle.

Success StoryFlexRay for BMW X5

Company confidential / Copyright Elektrobit Corporation 2011

We take AUTOSAR to the road!

Elektrobit Automotive SoftwareAm Wolfsmantel 46 · 91058 Erlangen

+49 9131 7701-0 · Fax +49 9131 7701-333 [email protected]

www.elektrobit.com

eb tresos product line introduction - hanser...

Documents