FordMsg3D3BusHiSpd_MDD

Module Design Document

For

FordMsg3D3BusHiSpd

April 20, 2018

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

TATA ELXSI,

INDIA


Change History

DescriptionAuthorVersionDate
Initial versionTATA ELXSI120-Apr-2018


Table of Contents

Table of Contents 3

1 Introduction 5

1.1 Purpose 5

1.2 Scope 5

2 FordMsg3D3BusHiSpd & High-Level Description 6

3 Design details of software module 7

3.1 Graphical representation of FordMsg3D3BusHiSpd 7

3.2 Data Flow Diagram 7

3.2.1 Component level DFD 7

3.2.2 Function level DFD 7

4 Constant Data Dictionary 8

4.1 Program (fixed) Constants 8

4.1.1 Embedded Constants 8

5 Software Component Implementation 9

5.1 Sub-Module Functions 9

5.1.1 Init: FordMsg3D3BusHiSpdInit1 9

5.1.2 Per: FordMsg3D3BusHiSpdPer1 9

5.2 Server Runables 9

5.3 Interrupt Functions 9

5.4 Module Internal (Local) Functions 10

5.4.1 Local Function #1 10

5.4.1.1 Design Rationale 10

5.4.1.2 Processing 10

5.4.2 Local Function #2 10

5.4.2.1 Design Rationale 11

5.4.2.2 Processing 11

5.4.3 Local Function #3 11

5.4.3.1 Design Rationale 11

5.4.3.2 Processing 11

5.4.4 Local Function #4 11

5.4.4.1 Design Rationale 12

5.4.4.2 Processing 12

5.4.5 Local Function #5 13

5.4.5.1 Design Rationale 13

5.4.5.2 Processing 13

5.5 GLOBAL Function/Macro Definitions 13

6 Known Limitations with Design 14

7 UNIT TEST CONSIDERATION 15

Appendix A Abbreviations and Acronyms 16

Appendix B Glossary 17

Appendix C References 18

Introduction

Purpose

Module Design Document for MM074A_FordMsg3D3BusHiSpd_Impl.

Scope

The following definitions are used throughout this document:

  • Shall: indicates a mandatory requirement without exception in compliance.

  • Should: indicates a mandatory requirement; exceptions allowed only with documented justification.

  • May: indicates an optional action.

FordMsg3D3BusHiSpd & High-Level Description

The purpose of the Ford Message 3D3 Bus High Speed function is to provide the Electric Power Steering system with signal values for the Traffic Jam Assist and Lane Center Assist functions from CAN. The Ford Message 3D3 function will perform the missing message as well as provide a validity flag for the signal values and received message.

Design details of software module

Graphical representation of FordMsg3D3BusHiSpd

Data Flow Diagram

Refer FDD

Component level DFD

Refer FDD

Function level DFD

Refer FDD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Constant NameResolutionUnitsValue
Please Refer DDNANANA

Software Component Implementation

Sub-Module Functions

The sub-module functions are grouped based on similar functionality that needs to be executed in a given “State” of the system (refer States and Modes). For a given module, the MDD will identify the type and number of sub-modules required. The sub-module types are described below.

Init: FordMsg3D3BusHiSpdInit1

Design Rationale

Refer FDD

Module Outputs

Refer FDD

Per: FordMsg3D3BusHiSpdPer1

Design Rationale

Refer FDD

Store Module Inputs to Local copies

Refer FDD

(Processing of function)………

Refer FDD

Store Local copy of outputs into Module Outputs

Refer FDD

Server Runables

None

Interrupt Functions

None

Module Internal (Local) Functions

Local Function #1

Function NameDiagEnaTypeMinMax
Arguments PassedFordTrlrBackupAssiEnad_Cnt_T_loglboolean0U1U
FordCanDtcInhb_Cnt_T_loglboolean0U1U
ClrDiagcFlgProxy_Cnt_T_u08uintt80U255U
*MissMsgDiagEna_Cnt_T_loglboolean0U1U
*ClrDiagcFlgProxyEna_Cnt_loglboolean0U1U
Return Value

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM074A_FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpdPer1

Local Function #2

Function NameMissMsgTypeMinMax
Arguments PassedFordEpsLifeCycMod_Cnt_T_u08uint80U255U
MissMsgDiagEna_Cnt_T_loglboolean0U1U
ClrDiagcFlgProxyEna_Cnt_loglboolean0U1U
*FordVehLatCtrlRampTyp_Cnt_T_enumFloat32-.02F0.02094F
*FordVehLatCtrlPrcsn_Cnt_T_enumEnum0U3U
*FordVehLatCtrlCrvt_IvsMtr_T_f32Float32-.02F0.02094F
*FordVehLatCtrlCrvtRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlPah_Rad_T_f32Float32-0.5F0.5235F
*FordVehLatCtrlPahRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlPahOffs_Mtr_T_f32Float32-5.12F5.11F
*FordVehLatCtrlPahOffsRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlCrvtRate_IvsMtr_T_f32Float32-0.001024F0.00102375F
*FordVehLatCtrlCrvtRateRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlReq_Cnt_T_enumEnum0U7U
*FordVehLatCtrlRingMax_Cnt_T_u08uint80U255U
*FordVehLatCtrlHandsOffDetnTqStimlsReq_Cnt_T_enumEnum0U1U
*FordVehLatCtrlImgProcrModlAVld_Cnt_T_u16uint160U65535U
Return Value

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM074A_FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpdPer1

Local Function #3

Function NameFordMsg3D3MissMsgFailTypeMinMax
Arguments PassedBusHiSpdMissThd_Cnt_T_u16uint16065535
MissMsgDiagEna_Cnt_T_loglboolean0U1U
ClrDiagcFlgProxyEna_Cnt_loglboolean0U1U
Return Value

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM074A_FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpdPer1/FordMsg3D3MsgMiss

Local Function #4

Function NameMsgPrsntTypeMinMax
Arguments PassedFord_LatCtlRampType_D_Rq_Cnt_enumEnum0U3U
Ford_LatCtlPrecision_D_Rq_Cnt_enumEnum0U3U
Ford_LatCtlCurv_No_Actl_Cnt_T_u16uint160U65535U
Ford_LatCtlPath_An_Actl_Cnt_T_u16uint160U65535U
Ford_LatCtlPathOffst_L_Actl_Cnt_T_u16uint160U65535U
Ford_LatCtlCurv_NoRate_Actl_Cnt_T_u16uint160U65535U
Ford_LatCtl_D_Rq_Cnt_T_enumEnum0U7U
Ford_LatCtlRng_L_Max_Cnt_T_u08uint80U255U
Ford_HandsOffCnfm_B_Rq_Cnt_T_enumEnum0U1U
FordEpsLifeCycMod_Cnt_T_u08uint80U255U
MissMsgDiagEna_Cnt_T_loglboolean0U1U
ClrDiagcFlgProxyEna_Cnt_loglboolean0U1U
*FordVehLatCtrlRampTyp_Cnt_T_enumFloat32-.02F0.02094F
*FordVehLatCtrlPrcsn_Cnt_T_enumEnum0U3U
*FordVehLatCtrlCrvt_IvsMtr_T_f32Float32-.02F0.02094F
*FordVehLatCtrlCrvtRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlPah_Rad_T_f32Float32-0.5F0.5235F
*FordVehLatCtrlPahRaw_Cnt_T_u16uint160U65535
*FordVehLatCtrlPahOffs_Mtr_T_f32Float32-5.12F5.11F
*FordVehLatCtrlPahOffsRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlCrvtRate_IvsMtr_T_f32Float32-0.001024F0.00102375F
*FordVehLatCtrlCrvtRateRaw_Cnt_T_u16uint160U65535U
*FordVehLatCtrlReq_Cnt_T_enumEnum0U7U
*FordVehLatCtrlRingMax_Cnt_T_u08uint80U255U
*FordVehLatCtrlHandsOffDetnTqStimlsReq_Cnt_T_enumEnum0U1U
*FordVehLatCtrlImgProcrModlAVld_Cnt_T_u16uint160U65535U
Return Value

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM074A_FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpdPer1

Local Function #5

Function NameFordMsg3D3MissMsgPassTypeMinMax
Arguments PassedMissMsgDiagEna_Cnt_T_loglboolean0U1U
ClrDiagcFlgProxyEna_Cnt_loglboolean0U1U
Return Value

Design Rationale

Processing

Please refer to the below path in the FDD model.

MM074A_FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpd/FordMsg3D3BusHiSpdPer1/FordMsg3D3MsgMiss

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

None

Abbreviations and Acronyms

Abbreviation or AcronymDescription
FDDFunctional Design Document. (See references)

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

TermDefinitionSource
MDDModule Design Document
DFDData Flow Diagram

References

Ref. #TitleVersion
1AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf)v1.4.0 R4.0 Rev 3
2MDD Guideline EA41.02
3EA4 Software Naming Conventions1.0.3 draft
4Software Design and Coding Standards3.0 draft
5MM074A_FordMsg3D3BusHiSpd_DesignSee Synergy Sub Project Version
Last modified October 12, 2025: Initial commit (ddf2e20)