MotTqCalcd_MDD
Module Design Document
For
MotTqCalcd
Prepared For:
,
Prepared By:
TATA ELXSI,
INDIA
Change History
| Description | Author | Version | Date |
| Initial version | TATA ELXSI | 1 | 13-Mar-2018 |
Table of Contents
2 MotTqCalcd & High-Level Description 5
3 Design details of software module 6
3.1 Graphical representation of MotTqCalcd 6
4.1 Program (fixed) Constants 7
5 Software Component Implementation 8
5.4 Module Internal (Local) Functions 9
5.5 GLOBAL Function/Macro Definitions 9
6 Known Limitations with Design 10
Appendix A Abbreviations and Acronyms 12
Introduction
Purpose
Module Design Document for SF067A_MotTqCalcd_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.
MotTqCalcd & High-Level Description
This function calculates motor torque estimate from measured Motor Currents or reference MotorCurrents based on the Motor Control and Thermal Protection LOA Mode.
Design details of software module
Graphical representation of MotTqCalcd

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 Name | Resolution | Units | Value |
|---|---|---|---|
Refer SF067A_MotTqCalcd_DataDict.m
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: MotTqCalcdInit1
Design Rationale
Refer FDD
Module Outputs
Refer FDD
Init: MotTqCalcd_Init
Design Rationale
This init function is generated by embedded coder and is not present in the Simulink model.
This function is always empty and is not called.
Module Outputs
There are no outputs for this function.
Per: Per1
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
None
GLOBAL Function/Macro Definitions
None
Known Limitations with Design
None
UNIT TEST CONSIDERATION
None
Abbreviations and Acronyms
| Abbreviation or Acronym | Description |
|---|---|
| FDD | Functional 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
| Term | Definition | Source |
|---|---|---|
| MDD | Module Design Document | |
| DFD | Data Flow Diagram |
References
| Ref. # | Title | Version |
|---|---|---|
| 1 | AUTOSAR Specification of Memory Mapping (Link:AUTOSAR_SWS_MemoryMapping.pdf) | v1.4.0 R4.0 Rev 3 |
| 2 | MDD Guideline EA4 | 1.02 |
| 3 | EA4 Software Naming Conventions | 1.0.3 draft |
| 4 | Software Design and Coding Standards | 3.0 draft |
| 5 | SF067A_MotTqCalcd_Design | See Synergy Sub Project Version |