EcuTMeas_MDD

Module Design Document

For

EcuTMeas

26-Sep-2017

Prepared By:

Brendon Binder,

Nexteer Automotive,

Saginaw, MI, USA
Change History

Table of Contents

1 Introduction 4

1.1 Purpose 4

2 EcuTMeas & High-Level Description 5

3 Design details of software module 6

3.1 Graphical representation of EcuTMeas 6

3.2 Data Flow Diagram 6

3.2.1 Component level DFD 6

3.2.2 Function level DFD 6

4 Constant Data Dictionary 7

4.1 Program (fixed) Constants 7

4.1.1 Embedded Constants 7

5 Software Component Implementation 8

5.1 Sub-Module Functions 8

5.1.1 Init: EcuTMeasInit1 8

5.1.1.1 Design Rationale 8

5.1.2 Per: EcuTMeasPer1 8

5.1.2.1 Design Rationale 8

5.2 Server Runables 8

5.3 Interrupt Functions 8

5.4 Module Internal (Local) Functions 8

5.4.1 Local Function #1 8

5.4.1.1 Design Rationale 8

5.5 GLOBAL Function/Macro Definitions 8

5.5.1 GLOBAL Function #1 8

6 Known Limitations with Design 9

7 UNIT TEST CONSIDERATION 10

Appendix A Abbreviations and Acronyms 11

Appendix B Glossary 12

Appendix C References 13

Introduction

Purpose

Module design document for EcuTMeas

EcuTMeas & High-Level Description

Measures and diagnoses an analog based temperature sensor on ECU.

This particular design can tolerate a transfer function that is not necessarily linear but can be interpolated with 8 different XY pairs.

Design details of software module

Graphical representation of EcuTMeas

Data Flow Diagram

Component level DFD

Refer FDD simulink model

Function level DFD

Refer FDD simulink model

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

*This the value might change based on EcuTx and EcuTy table size.

Software Component Implementation

Sub-Module Functions

Init: EcuTMeasInit1

Refer FDD simulink model

Design Rationale

‘Filter Initialization’ block in the FDD uses ‘FilLpInit’ library block twice rather than just once due to a design limitation with the Library block (see ‘Known limitations with design’). However, code has no such limitation. In code, the value to be written to the state variable according to the logic in ‘State Variable Initialization’ is calculated first. Then, the ‘FilLpInit’ library function is called just once and that will initialize the state variable with this calculated value and the gain according to the set frequency & time.

Per: EcuTMeasPer1

Refer FDD Simulink Model

Design Rationale

None

Server Runables

None

Interrupt Functions

None

Module Internal (Local) Functions

Local Function #1

Design Rationale

N/A

GLOBAL Function/Macro Definitions

GLOBAL Function #1

Known Limitations with Design

1. The FilLpInit block in the model cannot accept a variable as input for initialization of the state variable.

UNIT TEST CONSIDERATION

1. This component uses config params for some configurable constants. However for testing these in PIL/SIL, please use the following strategy:

   1. Rename the EcuTMeas_Cfg_private_pil.h file in tools/local/include folder to EcuTMeas_Cfg_private.h

   2. Replace the EcuTMeas_Cfg_private.h file in tools/local/generate folder with the above file.

Now, Tessy must be able to modify the values of these config params. We should then test them with the range that is given in their definition in the DataDict.m file

Abbreviations and Acronyms

Glossary

Note: Terms and definitions from the source “Nexteer Automotive” take precedence over all other definitions of the same term. Terms and definitions from the source “Nexteer Automotive” are formulated from multiple sources, including the following:

• ISO 9000

• ISO/IEC 12207

• ISO/IEC 15504

• Automotive SPICE® Process Reference Model (PRM)

• Automotive SPICE® Process Assessment Model (PAM)

• ISO/IEC 15288

• ISO 26262

• IEEE Standards

• SWEBOK

• PMBOK

• Existing Nexteer Automotive documentation

References