This content is not included in your SAE MOBILUS subscription, or you are not logged in.
Software Development for Multiple OEMs Using Tool Configured Middleware for CAN Communication
ISSN: 0148-7191, e-ISSN: 2688-3627
Published March 05, 2001 by SAE International in United States
Annotation ability available
Event: SAE 2001 World Congress
Years ago car manufacturers started using reusable software components for the development of ECU applications. As communication between ECUs is not a competitive advantage, there has been a lot of standardization efforts, especially in Europe. Whereas the standards for Operating Systems and Network Managements are widely accepted and used, all major OEMs created their own versions of Communication Modules, which presents a major roadblock for OEM independent ECU development. We show how the OEM specifics can be hidden by using a tool configured middleware.
CitationJost, P. and Hoffmann, S., "Software Development for Multiple OEMs Using Tool Configured Middleware for CAN Communication," SAE Technical Paper 2001-01-0110, 2001, https://doi.org/10.4271/2001-01-0110.
- “CAN Specification Version 2.0” Robert Bosch GmbH Schwieberdingen, Germany
- Etschberger K. “CAN; Grundlagen, Protokolle, Bausteine, Anwendugnen” Konrad Etschberger Hanser 1994
- Lawrenz W. “CAN System Engineering - From Theory to Practical Application” Springer Verlag New York Berlin, Heidelberg 1997
- Baudermann B. “CAN-Kommunikation als Softwarekomponenten für Kfz-Steuergeräte” Embedded Intelligence 2000 Design&Elektronik 2000
- “Interaction Layer, User's Manual Version 1.4” Vector Informatik GmbH Stuttgart, Germany
- “OSEK/VDX Communication, Version 2.2” 1999
- Chan C. et al. “Feature Oriented Domain Analysis (FODA). A Feasibility Study” SEI Carnegie Mellon University 1991
- Eisenecker U. Czarnecki K. Generative Programming Addison Wesley 2000