This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Implementation

Component Implementation

Component Documentation

1 - PwrDiscnct Review

Overview

Summary Sheet
Davinci Files
Source Code
MDD
QAC
Integration Manual

Sheet 1: Summary Sheet
























Rev 6.028-Oct-14

Peer Review Summary Sheet



























Component 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. PwrDiscnct
Component Revision:


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. 1





























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. Sankardu Varadapureddi
Change Request ID:


EA4#262





























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:































XMDD


XSource Code



Data Dictionary


XQAC



































XIntegration Manual


XDavinci Files








































































Comments:






























































































General Guidelines:
- The reviews shall be performed over the portions of the component that were modified as a result of the Change Request. (Note: If this peer review form was not
completed for pervious versions of this component, the Change Owner should review the entire component and complete the checklist in its entirety prior and check
the form into Syngery. This may be done prior to reviewing the modifications for this Change Result)
- The Change Owner shall responsible for completing the entire checklist (Pre and Group review items) prior holding the initial group review.
- New components should include FDD Owner and Intergator as apart of the Group Review Board (Source Code, Integration Manual, and Davinci Files)
- Select "Yes" and add "N/A" to the comments for checklist items that are not applicable for this change














Sheet 2: Davinci Files






















Rev 6.028-Oct-14
Peer Review Meeting Log (Davinci Review)


























Quality Check Items:

































YesNo
Rationale is required for all answers of No









Pre-review checklist for change ownersDCF: Latest StdDef imported








X
Comments:










































DCF: Only StdDef Port types are used (if not








X
Comments:




add justification)




































DCF: All unused definitions removed








X
Comments:

NA for EA4







































*Cfg.arxml.TT: Verfied Davinci Configurator imported the








X
Comments:
NA








change correctly
kzshz2: Either a generic sandbox or a baselined integration project can be used to verify












































*Cfg.h.TT: Verfied Davinci Configurator generates








X
Comments:
NA








the configuration header(s) file correctly




kzshz2: Either a generic sandbox or a baselined integration project can be used to verify









































Group-review for review boardAll changed files have been compared against previous








X
Comments:

First version

versions (If available)

kzshz2: Intended Use: Identify if previous version was compared and only the expected change(s) was present. This is for text files only, not binary or GUIs Rationale: This is helpful in identifying unapproved (intended or mistaken) changes.


































DCF:Automated validation check is performed








X
Comments:

























































DCF: Inputs/Outputs match names from requirements








X
Comments:

























































DCF: Inputs/Outputs configuration paremeters








X
Comments:










reviewedkzshz2: Intended Use: All changed inputs have been reviewed to ensure configuration parameters (i.e. Buffered vs Direct read/writes) are correct. This includes signal grouping when signal consistency is required by the FDD













































DCF: Sender/Reciever Ports type and default values








X

Comments:

Refer notes







macth their corresponding ports (internal/external)






kzshz2: Intended Use: Identify if all the Sender/Reciever ports are compatibale with there connecting ports. Rationale: This will help to avoid errors when this component is being integrated into a project.






































DCF: Ports prototype and default values








X
Comments:










macth their corresponding ports (internal/external)






kzshz2: Intended Use: Identify if all the Server/Client ports are compatibale with there connecting ports. Rationale: This will help to avoid errors when this component is being integrated into a project.






































DCF: Server runnable variables are using direct








X
Comments:

No server runnables in this component







read/writes













































DCF: Runnable calling frequencies match requirements








X
Comments:



























































General Notes / Comments:























BattVltg' range and intial values are conflicintg with ES250A definitions.- Fixed


































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:

Sankardu Varadapureddi


Review Date :

04/17/15
































Lead Peer Reviewer:


Lucas Wendling


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Kathleen Creager
Selva Sengottaiyan
Spandana Balani
































Rijvi Ahmed































Sheet 3: Source Code






















Rev 6.028-Oct-14
Peer Review Meeting Log (Source Code Review)

























Source File Name:




kzshz2: Intended Use: Identify which .asm, .c, or .h file is being reviewed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. PwrDiscnct.c
Source 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. 1

























Module Design Document Name:




kzshz2: Intended Use: Identify which version of the MDD this source file was written against. Rationale: Needed for traceability between source code and MDD PwrDiscnct_MDD.docx
MDD Revision:


kzshz2: Intended Use: Identify which version of the MDD this source file was written against. Rationale: Needed for traceability between source code and MDD 1

























Data Dictionary Revision:




kzshz2: Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the source file review. Rationale: Needed for traceability between source code and DD NA




FDD/SER/CMS























and Revision:


nz63rn: Intended Use: Identify which version of which FDD/CMS/SER this source file was written against. Rationale: Needed for traceability between source code and FDD/CMS/SER ES003A_PwrDiscnct_Design, ver:1.2.0

Quality Check Items:

































YesNo
Rationale is required for all answers of No









Pre-review checklist for change ownersSoftware Naming Convention V1.2 followed:








































for variable names







X
Comments:






















Referred working EA4 naming conventions document

























for constant names







X
Comments:






















Referred working EA4 naming conventions document

























for function names







X
Comments:






















Referred working EA4 naming conventions document

























for other names (component, memory







X
Comments:










mapping handles, typedefs, etc.)










Referred working EA4 naming conventions document


























All buffered outputs written in every path, i.e. no








X
Comments:










possibility of an uninitialized value being written






































Group-review Checklist (review board)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.


X
Comments:



and Version Control version in file comment block





































Change log contains detailed description of changes








X
Comments:



and CR number





































Code accurately implements FDD (Document or Model)








X
Comments:










































No Compiler Errors or Warnings verified


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.





X
Comments:
















































FDD test points exist as display variables: declared








X
Comments:










static volatile, written once and never used, names










NA

match the FDD













































Software Design and Coding Standards V2.0 followed:








































Code comments are clear, correct, and adequate







X
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







X
Comments:











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







































Function comment blocks are per standards and







X
Comments:











contain correct information: [N43]







































Code formatting (indentation, placement of







X
Comments:











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














[N57], [N58], [N59]
















































Embedded constants used per standards; no







X
Comments:











"magic numbers": [N12]







































All variables and constants defined at module







X
Comments:











level are included in appropriate MemMap










NA


section: [N25] and Naming Conventions
















































All execution-order-dependent code can be







X
Comments:











recognized by the compiler: [N80]







































No possibility of a non-terminating loop: [N63]







X
Comments:




















































No possibility of divide by zero: [N65]







X
Comments:




















































All integer division and modulus operations







X
Comments:











handle negative numbers correctly: [N76]







































All typecasting and fixed point arithmetic,







X
Comments:











including all use of fixed point macros and














timer functions, is correct and has no possibility























of unintended overflow or underflow: [N66]
















































No possibility of converting a negative floating







X
Comments:











point value to an unsigned type: [N67]







































All conversions between signed and unsigned







X
Comments:











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







































No possibility of dereferencing a null







X
Comments:











pointer: [N70]







































Global outputs (RTE and Non-RTE) Initialized:







X
Comments:











[N24]







































Module outputs are limited to the legal range







X
Comments:











defined in the FDD Data dictionary: [N53]







































All code is mapped with FDD (all FDD







X
Comments:











subfunctions and/or model blocks identified














with code comments; all code corresponds to























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
















































Struct types used for NvM have







X
Comments:











elements declared in decreasing order by size














and are not nested or used in arrays: [N84], [N85]
















































No violations of other coding standard rules







X
Comments:











identified during review
























































































General Notes / Comments:























1. Rename 'PwrDiscnct.h' to"'ElecGlbPrm.h". Remove the change log in this header file(to be consistent with others) - fixed

2. Rename 'StrtUpSt_Cnt_T_u8' to 'StrtUpSt_Cnt_T_u08' - fixed

3. Replace 0/1 with 'FALSE/TRUE' - fixed

4. Treat 'ELECGLBPRM_IVTRCNT_CNT_U08' as extern variable in the header file placed in contract folder - fixed

























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:

Sankardu Varadapureddi


Review Date :

04/20/15
































Lead Peer Reviewer:


Lucas Wendling


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Kathleen Creager
Spandana Balani
Rijvi Ahmed

































































Sheet 4: MDD






















Rev 6.028-Oct-14
Peer Review Meeting Log (MDD Review)






























Module Name:

kzshz2: Intended Use: Identify which file is has been reviewed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. PwrDiscnct_MDD.docx


Modulekzshz2: Intended Use: Identify how many source files are being reviewed and trace it to the appropriate MDD. Rationale: Required for traceability between source code and MDD
1of1





























MDD Revision:

kzshz2: Intended Use: Identify which version of the MDD has been reviewed. Rationale: Required for traceability between the MDD and review. Auditors will likely require this. 1


Source File Revision:


kzshz2: Intended Use: Identify which version of the source file was this MDD written for. Rationale: Needed for traceability between source code and MDD 1

Data Dictionary Revision:



kzshz2: Intended Use: Identify which version of the Data Dictionary was referenced for ranges during the review. Rationale: Needed for traceability between source code and DD. Note: Maybe this should be moved to the Summary sheet since there is only one Data Dictionary Version for all changes NA



















































Quality Check Items:

































YesNo
Rationale is required for all answers of No









Group-review Checklist (review board)Synergy version matches header








X
Comments:










































Change log contains detailed description of changes








X
Comments:










































Changes Highlighted (for Unit Tester)








X
Comments:
















First version.
























High-level Diagrams have been reviewed (Section 2)








X
Comments:
















































All Design Exceptions and Limitations are listed








X
Comments:
















































Design rationale given for all module input and output








X
Comments:










data not communicated through RTE ports, per













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













































All other Design rationale understood and captured








X
Comments:










appropriately





































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:

Sankardu Varadapureddi


Review Date :

04/20/15
































Lead Peer Reviewer:


Lucas Wendling


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Kathleen Creager
Spandana Balani
Rijvi Ahmed

































































Sheet 5: QAC






















Rev 6.028-Oct-14
Peer Review Meeting Log (QAC Review)


























Module Name:

kzshz2: Intended Use: Identify which .c file is being analyzed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. PwrDiscnct.c

Source File Revision:


1

Module
1of1


























Compliance Guidelines Version:















































kzshz2: Intended Use: Identify specific changes in results (new violation present, previous violation corrected, etc.). Changes to the version of the tool or the way the results were gathered should be described here also. This should be filled out prior to the review by the change owner. Rationale: Gives reviewers an what needs to be focused on. Forces the change owner to compare with previous results to catch any differences that may otherwise go unoticed Brief Summary of Changes (In Results or Tool):


































































Quality Check Items:

































YesNo
Rationale is required for all answers of No









Pre-review
checklist for change owners		QAC version is correct and did not change (List version)







kzshz2: Intended Use: Identify which version of the QAC Subproject was used and if any of the personalities may have changed. Rationale: Will help ensure this is factored into evaluating the results
X
Comments:

ver 1.1.0







































Contract Folder's header files are appropriate





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.


X
Comments:












































Group-review Checklist (review board)100% Compliance to the MISRA Compliance GuidelinesX
Comments:










































Cyclomatic complexity and Static path count ok per






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

X
Comments:




Design and Coding Standards rule [N47]






































General Notes / Comments:























1. Add MISRA deviation statement at file level for 'void' return type statements… - fixed

2.Polyspace results are reviewed.































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:

Sankardu Varadapureddi


Review Date :

04/20/15
































Lead Peer Reviewer:


Lucas Wendling


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Kathleen Creager
Spandana Balani
Rijvi Ahmed

































































Sheet 6: Integration Manual






















Rev 6.028-Oct-14
Peer Review Meeting Log (Integration Manual Review)


























Integration Manual Name:



kzshz2: Intended Use: Identify which file is being reviewed Rationale: Required for traceability. It will help to ensure this sheet is not attached to the wrong design review form. PwrDiscnct_Integration Manual.docx

Integration Manual Revision:



kzshz2: Intended Use: Identify which version of the integration manual has been reviewed. Rationale: Required for traceability between the MDD and review. Auditors will likely require this. 1





























Quality Check Items:

































YesNo
Rationale is required for all answers of No









Group-review Checklist (review board)Synergy version matches header








X
Comments:










































Latest template used








X
Comments:










































Change log contains detailed description of changes








X
Comments:










































Changes Highlighted (for Integrator)








X
Comments:
















First version

























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:

Sankardu Varadapureddi


Review Date :

04/20/15
































Lead Peer Reviewer:


Lucas Wendling


Approved by Reviewer(s):



Yes































Other Reviewer(s):


Kathleen Creager
Spandana Balani
Rijvi Ahmed

































































2 - PwrDiscnct_Integration Manual

Integration Manual

For

‘PwrDiscnct’

VERSION: 1.0

DATE: 09-Apr-2015

Prepared By:

Sankardu Varadapureddi,

Nexteer Automotive,

Saginaw, MI, USA


Revision History

Sl. No.DescriptionAuthorVersionDate
1Initial versionSankardu Varadapureddi1.009-Apr-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

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

Sr. No.TitleVersion
1FDD - ES003A_PwrDiscnct_DesignSee Synergy sub project version
2Software Naming ConventionsProcess 3.06.00
3Software Design and Coding StandardsProcess 3.06.00

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 file in the FDD

Specific Include Path present

No

Runnable Scheduling

This section specifies the required runnable scheduling.

InitScheduling RequirementsTrigger
None
RunnableScheduling RequirementsTrigger
PwrDiscnctPer1NoneRTE (2ms)

.

Memory Map REQUIREMENTS

Mapping

Memory SectionContentsNotes
PwrDiscnct_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

Non RTE NvM Blocks

Block Name
None

RTE NvM Blocks

Block Name
None

Compiler Settings

Preprocessor MACRO

None.

Optimization Settings

None

Appendix

None

3 - PwrDiscnct_MDD

Module Design Document

For

‘PwrDiscnct’

VERSION: 1.0

DATE: 09-Apr-2015

Prepared By:

Sankardu Varadapureddi,

Nexteer Automotive,

Saginaw, MI, USA


Location: The official version of this document is stored in the Nexteer Configuration Management System.

Revision History

Sl. No.DescriptionAuthorVersionDate
1Initial VersionSankardu Varadapureddi1.009-Apr-2015


Table of Contents

1 Abbrevations And Acronyms 4

2 References 5

3 Power Disconnect High-Level Description 6

4 Design details of software module 7

4.1 Graphical representation of POWER DISCONNECT 7

4.2 Data Flow Diagram 7

4.2.1 Module level DFD 7

4.2.2 Sub-Module level DFD 7

4.3 COMPONENT FLOW DIAGRAM 7

5 Variable Data Dictionary 8

5.1 User defined typedef definition/declaration 8

5.2 Variable definition for enumerated types 8

6 Constant Data Dictionary 9

6.1 Program(fixed) Constants 9

6.1.1 Embedded Constants 9

6.1.1.1 Local 9

6.1.1.2 Global 9

6.1.2 Module specific Lookup Tables Constants 9

7 Software Module Implementation 10

7.1 Sub-Module Functions 10

7.1.1 Initialization Functions 10

7.1.2 PERIODIC FUNCTIONS 10

7.1.2.1 Per: PwrDiscnct_Per1 10

7.1.2.1.1 Design Rationale 10

7.1.2.1.2 Store Module Inputs to Local copies 10

7.1.2.1.3 (Processing of function)……… 10

7.1.2.1.4 Store Local copy of outputs into Module Outputs 10

7.1.3 Interrupt Functions 10

7.1.4 Serial Communication Functions 11

7.1.5 Local Function/Macro Definitions 11

7.1.6 GLObAL Function/Macro Definitions 11

7.1.7 Tranisition FUNCTIONS 11

8 Known Limitations With Design 12

9 UNIT TEST CONSIDERATION 13

10 Appendix 14

Abbrevations And Acronyms

AbbreviationDescription
DFDDesign functional diagram
MDDModule design Document
FDDFunctional Design Document

References

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

Sr. No.TitleVersion
1MDD GuidelinesProcess 3.06.00
2Software Naming ConventionsProcess 3.06.00
3Software Design and Coding standardsProcess 3.06.00
4FDD - ES003A_PwrDiscnct_DesignSee Synergy sub project version

Power Disconnect High-Level Description

This function will verify that the PowerDisconnect is not stuck closed at init once per Ignition Cycle.

Design details of software module

Graphical representation of POWER DISCONNECT

Data Flow Diagram

Refer FDD

Module level DFD

Refer FDD

Sub-Module level DFD

Refer FDD

COMPONENT FLOW DIAGRAM

Refer FDD

Variable Data Dictionary

User defined typedef definition/declaration

<This section documents any user types uniquely used for the module.>

Typedef NameElement NameUser Defined Type

Legal Range

(min)

Legal Range

(max)

None

Variable definition for enumerated types

Enum NameElement NameValue
None

Constant Data Dictionary

Program(fixed) Constants

Embedded Constants

Local

Constant NameResolutionUnitsValue
None

Global

Constant Name

Module specific Lookup Tables Constants

Constant NameResolutionValueSoftware Segment
None

Software Module Implementation

Sub-Module Functions

Initialization Functions

None

PERIODIC FUNCTIONS

Per: PwrDiscnctPer1

Design Rationale

Design follows implemenetation in FDD.

Store Module Inputs to Local copies

Refer to FDD

(Processing of function)………

Refer to FDD (Block ‘PwrDiscnct’)

Store Local copy of outputs into Module Outputs

Refer to FDD

Interrupt Functions

None


Serial Communication Functions

None

Local Function/Macro Definitions

None

GLObAL Function/Macro Definitions

None

Tranisition FUNCTIONS

None

Known Limitations With Design

None

UNIT TEST CONSIDERATION

Appendix

None

4 - requirements

FDDIDSourceFunctionLine(s)StatusComment
.SwFileName.SwFuncName.SwLines.SwStatus.SwComment
ES003A88PwrDiscnct.cPwrDiscnctPer1885I
ES003A89PwrDiscnct.cPwrDiscnctPer1823-840I
ES003A82PwrDiscnct.cPwrDiscnctPer1884I
ES003A86PwrDiscnct.cPwrDiscnctPer1808-815I
ES003A87PwrDiscnct.cPwrDiscnctPer1848-856,864-869I
ES003A21PwrDiscnct.cPwrDiscnctPer1799-805I
ES003A22PwrDiscnct.cPwrDiscnctPer1810,835I
ES003A23PwrDiscnct.cPwrDiscnctPer1824-830I
ES003A47PwrDiscnct.cPwrDiscnctPer1796-882I
ES003A42PwrDiscnct.cPwrDiscnctPer1812,818I
ES003A43PwrDiscnct.cPwrDiscnctPer1837,844I
ES003A76PwrDiscnct.cPwrDiscnctPer1825-831I
ES003A106PwrDiscnct.cPwrDiscnctPer1792I
ES003A91PwrDiscnct.cPwrDiscnctPer1819I
ES003A93PwrDiscnct.cPwrDiscnctPer1843I
ES003A92PwrDiscnct.cPwrDiscnctPer1807-814I
ES003A95PwrDiscnct.cPwrDiscnctPer1833-839I
ES003A11PwrDiscnct.cPwrDiscnctPer1790I
ES003A10PwrDiscnct.cPwrDiscnctPer1789I
ES003A13PwrDiscnct.cPwrDiscnctPer1826I
ES003A12PwrDiscnct.cPwrDiscnctPer1791I
ES003A15PwrDiscnct.cPwrDiscnctPer1892I
ES003A14PwrDiscnct.cPwrDiscnctPer1891I
ES003A98PwrDiscnct.cPwrDiscnctPer1795-889I
ES003A18PwrDiscnct.cPwrDiscnctPer1803,829I
ES003A50PwrDiscnct.cPwrDiscnctPer1798-804I