Component Design
Component Documentation
- EA4-x NTC 0x0A3(0) Duty Cycle Exceeded.html
- EA4-x NTC 0x0A4(0-2) Absolute Temperature Thermal Limit.html
- SF009A_DutyCycThermProtn_Design_PeerReviewChkList.html
This is the multi-page printable view of this section. Click here to print.
NTC Overview
NTC 0x0A3.0 Duty Cycle Exceeded
(Reduced Performance)
Description:
•This diagnostic logs a fault when the thermal duty cycle filters exceed a calibrated threshold relative to thermal duty cycle performance.
Diagnostic Overview:
•Thermal duty cycle performance is customer specific and the duty cycle filter calibrations are designed to meet the specification while thermally protecting system components.
•The duty cycle filters monitor the current load supplied to the components (which is directly related to power loss and hence temperature rise) . If the current level and duration is above a specified performance, a limit is applied via a thermal limit table and a flag is set when the filter max output exceeds a calibrated limit.
Typical Fault Response:
•Response for this diagnostic is F3
•This is a recoverable fault that clears once the max filter output falls below the threshold within an ignition cycle.
 
Probable Sources 
(Most to Least Probable):
•High current input for extended period of time.
•Excessive steering usage by the driver.
| Initialization | |
| Periodic | X | 
| Event | 
| Date | Revision | Initials | 
| 08FE16 | Initial Release | JK | 
| Description of Unusual Event setting NTC | Root Cause / Explanation | 
| Date | FDD & Rev | Modifications to Diagnostic Function | 
Algorithm Changes / Lessons Learned / Revision Log
NTC Overview
NTC 0x0A4.(0-2) Absolute Temperature Thermal Limit
Description:
•This diagnostic logs a fault when either the controller temperature or copper temperature estimate exceed calibrated values.
Diagnostic Overview:
•The system components are designed to operated below specific temperature thresholds. If these threshold values are exceeded, a limit is applied to the system via limit tables to protect the components, and a diagnostic flag is set.
•This is a recoverable fault that clears once the controller temperature or copper temperature fall below the calibrated thresholds. 
 
Typical Fault Response:
•Response for this diagnostic is F3.
•This fault is recoverable once the temperature values fall below the threshold within an ignition cycle.
 
Probable Sources 
(Most to Least Probable):
•Excessive system usage
•System is exposed to high ambient temperature.
| Initialization | |
| Periodic | X | 
| Event | 
| Bit | Cause | 
| 0 | Limiting due to Controller Temperature | 
| 1 | Limiting due to Copper Temperature | 
| 2 | Limiting due to Both Temperatures | 
| Date | Revision | Initials | 
| 08FE16 | Initial Release | JK | 
| 10Au16 | Update the bits table with 3 bits used in the NTC | PP | 
| Description of Unusual Event setting NTC | Root Cause / Explanation | 
| Date | FDD & Rev | Modifications to Diagnostic Function | 
Algorithm Changes / Lessons Learned / Revision Log
| Instructions for Functional Design Package Peer Review | ||
| PRE-MEETING | ||
| Function Owner | Confirm that requirements are reviewed and approved PRIOR to the FDP peer review | |
| Function Owner | Start with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews | |
| Function Owner | Provide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review | |
| Function Owner | Notify the assigned peer reviewer and make sure they are prepared to do their function in the meeting | |
| Function Owner | Identify necessary attendance and invite to meeting | |
| Function Owner | Complete the "Author" column information for sections 1 through 5 prior to the review | |
| Function Owner | Complete the attendance invitation list in section 7 | |
| Function Owner | For Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews. | |
| DURING MEETING | ||
| Function Owner | Present document changes to the review team | |
| Peer Reviewer | Capture attendance of the review | |
| Peer Reviewer | Capture actions and issues in section 6. Identify issue summary, Document type, Reference (Requirement ID, section number, etc), Defect Type and indicate status as "OPEN" | |
| POST MEETING | ||
| Function Owner | Follow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided. | |
| Function Owner | Schedule follow up review OR review open items with peer reviewer and obtain agreement to close | |
| Peer Reviewer | Close change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates | 
| Rev | Change | Author | 
| 01.00.05 | Added lesson learned #3.5 | MDK | 
| 01.00.06 | Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models. | MDK | 
| 02.00.00 | Combined ESG and Systems into one, compatible with Data_Management 2.13.0 of CreateDD and VerifyDD. | K. Derry | 
| 02.01.00 | Added: Does FDD.DesignASIL match requirements? Added: Was webview model created without requirements highlighted? Removed: Redundant row in Data Dictionary section. Formatting: Column C now consistently center-justified. | K. Derry | 
| 02.02.00 | Added: Are all data types represented by released Data_Management classes? Removed: Are all runnables defined? Rationale: Automated tools checking. Removed: Does the Component shortname match data dictionary FDD metadata? Removed: "Data store name must resolve to Simulink signal object" Edited: Model Advisor report should now be left unzipped. | K. Derry | 
| Model Advisor Report - SF009A_DutyCycThermProtn.slx | |
| Simulink version: 8.2 | Model version: 1.0.0 | 
| System: SF009A_DutyCycThermProtn | Current run: 21-Sep-2016 11:16:05 | 
| Model Advisor configuration: ...NxtrModelAdvisorConfig.mat | |
| Pass | Fail | Warning | Not Run | Total | 
|  |  |  |  | 200 | 
You should turn on the following optimization(s):
| none. | |
Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions
Warning
The following Inport blocks have undefined or inherited sample times, data types or port dimensions
| Inport | Link | Conditions | 
| 1 | SF009A_DutyCycThermProtn/In1 | Missing port dimension Missing signal data type Missing port sample time | 
| 2 | SF009A_DutyCycThermProtn/In2 | Missing port dimension Missing signal data type Missing port sample time | 
| 3 | SF009A_DutyCycThermProtn/In3 | Missing port dimension Missing signal data type Missing port sample time | 
| 4 | SF009A_DutyCycThermProtn/In4 | Missing port dimension Missing signal data type Missing port sample time | 
| 5 | SF009A_DutyCycThermProtn/In5 | Missing port dimension Missing signal data type Missing port sample time | 
| 6 | SF009A_DutyCycThermProtn/In6 | Missing port dimension Missing signal data type Missing port sample time | 
| 7 | SF009A_DutyCycThermProtn/In7 | Missing port dimension Missing signal data type Missing port sample time | 
| 8 | SF009A_DutyCycThermProtn/In8 | Missing port dimension Missing signal data type Missing port sample time | 
| 9 | SF009A_DutyCycThermProtn/In9 | Missing port dimension Missing signal data type Missing port sample time | 
| 10 | SF009A_DutyCycThermProtn/In10 | Missing port dimension Missing signal data type Missing port sample time | 
| 11 | SF009A_DutyCycThermProtn/In11 | Missing port dimension Missing signal data type Missing port sample time | 
Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.
Warning
The following blocks are not supported or not recommended for C/C++ production code deployment:
| Block | Block Type | Code generation support | Recommendation for C/C++ production code deployment | 
| SF009A_DutyCycThermProtn/Step | Step | Yes | No | 
| SF009A_DutyCycThermProtn/Step1 | Step | Yes | No | 
Compares the state machine type of all Stateflow charts to the desired type.
Check for Classic state machines
Identify Stateflow charts using the Classic state machine type.
Warning
The following charts using Classic state machines were found in the model:
Check for Mealy state machines
Identify Stateflow charts using the Mealy state machine type.
Passed
No charts using Mealy state machines were found in the model.
_________________________________________________________________________________________
Check for Moore state machines
Identify Stateflow charts using the Moore state machine type.
Passed
No charts using Moore state machines were found in the model.
| Name | Value | 
| State Machine Type | Common | 
Check Simulink blocks and Stateflow objects that do not link to a requirements document
Warning
The following blocks do not link to a requirement document:
Identify subsystem names that use characters that are not correct in C code.
See Also
| Error | Subsystem block | 
| Name contains incorrect characters. | ..../DutyCycThermProtnInit1/Get Error Status | 
| Name contains incorrect characters. | ..../DutyCycThermProtnEnabled | 
Identify names of Inport or Outport blocks that use characters that are not correct in C code.
See Also
| Error | Incorrect port block | 
| Name contains incorrect characters. | ..../FiltSVReinit/IgnTiOff | 
| Name contains incorrect characters. | ..../FiltSVReinit/ReInitCntrVal | 
Identify levels in the model that include basic blocks and subsystems. Each level of a model must be designed with blocks of the same level (for example, only subsystems or only basic blocks).
See Also
Identify nonstandard display attributes in Simulink diagrams.
See Also
Check format settings
Identify incorrect model-level format options.
Warning
The following format display options are incorrect.
| Display Attribute | Recommended Value | Actual Value | 
| Display > Signals & Ports > Wide Nonscalar Lines | on | off | 
| View > Model Browser Options > Model Browser | off | on | 
Check block colors
Identify blocks using nonstandard colors.
Warning
The following blocks use nonstandard colors:
Check canvas colors
Identify canvases that are not white.
Passed
All diagrams use a white canvas.
_________________________________________________________________________________________
Check diagram zoom
Identify diagrams that do not have zoom factor set to 100 %.
Warning
The following diagrams do not have zoom factor set to 100 percent:
Identify whether to display block names.
See Also
Check for blocks with hidden names and obvious function
Identify block names that are displayed but can be hidden due to obvious behavior.
Passed
All blocks with obvious behavior have hidden names.
_________________________________________________________________________________________
Check for non-descriptive displayed block names
Identify block names that are displayed but should be hidden due to a lack of a descriptive name.
Warning
The following blocks have a name displayed, however, the name is not descriptive:
Check for missing block names
Identify block names that are hidden but should be displayed to show a descriptive name.
Warning
The following blocks have descriptive names, however, the names are hidden:
Identify Trigger and Enable blocks that are not centered in the upper third of the model diagram.
See Also
Identify blocks that use and fail to display nondefault values.
See Also
| Block | Parameter | Expected Value | Actual Value | 
| ....tiplier 1 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ....tiplier 2 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ....tiplier 3 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ....tiplier 4 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ....tiplier 5 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ....tiplier 6 Non-Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 1 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 2 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 3 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 4 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 5 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../Multiplier 6 Stall Condition Table Lookup | LookUpMeth | Interpolation-Extrapolation | Use Input Below | 
| ..../TempratureLimiting/Lookup Table | LookUpMeth | Interpolation-Extrapolation | Interpolation-Use End Values | 
| ..../TempratureLimiting/Lookup Table1 | LookUpMeth | Interpolation-Extrapolation | Interpolation-Use End Values | 
Identify blocks that require labeled signals. A subset of source and destination blocks require labeled signals.
See Also
Check source block labels
The following source blocks require labeled signals; Inport, From, Data Store Read, Constant, Bus Selector, Demux, Selector. If the signal name is visible on the block, this rule is considered met.
Warning
The following signals have no label:
Check destination block labels
The following destination blocks require labeled signals; Outport, Goto, Data Store Write, Bus Creator, Mux, Subsystem, Chart. If the signal name is visible on the source block, this rule is considered met.
Warning
The following signals have no label:
Identify blocks that are not allowed in discrete controllers. Prohibited blocks include all continuous blocks and some source and sink blocks.
See Also
Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.
Warning
The following blocks are not supported or not recommended for C/C++ production code deployment:
| Block | Block Type | Code generation support | Recommendation for C/C++ production code deployment | 
| SF009A_DutyCycThermProtn/Step | Step | Yes | No | 
| SF009A_DutyCycThermProtn/Step1 | Step | Yes | No | 
Identify blocks that use zero-based indexing.
See Also
Identify transitions in Stateflow flowcharts that are drawn incorrectly.
See Also
Check for conditions drawn vertically
Condition expressions should be drawn on the horizontal segments of flowcharts.
Warning
The following transitions have condition expressions that are not horizontal:
Check for action transitions drawn vertically
Transition actions should be drawn on the vertical segments of flowcharts.
Warning
The following transitions have action expressions that are not vertical:
Check for junctions for default transitions
All Junctions in a flow chart should have a default exit transition.
Warning
The following Junctions do not have a default exit transition:
Check for transitions that combine condition and action
Flowcharts should not combine condition evaluations and action expressions in a single transition.
Warning
The following transition have a mixture of condition and assignment actions:
This model contains the following C-MEX S-functions:
Consider setting Solver data inconsistency [?] to either error or warning (currently set to none) to validate whether S-functions adhere to the ODE solver consistency rules that Simulink applies to its built-in blocks.
Consider setting ArrayBounds exceeded [?]to either error or warning (currently set to none) to check if S-functions are writing outside array boundaries.
Note: These runtime diagnostics may slow down simulation considerably. You should set them back to none once you have verified that they do not cause any warnings or errors during simulation.
SF009A_DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/Data Store Memory2
SF009A_DutyCycThermProtn/Data Store Memory3
SF009A_DutyCycThermProtn/Data Store Memory4
SF009A_DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/Data Store Memory9
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory10
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory11
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory12
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory26
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory27
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory31
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory32
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory33
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory34
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory35
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory5
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory8
SF009A_DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/Data Store Memory2
SF009A_DutyCycThermProtn/Data Store Memory3
SF009A_DutyCycThermProtn/Data Store Memory4
SF009A_DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/Data Store Memory9
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory10
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory11
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory12
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory26
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory27
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory31
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory32
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory33
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory34
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory35
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory5
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory8
SF009A_DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/Data Store Memory2
SF009A_DutyCycThermProtn/Data Store Memory3
SF009A_DutyCycThermProtn/Data Store Memory4
SF009A_DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/Data Store Memory9
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory1
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory10
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory11
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory12
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory26
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory27
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory31
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory32
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory33
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory34
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory35
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory5
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory6
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory7
SF009A_DutyCycThermProtn/DutyCycThermProtn/Data Store Memory8
Note: These runtime diagnostics may slow down simulation considerably. You should set them back to Disable all once you have verified that they do not cause any warnings or errors during simulation.