1 - DutyCycThermProtn_DesignReview


Overview

Summary Sheet
Synergy Project
Source Code
MDD
PolySpace


Sheet 1: Summary Sheet
























Rev 1.28-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. SF009A_DutyCycThermProtn_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. SF009A_DutyCycThermProtn_Impl_2.3.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. Krishna Anne
Work CR ID:


EA4#7662





























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:































YesMDD


YesSource Code


YesPolySpace









































N/AIntegration Manual


N/ADavinci Files








































































Comments:

Reviewed changes alone



























































































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.





















Sheet 2: Synergy Project

Peer Review Meeting Log (Component Synergy Project Review)



















































Quality Check Items:




































Rationale is required for all answers of No










New baseline version name from Summary Sheet follows








Yes
Comments:



naming convention





































Project contains necessary subprojects








Yes
Comments:










































Project contains the correct version of subprojects








Yes
Comments:










































Design subproject is correct version








Yes
Comments:











































General Notes / Comments:



























































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:


























Change Owner:

Krishna Anne


Review Date :

09/29/16
































Lead Peer Reviewer:


Kathleen Creager


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Avinash James






































































Sheet 3: Source Code






















Rev 1.28-Jun-15
Peer Review Meeting Log (Source Code Review)

























Source File Name:


DutyCycThermProtn.c

Source File Revision:


6
Header File Name:


NA

Header File Revision:


kzshz2: Intended Use: Identify which version of the source file is being review. Rationale: Required for traceability between source code and review. Auditors will likely require this. NA

























MDD Name:

DutyCycThermProtn_MDD.docx

Revision:
3

























FDD/SCIR/DSR/FDR/CM Name:




SF009A_DutyCycThermProtn_Design

Revision:
2.2.1


























Quality Check Items:



































Rationale is required for all answers of No









Working EA4 Software Naming Convention followed:















































for variable names







Yes
Comments:

















































for constant names







Yes
Comments:

















































for function names







Yes
Comments:

















































for other names (component, memory







Yes
Comments:










mapping handles, typedefs, etc.)




































All paths assign a value to outputs, ensuring








N/A
Comments:









all outputs are initialized prior to being written











No changes here
























Requirements Tracability tags in code match the requirements tracability in the FDD








N/A
Comments:









requirements tracability in the FDD











Not applicable anymore, deleted few of them.
























All variables are declared at the function level.








Yes
Comments:
























Synergy version matches change history





kzshz2: Intended Use: Indicate that the the versioning was confirmed by the peer reviewer(s). Rationale: There have been many occassions where versions were not updated in files and as a result Unit Test were referencing wrong versions. This often time leads to the need to re-run of batch tests.


Yes
Comments:



and Version Control version in file comment block





































Change log contains detailed description of changes








Yes
Comments:



and Work CR number





































Code accurately implements FDD (Document or Model)








Yes
Comments:










































Verified no Compiler Errors or Warnings


KMC: Intended Use: To confirm no compiler errors or warnings exist for the code under review (warnings from contract header files may be ignored). Rationale: This is needed to ensure there will be no errors discovered at the time of integration. A Sandox project should be used; QAC can find compiler errors but not warnings.





Yes
Comments:
















































Component.h is included








N/A
Comments:
























All other includes are actually needed. (System includes








Yes
Comments:









only allowed in Nexteer library components)





































Software Design and Coding Standards followed:











Version: 2.1

























Code comments are clear, correct, and adequate







Yes
Comments:










and have been updated for the change: [N40] and













all other rules in the same section as rule [N40],






















plus [N75], [N12], [N23], [N33], [N37], [N38],






















[N48], [N54], [N77], [N79], [N72]














































Source file (.c and .h) comment blocks are per







Yes
Comments:










standards and contain correct information: [N41], [N42]





































Function comment blocks are per standards and







Yes
Comments:










contain correct information: [N43]





































Code formatting (indentation, placement of







Yes
Comments:










braces, etc.) is per standards: [N5], [N55], [N56],













[N57], [N58], [N59]














































Embedded constants used per standards; no







Yes
Comments:










"magic numbers": [N12]





































Memory mapping for non-RTE code







N/A
Comments:










is per standard





































All execution-order-dependent code can be







Yes
Comments:










recognized by the compiler: [N80]





































All loops have termination conditions that ensure







Yes
Comments:










finite loop iterations: [N63]





































All divides protect against divide by zero







N/A
Comments:










if needed: [N65]





































All integer division and modulus operations







N/A
Comments:










handle negative numbers correctly: [N76]





































All typecasting and fixed point arithmetic,







Yes
Comments:










including all use of fixed point macros and













timer functions, is correct and has no possibility






















of unintended overflow or underflow: [N66]














































All float-to-unsiged conversions ensure the.







N/A
Comments:










float value is non-negative: [N67]





































All conversions between signed and unsigned







N/A
Comments:










types handle msb==1 as intended: [N78]





































All pointer dereferencing protects against







Yes
Comments:










null pointer if needed: [N70]





































Component outputs are limited to the legal range







N/A
Comments:










defined in the FDD DataDict.m file : [N53]










Current change is neutral to the range limit

























All code is mapped with FDD (all FDD







Yes
Comments:










subfunctions and/or model blocks identified













with code comments; all code corresponds to






















some FDD subfunction and/or model block): [N40]













































Review did not identify violations of other








Yes
Comments:









coding standard rules





































Anomaly or Design Work CR created








N/A
Comments: List Anomaly or CR numbers









for any FDD corrections needed































































General Notes / Comments:

















































































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:


























Change Owner:

Krishna Anne


Review Date :

09/29/16
































Lead Peer Reviewer:


Kathleen Creager


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Avinash James






































































Sheet 4: MDD






















Rev 1.28-Jun-15
Peer Review Meeting Log (MDD Review)


























MDD Name:

DutyCycThermProtn_MDD.docx













MDD Revision:

3


























Source File Name:


DutyCycThermProtn.c











Source File Revision:


6

Source File Name:















Source File Revision:





Source File Name:















Source File Revision:






























Quality Check Items:




































Rationale is required for all answers of No










Synergy version matches document








Yes
Comments:













































Change log contains detailed description of changes








Yes
Comments:













































Changes Highlighted (for Unit Tester)








Yes
Comments:













































Diagrams have been included per MDD Guideline








N/A
Comments:











and reviewed






































All Design Exceptions and Limitations are listed








N/A
Comments:



















































Design rationale given for all global








Yes
Comments:











data not communicated through RTE ports, per














Design and Coding Standards rules [N9] and [N10].















































All implementation details that differ from the FDD are








N/A
Comments:











noted and explained in Design Rationale






































All Unit Test Considerations have been described








Yes
Comments:



















































General Notes / Comments:



























































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:


























Change Owner:

Krishna Anne


Review Date :

09/29/16
































Lead Peer Reviewer:


Kathleen Creager


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Avinash James






































































Sheet 5: PolySpace






















Rev 1.28-Jun-15
Peer Review Meeting Log (QAC/PolySpace Review)


























Source File Name:


DutyCycThermProtn.c











Source File Revision:


6

Source File Name:















Source File Revision:





Source File Name:















Source File Revision:






























EA4 Static Analysis Compliance Guideline version:







01.01.00














Poly Space version:


Windows User: eg. 2013b 2013b





Polyspace sub project version:




Windows User: eg. TL108a_PolyspaceSuprt_1.0.0 TL108A_PolyspaceSuprt_1.0.0






QAC version:


Windows User: eg 8.1.1-R 8.1.1-R





QAC sub project version:




Windows User: eg. TL_100A_1.1.0 TL100A_QACSuprt_1.2.0































Quality Check Items:




































Rationale is required for all answers of No



































Contract Folder's header files are appropriate and





kzshz2: Intended Use: Identify that the contract folder contains only the information required for this component. All other variables, constants, function prototypes, etc. should be removed. Rationale: This will help avoid unit testers having to considers object not used. It will also avoid having other files required for QAC.


Yes
Comments:




function prototypes match the latest component version







































100% Compliance to the EA4 Static AnalysisYes
Comments:





Compliance Guideline





























Are previously added justification and deviation








Yes
Comments:





comments still appropriate






































Do all MISRA deviation comments use approved








Yes
Comments:





deviation tags






































Cyclomatic complexity and Static path count OK






Creager, Kathleen: use Browse Function Metrics, STCYC and STPTH

Yes
Comments:





for all functions in the component per Design














and Coding Standards rule [N47]

































































































General Notes / Comments:



























































LN: Intended Use: Identify who were the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. KMC: Group Review Level removed in Rev 4.0 since the design review is not checked in until approved, so it would always be DR4. Review Board:


























Change Owner:

Krishna Anne


Review Date :

09/29/16
































Lead Peer Reviewer:


Kathleen Creager


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Avinash James





































































2 - DutyCycThermProtn_Integration Manual

Integration Manual

For

SF009A_DutyCycThermProtn

VERSION: 1.0

DATE: 02-Oct-2015

Prepared By:

Sarika Natu,

KPIT Technologies,

India

Revision History

DescriptionAuthorVersionDate
Initial versionSarika Natu1.002-Oct-2015

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

AbbreviationDescription
DFDDesign functional diagram
MDDModule design Document

References

Sr. No.TitleVersion
1MDD GuidelinesSoftware Process Release 04.02.00
2Software Naming ConventionsSoftware Process Release 04.02.00
3Design and Coding standardsSoftware Process Release 04.02.00
4FDD – SF009A_DutyCycThermProtn_DesignSee Synergy sub project version

Dependencies

SWCs

ModuleRequired Feature
None

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

None

Configuration REQUIREMeNTS

Build Time Config

ModulesNotes
None

Configuration Files to be provided by Integration Project

None

Da Vinci Parameter Configuration Changes

ParameterNotesSWC
None

DaVinci Interrupt Configuration Changes

ISR NameVIM #Priority DependencyNotes
None

Manual Configuration Changes

ConstantNotesSWC
None

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer DataDict.m file in the FDD

Required Global Data Outputs

Refer DataDict.m file in the FDD

Specific Include Path present

No

Runnable Scheduling

This section specifies the required runnable scheduling.

InitScheduling RequirementsTrigger
DutyCycThermProtnInit1NoneRTE(Init)
RunnableScheduling RequirementsTrigger
DutyCycThermProtnPer1NoneRTE(100ms)

Memory Map REQUIREMENTS

Mapping

Memory SectionContentsNotes
DutyCycThermProtn_START_SEC_CODE

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

Usage

FeatureRAMROM
<Memmap usuage info>

Table 1: ARM Cortex R4 Memory Usage

NvM Blocks

See DataDict.m

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

None

3 - DutyCycThermProtn_MDD

Module Design Document

For

DutyCycThermProtn

Sep 29, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Krishna Anne

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA


Change History

DescriptionAuthorVersionDate
Initial VersionSarika Natu(KPIT Technologies)1.002-Oct-2015
Updated to version 2.0.0 of FDDKrishna Anne2.007-Apr-2016
Fix for anomaly EA4# 7558Krishna Anne3.029-Sep-2016


Table of Contents

1 DutyCycThermProtn & High-Level Description 5

2 Design details of software module 6

2.1 Graphical representation of DutyCycThermProtn 6

2.2 Data Flow Diagram 7

2.2.1 Component level DFD 7

2.2.2 Function level DFD 7

3 Constant Data Dictionary 8

3.1 Program (fixed) Constants 8

3.1.1 Embedded Constants 8

4 Software Component Implementation 9

4.1 Sub-Module Functions 9

4.1.1 Init: DutyCycThermProtn_Init1 9

4.1.1.1 Design Rationale 9

4.1.1.2 Module Outputs 9

4.1.2 Per: DutyCycThermProtn_Per1 9

4.1.2.1 Design Rationale 9

4.1.2.2 Store Module Inputs to Local copies 9

4.1.2.3 (Processing of function)……… 9

4.1.2.4 Store Local copy of outputs into Module Outputs 9

4.2 Server Runables 9

4.3 Interrupt Functions 9

4.4 Module Internal (Local) Functions 9

4.4.1 Local Function #1 9

4.4.1.1 Design Rationale 9

4.4.1.2 Processing 10

4.4.2 Local Function #2 10

4.4.2.1 Design Rationale 10

4.4.2.2 Processing 10

4.4.3 Local Function #3 10

4.4.3.1 Design Rationale 10

4.4.3.2 Processing 10

4.4.4 Local Function #4 10

4.4.4.1 Design Rationale 11

4.4.4.2 Processing 11

4.4.5 Local Function #5 11

4.4.5.1 Design Rationale 11

4.4.5.2 Processing 11

4.4.6 Local Function #6 11

4.4.6.1 Design Rationale 11

4.4.6.2 Processing 12

4.5 GLOBAL Function/Macro Definitions 12

5 Known Limitations with Design 13

6 UNIT TEST CONSIDERATION 14

Appendix A Abbreviations and Acronyms 15

Appendix B Glossary 16

Appendix C References 17

DutyCycThermProtn & High-Level Description

The purpose of the Thermal Duty Cycle Protection is to limit and protect the system from excessive use, based on motor rotational velocity and system temperature. It also provides protection status information for use by other functions.

Design details of software module

Graphical representation of DutyCycThermProtn

Data Flow Diagram

See FDD

Component level DFD

See FDD

Function level DFD

See FDD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Refer .m file

Constant NameValue
DUTYCYCTHERMSIZE_CNT_U085
THERMLOADLIMSIZE_CNT_U088
MULTFILTERSIZE_CNT_U086

Software Component Implementation

Sub-Module Functions

Init: DutyCycThermProtn_Init1

Design Rationale

Refer FDD

Module Outputs

Refer FDD

Per: DutyCycThermProtn_Per1

Design Rationale

DutyCycThermProtn_Per1 function is divided into various functions to reduce the cyclomatic complexity.

The subsystems ‘Multiplier’ and ‘FilterPercMax’ are clubbed into ‘MultiFilterPercMax’ local function.

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 NameFiltSVReinitTypeMinMax
Arguments PassedIgnTiOff_Cnt_T_u32uint3201720000
VehTiVld_Cnt_T_LoglBoolean01
Return ValueNone

Design Rationale

Name of local function matches with subsystem name from FDD

Processing

Local Function #2

Function NameTemperatureSelectionTypeMinMax
Arguments PassedDiagcStsLimdTPrfmnc_Cnt_T_Loglboolean01
EcuTFild_DegCgrd_T_f32float32-50150
MotFetT_DegCgrd_T_f32float32-50200
MotMagT_DegCgrd_T_f32float32-50150
MotWidgT_DegCgrd_T_f32float32-50300
*Mult12Temp_DegCgrd_T_ s15p0Sint16-50200
*Mult36Temp_DegCgrd_T_s15p0Sint16-50300
Return ValueSlcTemp_DegCgrd_T_s15p0sint16-50300

Design Rationale

Name of local function matches with subsystem name from FDD

Note: The outputs of the function are Mult12Temp_DegCgrd_T_s15p0, Mult36Temp_DegCgrd_T_s15p0 and SlcTemp_DegCgrd_T_f32.

Processing

None

Local Function #3

Function NameTemperatureLimitingTypeMinMax
Arguments PassedEcuTFild_DegCgrd_T_f32float32-50150
MotWidgT_DegCgrd_T_f32float32-50300
Return ValueAbsTempLimitSlew_MotNwtMtrPerSec_T_f32float3208.79

Design Rationale

Name of local function matches with subsystem name from FDD

Processing

None

Local Function #4

Function NameMultiFilterPercMaxTypeMinMax
Arguments PassedMult12Temp_DegCgrd_T_s15p0sint16-50200
Mult36Temp_DegCgrd_T_s15p0sint16-50300
DutyCycThermProtnDi_Cnt_T_Loglboolean01
MotVelCrf_MotRadPerSec_T_f32float32-13501350
MotCurrPeakEstimd_AmprSqd_T_f32float32062500
MotCurrPeakEstimdFild_AmprSqd_T_f32float32062500
*MaxOut_Uls_T_u16p0uint160200
Return ValueThermLimSlowFilMax_Uls_T_f32float320200

Design Rationale

The subsystems ‘Multiplier’ and ‘FilterPercMax’ are clubbed into ‘MultiFilterPercMax’ local function.

Note: The outputs of the function are MaxOut_Uls_T_u16p0 and ThermLimSlowFilMax_Uls_T_f32.

Processing

None

Local Function #5

Function NameThermalLoadLimitTypeMinMax
Arguments PassedMotVelCrf_MotRadPerSec_T_f32float32-13501350
SlcTemp_DegCgrd_T_s15p0sint16-50300
MaxOut_Uls_T_u16p0uint160200
Return ValueThermalLoadLmt_MotNwtMtr_T_f32float3208.79

Design Rationale

Name of local function matches with subsystem name from FDD

Processing

None

Local Function #6

Function NameThermalLimitStatusTypeMinMax
Arguments PassedAbsTempLimitSlew_MotNwtMtrPerSec_T_f32float3208.79
DutyCycThermProtnDi_Cnt_T_LoglBoolean01
ThermalLoadLmt_MotNwtMtr_T_f32float3208.79
MaxOut_Uls_T_u16p0uint160200
*ThermMotTqLim_MotNwtMtr_T_f32float3208.8
Return ValueThermRednFac_Uls_T_f32float3201

Design Rationale

Name of local function matches with subsystem name from FDD

Note: The outputs of the function are ThermMotTqLim_MotNwtMtr_T_f32 and ThermRednFac_Uls_T_f32.

Local Function #6

Function NameUseInpLowrTypeMinMax
Arguments Passed*TableX_Cnt_T_s16sint16FULLFULL
*TableY_Cnt_T_u16uint16FULLFULL
Size_Cnt_T_u16uint16120
Input_Cnt_T_s16sint16FULLFULL
Return ValueTableY_Cnt_T_u16[Idx_Cnt_T_u08]uint16FULLFULL

Design Rationale

None.

Processing

None

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

  • Function UseInpLowr to be tested only as called by the component; input and output ranges will not be reached.

  • Function UseInpLowr’s TableX must have strictly increasing elements.

Abbreviations and Acronyms

Abbreviation or AcronymDescription

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.3.0 R4.0 Rev 2
2MDD GuidelineEA4 02.00.00
3Software Naming Conventions.doc1.0
4Software Design and Coding Standards.doc2.1
5FDD – SF009A_DutyCycThermProtn_DesignSee Synergy sub project version

4 - requirements

FDDIDSourceFunctionLine(s)StatusComment
.SwFileName.SwFuncName.SwLines.SwStatus.SwComment
SF009A151DutyCycThermProtn.cMultiFilterPercMax1390,1394I
SF009A150DutyCycThermProtn.cDutyCycThermProtnPer11133-1138I
SF009A248DutyCycThermProtn.cTemperatureLimiting1342,1344,1349,1354,1359I
SF009A215DutyCycThermProtn.cThermalLoadLimit1555I
SF009A155DutyCycThermProtn.cMultiFilterPercMax1387-1446I
SF009A213DutyCycThermProtn.cThermalLoadLimit1508I
SF009A217DutyCycThermProtn.cMultiFilterPercMax1399I
SF009A114DutyCycThermProtn.cTemperatureSelection1264,1268I
SF009A117DutyCycThermProtn.cDutyCycThermProtnInit1,MultiFilterPercMax945-952,1448-1483I
SF009A116DutyCycThermProtn.cMultiFilterPercMax1398-1438I
SF009A161DutyCycThermProtn.cThermalLoadLimit1540-1552I
SF009A252DutyCycThermProtn.cTemperatureLimiting1313-1319I
SF009A235DutyCycThermProtn.cThermalLimitStatus1599-1608I
SF009A250DutyCycThermProtn.cTemperatureLimiting1298-1304I
SF009A138DutyCycThermProtn.cDutyCycThermProtnPer11106-1111I
SF009A257DutyCycThermProtn.cMultiFilterPercMax1482I
SF009A232DutyCycThermProtn.cThermalLimitStatus1596I
SF009A233DutyCycThermProtn.cThermalLimitStatus1588I
SF009A174DutyCycThermProtn.cDutyCycThermProtnInit1945-952I
SF009A222DutyCycThermProtn.cMultiFilterPercMax1402-1416,1422,1436I
SF009A44DutyCycThermProtn.cDutyCycThermProtnPer11144I
SF009A45DutyCycThermProtn.cDutyCycThermProtnPer11146I
SF009A41DutyCycThermProtn.cDutyCycThermProtnPer11085I
SF009A181DutyCycThermProtn.cFiltSVReinit1196I
SF009A162DutyCycThermProtn.cThermalLoadLimit1528-1533I
SF009A184DutyCycThermProtn.cTemperatureSelection1227I
SF009A185DutyCycThermProtn.cTemperatureSelection1229I
SF009A9DutyCycThermProtn.cDutyCycThermProtnPer11088I
SF009A283DutyCycThermProtn.cDutyCycThermProtnPer11147I
SF009A285DutyCycThermProtn.cDutyCycThermProtnInit1,FiltSVReinit927-943,1185-1194I
SF009A287DutyCycThermProtn.cThermalLimitStatus1621-1627I
SF009A144DutyCycThermProtn.cTemperatureSelection1243-1252I
SF009A205DutyCycThermProtn.cDutyCycThermProtnInit1928,932-937,941I
SF009A143DutyCycThermProtn.cThermalLimitStatus1612-1619I
SF009A148DutyCycThermProtn.cTemperatureLimiting1330-1338I
SF009A247DutyCycThermProtn.cThermalLimitStatus1630I
SF009A109DutyCycThermProtn.cDutyCycThermProtnPer11084I
SF009A168DutyCycThermProtn.cMultiFilterPercMax1476,1480I
SF009A169DutyCycThermProtn.cDutyCycThermProtnPer11143-1148I
SF009A251DutyCycThermProtn.cTemperatureLimiting1312-1318I
SF009A167DutyCycThermProtn.cMultiFilterPercMax1450-1485I
SF009A249DutyCycThermProtn.cTemperatureLimiting1297-1303I
SF009A188DutyCycThermProtn.cTemperatureSelection1227I
SF009A221DutyCycThermProtn.cMultiFilterPercMax1421,1435I
SF009A220DutyCycThermProtn.cMultiFilterPercMax1401-1415I
SF009A11DutyCycThermProtn.cDutyCycThermProtnInit1945-952I
SF009A39DutyCycThermProtn.cDutyCycThermProtnPer11094I
SF009A38DutyCycThermProtn.cDutyCycThermProtnPer11087I
SF009A33DutyCycThermProtn.cDutyCycThermProtnPer11092I
SF009A32DutyCycThermProtn.cDutyCycThermProtnPer11089I
SF009A37DutyCycThermProtn.cDutyCycThermProtnPer11093I
SF009A36DutyCycThermProtn.cDutyCycThermProtnPer11091I
SF009A35DutyCycThermProtn.cDutyCycThermProtnPer11090I
SF009A34DutyCycThermProtn.cDutyCycThermProtnPer11086I
SF009A164DutyCycThermProtn.cMultiFilterPercMax1449-1484I
SF009A246DutyCycThermProtn.cThermalLimitStatus1585,1593I
SF009A267DutyCycThermProtn.cThermalLimitStatus1591I