Sr. No.	Title	Version
1	FDD : SF049A_LoaMgr_Design	See Synergy sub project version
2	Software Naming Conventions	Process 4.02.00
3	Software Design and Coding Standards	Process 4.02.00

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

Required Global Data Outputs

Refer DataDict.m file file in the FDD

Specific Include Path present

Runnable Scheduling

This section specifies the required runnable scheduling.

Init	Scheduling Requirements	Trigger
LoaMgrInit1	None	RTE (Init)

Runnable	Scheduling Requirements	Trigger
LoaMgrPer1	None	RTE (4 ms)

Memory Map REQUIREMENTS

Mapping

Memory Section	Contents	Notes
None

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

Usage

Feature	RAM	ROM
None

Table 1: ARM Cortex R4 Memory Usage

NvM Blocks

None

Compiler Settings

Preprocessor MACRO

None.

Optimization Settings

None.

Appendix

None

2 - LoaMgr_MDD

Module Design Document

For

LoaMgr

June 22, 2016 Prepared For:

Software Engineering

Nexteer Automotive,

Saginaw, MI, USA

Prepared By:

Sankardu Varadapureddi,

Nexteer Automotive,

Saginaw, MI, USA
Change History

Description	Author	Version	Date
Initial Version	Sankardu Varadapureddi	1	04-Aug-2015
Updated to design version 2.0.0	Sarika Natu	2	22-Jun-16

Table of Contents

1 Introduction 5

1.1 Purpose 5

1.2 Scope 5

2 LoaMgr High-Level Description 6

3 Design details of software module 7

3.1 Graphical representation of LoaMgr 7

3.2 Data Flow Diagram 7

3.2.1 Component level DFD 8

3.2.2 Function level DFD 8

4 Constant Data Dictionary 9

4.1 Program (fixed) Constants 9

4.1.1 Embedded Constants 9

5 Software Component Implementation 10

5.1 Sub-Module Functions 10

5.1.1 Init: LoaMgrInit1 10

5.1.1.1 Design Rationale 10

5.1.1.2 Module Outputs 10

5.1.2 Per: LoaMgrPer1 10

5.1.2.1 Design Rationale 10

5.1.2.2 Store Module Inputs to Local copies 10

5.1.2.3 (Processing of function)……… 10

5.1.2.4 Store Local copy of outputs into Module Outputs 10

5.2 Server Runables 10

5.3 Interrupt Functions 10

5.4 Module Internal (Local) Functions 10

5.4.1 Local Function #1 10

5.4.1.1 Design Rationale 10

5.4.1.2 Processing 11

5.4.2 Local Function #2 11

5.4.2.1 Design Rationale 11

5.4.2.2 Processing 11

5.4.3 Local Function #3 11

5.4.3.1 Design Rationale 11

5.4.3.2 Processing 11

5.4.4 Local Function #4 11

5.4.4.1 Design Rationale 11

5.4.4.2 Processing 11

5.4.5 Local Function #5 11

5.4.5.1 Design Rationale 12

5.4.5.2 Processing 12

5.4.6 Local Function #6 12

5.4.6.1 Design Rationale 12

5.4.6.2 Processing 12

5.4.7 Local Function #7 12

5.4.7.1 Design Rationale 12

5.4.7.2 Processing 12

5.4.8 Local Function #8 13

5.4.8.1 Design Rationale 13

5.4.8.2 Processing 13

5.5 GLOBAL Function/Macro Definitions 13

6 Known Limitations with Design 14

7 UNIT TEST CONSIDERATION 15

Appendix A Abbreviations and Acronyms 16

Appendix B Glossary 17

Appendix C References 18

Introduction

Purpose

Scope

LoaMgr High-Level Description

Refer to FDD

Design details of software module

Graphical representation of LoaMgr

Data Flow Diagram

Refer FDD

Component level DFD

Function level DFD

Constant Data Dictionary

Program (fixed) Constants

Embedded Constants

Local Constants

Constant Name	Resolution	Units	Value
Refer .m file

Software Component Implementation

Sub-Module Functions

Init: LoaMgrInit1

Design Rationale

Refer FDD

Module Outputs

Refer FDD

Per: LoaMgrPer1

Design Rationale

Refer FDD

Store Module Inputs to Local copies

Refer FDD

(Processing of function)………

Refer FDD

Store Local copy of outputs into Module Outputs

Refer FDD

Server Runables

None

Interrupt Functions

None

Module Internal (Local) Functions

Local Function #1

Function Name	ReqHwTqResp	Type	Min	Max
Arguments Passed	HwTqIdptMin_Cnt_T_u08	uint8	0	4
	TqLoaAvl_Cnt_T_lgc	boolean	FALSE	TRUE
Return Value	HwTqResp_Cnt_T_u08	uint8	0	5

Design Rationale

None

Processing

Refer to ‘HwTqResp’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Request_Responses’

Local Function #2

Function Name	ReqMotAgResp	Type	Min	Max
Arguments Passed	MotAgIdptMin_Cnt_T_u08	uint8	0	3
	SmpAvl_Cnt_T_lgc	boolean	FALSE	TRUE
Return Value	MotAgResp_Cnt_T_u08	uint8	0	5

Design Rationale

None

Processing

Refer to ‘MotAgResp’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Request_Responses’

Local Function #3

Function Name	ReqCurrMeasResp	Type	Min	Max
Arguments Passed	CurrMeasIdptMin_Cnt_T_u08	uint8	0	2
Return Value	CurrMeasResp_Cnt_T_u08	uint8	0	5

Design Rationale

None

Processing

Refer to ‘CurrMeasResp’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Request_Responses’

Local Function #4

Function Name	ReqInvtrResp	Type	Min	Max
Arguments Passed	IvtrIdptMin_Cnt_T_u08	uint8	0	2
Return Value	InvtrResp_Cnt_T_u08	uint8	0	5

Design Rationale

None

Processing

Refer to ‘CurrMeasResp’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Request_Responses’

Local Function #5

Function Name	CntSwBasdMtgtnChk	Type	Min	Max
Arguments Passed	Resp_Cnt_T_u08	uint8	0	5
	PrevMtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE
Return Value	MtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE

Design Rationale

None

Processing

This function corresponds to common logic (for all requests) in ‘CntSwBasdMtgtn’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Arbitrate_Responses’

Local Function #6

Function Name	SelFinalResp	Type	Min	Max
Arguments Passed	MultiMtgtnResp_Cnt_T_u08	uint8	0	5
	HwTqResp_Cnt_T_u08	uint8	0	5
	MotAgResp_Cnt_T_u08	uint8	0	5
	CurrMeasResp_Cnt_T_u08	uint8	0	5
	InvtrResp_Cnt_T_u08	uint8	0	5
Return Value	LoaSt_Cnt_T_enum	LoaSt1	0	5

Design Rationale

None

Processing

This function corresponds to ‘SelFinalResp’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Arbitrate_Responses’

Local Function #7

Function Name	SetFaults	Type	Min	Max
Arguments Passed	LoaSt_Cnt_T_enum	LoaSt1	0	5
	HwTqIdptMin_Cnt_T_u08	uint8	0	4
	MotAgIdptMin_Cnt_T_u08	uint8	0	3
	CurrMeasIdptMin_Cnt_T_u08	uint8	0	2
	IvtrIdptMin_Cnt_T_u08	uint8	0	2
Return Value	None

Design Rationale

None

Processing

This function corresponds to ‘Set_Faults’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1’

Local Function #8

Function Name	SwMtgtnEn	Type	Min	Max
Arguments Passed	HwTqLoaMtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE
	MotAgLoaMtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE
	CurrMeasLoaMtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE
	IvtrLoaMtgtnEna_Cnt_T_lgc	boolean	FALSE	TRUE
	*LoaSca_Uls_T_f32	float32	0	1
	*LoaRateLim_UlsPerSec_T_f32	float32	0.01	500
Return Value	None

Design Rationale

None

Processing

This function corresponds to ‘SwMtgtn’ block in FDD at ‘SF049A_LoaMgr/LoaMgr/LoaMgrPer1/Assign_Scale’.

Note that ‘*LoaSca_Uls_T_f32’ and ‘*LoaRateLim_UlsPerSec_T_f32’ are the outputs of this function.

GLOBAL Function/Macro Definitions

None

Known Limitations with Design

None

UNIT TEST CONSIDERATION

None

Abbreviations and Acronyms

Abbreviation or Acronym	Description

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.01
3	Software Naming Conventions.doc	EA4 01.00.00
4	Software Design and Coding Standards.doc	2.1
5	FDD : SF049A_LoaMgr_Design	See Synergy sub project version

3 - LoaMgr_Review

Overview

Summary Sheet
Synergy Project
Davinci Files
Source Code
MDD
PolySpace
Integration Manual

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. SF049A_LoaMgr_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. SF049A_LoaMgr_Impl

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. Sarika Natu

Work CR ID:

EA4#5741

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

Source Code

PolySpace

Integration Manual

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

Comments:

naming convention

Project contains necessary subprojects

Comments:

Project contains the correct version of subprojects

Comments:

Design subproject is correct version

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:

Sarika Natu

Review Date :

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 3: Davinci Files

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Davinci Review)

Quality Check Items:

Rationale is required for all answers of No

Only StdDef Port types are used

Yes

Comments:

For components not using application data types, do all

Yes

Comments:

port interface names end in PortIf and a sequence number

Non-program-specific components saved

Yes

Comments:

in Autosar 4.0.3 format

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

N/A

Comments:

change correctly

*Cfg.h.TT: Verfied Davinci Configurator generates

N/A

Comments:

the configuration header(s) file correctly

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

All changed files have been compared against previous

Yes

Comments:

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.

Automated validation check is performed

Yes

Comments:

Naming conventions followed. All names should

Yes

Comments:

match DataDict.m

Sender/Receiver port properties match DataDict.m

Yes

Comments:

file (use .m file helper tool)

Calibration port properties match DataDict.m

Yes

Comments:

file (use .m file helper tool)

Components using application data types:

Sender/Receiver port initialization values match

N/A

Comments:

DataDict.m file

Calibration port initialization values match

N/A

Comments:

DataDict.m file

Components not using application data types:

Sender/Receiver port initialization values match

Yes

Comments:

DataDict.m file and have been converted to counts

for fixed point types

Calibration port initialization values match

Yes

Comments:

DataDict.m file and have been converted to counts

for fixed point types

Mapping set and all unused items have been

Yes

Comments:

removed

All sender/receiver port read/writes using direct

Yes

Comments:

read/writes(List justification if not)

Runnable calling frequencies match FDD

N/A

Comments:

DataDict.m display variables: created as

Yes

Comments:

PerInstanceMemory. Matches the FDD

Component is correct component type

Yes

Comments:

General Notes / Comments:

Change Owner:

Sarika Natu

Review Date :

Component Type :

Application

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 4: Source Code

Rev 1.2

8-Jun-15

Peer Review Meeting Log (Source Code Review)

Source File Name:

LoaMgr.c

Source File Revision:

Header File Name:

None

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:

LoaMgr_MDD.docx

Revision:

FDD/SCIR/DSR/FDR/CM Name:

SF049A_LoaMgr_Design

Revision:

SF049A_LoaMgr_Design_2.0.0

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

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

Yes

Comments:

requirements tracability in the FDD

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:

CR No : EA4#5741

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:

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

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: CR number: EA4#5741

for any FDD corrections needed

General Notes / Comments:

Change Owner:

Sarika Natu

Review Date :

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 5: MDD

Rev 1.2

8-Jun-15

Peer Review Meeting Log (MDD Review)

MDD Name:

LoaMgr_MDD.docx

MDD Revision:

Source File Name:

LoaMgr.c

Source File Revision:

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

Yes

Comments:

and reviewed

All Design Exceptions and Limitations are listed

N/A

Comments:

Design rationale given for all global

N/A

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

N/A

Comments:

General Notes / Comments:

Change Owner:

Sarika Natu

Review Date :

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 6: PolySpace

Rev 1.2

8-Jun-15

Peer Review Meeting Log (QAC/PolySpace Review)

Source File Name:

LoaMgr.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 Not released

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

Sarika Natu

Review Date :

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

Sheet 7: Integration Manual

Rev 1.2

8-Jun-15

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. LoaMgr_IntegrationManual.doc

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:

Rationale is required for all answers of No

Synergy version matches header

N/A

Comments:

Latest template used

N/A

Comments:

Change log contains detailed description of changes

N/A

Comments:

Changes Highlighted (for Integrator)

N/A

Comments:

Initial version

General Notes / Comments:

Change Owner:

Sarika Natu

Review Date :

Lead Peer Reviewer:

Approved by Reviewer(s):

Other Reviewer(s):

4 - requirements

FDD	ID	Source	Function	Line(s)	Status	Comment
		.SwFileName	.SwFuncName	.SwLines	.SwStatus	.SwComment
SF049A	154	LoaMgr.c	SetFaults	1355	I
SF049A	127	LoaMgr.c	SetFaults	1340	I
SF049A	176	LoaMgr.c	LoaMgrPer1	923-928	I
SF049A	60	LoaMgr.c	LoaMgrPer1	915	I
SF049A	61	LoaMgr.c	LoaMgrPer1	916	I
SF049A	62	LoaMgr.c	LoaMgrPer1	924	I
SF049A	64	LoaMgr.c	LoaMgrPer1	932	I
SF049A	65	LoaMgr.c	LoaMgrPer1	940	I
SF049A	178	LoaMgr.c	LoaMgrPer1	939-944	I
SF049A	177	LoaMgr.c	LoaMgrPer1	931-936	I
SF049A	69	LoaMgr.c	LoaMgrPer1	952-956	I
SF049A	175	LoaMgr.c	LoaMgrPer1	914-920	I
SF049A	81	LoaMgr.c	LoaMgrPer1	992	I
SF049A	173	LoaMgr.c	LoaMgrInit1	787	I
SF049A	80	LoaMgr.c	LoaMgrPer1	991	I
SF049A	104	LoaMgr.c	SwMtgtnEn	1432-1433,1448-1449,1464-1465	I
SF049A	48	LoaMgr.c	LoaMgrPer1	1075	I
SF049A	49	LoaMgr.c	LoaMgrPer1	1077	I
SF049A	46	LoaMgr.c	LoaMgrPer1	1076	I
SF049A	47	LoaMgr.c	LoaMgrPer1	1081	I
SF049A	44	LoaMgr.c	LoaMgrPer1	881	I
SF049A	43	LoaMgr.c	LoaMgrPer1	880	I
SF049A	105	LoaMgr.c	SwMtgtnEn	1424,1440,1456	I
SF049A	118	LoaMgr.c	SetFaults	1332	I
SF049A	183	LoaMgr.c	LoaMgrPer1	888	I
SF049A	186	LoaMgr.c	LoaMgrPer1	893	I
SF049A	187	LoaMgr.c	LoaMgrPer1	898	I
SF049A	184	LoaMgr.c	LoaMgrPer1	882	I
SF049A	188	LoaMgr.c	LoaMgrPer1	903	I
SF049A	96	LoaMgr.c	LoaMgrPer1	1054-1057	I
SF049A	68	LoaMgr.c	LoaMgrPer1	951-955	I
SF049A	145	LoaMgr.c	SetFaults	1350	I
SF049A	97	LoaMgr.c	LoaMgrPer1	1061-1064	I
SF049A	83	LoaMgr.c	LoaMgrPer1	993	I
SF049A	100	LoaMgr.c	LoaMgrPer1,SwMtgtnEn	1035-1043,1399-1408	I
SF049A	136	LoaMgr.c	SetFaults	1345	I
SF049A	99	LoaMgr.c	LoaMgrPer1,SwMtgtnEn	1034-1042,1388-1389	I
SF049A	75	LoaMgr.c	LoaMgrPer1	975-979	I
SF049A	74	LoaMgr.c	LoaMgrPer1	974-978	I
SF049A	73	LoaMgr.c	LoaMgrPer1	968-972	I
SF049A	72	LoaMgr.c	LoaMgrPer1	967-971	I
SF049A	71	LoaMgr.c	LoaMgrPer1	959-963	I
SF049A	70	LoaMgr.c	LoaMgrPer1	958-962	I
SF049A	102	LoaMgr.c	SwMtgtnEn	1399-1408	I
SF049A	93	LoaMgr.c	LoaMgrPer1	1020-1023	I
SF049A	101	LoaMgr.c	SwMtgtnEn	1399-1408	I
SF049A	95	LoaMgr.c	LoaMgrPer1	1047-1050	I
SF049A	94	LoaMgr.c	LoaMgrPer1	1027-1030	I
SF049A	79	LoaMgr.c	LoaMgrPer1	984-989	I
SF049A	78	LoaMgr.c	LoaMgrPer1	983-988	I
SF049A	115	LoaMgr.c	SetFaults	1328	I
SF049A	13	LoaMgr.c	LoaMgrPer1	885	I
SF049A	12	LoaMgr.c	LoaMgrPer1	883	I
SF049A	14	LoaMgr.c	LoaMgrPer1	884	I
SF049A	17	LoaMgr.c	LoaMgrInit1	787	I
SF049A	16	LoaMgr.c	LoaMgrPer1	1080	I
SF049A	18	LoaMgr.c	LoaMgrPer1	882	I
SF049A	108	LoaMgr.c	LoaMgrPer1,SwMtgtnEn	1087,1416-1475	I
SF049A	107	LoaMgr.c	SwMtgtnEn	1416-1475	I
SF049A	110	LoaMgr.c	LoaMgrPer1	1084	I
SF049A	203	LoaMgr.c	LoaMgrPer1	1073-1080	I