This content is not included in your SAE MOBILUS subscription, or you are not logged in.
From the Napkin to Autocode, a Body Control Module Software Development Journey
ISSN: 0148-7191, e-ISSN: 2688-3627
Published March 28, 2017 by SAE International in United States
Annotation ability available
The Body Control Module (BCM) is a very large integration site for vehicle features and functions (e.g., Locking, Alarms, interior lighting, exterior lighting, etc…). Every few years the demand to add more feature/functions and integrate more vehicle content increases. The expectation of the 2013 MY (model year) BCM, was to double the feature content and use it globally. The growth in 3 years of feature/function content was huge number that grew from 150 to over 300. This posed a major challenge to the software development team based on the methods and process that were deployed at the time. This paper cites the cultural and technology changes that were overcome when Ford Motor Company partnered with Tata Consultancy Services to help manage and define this new software engineering development methodology. The process of getting from a vague description of a new body module feature to a saleable product, presents several very challenging problems.
|Technical Paper||Systems Engineering Efforts - What, When and How Much?|
|Ground Vehicle Standard||Determination of the Effective Projected Luminous Lens Area (EPLLA) by Design Analysis|
|Technical Paper||The Use of LED Lamps for Turn and Stop Signal Presentations|
CitationBrombach, R. and Gadkari, A., "From the Napkin to Autocode, a Body Control Module Software Development Journey," SAE Technical Paper 2017-01-1622, 2017, https://doi.org/10.4271/2017-01-1622.
- The Intel 4004 is a 4-bit central processing unit (CPU) released by Intel Corporation in 1971. It was the first commercially available microprocessor by Intel. -Wikipedia
- MROM was a process where the silicon manufacturer would embed the software logic into the microcontroller silicon itself. The software was not modifiable after manufacturing of the microcontroller.
- Patent number 6133827 Speed dependent Vehicle Courtesy Lamp Control for an Automobile. Ron Brombach and Ray Alvey October 17, 2000
- Behavioral models are used in the MatLab environment for simulation and testing. The data types defined in this environment are either Float or Real numbers. They are not intended to be used for auto generation of the code. The data types need to be converted to the target micro controller platform, generally a fix point or integer number, which are referred to implementation models.
- MathWorks Automotive Advisory Board, https://www.mathworks.com/solutions/automotive/standards/maab.html
- MCDC –Modified condition/decision coverage analysis by the Simulink Verification toolbox.