Component Implementation

• 1: EcuTMeas Review
• 2: EcuTMeas_IntegrationManual
• 3: EcuTMeas_MDD
• 4: requirements

1 - EcuTMeas Review

Rev 1.2

8-Jun-15

Peer Review Summary Sheet

Synergy Project Name:

kzshz2: Intended Use: Identify which component is being reviewed. This should be the Module Short Name from Synergy Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. ES210A_EcuTMeas_Impl

Revision / Baseline:

kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. ES210A_EcuTMeas_Impl_1.4.0

Change Owner:

kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Spandana Balani

Work CR ID:

EA4#5624

kzshz2: Intended Use: Intended to identify at a high level to the reviewers which areas of the component have been changed. Rationale: This will be good information to know when ensuring appropriate reviews have been completed. Modified File Types:

kzshz2: Intended Use: Identify who where the reviewers, what they reviewed, and if the reviewed changes have been approved to release the code for testing. Comments here should be at a highlevel, the specific comments should be present on the specific review form sheet. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. ADD DR Level Move reviewer and approval to individual checklist form Review Checklist Summary:

Reviewed:

N/A

MDD

N/A

Source Code

N/A

PolySpace

N/A

Integration Manual

N/A

Davinci Files

Comments:

Rebaselined to include updated design subproject

General Guidelines: - The reviews shall be performed over the portions of the component that were modified as a result of the Change Request. - New components should include FDD Owner and Integrator as apart of the Group Review Board (Source Code, Integration Manual, and Davinci Files) - Enter any rework required into the comment field and select No. When the rework is complete, review again using this same review sheet and select Yes. Add date and additional comment stating that the rework is completed. - To review a component with multiple source code files use the "Add Source" button to create a Source code tab for each source file. - .h file should be reviewed with the source file as part of the source file.

2 - EcuTMeas_IntegrationManual

Integration Manual

For

ECU TEMPERATURE MEASUREMENT

VERSION: 2.0

DATE: 21-MAR-2016

Prepared By:

Krishna Anne,

Nexteer Automotive,

Saginaw, MI, USA

Revision History

Table of Contents

1 Abbrevations And Acronyms 4

2 References 5

3 Dependencies 6

3.1 SWCs 6

3.2 Global Functions(Non RTE) to be provided to Integration Project 6

4 Configuration REQUIREMeNTS 7

4.1 Build Time Config 7

4.2 Configuration Files to be provided by Integration Project 7

4.3 Da Vinci Parameter Configuration Changes 7

4.4 DaVinci Interrupt Configuration Changes 7

4.5 Manual Configuration Changes 7

5 Integration DATAFLOW REQUIREMENTS 8

5.1 Required Global Data Inputs 8

5.2 Required Global Data Outputs 8

5.3 Specific Include Path present 8

6 Runnable Scheduling 9

7 Memory Map REQUIREMENTS 10

7.1 Mapping 10

7.2 Usage 10

7.3 Non RTE NvM Blocks 10

7.4 RTE NvM Blocks 10

8 Compiler Settings 11

8.1 Preprocessor MACRO 11

8.2 Optimization Settings 11

9 Appendix 12

Abbrevations And Acronyms

References

This section lists the title & version of all the documents that are referred for development of this document

Dependencies

SWCs

Global Functions(Non RTE) to be provided to Integration Project

Configuration REQUIREMeNTS

Build Time Config

Configuration Files to be provided by Integration Project

Include NxtrFil.h in Rte_UserTypes.h header file

Da Vinci Parameter Configuration Changes

DaVinci Interrupt Configuration Changes

Manual Configuration Changes

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file

Required Global Data Outputs

Refer DataDict.m file

Specific Include Path present

No

Runnable Scheduling

This section specifies the required runnable scheduling.

Memory Map REQUIREMENTS

Mapping

* Each …START_SEC… constant is terminated by a …STOP_SEC… constant as specified in the AUTOSAR Memory Mapping requirements.

Usage

Table 1: ARM Cortex R4 Memory Usage

Non RTE NvM Blocks

Note : Size of the NVM block if configured in developer

RTE NvM Blocks

Note : Size of the NVM block if configured in developer

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

3 - EcuTMeas_MDD

Module Design Document

For ECU Temperature Measurement

VERSION: 2.0

DATE: 21-MAR-2016

Prepared By:

Krishna Anne,

Nexteer Automotive,

Saginaw, MI, USA

Revision History

Table of Contents

1 Abbrevations And Acronyms 5

2 References 6

3 Ecutmeas & High-Level Description 7

4 Design details of software module 8

4.1 Graphical representation of Ecutmeas 8

4.2 Data Flow Diagram 8

4.2.1 Module level DFD 8

4.2.2 Sub-Module level DFD 8

4.3 COMPONENT FLOW DIAGRAM 8

5 Constant Data Dictionary 9

5.1.1.1 9

5.1.2 Module specific Lookup Tables Constants 9

6 Software Module Implementation 10

6.1 Sub-Module Functions 10

6.1.1 Initialization Functions 10

6.1.1.1 INIT: EcuTMeasINIT1 10

6.1.1.2 Design Rationale 10

6.1.1.3 Store Module Inputs to Local copies 10

6.1.1.4 (Processing of function)……… 10

6.1.1.5 Store Local copy of outputs into Module Outputs 10

6.1.2 PERIODIC FUNCTIONS 10

6.1.2.1 Per: EcuTMeasPer1 10

6.1.2.2 Design Rationale 10

6.1.2.3 Store Module Inputs to Local copies 10

6.1.2.4 (Processing of function)……… 10

6.1.2.5 Store Local copy of outputs into Module Outputs 10

6.2 Interrupt Functions 10

6.3 Serial Communication Functions 11

6.4 Local Function/Macro Definitions 11

6.5 GLObAL Function/Macro Definitions 11

6.6 TRANSIENT FUNCTIONS 11

7 Known Limitations With Design 12

8 UNIT TEST CONSIDERATION 13

9 Appendix 14

Abbrevations And Acronyms

References

This section lists the title & version of all the documents that are referred for development of this document

Ecutmeas & High-Level Description

Measures and diagnoses thermistor on ECU.

Design details of software module

Graphical representation of Ecutmeas

Data Flow Diagram

Module level DFD

N/A

Sub-Module level DFD

N/A

COMPONENT FLOW DIAGRAM

N/A

Variable definition for enumerated types

Constant Data Dictionary

Module specific Lookup Tables Constants

Software Module Implementation

Sub-Module Functions

None

Initialization Functions

INIT: EcuTMeasINIT1

Design Rationale

Per FDD author intent is to use standard Nexteer FilLp functions

Store Module Inputs to Local copies

Refer to FDD

(Processing of function)………

Refer to FDD

Store Local copy of outputs into Module Outputs

Refer to FDD

PERIODIC FUNCTIONS

(Note: For multiple periodic functions, insert new headers at the “Header 2” level – subset of “7.1.2 Periodic Functions” and follow the same sub-section design shown below). If none required, place the text “None”)

Per: EcuTMeasPer1

Design Rationale

Per FDD author intent is to use standard Nexteer FilLp functions

Store Module Inputs to Local copies

Refer to FDD

(Processing of function)………

Refer to FDD

Store Local copy of outputs into Module Outputs

Refer to FDD

Interrupt Functions

None

Serial Communication Functions

None

Local Function/Macro Definitions

Local Function #1

None

GLObAL Function/Macro Definitions

GLObAL Function #1

N/A

TRANSIENT FUNCTIONS

None

Known Limitations With Design

None

UNIT TEST CONSIDERATION

1. The Per Instance Memory in .m file EcuTMeasFilStVarPrev given as float32 type, represents the State variable of the filter FilSt, element of the struct FilLpRec1

   1. Range of Rte_Pim_EcuTMeasFilStVarPrev.FilSt is the range given in the .m file

2. the equation to calculate filter gain is:

FilGain = 1 - exp(-2PI * FrqPole * TiStep)

1. FrqPole is Rte_Prm_EcuTMeasFilTau_Val

2. TiStep is 100ms

3. Range of Rte_Pim_EcuTMeasFilStVarPrev.FilGain is calculated using the range of Rte_Prm_EcuTMeasFilTau_Val

3. The equation to calculate the filter output is:

Outp = ((Inp - FilSt) * FilGain) + FilSt

Appendix

None

4 - requirements