instruction stringlengths 29 35k | input stringclasses 1 value | output stringlengths 29 35k |
|---|---|---|
[DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity -----------------------------------------------------------------------------------------------------------------------------------------------------
Aim:
The following "Software Behaviours" shall be implemented (SW Requirements) with this CR:
- TBD
which correspond to the following "System Features":
- SF 10.1 Provide Vehicle Velocity
Description:
For this System Feature (from DCRP), the aforementioned Software Behaviours have been identified, and these need to be derived and released in the SwRS.
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
1. DAI SYS.1: "Fahrzeuggeschwindigkeit bereitstellen".
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011dd92.
b. Filter: (((ZF_Supplier_Status == partly agreed) OR (ZF_Supplier_Status == agreed)) AND (Object Type == requirement) AND (xxx_Planned_Delivery == X0260) AND (Attribute "151_SoftwareBehaviour" contains one or the other aforementioned Software Behaviours))
c. For PSW Behaviours, please also consider only those source requirements where "091_Req_Class_Discipline" is set to "SWE.1".
d. For BSW Behaviours, no distinction is to be made based on the attribute "091_Req_Class_Discipline", while deriving SW-Requirements.
2. DAI SYS.3 IBC (including TSC): "SyDesign".
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001537e2.
b. Filter: (((Attribute '011_Object State_DXL' contains 'Approved') OR (011_Object State == 04 Approved)) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (016_(Sub)System == software) AND (Attribute "DXL for 140_System Feature (SyRS)" OR Attribute "DXL for 140_System Feature (TSC)" contains one or the other aforementioned System Features)).
3. DAI SYS.3 EPB (including TSC): "SyDesign" (Only for the ESS part).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00143fc1.
b. Filter: (((Attribute '011_Object State_DXL' contains 'Approved') OR (011_Object State == 04 Approved)) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (016_(Sub)System == software)).
4. DAI HWE.2 IBC: "DAI_MMA IBC GEN2 ECU AD" (Read-Only Module).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d856.
b. Filter: ((011_Object State == 04 Approved) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (115_ECU_(Sub)System == ECU related SW)).
5. Core HWE.2 IBC: "IBC Gen2 ECU AD" (Only for connecting CSC SwRS to Core GEE and to tag Core GEE requirements to the right Software Behaviours).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000cce21.
b. Filter: ((011_Object State == 04 Approved) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (115_ECU_(Sub)System == ECU related SW)).
Output Document(s):
All SWE.1 related artefacts including the Slave Module Baselines in the DAI MMA IBC application project (SW Requirement Specifications, SW Parameter Table, et. al.)!
Acceptance Criteria(s):
1. SW Requirements are released (incl. Stakeholder and Formal Reviews) in the application slave modules.
2. SW Requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the Attribute "014_Requirement Source Comment" in the application slave modules.
3. Attribute "151_SoftwareBehaviour" is tagged in source documents (such as SyDesign and Core ECU AD), when these parent requirements are linked to SwRS.
4. Source requirements are reviewed via proper checklists and review findings are provided.
----------------------------------------------------------------------------------------------------------------------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------
[25.08.2021, KrauseT3]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
No source requirement identified for the affected system feature in valid state to be derived.
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
--> reject this CR | [DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity -----------------------------------------------------------------------------------------------------------------------------------------------------
Aim:
The following "Software Behaviours" shall be implemented (SW Requirements) with this CR:
- TBD
which correspond to the following "System Features":
- SF 10.1 Provide Vehicle Velocity
Description:
For this System Feature (from DCRP), the aforementioned Software Behaviours have been identified, and these need to be derived and released in the SwRS.
Source Document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
1. DAI SYS.1: "Fahrzeuggeschwindigkeit bereitstellen".
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011dd92.
b. Filter: (((ZF_Supplier_Status == partly agreed) OR (ZF_Supplier_Status == agreed)) AND (Object Type == requirement) AND (xxx_Planned_Delivery == X0260) AND (Attribute "151_SoftwareBehaviour" contains one or the other aforementioned Software Behaviours))
c. For PSW Behaviours, please also consider only those source requirements where "091_Req_Class_Discipline" is set to "SWE.1".
d. For BSW Behaviours, no distinction is to be made based on the attribute "091_Req_Class_Discipline", while deriving SW-Requirements.
2. DAI SYS.3 IBC (including TSC): "SyDesign".
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001537e2.
b. Filter: (((Attribute '011_Object State_DXL' contains 'Approved') OR (011_Object State == 04 Approved)) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (016_(Sub)System == software) AND (Attribute "DXL for 140_System Feature (SyRS)" OR Attribute "DXL for 140_System Feature (TSC)" contains one or the other aforementioned System Features)).
3. DAI SYS.3 EPB (including TSC): "SyDesign" (Only for the ESS part).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00143fc1.
b. Filter: (((Attribute '011_Object State_DXL' contains 'Approved') OR (011_Object State == 04 Approved)) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (016_(Sub)System == software)).
4. DAI HWE.2 IBC: "DAI_MMA IBC GEN2 ECU AD" (Read-Only Module).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0013d856.
b. Filter: ((011_Object State == 04 Approved) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (115_ECU_(Sub)System == ECU related SW)).
5. Core HWE.2 IBC: "IBC Gen2 ECU AD" (Only for connecting CSC SwRS to Core GEE and to tag Core GEE requirements to the right Software Behaviours).
a. Link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-000cce21.
b. Filter: ((011_Object State == 04 Approved) AND ((010_Object Type == Definition) OR (010_Object Type == Requirement)) AND (115_ECU_(Sub)System == ECU related SW)).
Output Document(s):
All SWE.1 related artefacts including the Slave Module Baselines in the DAI MMA IBC application project (SW Requirement Specifications, SW Parameter Table, et. al.)!
Acceptance Criteria(s):
1. SW Requirements are released (incl. Stakeholder and Formal Reviews) in the application slave modules.
2. SW Requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the Attribute "014_Requirement Source Comment" in the application slave modules.
3. Attribute "151_SoftwareBehaviour" is tagged in source documents (such as SyDesign and Core ECU AD), when these parent requirements are linked to SwRS.
4. Source requirements are reviewed via proper checklists and review findings are provided.
----------------------------------------------------------------------------------------------------------------------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------
[25.08.2021, KrauseT3]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
No source requirement identified for the affected system feature in valid state to be derived.
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
--> reject this CR | |
[DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity SW Architectural Design for feature implementation of [DCRP 84.1 ML1][IBC][SW-AD] SF 10.1 Provide Vehicle Velocity - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
- SW architechtural design
--------------------------------------------------------------------------------
Acceptance Criteria:
- SW architechtural design is defined identifying SW elements
- SW Requirements are allocated to the SW elements
- SW interfaces are defined
- dynamic behavior for software elements is defined
- Consistency and traceability between requirements and SW elements is identified
- SW architechtural design is released
-------------------------------------------------------------------------------- 2021-10-01 C. Klukowski:
Details were discussed with stakeholders, refert attached pdf 'CustPsw.pdf'.
In general composition, components, runnables need to be created.
Mapping of runnables to Task.
Allocation to dspr, pflash, coexistence, coreAlloction.
The ASILs shall be carried over from MRA_V3 (ASIL D).
A task for SwAD and build&integration team will be created in order to update the SW Build view.
Requirements are not available, behaviors are not defined.
Budgets will be carried over from resource estimation sheet.
2021-08-16 C. Klukowski:
Agree to summary of comment 'SWPM (J. Barg) (10.09.21 - 11:02)', but the Build target date needs to be shifted changed too. I have requested to change the target date once via mail and once within the standup meeting.
SWPM (J. Barg) (10.09.21 - 11:02):
--------------------------------------------------------------------------------
For this feature the module CustPSW needs to be implemented in X0260.
Meeting decision 2021-09-10 (J. Barg, O. Schumacher, F. Rausch, C. Klukowski, O. Rink, C. Knechtges):
This CR should be used to provide minimum information to Integration team to implement CustPSW module.
In first step a carry over of CustPSW from MRA project is planned for X0260.
For implementation of PSW CR5569339 and 5569345 will be used.
--------------------------------------------------------------------------------
2021-08-05 B. Lyubenov, C. Klukowski:
Analyze the required content of the SwRS.
Update model:
- Impacted behaviors
- Define Rte interfaces, please also cover Comms Tx/Rx signal list Link: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/Daimler/MMA/IBC/01%5fRequirements/04%5fSW/VC%5fInterfaces%5fSignals%5fList/project.pj&selection=%22Rx%5fTx%5fList%5fDaimler%5fMMA.xlsx%22
- Technical interfaces and map to funct. interfaces at behaviors
- Create task for domain architect
- Import requirements and map them
- Model NvMblocks
- Cover scheduling/runnables | [DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity SW Architectural Design for feature implementation of [DCRP 84.1 ML1][IBC][SW-AD] SF 10.1 Provide Vehicle Velocity - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
- SW architechtural design
--------------------------------------------------------------------------------
Acceptance Criteria:
- SW architechtural design is defined identifying SW elements
- SW Requirements are allocated to the SW elements
- SW interfaces are defined
- dynamic behavior for software elements is defined
- Consistency and traceability between requirements and SW elements is identified
- SW architechtural design is released
-------------------------------------------------------------------------------- 2021-10-01 C. Klukowski:
Details were discussed with stakeholders, refert attached pdf 'CustPsw.pdf'.
In general composition, components, runnables need to be created.
Mapping of runnables to Task.
Allocation to dspr, pflash, coexistence, coreAlloction.
The ASILs shall be carried over from MRA_V3 (ASIL D).
A task for SwAD and build&integration team will be created in order to update the SW Build view.
Requirements are not available, behaviors are not defined.
Budgets will be carried over from resource estimation sheet.
2021-08-16 C. Klukowski:
Agree to summary of comment 'SWPM (J. Barg) (10.09.21 - 11:02)', but the Build target date needs to be shifted changed too. I have requested to change the target date once via mail and once within the standup meeting.
SWPM (J. Barg) (10.09.21 - 11:02):
--------------------------------------------------------------------------------
For this feature the module CustPSW needs to be implemented in X0260.
Meeting decision 2021-09-10 (J. Barg, O. Schumacher, F. Rausch, C. Klukowski, O. Rink, C. Knechtges):
This CR should be used to provide minimum information to Integration team to implement CustPSW module.
In first step a carry over of CustPSW from MRA project is planned for X0260.
For implementation of PSW CR5569339 and 5569345 will be used.
--------------------------------------------------------------------------------
2021-08-05 B. Lyubenov, C. Klukowski:
Analyze the required content of the SwRS.
Update model:
- Impacted behaviors
- Define Rte interfaces, please also cover Comms Tx/Rx signal list Link: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/BRK/Customer/Daimler/MMA/IBC/01%5fRequirements/04%5fSW/VC%5fInterfaces%5fSignals%5fList/project.pj&selection=%22Rx%5fTx%5fList%5fDaimler%5fMMA.xlsx%22
- Technical interfaces and map to funct. interfaces at behaviors
- Create task for domain architect
- Import requirements and map them
- Model NvMblocks
- Cover scheduling/runnables | |
[DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity SWE.6 Software Qualification Test for feature implementation of [DCRP 84.1 ML1][IBC][SW-Testing] SF 10.1 Provide Vehicle Velocity - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
DCRP Customer-LH SW Requirements
--------------------------------------------------------------------------------
Output Work Products:
- Software Qualification Test strategy
- Specification for Software Quelification Tests
- Testcase plan - Test results
- Traceability to SW Requirements and Test Results report
--------------------------------------------------------------------------------
Acceptance Criteria:
Test passed according to SW Requirements Test Results are recorded into Report
-------------------------------------------------------------------------------- Test Execution was not fully performed for this Release due to missing SwRS and lack of availability of the HIL.
These tests will be executed for X0300.
This CR will be rejected. | [DCRP 84.02 ML1] [IBC] SF 10.1 Provide Vehicle Velocity SWE.6 Software Qualification Test for feature implementation of [DCRP 84.1 ML1][IBC][SW-Testing] SF 10.1 Provide Vehicle Velocity - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
DCRP Customer-LH SW Requirements
--------------------------------------------------------------------------------
Output Work Products:
- Software Qualification Test strategy
- Specification for Software Quelification Tests
- Testcase plan - Test results
- Traceability to SW Requirements and Test Results report
--------------------------------------------------------------------------------
Acceptance Criteria:
Test passed according to SW Requirements Test Results are recorded into Report
-------------------------------------------------------------------------------- Test Execution was not fully performed for this Release due to missing SwRS and lack of availability of the HIL.
These tests will be executed for X0300.
This CR will be rejected. | |
[DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request -----------------------------------------------------------------------------------------------------------------------------------------------------
aim:
the following "software behaviours" shall be implemented (sw requirements) with this cr:
- providevehicleconfiguration
- performbrakelightactivation
- transmitvehiclebussignal
- performdistancecontrolrequest
- determinevehiclespeed
which correspond to the following "system features":
- gf 1.11 brake light request
description:
for this system feature (from dcrp), the aforementioned software behaviours have been identified, and these need to be derived and released in the swrs.
source document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
1. dai sys.1: "bremslicht ansteuern".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-0011dd80.
b. filter: (((zf_supplier_status == partly agreed) or (zf_supplier_status == agreed)) and (object type == requirement) and (xxx_planned_delivery == x0260) and (attribute "151_softwarebehaviour" contains one or the other aforementioned software behaviours))
c. for psw behaviours, please also consider only those source requirements where "091_req_class_discipline" is set to "swe.1".
d. for bsw behaviours, no distinction is to be made based on the attribute "091_req_class_discipline", while deriving sw-requirements.
2. dai sys.1: "adaptives bremslicht".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-00119a40.
b. filter: (((zf_supplier_status == partly agreed) or (zf_supplier_status == agreed)) and (object type == requirement) and ((xxx_planned_delivery == x0260) and (attribute "151_softwarebehaviour" contains one or the other aforementioned software behaviours))
c. for psw behaviours, please also consider only those source requirements where "091_req_class_discipline" is set to "swe.1".
d. for bsw behaviours, no distinction is to be made based on the attribute "091_req_class_discipline", while deriving sw-requirements.
3. dai sys.3 ibc (including tsc): "sydesign".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-001537e2.
b. filter: (((attribute '011_object state_dxl' contains 'approved') or (011_object state == 04 approved)) and ((010_object type == definition) or (010_object type == requirement)) and (016_(sub)system == software) and (attribute "dxl for 140_system feature (syrs)" or attribute "dxl for 140_system feature (tsc)" contains one or the other aforementioned system features)).
4. dai sys.3 epb (including tsc): "sydesign" (only for the ess part).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-00143fc1.
b. filter: (((attribute '011_object state_dxl' contains 'approved') or (011_object state == 04 approved)) and ((010_object type == definition) or (010_object type == requirement)) and (016_(sub)system == software)).
5. dai hwe.2 ibc: "dai_mma ibc gen2 ecu ad" (read-only module).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-0013d856.
b. filter: ((011_object state == 04 approved) and ((010_object type == definition) or (010_object type == requirement)) and (115_ecu_(sub)system == ecu related sw)).
5. core hwe.2 ibc: "ibc gen2 ecu ad" (only for connecting csc swrs to core gee and to tag core gee requirements to the right software behaviours).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-000cce21.
b. filter: ((011_object state == 04 approved) and ((010_object type == definition) or (010_object type == requirement)) and (115_ecu_(sub)system == ecu related sw)).
output document(s):
all swe.1 related artefacts including the slave module baselines in the dai mma ibc application project (sw requirement specifications, sw parameter table, et. al.)!
acceptance criteria(s):
1. sw requirements are released (incl. stakeholder and formal reviews) in the application slave modules.
2. sw requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the attribute "014_requirement source comment" in the application slave modules.
3. attribute "151_softwarebehaviour" is tagged in source documents (such as sydesign and core ecu ad), when these parent requirements are linked to swrs.
4. source requirements are reviewed via proper checklists and review findings are provided.
----------------------------------------------------------------------------------------------------------------------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------
[06.08.2021, singhp5]
---------------------------------------------------------------------------------------------------------------------
brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
1. for the aforementioned software behaviours, individual alm_tasks were created per team to cover the swe.1 activities as part of this cr.
2. note: not all source requirements are or can be tagged to the software behaviours (attribute "151_softwarebehaviour") currently. but all the potential source modules are listed in the cr description. when during the swrs development, new source requirments in these source modules are identified, then it is agreed with the sw-development line management, that the relevant sys.1, sys.3 and hwe.2 requirements shall be linked from swrs and tagged to the corresponding software behaviours by the individual alm_task owner.
---------------------------------------------------------------------------------------------------------------------
complexity: [medium]
experience: [known topic]
carry over: [basis available]
---------------------------------------------------------------------------------------------------------------------
proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a)
title/header: develop and release software requirements for the aforementioned software behaviours
description:
create alm_task for each affected software behaviour (or combine several software behaviours for one team) to develop and release software requirements (via reuse of requalified requirements or via project specific tailoring).
the detailed swrs work-instruction, view, and atttribute information for requalification in the mqb-48w ebc swrs is available here:
1. refer to the wiki in zoom page: https://zoom.zf-world.com/sites/com19/groups/14921/pages/wiki/swrs%20requalification.aspx.
2. additional training information for the swrs requalification is available in ptc: swe.1 basic training lite for requalification (https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brksw/teams/softwaresystemengineering/swrequirements/03_training/project.pj&selection=swe.1 basic training lite for requalification.pptx) (esp. under faq section).
acceptance criteria(s):
1. sw requirements are released (incl. stakeholder and formal reviews) in the application slave modules.
2. sw requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the attribute "014_requirement source comment" in the application slave modules.
3. attribute "151_softwarebehaviour" is tagged in source documents (such as sydesign and core ecu ad), when these parent requirements are linked to swrs.
review type: stakeholder review [yes], formal review [yes]
review selection reason: new requirements might be created
review department(s): swe.1, swe.2, swe.3 and swe.6
==> what to review: please check against the corresponding alm_task notes to identify and confirm the swrs module baselines to be reviewed!
==> what checklists: please check against the corresponding alm_task notes to identify, confirm and add the checklists!
estimated effort: 5h (effort only for sw-requirements team for coordination)
---------------------------------------------------------------------------------------------------------------------
b)
title/header: review source requirements for the aforementioned software behaviours
description:
create alm_task for review of all source requirements for the affected software behaviours. capture findings via source document checklist in ptc and provide findings in doors and create a spawned ptc item in case of findings.
acceptance criteria(s):
1. source requirements are reviewed via proper checklists and review findings are provided.
review type: stakeholder review [yes]
review selection reason: source requirements to software
review department(s): swe.1
==> what to review: please check against the corresponding alm_task notes to identify and confirm the source modules to be reviewed!
==> what checklists: please check against the corresponding alm_task notes to identify, confirm and add the checklists!
estimated effort: 5h
---------------------------------------------------------------------------------------------------------------------------------------------------- | [DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request -----------------------------------------------------------------------------------------------------------------------------------------------------
aim:
the following "software behaviours" shall be implemented (sw requirements) with this cr:
- providevehicleconfiguration
- performbrakelightactivation
- transmitvehiclebussignal
- performdistancecontrolrequest
- determinevehiclespeed
which correspond to the following "system features":
- gf 1.11 brake light request
description:
for this system feature (from dcrp), the aforementioned software behaviours have been identified, and these need to be derived and released in the swrs.
source document(s) including baseline information and chapter / other filter criteria to uniquely identify a source requirement checkpoint:
1. dai sys.1: "bremslicht ansteuern".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-0011dd80.
b. filter: (((zf_supplier_status == partly agreed) or (zf_supplier_status == agreed)) and (object type == requirement) and (xxx_planned_delivery == x0260) and (attribute "151_softwarebehaviour" contains one or the other aforementioned software behaviours))
c. for psw behaviours, please also consider only those source requirements where "091_req_class_discipline" is set to "swe.1".
d. for bsw behaviours, no distinction is to be made based on the attribute "091_req_class_discipline", while deriving sw-requirements.
2. dai sys.1: "adaptives bremslicht".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-00119a40.
b. filter: (((zf_supplier_status == partly agreed) or (zf_supplier_status == agreed)) and (object type == requirement) and ((xxx_planned_delivery == x0260) and (attribute "151_softwarebehaviour" contains one or the other aforementioned software behaviours))
c. for psw behaviours, please also consider only those source requirements where "091_req_class_discipline" is set to "swe.1".
d. for bsw behaviours, no distinction is to be made based on the attribute "091_req_class_discipline", while deriving sw-requirements.
3. dai sys.3 ibc (including tsc): "sydesign".
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-001537e2.
b. filter: (((attribute '011_object state_dxl' contains 'approved') or (011_object state == 04 approved)) and ((010_object type == definition) or (010_object type == requirement)) and (016_(sub)system == software) and (attribute "dxl for 140_system feature (syrs)" or attribute "dxl for 140_system feature (tsc)" contains one or the other aforementioned system features)).
4. dai sys.3 epb (including tsc): "sydesign" (only for the ess part).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-00143fc1.
b. filter: (((attribute '011_object state_dxl' contains 'approved') or (011_object state == 04 approved)) and ((010_object type == definition) or (010_object type == requirement)) and (016_(sub)system == software)).
5. dai hwe.2 ibc: "dai_mma ibc gen2 ecu ad" (read-only module).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-0013d856.
b. filter: ((011_object state == 04 approved) and ((010_object type == definition) or (010_object type == requirement)) and (115_ecu_(sub)system == ecu related sw)).
5. core hwe.2 ibc: "ibc gen2 ecu ad" (only for connecting csc swrs to core gee and to tag core gee requirements to the right software behaviours).
a. link: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-m-000cce21.
b. filter: ((011_object state == 04 approved) and ((010_object type == definition) or (010_object type == requirement)) and (115_ecu_(sub)system == ecu related sw)).
output document(s):
all swe.1 related artefacts including the slave module baselines in the dai mma ibc application project (sw requirement specifications, sw parameter table, et. al.)!
acceptance criteria(s):
1. sw requirements are released (incl. stakeholder and formal reviews) in the application slave modules.
2. sw requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the attribute "014_requirement source comment" in the application slave modules.
3. attribute "151_softwarebehaviour" is tagged in source documents (such as sydesign and core ecu ad), when these parent requirements are linked to swrs.
4. source requirements are reviewed via proper checklists and review findings are provided.
----------------------------------------------------------------------------------------------------------------------------------------------------- -----------------------------------------------------------------------------------------------------------------------------------------------------
[06.08.2021, singhp5]
---------------------------------------------------------------------------------------------------------------------
brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
1. for the aforementioned software behaviours, individual alm_tasks were created per team to cover the swe.1 activities as part of this cr.
2. note: not all source requirements are or can be tagged to the software behaviours (attribute "151_softwarebehaviour") currently. but all the potential source modules are listed in the cr description. when during the swrs development, new source requirments in these source modules are identified, then it is agreed with the sw-development line management, that the relevant sys.1, sys.3 and hwe.2 requirements shall be linked from swrs and tagged to the corresponding software behaviours by the individual alm_task owner.
---------------------------------------------------------------------------------------------------------------------
complexity: [medium]
experience: [known topic]
carry over: [basis available]
---------------------------------------------------------------------------------------------------------------------
proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
a)
title/header: develop and release software requirements for the aforementioned software behaviours
description:
create alm_task for each affected software behaviour (or combine several software behaviours for one team) to develop and release software requirements (via reuse of requalified requirements or via project specific tailoring).
the detailed swrs work-instruction, view, and atttribute information for requalification in the mqb-48w ebc swrs is available here:
1. refer to the wiki in zoom page: https://zoom.zf-world.com/sites/com19/groups/14921/pages/wiki/swrs%20requalification.aspx.
2. additional training information for the swrs requalification is available in ptc: swe.1 basic training lite for requalification (https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brksw/teams/softwaresystemengineering/swrequirements/03_training/project.pj&selection=swe.1 basic training lite for requalification.pptx) (esp. under faq section).
acceptance criteria(s):
1. sw requirements are released (incl. stakeholder and formal reviews) in the application slave modules.
2. sw requirements are linked to project specific source requirements as out-links, or in exceptional cases when no upwards traceability can be provided, the requirements are justified via the attribute "014_requirement source comment" in the application slave modules.
3. attribute "151_softwarebehaviour" is tagged in source documents (such as sydesign and core ecu ad), when these parent requirements are linked to swrs.
review type: stakeholder review [yes], formal review [yes]
review selection reason: new requirements might be created
review department(s): swe.1, swe.2, swe.3 and swe.6
==> what to review: please check against the corresponding alm_task notes to identify and confirm the swrs module baselines to be reviewed!
==> what checklists: please check against the corresponding alm_task notes to identify, confirm and add the checklists!
estimated effort: 5h (effort only for sw-requirements team for coordination)
---------------------------------------------------------------------------------------------------------------------
b)
title/header: review source requirements for the aforementioned software behaviours
description:
create alm_task for review of all source requirements for the affected software behaviours. capture findings via source document checklist in ptc and provide findings in doors and create a spawned ptc item in case of findings.
acceptance criteria(s):
1. source requirements are reviewed via proper checklists and review findings are provided.
review type: stakeholder review [yes]
review selection reason: source requirements to software
review department(s): swe.1
==> what to review: please check against the corresponding alm_task notes to identify and confirm the source modules to be reviewed!
==> what checklists: please check against the corresponding alm_task notes to identify, confirm and add the checklists!
estimated effort: 5h
---------------------------------------------------------------------------------------------------------------------------------------------------- | |
[DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request SWE.6 Software Qualification Test for feature implementation of [DCRP 67.1 ML1][IBC][SW-Testing] GF 1.11 Brake Light Request - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
DCRP Customer-LH SW Requirements
--------------------------------------------------------------------------------
Output Work Products:
- Software Qualification Test strategy
- Specification for Software Quelification Tests
- Testcase plan - Test results
- Traceability to SW Requirements and Test Results report
--------------------------------------------------------------------------------
Acceptance Criteria:
Test passed according to SW Requirements Test Results are recorded into Report
-------------------------------------------------------------------------------- Test Execution was not fully performed for this Release due to missing SwRS and lack of availability of the HIL.
These tests will be executed for X0300.
This CR will be rejected. | [DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request SWE.6 Software Qualification Test for feature implementation of [DCRP 67.1 ML1][IBC][SW-Testing] GF 1.11 Brake Light Request - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
DCRP Customer-LH SW Requirements
--------------------------------------------------------------------------------
Output Work Products:
- Software Qualification Test strategy
- Specification for Software Quelification Tests
- Testcase plan - Test results
- Traceability to SW Requirements and Test Results report
--------------------------------------------------------------------------------
Acceptance Criteria:
Test passed according to SW Requirements Test Results are recorded into Report
-------------------------------------------------------------------------------- Test Execution was not fully performed for this Release due to missing SwRS and lack of availability of the HIL.
These tests will be executed for X0300.
This CR will be rejected. | |
[DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request SWE.3 Software Detailed Design and Unit Construction
SWE.4 Software Unit Verification
for feature implementation of [DCRP 67.1 ML1][IBC][SW-D] GF 1.11 Brake Light Request - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
SWE.3
- Sofware detailed design
- Interfaces for software units
- Software Unit
SWE.4
- Software Unit Verification strategy
- Criteria for software unit verification
- Software Unit Verification results
--------------------------------------------------------------------------------
Acceptance Criteria:
SWE.3
Software detailed design is approved and released
Interfaces for Software Units are implemented
Software Units are approved and released
SWE.4
Software Unit verification strategy is approved including acceptance criteria
Software Unit verification results report is approved and released
-------------------------------------------------------------------------------- OK | [DCRP 67.03 ML1] [IBC] GF 1.11 Brake Light Request SWE.3 Software Detailed Design and Unit Construction
SWE.4 Software Unit Verification
for feature implementation of [DCRP 67.1 ML1][IBC][SW-D] GF 1.11 Brake Light Request - B3
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B3
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
SWE.3
- Sofware detailed design
- Interfaces for software units
- Software Unit
SWE.4
- Software Unit Verification strategy
- Criteria for software unit verification
- Software Unit Verification results
--------------------------------------------------------------------------------
Acceptance Criteria:
SWE.3
Software detailed design is approved and released
Interfaces for Software Units are implemented
Software Units are approved and released
SWE.4
Software Unit verification strategy is approved including acceptance criteria
Software Unit verification results report is approved and released
-------------------------------------------------------------------------------- OK | |
[Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Wheel Spin direction is not used in the project. Hence the SIT Requirements shall be rejected. System CCB (RLU) (09.11.21 - 16:08):
--------------------------------------------------------------------------------
update SIT
--------------------------------------------------------------------------------
Rene Ludwig, (09.11.2021):
--------------------------------------------------------------------------------
Brief investigation comment:
Deletion of SIgnal Wheel Spin Direction
Impact on cost and schedule has been checked and agreed initially by APDF
Impact on operating environment has been judged as n/a because the signal is not used in S/W - only test (which will be changed)
Technically this is feasible. Asignal shall be deleted
--------------------------------------------------------------------------------
Task 1: SYS.2
- Risk (low/high): low
- Task for R. Ludwig: Deletion of Wheel Spin Direction Signals / Verifier: T.Hein (1 h)
- Task-Decription:
Delete SIT Definitions 21, 22, 23, 24
Delete SIT Requirements 93, 94, 95, 96
System CCB (RLU) (09.11.21 - 15:56):
--------------------------------------------------------------------------------
update the Requirements accordingly
-------------------------------------------------------------------------------- | [Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Wheel Spin direction is not used in the project. Hence the SIT Requirements shall be rejected. System CCB (RLU) (09.11.21 - 16:08):
--------------------------------------------------------------------------------
update SIT
--------------------------------------------------------------------------------
Rene Ludwig, (09.11.2021):
--------------------------------------------------------------------------------
Brief investigation comment:
Deletion of SIgnal Wheel Spin Direction
Impact on cost and schedule has been checked and agreed initially by APDF
Impact on operating environment has been judged as n/a because the signal is not used in S/W - only test (which will be changed)
Technically this is feasible. Asignal shall be deleted
--------------------------------------------------------------------------------
Task 1: SYS.2
- Risk (low/high): low
- Task for R. Ludwig: Deletion of Wheel Spin Direction Signals / Verifier: T.Hein (1 h)
- Task-Decription:
Delete SIT Definitions 21, 22, 23, 24
Delete SIT Requirements 93, 94, 95, 96
System CCB (RLU) (09.11.21 - 15:56):
--------------------------------------------------------------------------------
update the Requirements accordingly
-------------------------------------------------------------------------------- | |
[Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Wheel Spin direction is not used in the project.
Update the Testscripts accordingly
Also refer to CR 5874831 SIT requirment is rejected hence no Re-Test or Test adaption is needed. | [Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Wheel Spin direction is not used in the project.
Update the Testscripts accordingly
Also refer to CR 5874831 SIT requirment is rejected hence no Re-Test or Test adaption is needed. | |
[Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
For customer tickets [KPM] attach the logs to open point. PSM (R. Ludwig) (08.07.22 - 14:24):
--------------------------------------------------------------------------------
Cr not needed. Test cases will be updated with CR 5874916
-------------------------------------------------------------------------------- | [Issue]-ZF-PBC- WheelSpinDirection is Set to 250 Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
For customer tickets [KPM] attach the logs to open point. PSM (R. Ludwig) (08.07.22 - 14:24):
--------------------------------------------------------------------------------
Cr not needed. Test cases will be updated with CR 5874916
-------------------------------------------------------------------------------- | |
[Daimler][MMA][Issue]: No PDU`s which are mapped to at least one partial network should be received At least ComM_Mainfunction is called every 20 ms, but the ComM configuration tells that it should get called every 5 ms. That has to be fixed. At the same time the configuration of the other runnables shall be checked. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The cycle time of ComM_MainFunction cycle time of all channels shall be set to 20 ms. The other MainFunction cycle times are set up as expected.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
-------------------------------------------------------------------------------- | [Daimler][MMA][Issue]: No PDU`s which are mapped to at least one partial network should be received At least ComM_Mainfunction is called every 20 ms, but the ComM configuration tells that it should get called every 5 ms. That has to be fixed. At the same time the configuration of the other runnables shall be checked. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The cycle time of ComM_MainFunction cycle time of all channels shall be set to 20 ms. The other MainFunction cycle times are set up as expected.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
-------------------------------------------------------------------------------- | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3]Customer Issue]- [DTCs Issue] - 23 VF BEV Mule 1 HALF DTCs [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3]Customer Issue]- [DTCs Issue] - 23 VF BEV Mule 1 HALF DTC
Issue reprorted from Customer on SW1: See attachment for more details. Mahendar Reddy [2nd Aug 2021]:
-------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As part of this CR below changes need to be performed:
1. All the CAN1 and CAN2 Tx signals should be properly initialized as per DBC.
2. CRC and Checksum should be implemented for TX signals(The signals which have CRC and Checksum As per DBC ) .
The DBC path is given as below:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/00%5fFrom%5fCustomer/05%5fRequirements/1A%5fspec%5fBSM%5f140502021/BSM%20%2d%20Braking%20System%20Module/NW%20%2d%20Network%20Requirements/CAN%20Networks/project.pj
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale:
.
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahendar Reddy
Proposal of next steps (incl. effort/h and verification): Task need to be created. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3]Customer Issue]- [DTCs Issue] - 23 VF BEV Mule 1 HALF DTCs [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3]Customer Issue]- [DTCs Issue] - 23 VF BEV Mule 1 HALF DTC
Issue reprorted from Customer on SW1: See attachment for more details. Mahendar Reddy [2nd Aug 2021]:
-------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As part of this CR below changes need to be performed:
1. All the CAN1 and CAN2 Tx signals should be properly initialized as per DBC.
2. CRC and Checksum should be implemented for TX signals(The signals which have CRC and Checksum As per DBC ) .
The DBC path is given as below:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/00%5fFrom%5fCustomer/05%5fRequirements/1A%5fspec%5fBSM%5f140502021/BSM%20%2d%20Braking%20System%20Module/NW%20%2d%20Network%20Requirements/CAN%20Networks/project.pj
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale:
.
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahendar Reddy
Proposal of next steps (incl. effort/h and verification): Task need to be created. | |
[BSW_Test]:Issue with CARMODE Dyno [BSW_Test]:Issue with CARMODE Dyno
During VMM test 4.1.4 Test case : CarMode Dyno
Objective:
Test the functionally and quiescent current consumption in CarMode = DYNO.
When CarMode Dyno;Dyno2CarModSts1 = Dyno{0b101}, and CarModSubtypWdCarModSubtyp = Dyno2 {0b000}
And we Set UsageMode toDrivingUsgModSts = Driving{0b1101} the fault DTC (PERFORMANCE_DISABLED_BY_FOUR_WHL_DYNO_MODE )is observed in present and fault is not move to History.
As per the requiement when the usage mode in Driving system should exit from Dyno mode and faults should move to history. SWPM - Y.Meng - 09.09.21 - 08:34:
------------------------------------------------------
As attached clarification by Requirement team, this is not an issue.
CR can be rejected. | [BSW_Test]:Issue with CARMODE Dyno [BSW_Test]:Issue with CARMODE Dyno
During VMM test 4.1.4 Test case : CarMode Dyno
Objective:
Test the functionally and quiescent current consumption in CarMode = DYNO.
When CarMode Dyno;Dyno2CarModSts1 = Dyno{0b101}, and CarModSubtypWdCarModSubtyp = Dyno2 {0b000}
And we Set UsageMode toDrivingUsgModSts = Driving{0b1101} the fault DTC (PERFORMANCE_DISABLED_BY_FOUR_WHL_DYNO_MODE )is observed in present and fault is not move to History.
As per the requiement when the usage mode in Driving system should exit from Dyno mode and faults should move to history. SWPM - Y.Meng - 09.09.21 - 08:34:
------------------------------------------------------
As attached clarification by Requirement team, this is not an issue.
CR can be rejected. | |
[0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle Unterscheidung Volumen für die Bremsenbefüllung: Abhängig davon, ob isol. Vorderachse aktiv oder nicht aktiv ist.
- vgl. Erklärung und gewollte Umsetzung dokumentiert im CR 5431411
- Leider wurde bei der Umsetzung Vergessen das Trimming für RB_RBC_MAX_VOL_LAT_ACCEL_TBL_S16 und RB_DYN_REQ_BRK_PED_GRAD_TBL_S16 anzupassen (und zwar die Einträge für Wave 2)
- dies erfolgt mit diesem CR im CCB mit M. Neitsch (VW) genehmigt | [0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle Unterscheidung Volumen für die Bremsenbefüllung: Abhängig davon, ob isol. Vorderachse aktiv oder nicht aktiv ist.
- vgl. Erklärung und gewollte Umsetzung dokumentiert im CR 5431411
- Leider wurde bei der Umsetzung Vergessen das Trimming für RB_RBC_MAX_VOL_LAT_ACCEL_TBL_S16 und RB_DYN_REQ_BRK_PED_GRAD_TBL_S16 anzupassen (und zwar die Einträge für Wave 2)
- dies erfolgt mit diesem CR im CCB mit M. Neitsch (VW) genehmigt | |
[0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle Preconditions / Ausgangsituation:
SW SCS: M521
SW EBB: M621
Vehicle: SE310610074 (El Born Boost)
Maneuver name: PH_asphalt_straight_line_braking_low_decel_20_kph
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Braking to stillstand with const. pedal travel slightly below 20kph so that isolated front axle is not active
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
No over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
Over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Driver needs to react to over-braking by slightly releasing brake pedal.
--------------------------------------------------------------------------------
Analyse:
Volume parameters for stare 2 with all 4 dumps open needs to be lowered to wave 1 values. Duplicate of 5590732 | [0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle Preconditions / Ausgangsituation:
SW SCS: M521
SW EBB: M621
Vehicle: SE310610074 (El Born Boost)
Maneuver name: PH_asphalt_straight_line_braking_low_decel_20_kph
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Braking to stillstand with const. pedal travel slightly below 20kph so that isolated front axle is not active
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
No over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
Over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Driver needs to react to over-braking by slightly releasing brake pedal.
--------------------------------------------------------------------------------
Analyse:
Volume parameters for stare 2 with all 4 dumps open needs to be lowered to wave 1 values. Duplicate of 5590732 | |
[0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle ReTest Activity for ESC SW 522 --> CAT3
0522 - Test Build 5538545
Preconditions / Ausgangsituation:
SW SCS: M521
SW EBB: M621
Vehicle: SE310610074 (El Born Boost)
Maneuver name: PH_asphalt_straight_line_braking_low_decel_20_kph
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Braking to stillstand with const. pedal travel slightly below 20kph so that isolated front axle is not active
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
No over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
Over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Driver needs to react to over-braking by slightly releasing brake pedal.
--------------------------------------------------------------------------------
Analyse:
Volume parameters for stare 2 with all 4 dumps open needs to be lowered to wave 1 values. Test can be done by CASE | [0521][CAT4][CASE][VW_MEB31x_SCS] Over-braking at transition state 2,3 in case of non-isolated front axle ReTest Activity for ESC SW 522 --> CAT3
0522 - Test Build 5538545
Preconditions / Ausgangsituation:
SW SCS: M521
SW EBB: M621
Vehicle: SE310610074 (El Born Boost)
Maneuver name: PH_asphalt_straight_line_braking_low_decel_20_kph
--------------------------------------------------------------------------------
Actions / Aktionen:
1. Braking to stillstand with const. pedal travel slightly below 20kph so that isolated front axle is not active
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
No over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
Over-braking compared to driver input during the hydraulic blending at transition from pure electric to hydraulic.
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Driver needs to react to over-braking by slightly releasing brake pedal.
--------------------------------------------------------------------------------
Analyse:
Volume parameters for stare 2 with all 4 dumps open needs to be lowered to wave 1 values. Test can be done by CASE | |
[ASIL_C] SWE.6 Volvo ASIL C MSS2 GAXX - S_DL_SYS_SUPPLY_CAP_SCALE hardcoded Comment added to requirement that it value is hardcoded. Please update TC and consider the comment in your test. Approved | [ASIL_C] SWE.6 Volvo ASIL C MSS2 GAXX - S_DL_SYS_SUPPLY_CAP_SCALE hardcoded Comment added to requirement that it value is hardcoded. Please update TC and consider the comment in your test. Approved | |
VW MEB EBB PU WAVE II - PV1 - ID.Buzz; ENV; L-02& L-03 Test; 0x201295 -MPS1_NO_SIGNAL & 0x201131 - PTS1_NO_SIGNAL DTC; RFA 27875; PWA: 45456-03-831 Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . [Krishna Kumar Shanmugam(ShanmugK), 12-07-2021 14:01]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As per the Architecture input the Senthandler and Motpossensr need to be splitted into QM and ASIL component to fulfill the architecture requirement and safety.
SentHandler: QM component.
- MPS and PTS data storage buffer size 5 and then provide to SentHandlerASIL component(raw frame data from MCAL).
- Do all failure check to derive signal validity. but, not FM fault reporting.
- Provide 1 set of MPS1 and MPS2 data to MotPosnSnsr(QM component).
SentHandlerASIL: ASIL component.
- Read data and extract data from frame. do FM fault reporting.
- Provide 5 set of MPS1 and MPS2 data to to MotPosnSnsrASIL
MotPosnSnsr: QM component
- Get 1 set of MPS1 and MPS2. Motor electric angle is calculated and provided for motor controller.(Same as current implementation)
MotPosnSnsrASIL: ASIL component.
- Get 5 set of MPS1 and MPS2. Motor electric angle is calculated and provided for BHS.
- Now data is read from SentHandler(ASIL) instead of SentHandler(QM)
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split SentHandler component with respect to QM and ASIL C
Description: Refer CR.
Owner: Krishna
Reviewer: Burney
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split MotPosnSnsr component with respect to QM and ASIL C
Description: Refer CR.
Owner: Carsten
Reviewer: Pascal
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Provide new Vector cast environment for ECUAL Team
Description:
Please provide the vector cast environment for below mentioned files, Update the SW_Unit_Test.vcm file.
MotPosnSnsrAsil.c
MotPosnSnsrAsil_Cfg.c
SentHandlerAsil.c
Owner: yessika
Reviewer: Thorsten
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------ | VW MEB EBB PU WAVE II - PV1 - ID.Buzz; ENV; L-02& L-03 Test; 0x201295 -MPS1_NO_SIGNAL & 0x201131 - PTS1_NO_SIGNAL DTC; RFA 27875; PWA: 45456-03-831 Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . [Krishna Kumar Shanmugam(ShanmugK), 12-07-2021 14:01]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As per the Architecture input the Senthandler and Motpossensr need to be splitted into QM and ASIL component to fulfill the architecture requirement and safety.
SentHandler: QM component.
- MPS and PTS data storage buffer size 5 and then provide to SentHandlerASIL component(raw frame data from MCAL).
- Do all failure check to derive signal validity. but, not FM fault reporting.
- Provide 1 set of MPS1 and MPS2 data to MotPosnSnsr(QM component).
SentHandlerASIL: ASIL component.
- Read data and extract data from frame. do FM fault reporting.
- Provide 5 set of MPS1 and MPS2 data to to MotPosnSnsrASIL
MotPosnSnsr: QM component
- Get 1 set of MPS1 and MPS2. Motor electric angle is calculated and provided for motor controller.(Same as current implementation)
MotPosnSnsrASIL: ASIL component.
- Get 5 set of MPS1 and MPS2. Motor electric angle is calculated and provided for BHS.
- Now data is read from SentHandler(ASIL) instead of SentHandler(QM)
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split SentHandler component with respect to QM and ASIL C
Description: Refer CR.
Owner: Krishna
Reviewer: Burney
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split MotPosnSnsr component with respect to QM and ASIL C
Description: Refer CR.
Owner: Carsten
Reviewer: Pascal
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Provide new Vector cast environment for ECUAL Team
Description:
Please provide the vector cast environment for below mentioned files, Update the SW_Unit_Test.vcm file.
MotPosnSnsrAsil.c
MotPosnSnsrAsil_Cfg.c
SentHandlerAsil.c
Owner: yessika
Reviewer: Thorsten
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------ | |
VW MEB EBB PU WAVE II - PV1 - ID.Buzz; ENV; L-02& L-03 Test; 0x201295 -MPS1_NO_SIGNAL & 0x201131 - PTS1_NO_SIGNAL DTC; RFA 27875; PWA: 45456-03-831 Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . The tasks are completed, all the results are passed, the CR will be closed.
See Tra.NET IDs: 10432846(SWQ_SM5), 10432841(SYI_SM5), 10432841(SYI_Read_Sens)
RTCL updated, Test run 17 | VW MEB EBB PU WAVE II - PV1 - ID.Buzz; ENV; L-02& L-03 Test; 0x201295 -MPS1_NO_SIGNAL & 0x201131 - PTS1_NO_SIGNAL DTC; RFA 27875; PWA: 45456-03-831 Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . The tasks are completed, all the results are passed, the CR will be closed.
See Tra.NET IDs: 10432846(SWQ_SM5), 10432841(SYI_SM5), 10432841(SYI_Read_Sens)
RTCL updated, Test run 17 | |
[CRL]: CRL: Systemaktivierung über EVC-Coding für PRW Import attached files to /P_DAI_MMA_IBC
Related CRL: [CRL-1167692] CRL: Systemaktivierung über EVC-Coding für PRW
Related ALM_OP: 5568983 Task created.
Task completed. No further actions necessary. | [CRL]: CRL: Systemaktivierung über EVC-Coding für PRW Import attached files to /P_DAI_MMA_IBC
Related CRL: [CRL-1167692] CRL: Systemaktivierung über EVC-Coding für PRW
Related ALM_OP: 5568983 Task created.
Task completed. No further actions necessary. | |
[Daimler][MMA][Issue]: Check PNC bits and mirroring PNC bits - Failed Currently the ModeManagerPrj requests full communication on every startup, independent if there currently is a keep alive request or not. This behavior must be changed to only request communication if there is also a keep alive request. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Code: A check for the CommKeepAliveReasons shall be added before FULL_COMMUNICATION request is set.
SwRs: According to requirements team, software requirements shall be updated with 260 requirements task.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Proposed task attached. | [Daimler][MMA][Issue]: Check PNC bits and mirroring PNC bits - Failed Currently the ModeManagerPrj requests full communication on every startup, independent if there currently is a keep alive request or not. This behavior must be changed to only request communication if there is also a keep alive request. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Code: A check for the CommKeepAliveReasons shall be added before FULL_COMMUNICATION request is set.
SwRs: According to requirements team, software requirements shall be updated with 260 requirements task.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Proposed task attached. | |
[Daimler][MMA][Issue]: DUT is in sleep during NM PDU Transmission Fix NM keep alive.
Currently the ECU is kept alive by NM frames with active PNC00 (All_Active), only.
It must be evaluated, if all users of GetCommsCurrentComMode are fine with the information that the FR is active, or if they need the information that application frames are active. If FR active is enough for all, the issue can be fixed by simply returning the state of ComM_GetCurrentComMode(ESP_CHASSIS_2e4nxg4yd7af3slf2rza2ndr1_5f7d98d7, ...) Otherwise the interface must be split into two different ones, one for PNC and one for the FR/CAN itself. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
ComM returns FULL_COMMUNICATION, if all of the channels assigned to that ComMUser or its PNCs are in FULL_COMMUNICATION. If there are no external NM frames on CAN, the channel will be turned off, switching PNC_00 to state "NO_COMMUNICATION" at the same time => MM thinks it can shutdown the ECU.
If a user needs to know, if one of the channels (CAN or FR) is active it shall check the communication state of the channel's user. On any communication request from MM, the PNC_00 has to be enabled, currently. That will change in future, because a new "driving" PNC is going to be introduced.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): See Tasks.
-------------------------------------------------------------------------------- | [Daimler][MMA][Issue]: DUT is in sleep during NM PDU Transmission Fix NM keep alive.
Currently the ECU is kept alive by NM frames with active PNC00 (All_Active), only.
It must be evaluated, if all users of GetCommsCurrentComMode are fine with the information that the FR is active, or if they need the information that application frames are active. If FR active is enough for all, the issue can be fixed by simply returning the state of ComM_GetCurrentComMode(ESP_CHASSIS_2e4nxg4yd7af3slf2rza2ndr1_5f7d98d7, ...) Otherwise the interface must be split into two different ones, one for PNC and one for the FR/CAN itself. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
ComM returns FULL_COMMUNICATION, if all of the channels assigned to that ComMUser or its PNCs are in FULL_COMMUNICATION. If there are no external NM frames on CAN, the channel will be turned off, switching PNC_00 to state "NO_COMMUNICATION" at the same time => MM thinks it can shutdown the ECU.
If a user needs to know, if one of the channels (CAN or FR) is active it shall check the communication state of the channel's user. On any communication request from MM, the PNC_00 has to be enabled, currently. That will change in future, because a new "driving" PNC is going to be introduced.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): See Tasks.
-------------------------------------------------------------------------------- | |
[Issue]ZF-PBC- InCase Maintenance Mode, Fehlremeldungen Lamp is Set to 9 instead of 6 [ZalatO][30.06.2021-15:49]:
----------------------------------------
----------------------------------------
EPBi-VW_MQB-48W-SyDesign_10842
Preconditions:
Vehicle Mode:Static
IGN= ON
Engine = ON
Slope / Gradient = -1%
EPB Status:Released
Gear:D
Seatbelt:belted
ThrottlePedal = 0%
Car_DriverSeatbelt = Fastened
Car_DriverDoor = Closed
EPB_Fehlermeldungen_02 = 0
Action Performed:
Enter Maintenance Mode
Expected Result:
EPB in Maintenance Mode
EPB_Fehlermeldungen_02 = 6
Observed Result:
EPB in Maintenance Mode
EPB_Fehlermeldungen_02 = 9 The same issue is already reported and tracked by ALM_Open Point 5174856. Therefore, this CR can be rejected.
The related ALM_Open Point 5467320 has been commented accordingly. | [Issue]ZF-PBC- InCase Maintenance Mode, Fehlremeldungen Lamp is Set to 9 instead of 6 [ZalatO][30.06.2021-15:49]:
----------------------------------------
----------------------------------------
EPBi-VW_MQB-48W-SyDesign_10842
Preconditions:
Vehicle Mode:Static
IGN= ON
Engine = ON
Slope / Gradient = -1%
EPB Status:Released
Gear:D
Seatbelt:belted
ThrottlePedal = 0%
Car_DriverSeatbelt = Fastened
Car_DriverDoor = Closed
EPB_Fehlermeldungen_02 = 0
Action Performed:
Enter Maintenance Mode
Expected Result:
EPB in Maintenance Mode
EPB_Fehlermeldungen_02 = 6
Observed Result:
EPB in Maintenance Mode
EPB_Fehlermeldungen_02 = 9 The same issue is already reported and tracked by ALM_Open Point 5174856. Therefore, this CR can be rejected.
The related ALM_Open Point 5467320 has been commented accordingly. | |
FT:BYD-CD 10th_SOP_SW_RC1- S2BY02CA01_S3BY02CA01-10AB:Tune Test:4.5.9 MEFK Variant To resolve angle send out issue reported by Customer need to update tune parameter as below:
INIT_SP_TORQUE_THRESHOLD from 1 Nm to 11Nm .
For more details refer the attachment. this is a Cluster CR | FT:BYD-CD 10th_SOP_SW_RC1- S2BY02CA01_S3BY02CA01-10AB:Tune Test:4.5.9 MEFK Variant To resolve angle send out issue reported by Customer need to update tune parameter as below:
INIT_SP_TORQUE_THRESHOLD from 1 Nm to 11Nm .
For more details refer the attachment. this is a Cluster CR | |
[VW KPM] GE 0x02F2 Tasterlampe EPB bleibt aus The Function_lamp_parking_brake_button (RID 0x02F2), Function_lamp_for_autohold_button (RID 0x02F3) routine and Display text (RID 0x02F4) routine will be introduced by Diag team.
As discussed with Christian Eiserloh , the two 'Is' interfaces shall be provided by the diag team.
One interface shall indicate that the diagnostic control over routine is started and one interface shall provide the command itself (i.e. Lamp On/Lamp Off or value of text request in case of 02F4).
The relevant requirements for these routines can be found at the following link:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-671-000e90e6?doors.view=00000082
0x02F2 : Dia_Rou_MQB48W_636 up to Dia_Rou_MQB48W_654
0x02F3 : Dia_Rou_MQB48W_712 up to Dia_Rou_MQB48W_726
0x02F4 : Dia_Rou_MQB48W_693 up to Dia_Rou_MQB48W_711
0x02F2 - Turn ON or OFF the Parking brake function lamp - request provided through Boolean "Is" interface;
0x02F3 - Turn ON or OFF the Autohold function lamp - request provided through Boolean "Is" interface;
0x02F4 - Display on the dashboard one of the 15 possible texts found in HMI_C_EPB_TEXTE_TEXTMSG_STATE enum - request provided through uint8 interface. Please see the SetDisplayTextDashboard interface in MEB ESC;
Please update the Hmi code as such to accomodate the request from these routines.
Provided Interfaces
[Sergiu Fericel (Z0003215), Sep 21, 2020 3:42:09 PM CEST]
A new interface list is available:
--------------------------------------------------------------
0x02F2 EPB switch lamp
- BOOLEAN IsEpbSwitchLampActiveByDiag
- U8 GetEpbSwitchLamp
0x02F3 AutoHold switch lamp
- BOOLEAN IsAutoholdSwitchLampActiveByDiag
- U8 GetAutoholdSwitchLamp
0x02F4 EPB Text Display
- BOOLEAN IsDisplayTextDashboardActiveByDiag
- U8 GetDisplayTextDashboard Note:
0x02F2 (EPB switch lamp) is now available in DIAG and needs to be implemented in HMI
0x02F3 (AutoHold switch lamp) has been rejected by VW
0x02F4 (EPB Text Display) is already implemented
The RID 0x02F2 handling in HMI can be carried over from the MEB project (ALM_Change Request 4463359, HmiCoordinator revision 1.4.1.73). | [VW KPM] GE 0x02F2 Tasterlampe EPB bleibt aus The Function_lamp_parking_brake_button (RID 0x02F2), Function_lamp_for_autohold_button (RID 0x02F3) routine and Display text (RID 0x02F4) routine will be introduced by Diag team.
As discussed with Christian Eiserloh , the two 'Is' interfaces shall be provided by the diag team.
One interface shall indicate that the diagnostic control over routine is started and one interface shall provide the command itself (i.e. Lamp On/Lamp Off or value of text request in case of 02F4).
The relevant requirements for these routines can be found at the following link:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-671-000e90e6?doors.view=00000082
0x02F2 : Dia_Rou_MQB48W_636 up to Dia_Rou_MQB48W_654
0x02F3 : Dia_Rou_MQB48W_712 up to Dia_Rou_MQB48W_726
0x02F4 : Dia_Rou_MQB48W_693 up to Dia_Rou_MQB48W_711
0x02F2 - Turn ON or OFF the Parking brake function lamp - request provided through Boolean "Is" interface;
0x02F3 - Turn ON or OFF the Autohold function lamp - request provided through Boolean "Is" interface;
0x02F4 - Display on the dashboard one of the 15 possible texts found in HMI_C_EPB_TEXTE_TEXTMSG_STATE enum - request provided through uint8 interface. Please see the SetDisplayTextDashboard interface in MEB ESC;
Please update the Hmi code as such to accomodate the request from these routines.
Provided Interfaces
[Sergiu Fericel (Z0003215), Sep 21, 2020 3:42:09 PM CEST]
A new interface list is available:
--------------------------------------------------------------
0x02F2 EPB switch lamp
- BOOLEAN IsEpbSwitchLampActiveByDiag
- U8 GetEpbSwitchLamp
0x02F3 AutoHold switch lamp
- BOOLEAN IsAutoholdSwitchLampActiveByDiag
- U8 GetAutoholdSwitchLamp
0x02F4 EPB Text Display
- BOOLEAN IsDisplayTextDashboardActiveByDiag
- U8 GetDisplayTextDashboard Note:
0x02F2 (EPB switch lamp) is now available in DIAG and needs to be implemented in HMI
0x02F3 (AutoHold switch lamp) has been rejected by VW
0x02F4 (EPB Text Display) is already implemented
The RID 0x02F2 handling in HMI can be carried over from the MEB project (ALM_Change Request 4463359, HmiCoordinator revision 1.4.1.73). | |
[VW KPM] GE 0x02F2 Tasterlampe EPB bleibt aus Remove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2
please remove below highlighted part [Mahesh Mannuru,03.03.2022]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> This CR is related to Remove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2 because GE 0x02F2 Tasterlampe EPB sets to OFF
-> static and dynamic testing action is required.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahesh M
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1:
------------------------------------------------------
Title: [MQB ESC] [DIAG] -Update the GE 0x02F2 Tasterlampe EPB sets to OFF
->As per the CRRemove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2
->Please refer CR for more details: 6033744
Owner: Mahesh Mannuru
Reviewer: Anvesh Kyatham
Estimated design effort/h:
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 4
------------------------------------------------------
Total effort/h: 5
[Optional] Planned completion date: 11th March | [VW KPM] GE 0x02F2 Tasterlampe EPB bleibt aus Remove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2
please remove below highlighted part [Mahesh Mannuru,03.03.2022]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> This CR is related to Remove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2 because GE 0x02F2 Tasterlampe EPB sets to OFF
-> static and dynamic testing action is required.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahesh M
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1:
------------------------------------------------------
Title: [MQB ESC] [DIAG] -Update the GE 0x02F2 Tasterlampe EPB sets to OFF
->As per the CRRemove SetEpbSwitchLampActiveByDiag(FALSE); function from UpdateFunctionLampParkingBrake () In Rotine 0x02F2
->Please refer CR for more details: 6033744
Owner: Mahesh Mannuru
Reviewer: Anvesh Kyatham
Estimated design effort/h:
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 4
------------------------------------------------------
Total effort/h: 5
[Optional] Planned completion date: 11th March | |
[Daimler_MMA_IBC] Comparison of fingerprints Mandantory Bootloader Update Step 2.1 for X0300
Files downloaded and archived.
PTC Integrity Path: ..\BrkSw\SwDevelopmentPool\Software\Supplier\Vector\Daimler\MB_BASE_LAYER\2021_10_27 Starter_Kit_Classic_Aurix Step 2.1\ Task1 Bootloader Update Step 2.1
Title:
] Bootloader Update Step 2.1
Description:
Integrate the new SIP Changes
Proposed Tests:
è Application Running
è vFlash application
Estimated design effort/h:
Estimated implementation effort/h: 6
Estimated unit testing effort/h: 2
Total effort/h: 8
[Optional] Planned completion date: 24/01/22
CR1
Remove Patches in Gendata After Davinci generation
Bootloader Update Step 2.1
Title:
Remove Patches in Gendata After Davinci generation
Description:
è In Crypto_30_LibCv_Cfg.c , Csm_Cfg.c
CRYPTO_ALGOFAM_CUSTOM_CRYPTO_30_LIBCV_PADDING_PKCS7 is changed to CRYPTO_ALGOFAM_NOT_SET
è In FblHal_Cfg.H
#define FBL_TIMER_RELOAD_VALUE 99999 /* bhanu Manuval change */ changed from 19999
èIn FblMio_Cfg.c
void MemDriver_MemInit(void)
{
/* ZF_Patch added banhu */
vMemAccM_InitMemory();
vMemAccM_Init();
/* ZF_Patch added banhu End */
}
èIn Fr_Cfg.h
//#define FR_VCC_REG_START_ADDR 0x00000000uL
/*ZF_Patch Bhanu added */
#define FR_VCC_REG_START_ADDR 0xF001C000uL
/*ZF_Patch Bhanu added End */
èPduR_Dcm.h, Pdur_Lcfg.c
#define PDUR_STOP_SEC_CODE
#include "MemMap.h" /* PRQA S 5087 */ /* MD_MSR_MemMap */
èvBrs_Lcfg.h
//#include "BrsMain_Types.h"
CR2
Remove Patches in BSW Source files
Bootloader Update Step 2.1
Title:
Remove Patches in BSW Source files
Description:
Memmap changes:
ComM.c, fblcw.c, PduR.c, Pdur_Lock.c, PduR_RmTp.c
In Crypto_30_LibCv_Cipher.c
In Crypto_30_LibCv_Custom.h
//# include "Crypto_30_LibCv_Custom_Generated.h"
In Crypto_30_vHsm_Custom.h
//# include "Crypto_30_vHsm_Custom_Generated.h"
Eep changes takenover from old changes
In fbl_diag_oem.c
Range check removed
Changed the version
In fbl_diag_oem.c
Taken over:
èadded the fbl_spi_infineon_qspi
In _FrTrcv_30_Tja1080_Phy.c
Dio changes tekenover | [Daimler_MMA_IBC] Comparison of fingerprints Mandantory Bootloader Update Step 2.1 for X0300
Files downloaded and archived.
PTC Integrity Path: ..\BrkSw\SwDevelopmentPool\Software\Supplier\Vector\Daimler\MB_BASE_LAYER\2021_10_27 Starter_Kit_Classic_Aurix Step 2.1\ Task1 Bootloader Update Step 2.1
Title:
] Bootloader Update Step 2.1
Description:
Integrate the new SIP Changes
Proposed Tests:
è Application Running
è vFlash application
Estimated design effort/h:
Estimated implementation effort/h: 6
Estimated unit testing effort/h: 2
Total effort/h: 8
[Optional] Planned completion date: 24/01/22
CR1
Remove Patches in Gendata After Davinci generation
Bootloader Update Step 2.1
Title:
Remove Patches in Gendata After Davinci generation
Description:
è In Crypto_30_LibCv_Cfg.c , Csm_Cfg.c
CRYPTO_ALGOFAM_CUSTOM_CRYPTO_30_LIBCV_PADDING_PKCS7 is changed to CRYPTO_ALGOFAM_NOT_SET
è In FblHal_Cfg.H
#define FBL_TIMER_RELOAD_VALUE 99999 /* bhanu Manuval change */ changed from 19999
èIn FblMio_Cfg.c
void MemDriver_MemInit(void)
{
/* ZF_Patch added banhu */
vMemAccM_InitMemory();
vMemAccM_Init();
/* ZF_Patch added banhu End */
}
èIn Fr_Cfg.h
//#define FR_VCC_REG_START_ADDR 0x00000000uL
/*ZF_Patch Bhanu added */
#define FR_VCC_REG_START_ADDR 0xF001C000uL
/*ZF_Patch Bhanu added End */
èPduR_Dcm.h, Pdur_Lcfg.c
#define PDUR_STOP_SEC_CODE
#include "MemMap.h" /* PRQA S 5087 */ /* MD_MSR_MemMap */
èvBrs_Lcfg.h
//#include "BrsMain_Types.h"
CR2
Remove Patches in BSW Source files
Bootloader Update Step 2.1
Title:
Remove Patches in BSW Source files
Description:
Memmap changes:
ComM.c, fblcw.c, PduR.c, Pdur_Lock.c, PduR_RmTp.c
In Crypto_30_LibCv_Cipher.c
In Crypto_30_LibCv_Custom.h
//# include "Crypto_30_LibCv_Custom_Generated.h"
In Crypto_30_vHsm_Custom.h
//# include "Crypto_30_vHsm_Custom_Generated.h"
Eep changes takenover from old changes
In fbl_diag_oem.c
Range check removed
Changed the version
In fbl_diag_oem.c
Taken over:
èadded the fbl_spi_infineon_qspi
In _FrTrcv_30_Tja1080_Phy.c
Dio changes tekenover | |
[Issue] ZF-PBC-FaultLamp is expected as (0A) but it shows (05) incase of Hardwired Faulty Apply and SwitchStuck With this CR the System Information topic (e.g. text messages, status lamp, yellow warning lamp, park brake switch lamp)
For further detailes please refer to OP ALM_Open Point 2982004. Implement as requested. | [Issue] ZF-PBC-FaultLamp is expected as (0A) but it shows (05) incase of Hardwired Faulty Apply and SwitchStuck With this CR the System Information topic (e.g. text messages, status lamp, yellow warning lamp, park brake switch lamp)
For further detailes please refer to OP ALM_Open Point 2982004. Implement as requested. | |
[Issue][SWE.4][LCM]lcm_ebf - #Lcm_Ebf_Active_State_Timer is not reset when state LCM_EBF_EBB_STATE_3_ACTIVE is left Description:
#Lcm_Ebf_Active_State_Timer has not been reset to ZERO, by re-entering state LCM_EBF_EBB_STATE_3_ACTIVE, the timer count continually instead of starting from 0. See attachment
Note:
This issue has found in SW version lcm_ebf 1.2.1.3.1.8.1.10.1.1 reset timer when leaving active state to available | [Issue][SWE.4][LCM]lcm_ebf - #Lcm_Ebf_Active_State_Timer is not reset when state LCM_EBF_EBB_STATE_3_ACTIVE is left Description:
#Lcm_Ebf_Active_State_Timer has not been reset to ZERO, by re-entering state LCM_EBF_EBB_STATE_3_ACTIVE, the timer count continually instead of starting from 0. See attachment
Note:
This issue has found in SW version lcm_ebf 1.2.1.3.1.8.1.10.1.1 reset timer when leaving active state to available | |
[Issue]ZF-PBC- Drive Info Message-EPB_Texte_02- is always set to 0 PSM (RLu) (05.05.2021 - 16:02):
--------------------------------------------------------------------
S/W to analyze why Textmessage is not triggered.
-------------------------------------------------------------------
Vehicle:
MQB48w GV1 Vehicle MQB48 4-0001
Preconditions:
Vehicle Mode:Static
IGN:ON
Engine:OFF
Slope / Gradient:30
EPB Status:released
Gear:N
Seatbelt:belted
Auto Hold:OFF
Activity:
1. Set temperature >300 º C
2. Switch key to IGN_OFF
3. Apply with the EPB-Switch
4. Check clamp force with diagnostics
5. Wait 180 Seconds
6. Check clamp force with diagnostics
7. Switch key to IGN_ON
8. START Engine
9. PERFORM DAA
Expected Behavior:
If the vehicle state lays outside the defined operation range for the parking brake (brake temperature, gradient, etc.), the text message "EPB_Texte_02 :: 0x01" shall be displayed.
Actual Behavior:
"EPB_Texte_02 :: 0x01" is not displayed.
Test ID:
TMO-002
Test Description:
Reclamp >300 º C 30% in IGN off
Logfile:
TMO-002_VW_MQB48_4-0001_EPB_SCS_X307-009__eBB_X307-009_14.04.2021_0053.MDF
Further Information:
PBCout.OutofSpecMessage is not set to 27 by PBC.
Function is not according EPBi-VW_MQB-48W-SyRS-3516 <Pruthvi M> (15.07.21 - 18:00):
--------------------------------------------------------------------------------
Brief investigation comment:
Compiler switch for OUT_OF_SPEC_MESSAGE is disabled for this project. That is why "EPB_Texte_02 :: 0x01" is not displayed.
Compilerswitch for OUT_OF_SPEC_MESSAGE is enabled by Task_5458909 and the above scenario is tested along with that task and results are as expected.
Proposal of next steps:
@Florian Zimmer: No task required. Please tag this CR to Task_5458909.
Function & Control CCB - FZI - 05.07.21 - 15:28:
Please investigate this point and advise the next steps. | [Issue]ZF-PBC- Drive Info Message-EPB_Texte_02- is always set to 0 PSM (RLu) (05.05.2021 - 16:02):
--------------------------------------------------------------------
S/W to analyze why Textmessage is not triggered.
-------------------------------------------------------------------
Vehicle:
MQB48w GV1 Vehicle MQB48 4-0001
Preconditions:
Vehicle Mode:Static
IGN:ON
Engine:OFF
Slope / Gradient:30
EPB Status:released
Gear:N
Seatbelt:belted
Auto Hold:OFF
Activity:
1. Set temperature >300 º C
2. Switch key to IGN_OFF
3. Apply with the EPB-Switch
4. Check clamp force with diagnostics
5. Wait 180 Seconds
6. Check clamp force with diagnostics
7. Switch key to IGN_ON
8. START Engine
9. PERFORM DAA
Expected Behavior:
If the vehicle state lays outside the defined operation range for the parking brake (brake temperature, gradient, etc.), the text message "EPB_Texte_02 :: 0x01" shall be displayed.
Actual Behavior:
"EPB_Texte_02 :: 0x01" is not displayed.
Test ID:
TMO-002
Test Description:
Reclamp >300 º C 30% in IGN off
Logfile:
TMO-002_VW_MQB48_4-0001_EPB_SCS_X307-009__eBB_X307-009_14.04.2021_0053.MDF
Further Information:
PBCout.OutofSpecMessage is not set to 27 by PBC.
Function is not according EPBi-VW_MQB-48W-SyRS-3516 <Pruthvi M> (15.07.21 - 18:00):
--------------------------------------------------------------------------------
Brief investigation comment:
Compiler switch for OUT_OF_SPEC_MESSAGE is disabled for this project. That is why "EPB_Texte_02 :: 0x01" is not displayed.
Compilerswitch for OUT_OF_SPEC_MESSAGE is enabled by Task_5458909 and the above scenario is tested along with that task and results are as expected.
Proposal of next steps:
@Florian Zimmer: No task required. Please tag this CR to Task_5458909.
Function & Control CCB - FZI - 05.07.21 - 15:28:
Please investigate this point and advise the next steps. | |
TTR - Master Faults related to ADAS_FD_HMI, ADAS_FD_INFO and BRAKE2_FD_2 are not moving to History state when Fault Condition is removed @Om and Mayuka, Could you clarify what does style="font-size:11.0pt;">Master Faults to be set as Condition Latched mean? What is the "Condition" here to move to History? Is it when fault condition is removed? OR Is it when Redundant faults are Passed?
2021-03-05: KrishnaO
Is this for L2+ N/w if yes then it would be treated as COMMS power cycle fault and latched as long as COMMS is actively communicating , once COMMS communication is turned off this fault shall be cleared and it would move to history.
Mayuka: Please update fail safe manual to reflect this. Filter on FAULTS with COMMS FAULT = TRUE and COMMS_FAULT_TYPE = NON_COMMS_FAULTS
Add a new point under "Enable conditions"
L2+ N/w: Will be treated as COMMS power cycle fault and latched as long as COMMS is actively communicating, once COMMS communication is turned off this fault shall be cleared and it would move to history. | TTR - Master Faults related to ADAS_FD_HMI, ADAS_FD_INFO and BRAKE2_FD_2 are not moving to History state when Fault Condition is removed @Om and Mayuka, Could you clarify what does style="font-size:11.0pt;">Master Faults to be set as Condition Latched mean? What is the "Condition" here to move to History? Is it when fault condition is removed? OR Is it when Redundant faults are Passed?
2021-03-05: KrishnaO
Is this for L2+ N/w if yes then it would be treated as COMMS power cycle fault and latched as long as COMMS is actively communicating , once COMMS communication is turned off this fault shall be cleared and it would move to history.
Mayuka: Please update fail safe manual to reflect this. Filter on FAULTS with COMMS FAULT = TRUE and COMMS_FAULT_TYPE = NON_COMMS_FAULTS
Add a new point under "Enable conditions"
L2+ N/w: Will be treated as COMMS power cycle fault and latched as long as COMMS is actively communicating, once COMMS communication is turned off this fault shall be cleared and it would move to history. | |
[FCA_WS][Integration][FB02] E_PENDING #Define This CR is used to Plan/Monitor the SWE 3 thru 4 work for the bug fixes for "CGD" feature *
2021-06-21 PuckettM
*
Ready to begin FC00 updates for bug fixes. | [FCA_WS][Integration][FB02] E_PENDING #Define This CR is used to Plan/Monitor the SWE 3 thru 4 work for the bug fixes for "CGD" feature *
2021-06-21 PuckettM
*
Ready to begin FC00 updates for bug fixes. | |
[Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/9/22 15:56:00
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: Disable ADC fail counter check for ADC channel 27
--------------------------------------------------------------------------------
Details (Exact description):
Due to the low priority the ADC channel 27 is possible to have refresh failure and once the fail counter incremented to 4 there would be unexpected SYS_ASIC_AD_REFRESH_FAILURE lached.
Since the ADC Channel 27 is not being used anywhere in current SW, to enhance the robustness of the system propose to disable the fail counter check for ADC channel 27.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Refer to attached mail as well.
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
Disable Channel 27 Asic Adc Supported
1.need to upgrade PolarisIo Component to 1.59(Old CP 1.56)
upgrade no side affect
2. Disable Channel 27 Asic Adc Supported(The changeset is attached.)
After discussions with Core teams, upgrade the mainline of PolarisIo Component,Disable this channel no side effect
Refer to email in attachment.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):creat Task for ThirdParty and ECUAL
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title:[ECUAL][PolarisIo]:Disable Channel 27 Asic Adc Supported.
Description: refer to CR
Owner: Qin Wei
Reviewer:Sreedhar
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
------------------------------------------------------
Total effort/h:8
[Optional] Planned completion date:
------------------------------------------------------ | [Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/9/22 15:56:00
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: Disable ADC fail counter check for ADC channel 27
--------------------------------------------------------------------------------
Details (Exact description):
Due to the low priority the ADC channel 27 is possible to have refresh failure and once the fail counter incremented to 4 there would be unexpected SYS_ASIC_AD_REFRESH_FAILURE lached.
Since the ADC Channel 27 is not being used anywhere in current SW, to enhance the robustness of the system propose to disable the fail counter check for ADC channel 27.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Refer to attached mail as well.
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
Disable Channel 27 Asic Adc Supported
1.need to upgrade PolarisIo Component to 1.59(Old CP 1.56)
upgrade no side affect
2. Disable Channel 27 Asic Adc Supported(The changeset is attached.)
After discussions with Core teams, upgrade the mainline of PolarisIo Component,Disable this channel no side effect
Refer to email in attachment.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):creat Task for ThirdParty and ECUAL
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title:[ECUAL][PolarisIo]:Disable Channel 27 Asic Adc Supported.
Description: refer to CR
Owner: Qin Wei
Reviewer:Sreedhar
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
------------------------------------------------------
Total effort/h:8
[Optional] Planned completion date:
------------------------------------------------------ | |
[Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/9/22 15:56:00
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: Save ADC channel debug information to NVRAM
--------------------------------------------------------------------------------
Details (Exact description):
For further anlaysis the ADC Channel data refresh relevant debug information shall be saved to NVRAM.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
1.Save Debug info for Lotus project, See attachment email for details.
reference file:
[persistency component]
Change NVRAM_UNUSED10_BLK_ID to NVRAM_POLARISIO_FAULT_DEBUG_BLK_ID for Store info.
[SystemAsicMain component]
SystemAsicMain_Cfg_Sub.h
[PolarisIo component]
PolarisIoFailsafes.c & PolarisIo.c
The changeset is attached. See attachment email for details
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK1
------------------------------------------------------
Title:[MCAL&OS] --- Change NVRAM_UNUSED10_BLK_ID to NVRAM_POLARISIO_FAULT_DEBUG_BLK_ID for Store info.
Description:Core1 and bloack len is 42Byte, can stroe 40byte data and two byte CRC.
Owner: Gao shaobo
Reviewer:
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
TASK2
------------------------------------------------------
Title:[ECUAL][SystemAsicMain][PolarisIo] --- Save AD refresh fault information to NVRAM .
Description:
Owner: Qin wei
Reviewer: krishnakumar
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:24
[Optional] Planned completion date:
------------------------------------------------------ | [Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/9/22 15:56:00
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: Save ADC channel debug information to NVRAM
--------------------------------------------------------------------------------
Details (Exact description):
For further anlaysis the ADC Channel data refresh relevant debug information shall be saved to NVRAM.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
1.Save Debug info for Lotus project, See attachment email for details.
reference file:
[persistency component]
Change NVRAM_UNUSED10_BLK_ID to NVRAM_POLARISIO_FAULT_DEBUG_BLK_ID for Store info.
[SystemAsicMain component]
SystemAsicMain_Cfg_Sub.h
[PolarisIo component]
PolarisIoFailsafes.c & PolarisIo.c
The changeset is attached. See attachment email for details
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK1
------------------------------------------------------
Title:[MCAL&OS] --- Change NVRAM_UNUSED10_BLK_ID to NVRAM_POLARISIO_FAULT_DEBUG_BLK_ID for Store info.
Description:Core1 and bloack len is 42Byte, can stroe 40byte data and two byte CRC.
Owner: Gao shaobo
Reviewer:
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
TASK2
------------------------------------------------------
Title:[ECUAL][SystemAsicMain][PolarisIo] --- Save AD refresh fault information to NVRAM .
Description:
Owner: Qin wei
Reviewer: krishnakumar
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:24
[Optional] Planned completion date:
------------------------------------------------------ | |
[Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/10/22 14:42:54
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: New fault for SYS_ASIC_ADC_READ_BIT_STUCK, increase fault qualificaiton for SYS_ASIC_AD_REFRESH_FAILURE
--------------------------------------------------------------------------------
Details (Exact description):
1. Creating a new fault code for startup failure SYS_ASIC_ADC_READ_BIT_STUCK.
2. Increase the fault qualification time to 190ms as per requirement for SYS_ASIC_AD_REFRESH_FAILURE.Update in mainline , make project generic.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Refer to attached mail
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
1.SYS_ASIC_ADC_READ_BIT_STUCK can define in SISO directly,Since current ECUAL code uses ifndef SYS_ASIC_ADC_READ_BIT_STUCK, will define this fault. SYS_ASIC_ADC_READ_BIT_STUCK fault has the same properties as SYS_ASIC_AD_REFRESH_FAILURE
2.Increase the fault qualification time to 190ms as per requirement for SYS_ASIC_AD_REFRESH_FAILURE.Update in mainline , make project generic.
#define SYS_ASIC_AD_REFRESH_CHANNEL_GOAL 4U -> #define SYS_ASIC_AD_REFRESH_CHANNEL_GOAL 38U
The changeset as above.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):Creat CR for SISO team, creat task.
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:[ECUAL] --- Increase the fault qualification time to 190ms.
Description: refer to CR.
Owner: Qin Wei
Reviewer:Xu Fan
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:24
[Optional] Planned completion date:
------------------------------------------------------ | [Lotus_IBC_SE5.3_Cal] SYS_ASIC_AD_REFRESH_FAILURE fault found on customer vehicle and could not clear by ign on/off <Yixiao Yao>: 2022/10/22 14:42:54
--------------------------------------------------------------------------------
Aim (Objective and Rationale):
[ECUAL]: New fault for SYS_ASIC_ADC_READ_BIT_STUCK, increase fault qualificaiton for SYS_ASIC_AD_REFRESH_FAILURE
--------------------------------------------------------------------------------
Details (Exact description):
1. Creating a new fault code for startup failure SYS_ASIC_ADC_READ_BIT_STUCK.
2. Increase the fault qualification time to 190ms as per requirement for SYS_ASIC_AD_REFRESH_FAILURE.Update in mainline , make project generic.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
Refer to attached mail
--------------------------------------------------------------------------------
Output Work Products:
--------------------------------------------------------------------------------
Acceptance Criteria:
-------------------------------------------------------------------------------- --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
1.SYS_ASIC_ADC_READ_BIT_STUCK can define in SISO directly,Since current ECUAL code uses ifndef SYS_ASIC_ADC_READ_BIT_STUCK, will define this fault. SYS_ASIC_ADC_READ_BIT_STUCK fault has the same properties as SYS_ASIC_AD_REFRESH_FAILURE
2.Increase the fault qualification time to 190ms as per requirement for SYS_ASIC_AD_REFRESH_FAILURE.Update in mainline , make project generic.
#define SYS_ASIC_AD_REFRESH_CHANNEL_GOAL 4U -> #define SYS_ASIC_AD_REFRESH_CHANNEL_GOAL 38U
The changeset as above.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):Creat CR for SISO team, creat task.
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title:[ECUAL] --- Increase the fault qualification time to 190ms.
Description: refer to CR.
Owner: Qin Wei
Reviewer:Xu Fan
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:24
[Optional] Planned completion date:
------------------------------------------------------ | |
BSW_APPL: New CAN Transceiver for CAN-FD14 Make necessary changes for replacing the CAN chips as shown below (attachment has hi level comparison & specs at the bottom of each column)
Old- TJA1145T/FD (CAN1, CAN2), New- NXP TJA1057GT/3(CAN1), NXP TJA1043 (CAN2) Synopsis of changes
CAN FD 14 bus transceiver is changed from SPI based(TJA 1145) to PIN based(TJA 1057) , hence in the CommsManager_Cfg , CommsTRansceiver and CommsTransceiver_Cfg component make appropriate modifications to accomodate the new transceiver. refer attached Sw for the same. Also modified the code to resolve brkpdl issue per OP | BSW_APPL: New CAN Transceiver for CAN-FD14 Make necessary changes for replacing the CAN chips as shown below (attachment has hi level comparison & specs at the bottom of each column)
Old- TJA1145T/FD (CAN1, CAN2), New- NXP TJA1057GT/3(CAN1), NXP TJA1043 (CAN2) Synopsis of changes
CAN FD 14 bus transceiver is changed from SPI based(TJA 1145) to PIN based(TJA 1057) , hence in the CommsManager_Cfg , CommsTRansceiver and CommsTransceiver_Cfg component make appropriate modifications to accomodate the new transceiver. refer attached Sw for the same. Also modified the code to resolve brkpdl issue per OP | |
BSW_APPL: New CAN Transceiver for CAN-FD14 Make necessary changes for replacing the CAN chips as shown below (attachment has hi level comparison & specs at the bottom of each column)
Old- TJA1145T/FD (CAN1, CAN2), New- NXP TJA1057GT/3(CAN1), NXP TJA1043 (CAN2) Make necessary Port, DIO and SPi config changes based on the modified schematics. | BSW_APPL: New CAN Transceiver for CAN-FD14 Make necessary changes for replacing the CAN chips as shown below (attachment has hi level comparison & specs at the bottom of each column)
Old- TJA1145T/FD (CAN1, CAN2), New- NXP TJA1057GT/3(CAN1), NXP TJA1043 (CAN2) Make necessary Port, DIO and SPi config changes based on the modified schematics. | |
Issue in Diag ROE on transmitting on bus , when the faults are active then not transmiting on Bus. Please create the SWE.3/4 tasks per the IA 5398766 2021-06-28 GanesaS1:
Impacted Software Component
CGD - Diagservice
VILC
AUTOSAR - BSWm
2021-08-18 GanesaS1:
All planned tasks has been completed.
checkpoint details are updated in SCIS sheet. | Issue in Diag ROE on transmitting on bus , when the faults are active then not transmiting on Bus. Please create the SWE.3/4 tasks per the IA 5398766 2021-06-28 GanesaS1:
Impacted Software Component
CGD - Diagservice
VILC
AUTOSAR - BSWm
2021-08-18 GanesaS1:
All planned tasks has been completed.
checkpoint details are updated in SCIS sheet. | |
[Issue] of PBC_X01_100_01p - SiL Test - Issue of Control Actuation for Driver state is None Precondition: Set ActuatorStateLeft/Right=ePbcActuatorStateParkApplied,MotorDriverStateLeft/Right=ePbcMotorDriverStateNone
Action: Set PbcIn.ApplyReleaseRequest = ePbcApplyReleaseRequestRelease
Expected Behavior: PbcOut.ActuatorStateLeft/Right=ePbcActuatorStateReleased
Actual Behaviour: PbcOut.ActuatorStateLeft/Right=ePbcActuatorStateReleasing after 30Mins also
Please see attachment [Marek Gornisiewicz 09:54 27.09.2021]:
CCB ADTY4.1 MGO:
Testcase is already adapted with Task 5659810
Cr can be rejected
<Divya Teja Kottakonda> (09.07.21 - 20:19):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the test scenario due to low motor currents a tooth belt check is triggered.
where an apply is requested but the motor driver state does not match with the motor commands as it is continuously kept in release,
Due to this mismatch the conditions for the brake to change from releasing to released fails.
As its not realistic to keep the motor driver state in release continuously,(Observed in the testcase)
So the test case needs to be adapted so that the motor driver state syncs with the motor commands.
--------------------------------------------------------------------------------
Proposal of next steps: The test case should be adapted and tested
Function & Control CCB - FZI - 02.07.21 - 11:08:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_100_01p - SiL Test - Issue of Control Actuation for Driver state is None Precondition: Set ActuatorStateLeft/Right=ePbcActuatorStateParkApplied,MotorDriverStateLeft/Right=ePbcMotorDriverStateNone
Action: Set PbcIn.ApplyReleaseRequest = ePbcApplyReleaseRequestRelease
Expected Behavior: PbcOut.ActuatorStateLeft/Right=ePbcActuatorStateReleased
Actual Behaviour: PbcOut.ActuatorStateLeft/Right=ePbcActuatorStateReleasing after 30Mins also
Please see attachment [Marek Gornisiewicz 09:54 27.09.2021]:
CCB ADTY4.1 MGO:
Testcase is already adapted with Task 5659810
Cr can be rejected
<Divya Teja Kottakonda> (09.07.21 - 20:19):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the test scenario due to low motor currents a tooth belt check is triggered.
where an apply is requested but the motor driver state does not match with the motor commands as it is continuously kept in release,
Due to this mismatch the conditions for the brake to change from releasing to released fails.
As its not realistic to keep the motor driver state in release continuously,(Observed in the testcase)
So the test case needs to be adapted so that the motor driver state syncs with the motor commands.
--------------------------------------------------------------------------------
Proposal of next steps: The test case should be adapted and tested
Function & Control CCB - FZI - 02.07.21 - 11:08:
Please investigate this point and advise the next steps. | |
[Comms]E4 Comms interface implementation --------------------------------------------------------------------------------
Aim (Objective and Rationale):
E4 comms interface implemented
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
See attached.
--------------------------------------------------------------------------------
Output Work Products:
SW update
--------------------------------------------------------------------------------
Acceptance Criteria:
Review pass Brief Analysis:
Need to implemente signals as per attachment along with the mentioned interfaces by PSW team.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
See attached.
--------------------------------------------------------------------------------
Output Work Products:
SW update
--------------------------------------------------------------------------------
Acceptance Criteria:
Review pass
Tasks required: 1qty
Analysis done by: Aradhyula Vasundhara | [Comms]E4 Comms interface implementation --------------------------------------------------------------------------------
Aim (Objective and Rationale):
E4 comms interface implemented
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
See attached.
--------------------------------------------------------------------------------
Output Work Products:
SW update
--------------------------------------------------------------------------------
Acceptance Criteria:
Review pass Brief Analysis:
Need to implemente signals as per attachment along with the mentioned interfaces by PSW team.
--------------------------------------------------------------------------------
Input Work Products (Link or other reference):
See attached.
--------------------------------------------------------------------------------
Output Work Products:
SW update
--------------------------------------------------------------------------------
Acceptance Criteria:
Review pass
Tasks required: 1qty
Analysis done by: Aradhyula Vasundhara | |
SAIC AS32 | SWE.6 | SIL Test | PPAI |GenC_SW_PPAI_4875| can't satisfy S_ARB_PA_STATE is not ARB_ACTIVE and S_PAMST is APA_ACTIVE at same time Activity Description:
This working package include the SW test execution activities on new or changed requirement test per this SW project release phase on Interface, Interaction, Qualification and SW Fault insertion tests, it is organized as below grouped activities:
II Perform SW Test preparation and Execution
1. Prepare test specification for each planned test
2. Prepare test case for each planned tests
3. Setup traceability test cases and SW Requirement / Architecture
4. Setup Test environment
5. Execute tests per Test Order
6. Test reporting
7. Test closing with evaluated test coverage
Input of this WP are:
1. Imapct Analysis
2. SW Requirement
3. SW Architecure
4. SW Design
5. SW Components and Integrated SW
6. System Requirement & Architecture (including ECU HW)
7. Customer Requirement
Output of this WP are:
1. Test Content Plan
2. Test Schedule
3. Test Summary with Test Deviations (PTCI IM Open Points)
4. Test Specification
5. Test Case
6. Test Order (PTCI IM CR and Task)
7. Test Environment
8. Test Report
The new and changed requirements including: MSS(VS),MS,ARB(TSC),PSP(OTM),TSC Go to analysed | SAIC AS32 | SWE.6 | SIL Test | PPAI |GenC_SW_PPAI_4875| can't satisfy S_ARB_PA_STATE is not ARB_ACTIVE and S_PAMST is APA_ACTIVE at same time Activity Description:
This working package include the SW test execution activities on new or changed requirement test per this SW project release phase on Interface, Interaction, Qualification and SW Fault insertion tests, it is organized as below grouped activities:
II Perform SW Test preparation and Execution
1. Prepare test specification for each planned test
2. Prepare test case for each planned tests
3. Setup traceability test cases and SW Requirement / Architecture
4. Setup Test environment
5. Execute tests per Test Order
6. Test reporting
7. Test closing with evaluated test coverage
Input of this WP are:
1. Imapct Analysis
2. SW Requirement
3. SW Architecure
4. SW Design
5. SW Components and Integrated SW
6. System Requirement & Architecture (including ECU HW)
7. Customer Requirement
Output of this WP are:
1. Test Content Plan
2. Test Schedule
3. Test Summary with Test Deviations (PTCI IM Open Points)
4. Test Specification
5. Test Case
6. Test Order (PTCI IM CR and Task)
7. Test Environment
8. Test Report
The new and changed requirements including: MSS(VS),MS,ARB(TSC),PSP(OTM),TSC Go to analysed | |
Renault XDD - AC00-PDCS-P2*server_max value issue. This item shall implement SWE.3/4 for Provide Diagnostic Services feature for the BA00 SW.
The scope is summarized in the IA Document [ Suman Bathini (Z650149)- 18.05.2021 ]
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> New DIDs and DTCs need to be introduced as per the Impact Analysis document..
For that,
-> Update the CDD and Davinci configuration according to requirements,
-> Implement the General DIDs and DTCs planned for BA release as per the requirements.
-> Implement the Feature related DIDs and DTCs planned for BA release as per the requirements .
-> Please see the attached file for DIDs and DTC information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Suman Bathini
Proposal of next steps (incl. effort/h and verification): Please create bellow task(s).
--------------------------------------------------------------------------------
TASK 1: DAIG Autosar Stack Configuration
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3][Sprint 1][Autosar]- Update the DCM, DEM and DIAG SwC configuration for BA release.
Description:
Update CDD file and Davinci configuration according to requirements.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: 45
Estimated implementation effort/h: NA
Estimated unit testing effort/h: NA
------------------------------------------------------
Total effort/h: 45
[Optional] Planned completion date: -
------------------------------------------------------
TASK 2: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 1][Rhapsody]- Implement PDCS - General DIDs and DTCs planned for BA00 release.
Description:
Implement General DIDs planned for BA release as per the requirements.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: 50
Estimated implementation effort/h: 20
Estimated unit testing effort/h: 20
------------------------------------------------------
Total effort/h: 90
[Optional] Planned completion date: -
------------------------------------------------------
TASK 3: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 1][Rhapsody]- Implement Feature related DIDs and DTCs planned for BA00 release.
DecoBATT
SystemState
LSS Torque
LDW
Description:
Implement Feature related DIDs and DTCs planned for BA00 release.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Tejaswini V
Reviewer: Suman B
Estimated design effort/h: -
Estimated implementation effort/h: -
Estimated unit testing effort/h: -
------------------------------------------------------
Total effort/h: -
[Optional] Planned completion date: -
------------------------------------------------------ | Renault XDD - AC00-PDCS-P2*server_max value issue. This item shall implement SWE.3/4 for Provide Diagnostic Services feature for the BA00 SW.
The scope is summarized in the IA Document [ Suman Bathini (Z650149)- 18.05.2021 ]
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> New DIDs and DTCs need to be introduced as per the Impact Analysis document..
For that,
-> Update the CDD and Davinci configuration according to requirements,
-> Implement the General DIDs and DTCs planned for BA release as per the requirements.
-> Implement the Feature related DIDs and DTCs planned for BA release as per the requirements .
-> Please see the attached file for DIDs and DTC information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Suman Bathini
Proposal of next steps (incl. effort/h and verification): Please create bellow task(s).
--------------------------------------------------------------------------------
TASK 1: DAIG Autosar Stack Configuration
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3][Sprint 1][Autosar]- Update the DCM, DEM and DIAG SwC configuration for BA release.
Description:
Update CDD file and Davinci configuration according to requirements.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: 45
Estimated implementation effort/h: NA
Estimated unit testing effort/h: NA
------------------------------------------------------
Total effort/h: 45
[Optional] Planned completion date: -
------------------------------------------------------
TASK 2: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 1][Rhapsody]- Implement PDCS - General DIDs and DTCs planned for BA00 release.
Description:
Implement General DIDs planned for BA release as per the requirements.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: 50
Estimated implementation effort/h: 20
Estimated unit testing effort/h: 20
------------------------------------------------------
Total effort/h: 90
[Optional] Planned completion date: -
------------------------------------------------------
TASK 3: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 1][Rhapsody]- Implement Feature related DIDs and DTCs planned for BA00 release.
DecoBATT
SystemState
LSS Torque
LDW
Description:
Implement Feature related DIDs and DTCs planned for BA00 release.
Please see the attached file for more information.
3000_Software_Delivery_Plan_Diagnostic_PR50524_1.7.xlsx
Owner: Tejaswini V
Reviewer: Suman B
Estimated design effort/h: -
Estimated implementation effort/h: -
Estimated unit testing effort/h: -
------------------------------------------------------
Total effort/h: -
[Optional] Planned completion date: -
------------------------------------------------------ | |
Renault XDD - AC00-PDCS-P2*server_max value issue. This item shall implement SWE.3/4 for Provide Diagnostic Services feature for the BA00 SW.
The scope is summarized in the IA Document
Please consider the Diag OPs, revert PDC counter And changes in email attached in attachment section
5410957
5349862
5468164
Services, DID's and DTC's untill BA00 Sprint2 defined below.
SW Diagnostic Delivery Plan:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22 [ Tejaswini Visarapu(Z0086552)- 15.07.2021 ]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> Implement Security Access with Sub services 27 01 & 27 02 based on requirements.
-> Fix the open points from AC00 mentioned in the CR.
-> New DIDs(including VIN) and DTCs need to be introduced as per the BA00 Sprint-2 Requirements.
For that,
-> Update the CDD and Davinci configuration according to requirements.
-> Implement the DIDs and DTCs planned for BA Sprint-2 as per the requirements.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
E152 87 DTCMux ADAS
E148 87 DTCMux VDC
E156 87 DTCMux STRG
E140 87 DTCMux ECM
E14F 87 DTCMux BCM
E15B 87 DTCMux USM
E14E 87 DTCMux METER
E176 87 DTCMux CDM
-> Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Tejaswini Visarapu
Proposal of next steps (incl. effort/h and verification): Please create bellow task(s).
--------------------------------------------------------------------------------
TASK 1: DIAG Autosar Stack Configuration
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3][Sprint 2][Autosar]- Update the DCM, DEM and DIAG SwC configuration for BA release.
Description:
Fix the open points from AC00 mentioned in the CR.
Configure Security Access Sub services 27 01(Request Seed) and 27 02(Send Key).
Configure CDD file and Davinci configuration according to requirements.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
E152 87 DTCMux ADAS
E148 87 DTCMux VDC
E156 87 DTCMux STRG
E140 87 DTCMux ECM
E14F 87 DTCMux BCM
E15B 87 DTCMux USM
E14E 87 DTCMux METER
E176 87 DTCMux CDM
Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: --
Estimated implementation effort/h: NA
Estimated unit testing effort/h: NA
------------------------------------------------------
Total effort/h: --
[Optional] Planned completion date: -
------------------------------------------------------
TASK 2: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 2][Rhapsody] - Security Access(0x27) Implementation.
Description:
Implement Security Access with sub services 27 01 & 27 02.
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: --
Estimated implementation effort/h: --
Estimated unit testing effort/h: --
------------------------------------------------------
Total effort/h: --
[Optional] Planned completion date: -
------------------------------------------------------
TASK 3: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 2][Rhapsody]- Implement DIDs planned for BA00 Sprint-2.
Description:
Fix the open points from AC00 mentioned in the CR.
Implement DIDs(including VIN) planned for BA00 Sprint-2.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
Owner: Tejaswini V
Reviewer: Suman B
Estimated design effort/h: -
Estimated implementation effort/h: -
Estimated unit testing effort/h: -
------------------------------------------------------
Total effort/h: -
[Optional] Planned completion date: -
------------------------------------------------------ | Renault XDD - AC00-PDCS-P2*server_max value issue. This item shall implement SWE.3/4 for Provide Diagnostic Services feature for the BA00 SW.
The scope is summarized in the IA Document
Please consider the Diag OPs, revert PDC counter And changes in email attached in attachment section
5410957
5349862
5468164
Services, DID's and DTC's untill BA00 Sprint2 defined below.
SW Diagnostic Delivery Plan:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22 [ Tejaswini Visarapu(Z0086552)- 15.07.2021 ]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> Implement Security Access with Sub services 27 01 & 27 02 based on requirements.
-> Fix the open points from AC00 mentioned in the CR.
-> New DIDs(including VIN) and DTCs need to be introduced as per the BA00 Sprint-2 Requirements.
For that,
-> Update the CDD and Davinci configuration according to requirements.
-> Implement the DIDs and DTCs planned for BA Sprint-2 as per the requirements.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
E152 87 DTCMux ADAS
E148 87 DTCMux VDC
E156 87 DTCMux STRG
E140 87 DTCMux ECM
E14F 87 DTCMux BCM
E15B 87 DTCMux USM
E14E 87 DTCMux METER
E176 87 DTCMux CDM
-> Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Tejaswini Visarapu
Proposal of next steps (incl. effort/h and verification): Please create bellow task(s).
--------------------------------------------------------------------------------
TASK 1: DIAG Autosar Stack Configuration
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3][Sprint 2][Autosar]- Update the DCM, DEM and DIAG SwC configuration for BA release.
Description:
Fix the open points from AC00 mentioned in the CR.
Configure Security Access Sub services 27 01(Request Seed) and 27 02(Send Key).
Configure CDD file and Davinci configuration according to requirements.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
E152 87 DTCMux ADAS
E148 87 DTCMux VDC
E156 87 DTCMux STRG
E140 87 DTCMux ECM
E14F 87 DTCMux BCM
E15B 87 DTCMux USM
E14E 87 DTCMux METER
E176 87 DTCMux CDM
Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: --
Estimated implementation effort/h: NA
Estimated unit testing effort/h: NA
------------------------------------------------------
Total effort/h: --
[Optional] Planned completion date: -
------------------------------------------------------
TASK 2: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 2][Rhapsody] - Security Access(0x27) Implementation.
Description:
Implement Security Access with sub services 27 01 & 27 02.
Owner: Suman B
Reviewer: Tejaswini V
Estimated design effort/h: --
Estimated implementation effort/h: --
Estimated unit testing effort/h: --
------------------------------------------------------
Total effort/h: --
[Optional] Planned completion date: -
------------------------------------------------------
TASK 3: DIAG Design and Implementation
------------------------------------------------------
Title:[Steering][RN_XDD][SWE.3/4][Sprint 2][Rhapsody]- Implement DIDs planned for BA00 Sprint-2.
Description:
Fix the open points from AC00 mentioned in the CR.
Implement DIDs(including VIN) planned for BA00 Sprint-2.
0x0111 Offset torque (from torque sensor) (main)
0x0113 Motor current demand
0x0115 Assistance Level
0x0153 Initial right RES position
0x0154 Initial left RES position
0x0160 Derating assistance level
0x0169 Max CPU load
0xD002 DebugInto
0x01BE LDW_VibrationIntensity_Master
Please see the attached link for more information.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/Renault%5fNissan/XDD/PR50524%5fRN%5fXDD%5fBD%5fEPS/30%5fSoftware%23forceJump%3d%23n%3d%233000%5fManagement&selection=%223000%5fSoftware%5fDelivery%5fPlan%5fDiagnostic%5fPR50524.xlsx%22
Owner: Tejaswini V
Reviewer: Suman B
Estimated design effort/h: -
Estimated implementation effort/h: -
Estimated unit testing effort/h: -
------------------------------------------------------
Total effort/h: -
[Optional] Planned completion date: -
------------------------------------------------------ | |
Renault XDD - AC00-PDCS-P2*server_max value issue. Fix implemented in SW BA. Please confirm if it was retest or please retest on newest SW version. See attached E-Mail "RE RN XDD AC00 OPs to close wo ver CR.msg" | Renault XDD - AC00-PDCS-P2*server_max value issue. Fix implemented in SW BA. Please confirm if it was retest or please retest on newest SW version. See attached E-Mail "RE RN XDD AC00 OPs to close wo ver CR.msg" | |
[VW_MQB48W_ESC][401-012[CAT3][TEC][ESP] ESP Textanzeigen_03 is expected to go in value 11 when returning to Full on from ASR OFF Implement the following values for ESP_Textanzeigen_03:
- ZF_MQB48W_ESP_Tast_294829: ASR_off (0x7) when in ASR_OFF mode
- ZF_MQB48W_ESP_Tast_294831: ASR_aktiviert (0xB) when returning to full mode after ASR_OFF mode
Be aware that these requirements for ESP_Textanzeigen_03 are different from the VW MEB.
Please check if there are more requirements and/or if further changes are required in this context in order to adapt the implementation to the MQB requirements and take appropriate steps. Christian Eiserloh (EiserloC) [2022-02-25 12:15]:
Implement:
- ZF_MQB48W_ESP_Tast_294829: ESP_Textanzeigen_03 = ASR_OFF (0x7) when in ASR_OFF mode (PERFMODE_TEXT_ASR_OFF)
- ZF_MQB48W_ESP_Tast_294831: ESP_Textanzeigen_03 = ASR_AKTIVIERT (0xB) when returning to full mode (PERFMODE_TEXT_ESC_ON) after ASR_OFF mode
The handling for ESP_Textanzeigen_03 shall be carried over from MEB if applicable and then be adjusted to the MQB requirements. | [VW_MQB48W_ESC][401-012[CAT3][TEC][ESP] ESP Textanzeigen_03 is expected to go in value 11 when returning to Full on from ASR OFF Implement the following values for ESP_Textanzeigen_03:
- ZF_MQB48W_ESP_Tast_294829: ASR_off (0x7) when in ASR_OFF mode
- ZF_MQB48W_ESP_Tast_294831: ASR_aktiviert (0xB) when returning to full mode after ASR_OFF mode
Be aware that these requirements for ESP_Textanzeigen_03 are different from the VW MEB.
Please check if there are more requirements and/or if further changes are required in this context in order to adapt the implementation to the MQB requirements and take appropriate steps. Christian Eiserloh (EiserloC) [2022-02-25 12:15]:
Implement:
- ZF_MQB48W_ESP_Tast_294829: ESP_Textanzeigen_03 = ASR_OFF (0x7) when in ASR_OFF mode (PERFMODE_TEXT_ASR_OFF)
- ZF_MQB48W_ESP_Tast_294831: ESP_Textanzeigen_03 = ASR_AKTIVIERT (0xB) when returning to full mode (PERFMODE_TEXT_ESC_ON) after ASR_OFF mode
The handling for ESP_Textanzeigen_03 shall be carried over from MEB if applicable and then be adjusted to the MQB requirements. | |
[VW_MQB48W_ESC][401-012[CAT3][TEC][ESP] ESP Textanzeigen_03 is expected to go in value 11 when returning to Full on from ASR OFF Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
[Eiserloh Christian KBL ADWC51 (EiserloC), Aug 3, 2022 2:56:01 PM CEST]
The re-test TMP ID 98831 is not failed, but executed wrongly. Instead of returning to ESP Full On in a fault free environment, the fault EXCESSIVE_INIT_TIME_ERROR is latched which inhibits ESP and thus leads to ESP_Textanzeigen_03 = ESP_Stoerung (0x1). That error value has higher priority than any of the ESP mode values. The behavior is correct.
Please test again and make sure that there is no fault that inhibits ESP. ReTested with SW : VW10_P03_M10_S02_VT3_504-007-000_XXXX_N
Behavior ok . ESP Textanzeigen_03 signal is set to value 0x7 when ASR is OFF, then change on value 0xB druing changes to Full ON and than remains on value 0 consatnt .
TMP ID : 135088 (TC 35)
Results already stored in Doors , in "Run Details 14".
Test was executed several times for assure that the behavior correct is reproductible .
TMP IDs : 154882, 154900, 154904 | [VW_MQB48W_ESC][401-012[CAT3][TEC][ESP] ESP Textanzeigen_03 is expected to go in value 11 when returning to Full on from ASR OFF Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
[Eiserloh Christian KBL ADWC51 (EiserloC), Aug 3, 2022 2:56:01 PM CEST]
The re-test TMP ID 98831 is not failed, but executed wrongly. Instead of returning to ESP Full On in a fault free environment, the fault EXCESSIVE_INIT_TIME_ERROR is latched which inhibits ESP and thus leads to ESP_Textanzeigen_03 = ESP_Stoerung (0x1). That error value has higher priority than any of the ESP mode values. The behavior is correct.
Please test again and make sure that there is no fault that inhibits ESP. ReTested with SW : VW10_P03_M10_S02_VT3_504-007-000_XXXX_N
Behavior ok . ESP Textanzeigen_03 signal is set to value 0x7 when ASR is OFF, then change on value 0xB druing changes to Full ON and than remains on value 0 consatnt .
TMP ID : 135088 (TC 35)
Results already stored in Doors , in "Run Details 14".
Test was executed several times for assure that the behavior correct is reproductible .
TMP IDs : 154882, 154900, 154904 | |
[DE30_IBC_BSW_PSW] update for 1st software compiling update for stub.
changes are attached. Check in the attachment. | [DE30_IBC_BSW_PSW] update for 1st software compiling update for stub.
changes are attached. Check in the attachment. | |
[DE30_IBC_BSW_PSW] update for 1st software compiling based on Geely ER, udpated trims interface MC_TYPE.
updated tyre size to according to customer input.
updated some function macro for compiling.
changes are attached. Check in the attachment.
Chassinfmain CP which has attached changes is preintegrated ,only chassinftrims changes checkin required. | [DE30_IBC_BSW_PSW] update for 1st software compiling based on Geely ER, udpated trims interface MC_TYPE.
updated tyre size to according to customer input.
updated some function macro for compiling.
changes are attached. Check in the attachment.
Chassinfmain CP which has attached changes is preintegrated ,only chassinftrims changes checkin required. | |
[DE30_IBC_BSW_PSW] update for 1st software compiling Based on the Geely E4, updated some interface for actuator control.
changes are attached.
Changes done using CR 5302869 to send the configuration time from BSW to PSW are carried over and changes are attached. Check in the attachment. | [DE30_IBC_BSW_PSW] update for 1st software compiling Based on the Geely E4, updated some interface for actuator control.
changes are attached.
Changes done using CR 5302869 to send the configuration time from BSW to PSW are carried over and changes are attached. Check in the attachment. | |
[DE30_IBC_BSW_PSW] update for 1st software compiling PSW has removed VMM, so cubix need remove corresponding interface.
changes are attached. Check in the attachment. | [DE30_IBC_BSW_PSW] update for 1st software compiling PSW has removed VMM, so cubix need remove corresponding interface.
changes are attached. Check in the attachment. | |
[DE30_IBC_BSW_PSW] update for 1st software compiling Based on the Geely E4, some interfaces is added for PSW use.
changes are attached. Check in the attachment. Brief investigation comment: As PSW required, they integrate a new checkpoint from Geely project, we should add the new interface to stub. but this interface don't have the can signal to mapping.
----------------------------------------------------------------------
- 1 task for Owner:Huimin.Zuo /Reviewer:Sreelaksmi
-------------------------------------------------------------------------------- | [DE30_IBC_BSW_PSW] update for 1st software compiling Based on the Geely E4, some interfaces is added for PSW use.
changes are attached. Check in the attachment. Brief investigation comment: As PSW required, they integrate a new checkpoint from Geely project, we should add the new interface to stub. but this interface don't have the can signal to mapping.
----------------------------------------------------------------------
- 1 task for Owner:Huimin.Zuo /Reviewer:Sreelaksmi
-------------------------------------------------------------------------------- | |
[DE30_IBC_BSW_PSW] update for 1st software compiling update cubix macro switch for LC input interface. attachedment is ready for check-in | [DE30_IBC_BSW_PSW] update for 1st software compiling update cubix macro switch for LC input interface. attachedment is ready for check-in | |
[DE30_IBC_BSW_PSW] update for 1st software compiling used macro switch for VDSW interface. attachement is ready for check-in | [DE30_IBC_BSW_PSW] update for 1st software compiling used macro switch for VDSW interface. attachement is ready for check-in | |
[VW_MQB48W_ESC][ADTY3][401-010][CAT3] Value of DbOut.DrvPressReq_s16 remains constant regardless of MCP or PTS state Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
For customer tickets [KPM] attach the logs to open point. Another OP was raised on the HIL environment. OP no longer valid | [VW_MQB48W_ESC][ADTY3][401-010][CAT3] Value of DbOut.DrvPressReq_s16 remains constant regardless of MCP or PTS state Kindly perform retest for related issue.
For issue details and analysis results kindly refer open point description and conclusion field.
Document the test results in OP conclusion field and set the custom pick field 3 value.
For customer tickets [KPM] attach the logs to open point. Another OP was raised on the HIL environment. OP no longer valid | |
[QA][WR][ID412][MAN.3]Project Management Plan - quality review not passed Documents to be shared into the appropiate delivery folder:
- Project Management Plan
- CPDF
- etc. 2022-02-17 OESERR:
All work products completed.
2021-07-09 oeserr:
Work product updates required as result of quality audit. | [QA][WR][ID412][MAN.3]Project Management Plan - quality review not passed Documents to be shared into the appropiate delivery folder:
- Project Management Plan
- CPDF
- etc. 2022-02-17 OESERR:
All work products completed.
2021-07-09 oeserr:
Work product updates required as result of quality audit. | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Execution context, RAM, ROM budget needs to be confirmed.
Propose:
Core 1, ASIL D.
Tasking 10ms
RAM: 5000
ROM: 2000
The component uses standard functions that can be found in math.h, stdlib.h therefore, libc_fpu PRAGMA needs to be added in partitioning wizard for the used region
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE 2022-10-24 CSe: After re-confirming with originator, no further actions required for SwAD. This CR is obsolete and can be rejected. | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Execution context, RAM, ROM budget needs to be confirmed.
Propose:
Core 1, ASIL D.
Tasking 10ms
RAM: 5000
ROM: 2000
The component uses standard functions that can be found in math.h, stdlib.h therefore, libc_fpu PRAGMA needs to be added in partitioning wizard for the used region
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE 2022-10-24 CSe: After re-confirming with originator, no further actions required for SwAD. This CR is obsolete and can be rejected. | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for MeMo:
A new block needs be added in static area to cover the additional counters needed in Mclc.
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w CR can be cancelled. For more information see attachements. | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for MeMo:
A new block needs be added in static area to cover the additional counters needed in Mclc.
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w CR can be cancelled. For more information see attachements. | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for SD:
Carry over the logic required to count the specific events, supply output data for Diag
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE [07.02.2022], R.Klatich: .ini file has to be updated
[21.10.2021], R.Klatich:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Mclc has to be implemented in MEB UN-ECE
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Mclc will be a carry-over from MEB Classic project, all required changes will be made so that it can run in the UN-ECE SW.
The logic will be tested with a script that contains a data set and the expected output of the data delivered by the customer.
TASK
------------------------------------------------------
Title: [MEB UNECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler)
Description: Carry-over from MEB Classic
Owner: Robert Klatich
Reviewer: Christoph Probst
Estimated design effort/h: 8
Estimated implementation effort/h: 8
Estimated unit testing effort/h: 8
------------------------------------------------------
Total effort/h: 16
[Optional] Planned completion date: 22.10.2021
------------------------------------------------------ | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for SD:
Carry over the logic required to count the specific events, supply output data for Diag
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE [07.02.2022], R.Klatich: .ini file has to be updated
[21.10.2021], R.Klatich:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Mclc has to be implemented in MEB UN-ECE
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Mclc will be a carry-over from MEB Classic project, all required changes will be made so that it can run in the UN-ECE SW.
The logic will be tested with a script that contains a data set and the expected output of the data delivered by the customer.
TASK
------------------------------------------------------
Title: [MEB UNECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler)
Description: Carry-over from MEB Classic
Owner: Robert Klatich
Reviewer: Christoph Probst
Estimated design effort/h: 8
Estimated implementation effort/h: 8
Estimated unit testing effort/h: 8
------------------------------------------------------
Total effort/h: 16
[Optional] Planned completion date: 22.10.2021
------------------------------------------------------ | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for Diag:
Diag has to output the following data provided by Mclc data containing:
- Rainflow matrix;
- Retention time;
- Damage;
Also the possibility to enable/disable Mclc via coding needs to be provided.
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w G Baburao 10.02.2022:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Implement diag services for MLCC as per the Doors requirements.
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Read DIDs:
--------
-> 0x030F
-> 0x0310
-> 0x0311
-> 0x0312
-> 0x030E
Write DIDs:
---------
0x030E
Routine:
------
-> 0x0313
-> plese refer the attached screen shots for the better understanding.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): G Baburao
Proposal of next steps (incl. effort/h and verification): please create the tasks
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.1] - Update the MCLC realted DIDs
Description:
-> The 'SwRS-BSW-VehicleDiagnostics' document is DOORS (/C_BrkSw_CSC/40 SW/BSW) needs to be updated concerning customer requirement.
-> The linkage between SwRS and customer requirement shall be established too.
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: GossenD
Reviewer: Licina D
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK 2/5:
-------------------------------------------------------------
Title: [MEB UNECE ESC][Arch][SWE.2] - Update the MCLC realted DIDs.
Description:
->The feature architecture in the \01_Architecture_Design Rhapsody model under ProvideDiagnoticService of FunctionalArchitecture/Diagnostic domain needs to be updated concerning customer requirements.
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: Christoph Bayer
Reviewer: Nancy Rana
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK 3/5:
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.2] - Update the MCLC realted DIDs.
Description:
-> The feature architecture in the \01_Architecture_Design Rhapsody model under the TechnicalArhitecture/Diagnostic domain needs to be updated concerning customer requirements
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: GossenD
Reviewer: LicinaD
Estimated design effort/h: 0
Estimated implementation effort/h: 6
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
------------------------------------------------------
TASK 4/5:
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.3/4] - Provide dcm config for autosar team and implement diag services of MCLC
Description:
Provide dcm config for autosar team and implement diag services
-> pleasw refer the Ananlysis
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Read DIDs:
--------
-> 0x030F
-> 0x0310
-> 0x0311
-> 0x0312
-> 0x030E
Write DIDs:
---------
0x030E
Routine:
------
-> 0x0313
Owner: Subbarao K
Reviewer: Baburao G
Estimated design effort/h: 5
Estimated implementation effort/h: 10
Estimated unit testing effort/h: 10
------------------------------------------------------
Total effort/h: 25h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: Update DCM Configuration and generate RTE for the menction DID/RID
Description:
-> Update Autosar Configuration
-> testing is part of Diag task.
Owner: Niranjan bhalerao
Reviewer: Javali Siva Santhosh
Estimated design effort/h: -
Estimated implementation effort/h: 3
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 3
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/6
------------------------------------------------------
Title: Update PDX with services for MLCC
Description:
Update PDX with services for MLCC
Owner: Gego Kuriakose
Reviewer: V.Vutev
Estimated design effort/h:
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 1
------------------------------------------------------
Total effort/h:3
[Optional] Planned completion date:
------------------------------------------------------
From Function Side following Checkpoint will be used:
#/BrkSw#SwDevelopmentPool/Software/Components/Mclc#forceJump=#b=1.8
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mclc/project.pj
Checkpoint there 1.8
Please check that all Chassinf interfaces/defines and other interfaces will be provided within this CR
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Gelenkwellenzähler activate/deactivate: Carry over from MEB classic project, adaptation channel 0x030E, also RTE interface required!
Measurement values: 0x030F, 0x0310, 0x0311 and 0x0312 to be implemented, also carry over
All legacy interface from MEB Classic needs to be replaced by Rte Interface to be provide the data,
architecture team Rene Lotz needs to be involved!!!
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
-------------------------------------------------------------------------------- | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for Diag:
Diag has to output the following data provided by Mclc data containing:
- Rainflow matrix;
- Retention time;
- Damage;
Also the possibility to enable/disable Mclc via coding needs to be provided.
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w G Baburao 10.02.2022:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Implement diag services for MLCC as per the Doors requirements.
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Read DIDs:
--------
-> 0x030F
-> 0x0310
-> 0x0311
-> 0x0312
-> 0x030E
Write DIDs:
---------
0x030E
Routine:
------
-> 0x0313
-> plese refer the attached screen shots for the better understanding.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): G Baburao
Proposal of next steps (incl. effort/h and verification): please create the tasks
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.1] - Update the MCLC realted DIDs
Description:
-> The 'SwRS-BSW-VehicleDiagnostics' document is DOORS (/C_BrkSw_CSC/40 SW/BSW) needs to be updated concerning customer requirement.
-> The linkage between SwRS and customer requirement shall be established too.
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: GossenD
Reviewer: Licina D
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK 2/5:
-------------------------------------------------------------
Title: [MEB UNECE ESC][Arch][SWE.2] - Update the MCLC realted DIDs.
Description:
->The feature architecture in the \01_Architecture_Design Rhapsody model under ProvideDiagnoticService of FunctionalArchitecture/Diagnostic domain needs to be updated concerning customer requirements.
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: Christoph Bayer
Reviewer: Nancy Rana
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK 3/5:
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.2] - Update the MCLC realted DIDs.
Description:
-> The feature architecture in the \01_Architecture_Design Rhapsody model under the TechnicalArhitecture/Diagnostic domain needs to be updated concerning customer requirements
Link for DOORS requirement:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Owner: GossenD
Reviewer: LicinaD
Estimated design effort/h: 0
Estimated implementation effort/h: 6
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 6
------------------------------------------------------
TASK 4/5:
------------------------------------------------------
Title: [MEB UNECE ESC][Diag][SWE.3/4] - Provide dcm config for autosar team and implement diag services of MCLC
Description:
Provide dcm config for autosar team and implement diag services
-> pleasw refer the Ananlysis
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1075-0013e2a0?doors.view=00000021
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1519-0013e2a4?doors.view=00000006
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-O-1021-0013e2a6?doors.view=00000006
Read DIDs:
--------
-> 0x030F
-> 0x0310
-> 0x0311
-> 0x0312
-> 0x030E
Write DIDs:
---------
0x030E
Routine:
------
-> 0x0313
Owner: Subbarao K
Reviewer: Baburao G
Estimated design effort/h: 5
Estimated implementation effort/h: 10
Estimated unit testing effort/h: 10
------------------------------------------------------
Total effort/h: 25h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: Update DCM Configuration and generate RTE for the menction DID/RID
Description:
-> Update Autosar Configuration
-> testing is part of Diag task.
Owner: Niranjan bhalerao
Reviewer: Javali Siva Santhosh
Estimated design effort/h: -
Estimated implementation effort/h: 3
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 3
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/6
------------------------------------------------------
Title: Update PDX with services for MLCC
Description:
Update PDX with services for MLCC
Owner: Gego Kuriakose
Reviewer: V.Vutev
Estimated design effort/h:
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 1
------------------------------------------------------
Total effort/h:3
[Optional] Planned completion date:
------------------------------------------------------
From Function Side following Checkpoint will be used:
#/BrkSw#SwDevelopmentPool/Software/Components/Mclc#forceJump=#b=1.8
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/BrkSw/SwDevelopmentPool/Software/Components/Mclc/project.pj
Checkpoint there 1.8
Please check that all Chassinf interfaces/defines and other interfaces will be provided within this CR
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Gelenkwellenzähler activate/deactivate: Carry over from MEB classic project, adaptation channel 0x030E, also RTE interface required!
Measurement values: 0x030F, 0x0310, 0x0311 and 0x0312 to be implemented, also carry over
All legacy interface from MEB Classic needs to be replaced by Rte Interface to be provide the data,
architecture team Rene Lotz needs to be involved!!!
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
-------------------------------------------------------------------------------- | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) in electric cars (phev and bev) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
therefore, the mechanical component load counter (gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
the data calculated by mclc needs to be stored and partly outputted by diag.
mclc is already implemented in the meb "classic" project and has to be carry over to vw common.
meb op: alm_open point 4108836
mclc will be located in the sd subsystem.
file should be mapped on dspr1__vp_d,
files to be mapped:
- mclc_inputs.c
- mclc_rainflow.c
- mclc_wrapper.c
see mail attachment for final decision of dspr1__vp_d mapping!
requirements:
belastungszähler gelenkwelle_fktre_meb_un_ece
[02.09.2021], r.klatich:
in partitioning.partwizconf section libc_fpu pragma has to be added for sd:
<pragmas name="libc_fpu" pragmatype="pragma_u"/>
<pragmas name="libc_fpu" pragmatype="pragma_i"/> [kwioteks - 01.10.2021 - 08:23]
analysis target date moved due to missing finla information (see email attached)
[kwioteks - 25.10.2021 - 08:00]
pragma mapping to be clarified!
[kwioteks - 25.10.2021 - 13:00]
task
--------------------------------------------------------------------------------
brief analysis summary:
[mqb48-w esc] partitioning update requested for mclc component added to project
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
risk (low/medium/high):
high
--------------------------------------------------------------------------------
analysis completed by (applicable only for distributed analyses):
proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
task integration team
------------------------------------------------------
title:
[mqb48-w esc] partitioning update requested for mclc component added to projectc
description:
template for task/cr:cr 5468389
------------------------------------------------------------------------------------------------
link and checkpoint/revision of partitioning concept:
https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brk/customer/vw/meb%5fmy2023/esc/05%5fsoftware/view%5fmainline/mmc%5fappl/01%5farchitecture%5fdesign/project.pj&developmentpath=iqm%5fpreinteg%5fvw10%5fp07%5fm10%5fvtx%5fa&selection=swad%5fvw%5fmqb48w%5fesc%2dcomponentlist.xml
------------------------------------------------------------------------------------------------
subsystem/domain/component checkpoint(s):
add the ptc integrity info (path and checkpoint) for the related components containing the files to be mapped here.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/brksw/swdevelopmentpool/software/components/mclc/project.pj (1.8)
------------------------------------------------------------------------------------------------
list of new or deleted files / mapping:
add the files (only *.c files) and the mapping regions here, in case of pragmas or libs to be added enter needed information.
------------------------------------------------------------------------------------------------
c files to be mapped:
- mclc_inputs.c
- mclc_rainflow.c
- mclc_wrapper.c
all c-files need to be mapped to dspr1__vp_d
pragma:
libc_fpu pragma u type an i type needs to be created mapped to dspr1__vp_d
owner: priyanka nasika
reviewer: kwiotek sascha
estimated design effort/h: 2
estimated implementation effort/h: 1
estimated unit testing effort/h: 2
------------------------------------------------------
total effort/h: 5
[optional] planned completion date: 29.10.2021 | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) in electric cars (phev and bev) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
therefore, the mechanical component load counter (gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
the data calculated by mclc needs to be stored and partly outputted by diag.
mclc is already implemented in the meb "classic" project and has to be carry over to vw common.
meb op: alm_open point 4108836
mclc will be located in the sd subsystem.
file should be mapped on dspr1__vp_d,
files to be mapped:
- mclc_inputs.c
- mclc_rainflow.c
- mclc_wrapper.c
see mail attachment for final decision of dspr1__vp_d mapping!
requirements:
belastungszähler gelenkwelle_fktre_meb_un_ece
[02.09.2021], r.klatich:
in partitioning.partwizconf section libc_fpu pragma has to be added for sd:
<pragmas name="libc_fpu" pragmatype="pragma_u"/>
<pragmas name="libc_fpu" pragmatype="pragma_i"/> [kwioteks - 01.10.2021 - 08:23]
analysis target date moved due to missing finla information (see email attached)
[kwioteks - 25.10.2021 - 08:00]
pragma mapping to be clarified!
[kwioteks - 25.10.2021 - 13:00]
task
--------------------------------------------------------------------------------
brief analysis summary:
[mqb48-w esc] partitioning update requested for mclc component added to project
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
risk (low/medium/high):
high
--------------------------------------------------------------------------------
analysis completed by (applicable only for distributed analyses):
proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
task integration team
------------------------------------------------------
title:
[mqb48-w esc] partitioning update requested for mclc component added to projectc
description:
template for task/cr:cr 5468389
------------------------------------------------------------------------------------------------
link and checkpoint/revision of partitioning concept:
https://skobde-mks.kobde.trw.com:7001/si/viewrevision?projectname=/brk/customer/vw/meb%5fmy2023/esc/05%5fsoftware/view%5fmainline/mmc%5fappl/01%5farchitecture%5fdesign/project.pj&developmentpath=iqm%5fpreinteg%5fvw10%5fp07%5fm10%5fvtx%5fa&selection=swad%5fvw%5fmqb48w%5fesc%2dcomponentlist.xml
------------------------------------------------------------------------------------------------
subsystem/domain/component checkpoint(s):
add the ptc integrity info (path and checkpoint) for the related components containing the files to be mapped here.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/brksw/swdevelopmentpool/software/components/mclc/project.pj (1.8)
------------------------------------------------------------------------------------------------
list of new or deleted files / mapping:
add the files (only *.c files) and the mapping regions here, in case of pragmas or libs to be added enter needed information.
------------------------------------------------------------------------------------------------
c files to be mapped:
- mclc_inputs.c
- mclc_rainflow.c
- mclc_wrapper.c
all c-files need to be mapped to dspr1__vp_d
pragma:
libc_fpu pragma u type an i type needs to be created mapped to dspr1__vp_d
owner: priyanka nasika
reviewer: kwiotek sascha
estimated design effort/h: 2
estimated implementation effort/h: 1
estimated unit testing effort/h: 2
------------------------------------------------------
total effort/h: 5
[optional] planned completion date: 29.10.2021 | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for MeMo:
A new block needs be added in static area to cover the additional counters needed in Mclc.
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w --------------------------------------------------------------------------------
Brief analysis summary:
A new block needs be added in static area to cover the additional counters needed in Mclc.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK Memory
------------------------------------------------------
Title:[MY_2023_ESC] A new block needs be added in static area to cover the additional counters needed in Mclc
Description:
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
For more informations please look into CR attachements.
Owner:Miruna Barboni
Reviewer:OoiSiang Tan
Estimated design effort/h: 6
Estimated implementation effort/h: 14
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 20
[Optional] Planned completion date:01.10.2021
------------------------------------------------------
TASK Autosar
------------------------------------------------------
Title: Generate Nvm and EA after 1 new block has been added in static area
Description: Use the DaVinci configuration files ( Nvm and Ea arxml's) provided by the memory task to generate and check-in the Nvm , Ea and Rte files.
------------------------------------------------------
Owner: Sourabh Sarda
Reviewer:Ujawane Riya
Estimated design effort/h:2
Estimated implementation effort/h:2
Estimated unit testing effort/h:0
------------------------------------------------------
Total effort/h:4
[Optional] Planned completion date:01.10.2021
------------------------------------------------------ | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for MeMo:
A new block needs be added in static area to cover the additional counters needed in Mclc.
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE
Belastungszähler Gelenkwelle_MQB48-w --------------------------------------------------------------------------------
Brief analysis summary:
A new block needs be added in static area to cover the additional counters needed in Mclc.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK Memory
------------------------------------------------------
Title:[MY_2023_ESC] A new block needs be added in static area to cover the additional counters needed in Mclc
Description:
The block configuration is as follows:
Block Name: MCLC_DATA
Block Length: 4000 bytes
Protection Strategy: checksummed
Reset Protected: 0
Block Default: 0x00 Write Strategy: During Shutdown
TRW Code Generation: Yes
Plant Progr.: No
Assigned Component: Mclc
- The NvM and Ea configuration should be the similar to the Flm blocks (FLM_STD_DATA, FLM_AX_MATRIX_DATA and FLM_SNPSHOT_DATA...), see CR: 2723500.
- Mclc should be assigned with Core_1.
- NvM_Cfg.c the pointer to the RAM buffers should be: Mclc_Nvram.Data
For more informations please look into CR attachements.
Owner:Miruna Barboni
Reviewer:OoiSiang Tan
Estimated design effort/h: 6
Estimated implementation effort/h: 14
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 20
[Optional] Planned completion date:01.10.2021
------------------------------------------------------
TASK Autosar
------------------------------------------------------
Title: Generate Nvm and EA after 1 new block has been added in static area
Description: Use the DaVinci configuration files ( Nvm and Ea arxml's) provided by the memory task to generate and check-in the Nvm , Ea and Rte files.
------------------------------------------------------
Owner: Sourabh Sarda
Reviewer:Ujawane Riya
Estimated design effort/h:2
Estimated implementation effort/h:2
Estimated unit testing effort/h:0
------------------------------------------------------
Total effort/h:4
[Optional] Planned completion date:01.10.2021
------------------------------------------------------ | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for OS:
Routines shall run in the 10ms ASIL D task (although the Data is in the QM partition), inputs are from performance subsystems.
InitMclc() should be called in Task_Start_Init_D_C1 and Update Calls in Task_10ms_D_C1(after SLR):
- UpdateMclcInput();
- UpdateMclcProccesing();
- UpdateMclcOutput();
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE --------------------------------------------------------------------------------
Brief analysis summary:
InitMclc sh all be added after InitSlr in Task_Start_Init_D_C1 in AppTasksC1.c. This shall be done by OS Team
UpdateMclcInput, UpdateMclcProccesing and UpdateMclcOutput shall be added in Task_10ms_D_C1 after SLR calls. This shall be done by Autosar Team.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeberA4
Proposal of next steps (incl. effort/h and verification):
Create Tasks and aprrove CR.
-------------------------------------------------------------------------------- | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) In electric cars (PHEV and BEV) the torsion force changes on the axle are greater as in combustion engines vehicle because of recuperation.
Therefore, the mechanical component load counter (Gelenkwellenbelastungszähler) needs to be implemented to determinate the stress level of the component by
analyzing the torsion force changes on the axle.
The data calculated by MCLC needs to be stored and partly outputted by Diag.
MCLC is already implemented in the MEB "Classic" project and has to be carry over to VW Common.
MEB OP: ALM_Open Point 4108836
Workpackages for OS:
Routines shall run in the 10ms ASIL D task (although the Data is in the QM partition), inputs are from performance subsystems.
InitMclc() should be called in Task_Start_Init_D_C1 and Update Calls in Task_10ms_D_C1(after SLR):
- UpdateMclcInput();
- UpdateMclcProccesing();
- UpdateMclcOutput();
Requirements:
Belastungszähler Gelenkwelle_FktRe_MEB_UN_ECE --------------------------------------------------------------------------------
Brief analysis summary:
InitMclc sh all be added after InitSlr in Task_Start_Init_D_C1 in AppTasksC1.c. This shall be done by OS Team
UpdateMclcInput, UpdateMclcProccesing and UpdateMclcOutput shall be added in Task_10ms_D_C1 after SLR calls. This shall be done by Autosar Team.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeberA4
Proposal of next steps (incl. effort/h and verification):
Create Tasks and aprrove CR.
-------------------------------------------------------------------------------- | |
[VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) Unfortunately the MCLC integration was postponed in the project. However the MCLC block configuration was already finished. Without SD integration, the SW would not compile. Thus, MCLC block was deactivated temporarily.
Please reactivate the MCLC block again in the NVRAM configuration:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
2 Tasks are needed (NVM + Autosar). Use branch NvramArWrp_VW_UN_ECE_ESC. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------Unfortunately the MCLC integration was postponed in the project. However the MCLC block configuration was already finished. Without SD integration, the SW would not compile. Thus, MCLC block was deactivated temporarily.
Reactivation of the MCLC block again in the NVRAM configuration is needed:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
2 Tasks are needed (NVM + Autosar).
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Barboni Miruna
Proposal of next steps (incl. effort/h and verification): 1 Memory Task & 1 Autosar Task
--------------------------------------------------------------------------------
TASK Memory
------------------------------------------------------
Title: [UN ECE ESC][Memo]Reactivate MCLC NVRAM block
Description:
Please reactivate the MCLC block again in the NVRAM configuration:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
Owner: Miruna Barboni
Reviewer: Ooi Siang Tan
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK Autosar
------------------------------------------------------
Title: [BswAutocore] Generate and check in memory related (NvM, Ea, Fee, etc.) files
Description: Use the DaVinci configuration files provided by the memory task to generate and check-in the memory related (NvM, Ea, Fee, etc.) files to UN ECE ESC project.
Owner: Simo Mannan
Reviewer:
Estimated design effort/h:1
Estimated implementation effort/h:1
Estimated unit testing effort/h:0
------------------------------------------------------
Total effort/h: 2 | [VW MEB UNE-ECE][SD] Implementation mechanical component load counter (Gelenkwellenbelastungszähler) Unfortunately the MCLC integration was postponed in the project. However the MCLC block configuration was already finished. Without SD integration, the SW would not compile. Thus, MCLC block was deactivated temporarily.
Please reactivate the MCLC block again in the NVRAM configuration:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
2 Tasks are needed (NVM + Autosar). Use branch NvramArWrp_VW_UN_ECE_ESC. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------Unfortunately the MCLC integration was postponed in the project. However the MCLC block configuration was already finished. Without SD integration, the SW would not compile. Thus, MCLC block was deactivated temporarily.
Reactivation of the MCLC block again in the NVRAM configuration is needed:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
2 Tasks are needed (NVM + Autosar).
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Barboni Miruna
Proposal of next steps (incl. effort/h and verification): 1 Memory Task & 1 Autosar Task
--------------------------------------------------------------------------------
TASK Memory
------------------------------------------------------
Title: [UN ECE ESC][Memo]Reactivate MCLC NVRAM block
Description:
Please reactivate the MCLC block again in the NVRAM configuration:
- MCLC header file include
- MCLC RAM buffer referral
- other needed NVM attributes (most probably NvramReadAll & NvramWriteAll checkboxes); watch closely for DaVinci warnings!
Owner: Miruna Barboni
Reviewer: Ooi Siang Tan
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 0
------------------------------------------------------
Total effort/h: 2
------------------------------------------------------
TASK Autosar
------------------------------------------------------
Title: [BswAutocore] Generate and check in memory related (NvM, Ea, Fee, etc.) files
Description: Use the DaVinci configuration files provided by the memory task to generate and check-in the memory related (NvM, Ea, Fee, etc.) files to UN ECE ESC project.
Owner: Simo Mannan
Reviewer:
Estimated design effort/h:1
Estimated implementation effort/h:1
Estimated unit testing effort/h:0
------------------------------------------------------
Total effort/h: 2 | |
[0521][CAT4][CASE][VW_MEB_SCS] IsoVA: Verstimmung Fahrerwunsch möglich Preconditions / Ausgangsituation:
SW SCS: b521
SW EBB: a657
Maneuver name: xxx
Vehicle: xxx
--------------------------------------------------------------------------------
Actions / Aktionen:
1. PH_asphalt_straight_line_braking_medium_decel_120_kph
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
Fahrerwunsch folgt physikalisch korrekt dem Pedalweg, entweder durch Mcp- oder PTS-basierte Berechnung.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
IsoVA: Fahrerwunsch steigt kaum weiter an trotz steigendem Pedalweg
• 20210618_MEB41B20181_b521_a657_001_027
• Vgl. vorherigen Punkt
• Hier macht es mMn auch Sinn, dass der Fahrerwunsch PTS basiert weiter anwächst
• Vertrauen auf Mcp obwohl dieser durch das "Blending" in die VA gar nicht die Fahreraktivität wiederspiegeln kann
IsoVA: Fahrerwunsch lernt sich runter trotz steigendem Pedalweg
• 20210616_VW316810076_b521_a621_009
• Bei Wechsel nach DeltaMcp ist VA noch am synchronisieren
• Dadurch sinkt Mcp und Fahrerwunsch weiter ab, obwohl Pedalweg ansteigt
• Auswirkung auf analoges Dumpen?
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Bisher keine negativen rausgefahren bzw. bisher nicht beachtet (?) -> Analoges Dumpen könnte zu früh abbrechen, da Fahrerwunsch schon erreicht, Druck und Generatoranforderung aber noch absinken bzw. ansteigen könnten.
--------------------------------------------------------------------------------
Mögliche Lösung:
-Fahrerwunsch wird PTS-basiert berechnet, wenn der Mcp durch Ventil/Pumpenaktivitäten manipuliert wird. Aufhebung der VA stellt insofern auch ein Blending dar. Umschaltung im DB erst wenn FrontAxleIsolated auf FALSE geht?
-Erhöhung Vorbefüllungsvolumen => keine vielversprechende Lösung, da Vorbefüllungsvolumen so gewählt werden muss, dass Verzögerungshomogenität erreicht wird und damit das Verhältnis von Momentenaufbau an den Rädern zu Pedalweg stimmen muss (nicht Mcp zu Pedalweg) [14.09.21], E. Webert: Umsetzung erfolgt für MEB UN ECE (und MQB). Nicht mehr für den MEB Classic.
[23.09.2022], E. Webert: Bisher gab es keine negativen Punkte. Damit wird dieser CR rejectet. | [0521][CAT4][CASE][VW_MEB_SCS] IsoVA: Verstimmung Fahrerwunsch möglich Preconditions / Ausgangsituation:
SW SCS: b521
SW EBB: a657
Maneuver name: xxx
Vehicle: xxx
--------------------------------------------------------------------------------
Actions / Aktionen:
1. PH_asphalt_straight_line_braking_medium_decel_120_kph
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
Fahrerwunsch folgt physikalisch korrekt dem Pedalweg, entweder durch Mcp- oder PTS-basierte Berechnung.
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
IsoVA: Fahrerwunsch steigt kaum weiter an trotz steigendem Pedalweg
• 20210618_MEB41B20181_b521_a657_001_027
• Vgl. vorherigen Punkt
• Hier macht es mMn auch Sinn, dass der Fahrerwunsch PTS basiert weiter anwächst
• Vertrauen auf Mcp obwohl dieser durch das "Blending" in die VA gar nicht die Fahreraktivität wiederspiegeln kann
IsoVA: Fahrerwunsch lernt sich runter trotz steigendem Pedalweg
• 20210616_VW316810076_b521_a621_009
• Bei Wechsel nach DeltaMcp ist VA noch am synchronisieren
• Dadurch sinkt Mcp und Fahrerwunsch weiter ab, obwohl Pedalweg ansteigt
• Auswirkung auf analoges Dumpen?
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
Bisher keine negativen rausgefahren bzw. bisher nicht beachtet (?) -> Analoges Dumpen könnte zu früh abbrechen, da Fahrerwunsch schon erreicht, Druck und Generatoranforderung aber noch absinken bzw. ansteigen könnten.
--------------------------------------------------------------------------------
Mögliche Lösung:
-Fahrerwunsch wird PTS-basiert berechnet, wenn der Mcp durch Ventil/Pumpenaktivitäten manipuliert wird. Aufhebung der VA stellt insofern auch ein Blending dar. Umschaltung im DB erst wenn FrontAxleIsolated auf FALSE geht?
-Erhöhung Vorbefüllungsvolumen => keine vielversprechende Lösung, da Vorbefüllungsvolumen so gewählt werden muss, dass Verzögerungshomogenität erreicht wird und damit das Verhältnis von Momentenaufbau an den Rädern zu Pedalweg stimmen muss (nicht Mcp zu Pedalweg) [14.09.21], E. Webert: Umsetzung erfolgt für MEB UN ECE (und MQB). Nicht mehr für den MEB Classic.
[23.09.2022], E. Webert: Bisher gab es keine negativen Punkte. Damit wird dieser CR rejectet. | |
[XQA][PA2123][ASPICE][SWE.6][CL2][GP.2.2.4]_Software Qualification Test_Review protocol about consistency between test specification and SW requirements not well understandable Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | [XQA][PA2123][ASPICE][SWE.6][CL2][GP.2.2.4]_Software Qualification Test_Review protocol about consistency between test specification and SW requirements not well understandable Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | |
[XQA][PA2123][ASPICE][SWE.6][CL1][BP.6]_Software Qualification Test_Inconsistency between software requirements, test purpose, test specification, test case description and test implementation Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | [XQA][PA2123][ASPICE][SWE.6][CL1][BP.6]_Software Qualification Test_Inconsistency between software requirements, test purpose, test specification, test case description and test implementation Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | |
[XQA][PA2123][ASPICE][SWE.6][CL1][BP.2]_Software Qualification Test_Test procedure inconsistent with requirement Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | [XQA][PA2123][ASPICE][SWE.6][CL1][BP.2]_Software Qualification Test_Test procedure inconsistent with requirement Container for management and quality assurance activities for IS4 release Container for management and quality assurance activities for IS4 release | |
[QA][PA2116][SYS.1][BP.2][GP.2.1.7]not all stakeholders (persons with clearly stated roles/authorities) on customer and ZF side have been adequately identified ASPICE assessment report.
SYS.1_BP.2
Weaknesses:
(-) not all stakeholders (persons with clearly stated roles/authorities) on customer and ZF side have been adequately identified. In the communication plan we see that roles/departments that are usually involved in a steering project are not or insufficiently described. unclear, whether all relevant stakeholders are involved (though there is evidence about significant communication with the customer, and e.g. with the ZF production representative)
SYS.1_GP.2.1.7
Weaknesses:
(-) Customer related meetings are defined, no other meetings Communication plan and SEMP are updated, and the tasks are linked. | [QA][PA2116][SYS.1][BP.2][GP.2.1.7]not all stakeholders (persons with clearly stated roles/authorities) on customer and ZF side have been adequately identified ASPICE assessment report.
SYS.1_BP.2
Weaknesses:
(-) not all stakeholders (persons with clearly stated roles/authorities) on customer and ZF side have been adequately identified. In the communication plan we see that roles/departments that are usually involved in a steering project are not or insufficiently described. unclear, whether all relevant stakeholders are involved (though there is evidence about significant communication with the customer, and e.g. with the ZF production representative)
SYS.1_GP.2.1.7
Weaknesses:
(-) Customer related meetings are defined, no other meetings Communication plan and SEMP are updated, and the tasks are linked. | |
[VW KPM] $600A0 CPU_MPU_EXCEPTION nach Routine 0x02AE Fix the CPU_MPU_EXCEPTION for the listed routies.
-> 0x02AE, 0x02EE and 0x02ED G Baburao,09.08.2021:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> For the routines (0x02AE, 0x02EE and 0x02ED) Null point exception is facing due to Actual arguments passed with out address operator in the RoutineServices_ParkingBrakeMotorClosingStepwise_Start(),RoutineServices_ParkingBrakeMotorLeftClosingStepwise_Start() and RoutineServices_ParkingBrakeMotorRightClosingStepwise_Start()
-> Rework on the belwo 3 functions to fix the issue.
routineProcessStatus = GenericStartRoutineInterface(EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_closing_stepwise_In, NULL, EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_right_closing_stepwise_In, NULL, EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_left_closing_stepwise_In, NULL, EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): G Baburao.
Proposal of next steps (incl. effort/h and verification): create the task below task(s)
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title:[MQB_ESC][Diag][401SW] :Fix the issue related to CPU_MPU_EXCEPTION in 0x02AE, 0x02EE and 0x02ED
Description:
Implementation:
-> For the routines (0x02AE, 0x02EE and 0x02ED) Null point exception is facing due to Actual arguments passed with out address operator in the RoutineServices_ParkingBrakeMotorClosingStepwise_Start(),RoutineServices_ParkingBrakeMotorLeftClosingStepwise_Start() and RoutineServices_ParkingBrakeMotorRightClosingStepwise_Start()
-> Rework on the belwo 3 functions to fix the issue.
routineProcessStatus = GenericStartRoutineInterface(EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_closing_stepwise_In, NULL, EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_right_closing_stepwise_In, NULL, EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_left_closing_stepwise_In, NULL, EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
Quality:
-------
-> Fix the QAC and polysapce ,if any.
-> VC update not applicable as it bug fix.
Owner: Anvesh K
Reviewer: Baburao G
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 3
------------------------------------------------------
Total effort/h: 5
[Optional] Planned completion date: NA
------------------------------------------------------ | [VW KPM] $600A0 CPU_MPU_EXCEPTION nach Routine 0x02AE Fix the CPU_MPU_EXCEPTION for the listed routies.
-> 0x02AE, 0x02EE and 0x02ED G Baburao,09.08.2021:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
-> For the routines (0x02AE, 0x02EE and 0x02ED) Null point exception is facing due to Actual arguments passed with out address operator in the RoutineServices_ParkingBrakeMotorClosingStepwise_Start(),RoutineServices_ParkingBrakeMotorLeftClosingStepwise_Start() and RoutineServices_ParkingBrakeMotorRightClosingStepwise_Start()
-> Rework on the belwo 3 functions to fix the issue.
routineProcessStatus = GenericStartRoutineInterface(EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_closing_stepwise_In, NULL, EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_right_closing_stepwise_In, NULL, EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_left_closing_stepwise_In, NULL, EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): G Baburao.
Proposal of next steps (incl. effort/h and verification): create the task below task(s)
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title:[MQB_ESC][Diag][401SW] :Fix the issue related to CPU_MPU_EXCEPTION in 0x02AE, 0x02EE and 0x02ED
Description:
Implementation:
-> For the routines (0x02AE, 0x02EE and 0x02ED) Null point exception is facing due to Actual arguments passed with out address operator in the RoutineServices_ParkingBrakeMotorClosingStepwise_Start(),RoutineServices_ParkingBrakeMotorLeftClosingStepwise_Start() and RoutineServices_ParkingBrakeMotorRightClosingStepwise_Start()
-> Rework on the belwo 3 functions to fix the issue.
routineProcessStatus = GenericStartRoutineInterface(EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_closing_stepwise_In, NULL, EPB_BOTH_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_right_closing_stepwise_In, NULL, EPB_RIGHT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
routineProcessStatus = GenericStartRoutineInterface(EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_ID, Parameter_Parking_brake_motor_left_closing_stepwise_In, NULL, EPB_LEFT_CLOSE_STEP_BY_STEP_TEST_REQ_LENGTH, NULL, ErrorCode);
Quality:
-------
-> Fix the QAC and polysapce ,if any.
-> VC update not applicable as it bug fix.
Owner: Anvesh K
Reviewer: Baburao G
Estimated design effort/h: 0
Estimated implementation effort/h: 2
Estimated unit testing effort/h: 3
------------------------------------------------------
Total effort/h: 5
[Optional] Planned completion date: NA
------------------------------------------------------ | |
[VW KPM] $600A0 CPU_MPU_EXCEPTION nach Routine 0x02AE [Error Description]: Vorbedingung: ESC+eBKV in Betrieb genommen, EPB geschlossen
Verifikationsinstanz: Fahrzeug
Aktion:
A1: GE 0x02AE open ausführen
Resultat:
R1: Lampe ESP, ABS, BK an
EPB_Schalterposition=3=Fehler
Fehlereintrag $600A0 Interne Störung / CPU_MPU_EXCEPTION
Erwartetes Ergebnis:
E1: keine Fehler/Störungen
Heilung: Kl.15 Wechsel
Bemerkung: Verhalten wie in KPM 8600118?
Tester: extern.frank.goldberg1@volkswagen.de
[Fault Type]: 1284
[Creator Contact Person]: EICHLER,FRIEDRICH
[Creator Email]: extern.frank.goldberg1@volkswagen.de
[Creator Phone]: +49537180-55809 YelluriN:
As per the OP Comments, the behaviour is acceptable.
Test cases are passed.
Please find the Attachements.
YelluriN: CR is analysed by tcs | [VW KPM] $600A0 CPU_MPU_EXCEPTION nach Routine 0x02AE [Error Description]: Vorbedingung: ESC+eBKV in Betrieb genommen, EPB geschlossen
Verifikationsinstanz: Fahrzeug
Aktion:
A1: GE 0x02AE open ausführen
Resultat:
R1: Lampe ESP, ABS, BK an
EPB_Schalterposition=3=Fehler
Fehlereintrag $600A0 Interne Störung / CPU_MPU_EXCEPTION
Erwartetes Ergebnis:
E1: keine Fehler/Störungen
Heilung: Kl.15 Wechsel
Bemerkung: Verhalten wie in KPM 8600118?
Tester: extern.frank.goldberg1@volkswagen.de
[Fault Type]: 1284
[Creator Contact Person]: EICHLER,FRIEDRICH
[Creator Email]: extern.frank.goldberg1@volkswagen.de
[Creator Phone]: +49537180-55809 YelluriN:
As per the OP Comments, the behaviour is acceptable.
Test cases are passed.
Please find the Attachements.
YelluriN: CR is analysed by tcs | |
Geely Lotus | DA00(Lane1) | SWE.6 | SIL Test | Protect Against Excessive Steering Gear Friction (PAESGF) Feature | Signal issue Activity Description: Bug Fix Confirmation(OP confirmation)for VP2-1_SW_PURL3
Feature:Protect Against Excessive Steering Gear Friciton go to analysed | Geely Lotus | DA00(Lane1) | SWE.6 | SIL Test | Protect Against Excessive Steering Gear Friction (PAESGF) Feature | Signal issue Activity Description: Bug Fix Confirmation(OP confirmation)for VP2-1_SW_PURL3
Feature:Protect Against Excessive Steering Gear Friciton go to analysed | |
Geely Lotus | DA00(Lane1) | SWE.6 | SIL Test | Protect Against Excessive Steering Gear Friction (PAESGF) Feature | Signal issue This is only an intermediate CR to cluster all working packages same as the parent build requested but valid only for this release candidate build and this sigle change allocated. Go to ALM_Analysed | Geely Lotus | DA00(Lane1) | SWE.6 | SIL Test | Protect Against Excessive Steering Gear Friction (PAESGF) Feature | Signal issue This is only an intermediate CR to cluster all working packages same as the parent build requested but valid only for this release candidate build and this sigle change allocated. Go to ALM_Analysed | |
[657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected Restart after under voltage is not possible. The initialization fails with fault EBB_INIT_MPS_FAULT and EBB remains fully degraded. The reason for the failed initialization is the bridge driver is still degraded because of ACTIVE_BRAKING_COMPLETED fault. This fault is ignition latched and prevents restart when under voltage faults (condition latched) are cleared.
The SiSo configuration must be adapted. The active braking mode shall not be set for condition latched fault monitors.
Following this rule the attribute Set_Active_Braking shall be set to FALSE for the following failure monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH Cristian Traier (22/09/20201):
--------------------------------------------------------------------------------
Brief analysis summary:Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
Owner: Cristian Traier
Reviewer: Ionut Stanca
Estimated effort/h: 4h
Task-Description:
In DMT, change the attribute Set_Active_Braking to FALSE for the following fault monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH
--------------------------------------------------------------------------------
[Optionlal] Planed completion date: | [657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected Restart after under voltage is not possible. The initialization fails with fault EBB_INIT_MPS_FAULT and EBB remains fully degraded. The reason for the failed initialization is the bridge driver is still degraded because of ACTIVE_BRAKING_COMPLETED fault. This fault is ignition latched and prevents restart when under voltage faults (condition latched) are cleared.
The SiSo configuration must be adapted. The active braking mode shall not be set for condition latched fault monitors.
Following this rule the attribute Set_Active_Braking shall be set to FALSE for the following failure monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH Cristian Traier (22/09/20201):
--------------------------------------------------------------------------------
Brief analysis summary:Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
Owner: Cristian Traier
Reviewer: Ionut Stanca
Estimated effort/h: 4h
Task-Description:
In DMT, change the attribute Set_Active_Braking to FALSE for the following fault monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH
--------------------------------------------------------------------------------
[Optionlal] Planed completion date: | |
[657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected Restart after under voltage is not possible. The initialization fails with fault EBB_INIT_MPS_FAULT and EBB remains fully degraded. The reason for the failed initialization is the bridge driver is still degraded because of ACTIVE_BRAKING_COMPLETED fault. This fault is ignition latched and prevents restart when under voltage faults (condition latched) are cleared.
The SiSo configuration must be adapted. The active braking mode shall not be set for condition latched fault monitors.
Following this rule the attribute Set_Active_Braking shall be set to FALSE for the following failure monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH Cristian Traier (23/09/20201):
--------------------------------------------------------------------------------
Brief analysis summary:Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
Owner: Cristian Traier
Reviewer: Ionut Stanca
Estimated effort/h: 4h
Task-Description:
In DMT, change the attribute Set_Active_Braking to FALSE for the following fault monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH | [657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected Restart after under voltage is not possible. The initialization fails with fault EBB_INIT_MPS_FAULT and EBB remains fully degraded. The reason for the failed initialization is the bridge driver is still degraded because of ACTIVE_BRAKING_COMPLETED fault. This fault is ignition latched and prevents restart when under voltage faults (condition latched) are cleared.
The SiSo configuration must be adapted. The active braking mode shall not be set for condition latched fault monitors.
Following this rule the attribute Set_Active_Braking shall be set to FALSE for the following failure monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH Cristian Traier (23/09/20201):
--------------------------------------------------------------------------------
Brief analysis summary:Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: Change Set_Active_Braking attribute to FALSE for SYSTEM_VOLTAGE fault monitors
--------------------------------------------------------------------------------
Owner: Cristian Traier
Reviewer: Ionut Stanca
Estimated effort/h: 4h
Task-Description:
In DMT, change the attribute Set_Active_Braking to FALSE for the following fault monitors:
SYSTEM_VOLTAGE_EXCESSIVE_LOW
SYSTEM_VOLTAGE_ASIC_RANGE_LOW
SYSTEM_VOLTAGE_EXCESSIVE_HIGH
SYSTEM_VOLTAGE_ASIC_RANGE_HIGH
SYSTEM_VOLTAGE_RESET_LOW
SYSTEM_VOLTAGE_RESET_HIGH | |
[657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected It is possible, that the DTCs SYSTEM_VOLTAGE_EXCESSIVE_LOW or SYSTEM_VOLTAGE_RESET_LOW disappear for a short time from Faultstack. It is also possible, that SYSTEM_VOLTAGE_RESET_LOW is replaced by SYSTEM_VOLTAGE_ASIC_RANGE_LOW for a short period of time.
In that case the initialization timer must be reseted, to avoid a cancellation of the routine and a full degradation of the EBB with an EBB_INIT_MPS_FAULT, when the timer exceeds its threshold. The initialization timer shall be extended with an additional reset condition.
Additionally, the timer shall not start, if the SYSTEM_VOLTAGE_ASIC_RANGE_LOW fault is present. | [657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected It is possible, that the DTCs SYSTEM_VOLTAGE_EXCESSIVE_LOW or SYSTEM_VOLTAGE_RESET_LOW disappear for a short time from Faultstack. It is also possible, that SYSTEM_VOLTAGE_RESET_LOW is replaced by SYSTEM_VOLTAGE_ASIC_RANGE_LOW for a short period of time.
In that case the initialization timer must be reseted, to avoid a cancellation of the routine and a full degradation of the EBB with an EBB_INIT_MPS_FAULT, when the timer exceeds its threshold. The initialization timer shall be extended with an additional reset condition.
Additionally, the timer shall not start, if the SYSTEM_VOLTAGE_ASIC_RANGE_LOW fault is present. | |
[657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected The different voltage sources for Asics and SystemVoltage faults result in problems during rising voltages and related rehabilitation.
The BD Asic on the latest HW is supplied by VBAT_SW which is lower than KL30_M_FUSED which's the source for the SystemVoltage faults and thus the input for performance behavior.
Thus when the SystemVoltage is during slow raising voltage already at 6.5V to pass the EXC LOW fault the VBAT_SW voltage is still below the 6V the BD needs for it's startup.
Performance only checks for the passed EXC LOW fault and not if the Asic is already ready and that results in a try for motor init which can not be done without the Asic.
Discussed solution is to set the rehabilitation threshold for the EXC LOW fault from 6.5V to 7V so when performance tries to initialize the motor position the BD Asic is already supplied by a voltage hinger than 6V.
Attached Mail and meeting minutes from meeting with System and GEE.
OP description:
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar16
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 789020 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. MannesM1 28.09.21 13:40
PwrSup shall be updated to be more robust during UV and "delay" the recovery of the SystemVoltage EXC LOW fault to 7V instead of 6.5V
ALso Capella faults shall get a UV robustnes upgrade.
BrdigeDriver updates will be done with a seperate CR 5309536. | [657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected The different voltage sources for Asics and SystemVoltage faults result in problems during rising voltages and related rehabilitation.
The BD Asic on the latest HW is supplied by VBAT_SW which is lower than KL30_M_FUSED which's the source for the SystemVoltage faults and thus the input for performance behavior.
Thus when the SystemVoltage is during slow raising voltage already at 6.5V to pass the EXC LOW fault the VBAT_SW voltage is still below the 6V the BD needs for it's startup.
Performance only checks for the passed EXC LOW fault and not if the Asic is already ready and that results in a try for motor init which can not be done without the Asic.
Discussed solution is to set the rehabilitation threshold for the EXC LOW fault from 6.5V to 7V so when performance tries to initialize the motor position the BD Asic is already supplied by a voltage hinger than 6V.
Attached Mail and meeting minutes from meeting with System and GEE.
OP description:
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar16
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 789020 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. MannesM1 28.09.21 13:40
PwrSup shall be updated to be more robust during UV and "delay" the recovery of the SystemVoltage EXC LOW fault to 7V instead of 6.5V
ALso Capella faults shall get a UV robustnes upgrade.
BrdigeDriver updates will be done with a seperate CR 5309536. | |
[657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar16
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 789020 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. Cr had been analyze | [657][CAT3][TEC] [VW_ID_BUZZ_EBB] Safety Mechaninsm3 -SYS AD level - EBB_INIT_MPS_FAULT is seen but not expected ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar16
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 789020 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. Cr had been analyze | |
[VW KPM] DTC Geber 1 für Bremspedalweg Unterbrechung [Error Description]: Beanstandung vom Prüfplatz NV-Fahrzeugrobustheit aus KW27:
Fehlerbeschreibung:
Diagnoseeintrag nach Prüfspannungsimpuls(en):
Display: [P057A00] PTS1_NO_SIGNAL
Diagnostic: [02101553, 0x201131] Geber 1 für Bremspedalweg Unterbrechung
Vorbedingung:
1. Ubat 13V
2. Kl.15 EIN
3. FSP löschen
4. Klemmenwechsel
5. FSP lesen
Aktion:
1. Klemmenwechsel
2. variable Wartezeit
3. Prüfspannungsimpuls abspielen
4. Klemmenwechsel
5. FSP lesen
erwartetes Ergebnis:
1. kein unberechtigter FSPE nach Prüfspannungsimpuls
2. sämtliche Funktionen des Fahrzeugs sind nach dem Prüfspannungsimpuls wieder hergestellt
Fahrzeug:
VW316820061
bei Impulsen:
E09-001_TF1_Resetverhalten
E09-000_TF2_Resetverhalten
E09-001_TF2_Resetverhalten
E09-002_TF2_Resetverhalten
E09-002_TF3_Resetverhalten
E09-003_TF3_Resetverhalten
E09-002_TF4_Resetverhalten
E09-001_TF5_Resetverhalten
E09-002_TF5_Resetverhalten
Dokumente zur Art und zum Verlauf der Impulse befinden sich im angehängten ZIP Archiv ~wichtige Zusatzinfos~.
Tester:
Extern.stefan.willmes1@volkswagen.de
+49-1621027754
Automatisierte Prüfung der Diagnose nach Prüfspannungsimpuls
- Prüfaufbau: Batterie des REALEN FAHRZEUGS wird durch eine externe Spannungsquelle ersetzt, die das Fahrzeug mit dem Prüfspannungsimpuls beaufschlagt. Datenlogger und Diagnose sind am Fahrzeug angeschlossen. Die Klemmensteuerung erfolgt automatisiert.
- Klemmenwechsel: Kl.15 AUS, Kl.S AUS, Kl.15 EIN
- FSPE: Fehlerspeichereintrag
- getestet wird stets nach der neuesten Version des Prüfspannungsimpulses
- Die an den Bordnetzklemmen aufgezeichnete Analogspannung lässt sich als Umgebungsvariable darstellen. Dazu muss die Datenbasis aus dem angehängten ZIP Archiv ~Wichtige Zusatzinfos~ zu CAN24 hinzugefügt werden.
Kommentar:
Die sinngemäßen Diagnoseeinträge Unter- bzw. Über-Spannung sowie die Diagnoseeinträge Funktionseinschränkung durch Über- bzw. Unter-Spannung wurden nicht auf die in der Steuergerätespezifikation festgelegten Spannungslevel und Qualifizierungszeiten überprüft. Geprüft wurde die Plausibilität von Diagnoseeinträgen bezogen auf die Spannungslevel der Spannungsereignisse.
[Fault Type]: 0
[Status]: 0
[Creator Contact Person]: WOLLENBERG,MARKO
[Creator Email]: extern.stefan.willmes1@volkswagen.de
[Creator Phone]: +49-162-1027754 [Krishna Kumar Shanmugam(ShanmugK), 04-10-2021 10:33]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
- Faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL are observed during environmental test. These faults are latched when the supply voltage of sensor is below 4.85 V.
- So, the faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL shall be assigned to low voltage fault group.
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [MEB][EBB] Add faults PTS1_NO_SIGNAL, PTS2_NO_SIGNAL and MPS2_NO_SIGNAL to low voltage fault group.
Description:
- Faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL are observed during environmental test. These faults are latched when the supply voltage of sensor is below 4.85 V.
- So, the faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL shall be assigned to low voltage fault group.
Owner:
Reviewer:
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date:
--------------------------------------------------- | [VW KPM] DTC Geber 1 für Bremspedalweg Unterbrechung [Error Description]: Beanstandung vom Prüfplatz NV-Fahrzeugrobustheit aus KW27:
Fehlerbeschreibung:
Diagnoseeintrag nach Prüfspannungsimpuls(en):
Display: [P057A00] PTS1_NO_SIGNAL
Diagnostic: [02101553, 0x201131] Geber 1 für Bremspedalweg Unterbrechung
Vorbedingung:
1. Ubat 13V
2. Kl.15 EIN
3. FSP löschen
4. Klemmenwechsel
5. FSP lesen
Aktion:
1. Klemmenwechsel
2. variable Wartezeit
3. Prüfspannungsimpuls abspielen
4. Klemmenwechsel
5. FSP lesen
erwartetes Ergebnis:
1. kein unberechtigter FSPE nach Prüfspannungsimpuls
2. sämtliche Funktionen des Fahrzeugs sind nach dem Prüfspannungsimpuls wieder hergestellt
Fahrzeug:
VW316820061
bei Impulsen:
E09-001_TF1_Resetverhalten
E09-000_TF2_Resetverhalten
E09-001_TF2_Resetverhalten
E09-002_TF2_Resetverhalten
E09-002_TF3_Resetverhalten
E09-003_TF3_Resetverhalten
E09-002_TF4_Resetverhalten
E09-001_TF5_Resetverhalten
E09-002_TF5_Resetverhalten
Dokumente zur Art und zum Verlauf der Impulse befinden sich im angehängten ZIP Archiv ~wichtige Zusatzinfos~.
Tester:
Extern.stefan.willmes1@volkswagen.de
+49-1621027754
Automatisierte Prüfung der Diagnose nach Prüfspannungsimpuls
- Prüfaufbau: Batterie des REALEN FAHRZEUGS wird durch eine externe Spannungsquelle ersetzt, die das Fahrzeug mit dem Prüfspannungsimpuls beaufschlagt. Datenlogger und Diagnose sind am Fahrzeug angeschlossen. Die Klemmensteuerung erfolgt automatisiert.
- Klemmenwechsel: Kl.15 AUS, Kl.S AUS, Kl.15 EIN
- FSPE: Fehlerspeichereintrag
- getestet wird stets nach der neuesten Version des Prüfspannungsimpulses
- Die an den Bordnetzklemmen aufgezeichnete Analogspannung lässt sich als Umgebungsvariable darstellen. Dazu muss die Datenbasis aus dem angehängten ZIP Archiv ~Wichtige Zusatzinfos~ zu CAN24 hinzugefügt werden.
Kommentar:
Die sinngemäßen Diagnoseeinträge Unter- bzw. Über-Spannung sowie die Diagnoseeinträge Funktionseinschränkung durch Über- bzw. Unter-Spannung wurden nicht auf die in der Steuergerätespezifikation festgelegten Spannungslevel und Qualifizierungszeiten überprüft. Geprüft wurde die Plausibilität von Diagnoseeinträgen bezogen auf die Spannungslevel der Spannungsereignisse.
[Fault Type]: 0
[Status]: 0
[Creator Contact Person]: WOLLENBERG,MARKO
[Creator Email]: extern.stefan.willmes1@volkswagen.de
[Creator Phone]: +49-162-1027754 [Krishna Kumar Shanmugam(ShanmugK), 04-10-2021 10:33]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
- Faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL are observed during environmental test. These faults are latched when the supply voltage of sensor is below 4.85 V.
- So, the faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL shall be assigned to low voltage fault group.
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [MEB][EBB] Add faults PTS1_NO_SIGNAL, PTS2_NO_SIGNAL and MPS2_NO_SIGNAL to low voltage fault group.
Description:
- Faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL are observed during environmental test. These faults are latched when the supply voltage of sensor is below 4.85 V.
- So, the faults PTS1_NO_SIGNAL,PTS2_NO_SIGNAL and MPS2_NO_SIGNAL shall be assigned to low voltage fault group.
Owner:
Reviewer:
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date:
--------------------------------------------------- | |
[VW KPM] DTC Geber 1 für Bremspedalweg Unterbrechung Retest required
-------------
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar14
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 10428030 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. OpRa: The test was updated based on the developer feedback and the retest is passed.
CR had been analyzed. | [VW KPM] DTC Geber 1 für Bremspedalweg Unterbrechung Retest required
-------------
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar14
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 10428030 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. OpRa: The test was updated based on the developer feedback and the retest is passed.
CR had been analyzed. | |
Issue of SsmPb / AutoApply after IGN-OFF despite that AutoApply is suppressed by EPB-switch Jochen Mohr (01.07.2021):
System under test:
HW: EBC460v1, HOST-App: KJMV21AB_Integ1, PBC-App: X300, Vehicle: MV560ICE (ZACNJCVP4MPR17708), Tester: Marcel Havrda, Reviewer: Jochen Mohr
TestCase:
ID: WU-001
Preconditions:
Vehicle-mode: STATIC / IGN-state: ON / Engine-state: ON / Gradient: 0% / EPB-state: Released / Gear: P
Operations:
Op1: Set and hold EPB-switch in Release position (tested with and without pressed brake pedal)
Op2: Set IGN to OFF
Expected behaviour:
AutoApply is suppressed by EPB-switch (see attached IO-trace with MT "JeepCompass_MT_WU-001.zipx")
Observed behaviour:
If the vehicle has an automatic transmission the AutoApply is performed if EPB-switch is set back into neutral position.
Attachment: JeepCompass_AT_WU-001_with_BrakePedal.zipx, JeepCompass_AT_WU-001_without_BrakePedal.zipx, JeepCompass_MT_WU-001.zipx <Divya Teja Kottakonda> (16.08.21 - 19:59):
--------------------------------------------------------------------------------
Brief investigation comment:
The Apply that is observed when the switch goes to neutral is because of the function AAP_SHIFT_LEVER_NOT_PARK_APPLY.
Dicussed with Arnd Bagusat and decided to disable the function
The below parameter change needs to be done
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Divya Teja>: <Title> / Verifier: <Any>
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [X] or No [] (please mark with an "x")
-------------------------------------------------------------------------------- | Issue of SsmPb / AutoApply after IGN-OFF despite that AutoApply is suppressed by EPB-switch Jochen Mohr (01.07.2021):
System under test:
HW: EBC460v1, HOST-App: KJMV21AB_Integ1, PBC-App: X300, Vehicle: MV560ICE (ZACNJCVP4MPR17708), Tester: Marcel Havrda, Reviewer: Jochen Mohr
TestCase:
ID: WU-001
Preconditions:
Vehicle-mode: STATIC / IGN-state: ON / Engine-state: ON / Gradient: 0% / EPB-state: Released / Gear: P
Operations:
Op1: Set and hold EPB-switch in Release position (tested with and without pressed brake pedal)
Op2: Set IGN to OFF
Expected behaviour:
AutoApply is suppressed by EPB-switch (see attached IO-trace with MT "JeepCompass_MT_WU-001.zipx")
Observed behaviour:
If the vehicle has an automatic transmission the AutoApply is performed if EPB-switch is set back into neutral position.
Attachment: JeepCompass_AT_WU-001_with_BrakePedal.zipx, JeepCompass_AT_WU-001_without_BrakePedal.zipx, JeepCompass_MT_WU-001.zipx <Divya Teja Kottakonda> (16.08.21 - 19:59):
--------------------------------------------------------------------------------
Brief investigation comment:
The Apply that is observed when the switch goes to neutral is because of the function AAP_SHIFT_LEVER_NOT_PARK_APPLY.
Dicussed with Arnd Bagusat and decided to disable the function
The below parameter change needs to be done
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Divya Teja>: <Title> / Verifier: <Any>
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [X] or No [] (please mark with an "x")
-------------------------------------------------------------------------------- | |
[Issue]ZF-PBC-_SsmPbIn._ReleaseInhibit is always set to (Inhibit = 27) [ZalatO][14.07.2021-16:35]:
----------------------------------------
Due to the Inhibition of ReleaseInhibit, EPBi-VW_MQB-48W-SyDesign_3543 Requirement is not Fullfilled
PSM (RLu) (13.07.2021 - 08:14):
--------------------------------------------------------------------------------
please investigate why inhibition is set permanently.
--------------------------------------------------------------------------------
[ZalatO][01.07.2021-11:00]:
----------------------------------------
----------------------------------------
Preconditions:
Vehicle Mode:Static
IGN= ON
Engine = ON
Slope / Gradient = -1%
EPB Status: Applied
Gear:P
Seatbelt:belted
ThrottlePedal = 0%
Car_DriverSeatbelt = Fastened
Car_DriverDoor = Closed
Action Performed:
Release EPB
Expected Result:
SsmPbInReleaseInhibit = 5
Observed Result:
SsmPbInReleaseInhibit = 27 always [Tayfun Ikinci (ikincit), 13.08.2021, 12:39:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
Please do not mix MEB classic and MQB48W
MEB classic
MQB 48W
The expected is not available in this project.
Please recheck, also keep in mind that Door and SeatBelt mapping is/was not working properly
So the observed result 27 means "eSsmPbReleaseNotInhibited = 27" and is therefore NOT the rootcause for the non opening EPB. -> I have updated the CR header accordingly.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
Please recheck on HIL and please also write down your ReleaseTrigger -> I expect it was SwitchRelease -> but did not found it in the description.
Root cause might be the missing driver present due to Door and Belt
Please assign back to HIL / Omar
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
PSM (RLu) (10.08.2021 - 08:06):
--------------------------------------------------------------------------------
It seems that the enumeration codes are wrong in the S/W. The release inhibition is not set to FULLY.
It shall be: ReleaseInhibitFully = ENUM1 = 27
In the S/W: 27 = Not Inhibited. See ALM_Change Request 5409991
--------------------------------------------------------------------------------
PSM (RLu) (05.08.2021 - 13:47):
--------------------------------------------------------------------------------
Below Requirements are from HMS System. The logic of generating a release inhibition signal is not known within EPB system.
But its judged unwanted to have the release inhibition signal always set to = inhibitFully. Especially in this standard testcase.
S/W please analyse why release inhibition is set.
--------------------------------------------------------------------------------
[Tayfun Ikinci (ikincit), 13.07.2021, 08:28:09]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
configuration
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
- here are some requirements listed. @Rene please check if they are complete
- Which requirement is not fulfilled in this testcase / CR?
please assign CR back to Rene to clarify
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
-------------------------------------------------------------------------------- | [Issue]ZF-PBC-_SsmPbIn._ReleaseInhibit is always set to (Inhibit = 27) [ZalatO][14.07.2021-16:35]:
----------------------------------------
Due to the Inhibition of ReleaseInhibit, EPBi-VW_MQB-48W-SyDesign_3543 Requirement is not Fullfilled
PSM (RLu) (13.07.2021 - 08:14):
--------------------------------------------------------------------------------
please investigate why inhibition is set permanently.
--------------------------------------------------------------------------------
[ZalatO][01.07.2021-11:00]:
----------------------------------------
----------------------------------------
Preconditions:
Vehicle Mode:Static
IGN= ON
Engine = ON
Slope / Gradient = -1%
EPB Status: Applied
Gear:P
Seatbelt:belted
ThrottlePedal = 0%
Car_DriverSeatbelt = Fastened
Car_DriverDoor = Closed
Action Performed:
Release EPB
Expected Result:
SsmPbInReleaseInhibit = 5
Observed Result:
SsmPbInReleaseInhibit = 27 always [Tayfun Ikinci (ikincit), 13.08.2021, 12:39:59]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
Please do not mix MEB classic and MQB48W
MEB classic
MQB 48W
The expected is not available in this project.
Please recheck, also keep in mind that Door and SeatBelt mapping is/was not working properly
So the observed result 27 means "eSsmPbReleaseNotInhibited = 27" and is therefore NOT the rootcause for the non opening EPB. -> I have updated the CR header accordingly.
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
Please recheck on HIL and please also write down your ReleaseTrigger -> I expect it was SwitchRelease -> but did not found it in the description.
Root cause might be the missing driver present due to Door and Belt
Please assign back to HIL / Omar
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
--------------------------------------------------------------------------------
PSM (RLu) (10.08.2021 - 08:06):
--------------------------------------------------------------------------------
It seems that the enumeration codes are wrong in the S/W. The release inhibition is not set to FULLY.
It shall be: ReleaseInhibitFully = ENUM1 = 27
In the S/W: 27 = Not Inhibited. See ALM_Change Request 5409991
--------------------------------------------------------------------------------
PSM (RLu) (05.08.2021 - 13:47):
--------------------------------------------------------------------------------
Below Requirements are from HMS System. The logic of generating a release inhibition signal is not known within EPB system.
But its judged unwanted to have the release inhibition signal always set to = inhibitFully. Especially in this standard testcase.
S/W please analyse why release inhibition is set.
--------------------------------------------------------------------------------
[Tayfun Ikinci (ikincit), 13.07.2021, 08:28:09]
--------------------------------------------------------------------------------
Brief investigation comment:
--------------------------------------------------------------------------------
configuration
--------------------------------------------------------------------------------
Proposal of next steps:
--------------------------------------------------------------------------------
- here are some requirements listed. @Rene please check if they are complete
- Which requirement is not fulfilled in this testcase / CR?
please assign CR back to Rene to clarify
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [X] (please mark with an "x")
-------------------------------------------------------------------------------- | |
[Issue]ZF-PBC-_SsmPbIn._ReleaseInhibit is always set to (Inhibit = 27) FI OP to complete remaining Work Products (WPs) left over from FI OP 3196954.
The following WPs need to be done:
SYS.3 Safety - CR 3199040
SYS.3 Safety - CR 4055531
SWE.1 - CR 4473826
SWE.2 - CR 5409964
SWE.3
please refer to the related SwReq and SwArch CRs and implement accordingly. <Sankararao Gudena> (06.08.21 - 07:16):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Route signal ARCfulfilled from vehicle wrapper to a new interface SsmPbOutAdditionalReleaseConditionsFulfilled
2. Remove enum eSsmPbReleaseInhibitInvalid from SsmPbInterface.h.
3. Replace enum eSsmPbReleaseInhibitInvalid with eSsmPbReleaseInhibitNotInhibited in Switch demand interface in DD
4. Remove check for eSsmPbReleaseInhibitNotInhibited in DAA as shown below.
--------------------------------------------------------------------------------
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Sankar>: <Title> / Verifier: <Remove enum ReleaseInhibitInvalid and add new SSM Interface for ARC fulfilled> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | [Issue]ZF-PBC-_SsmPbIn._ReleaseInhibit is always set to (Inhibit = 27) FI OP to complete remaining Work Products (WPs) left over from FI OP 3196954.
The following WPs need to be done:
SYS.3 Safety - CR 3199040
SYS.3 Safety - CR 4055531
SWE.1 - CR 4473826
SWE.2 - CR 5409964
SWE.3
please refer to the related SwReq and SwArch CRs and implement accordingly. <Sankararao Gudena> (06.08.21 - 07:16):
--------------------------------------------------------------------------------
Brief investigation comment:
1. Route signal ARCfulfilled from vehicle wrapper to a new interface SsmPbOutAdditionalReleaseConditionsFulfilled
2. Remove enum eSsmPbReleaseInhibitInvalid from SsmPbInterface.h.
3. Replace enum eSsmPbReleaseInhibitInvalid with eSsmPbReleaseInhibitNotInhibited in Switch demand interface in DD
4. Remove check for eSsmPbReleaseInhibitNotInhibited in DAA as shown below.
--------------------------------------------------------------------------------
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Sankar>: <Title> / Verifier: <Remove enum ReleaseInhibitInvalid and add new SSM Interface for ARC fulfilled> (18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
-------------------------------------------------------------------------------- | |
[VW KPM] DTC Geber 2 für Bremspedalweg Unterbrechung [Error Description]: Beanstandung vom Prüfplatz NV-Fahrzeugrobustheit aus KW27:
Fehlerbeschreibung:
Diagnoseeintrag nach Prüfspannungsimpuls(en):
Display: [P05DB00] PTS2_NO_SIGNAL
Diagnostic: [02101554, 0x201132] Geber 2 für Bremspedalweg Unterbrechung
Vorbedingung:
1. Ubat 13V
2. Kl.15 EIN
3. FSP löschen
4. Klemmenwechsel
5. FSP lesen
Aktion:
1. Klemmenwechsel
2. variable Wartezeit
3. Prüfspannungsimpuls abspielen
4. Klemmenwechsel
5. FSP lesen
erwartetes Ergebnis:
1. kein unberechtigter FSPE nach Prüfspannungsimpuls
2. sämtliche Funktionen des Fahrzeugs sind nach dem Prüfspannungsimpuls wieder hergestellt
Fahrzeug:
VW316820061
bei Impulsen:
E09-001_TF1_Resetverhalten
E09-000_TF2_Resetverhalten
E09-001_TF2_Resetverhalten
E09-001_TF5_Resetverhalten
Dokumente zur Art und zum Verlauf der Impulse befinden sich im angehängten ZIP Archiv ~wichtige Zusatzinfos~.
Tester:
Extern.stefan.willmes1@volkswagen.de
+49-1621027754
Automatisierte Prüfung der Diagnose nach Prüfspannungsimpuls
- Prüfaufbau: Batterie des REALEN FAHRZEUGS wird durch eine externe Spannungsquelle ersetzt, die das Fahrzeug mit dem Prüfspannungsimpuls beaufschlagt. Datenlogger und Diagnose sind am Fahrzeug angeschlossen. Die Klemmensteuerung erfolgt automatisiert.
- Klemmenwechsel: Kl.15 AUS, Kl.S AUS, Kl.15 EIN
- FSPE: Fehlerspeichereintrag
- getestet wird stets nach der neuesten Version des Prüfspannungsimpulses
- Die an den Bordnetzklemmen aufgezeichnete Analogspannung lässt sich als Umgebungsvariable darstellen. Dazu muss die Datenbasis aus dem angehängten ZIP Archiv ~Wichtige Zusatzinfos~ zu CAN24 hinzugefügt werden.
Kommentar:
Die sinngemäßen Diagnoseeinträge Unter- bzw. Über-Spannung sowie die Diagnoseeinträge Funktionseinschränkung durch Über- bzw. Unter-Spannung wurden nicht auf die in der Steuergerätespezifikation festgelegten Spannungslevel und Qualifizierungszeiten überprüft. Geprüft wurde die Plausibilität von Diagnoseeinträgen bezogen auf die Spannungslevel der Spannungsereignisse.
[Fault Type]: 0
[Status]: 0
[Creator Contact Person]: WOLLENBERG,MARKO
[Creator Email]: extern.stefan.willmes1@volkswagen.de
[Creator Phone]: +49-162-1027754 Add fault to FM voltage suppression group, please link task 5753764 to the CR. | [VW KPM] DTC Geber 2 für Bremspedalweg Unterbrechung [Error Description]: Beanstandung vom Prüfplatz NV-Fahrzeugrobustheit aus KW27:
Fehlerbeschreibung:
Diagnoseeintrag nach Prüfspannungsimpuls(en):
Display: [P05DB00] PTS2_NO_SIGNAL
Diagnostic: [02101554, 0x201132] Geber 2 für Bremspedalweg Unterbrechung
Vorbedingung:
1. Ubat 13V
2. Kl.15 EIN
3. FSP löschen
4. Klemmenwechsel
5. FSP lesen
Aktion:
1. Klemmenwechsel
2. variable Wartezeit
3. Prüfspannungsimpuls abspielen
4. Klemmenwechsel
5. FSP lesen
erwartetes Ergebnis:
1. kein unberechtigter FSPE nach Prüfspannungsimpuls
2. sämtliche Funktionen des Fahrzeugs sind nach dem Prüfspannungsimpuls wieder hergestellt
Fahrzeug:
VW316820061
bei Impulsen:
E09-001_TF1_Resetverhalten
E09-000_TF2_Resetverhalten
E09-001_TF2_Resetverhalten
E09-001_TF5_Resetverhalten
Dokumente zur Art und zum Verlauf der Impulse befinden sich im angehängten ZIP Archiv ~wichtige Zusatzinfos~.
Tester:
Extern.stefan.willmes1@volkswagen.de
+49-1621027754
Automatisierte Prüfung der Diagnose nach Prüfspannungsimpuls
- Prüfaufbau: Batterie des REALEN FAHRZEUGS wird durch eine externe Spannungsquelle ersetzt, die das Fahrzeug mit dem Prüfspannungsimpuls beaufschlagt. Datenlogger und Diagnose sind am Fahrzeug angeschlossen. Die Klemmensteuerung erfolgt automatisiert.
- Klemmenwechsel: Kl.15 AUS, Kl.S AUS, Kl.15 EIN
- FSPE: Fehlerspeichereintrag
- getestet wird stets nach der neuesten Version des Prüfspannungsimpulses
- Die an den Bordnetzklemmen aufgezeichnete Analogspannung lässt sich als Umgebungsvariable darstellen. Dazu muss die Datenbasis aus dem angehängten ZIP Archiv ~Wichtige Zusatzinfos~ zu CAN24 hinzugefügt werden.
Kommentar:
Die sinngemäßen Diagnoseeinträge Unter- bzw. Über-Spannung sowie die Diagnoseeinträge Funktionseinschränkung durch Über- bzw. Unter-Spannung wurden nicht auf die in der Steuergerätespezifikation festgelegten Spannungslevel und Qualifizierungszeiten überprüft. Geprüft wurde die Plausibilität von Diagnoseeinträgen bezogen auf die Spannungslevel der Spannungsereignisse.
[Fault Type]: 0
[Status]: 0
[Creator Contact Person]: WOLLENBERG,MARKO
[Creator Email]: extern.stefan.willmes1@volkswagen.de
[Creator Phone]: +49-162-1027754 Add fault to FM voltage suppression group, please link task 5753764 to the CR. | |
[VW KPM] DTC Geber 2 für Bremspedalweg Unterbrechung Retest required
-------------
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar14
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 10428030 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. OpRa: The test was updated based on the developer feedback and the retest is passed.
CR had been analyzed. | [VW KPM] DTC Geber 2 für Bremspedalweg Unterbrechung Retest required
-------------
ECU:: -
Vehicle / Fahrzeug:: Tested on CIAT LabCar14
------------------------------
Preconditions / Ausgangssituation::
Close loop maneuver with vehiclee speed up to 15 kph
Activity / durchgefuhrte Aktion::
The battery voltage is ramp down to 5.9V in order to see the SYSTEM_VOLTAGE_EXCESSIVE_LOW
Expected Behavior / erwartetes Sollverhalten::
EBB_INIT_MPS_FAULT should not be seen.
Actual Behavior / Istverhalten::
When the battery voltage is below 6V the SYSTEM_VOLTAGE_EXCESSIVE_LOW fault is seen and the ebb system state is fully degraded (~CAN1-Tx:Brake->EBKV_03->EBKV_Status_02 = 1). After the battery voltage is reset to 13.5 V the system state switches to init state but the MPS sensors do not calibrate correctly even if there is no other manipulation which can hinder their correct calibration, and after the initialization phase is done, the EBB_INIT_MPS_FAULT is seen and the system state enters in fully degraded state.
Requirement ID not fullfilled / Lastenheft ID nicht erfullt:: No requirement is impacted, the unwanted behavior is seen immediately after the validation of the requirement
Trace / Messung:: TraNet ID: 10428030 Subsystem: SYI_SM3_Full, TC 8
Impact / Einfluss::
MPS sensors do not calibrate correctly after the voltage is ramp down under 6V. OpRa: The test was updated based on the developer feedback and the retest is passed.
CR had been analyzed. | |
[VW KPM] Geber 1 für Bremspedalweg Unterbrechung Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . [Krishna Kumar Shanmugam(ShanmugK), 12-07-2021 14:01]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As per the Architecture input the Senthandler and Motpossensr need to be splitted into QM and ASIL component to fulfill the architecture requirement and safety.
SentHandler: QM component.
- MPS and PTS data storage buffer size 5 and then provide to SentHandlerASIL component(raw frame data from MCAL).
- Do all failure check to derive signal validity. but, not FM fault reporting.
- Provide 1 set of MPS1 and MPS2 data to MotPosnSnsr(QM component).
SentHandlerASIL: ASIL component.
- Read data and extract data from frame. do FM fault reporting.
- Provide 5 set of MPS1 and MPS2 data to to MotPosnSnsrASIL
MotPosnSnsr: QM component
- Get 1 set of MPS1 and MPS2. Motor electric angle is calculated and provided for motor controller.(Same as current implementation)
MotPosnSnsrASIL: ASIL component.
- Get 5 set of MPS1 and MPS2. Motor electric angle is calculated and provided for BHS.
- Now data is read from SentHandler(ASIL) instead of SentHandler(QM)
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split SentHandler component with respect to QM and ASIL C
Description: Refer CR.
Owner: Krishna
Reviewer: Burney
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split MotPosnSnsr component with respect to QM and ASIL C
Description: Refer CR.
Owner: Carsten
Reviewer: Pascal
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Provide new Vector cast environment for ECUAL Team
Description:
Please provide the vector cast environment for below mentioned files, Update the SW_Unit_Test.vcm file.
MotPosnSnsrAsil.c
MotPosnSnsrAsil_Cfg.c
SentHandlerAsil.c
Owner: yessika
Reviewer: Thorsten
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------ | [VW KPM] Geber 1 für Bremspedalweg Unterbrechung Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . [Krishna Kumar Shanmugam(ShanmugK), 12-07-2021 14:01]
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
As per the Architecture input the Senthandler and Motpossensr need to be splitted into QM and ASIL component to fulfill the architecture requirement and safety.
SentHandler: QM component.
- MPS and PTS data storage buffer size 5 and then provide to SentHandlerASIL component(raw frame data from MCAL).
- Do all failure check to derive signal validity. but, not FM fault reporting.
- Provide 1 set of MPS1 and MPS2 data to MotPosnSnsr(QM component).
SentHandlerASIL: ASIL component.
- Read data and extract data from frame. do FM fault reporting.
- Provide 5 set of MPS1 and MPS2 data to to MotPosnSnsrASIL
MotPosnSnsr: QM component
- Get 1 set of MPS1 and MPS2. Motor electric angle is calculated and provided for motor controller.(Same as current implementation)
MotPosnSnsrASIL: ASIL component.
- Get 5 set of MPS1 and MPS2. Motor electric angle is calculated and provided for BHS.
- Now data is read from SentHandler(ASIL) instead of SentHandler(QM)
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split SentHandler component with respect to QM and ASIL C
Description: Refer CR.
Owner: Krishna
Reviewer: Burney
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Split MotPosnSnsr component with respect to QM and ASIL C
Description: Refer CR.
Owner: Carsten
Reviewer: Pascal
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 35 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [ID_BUZZ] [WAVE II] - Provide new Vector cast environment for ECUAL Team
Description:
Please provide the vector cast environment for below mentioned files, Update the SW_Unit_Test.vcm file.
MotPosnSnsrAsil.c
MotPosnSnsrAsil_Cfg.c
SentHandlerAsil.c
Owner: yessika
Reviewer: Thorsten
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
-----------------------------------------------------
Total effort/h: 7 hrs
[Optional] Planned completion date: 16/07/2021
------------------------------------------------------ | |
[VW KPM] Geber 1 für Bremspedalweg Unterbrechung Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . The tasks are completed, all the results are passed, the CR will be closed.
See Tra.NET IDs: 10432846(SWQ_SM5), 10432841(SYI_SM5), 10432841(SYI_Read_Sens)
RTCL updated, Test run 17 | [VW KPM] Geber 1 für Bremspedalweg Unterbrechung Currently SentHandler is mapped to QM partition. but, need to fulfill ASIL C safety requirements because reading the Sensor value itself need to be QM accessible and failsafe related to the data read need to be present in ASIL C.
Further, SentHandler shall be splited into two components,
QM component: Reading of Sensor values.
ASIL C component: Failsafe mechanisms . The tasks are completed, all the results are passed, the CR will be closed.
See Tra.NET IDs: 10432846(SWQ_SM5), 10432841(SYI_SM5), 10432841(SYI_Read_Sens)
RTCL updated, Test run 17 | |
[ASIL_C/D][SYS.5][ASIL C][GA02] S_VEHICLE_SPEED_QF transiton from "VALID" to "NOT VALID" too long Dummy CR. Dummy CR | [ASIL_C/D][SYS.5][ASIL C][GA02] S_VEHICLE_SPEED_QF transiton from "VALID" to "NOT VALID" too long Dummy CR. Dummy CR | |
Takeover OP 5165631 - DTC-C16602F can't raised when conditions met at GAC side This CR is Created to Reject the Open Points.Project is cancelled, refer mail attachement.
In case Project is resume, need to re open all OP's attached to this CR The Attached OP's need to fixed once the project is resumed. Rejecting OP for sake of Process and project cancellation. | Takeover OP 5165631 - DTC-C16602F can't raised when conditions met at GAC side This CR is Created to Reject the Open Points.Project is cancelled, refer mail attachement.
In case Project is resume, need to re open all OP's attached to this CR The Attached OP's need to fixed once the project is resumed. Rejecting OP for sake of Process and project cancellation. | |
Padwear adjust applies both but releases only one actuator Date 7/30/21
Description of issue or needed change Pad wear adjust applies both but releases only one actuator.
Test Environment (SIL,HIL,VEH) SIL test case: SIL -700-028-PBC_MSC_PAD_ADJUSTMENT_START_RELEASED
Software level X042
Software Module if known Demand_State.c
Requirement Pad wear Adjust should apply and then release all available actuators.
DataFile
Note/Screenshot
PTC Reference EPB System CCB - JAS - 08.03.21:Please investigate this point and advise the next steps. | Padwear adjust applies both but releases only one actuator Date 7/30/21
Description of issue or needed change Pad wear adjust applies both but releases only one actuator.
Test Environment (SIL,HIL,VEH) SIL test case: SIL -700-028-PBC_MSC_PAD_ADJUSTMENT_START_RELEASED
Software level X042
Software Module if known Demand_State.c
Requirement Pad wear Adjust should apply and then release all available actuators.
DataFile
Note/Screenshot
PTC Reference EPB System CCB - JAS - 08.03.21:Please investigate this point and advise the next steps. | |
Takeover OP 5165768 - GAC complains DID F18C no value Most of the GAC A12 OP's are already fixed/ analyzed for Gx16. THis CR is created to map new OP which are created in place of GAC A12. THis is just for Process purpose and proper OP tracking.
The OP's are fixed in some other CR , that reference can be found in OPlist. For GAC A12 to Gx16 OP mapping refer description of OP. It contains the related GAC OP number.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/BaoNeng/GX16%5fBD%5fEPS/PR56556%5fLVS%5fENG%5fAPP%5fBaoNeng%5fGX16%5fEPS%5fBD%5fSYS%5fHroom%5fAP/30%5fSoftware/3000%5fManagement&selection=%223000%5fSW%5fOpen%5fIssue%5fList.xlsx%22 Approved | Takeover OP 5165768 - GAC complains DID F18C no value Most of the GAC A12 OP's are already fixed/ analyzed for Gx16. THis CR is created to map new OP which are created in place of GAC A12. THis is just for Process purpose and proper OP tracking.
The OP's are fixed in some other CR , that reference can be found in OPlist. For GAC A12 to Gx16 OP mapping refer description of OP. It contains the related GAC OP number.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/BaoNeng/GX16%5fBD%5fEPS/PR56556%5fLVS%5fENG%5fAPP%5fBaoNeng%5fGX16%5fEPS%5fBD%5fSYS%5fHroom%5fAP/30%5fSoftware/3000%5fManagement&selection=%223000%5fSW%5fOpen%5fIssue%5fList.xlsx%22 Approved | |
Takeover OP 5353260 - FT : GAC_A18 : Test 8.23.7 Test for DID $F10B is supported to be read out with service $22 Most of the GAC A12 OP's are already fixed/ analyzed for Gx16. THis CR is created to map new OP which are created in place of GAC A12. THis is just for Process purpose and proper OP tracking.
The OP's are fixed in some other CR , that reference can be found in OPlist. For GAC A12 to Gx16 OP mapping refer description of OP. It contains the related GAC OP number.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/BaoNeng/GX16%5fBD%5fEPS/PR56556%5fLVS%5fENG%5fAPP%5fBaoNeng%5fGX16%5fEPS%5fBD%5fSYS%5fHroom%5fAP/30%5fSoftware/3000%5fManagement&selection=%223000%5fSW%5fOpen%5fIssue%5fList.xlsx%22 Approved | Takeover OP 5353260 - FT : GAC_A18 : Test 8.23.7 Test for DID $F10B is supported to be read out with service $22 Most of the GAC A12 OP's are already fixed/ analyzed for Gx16. THis CR is created to map new OP which are created in place of GAC A12. THis is just for Process purpose and proper OP tracking.
The OP's are fixed in some other CR , that reference can be found in OPlist. For GAC A12 to Gx16 OP mapping refer description of OP. It contains the related GAC OP number.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=%23/Steering%23Projects/BaoNeng/GX16%5fBD%5fEPS/PR56556%5fLVS%5fENG%5fAPP%5fBaoNeng%5fGX16%5fEPS%5fBD%5fSYS%5fHroom%5fAP/30%5fSoftware/3000%5fManagement&selection=%223000%5fSW%5fOpen%5fIssue%5fList.xlsx%22 Approved | |
Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing See linked OP for details:1) Sensor/Actuators NVM Application - To update application NVM/FEE map (removal of new blocks and revert back to the old FMM blocks with original names) Revert Nvram_Cfg checkpoint back to Mem_Nvram_Cfg_MY22_GM_BT1XX_LD_IBC_Global_B_1.19. | Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing See linked OP for details:1) Sensor/Actuators NVM Application - To update application NVM/FEE map (removal of new blocks and revert back to the old FMM blocks with original names) Revert Nvram_Cfg checkpoint back to Mem_Nvram_Cfg_MY22_GM_BT1XX_LD_IBC_Global_B_1.19. | |
Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing Issue Description:
GM has found that some of the ECUs with the latest V21 software is setting CPU_FAILURE_SEVERITY_TRANSIENT fault is being set. It was because the block CPU_ALARM_FAULT_INFO is reading all "0". Upon further investigation and taking a DFALSH dump of the faulty ECU, it has been found that CPU_ALARM_FAULT_INFO block along with ROLLS_TEST_MODE mode are not present in the FEE.
Root Cause:
The Root cause has found to be that the number of Fee blocks that are configured in App (419) is more than that are configured in Boot (388). So, when garbage collection happens in Boot ( GC might happen in Boot if it is interrupted in App previously), only the 388 blocks configured plus the 10 of the remaining unconfigured blocks( i.e. blocks that are configured in App but not in Boot) are copied to the new sector and the remaining unconfigured blocks will be erased.
Proposed fix:
The proposed fix is to revert the additional blocks that were added in V21 (V20 has 397 blocks) to bring down the number of Fee blocks to 397.
Note: Even though V20 has 397 blocks ( which is greater that the Boot which has 388), all of them will be copied if GC happens in Boot because the number of unconfigured blocks in Boot will be less than 10 ( 397 - 388).
See linked OP for details
2) MCAL - to Update NVM/FEE map in the MCAL (removal of new blocks and revert back to the old FMM blocks with original names) Revert back the App MCAL to 397 blocks. McalCfg checkpoint 1.2.1.35.2.15.2.69.2.17 is where the additional FMM blocks are added which brought the total number of block to 419. So, we need to revert back this checkpoint to 1.2.1.35.2.15.2.69.2.16 which has 397 blocks. | Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing Issue Description:
GM has found that some of the ECUs with the latest V21 software is setting CPU_FAILURE_SEVERITY_TRANSIENT fault is being set. It was because the block CPU_ALARM_FAULT_INFO is reading all "0". Upon further investigation and taking a DFALSH dump of the faulty ECU, it has been found that CPU_ALARM_FAULT_INFO block along with ROLLS_TEST_MODE mode are not present in the FEE.
Root Cause:
The Root cause has found to be that the number of Fee blocks that are configured in App (419) is more than that are configured in Boot (388). So, when garbage collection happens in Boot ( GC might happen in Boot if it is interrupted in App previously), only the 388 blocks configured plus the 10 of the remaining unconfigured blocks( i.e. blocks that are configured in App but not in Boot) are copied to the new sector and the remaining unconfigured blocks will be erased.
Proposed fix:
The proposed fix is to revert the additional blocks that were added in V21 (V20 has 397 blocks) to bring down the number of Fee blocks to 397.
Note: Even though V20 has 397 blocks ( which is greater that the Boot which has 388), all of them will be copied if GC happens in Boot because the number of unconfigured blocks in Boot will be less than 10 ( 397 - 388).
See linked OP for details
2) MCAL - to Update NVM/FEE map in the MCAL (removal of new blocks and revert back to the old FMM blocks with original names) Revert back the App MCAL to 397 blocks. McalCfg checkpoint 1.2.1.35.2.15.2.69.2.17 is where the additional FMM blocks are added which brought the total number of block to 419. So, we need to revert back this checkpoint to 1.2.1.35.2.15.2.69.2.16 which has 397 blocks. | |
Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing See linked OP for details.
3) NVM Autosar team - Update Autosar NVM/FEE information (removal of new blocks and revert back to the old FMM blocks with original names) Vidya Sgar D [03-July-2021] :
--------------------------------------------------------------------------------
Aim of CR : FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data
--------------------------------------------------------------------------------
Input to Start : BSW_BswAutocore_Vector_GM_BT1XX_1.90 check-point is used
-------------------------------------------------------------------------------
Issue Description:
GM has found that some of the ECUs with the latest V21 software is setting CPU_FAILURE_SEVERITY_TRANSIENT fault is being set. It was because the block CPU_ALARM_FAULT_INFO is reading all "0". Upon further investigation and taking a DFALSH dump of the faulty ECU, it has been found that CPU_ALARM_FAULT_INFO block along with ROLLS_TEST_MODE mode are not present in the FEE.
Root Cause:
The Root cause has found to be that the number of Fee blocks that are configured in App (419) is more than that are configured in Boot (388). So, when garbage collection happens in Boot ( GC might happen in Boot if it is interrupted in App previously), only the 388 blocks configured plus the 10 of the remaining unconfigured blocks( i.e. blocks that are configured in App but not in Boot) are copied to the new sector and the remaining unconfigured blocks will be erased.
So the OP 5570237 was created to fix this issue.
Solution :
As per CR description and analysis, We need to revert the 5421748 task's changes with following configuration in AUTOSAR NvM & Fee modules.
a. Remove below FMM1.1 blocks from NvM configuration and Keep the previous FMM blocks as it is matching to Autosar_NvM_Config.arxml (1.21)
- FMM Data 0
- FMM Data 1
- FMM Data 2
- FMM Data 3
- FMM Data 4
- FMM Data 5
- FMM Data 6
- FMM Data 7
- FMM Data 8
- FMM Data 9
- FMM Data 10
- FMM Data 11
- FMM Extended Fault 0
- FMM Extended Fault 1
- FMM Extended Fault 2
- FMM Extended Fault 3
- FMM Extended Fault 4
- FMM Expanded Fault 0
- FMM Expanded Fault 1
- FMM Expanded Fault 2
- FMM Expanded Fault 3
- FMM Expanded Fault 4
--------------------------------------------------------------------------------------------------------------------------------------------
Proposal of next steps: Please create a Task
--------------------------------------------------------------------------------------------------------------------------------------------
Task : BTxx : BswAutocore: Revert the NvM Configuration to remove the FMM1.1 blocks added as per task 5421748
--------------------------------------------------------------------------------------------------------------------------------------------
Configure the AUTOSAR Fee & NVM Module as per the Solution Proposed in the CR Analysis comments.
Work Products:
---------------------------
- Autosar Fee & NvM modules shall be configured for rename and removal of NvM blocks by reverting the Configuration to 1.21 check-point of Autosar_Nvm_Config.arxml file.
- Verify configuration for any unresolved errors w.r.t NvM blocks rename and remove.
- Validate and Generate the Configuration for Fee & NvM blocks updates.
- After the successful generation, verify the generated NvM Config code files. The generated files must match to the Autosar NvM Generated files of BswAutocore check-point 1.87.
Test Procedure:
---------------------------
1. As the CR is to rever the changes to the previous working version of the NvM, we would not need to perform a specific test at the developer work bench.
2. For the verification of changes functionality, Perform Read / Write and then Read Operation of the FMM Blocks.
3. Ensure to perform Shutdown and Read the blocks at the startup of the ECU after shutdown.
Acceptance Criteria:
--------------------------------
- Updated BswAutocore (Autosar) modules shall not be having any generation errors.
- No other Changes apart from Fee & NvM shall be configured. Unchanged modules should remain same with Base Work package.
- Genereted files must be compiled and should not cause any errors.
- Changes of the Modified/added NvM blocks must be Tested and a Test Report to be attached to the Task/CR.
- CG3000 doc: No need of CG3000 for this CR since we are reverting the configuration and no new changes are introduced.
--------------------------------------------------------------------------------------------------------------------------------------------
Task Owner: Vidya Sagar D
Reviewer: Li Rui
Estimated Design effort/h: 0h
Esitimated implementation effort/h:6h
Estimated unit testing effort/h: 1h
-------------------------------------------------------------
Total effort/h: 7h
------------------------------------------------------------- | Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing See linked OP for details.
3) NVM Autosar team - Update Autosar NVM/FEE information (removal of new blocks and revert back to the old FMM blocks with original names) Vidya Sgar D [03-July-2021] :
--------------------------------------------------------------------------------
Aim of CR : FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data
--------------------------------------------------------------------------------
Input to Start : BSW_BswAutocore_Vector_GM_BT1XX_1.90 check-point is used
-------------------------------------------------------------------------------
Issue Description:
GM has found that some of the ECUs with the latest V21 software is setting CPU_FAILURE_SEVERITY_TRANSIENT fault is being set. It was because the block CPU_ALARM_FAULT_INFO is reading all "0". Upon further investigation and taking a DFALSH dump of the faulty ECU, it has been found that CPU_ALARM_FAULT_INFO block along with ROLLS_TEST_MODE mode are not present in the FEE.
Root Cause:
The Root cause has found to be that the number of Fee blocks that are configured in App (419) is more than that are configured in Boot (388). So, when garbage collection happens in Boot ( GC might happen in Boot if it is interrupted in App previously), only the 388 blocks configured plus the 10 of the remaining unconfigured blocks( i.e. blocks that are configured in App but not in Boot) are copied to the new sector and the remaining unconfigured blocks will be erased.
So the OP 5570237 was created to fix this issue.
Solution :
As per CR description and analysis, We need to revert the 5421748 task's changes with following configuration in AUTOSAR NvM & Fee modules.
a. Remove below FMM1.1 blocks from NvM configuration and Keep the previous FMM blocks as it is matching to Autosar_NvM_Config.arxml (1.21)
- FMM Data 0
- FMM Data 1
- FMM Data 2
- FMM Data 3
- FMM Data 4
- FMM Data 5
- FMM Data 6
- FMM Data 7
- FMM Data 8
- FMM Data 9
- FMM Data 10
- FMM Data 11
- FMM Extended Fault 0
- FMM Extended Fault 1
- FMM Extended Fault 2
- FMM Extended Fault 3
- FMM Extended Fault 4
- FMM Expanded Fault 0
- FMM Expanded Fault 1
- FMM Expanded Fault 2
- FMM Expanded Fault 3
- FMM Expanded Fault 4
--------------------------------------------------------------------------------------------------------------------------------------------
Proposal of next steps: Please create a Task
--------------------------------------------------------------------------------------------------------------------------------------------
Task : BTxx : BswAutocore: Revert the NvM Configuration to remove the FMM1.1 blocks added as per task 5421748
--------------------------------------------------------------------------------------------------------------------------------------------
Configure the AUTOSAR Fee & NVM Module as per the Solution Proposed in the CR Analysis comments.
Work Products:
---------------------------
- Autosar Fee & NvM modules shall be configured for rename and removal of NvM blocks by reverting the Configuration to 1.21 check-point of Autosar_Nvm_Config.arxml file.
- Verify configuration for any unresolved errors w.r.t NvM blocks rename and remove.
- Validate and Generate the Configuration for Fee & NvM blocks updates.
- After the successful generation, verify the generated NvM Config code files. The generated files must match to the Autosar NvM Generated files of BswAutocore check-point 1.87.
Test Procedure:
---------------------------
1. As the CR is to rever the changes to the previous working version of the NvM, we would not need to perform a specific test at the developer work bench.
2. For the verification of changes functionality, Perform Read / Write and then Read Operation of the FMM Blocks.
3. Ensure to perform Shutdown and Read the blocks at the startup of the ECU after shutdown.
Acceptance Criteria:
--------------------------------
- Updated BswAutocore (Autosar) modules shall not be having any generation errors.
- No other Changes apart from Fee & NvM shall be configured. Unchanged modules should remain same with Base Work package.
- Genereted files must be compiled and should not cause any errors.
- Changes of the Modified/added NvM blocks must be Tested and a Test Report to be attached to the Task/CR.
- CG3000 doc: No need of CG3000 for this CR since we are reverting the configuration and no new changes are introduced.
--------------------------------------------------------------------------------------------------------------------------------------------
Task Owner: Vidya Sagar D
Reviewer: Li Rui
Estimated Design effort/h: 0h
Esitimated implementation effort/h:6h
Estimated unit testing effort/h: 1h
-------------------------------------------------------------
Total effort/h: 7h
------------------------------------------------------------- | |
Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing 4) FMM - To back out changes to FMM back to the usage of 2 bit FMM data with the original block names.
FM checkpoint is reverted from 1.87.1.19.1.14 with FMM1.1 implementation to 1.87.1.19.1.13 without FMM1.1 implementation. No other changes are missed in reverting the checkpoint Rejecting CR since task is not needed. Changes are provided by reverting checkpoint. | Lead - Short term solution - FEE Memory Lost caused by mismatch between Boot and Application Max number of blocks impacts several features using FEE data found on / during customer testing 4) FMM - To back out changes to FMM back to the usage of 2 bit FMM data with the original block names.
FM checkpoint is reverted from 1.87.1.19.1.14 with FMM1.1 implementation to 1.87.1.19.1.13 without FMM1.1 implementation. No other changes are missed in reverting the checkpoint Rejecting CR since task is not needed. Changes are provided by reverting checkpoint. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Below mentioned "Regenerative Management" related signals, in which few are implemented and few are covered(pending) in other CRs. Corresponding CRs information mentioned below:
CAN1 Tx:
Message IDSignal GroupSignalImplemented StatusTask Reference
0x101BRAKE1ABSActiveYesTask -5032953
0x101BRAKE1Brake_MaxRegen_ReadyNew
0x101BRAKE1ESCActiveYesTask -5032953
0x418BRAKE7ASRActiveyesTask - 5644644
0x4AFBRAKE8ABSFailStsyesTask - 5497632
0x4AFBRAKE8ESCFailStsyesTask - 5678440
0x4AFBRAKE8RollsModeActYesTask - 5678440
CAN2 Tx:
Signal GroupSignalImplemented StatusTask Reference
BRAKE1ABSActiveYesTask -5032953
BRAKE1ESCActiveYesTask -5032953
BRAKE7ASRActiveyesTask - 5644644
BRAKE8ABSFailStsyesTask - 5497632
BRAKE8ESCFailStsYesTask - 5678440
BRAKE8RollsModeActYesTask - 5678440
HY_BRAKERegenBrkAxTorqReqstPendingCR - 5717686
CAN1 Rx:
Message IDSignal GroupSignalImplemented StatusSWCR Reference Task Reference
0xFABCM_COMMANDCmdIgn_FailStsYesSW2CR - 5368092Task - 5497597
0xFABCM_COMMANDCmdIgnStsYesSWCR - 4993032Task -5032953
0xFCENGINE1GasPedalPositionyesSW3CR - 5368096Task - 5677925
0xFCENGINE1GasPedalPositionFailStsyesSW3CR - 5368096Task - 5677925
0x36EHCP_DISPHVBatSOC_HCPYesSW3CR - 5624237Task - 5678501
0x36EHCP_DISPHVBatSOCV_HCPNew
0x73ATIME_DATEDay1New
0x73ATIME_DATEDay2New
0x73ATIME_DATEHour1New
0x73ATIME_DATEHour2New
0x73ATIME_DATEMinute1New
0x73ATIME_DATEMinute2New
0x73ATIME_DATEMonth1New
0x73ATIME_DATEMonth2New
0x73ATIME_DATEYear1New
0x73ATIME_DATEYear2New
0x73ATIME_DATEYear3New
0x73ATIME_DATEYear4New
0x5A8TRANSM2ShiftLeverPositionyesSW3CR - 5368096Task - 5677925
CAN2 Rx:
Signal GroupSignalImplemented StatusCR Reference
AXLE_TORQUE_BSMEstRegenBrkAxTorqPendingCR - 5677945
AXLE_TORQUE_BSMMaxRegenDiffTorque_ActivePendingCR - 5677945
AXLE_TORQUE_BSMMaxRegenDiffTorque_AxlePendingCR - 5677945
ENGINE1GasPedalPositionyesCR - 5368096
ENGINE1GasPedalPositionFailStsyesCR - 5368096
HYBRID1FrontAxleTrqEstPendingCR - 5677945
TRANSM2ShiftLeverPositionyesCR - 5368096
In the above signals list, in which the signals "Implemented Status" mentioned as "New" need to be implemented as part of this CR. Mahendar Reddy [7th Octo 2021]:
-------------------------------------------------------------------------------
Brief analysis summary:.
--------------------------------------------------------------------------------
The below signals need to be implemented as part of this CR.
ChannalSignal GroupSignalTx/Rx
CAN1BRAKE1Brake_MaxRegen_ReadyTx
CAN1HCP_DISPHVBatSOCV_HCPRx
CAN1TIME_DATEDay1Rx
CAN1TIME_DATEDay2Rx
CAN1TIME_DATEHour1Rx
CAN1TIME_DATEHour2Rx
CAN1TIME_DATEMinute1Rx
CAN1TIME_DATEMinute2Rx
CAN1TIME_DATEMonth1Rx
CAN1TIME_DATEMonth2Rx
CAN1TIME_DATEYear1Rx
CAN1TIME_DATEYear2Rx
CAN1TIME_DATEYear3Rx
CAN1TIME_DATEYear4Rx
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale: .
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahendar Reddy
Proposal of next steps (incl. effort/h and verification): Task need to be created. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Below mentioned "Regenerative Management" related signals, in which few are implemented and few are covered(pending) in other CRs. Corresponding CRs information mentioned below:
CAN1 Tx:
Message IDSignal GroupSignalImplemented StatusTask Reference
0x101BRAKE1ABSActiveYesTask -5032953
0x101BRAKE1Brake_MaxRegen_ReadyNew
0x101BRAKE1ESCActiveYesTask -5032953
0x418BRAKE7ASRActiveyesTask - 5644644
0x4AFBRAKE8ABSFailStsyesTask - 5497632
0x4AFBRAKE8ESCFailStsyesTask - 5678440
0x4AFBRAKE8RollsModeActYesTask - 5678440
CAN2 Tx:
Signal GroupSignalImplemented StatusTask Reference
BRAKE1ABSActiveYesTask -5032953
BRAKE1ESCActiveYesTask -5032953
BRAKE7ASRActiveyesTask - 5644644
BRAKE8ABSFailStsyesTask - 5497632
BRAKE8ESCFailStsYesTask - 5678440
BRAKE8RollsModeActYesTask - 5678440
HY_BRAKERegenBrkAxTorqReqstPendingCR - 5717686
CAN1 Rx:
Message IDSignal GroupSignalImplemented StatusSWCR Reference Task Reference
0xFABCM_COMMANDCmdIgn_FailStsYesSW2CR - 5368092Task - 5497597
0xFABCM_COMMANDCmdIgnStsYesSWCR - 4993032Task -5032953
0xFCENGINE1GasPedalPositionyesSW3CR - 5368096Task - 5677925
0xFCENGINE1GasPedalPositionFailStsyesSW3CR - 5368096Task - 5677925
0x36EHCP_DISPHVBatSOC_HCPYesSW3CR - 5624237Task - 5678501
0x36EHCP_DISPHVBatSOCV_HCPNew
0x73ATIME_DATEDay1New
0x73ATIME_DATEDay2New
0x73ATIME_DATEHour1New
0x73ATIME_DATEHour2New
0x73ATIME_DATEMinute1New
0x73ATIME_DATEMinute2New
0x73ATIME_DATEMonth1New
0x73ATIME_DATEMonth2New
0x73ATIME_DATEYear1New
0x73ATIME_DATEYear2New
0x73ATIME_DATEYear3New
0x73ATIME_DATEYear4New
0x5A8TRANSM2ShiftLeverPositionyesSW3CR - 5368096Task - 5677925
CAN2 Rx:
Signal GroupSignalImplemented StatusCR Reference
AXLE_TORQUE_BSMEstRegenBrkAxTorqPendingCR - 5677945
AXLE_TORQUE_BSMMaxRegenDiffTorque_ActivePendingCR - 5677945
AXLE_TORQUE_BSMMaxRegenDiffTorque_AxlePendingCR - 5677945
ENGINE1GasPedalPositionyesCR - 5368096
ENGINE1GasPedalPositionFailStsyesCR - 5368096
HYBRID1FrontAxleTrqEstPendingCR - 5677945
TRANSM2ShiftLeverPositionyesCR - 5368096
In the above signals list, in which the signals "Implemented Status" mentioned as "New" need to be implemented as part of this CR. Mahendar Reddy [7th Octo 2021]:
-------------------------------------------------------------------------------
Brief analysis summary:.
--------------------------------------------------------------------------------
The below signals need to be implemented as part of this CR.
ChannalSignal GroupSignalTx/Rx
CAN1BRAKE1Brake_MaxRegen_ReadyTx
CAN1HCP_DISPHVBatSOCV_HCPRx
CAN1TIME_DATEDay1Rx
CAN1TIME_DATEDay2Rx
CAN1TIME_DATEHour1Rx
CAN1TIME_DATEHour2Rx
CAN1TIME_DATEMinute1Rx
CAN1TIME_DATEMinute2Rx
CAN1TIME_DATEMonth1Rx
CAN1TIME_DATEMonth2Rx
CAN1TIME_DATEYear1Rx
CAN1TIME_DATEYear2Rx
CAN1TIME_DATEYear3Rx
CAN1TIME_DATEYear4Rx
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale: .
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Mahendar Reddy
Proposal of next steps (incl. effort/h and verification): Task need to be created. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative AXLE_TORQUE_BSM.EstRegenBrkAxTorq signal received on CAN1 and corresponding interface "U16 GetEstRegenBrkAxTorq(void)" is provided by comms as part of task - 5843610.
As per the requirement, process Renegenerative Braking based on input interface "U16 GetEstRegenBrkAxTorq(void)".
Attached the requeremen document "VF378_V1_R1_637_RegenerativeManagement.docx". PAVAN KISHORE [11-03-2022]:
As per analysis with 'ARBORIO NICOLA' following changes needs to be performed in code
The above changes needs to performed in 'Rb_Input.c' file. Same file needs to be updated as per CR '5911318'. Hence same task has been linked to both CR '5911318' & '5911269'.
Respective Mail from 'Nicola' is attached to the CR.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Daniel Raj(z0009255) - 23-Dec-21
----------------------------------------------------
As per VF378_V1_R1[Regenerative Management], Strategy Requirements.
AxleTorqueBsm.EstRegenBrkAxTorq -> Is used to calculate the current hydraulic braking needed.
Hybrid1.FrontAxleTrqEst -> Is used to calculate the repartition of braking.
Singal Hybrid1.FrontAxleTrqEst is already being used by RB as pointed below through interface GetRegenTorqAchieved.
Signal AxleTorqueBsm.EstRegenBrkAxTorq is implemented by COMMS recently(Can be accessed through the interface GetEstRegenBrkAxTorq())
This CR is created to notify RB to take care of the required implementation on their side.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No change in RB subsystem needed. Standard interface to be provided from COMMS. Team assignment changed.
Reason for change request not understood and given information not sufficient.
Typically and also in WL regen torque feedback is received via the standard interface GetRegenTorqAchieved() with corresponding input validation INPUT_VALID_EST_REGEN_TORQ like this:
/**
read actual axle recu brake torque
*/
if (IsInputValid(INPUT_VALID_EST_REGEN_TORQ) != FALSE)
{
RbIn.v.Flg.VehRecuTrqVal_b1 = TRUE;
RbIn.VehRecuTrq_s16 = (S16)GetRegenTorqAchieved();
}
else
{
RbIn.v.Flg.VehRecuTrqVal_b1 = FALSE;
RbIn.VehRecuTrq_s16 = 0;
}
RbIn.VehRecuTrq_s16 = -RbIn.VehRecuTrq_s16;
In case of CAN changes the new/changed CAN signal must be received and provided via the given standard interface including corresponding input validation. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative AXLE_TORQUE_BSM.EstRegenBrkAxTorq signal received on CAN1 and corresponding interface "U16 GetEstRegenBrkAxTorq(void)" is provided by comms as part of task - 5843610.
As per the requirement, process Renegenerative Braking based on input interface "U16 GetEstRegenBrkAxTorq(void)".
Attached the requeremen document "VF378_V1_R1_637_RegenerativeManagement.docx". PAVAN KISHORE [11-03-2022]:
As per analysis with 'ARBORIO NICOLA' following changes needs to be performed in code
The above changes needs to performed in 'Rb_Input.c' file. Same file needs to be updated as per CR '5911318'. Hence same task has been linked to both CR '5911318' & '5911269'.
Respective Mail from 'Nicola' is attached to the CR.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Daniel Raj(z0009255) - 23-Dec-21
----------------------------------------------------
As per VF378_V1_R1[Regenerative Management], Strategy Requirements.
AxleTorqueBsm.EstRegenBrkAxTorq -> Is used to calculate the current hydraulic braking needed.
Hybrid1.FrontAxleTrqEst -> Is used to calculate the repartition of braking.
Singal Hybrid1.FrontAxleTrqEst is already being used by RB as pointed below through interface GetRegenTorqAchieved.
Signal AxleTorqueBsm.EstRegenBrkAxTorq is implemented by COMMS recently(Can be accessed through the interface GetEstRegenBrkAxTorq())
This CR is created to notify RB to take care of the required implementation on their side.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No change in RB subsystem needed. Standard interface to be provided from COMMS. Team assignment changed.
Reason for change request not understood and given information not sufficient.
Typically and also in WL regen torque feedback is received via the standard interface GetRegenTorqAchieved() with corresponding input validation INPUT_VALID_EST_REGEN_TORQ like this:
/**
read actual axle recu brake torque
*/
if (IsInputValid(INPUT_VALID_EST_REGEN_TORQ) != FALSE)
{
RbIn.v.Flg.VehRecuTrqVal_b1 = TRUE;
RbIn.VehRecuTrq_s16 = (S16)GetRegenTorqAchieved();
}
else
{
RbIn.v.Flg.VehRecuTrqVal_b1 = FALSE;
RbIn.VehRecuTrq_s16 = 0;
}
RbIn.VehRecuTrq_s16 = -RbIn.VehRecuTrq_s16;
In case of CAN changes the new/changed CAN signal must be received and provided via the given standard interface including corresponding input validation. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Requirements are mentioned as below captured from attached requirement document "VF378_V1_R1_637_RegenerativeManagement.docx".
Refer the attached requirement document for details. The RB analysis is done against the existing CHR WL codebase and the potential software updates have been identified.
The analysis is attached to the CR as an excel sheet. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Requirements are mentioned as below captured from attached requirement document "VF378_V1_R1_637_RegenerativeManagement.docx".
Refer the attached requirement document for details. The RB analysis is done against the existing CHR WL codebase and the potential software updates have been identified.
The analysis is attached to the CR as an excel sheet. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Implement "RBMDriveModeEnable" status as per the requirement and below is the captured requirement. Attached the requirement document "VFS_BSM_P637BEV.doc" for reference. [Lokendra Pavan Kumar Pappala, 18.08.2022]:
- STLA removed the dependency of RBMDriveModeEnable on regenerative braking.
- Hence, this CR can be rejected.
- Please refer to the email attachment 'R No RB off in case of ASR OFF switch.msg'
[Lokendra Pavan Kumar Pappala, 13.07.2022]:
- Need more clarification from Stellantis, please check the email from Arborio Nicola attached.
- This CR can be moved to x410.
[Lokendra Pavan Kumar Pappala, 23.06.2022]:
- Local implementation complete
- Need more clarification from Stellantis, please check the email from Arborio Nicola attached.
- This CR can be moved to x400. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Implement "RBMDriveModeEnable" status as per the requirement and below is the captured requirement. Attached the requirement document "VFS_BSM_P637BEV.doc" for reference. [Lokendra Pavan Kumar Pappala, 18.08.2022]:
- STLA removed the dependency of RBMDriveModeEnable on regenerative braking.
- Hence, this CR can be rejected.
- Please refer to the email attachment 'R No RB off in case of ASR OFF switch.msg'
[Lokendra Pavan Kumar Pappala, 13.07.2022]:
- Need more clarification from Stellantis, please check the email from Arborio Nicola attached.
- This CR can be moved to x410.
[Lokendra Pavan Kumar Pappala, 23.06.2022]:
- Local implementation complete
- Need more clarification from Stellantis, please check the email from Arborio Nicola attached.
- This CR can be moved to x400. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative [Fiat Ducato]:[DIAG] Update of 0X2A09 Regen Brake Status
The below is the DBC path:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/00%5fFrom%5fCustomer/05%5fRequirements/1A%5fspec%5fBSM%5f140502021/BSM%20%2d%20Braking%20System%20Module/NW%20%2d%20Network%20Requirements/CAN%20Networks/project.pj
CAN1-Interface Sheet:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/01%5fRequirements/01%5fOEM%5fVM/COMMS%5fInterface/project.pj&selection=%22COMMS%5fInterface%5fP637BEV%5fE1A%5fR1%5fC1CAN.xlsx%22
Refer the attached "C1_CAN_Rx_SW3" and "C2_CAN_Rx_SW3" documents and implement the signals mentioned in the document as part of this CR.
CAN2.Hybrid1.RegenBrkAxTorqCap should also be implemented with this CR. [Rajat Kumar, 01.11.2021]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--> Diagnostic Changes will taken care in ReadDataByIdentifier_cfg.c file .
--> Replace old interface "GetRegenTorqCap()" with new interface "U16 GetReGenBrkAxTorqCap(void)" in Diag function ReadRegenBrakeStatus.
/*Regen Torque Capability*/
-->Before used Comms interface:-- torque_request = GetRegenTorqCap();
-->Now using Comms interface -- torque_request = GetReGenBrkAxTorqCap();
-->USED CheckPoint: 1.3.1.30 for Analysis .
--------------------------------------------------------------------------------
Risk (low/medium/high): Medium
As this is related to ReadDataByIdentifier_cfg.c
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rajat Kumar
Proposal of next steps (incl. effort/h and verification): Please create below task
--------------------------------------------------------------------------------
TASK_1:
--------------------------------------------------------------------------------
Title:- [Fiat Ducato]:[DIAG] Update of 0x2A09 regen Brake Status
Description:-
Please refer the CR analysis.
Owner: Rajat Kumar
Reviewer: Baburao
Estimated design effort/h: 6hrs
Estimated unit testing effort/h: 2hrs
------------------------------------------------------
Total effort/h: 8hrs
[Optional] Planned completion date: NA. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative [Fiat Ducato]:[DIAG] Update of 0X2A09 Regen Brake Status
The below is the DBC path:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewproject?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/00%5fFrom%5fCustomer/05%5fRequirements/1A%5fspec%5fBSM%5f140502021/BSM%20%2d%20Braking%20System%20Module/NW%20%2d%20Network%20Requirements/CAN%20Networks/project.pj
CAN1-Interface Sheet:
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/IBC/Customer/Fiat/Ducato%5fBEV%5fMY2024%2d25/01%5fRequirements/01%5fOEM%5fVM/COMMS%5fInterface/project.pj&selection=%22COMMS%5fInterface%5fP637BEV%5fE1A%5fR1%5fC1CAN.xlsx%22
Refer the attached "C1_CAN_Rx_SW3" and "C2_CAN_Rx_SW3" documents and implement the signals mentioned in the document as part of this CR.
CAN2.Hybrid1.RegenBrkAxTorqCap should also be implemented with this CR. [Rajat Kumar, 01.11.2021]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
--> Diagnostic Changes will taken care in ReadDataByIdentifier_cfg.c file .
--> Replace old interface "GetRegenTorqCap()" with new interface "U16 GetReGenBrkAxTorqCap(void)" in Diag function ReadRegenBrakeStatus.
/*Regen Torque Capability*/
-->Before used Comms interface:-- torque_request = GetRegenTorqCap();
-->Now using Comms interface -- torque_request = GetReGenBrkAxTorqCap();
-->USED CheckPoint: 1.3.1.30 for Analysis .
--------------------------------------------------------------------------------
Risk (low/medium/high): Medium
As this is related to ReadDataByIdentifier_cfg.c
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rajat Kumar
Proposal of next steps (incl. effort/h and verification): Please create below task
--------------------------------------------------------------------------------
TASK_1:
--------------------------------------------------------------------------------
Title:- [Fiat Ducato]:[DIAG] Update of 0x2A09 regen Brake Status
Description:-
Please refer the CR analysis.
Owner: Rajat Kumar
Reviewer: Baburao
Estimated design effort/h: 6hrs
Estimated unit testing effort/h: 2hrs
------------------------------------------------------
Total effort/h: 8hrs
[Optional] Planned completion date: NA. | |
[Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Implement "IgnOffExpTime" and provide interface, as per the requirement and below is the captured requirement. Attached the requirement document "VFS_BSM_P637BEV.doc" for reference. Daniel Raj(z0009255) - 23-Mar-22
Update the file CustServices.ini with the newly added IgnitionOffExpTime folder details.
----------------------------------------------------------------------------------------------------------------------------------------------
Sirisha.M [1st, Mar 2022]:
-------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Analyzed Impelementation of IgnOffExpTime as per 1A Spec requirements and Made a document with all the analyzed points and
Attached that document in CR for reference.
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale:
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Sirisha.M
Proposal of next steps (incl. effort/h and verification): Task need to be created. | [Fiat_Ducato_BEV_IBC_637]:[Mule:CAT-3][VF378_V1_R1]- Regenerative Management - Overlay Regenerative Implement "IgnOffExpTime" and provide interface, as per the requirement and below is the captured requirement. Attached the requirement document "VFS_BSM_P637BEV.doc" for reference. Daniel Raj(z0009255) - 23-Mar-22
Update the file CustServices.ini with the newly added IgnitionOffExpTime folder details.
----------------------------------------------------------------------------------------------------------------------------------------------
Sirisha.M [1st, Mar 2022]:
-------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Analyzed Impelementation of IgnOffExpTime as per 1A Spec requirements and Made a document with all the analyzed points and
Attached that document in CR for reference.
--------------------------------------------------------------------------------
Risk (low/medium/high) with rationale:
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Sirisha.M
Proposal of next steps (incl. effort/h and verification): Task need to be created. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.