Powertrain Strategies for the 21st Century: Designing Global Powertrains

Transcription

1 Powertrain Strategies for the 21st Century: Designing Global Powertrains Joe Capuano, Regional Business Unit Leader, Diesel and Gasoline Engine Controls 1

2 Embedded System Advancement Challenges: Management of global customer platforms Multi-core + FlexIO 16/32-bit + ASIC 8-bit + discrete Model/Autocode IP/Know-how C/C++ protection Assembler AUTOSAR/SW-Sharing Sharing OEM specs Supplier functions System level testing, FMEA, FTA Fun2Drv/FE/Emis Turn-key Linear development HW independent SW Software maintenance V-model PFI Alt-Fuel/Hybrid/EV GDI/ETC Innovation management Adv Combustion Validation and Verification Increased Customer Demands Increased Reuse & Cooperation 2

3 AUTOSAR Software Sharing 3

4 9 Core Partners 21 Development Members 86 Associate Members 50 Premium Members 10 Attendees General OEM Generic Tier 1 Standard Software Tools and Services Semiconductors source: (2012) 4

5 Standardization Architecture Basic Software Methodology Application Interfaces Architecture Basic Software Specification of a complete basic software layer as integration platform for hardware independent application software. Application Interfaces Specification of standardized interfaces of mature automotive applications from all domains as bases for application software. Methodology Common exchange formats or description templates to enable seamless co-operation during the complete development process. 5

6 Bosch PT-ECU Roadmap to Legacy Base SW: SW sharing based on AUTOSAR AUTOSAR SW from Bosch and OEM Interim Product: Stepwise migration to AUTOSAR based on customer request BSW from CUBAS Mixed Mode in ASW Future Product: AUTOSAR compliant ECU based on CUBAS Mixed Mode in Application SW Legacy Sw-C AU TOSAR Adapter AUTOSAR Sw-C RTE AUTOSAR Adapter Legacy Sw-C Legacy Adapter AUTOSAR Compliant Sw-C RTE Legacy Sw-C AUTOSAR Compliant Sw-C RTE Legacy BSW Legacy BSW CUBAS CDD CUBAS AUTOSAR BSW CUBAS = Common Base SW RTE = Run-time environment CDD = Complex Device Driver 6

7 AUTOSAR Software Sharing 7

8 SW Sharing (w/o AUTOSAR) OEM Specs *.C, *.obj Tier1 Interface CODE SPEC SHARING OEM: Source/Obj Function spec code Interface SW system description test cases Integration Validation of test eng/veh cases SW functions system before test cases delivery Supplier: Interface Test cases adapter generation SW Function integration/testing coding/testing SW system integration/testing testing S system testing 8

9 SW Sharing (w/ AUTOSAR) *.C, *.obj AUTOSAR Interface CODE SHARING OEM: AUTOSAR BSW/App interface, & Interface descriptions Integration test cases SW system test cases Supplier: Interface adapter SWintegration/testing SW system testing 9

10 Outport2SendMessage Realization Elements LHS RHS Realization Elements Realization Elements system : SDModule system : SLSystem module-modulevariable system-systemelement source : SLBlock blocktype = =Outport source : SDElement, SDPrimitive elementname = name.value primitive-primitiveimplproperties owner-attribute primitive-primitiveproperties : SDElement, Properties name : MDLString, MDLElement {ID=elementID} : SDElement, ImplProperties elementname = =Name elementid = "sdp_"+source.elementid {ID=elementID} issetter = >true elementid = "sdip_"+source.elementid scope = >exported kind = >variable SLBlock +blocktype : String -BlockSubsystem2Folder() -BlockSubsystem2FolderAlg() -Inport2ReceiveMessage() -Outport2SendMessage() -SLBlock2SDClass() -SLBlock2SDClassAlg() Management of Global Powertrain Requirements Model Exchange (w/o AUTOSAR) Models M2M MODEL EXCHANGE Challenges: Different tool OEMs with specific adaptations Different modeling guidelines Model Conversion Approach: Increase model compatability by industrialiazation of Sw based on AUTOSAR 10

11 Model Exchange (w/ AUTOSAR) AUTOSAR MODEL EXCHANGE Models Common guideline Standardized libraries, efficient usage or resources Independence of tool version/supplier No dependency on supplier s modeling style Win-Win for OEM- Suppliers-Tool l Provider 11

12 VeMotionSAR - Architecture based development Definition of software structure according to functional and nonfunctional (e.g. reuse, distributable) requirements Driver for functional unification by one common SW architecture Specification of interfaces and task orders VeMotionSAR h ti / 12

13 Dev Tools Vehicle Simulator MCD Tools MiL/HiL/SiL re Hardwa Managing Global Powertrain Development Core Dig Periphe erals Standardization inter/intra systems Modular Design / Reuse Flexibility Cooperation Torq que Secu urity En g/veh Fun nctions Cal libration Auto Code Modeling Software Rapid Prototyping 13

14 Thank you for your attention! 14