Sr. No.	Title	Version
1	FDD – ES259A Battery or Switched Voltage Correlation	See Synergy subproject version
2	Software Naming Conventions	Process 4.01.0
3	Software Design and Coding Standards	Process 4.01.0

Dependencies

SWCs

Module	Required Feature
None

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

None

Configuration REQUIREMeNTS

Build Time Config

Modules	Notes
None

Configuration Files to be provided by Integration Project

None

Da Vinci Parameter Configuration Changes

Parameter	Notes	SWC
None

DaVinci Interrupt Configuration Changes

ISR Name	VIM #	Priority Dependency	Notes
None

Manual Configuration Changes

Constant	Notes	SWC
None

Integration DATAFLOW REQUIREMENTS

Required Global Data Inputs

Refer to DataDict.m file in the FDD.

Required Global Data Outputs

Refer to DataDict.m file in the FDD.

Specific Include Path present

Runnable Scheduling

This section specifies the required runnable scheduling.

Init	Scheduling Requirements	Trigger
None

Runnable	Scheduling Requirements	Trigger
BattVltgPer1	None	RTE (2ms)

Memory Map REQUIREMENTS

Mapping

Memory Section	Contents	Notes

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

Usage

Feature	RAM	ROM
<Memmap usuage info>

Table 1: ARM Cortex R4 Memory Usage

NvM Blocks

None

Compiler Settings

Preprocessor MACRO

None

Optimization Settings

None

Appendix

None

2 - BattVltgCorrln_MDD

Module Design Document

For

BattVltgCorrln

May 24, 2016Mar 21, 2016

Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Nick Saxton,

Nexteer Automotive,

Saginaw, MI, USAChange History

Description	Author	Version	Date
Initial Version	N. Saxton	1.00.00	08-Jul-2015
Updated for FDD 1.2.2	N. Saxton	2.00.00	06-Aug-2015
Updated for FDD 1.4.0	Sankardu Varadapureddi	3	21-Mar-2016
Updated for FDD 2.0.0	N. Saxton	4	24-May-2016

Table of Contents

1 BattVltgCorrln & High-Level Description 4

2 Design details of software module 5

2.1 Graphical representation of BattVltgCorrln 5

2.2 Data Flow Diagram 5

2.2.1 Component level DFD 5

2.2.2 Function level DFD 5

3 Constant Data Dictionary 6

3.1 Program (fixed) Constants 6

3.1.1 Embedded Constants 6

4 Software Component Implementation 7

4.1.1 Sub-Module Functions 7

4.1.2 Interrupt Service Routines 7

4.1.3 Server Runnable Functions 7

4.1.4 Module Internal (Local) Functions 7

4.1.5 Transition Functions 9

5 Known Limitations with Design 10

6 UNIT TEST CONSIDERATION 11

Appendix A Abbreviations and Acronyms 12

Appendix B Glossary 13

Appendix C References 15

BattVltgCorrln & High-Level Description

This function determines the correlation between three input signals (battery voltage, switched battery voltage 1, and switched battery voltage 2) to conclude their validities.

Design details of software module

Graphical representation of BattVltgCorrln

Data Flow Diagram

Component level DFD

N/A

Function level DFD

N/A

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Constant Name	Resolution	Units	Value
BATTVLTGIDPTSIGLOLIMIT_CNT_U08	None	NA	0
BATTVLTGIDPTSIGHILIMIT _CNT_U08	None	NA	3

* Refer FDD for other constant definition

Software Component Implementation

Sub-Module Functions

Initialization sub-module {_Init()}

None

Periodic sub-module {_Per()}

BattVltgCorrlnPer1

Design Rationale

Refer to FDD

Store module inputs to local copies

Refer to FDD

(Processing of function)……

Refer to FDD

Store local copy of outputs into module outputs

Refer FDD

Interrupt Service Routines

None

Server Runnable Functions

None

Module Internal (Local) Functions

Local Function #1

Function Name	InstCorrln	Type	Min	Max
Arguments Passed	Vltg_Volt_T_f32	float32	0	40
	VltgSwd1_Volt_T_f32	float32	0	40
	VltgSwd2_Volt_T_f32	float32	0	40
	BattVltgAdcFaild_Cnt_T_logl	boolean	FALSE	TRUE
	BattVltgSwd1AdcFaild_Cnt_T_logl	boolean	FALSE	TRUE
	BattVltgSwd2AdcFaild_Cnt_T_logl	boolean	FALSE	TRUE
	*VltgOk_Cnt_T_u08	uint8	0	1
	*Swd1Ok_Cnt_T_u08	uint8	0	1
	*Swd2Ok_Cnt_T_u08	uint8	0	1
Return Value	BattSwdVltgLimd_Cnt_T_logl	boolean	FALSE	TRUE

Description

Refer FDD

Local Function #2

Function Name	DetIdptSig	Type	Min	Max
Arguments Passed	Ntc0x3CQlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD
	Ntc044QlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD
	Ntc0x4CQlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD
	*VltgNotFailed_Cnt_T_u08	uint8	0	1
	*VltgSwd1NotFailed_Cnt_T_u08	uint8	0	1
	*VltgSwd2NotFailed_Cnt_T_u08	uint8	0	1
Return Value	VltgCorrlnIdptSig_Cnt_T_u08	uint8	0	3

Description

This function implements the Determine Independent Signals block in the FDD but with a few differences. Instead of implementing the truth table as shown in the FDD, each signal “not failed” variable is set based on the signal’s OK status. Once a signal is considered “not failed”, the variable representing the number of independent signals is incremented. However, while possible in the code, it is not possible for a situation to arise in which there is only one independent signal, therefore a check is performed at the end of this function to set the number of independent signals to 0 and each “not failed” variable to FALSE if this situation occurs.

Local Function #3

Function Name	GetCorrlnSts	Type	Min	Max
Arguments Passed	VltgNotFailed_Cnt_T_u08	uint8	0	1
	VltgSwd1NotFailed_Cnt_T_u08	uint8	0	1
	VltgSwd2NotFailed_Cnt_T_u08	uint8	0	1
	VltgOk_Cnt_T_u08	uint8	0	1
	Swd1Ok_Cnt_T_u08	uint8	0	1
	Swd2Ok_Cnt_T_u08	uint8	0	1
	* DftBrdgVltgActv_Cnt_T_logl	boolean	FALSE	TRUE
Return Value	CorrlnSts_Cnt_T_u08	uint8	0	7

* DftBrdgVltgActv_Cnt_T_logl is an output of this function.

Description

Refer FDD

Local Function #4

Function Name	DetSwdSat	Type	Min	Max
Arguments Passed	VltgSwd1_Volt_T_f32	float32	0	40
	VltgSwd2_Volt_T_f32	float32	0	40
	VltgSwd1Ok_Cnt_T_u08	uint8	0	1
	VltgSwd2Ok_Cnt_T_u08	uint8	0	1
Return Value	SwdSat_Cnt_T_lgc	boolean	FALSE	TRUE

Description

This function determines if switched battery voltages have reached saturation voltage and was created to reduce cyclomatic complexity and static path count of the Instantaneous Correlation subfunction.

Local Function #5

Function Name	DetNtcQlfrSts	Type	Min	Max
Arguments Passed	Invtr1Inctv_Cnt_T_logl	boolean	FALSE	TRUE
	Invtr2Inctv_Cnt_T_logl	boolean	FALSE	TRUE
	VltgOk_Cnt_T_u08	uint8	0	1
	Swd1Ok_Cnt_T_u08	uint8	0	1
	Swd2Ok_Cnt_T_u08	uint8	0	1
	*Ntc3CQlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD
	*Ntc3CQlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD
	*Ntc3CQlfrSts_Cnt_T_enum	enum	SIGQLFR_NORES	SIGQLFR_FAILD

Description

This function implements the NTC <xx> blocks in the Determine Independent Signals subfunction. It sets each NTC status based on the OK status of each voltage signal. Then, the NTC qualifier status for each signal is retrieved and saved in the corresponding enum parameter. This function was created to reduce complexity and static path count of the Determine Independent Signals subfunction.

Local Function #6

Function Name	FlgChk	Type	Min	Max
Arguments Passed	FlgIn_Cnt_T_logl	boolean	FALSE	TRUE
	*FlgOut_Cnt_T_u08	uint8	0	1

*FlgOut_Cnt_T_u08 is an output of this function.

Description

If Input flag is 'TRUE', then set output flag to 'FASLE'. Otherwise don't do anything. This function is added to reduce cyclomatic complexity of 'InstCorrln' function.

Local Function #7

Function Name	RngChk	Type	Min	Max
Arguments Passed	Vltg_Volt_T_f32	float32	0	40
	VltgSwd1_Volt_T_f32	float32	0	40
	VltgSwd2_Volt_T_f32	float32	0	40
	*VltgRngOk_Cnt_T_u08	uint8	0	1
	*Swd1RngOk_Cnt_T_u08	uint8	0	1
	*Swd2RngOk_Cnt_T_u08	uint8	0	1

*VltgRngOk_Cnt_T_u08, *Swd1RngOk_Cnt_T_u08 and *Swd2RngOk_Cnt_T_u08 are outputs of this function.

Description

Implements “Range Check” block in the model. Created to reduce cyclomatic complexity and static path count.

Transition Functions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

None

Abbreviations and Acronyms

None

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.3.0 R4.0 Rev 2
2	MDD Guideline	EA4 01.00.00
3	Software Naming Conventions.doc	2.0
4	Software Design and Coding Standards.doc	2.1
5	FDD – ES259A Battery or Switched Voltage Correlation	See Synergy subproject version

3 - BattVltgCorrln_PeerReview

Overview

Summary Sheet
Synergy Project
Source Code
PolySpace

Sheet 1: Summary Sheet

Rev 1.2

8-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. ES259A_BattVltgCorrln_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. 2.1.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. Nick Saxton

Work CR ID:

EA4#6383

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:

MDD

Yes

Source Code

Yes

PolySpace

Integration Manual

Davinci Files

Comments:

Only reviewed changes - fixed incorrect status bit being used in setting NTC 3C

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:

Nick Saxton

Review Date :

06/21/16

Lead Peer Reviewer:

Krishna Anne

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 3: Source Code

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Source Code Review)

Source File Name:

BattVltgCorrln.c

Source File Revision:

Header File Name:

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.

MDD Name:

BattVltgCorrln_MDD.doc

Revision:

FDD/SCIR/DSR/FDR/CM Name:

ES259A_BattVltgCorrln_Design

Revision:

2.0.1

Quality Check Items:

Rationale is required for all answers of No

Working EA4 Software Naming Convention followed:

for variable names

N/A

Comments:

for constant names

N/A

Comments:

for function names

N/A

Comments:

for other names (component, memory

N/A

Comments:

mapping handles, typedefs, etc.)

All paths assign a value to outputs, ensuring

N/A

Comments:

all outputs are initialized prior to being written

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

N/A

Comments:

requirements tracability in the FDD

All variables are declared at the function level.

N/A

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

N/A

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

N/A

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

N/A

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

N/A

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,

N/A

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

N/A

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]

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:

Change Owner:

Nick Saxton

Review Date :

06/21/16

Lead Peer Reviewer:

Krishna Anne

Approved by Reviewer(s):

Yes

Other Reviewer(s):

Sheet 4: PolySpace

Rev 1.2

8-Jun-15

Peer Review Meeting Log (QAC/PolySpace Review)

Source File Name:

BattVltgCorrln.c

Source File Revision:

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 Analysis

Yes

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:

Change Owner:

Nick Saxton

Review Date :

06/21/16

Lead Peer Reviewer:

Krishna Anne

Approved by Reviewer(s):

Yes

Other Reviewer(s):

4 - requirements

FDD	ID	Source	Function	Line(s)	Status	Comment
		.SwFileName	.SwFuncName	.SwLines	.SwStatus	.SwComment
ES259A	146	BattVltgCorrln.c	BattVltgCorrlnPer1	950	I
ES259A	214	BattVltgCorrln.c	BattVltgCorrlnPer1	994	I
ES259A	152	BattVltgCorrln.c	DetSwdSat	1345-1374	I
ES259A	199	BattVltgCorrln.c	BattVltgCorrlnPer1	857	I
ES259A	154	BattVltgCorrln.c	DetSwdSat	1347-1376	I
ES259A	147	BattVltgCorrln.c	BattVltgCorrlnPer1	950	I
ES259A	195	BattVltgCorrln.c	BattVltgCorrlnPer1	856	I
ES259A	67	BattVltgCorrln.c	BattVltgCorrlnPer1	853	I
ES259A	153	BattVltgCorrln.c	DetSwdSat	1346-1375	I
ES259A	133	BattVltgCorrln.c	DetNtcQlfrSts	1428	I
ES259A	68	BattVltgCorrln.c	BattVltgCorrlnPer1	852	I
ES259A	89	BattVltgCorrln.c	BattVltgCorrlnPer1	951	I
ES259A	65	BattVltgCorrln.c	BattVltgCorrlnPer1	854	I
ES259A	66	BattVltgCorrln.c	BattVltgCorrlnPer1	855	I
ES259A	178	BattVltgCorrln.c	BattVltgCorrlnPer1	864-945	I
ES259A	177	BattVltgCorrln.c	BattVltgCorrlnPer1	865-946	I
ES259A	83	BattVltgCorrln.c	InstCorrln	1179	I
ES259A	175	BattVltgCorrln.c	BattVltgCorrlnPer1	869-902,916-943	I
ES259A	174	BattVltgCorrln.c	BattVltgCorrlnPer1	904-914	I
ES259A	172	BattVltgCorrln.c	BattVltgCorrlnPer1	864-945	I
ES259A	171	BattVltgCorrln.c	BattVltgCorrlnPer1	865-946	I
ES259A	85	BattVltgCorrln.c	DetNtcQlfrSts	1461	I
ES259A	25	BattVltgCorrln.c	BattVltgCorrlnPer1	951	I
ES259A	138	BattVltgCorrln.c	BattVltgCorrlnPer1	961-977	I
ES259A	20	BattVltgCorrln.c	BattVltgCorrlnPer1	858-1260	I
ES259A	91	BattVltgCorrln.c	DetNtcQlfrSts	1477	I
ES259A	48	BattVltgCorrln.c	BattVltgCorrlnPer1	850	I
ES259A	49	BattVltgCorrln.c	BattVltgCorrlnPer1	851	I
ES259A	28	BattVltgCorrln.c	DetNtcQlfrSts	1452	I
ES259A	87	BattVltgCorrln.c	DetNtcQlfrSts	1474,1480	I
ES259A	182	BattVltgCorrln.c	BattVltgCorrlnPer1	869-879,916-943	I
ES259A	183	BattVltgCorrln.c	BattVltgCorrlnPer1	865-946	I
ES259A	180	BattVltgCorrln.c	BattVltgCorrlnPer1	881-902	I
ES259A	186	BattVltgCorrln.c	BattVltgCorrlnPer1	869-879	I
ES259A	84	BattVltgCorrln.c	InstCorrln	1173	I
ES259A	184	BattVltgCorrln.c	BattVltgCorrlnPer1	864-945	I
ES259A	188	BattVltgCorrln.c	BattVltgCorrlnPer1	881-943	I
ES259A	201	BattVltgCorrln.c	BattVltgCorrlnPer1	858	I
ES259A	200	BattVltgCorrln.c	BattVltgCorrlnPer1	859	I
ES259A	142	BattVltgCorrln.c	DetNtcQlfrSts	1438	I
ES259A	143	BattVltgCorrln.c	DetNtcQlfrSts	1463	I
ES259A	140	BattVltgCorrln.c	DetIdptSig	1241-1280	I
ES259A	141	BattVltgCorrln.c	DetIdptSig	1241-1280	I
ES259A	139	BattVltgCorrln.c	DetIdptSig	1241-1280	I
ES259A	148	BattVltgCorrln.c	BattVltgCorrlnPer1	950	I
ES259A	77	BattVltgCorrln.c	InstCorrln	1146,1163-1270	I
ES259A	76	BattVltgCorrln.c	BattVltgCorrlnPer1	981-987	I
ES259A	75	BattVltgCorrln.c	InstCorrln	1154	I
ES259A	74	BattVltgCorrln.c	DetIdptSig	1240-1279	I
ES259A	73	BattVltgCorrln.c	DetIdptSig	1240-1279	I
ES259A	126	BattVltgCorrln.c	DetNtcQlfrSts	1426,1431	I
ES259A	128	BattVltgCorrln.c	BattVltgCorrlnPer1	951	I
ES259A	94	BattVltgCorrln.c	DetNtcQlfrSts	1471	I
ES259A	78	BattVltgCorrln.c	DetIdptSig	1240-1279	I
ES259A	150	BattVltgCorrln.c	BattVltgCorrlnPer1	993	I
ES259A	134	BattVltgCorrln.c	BattVltgCorrlnPer1	992	I
ES259A	155	BattVltgCorrln.c	DetSwdSat	1348-1377	I
ES259A	22	BattVltgCorrln.c	DetNtcQlfrSts	1449,1455	I
ES259A	80	BattVltgCorrln.c	DetIdptSig	1240-1279	I
ES259A	132	BattVltgCorrln.c	DetNtcQlfrSts	1423	I
ES259A	18	BattVltgCorrln.c	BattVltgCorrlnPer1	849	I
ES259A	31	BattVltgCorrln.c	DetNtcQlfrSts	1446	I
ES259A	51	BattVltgCorrln.c	BattVltgCorrlnPer1	991	I
ES259A	53	BattVltgCorrln.c	InstCorrln	1184	I
ES259A	81	BattVltgCorrln.c	DetIdptSig	1240-1279	I
ES259A	124	BattVltgCorrln.c	DetNtcQlfrSts	1421	I