instruction
stringlengths 29
35k
| input
stringclasses 1
value | output
stringlengths 29
35k
|
---|---|---|
C1+ CV01 - Open phase faults during vehicle integration D2 -- Problem Description (R: PRE):
During Vehicle integration, open phase faults have been observed
Requirement which is violated (R: Originator):
Expected behavior (R: Originator):
Operating Environment (R: Originator):
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
n/a
D4a -- Verified Root Cause (R: PRE):
Open phase faults: Current control tune parameters incorrect (no EPP current control tuning performed)
D4b -- Verified Escape Point (R: PRE):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
PCA:
Current control tune to be performed after Dyno4 is operational in BVP
D7 -- Lessons Learned (R: PRE): The solution was proposed in the attachment and consists in the current controller gain increase, as they were incorrect. The current controller parameters have been updated in the .par file at the end of July. So far, the issue has not been seen again.
The following parameters have been updated:
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap
More details in the attached message. | C1+ CV01 - Open phase faults during vehicle integration D2 -- Problem Description (R: PRE):
During Vehicle integration, open phase faults have been observed
Requirement which is violated (R: Originator):
Expected behavior (R: Originator):
Operating Environment (R: Originator):
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
n/a
D4a -- Verified Root Cause (R: PRE):
Open phase faults: Current control tune parameters incorrect (no EPP current control tuning performed)
D4b -- Verified Escape Point (R: PRE):
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
PCA:
Current control tune to be performed after Dyno4 is operational in BVP
D7 -- Lessons Learned (R: PRE): The solution was proposed in the attachment and consists in the current controller gain increase, as they were incorrect. The current controller parameters have been updated in the .par file at the end of July. So far, the issue has not been seen again.
The following parameters have been updated:
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMap
MotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap
More details in the attached message. |
|
[Opel K0][Requirement] - Drop and replace SSM_PB related modules SWPM - SKO (21.07.21 - 13:47)
--------------------------------------------------------------------------------
Brief investigation comment:
After latest branch from VW it is identified that some of SSM_PB related modules need to be updated as shown below:
Drop and replace the yellow highlighted modules?
Instead the following modules shall be shared from BrkSW – POOL into the PSA k0
1.3 of
And
-------------------------------------------------------------------------------- Brief analysis summary:
-----------------------
Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.
------------------------------------------------------------------------------
TASK
------------------------------------------------------------------------------
Drop the Ssm_Pbi and SsmPbWrp components from the below Repository location path
/SCS#Customer/PSA/K0/05_Software/VIEW_Mainline/MMC_APPL/MMC_APPL_SW/Application/EPBi/project.pj
Share Ssm_Pbi & SsmPbWrp from BrkSW repository location
/BrkSw/SwDevelopmentPool/Software/Components/Ssm_Pbi/project.pj- Checkpoint 1.9.2.1
/BrkSw/SwDevelopmentPool/Software/Components/SsmPbWrp/project.pj- Checkpoint 1.3
Acceptance criteria:
-----------------------------
After sharing the new sub components verify the compilation check.
Owner: Sravan Kumar Akoju
Reviewer: Mehta Jay
Estimated design effort/h: 1hr
Estimated implementation effort/h: 3hr
Estimated unit testing effort/h: 0 | [Opel K0][Requirement] - Drop and replace SSM_PB related modules SWPM - SKO (21.07.21 - 13:47)
--------------------------------------------------------------------------------
Brief investigation comment:
After latest branch from VW it is identified that some of SSM_PB related modules need to be updated as shown below:
Drop and replace the yellow highlighted modules?
Instead the following modules shall be shared from BrkSW – POOL into the PSA k0
1.3 of
And
-------------------------------------------------------------------------------- Brief analysis summary:
-----------------------
Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.
------------------------------------------------------------------------------
TASK
------------------------------------------------------------------------------
Drop the Ssm_Pbi and SsmPbWrp components from the below Repository location path
/SCS#Customer/PSA/K0/05_Software/VIEW_Mainline/MMC_APPL/MMC_APPL_SW/Application/EPBi/project.pj
Share Ssm_Pbi & SsmPbWrp from BrkSW repository location
/BrkSw/SwDevelopmentPool/Software/Components/Ssm_Pbi/project.pj- Checkpoint 1.9.2.1
/BrkSw/SwDevelopmentPool/Software/Components/SsmPbWrp/project.pj- Checkpoint 1.3
Acceptance criteria:
-----------------------------
After sharing the new sub components verify the compilation check.
Owner: Sravan Kumar Akoju
Reviewer: Mehta Jay
Estimated design effort/h: 1hr
Estimated implementation effort/h: 3hr
Estimated unit testing effort/h: 0 |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Conclusion taken over from spawned CR with first change regarding this topic: [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird mit der 2. Task eingecheckt => Task 5705543
[04.10.2021], E. Webert:
- Unklar, ob die Änderung das Problem löst
- laut weiteren Analysen kommt es zu einem nicht gewünschten Verhalten aufgrund einer Logik im ARB (MAX-Bildung bei SSM?)
- Man sollte versuchen es vorher im ARB zu lösen, dann kann dieses CR rejectet werden
- auf Feedback warten
[04.11.2021], E. Webert:
- vg. Mail im Anhang: AW_ noch offene OP-Bewertung für die anstehende CAT5.msg
- laut CASE soll für MEB Classic erstmal keine Lösung erfolgen
- für UN ECE soll es neue bewertet werden => teilweise gibt es Lösungsvorschläge für einen Fix im ARB => Mail im Anhang: WG Analyse Anregungen nach HBB.msg
- Punkt wird rejectet | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Conclusion taken over from spawned CR with first change regarding this topic: [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird mit der 2. Task eingecheckt => Task 5705543
[04.10.2021], E. Webert:
- Unklar, ob die Änderung das Problem löst
- laut weiteren Analysen kommt es zu einem nicht gewünschten Verhalten aufgrund einer Logik im ARB (MAX-Bildung bei SSM?)
- Man sollte versuchen es vorher im ARB zu lösen, dann kann dieses CR rejectet werden
- auf Feedback warten
[04.11.2021], E. Webert:
- vg. Mail im Anhang: AW_ noch offene OP-Bewertung für die anstehende CAT5.msg
- laut CASE soll für MEB Classic erstmal keine Lösung erfolgen
- für UN ECE soll es neue bewertet werden => teilweise gibt es Lösungsvorschläge für einen Fix im ARB => Mail im Anhang: WG Analyse Anregungen nach HBB.msg
- Punkt wird rejectet |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird nach erfolgreichem Test mit einem weiteren CR eingecheckt: 5732889 | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- [31.08.2021], E. Webert:
- Soll dieses Änderung noch für den MEB Classic erfolgen? Ja, sonst sind Kundenbeanstandungen zu erwarten (Pedalrückwirkungen)
- Für welche SW? Geplant für X523 => Wann ist die X523?
- Frage aus dem CCB mit VW: Tritt es auch bei anderen Boost-Funktionen oder der HVV (Hinterachsvollverzögerung) auf? Sollte man auch bei weiteren Funktionen Pedalkraftkompensation abschalten?
- HVV heißt bei uns RAxB (vgl. Mail im Anhang AW_ OP 5532680 - _0521__CASE__VW_MEB41x_SCS_MCP oscillations cause HBA exit and HBA triggering_CBecker.msg)
- Wir gucken auf den ARB-Mode BRK_CTRL_ARB_BRAKE_ASSIST und dieser Mode deckt nicht nur HBA ab, sondern alle HBX-Funktionen (HBA, HBB, DBK, RAxB, RAB [Prefill])
- Heißt wir brauchen keine weiteren Ausnahmen.
[13.09.2021], E. Webert:
- es muss eine weitere Ausnahme erfolgen
- vgl. dazu CR 5703695 - RB: Pedalflattern im Stillstand (HBA und PFC im Stillstand)
- die Logik wird nach erfolgreichem Test mit einem weiteren CR eingecheckt: 5732889 |
|
[0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Test can be done by CASE | [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering Preconditions / Ausgangsituation:
Vehicle: AERO / ID.Buzz054 / ID.Buzz089
SW SCS: M521 /b521
SW EBB: 657-002 / b651
Maneuver name: HBA
--------------------------------------------------------------------------------
Actions / Aktionen:
1. HBA triggering
2. xxx
3. xxx
4. xxx
5. xxx
--------------------------------------------------------------------------------
Expected Behavior / erwartetes Sollverhalten:
HBA should stay active / HBA should not become active without driver intent
--------------------------------------------------------------------------------
Actual Behavior / Istverhalten:
2021-07-01_AERO_009_248.MDF
2021-07-13_ID.BUZZ054_299.MDF
--> HBA exit (DEACT9) due to MCP oscillations
2021-07-20_ID.BUZZ089_299.MDF
--> HBA triggered again without driver intent (caused by MCP oscillaions)
Oscillations are also seen in analog pressure measurement circuit 1 and 2
--------------------------------------------------------------------------------
Requirement ID not fullfilled (if known)/ Lastenheft ID nicht erfuellt (wenn bekannt):
xxx
--------------------------------------------------------------------------------
Impact / Einfluss:
xxx
-------------------------------------------------------------------------------- Test can be done by CASE |
|
HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activity Description:
With the outcome from W130j as Impact Analysis results on SWE1 per one clustered change from this release and one build, the change impacted features and behaviors identified and determined, SW Requriement Project Manager arrange Feature manager or Funciton Developers to Generate SW Requriements by following below Task scope and ZF procedures and steps:
(Notes: Due to specific change may derives tailored activities from Impact Analysis on below full activity scope, therefore the actual activities tailor status of the Task to be described by Task Responsible in this Task Notes area, per Review activity description, it need performed in connected review Task Conclusion area due to the main Task Notes area can't be updated while in Reivew phase)
Task Scope:
Feature:
Behavior:
Process following:
1. Develop Behaviour Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
1.1 Write SW Requirements with bleow sub steps which follows C_066_3_SSE_025_EN Write SW Requirements Work Instruction:
3.1. Processing Collected Software Requirements
3.2. Manage Requirements and Traceability
3.3. Software Requirements Style
3.4. Handling of software requirement sources
3.5. Handling of Signals and Parameters for software requirements
3.6. Handling of Attributes for software requirements
Attributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes
1.2 ?Assign SW Releases for SW Requirements with below sub steps which follows C_066_3_SSE_020_EN Assign SW Releases for SW Requirements Work Instruction:
3.1. Add SW release to a requirement
3.2. Removing a SW release from a requirement
3.3. Maintaining requirements assigned to multiple SW releases – functional change
3.4. Maintaining requirements assigned to multiple SW releases – no functional change
3.5. Maintaining requirements assigned to multiple SW releases – bug fix
2. Review Software Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
Organise a Software Requirements Review performed with below sub steps and follows C_066_3_SSE_029_EN Organise a Software Requirements Review Work Instruction:
3.1. Organize a formal software requirements review
3.1.1. Prepare the review of software requirements
3.1.2. Perform technical and formal review
3.1.3. Organize Review by stakeholder
3.1.4. Stakeholder Review
3.1.5. Finalize SW Requirements review
3.2. Organize an informal software requirements review
4. Review invitation
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. Impact Analysis
6. SW engineering traceability matrix
?
Output of this WP:
1. SW Requirement
2. SW Requirement Baseline
3. FSF Manual (Updates)
Responsible: SW Feature Manager, SW FM Developer
Support: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ? Change to Analysed | HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activity Description:
With the outcome from W130j as Impact Analysis results on SWE1 per one clustered change from this release and one build, the change impacted features and behaviors identified and determined, SW Requriement Project Manager arrange Feature manager or Funciton Developers to Generate SW Requriements by following below Task scope and ZF procedures and steps:
(Notes: Due to specific change may derives tailored activities from Impact Analysis on below full activity scope, therefore the actual activities tailor status of the Task to be described by Task Responsible in this Task Notes area, per Review activity description, it need performed in connected review Task Conclusion area due to the main Task Notes area can't be updated while in Reivew phase)
Task Scope:
Feature:
Behavior:
Process following:
1. Develop Behaviour Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
1.1 Write SW Requirements with bleow sub steps which follows C_066_3_SSE_025_EN Write SW Requirements Work Instruction:
3.1. Processing Collected Software Requirements
3.2. Manage Requirements and Traceability
3.3. Software Requirements Style
3.4. Handling of software requirement sources
3.5. Handling of Signals and Parameters for software requirements
3.6. Handling of Attributes for software requirements
Attributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes
1.2 ?Assign SW Releases for SW Requirements with below sub steps which follows C_066_3_SSE_020_EN Assign SW Releases for SW Requirements Work Instruction:
3.1. Add SW release to a requirement
3.2. Removing a SW release from a requirement
3.3. Maintaining requirements assigned to multiple SW releases – functional change
3.4. Maintaining requirements assigned to multiple SW releases – no functional change
3.5. Maintaining requirements assigned to multiple SW releases – bug fix
2. Review Software Requirements (C_066_2_SSE_002_EN_SoftwareRequirementsAnalysis defines general)
Organise a Software Requirements Review performed with below sub steps and follows C_066_3_SSE_029_EN Organise a Software Requirements Review Work Instruction:
3.1. Organize a formal software requirements review
3.1.1. Prepare the review of software requirements
3.1.2. Perform technical and formal review
3.1.3. Organize Review by stakeholder
3.1.4. Stakeholder Review
3.1.5. Finalize SW Requirements review
3.2. Organize an informal software requirements review
4. Review invitation
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. Impact Analysis
6. SW engineering traceability matrix
?
Output of this WP:
1. SW Requirement
2. SW Requirement Baseline
3. FSF Manual (Updates)
Responsible: SW Feature Manager, SW FM Developer
Support: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ? Change to Analysed |
|
[Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply Preconditions:Init with Fully released actuators. Close to Parkapplied, Set PbcIn.HostavailabilityRl/Rr/Both = None OR Relase OR Apply.
Action:Set Wheespeed to 3 km/h or perform a parkapply
Expected Behaviour: Good side perform a RAR.Bad side MotorCommad not move to any state.
Actual behaviour: Good side perform a RAR. bad side set PbcOut.MotorCommad = Apply(Stop/None one for cycle, and set PbcOut.ActuatorState to ePbcActuatorStateUnknown
11/1/21: Analzed by Lubbers with changes made to Design Document.
Further Information: Same behaviour with undervoltage and parkapply. Only left side try to start an actuation. This behaviour seems to be strange.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. | [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply Preconditions:Init with Fully released actuators. Close to Parkapplied, Set PbcIn.HostavailabilityRl/Rr/Both = None OR Relase OR Apply.
Action:Set Wheespeed to 3 km/h or perform a parkapply
Expected Behaviour: Good side perform a RAR.Bad side MotorCommad not move to any state.
Actual behaviour: Good side perform a RAR. bad side set PbcOut.MotorCommad = Apply(Stop/None one for cycle, and set PbcOut.ActuatorState to ePbcActuatorStateUnknown
11/1/21: Analzed by Lubbers with changes made to Design Document.
Further Information: Same behaviour with undervoltage and parkapply. Only left side try to start an actuation. This behaviour seems to be strange.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. |
|
[Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity Preconditions: Init with Fully released actuators.
Action: Apply or Release, Set PbcInHostavailability to apply if acatuation is in apply direction or release if actuation is in release direction.
Expected Behaviour: Actuation is finished
Actual behaviour: Actuation stops and affected actuator is unknown
Further Information/Requirements: If actuation is possible shall not stop..
Please see attachment
1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document. EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. | [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity Preconditions: Init with Fully released actuators.
Action: Apply or Release, Set PbcInHostavailability to apply if acatuation is in apply direction or release if actuation is in release direction.
Expected Behaviour: Actuation is finished
Actual behaviour: Actuation stops and affected actuator is unknown
Further Information/Requirements: If actuation is possible shall not stop..
Please see attachment
1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document. EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps. |
|
[Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h Preconditions:Precondition for RAR
Action:Set all speeds >= 15 km/h
Expected Behaviour: No RAR perfomed
Actual behaviour: RAR is performed
Further Information/Requirements: This threshold of 15km/h is the limit of RAR,because of HSB Vehicle safety speed. Maybe the HSB from Host will not enable the applyline and this will lead an internal fault. See VDA Chapter 3.1.2 HOST Safety Barrier
Investigate possible difference between host and PBC ref speed calculation.
SIL Test -130-304-PBC_RAR_BY_WHEEL_SPEED_15_KMH
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
12/02/21: Change Implemented per associated task. | [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h Preconditions:Precondition for RAR
Action:Set all speeds >= 15 km/h
Expected Behaviour: No RAR perfomed
Actual behaviour: RAR is performed
Further Information/Requirements: This threshold of 15km/h is the limit of RAR,because of HSB Vehicle safety speed. Maybe the HSB from Host will not enable the applyline and this will lead an internal fault. See VDA Chapter 3.1.2 HOST Safety Barrier
Investigate possible difference between host and PBC ref speed calculation.
SIL Test -130-304-PBC_RAR_BY_WHEEL_SPEED_15_KMH
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
12/02/21: Change Implemented per associated task. |
|
[Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early Preconditions: Init with Fully released actuators.
Action:Apply Release under several condition.
Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNone
Actual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleased
Further Information/Requirements: This can lead to a lock of software. In the past we made the experience that the Host system calls PBC.Cyclic as long as PbcOut.EcuPowerLatchRequest = ePbcPowerLatchRequested and if this signal depends on the actuatorstate it can happen that the PbcMotoCommands stays at ePbcMotorCommandStop.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
11/9/21: mrb Per Design Board review, this requirement is NOT necessary. (ML) | [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early Preconditions: Init with Fully released actuators.
Action:Apply Release under several condition.
Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNone
Actual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleased
Further Information/Requirements: This can lead to a lock of software. In the past we made the experience that the Host system calls PBC.Cyclic as long as PbcOut.EcuPowerLatchRequest = ePbcPowerLatchRequested and if this signal depends on the actuatorstate it can happen that the PbcMotoCommands stays at ePbcMotorCommandStop.
Please see attachment EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.
11/9/21: mrb Per Design Board review, this requirement is NOT necessary. (ML) |
|
[Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected When trying o connect CANApe with generated
DA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured.
Please analys and implment necessary Changes in A2l [26.08.2021, ScafesA]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The issue appear for the A2L generated in the SW version X200. In the X200 it was a issue and the information in the A2Ls have been incomplete and wrong and could cause errors with the VX1000 connection.
That Issue is confirmed that have been solved starting with SW version X250 with CR 5528764.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Alexandru Scafes
Proposal of next steps (incl. effort/h and verification): Retest if the VX 1000 connection is corrected and if the errors is still present on SW version X250 or newer.
-------------------------------------------------------------------------------- | [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected When trying o connect CANApe with generated
DA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured.
Please analys and implment necessary Changes in A2l [26.08.2021, ScafesA]--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The issue appear for the A2L generated in the SW version X200. In the X200 it was a issue and the information in the A2Ls have been incomplete and wrong and could cause errors with the VX1000 connection.
That Issue is confirmed that have been solved starting with SW version X250 with CR 5528764.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Alexandru Scafes
Proposal of next steps (incl. effort/h and verification): Retest if the VX 1000 connection is corrected and if the errors is still present on SW version X250 or newer.
-------------------------------------------------------------------------------- |
|
[VW KPM] [SV][BL][CAN] F1AB nach CheckMemory [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):
FLASH_TEST_Gutfall
Kommentar Prüfer:
Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert.
[A: 80126-A119]
[A: 80126-A694]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 F1 AB
Response (39): 62 F1 AB 58 33 32 35 58 33 32 33 41 30 30 32 44 45 4D 4F 49 58 30 35 41 30 30 36 41 30 30 31 42 30 30 31 42 30 30 31
00000 (TEST): Block 1 Typ: Writable [DATA]. Die Software Block Version hat sich vor dem CheckMemory aktualisiert. --> n.i.O.
00000 (TEST): Typ: Writable [DATA]. Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert oder es wurde bereits vor dem CheckMemory gemacht. --> n.i.O.
zugehörige Dateien:
Gutfall_2021-06-21_15-16-27_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]:
*********************
Developer comment:
In SW Module apnv.c - ApplFblNvWriteBlockStates the invalidation of the block is not taking place. Needs to be corrected. Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not Implemented
Description:
· Add NVRAM Block state write to invalidation of logical block
Proposed Tests:
· Check if block is invalid after erasing
Estimated design effort/h: 1
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 1
Total effort/h: 3
[Optional] Planned completion date: | [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):
FLASH_TEST_Gutfall
Kommentar Prüfer:
Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert.
[A: 80126-A119]
[A: 80126-A694]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 F1 AB
Response (39): 62 F1 AB 58 33 32 35 58 33 32 33 41 30 30 32 44 45 4D 4F 49 58 30 35 41 30 30 36 41 30 30 31 42 30 30 31 42 30 30 31
00000 (TEST): Block 1 Typ: Writable [DATA]. Die Software Block Version hat sich vor dem CheckMemory aktualisiert. --> n.i.O.
00000 (TEST): Typ: Writable [DATA]. Es hat sich trotz CheckMemory keiner der Software Block Versionen aktualisiert oder es wurde bereits vor dem CheckMemory gemacht. --> n.i.O.
zugehörige Dateien:
Gutfall_2021-06-21_15-16-27_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]:
*********************
Developer comment:
In SW Module apnv.c - ApplFblNvWriteBlockStates the invalidation of the block is not taking place. Needs to be corrected. Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not Implemented
Description:
· Add NVRAM Block state write to invalidation of logical block
Proposed Tests:
· Check if block is invalid after erasing
Estimated design effort/h: 1
Estimated implementation effort/h: 1
Estimated unit testing effort/h: 1
Total effort/h: 3
[Optional] Planned completion date: |
|
[VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF Perform an analysis for the issue below and suggest the next steps.
---------------------------------------------------------------------------------------------------------------------------
[Error Description]: Kontaktdaten:
E-Mail: VWAG R: WOB, EESN Sys-VQ
Beanstandung vom Sys-VQ-Prüfplatz
PMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):
Aktivierung aller Produktionsmodes in erlaubter Session
Kommentar Prüfer:
Der P-Mode wird durch die Parameter 0xFF FF FF nicht aktiviert. Gemäß der Spezifikation muss der P-Mode aktiviert werden, da mit Parameter 0xFF FF FF alle Bits gesetzt sind.
[A: Q-LAH_PMode-9]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 04 FE
Response (6): 62 04 FE 00 00 00
00000 (TEST): Der Identifier 04 FE wurde mit 0x62 04 FE 00 00 00 beantwortet.
Erwartet: != 00 00 00. --> n.i.O.
zugehörige Dateien:
TC_PMode_00_01_0_040_010_2021-06-21_15-04-28_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]: 05.08.2021 BoianD: This topic is related to Base Software (Diag / Chasinf). OBD / SiSo has nothing to do with the triggering of the production mode. | [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF Perform an analysis for the issue below and suggest the next steps.
---------------------------------------------------------------------------------------------------------------------------
[Error Description]: Kontaktdaten:
E-Mail: VWAG R: WOB, EESN Sys-VQ
Beanstandung vom Sys-VQ-Prüfplatz
PMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):
Aktivierung aller Produktionsmodes in erlaubter Session
Kommentar Prüfer:
Der P-Mode wird durch die Parameter 0xFF FF FF nicht aktiviert. Gemäß der Spezifikation muss der P-Mode aktiviert werden, da mit Parameter 0xFF FF FF alle Bits gesetzt sind.
[A: Q-LAH_PMode-9]
Fehler-Beschreibung DANTE:
00000 (DIAG): Diagnose - RequestPDU (3): 22 04 FE
Response (6): 62 04 FE 00 00 00
00000 (TEST): Der Identifier 04 FE wurde mit 0x62 04 FE 00 00 00 beantwortet.
Erwartet: != 00 00 00. --> n.i.O.
zugehörige Dateien:
TC_PMode_00_01_0_040_010_2021-06-21_15-04-28_CAN_Diagnose.asc
[Fault Type]: 0
[Creator Contact Person]: Koch, Sven
[Creator Email]: extern.nils.krueger@volkswagen.de
[Creator Phone]: 05.08.2021 BoianD: This topic is related to Base Software (Diag / Chasinf). OBD / SiSo has nothing to do with the triggering of the production mode. |
|
[Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented This CR shall be used to implement the following diagnostic jobs:
1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz
2. PreCheckProgrammingDependencies - StartRoutine: $31 01 02 07 zz
Information:
- The behavior of the routines is specified in the CDD but it must be checked whether further relevant customer requirements are specified in other specifications + DOORS modules.
- The CR shall cover SWE1, SWE2, SWE3 and SWE4.
- The CR has not be derived from BROP and/or DCRP but has been requested by the customer to be implemented for B1.1 (= X0150). Please, refer to the attached Excel Sheet "MMA_Diag_EffortEstimation_basedOn_v2.5_PlanningStatus_2021-04-08.xlsx" that is exchanged with the customer.
To Diag CCB:
- Please, add owner from Diag team.
- Please, add analysers from Diag team and SwAD team. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
19.05.2021 WeyandC:
Routine 0x0203 "Check Reprogramming Preconditions" is not specified in DOORS module "EBS_Diagnostic_Requirements_Specification". But the routines is specified by the CDD and by specification "DDS R01-01".
It is no longer requested by the customer that routine 0x0207 "PreCheckProgrammingDependencies" is supported by the application. This is why follow-up ALM_Change Request 5198683 has been or will be rejected.
Purpose of the CR:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified and have been discussed with the customer:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the CR must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
DIAG part:
1. Adapt SWC Diag
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml.
2. implementation of routine 0x0203 "Check Reprogramming Preconditions":
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
3. Diag framework adaptations:
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE and OS.
NOTE:
1. SWC-Diag will call the following Autosar interfaces:
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&brake_ctrl_active);
- (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&drive_ctrl_active);
The ports are still connected from Geely / VW (= baseline for the MMA project). No actions are required.
The Autosar interfaces can be used from SwAD / Autosar point of view. Please, refer to the attached email "AW_ ALM_Change Request 5136349_ _MMA__X0150__Diag_ Implement _Programming Check_ routines.msg" for details.
2. Diag Design:
- It was decided for this routine that Dcm configuration is not manually adapted in DaVinci Configurator. The multiple in and out parameters are NOT replaced with a single in- and a single out-parameter. Hence, the DiagArAdapter routine runnable must copy data from the multiple in-parameters to the single generic Diag in-parameter and vice versa from the single Diag generic out-parameter to the multiple out-parameters.
- It was also decided that stack variables (= function variables) will be used as the additional stack consumption is negligible.
- For the future, it will be check whether the Dcm configuration will be manually adapted in DaVinci Configurator for new routines or whether shared Diag RAM variables shall be used to copy data between parameters defined by Autosar and generic Diag parameters.
=> Both decision will not affect the implementation of routine 0x0203 that is provided with this CR.
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via Teams
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine: 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable for the routine to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavaraju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 26.05.2021 (set by task owner)
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
The following DIDs routine be implemented with this CR:
Routine 0x0203 "Check Reprogramming Preconditions" with sub function $01 "StartRoutine" is specified by the CDD and by specification "DDS R01-01".
Functionality:
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future. Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
Refer to the attached emails for further details.
Please, use this CR to define SW requirements for this routine.
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 26.05.2021
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement routine 0x0203 "Check Reprogramming Preconditions".
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl framework
Description:
Purpose of the task:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the task must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
General:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
Details:
1. Adapt SWC Diag:
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml
2. Framework adaptations:
DiagArAdapter:
- Adapt the interface GenericStartRoutineInterface:
- new parameter list: const U16 test_id, const U8 *input_parameters, U8 *const output_parameters, const U8 param_length, U16 * const out_param_length, Dcm_NegativeResponseCodeType *ErrorCode
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericStopRoutineInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericASyncShortTermAdjustmentInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
TestGroup:
- Adapt the interface CommandTest:
- new parameter list: const U16 comms_id, const U8 test_type, const BOOLEAN command, const U8* const parameters, U8* const output_data, const U16 length, U16* const out_length
- add a new block after the "Execute Command" block and before the "Update Group Status block":
- check if "status" is TST_STATUS_OK and "out_length" is not NULL; if so call interface "ExecuteGetCommandDataInterface" and store the return value via "out_length" pointer
- Add new type definition in the global header file for function pointer to retrieve the response parameters for start routine service request: typedef U16 (*GET_COMMAND_TEST_DATA_TYPE)(U8* results)
TestSpecification:
- Add new function U16 ExecuteGetCommandDataInterface(const U32 test_id, U8 results_buffer[]) with subsystem scope
- the function shall check whether "GetCommandTestDataInterface" is not NULL for the given "test_id"
- if so, it shall return the length returned by the respective "GetCommandTestDataInterface" interface.
- otherwise, it shall return 0 as length.
- Adapt definition of data type TEST_SPEC_DATA_TYPE:
- add new paramter "GET_COMMAND_TEST_DATA_TYPE GetCommandTestDataInterface" behind the "Get_Result_Data_Inteface" parameter
InputOutputControlById.c:
- non functional adaptation to make the SW compile:
- adapt the calls of function "CommandTest" in function "IoControlByIdentifier" to make the SW compile
- pass NULL for the new parameters of "CommandTest"
3. Implementation of routine 0x0203:
DiagArAdapter_cfg:
- Implement the new runnable "RoutineServices_Check_Reprogramming_Preconditions_Start":
- define stack variables:
- for 2nd parameter of CommandTest: const U8 start_routine_in_signals = 0u
- for 3rd parameter of CommandTest (=> it is expected that a size of 8 bytes will be sufficient => currently a size of 2 bytes would be ok): U8 start_routine_out_signals[DIAG_PRGR_PRECND_MAX_DYN_LENGTH]
- for 5th parameter of CommandTest: U16 data_length_out = 0u
- OpStatus == DCM_initial:
- call CommandTest with the listed parameters and with 1st parameter = PROG_PRECOND_CHECK_TEST_ID, with 4th parameter = 0 and with ErrorCode as 6th parameter
- if returned data_length_out is less than minimal response length (= 2) or greater than minimal response legnth + size of array "start_routine_out_signals":
- call UpdateTestManagementActive(FALSE)
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
- otherwise:
- copy data from "start_routine_out_signals" to actual out parameters "routineInfo_Out", "Number_of_Unfulfilled_Preconditions_Out", "List_of_Preconditions_Out" and set "DataLength" to the correct value
- return E_OK
- OpStatus == DCM_CANCEL:
- call UpdateTestManagementActive(FALSE)
- return E_OK
- OpStatus has another value:
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
TestSpecification_Cfg:
- Adapt ROM table Test_Spec_Data: replace dummy entry with entry for routine 0x0203:
{
&CommandChkPrgrPrecnd,
&UpdateChkPrgrPrecnd,
NULL,
NULL,
&ReportChkPrgrPrecndCommandData,
PROG_PRECOND_CHECK_TEST_ID,
ROUTINE_BY_ID_TEST,
EXCLUSIVE_TEST_GROUP,
SECURITY_ACCESS_NOT_REQUIRED,
PARAM_LENGTH_ZERO,
(U8)IOC_NO_CHECK_REQUIRED
}
RoutineControl_Cfg:
1. Implement Command_Interface with subsystem scope: CommandChkPrgrPrecnd
- Check all programming preconditions by calling the following functions and store the check results in LOCAL variable:
- CheckNonDefaultSessionSpeed()
=> returns FALSE if speed is to high and programming session cannot be entered
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&BOOLEAN x) and (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&BOOLEAN y)
=> at least one function returns TRUE if a control intervention is active and programming session cannot be entered
- IsEcuResetAllowedByPb()
=> returns FALSE if EPB actuation is active and programming session cannot be entered
2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd
- just return FALSE
3. Implement GetCommandTestDataInterface with subsystem scope: ReportChkPrgrPrecndCommandData
- set first response byte (DIAG_ROUTINE_STATUS_BYTE_INDEX) to 0x00 (DIAG_DAI_RID_SUCCESS_COMPLETED)
- set second byte to the number of Programming PreConditions that are not fulfilled and prevent the system from entering the programming session => note: the number must be calculated in this function
- if speed condition is unfulfilled, set next free response byte to 0x05 (DIAG_VEHICLE_SPEED_COND)
- if control intervention or EPB actuation is in progress, set next free response byte to 0x06 (DIAG_CONTROLLER_ACTIVE_COND)
- return the number of additional response bytes (= all bytes without pos. response byte + subfunction byte and RID bytes)
Note:
Please, find an untested(!) implementation proposal "Untested_Diag_ImplementatioProposal.zipx" attached to the task.
Note that this implementation might not work correctly, and may cause QAC and polyspace warnings that needs to be fixed or handled.
The proposal is based on SW checkpoint 1.3.3.142 with DiagArAdapter checkpoint 1.9.1.16 and DiagTestMgmtUnit checkpoint 1.8.2.7.
Owner: Ashwini Digajerla
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date: 25.05.2021 (set by task owner)
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: [MMA][X0200][SWAD] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
Please import and map requirements for stub implementation of the following routine:
0x0203 "Check Reprogramming Preconditions"
Map new runnable to OS task Task_DiagEvents_D_C0_1.
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date: 27.05.2021 (set by task owner)
------------------------------------------------------ | [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented This CR shall be used to implement the following diagnostic jobs:
1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz
2. PreCheckProgrammingDependencies - StartRoutine: $31 01 02 07 zz
Information:
- The behavior of the routines is specified in the CDD but it must be checked whether further relevant customer requirements are specified in other specifications + DOORS modules.
- The CR shall cover SWE1, SWE2, SWE3 and SWE4.
- The CR has not be derived from BROP and/or DCRP but has been requested by the customer to be implemented for B1.1 (= X0150). Please, refer to the attached Excel Sheet "MMA_Diag_EffortEstimation_basedOn_v2.5_PlanningStatus_2021-04-08.xlsx" that is exchanged with the customer.
To Diag CCB:
- Please, add owner from Diag team.
- Please, add analysers from Diag team and SwAD team. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
19.05.2021 WeyandC:
Routine 0x0203 "Check Reprogramming Preconditions" is not specified in DOORS module "EBS_Diagnostic_Requirements_Specification". But the routines is specified by the CDD and by specification "DDS R01-01".
It is no longer requested by the customer that routine 0x0207 "PreCheckProgrammingDependencies" is supported by the application. This is why follow-up ALM_Change Request 5198683 has been or will be rejected.
Purpose of the CR:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified and have been discussed with the customer:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the CR must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
DIAG part:
1. Adapt SWC Diag
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml.
2. implementation of routine 0x0203 "Check Reprogramming Preconditions":
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
3. Diag framework adaptations:
=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE and OS.
NOTE:
1. SWC-Diag will call the following Autosar interfaces:
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&brake_ctrl_active);
- (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&drive_ctrl_active);
The ports are still connected from Geely / VW (= baseline for the MMA project). No actions are required.
The Autosar interfaces can be used from SwAD / Autosar point of view. Please, refer to the attached email "AW_ ALM_Change Request 5136349_ _MMA__X0150__Diag_ Implement _Programming Check_ routines.msg" for details.
2. Diag Design:
- It was decided for this routine that Dcm configuration is not manually adapted in DaVinci Configurator. The multiple in and out parameters are NOT replaced with a single in- and a single out-parameter. Hence, the DiagArAdapter routine runnable must copy data from the multiple in-parameters to the single generic Diag in-parameter and vice versa from the single Diag generic out-parameter to the multiple out-parameters.
- It was also decided that stack variables (= function variables) will be used as the additional stack consumption is negligible.
- For the future, it will be check whether the Dcm configuration will be manually adapted in DaVinci Configurator for new routines or whether shared Diag RAM variables shall be used to copy data between parameters defined by Autosar and generic Diag parameters.
=> Both decision will not affect the implementation of routine 0x0203 that is provided with this CR.
--------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via Teams
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the new routine: 0x0203 "Check Reprogramming Preconditions"
- Map the new runnable for the routine to OS task Task_DiagEvents_D_C0_1. The slot is not relevant.
=> Generate RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavaraju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 26.05.2021 (set by task owner)
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
The following DIDs routine be implemented with this CR:
Routine 0x0203 "Check Reprogramming Preconditions" with sub function $01 "StartRoutine" is specified by the CDD and by specification "DDS R01-01".
Functionality:
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future. Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
Refer to the attached emails for further details.
Please, use this CR to define SW requirements for this routine.
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 26.05.2021
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement routine 0x0203 "Check Reprogramming Preconditions".
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl framework
Description:
Purpose of the task:
1. Implement sub function $01 "StartRoutine" for routine 0x0203 "Check Reprogramming Preconditions":
The routine shall check which conditions are currently not fulfilled for entering the programming session. It shall return the number of not fulfilled conditions and a list of those conditions.
The CDD already specifies a list of unfulfilled conditions. Additional conditions might be added if required after consultation with the customer.
The following reasons have been identified by now or require clarification:
- 0x05: vehicle speed
- 0x06: (1) Control is active or (2) EPB actuation is ongoing
=> Please, note that condition (2) for reason 0x06 has not been specified by customer or System but it is expected that the condition will be specified by System in the future.
Therefore, the check will be considered for the implementation of this routine. However, the stub ("IsEcuResetAllowedByPb") for the actual condition check will be kept as for the "Entering Programming Session" job ($10 02).
2. As this is the first routine that is implemented for MMA, the task must also be used to adapt the Diag framework to support routines under the project-specific conditions.
- Adaptations are required to support sub function $01 "StartRoutine" for service $31 "RoutineControl" with additional response bytes.
- Therefore, the generic start routine handling shall be adapted.
- The following SW pool components are affected: DiagArAdapter, DiagTestMgmtUnit
General:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
Details:
1. Adapt SWC Diag:
- Add service port for the new routine to SWC Diag and configure direction to server:
- Add runnable for the new routine.
=> Export updated Diag_AUTOSAR_Diag.arxml
2. Framework adaptations:
DiagArAdapter:
- Adapt the interface GenericStartRoutineInterface:
- new parameter list: const U16 test_id, const U8 *input_parameters, U8 *const output_parameters, const U8 param_length, U16 * const out_param_length, Dcm_NegativeResponseCodeType *ErrorCode
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericStopRoutineInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
- Adapt the interface GenericASyncShortTermAdjustmentInterface
- adapt the call of function CommandTest according to the new parameter list of the CommandInterface
TestGroup:
- Adapt the interface CommandTest:
- new parameter list: const U16 comms_id, const U8 test_type, const BOOLEAN command, const U8* const parameters, U8* const output_data, const U16 length, U16* const out_length
- add a new block after the "Execute Command" block and before the "Update Group Status block":
- check if "status" is TST_STATUS_OK and "out_length" is not NULL; if so call interface "ExecuteGetCommandDataInterface" and store the return value via "out_length" pointer
- Add new type definition in the global header file for function pointer to retrieve the response parameters for start routine service request: typedef U16 (*GET_COMMAND_TEST_DATA_TYPE)(U8* results)
TestSpecification:
- Add new function U16 ExecuteGetCommandDataInterface(const U32 test_id, U8 results_buffer[]) with subsystem scope
- the function shall check whether "GetCommandTestDataInterface" is not NULL for the given "test_id"
- if so, it shall return the length returned by the respective "GetCommandTestDataInterface" interface.
- otherwise, it shall return 0 as length.
- Adapt definition of data type TEST_SPEC_DATA_TYPE:
- add new paramter "GET_COMMAND_TEST_DATA_TYPE GetCommandTestDataInterface" behind the "Get_Result_Data_Inteface" parameter
InputOutputControlById.c:
- non functional adaptation to make the SW compile:
- adapt the calls of function "CommandTest" in function "IoControlByIdentifier" to make the SW compile
- pass NULL for the new parameters of "CommandTest"
3. Implementation of routine 0x0203:
DiagArAdapter_cfg:
- Implement the new runnable "RoutineServices_Check_Reprogramming_Preconditions_Start":
- define stack variables:
- for 2nd parameter of CommandTest: const U8 start_routine_in_signals = 0u
- for 3rd parameter of CommandTest (=> it is expected that a size of 8 bytes will be sufficient => currently a size of 2 bytes would be ok): U8 start_routine_out_signals[DIAG_PRGR_PRECND_MAX_DYN_LENGTH]
- for 5th parameter of CommandTest: U16 data_length_out = 0u
- OpStatus == DCM_initial:
- call CommandTest with the listed parameters and with 1st parameter = PROG_PRECOND_CHECK_TEST_ID, with 4th parameter = 0 and with ErrorCode as 6th parameter
- if returned data_length_out is less than minimal response length (= 2) or greater than minimal response legnth + size of array "start_routine_out_signals":
- call UpdateTestManagementActive(FALSE)
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
- otherwise:
- copy data from "start_routine_out_signals" to actual out parameters "routineInfo_Out", "Number_of_Unfulfilled_Preconditions_Out", "List_of_Preconditions_Out" and set "DataLength" to the correct value
- return E_OK
- OpStatus == DCM_CANCEL:
- call UpdateTestManagementActive(FALSE)
- return E_OK
- OpStatus has another value:
- return E_NOT_OK with ErrorCode DCM_E_GENERALREJECT
TestSpecification_Cfg:
- Adapt ROM table Test_Spec_Data: replace dummy entry with entry for routine 0x0203:
{
&CommandChkPrgrPrecnd,
&UpdateChkPrgrPrecnd,
NULL,
NULL,
&ReportChkPrgrPrecndCommandData,
PROG_PRECOND_CHECK_TEST_ID,
ROUTINE_BY_ID_TEST,
EXCLUSIVE_TEST_GROUP,
SECURITY_ACCESS_NOT_REQUIRED,
PARAM_LENGTH_ZERO,
(U8)IOC_NO_CHECK_REQUIRED
}
RoutineControl_Cfg:
1. Implement Command_Interface with subsystem scope: CommandChkPrgrPrecnd
- Check all programming preconditions by calling the following functions and store the check results in LOCAL variable:
- CheckNonDefaultSessionSpeed()
=> returns FALSE if speed is to high and programming session cannot be entered
- (void)Rte_Read_R_BrakeActive_BrakeControlArbitratorActive(&BOOLEAN x) and (void)Rte_Read_R_ArbDriveTorque_DriveControlArbitratorActive(&BOOLEAN y)
=> at least one function returns TRUE if a control intervention is active and programming session cannot be entered
- IsEcuResetAllowedByPb()
=> returns FALSE if EPB actuation is active and programming session cannot be entered
2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd
- just return FALSE
3. Implement GetCommandTestDataInterface with subsystem scope: ReportChkPrgrPrecndCommandData
- set first response byte (DIAG_ROUTINE_STATUS_BYTE_INDEX) to 0x00 (DIAG_DAI_RID_SUCCESS_COMPLETED)
- set second byte to the number of Programming PreConditions that are not fulfilled and prevent the system from entering the programming session => note: the number must be calculated in this function
- if speed condition is unfulfilled, set next free response byte to 0x05 (DIAG_VEHICLE_SPEED_COND)
- if control intervention or EPB actuation is in progress, set next free response byte to 0x06 (DIAG_CONTROLLER_ACTIVE_COND)
- return the number of additional response bytes (= all bytes without pos. response byte + subfunction byte and RID bytes)
Note:
Please, find an untested(!) implementation proposal "Untested_Diag_ImplementatioProposal.zipx" attached to the task.
Note that this implementation might not work correctly, and may cause QAC and polyspace warnings that needs to be fixed or handled.
The proposal is based on SW checkpoint 1.3.3.142 with DiagArAdapter checkpoint 1.9.1.16 and DiagTestMgmtUnit checkpoint 1.8.2.7.
Owner: Ashwini Digajerla
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date: 25.05.2021 (set by task owner)
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title: [MMA][X0200][SWAD] Support new routine 0x0203 "Check Reprogramming Preconditions"
Description:
Please import and map requirements for stub implementation of the following routine:
0x0203 "Check Reprogramming Preconditions"
Map new runnable to OS task Task_DiagEvents_D_C0_1.
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date: 27.05.2021 (set by task owner)
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 16
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'F' (Provider of information),
'G' (Behavior),
'H' (Involved team).
Description of the additional columns based on an example:
'C': DIAG_2119;
'E': 'The service Read DTC Information (SID $19) shall be supported, with all in this requirement specification defined "DTC Information'
'F': This column contains the teams or the behavior which support the implementation of this requirement by the behavior in column 'G', e.g. to provide information/interface to fulfill the requirement. In this case Fm has to provide an interface.
'G': Behavior: This column contains the behavior(s) which have to implement the customer requirement. In this case the customer requirement shall be implemented by the in column 'G' mentioned behavior(s).
'H': This column contains the teams which are impacted by this requirement, team might be in supporting role (refer column 'F') and other in 'responsible role' to implement the behavior (refer column'H').
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
22.04.2021
Ashwini Digajerla
Dig team:
As per cluster ID 16 below DIDs has to be implemented.
-Read ECU Name(c)
-Read Supported configuration mechanisms(0xF131)
-Read DID for Snapshot-Date: Vehicle Odometer in LowResolution(0x010A)
-Read DID for Snapshot-Date: Current Operating Time(0x0133)
Due to non availbility of the required interfaces for DID 0x010A and 0x0133 from Coms and FM subsytems ,seperate Spawn CR is created for implementing this 2 DIDs.
Req Reference:Cdd file from D:\Daimbler\VariantSB\DiagMain\Cfg\Model
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
26.04.2021 WeyandC: Ooi Siang Tan has been removed from the list of analysers as MeMo team is not involved in this CR. Please, refer to the attached email "AW_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function -Read ID-Data_ Remaining jobs_ Cluster ID 16.msg".
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Ashwini Digajerla .
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE1/4][Diag] SF 8.8 System Diagnostic Function -- Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
Owner: Joachim Hornung
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: Christian Weyand
Reviewer: Ahmed Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
Implement Diag application part to support DIDs 0xF104 and 0xF131 .
The task shall be used:
1. to update the design model
2. to implement the requested functionality including QAC, polyspace and log file analysis
3. and to update / add VCast tests, execute them and link them to the design model.
Details for point 2:
The implementation in diagnostic application needs to be adapted with below new DIDs.
-Read ECU Name(0xF104)
-Read Supported configuration mechanisms(0xF131)
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
Owner: Irannavar Satish Pundalik EXT HDR Tata Elxsi
Reviewer: Ashwini Digajerla
Estimated design effort/h:6
Estimated implementation effort/h:6
Estimated unit testing effort/h:18
------------------------------------------------------
Total effort/h: 30h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
Task SwAD:
------------------------------------------------------
Title:(SWE4/4)SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description: Please import and map requirements.
Owner:Caesar Klukowski
Reviewer: Christoph Bayer, Christian Weyand
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 4.5.2021
------------------------------------------------------
Task AUTOSAR:
------------------------------------------------------
Title:SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
->With new Arxml provided by Diag task ,create new service ports and runnables for 0xF101 and 0xF103 DIDs .
->Do task mapping for the new runnables in configarator . .
->Generated DCM and RTE and checkin the changes.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana Krishna
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 30.4.2021
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 16
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'F' (Provider of information),
'G' (Behavior),
'H' (Involved team).
Description of the additional columns based on an example:
'C': DIAG_2119;
'E': 'The service Read DTC Information (SID $19) shall be supported, with all in this requirement specification defined "DTC Information'
'F': This column contains the teams or the behavior which support the implementation of this requirement by the behavior in column 'G', e.g. to provide information/interface to fulfill the requirement. In this case Fm has to provide an interface.
'G': Behavior: This column contains the behavior(s) which have to implement the customer requirement. In this case the customer requirement shall be implemented by the in column 'G' mentioned behavior(s).
'H': This column contains the teams which are impacted by this requirement, team might be in supporting role (refer column 'F') and other in 'responsible role' to implement the behavior (refer column'H').
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
22.04.2021
Ashwini Digajerla
Dig team:
As per cluster ID 16 below DIDs has to be implemented.
-Read ECU Name(c)
-Read Supported configuration mechanisms(0xF131)
-Read DID for Snapshot-Date: Vehicle Odometer in LowResolution(0x010A)
-Read DID for Snapshot-Date: Current Operating Time(0x0133)
Due to non availbility of the required interfaces for DID 0x010A and 0x0133 from Coms and FM subsytems ,seperate Spawn CR is created for implementing this 2 DIDs.
Req Reference:Cdd file from D:\Daimbler\VariantSB\DiagMain\Cfg\Model
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
26.04.2021 WeyandC: Ooi Siang Tan has been removed from the list of analysers as MeMo team is not involved in this CR. Please, refer to the attached email "AW_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function -Read ID-Data_ Remaining jobs_ Cluster ID 16.msg".
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Ashwini Digajerla .
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE1/4][Diag] SF 8.8 System Diagnostic Function -- Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
Owner: Joachim Hornung
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: Christian Weyand
Reviewer: Ahmed Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
Implement Diag application part to support DIDs 0xF104 and 0xF131 .
The task shall be used:
1. to update the design model
2. to implement the requested functionality including QAC, polyspace and log file analysis
3. and to update / add VCast tests, execute them and link them to the design model.
Details for point 2:
The implementation in diagnostic application needs to be adapted with below new DIDs.
-Read ECU Name(0xF104)
-Read Supported configuration mechanisms(0xF131)
Davini Configarator changes:
->Although all diagnostic jobs are already configured in the Dcm configuration, a Dcm configuration update will be required with this CR 4861342 .
This is because:
1. “Dsp Data Use Port” shall be changed to “USE_DATA_SYNCH_CLIENT_SERVER” As the callout will never return “pending”.
->Task mapping for the RTE calls shall be done.
Davini Developer changes:
->Create new runnables for 0xF101 and 0xF103 DIDs and generated DCM and RTE.
Diag Application changes:
Code Changes:
-> Implement Read functions in DiagArAdapter_Cfg.c file
->Add Read functions for 2 DIDs in the file \ReadDataByIdentifier_Cfg_Priv.h .
-> In ReadDataByIdentifier_Cfg.c file add the call back functions in lookup table and implement functions to read the data.
-> Add required macros to the corresponding ReadDataByIdentifier_Cfg.h. and ReadDataByIdentifier_Cfg_sub.h files.
->only ROM data will be read with the 2 DIDs
->Attached code changes.
-> No actions required by MeMo,FM and coms team for this CR.
Owner: Irannavar Satish Pundalik EXT HDR Tata Elxsi
Reviewer: Ashwini Digajerla
Estimated design effort/h:6
Estimated implementation effort/h:6
Estimated unit testing effort/h:18
------------------------------------------------------
Total effort/h: 30h
[Optional] Planned completion date: 30.04.2021
------------------------------------------------------
Task SwAD:
------------------------------------------------------
Title:(SWE4/4)SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description: Please import and map requirements.
Owner:Caesar Klukowski
Reviewer: Christoph Bayer, Christian Weyand
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 4.5.2021
------------------------------------------------------
Task AUTOSAR:
------------------------------------------------------
Title:SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16
Description:
->With new Arxml provided by Diag task ,create new service ports and runnables for 0xF101 and 0xF103 DIDs .
->Do task mapping for the new runnables in configarator . .
->Generated DCM and RTE and checkin the changes.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana Krishna
------------------------------------------------------
Total effort/h: 8
[Optional] Planned completion date: 30.4.2021
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read Version Data, Cluster ID 9
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Comms, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 9
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'G' (Behavior),
'H' (Involved team).
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' 2021-06-02 WeyandC: Analysis update after meeting with J. Wagner (Autosar) und M. Schlien (Comms).
2021-05-26 C. Klukowski: Refer meeting minutes '2021-05-26_CR 4861296 - MMA X0200 Clarification regarding interfaces for version information for diagnostics.txt'.
Note:
1. The customer has confirmed that DID 0xEF02 "Read Standard Reprogramming SW Package information" is no longer requested to be supported by the application SW. Please, refer to the attached email "AW_ Read DIDs zum Auslesen der Versionsinformationen (X0200).msg".
2. Security colleague has confirmed that DID 0xEF04 "Read SSA Version Information" has already been implemented with ALM_Change Request 4970113 and that its implementation is no longer in the scope of this CR. Please, refer to the attached email "RE_ DAI MMA X0200 - Read SSA VErsion Information.msg".
3. The CR will be used to provide a fix implementation in Diag. A follow-up CR has been spawned to ALM_Change Request 5358720 investigate with Vector how the toolchain can be used to bring the data automatically into the SW and to replace the initial fix implementation.
4. Bootloader colleague C. Henkel was informed about the "µC Identification" that is read with DID 0xEF03 and which should be identical to the one that is read with 0xEF02 in the bootloader.
Purpose of the CR:
Provide implemenation for the following read jobs / read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x26
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for these DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
17.05.2021 WeyandC:
- Analysis have been started.
- Please, refer to the attached email "ALM_Change Request 4861296_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function Read Version Data_ Cluster ID 9 .msg" and the attached txt file "CR4861296_VersionData_Notes.txt".
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Weyand, discussed with J. Wagner (Autosar), M. Schlien (Comms), and C. Klukoswki (SwAD). Security team and Integration team are not affected.
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [DCRP 46.1] [IBC][SW-D] SF 8.8 System Diagnostic Function Read Version Data, Cluster ID
Description:
Please import and map requirements for stub implementation of the following diagnostic read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Map runanbles to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant from functional point of view..
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date:
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
The following DIDs shall be implemented:
- $22 EF 00: Read ECU Extract Version: is specified by section 1.13.1.20 "ECU Extract Version" in the customer DOORS module and by the CDD.
- $22 EF 01: Read Diagnostic Extract Version: is specified by the CDD.
- $22 EF 03: Read Standard Application SW Package information: is specified by section 1.13.1.22 "Standard Application SW Package information" in the customer DOORS module and by the CDD.
- $22 F1 0D: Read DDS Package Release: is specified by section 1.13.1.3 "DDS Package Release" in the customer DOORS module and by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement stubs for diagnostic read jobs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
+ $22 EF 00: Read ECU Extract Version - $22 EF 01: Read Diagnostic Extract Version
+ $22 EF 03: Read Standard Application SW Package information
+ $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: J. Wagner
Reviewer: H. Ambarukhana, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title:
Description:
Note: CR analysis is not yet completed and task description might be adapted.
The following read jobs / read DIDs shall be implemented with this task: - $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x0026
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
Note:
- The values for DIDs 0xEF00, 0xEF01, 0xEF03 are also defined in the attached text file.
Owner: S. Irannavar
Reviewer: A. Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date:
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read Version Data, Cluster ID 9
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1
As part of 'Work step: Perform Preliminary Impact Analysis' in stages https://cdc-stages.emea.zf-world.com:8443/pkit/go/pelement.do?id=469319&type=Subprocess following teams are identified, which are impacted by the customer requirements.
Diag, Comms, Security, Memo
Please assign as 'Owners'; Diag
Please assign as 'Analysers'; Diag, Comms, Memo, SwAD.
--------------------------------------------------------------------------------
Details (Exact description):
--------------------------------------------------------------------------------
Doing by SwD:
(SWE1)Please derive requirements from the 'Source' (for 'Source' refer below) and map the behavior to the derived requirements
(SWE2)Please update SwAD model according to derived requirements.
(SWE3)Please develop a sw design (RPY model) and implement the behaviors according to the derived requirements.
(SWE4)Please develop sw unit tests according to the derived requirements.
Doing by SwAD:
(SwAD)Import the derived requirements into SwAD model.
Input Work Products (Link or other reference): Source (customer requirements): refer attached excel sheet 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' ,please filter column 'N' 'Diag Cluster ID' for the value of 9
Link to customer requirements: http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00
The attachment 'MMA_Diag_Customer_Reqs_v1.1_SwAD.xlsx' is an export of the customer DOORS module 'EBS Diagnostic Requirements Specification', current 29.1, which contains additional columns:
'G' (Behavior),
'H' (Involved team).
--------------------------------------------------------------------------------
Output Work Products:
Refer stages
--------------------------------------------------------------------------------
Acceptance Criteria:
--------------------------------------------------------------------------------
The requirements are derived.
SwAD model updated according to derived requirements.
Sw design (RPY model) and implementation of the behaviors according to the derived requirements is done.
sw unit tests according to the derived requirements are developed.
Derived requirements are mapped to behaviors and imported to Domain Architecture.
In case of gaps/incompleteness/incorrectness which shall not be resolved with particular Task (where the review has failed), only 'ONE' follow up CR shall be created which covers all findings of all Tasks of that CR (purpose: reduction of CRs).
This must be agreed with the SwPM and the CR must be planned by SwPM.
This CR must be spawned by the parent CR of the failed Task.
Responsibility to provide the findings which shall be solved with another CR into the another CR belongs to the Owner of this Task. The reviewer should complete/close the Task only if the findings are documented in the follow up CR.
Example how the follow-up CR might look:
Summary: [FollowUp] <Summary_Of_CR_spawnedBy>
Description:
'This CR is a follow-up CR of <ID_of_CR_spawnedBy>.
With this CR the findings shall be resolved, which were identified during the review of the Task(s) attached to the CR <ID_of_CR_spawnedBy>.
It is agreed with SwPM to shift the correction of the findings to another build.
Task: <ID of Task with Findings>
Refer attachment 'ReviewFindingsOfTask_<ID of Task with Findings>'.' 2021-06-02 WeyandC: Analysis update after meeting with J. Wagner (Autosar) und M. Schlien (Comms).
2021-05-26 C. Klukowski: Refer meeting minutes '2021-05-26_CR 4861296 - MMA X0200 Clarification regarding interfaces for version information for diagnostics.txt'.
Note:
1. The customer has confirmed that DID 0xEF02 "Read Standard Reprogramming SW Package information" is no longer requested to be supported by the application SW. Please, refer to the attached email "AW_ Read DIDs zum Auslesen der Versionsinformationen (X0200).msg".
2. Security colleague has confirmed that DID 0xEF04 "Read SSA Version Information" has already been implemented with ALM_Change Request 4970113 and that its implementation is no longer in the scope of this CR. Please, refer to the attached email "RE_ DAI MMA X0200 - Read SSA VErsion Information.msg".
3. The CR will be used to provide a fix implementation in Diag. A follow-up CR has been spawned to ALM_Change Request 5358720 investigate with Vector how the toolchain can be used to bring the data automatically into the SW and to replace the initial fix implementation.
4. Bootloader colleague C. Henkel was informed about the "µC Identification" that is read with DID 0xEF03 and which should be identical to the one that is read with 0xEF02 in the bootloader.
Purpose of the CR:
Provide implemenation for the following read jobs / read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x26
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for these DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
17.05.2021 WeyandC:
- Analysis have been started.
- Please, refer to the attached email "ALM_Change Request 4861296_ _DCRP 46_1_ _IBC__SW-D_ SF 8_8 System Diagnostic Function Read Version Data_ Cluster ID 9 .msg" and the attached txt file "CR4861296_VersionData_Notes.txt".
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Weyand, discussed with J. Wagner (Autosar), M. Schlien (Comms), and C. Klukoswki (SwAD). Security team and Integration team are not affected.
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK 1/5
------------------------------------------------------
Title: [DCRP 46.1] [IBC][SW-D] SF 8.8 System Diagnostic Function Read Version Data, Cluster ID
Description:
Please import and map requirements for stub implementation of the following diagnostic read DIDs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Map runanbles to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant from functional point of view..
Owner: C. Klukowski
Reviewer: C. Bayer, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 8h
[Optional] Planned completion date:
------------------------------------------------------
TASK 2/5
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
The following DIDs shall be implemented:
- $22 EF 00: Read ECU Extract Version: is specified by section 1.13.1.20 "ECU Extract Version" in the customer DOORS module and by the CDD.
- $22 EF 01: Read Diagnostic Extract Version: is specified by the CDD.
- $22 EF 03: Read Standard Application SW Package information: is specified by section 1.13.1.22 "Standard Application SW Package information" in the customer DOORS module and by the CDD.
- $22 F1 0D: Read DDS Package Release: is specified by section 1.13.1.3 "DDS Package Release" in the customer DOORS module and by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 3/5
------------------------------------------------------
Title: [MMA][Diag][SWE2][X0200] Implement the following read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement stubs for diagnostic read jobs:
- $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: F. Mukkat
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date:
------------------------------------------------------
TASK 4/5
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for read DIDs: 0xEF00, 0xEF01, 0xEF03 and 0xF10D
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
+ $22 EF 00: Read ECU Extract Version - $22 EF 01: Read Diagnostic Extract Version
+ $22 EF 03: Read Standard Application SW Package information
+ $22 F1 0D: Read DDS Package Release
- Map the new runnables only for the DIDs that are implemented by SWC Diag to OS task Task_DiagEvents_D_C0_1. If no free slots are available, then map remaining ones to Task_DiagEvents_D_C0_2. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: J. Wagner
Reviewer: H. Ambarukhana, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7h
[Optional] Planned completion date:
------------------------------------------------------
TASK 5/5
------------------------------------------------------
Title:
Description:
Note: CR analysis is not yet completed and task description might be adapted.
The following read jobs / read DIDs shall be implemented with this task: - $22 EF 00: Read ECU Extract Version
- $22 EF 01: Read Diagnostic Extract Version
- $22 EF 03: Read Standard Application SW Package information
- $22 F1 0D: Read DDS Package Release
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for all the listed DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for all the listed DIDs to SWC Diag and configure direction to server:
- support operations ConditionCheckRead, and ReadData
- Add runnables for these DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementation in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for all the listed DIDs.
4. Implement callouts in ReadDataByIdentifier_Cfg to fill response buffer with requested data:
4.1. General:
- Extend configuration table "Read_Data_Id_Access".
- Implement a read callout in ReadDataByIdentifier_Cfg for the DID.
- The response data should provided by Diag itself. Use defines or const variables with file scope.
4.2. Regarding DID 0xEF00 "ECU Extract Version"
Response Format - data type : fix values:
- ECU Extract Major Version - BCD (1Byte) : 21
- ECU Extract Minor Version - BCD (1Byte) : 05
- ECU Extract Patch Version - BCD (1Byte) : 00
- Identification Type Module - Identifications EF00 : 0
- XDIS Version - ASCII (10Byte) : "20.4.1" + filled with space characters
- Export Date - ASCII (10Byte) : "2021-02-05" + filled with space characters
- ECU Name - ASCII (30Byte) : "ESP" + filled with space characters
- Checksum - HexField (200 Byte) : HEX: F9 12 B3 76 E0 05 21 B0 E2 EC 30 D5 B6 74 7F E8 3D 07 6B 22 + filled with 0x00
4.3. Regarding DID 0xEF01 "Diagnostic Extract Version"
Response Format - data type : fix values:
- Diagnostic Extract Major Version - BCD (1Byte): 02
- Diagnostic Extract Minor Version - BCD (1Byte): 00
- Diagnostic Extract Patch Version - BCD (1Byte): 02
- CANdela Version - ASCII (10Byte): “12.0.100” + filled with space characters
- DDM Version - ASCII (10Byte): “V16.0.0” + filled with space characters
- Exported Diagnostic - Variant ASCII (30Byte): "Diag_005002" + filled with space characters
4.4. Regarding DID 0xEF03 "Standard Application SW Package information"
Response Format - data type : fix values:
- Standard Application SW Package Major Version BCD (1Byte) : 11
- Standard Application SW Package Minor Version BCD (1Byte) : 26
- Standard Application SW Package Patch Level BCD (1Byte) : 03
- Standard Application SW Package Build Version BCD (1Byte) : 00
- µC Identification µC ID : "TC387TP" + filled with space characters
- Supplier Identification SupplierList : 0x0026
4.5. Regarding DID 0xF10D "Read DDS Package Release"
- Implement a new check function void CheckDdsPackageReleaseInfo(void) in ReadDataByIdentifier_Cfg with subsystem scope.
+ The new function shall be called from function InitDataAccessUnitApplication() after the call of function CheckActiveDiagInfo().
+ The function shall read Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID and store the content of the function in an U8 array with a size of 4 that is declared within the scope of the function
+ The following content is expected:
- array[0]: year of DDS package release of the application
- array[1]: month of DDS package release of the application
- array[2]: year of DDS package release of the bootloader
- array[3]: month of DDS package release of the bootloader
+ The DDS package release of the application is 20 dec (year), 1 dec (month) => introduce defines in ReadDataByIdentifier_Cfg with private scope
+ Check if this data is stored for the application. If so, do nothing. Otherwise, update the content of the array and write Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID with the updated array.
+ Note: No need to check the checksum of the Nvram block. If the checksum is invalid, the Nvram handler will return value 0xFF for all bytes of the block. The DDS package release will be considered as invalid, and the block will be updated.
- Implementation of the DID:
+ first read content of Nvram block NVRAM_DDS_PCKAGE_RELEASE_BLK_ID. Then copy the content byte wise into the the Nvram buffer
+ Note: No need to check the checksum of the Nvram block. If the checksum was incorrect, it was corrected in the init phase with function CheckDdsPackageReleaseInfo().
Note:
- The values for DIDs 0xEF00, 0xEF01, 0xEF03 are also defined in the attached text file.
Owner: S. Irannavar
Reviewer: A. Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 18h
[Optional] Planned completion date:
------------------------------------------------------ |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented This CR scope:
Integration of Crypto Stack + SSA for the functionally route of the SecOC jobs to Crypto SW
here the SecOC key generation has to be done using the default Car specific secret during the development phase (SSA-928)
Provision of initial (standard) key material:
Car-specific secret: 0x5577654d617274696e4a756c69616e416e64726561734d61726b757332303136, Data-ID: 4660 (0x1234)
Resulting SHA-512-Hash: 0x2be0d3774362c7df21f2a696d9915889b54163460a41d1d8c8c1104b
ba4da96a27bd88b5829667075caf4319559d35bbcac333c4c57ffc417e3d11f826472300
Resulting symmetric key: 0x2be0d3774362c7df21f2a696d9915889, resulting checksum for symmetric key: 0x26472300 Hari Krishna E 07/04/2021:
this CR is the first feature integration (Secure Comms) item of B1.1, due to that the CR shall be used for the SSA integration in general plus the SecOC interactions
Accordingly, the analysis has been performed to identify the interaction points of SecOC and SSA along with the important aspects to be considered for integration
1. SSA scheduling
2. SecOC key setup using the Standard Secret via KeyM
3. SecOC BroadCast PDU reception (BcTp)
4. SecOC Interactions withCSM (Crypto SwLib)
5. SSA key storage blocks in NvM
6. SecOC Interactions with FvM(SSA)
a presentation file (SecOC_Integ_Concept.pptx) has been prepared to cover the above listed topics out of customer spec & vector integration docs (refer attachments)
@CCB:
to realize the integration points, following tasks are necessary
#Task: Functional Integ of SSA + SecOC @ Security team (point 2 to 6)
#spawn CR: Scheduling of SSA @ SwAD team (point 1 - slides 3 & 4)
Note: dependencies related to NvM & Dem shall be addressed to CRs (4990180 & 5116760) | [Defect]: [Diag] ESP178: ID-Data services not implemented This CR scope:
Integration of Crypto Stack + SSA for the functionally route of the SecOC jobs to Crypto SW
here the SecOC key generation has to be done using the default Car specific secret during the development phase (SSA-928)
Provision of initial (standard) key material:
Car-specific secret: 0x5577654d617274696e4a756c69616e416e64726561734d61726b757332303136, Data-ID: 4660 (0x1234)
Resulting SHA-512-Hash: 0x2be0d3774362c7df21f2a696d9915889b54163460a41d1d8c8c1104b
ba4da96a27bd88b5829667075caf4319559d35bbcac333c4c57ffc417e3d11f826472300
Resulting symmetric key: 0x2be0d3774362c7df21f2a696d9915889, resulting checksum for symmetric key: 0x26472300 Hari Krishna E 07/04/2021:
this CR is the first feature integration (Secure Comms) item of B1.1, due to that the CR shall be used for the SSA integration in general plus the SecOC interactions
Accordingly, the analysis has been performed to identify the interaction points of SecOC and SSA along with the important aspects to be considered for integration
1. SSA scheduling
2. SecOC key setup using the Standard Secret via KeyM
3. SecOC BroadCast PDU reception (BcTp)
4. SecOC Interactions withCSM (Crypto SwLib)
5. SSA key storage blocks in NvM
6. SecOC Interactions with FvM(SSA)
a presentation file (SecOC_Integ_Concept.pptx) has been prepared to cover the above listed topics out of customer spec & vector integration docs (refer attachments)
@CCB:
to realize the integration points, following tasks are necessary
#Task: Functional Integ of SSA + SecOC @ Security team (point 2 to 6)
#spawn CR: Scheduling of SSA @ SwAD team (point 1 - slides 3 & 4)
Note: dependencies related to NvM & Dem shall be addressed to CRs (4990180 & 5116760) |
|
[Defect]: [Diag] ESP178: ID-Data services not implemented The customer was informed that a functional implementation for the following read DIDs cannot be provided for SW B2 / X0200:
- 0xF18C „ECU SerialNumber"
- 0x010C „Vehicle Odometer“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
Hence, the customer has requested at least a stub implementation for these DIDs:
- F18C „ECU SerialNumber“: 178X0200000001 (ASCII)
- 010C „Vehicle Odometer“: 0x00000A
- 0133 „Current Operating Time“: 0x0000000000
- F103 „Vedoc relevant information“: 178X0200000001 (ASCII)
=> Please, refer to the attached email "Fehlende Diagnosedienste zum B2.msg" for details.
This CR shall be used to provide the requested stub implementation for X0200.
Functional implementation will be provided with the following CRs at a later point of time:
- 0xF18C „ECU SerialNumber": ALM_Change Request 4861309
- 0x010C „Vehicle Odometer“: ALM_Change Request 5190898
- 0x0133 „Current Operating Time“: ALM_Change Request 5190898
- 0xF103 „Vedoc relevant information“: ALM_Change Request 4861309 --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
18.05.2021 WeyandC:
0. General note:
- The customer mixed up the following DIDs: 0x010A „Vehicle Odometer in Low Resolution“ and 0x010C "Vehicle Odometer“ in the attached email "Fehlende Diagnosedienste zum B2.msg".
- Other than stated in the CR description, a stub for DID 0x010A "Vehicle Odometer in Low Resolution" shall be provided with this CR - not for DID 0x010C.
- The customer has also confirmed that same string shall be returned for DID 0xF103 as for 0xF18C.
- Please, refer to the Excel Sheet "MMA_Diag_EffortEstimation_2021-05-18_Daimler.xlsx" that was updated today together with the customer (F. Tetzlaff).
Purpose of the CR:
Provide stub implemenation for the following read jobs / read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, accepted by S. Basavaraju, C. Klukowski
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK: Autosar
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C "ECU SerialNumber"
- 0x010A "Vehicle Odometer in Low Resolution"
- 0x0133 "Current Operating Time"
- 0xF103 "Vedoc relevant information"
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavarju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE1
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
The following DIDs shall be implemented:
- DID 0xF18C "ECUSerialNumberDataIdentifier" is specified by section 1.13.1.12 "ECU Serial Number" in the customer DOORS module and by the CDD.
- DID 0xF103 "Vedoc Relevant Information" is specified by section 1.13.1.25 "Vedoc Relevant Information" in the customer DOORS module and by the CDD.
- DID 0x010A "Vehicle Odometer in Low Resolution" is specified by the CDD.
- DID 0x0133 "Current Operating Time" is specified by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Please, use this task to specify SW requirements for the stub implementation of the 4 read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 26.06.2021
------------------------------------------------------
TASK: DIAG SWE3/4
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
Owner: Satishpundalik Irannavar
Reviewer: Ashwini Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 14h
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE2
------------------------------------------------------
Title: [MMA][Diag][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
(SWE2) Please update SwAD model according to derived requirements.
The CR is used to implement stubs for diagnostic read jobs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information"
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK SwAD
------------------------------------------------------
Title: [MMA] [X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103 - Import requirements and map the runnables
Description:
Import and map the requirements.
Map the runnables (10) to OS task Task_DiagEvents_D_C0_1.
For details refer CR or Tasks at CR.
Owner:Caesar Klukowski
Reviewer:Christian Weyand, Jens Auer
------------------------------------------------------
Total effort/h: 8
------------------------------------------------------ | [Defect]: [Diag] ESP178: ID-Data services not implemented The customer was informed that a functional implementation for the following read DIDs cannot be provided for SW B2 / X0200:
- 0xF18C „ECU SerialNumber"
- 0x010C „Vehicle Odometer“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
Hence, the customer has requested at least a stub implementation for these DIDs:
- F18C „ECU SerialNumber“: 178X0200000001 (ASCII)
- 010C „Vehicle Odometer“: 0x00000A
- 0133 „Current Operating Time“: 0x0000000000
- F103 „Vedoc relevant information“: 178X0200000001 (ASCII)
=> Please, refer to the attached email "Fehlende Diagnosedienste zum B2.msg" for details.
This CR shall be used to provide the requested stub implementation for X0200.
Functional implementation will be provided with the following CRs at a later point of time:
- 0xF18C „ECU SerialNumber": ALM_Change Request 4861309
- 0x010C „Vehicle Odometer“: ALM_Change Request 5190898
- 0x0133 „Current Operating Time“: ALM_Change Request 5190898
- 0xF103 „Vedoc relevant information“: ALM_Change Request 4861309 --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
18.05.2021 WeyandC:
0. General note:
- The customer mixed up the following DIDs: 0x010A „Vehicle Odometer in Low Resolution“ and 0x010C "Vehicle Odometer“ in the attached email "Fehlende Diagnosedienste zum B2.msg".
- Other than stated in the CR description, a stub for DID 0x010A "Vehicle Odometer in Low Resolution" shall be provided with this CR - not for DID 0x010C.
- The customer has also confirmed that same string shall be returned for DID 0xF103 as for 0xF18C.
- Please, refer to the Excel Sheet "MMA_Diag_EffortEstimation_2021-05-18_Daimler.xlsx" that was updated today together with the customer (F. Tetzlaff).
Purpose of the CR:
Provide stub implemenation for the following read jobs / read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
DIAG part:
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
AUOTSAR part:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information“
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE and OS.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): WeyandC, accepted by S. Basavaraju, C. Klukowski
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK: Autosar
------------------------------------------------------
Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
- Import updated Diag_AUTOSAR_Diag.arxml.
- Connect Dcm port to SWC Diag port for the 4 new DIDs:
- 0xF18C "ECU SerialNumber"
- 0x010A "Vehicle Odometer in Low Resolution"
- 0x0133 "Current Operating Time"
- 0xF103 "Vedoc relevant information"
- Map the 10 new runnables for the DIDs to OS task Task_DiagEvents_D_C0_1. The slots are not relevant.
=> Generate Dcm, RTE, and OS.
Owner: Hemanth Ambarukhana
Reviewer: Sireesha Basavarju, C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE1
------------------------------------------------------
Title: [MMA][Diag][SWE1][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
The following DIDs shall be implemented:
- DID 0xF18C "ECUSerialNumberDataIdentifier" is specified by section 1.13.1.12 "ECU Serial Number" in the customer DOORS module and by the CDD.
- DID 0xF103 "Vedoc Relevant Information" is specified by section 1.13.1.25 "Vedoc Relevant Information" in the customer DOORS module and by the CDD.
- DID 0x010A "Vehicle Odometer in Low Resolution" is specified by the CDD.
- DID 0x0133 "Current Operating Time" is specified by the CDD.
Customer DOORS module:
"EBS Diagnostic Requirements Specification": http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-0011ac00?doors.view=00000003
Please, use this task to specify SW requirements for the stub implementation of the 4 read DIDs:
- F18C „ECU SerialNumber“: return fix string 178X0200000001 (ASCII)
- 010A „Vehicle Odometer in Low Resolution“: return fix value 0x000A
- 0133 „Current Operating Time“: return fix value 0x0000000000
- F103 „Vedoc relevant information“: return fix string 178X0200000001 (ASCII)
Owner: J. Hornung
Reviewer: C. Weyand
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 26.06.2021
------------------------------------------------------
TASK: DIAG SWE3/4
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
This task shall be used for SWE3 (design model update + implementation) + SWE4 (VCast).
1. Adapt the Dcm configuration:
- change the value of attribute "DcmDspDataUsePort" under "/Dcm/DcmConfigSet/DcmDsp/DcmDspDatas/" from "USE_DATA_ASYNCH_CLIENT_SERVER" to "USE_DATA_SYNCH_CLIENT_SERVER" for the 4 DIDs
=> This change is proposed as the DIDs will always returns directly the final response. They will never return "Response Pending" (NRC 0x78).
2. Adapt SWC Diag
- Add service ports for the 4 DIDs to SWC Diag and configure direction to server:
- 0xF18C: support operations ConditionCheckRead, ReadData and ReadDataLength
- 0x010A: support operations ConditionCheckRead, and ReadData
- 0x0133: support operations ConditionCheckRead, and ReadData
- 0xF103: support operations ConditionCheckRead, ReadData and ReadDataLength
- Add runnables for the DIDs.
=> Export updated Diag_AUTOSAR_Diag.arxml
3. Update implementatiton in DiagArAdapter_Cfg.c:
- Implement newly generated runnables in DiagArAdapter_Cfg.c for the 4 DIDs.
4. Implement configuration and implementation in ReadDataByIdentifier_Cfg.
- add entries for the 4 DIDs to ROM table Read_Data_Id_Access and update the size of the table
- implement read functions for the new 4 DIDs:
a. read function for DID 0xF18C "ECU SerialNumber"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
b. read function for DID 0x010A "Vehicle Odometer in Low Resolution"
- shall fill the buffer with hex value 0x000A
- shall copy data of (a) define(s) to the response buffer
- response length: 2 byte
c. read function for DID 0x0133 "Current Operating Time"
- shall fill the buffer with hex value 0x0000000000
- shall copy data of (a) define(s) to the response buffer
- response length: 5 byte
d. read function for DID 0xF103 "Vedoc relevant information"
- shall fill the buffer with ASCII string 178X0200000001
- shall copy data from a ROM variable
- shall be implemented similarly as read function DiagRead_F104_EcuName
- response length: 15 byte
Owner: Satishpundalik Irannavar
Reviewer: Ashwini Digajerla
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 14h
[Optional] Planned completion date:
------------------------------------------------------
TASK: DIAG SWE2
------------------------------------------------------
Title: [MMA][Diag][X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103
Description:
(SWE2) Please update SwAD model according to derived requirements.
The CR is used to implement stubs for diagnostic read jobs:
- 0xF18C „ECU SerialNumber"
- 0x010A „Vehicle Odometer in Low Resolution“
- 0x0133 „Current Operating Time“
- 0xF103 „Vedoc relevant information"
Please, note that SW requirements might not be available in time. In that case, it must be checked whether a follow-up CR needs to be created.
Owner: C. Weyand
Reviewer: A. Elfeky
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4h
[Optional] Planned completion date: 28.05.2021
------------------------------------------------------
TASK SwAD
------------------------------------------------------
Title: [MMA] [X0200] Provide stub implementation for DIDs 0xF18C, 0x010A, 0x0133 and 0xF103 - Import requirements and map the runnables
Description:
Import and map the requirements.
Map the runnables (10) to OS task Task_DiagEvents_D_C0_1.
For details refer CR or Tasks at CR.
Owner:Caesar Klukowski
Reviewer:Christian Weyand, Jens Auer
------------------------------------------------------
Total effort/h: 8
------------------------------------------------------ |
|
[VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler Due to incorrect size of the ICC array "IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean" and the "for loop" shown below, Start/Stop function is always considered to be disabled by Chassinf (IsChassinfFunctionEnable(CHASSINF_SSA) always returns FALSE) even if the ECU is coded for Start/Stop and therefore, 'Systemfehler' is sent on the signal "ESP_StartStopp_Info" by the Start/Stop Handler.
The issue is reported for X0401 SW as ICC is still used. In the later SW versions, ICC is replaced with RTE and this issue would not occur . The above fix therefore, is only required for X0401 SW. Brief analysis summary:
--------------------------------------------------------------------------------
This CR should be used for Regeneration of ICC to provide updated inter core communication wrapper for the rest of the software.
Regeneration is required to resolve the issues due to incorrect size of ICC array 'IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean '
Correct array size is 152.
Latest x401 CP : 1.633.1.215.2.68 should be used.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Implement proposed task | [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler Due to incorrect size of the ICC array "IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean" and the "for loop" shown below, Start/Stop function is always considered to be disabled by Chassinf (IsChassinfFunctionEnable(CHASSINF_SSA) always returns FALSE) even if the ECU is coded for Start/Stop and therefore, 'Systemfehler' is sent on the signal "ESP_StartStopp_Info" by the Start/Stop Handler.
The issue is reported for X0401 SW as ICC is still used. In the later SW versions, ICC is replaced with RTE and this issue would not occur . The above fix therefore, is only required for X0401 SW. Brief analysis summary:
--------------------------------------------------------------------------------
This CR should be used for Regeneration of ICC to provide updated inter core communication wrapper for the rest of the software.
Regeneration is required to resolve the issues due to incorrect size of ICC array 'IccTxBuf_C1_C0.IsChassinfFunctionEnable_boolean '
Correct array size is 152.
Latest x401 CP : 1.633.1.215.2.68 should be used.
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Implement proposed task |
|
Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset (series software S011) in a new format for new Software S012:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
(Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22 )
This Change Request shall be used to for PBC Function & Control Team - change in parameter set P. Billig (23.07.21 - 14:10):
--------------------------------------------------------------------------------
Brief investigation comment:
This CR is for adapting some revision numbers and generating the new PARAMPBL_*.c file only (F&C part, see above).
To do so:
- Adapt minor revision of parameter file as usual. Do NOT generate parameter files yet.
- In file PBC_PARA\03_Integration\Build_Param\Config\DB_0003_7101_4KE_A001_AU5160000000_AU5164KESW0001DSA001.ocnf adapt values
<DataRecordVersion>A00G</DataRecordVersion>
<ModulVariant>AU516PBCA00G</ModulVariant>
to
<DataRecordVersion>A00H</DataRecordVersion>
<ModulVariant>AU516PBCA00H</ModulVariant>
- Update PBC_PARA\03_Integration\Build_Param\Build module to checkpoint 1.14.1.9.1.3
- Now generate new parameter files.
- If not present, check in generated PARAMPBL_*.c file
- If an older PARAMPBL_*.c is present at the same folder with a different name, remove it.
- Check in other parameter file generation artifacts, as usual.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for TCI: <Title> Audi CBEV - Adapt some parameter file revision numbers and generate new parameter files / Verifier: E. Harder (8 h)
Is a change in the ParameterFile required? (Do we need a PARA build?)
--------------------------------------------------------------------------------
Yes [x] or No []
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 22.07.21 - 13:40:
Please investigate this point and advise the next steps. | Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset (series software S011) in a new format for new Software S012:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
(Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22 )
This Change Request shall be used to for PBC Function & Control Team - change in parameter set P. Billig (23.07.21 - 14:10):
--------------------------------------------------------------------------------
Brief investigation comment:
This CR is for adapting some revision numbers and generating the new PARAMPBL_*.c file only (F&C part, see above).
To do so:
- Adapt minor revision of parameter file as usual. Do NOT generate parameter files yet.
- In file PBC_PARA\03_Integration\Build_Param\Config\DB_0003_7101_4KE_A001_AU5160000000_AU5164KESW0001DSA001.ocnf adapt values
<DataRecordVersion>A00G</DataRecordVersion>
<ModulVariant>AU516PBCA00G</ModulVariant>
to
<DataRecordVersion>A00H</DataRecordVersion>
<ModulVariant>AU516PBCA00H</ModulVariant>
- Update PBC_PARA\03_Integration\Build_Param\Build module to checkpoint 1.14.1.9.1.3
- Now generate new parameter files.
- If not present, check in generated PARAMPBL_*.c file
- If an older PARAMPBL_*.c is present at the same folder with a different name, remove it.
- Check in other parameter file generation artifacts, as usual.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for TCI: <Title> Audi CBEV - Adapt some parameter file revision numbers and generate new parameter files / Verifier: E. Harder (8 h)
Is a change in the ParameterFile required? (Do we need a PARA build?)
--------------------------------------------------------------------------------
Yes [x] or No []
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 22.07.21 - 13:40:
Please investigate this point and advise the next steps. |
|
Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset in a new format:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
*. will be implemented with CR 5533486
Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22
Please use this CR to introduce the odx file format Since this involves changes only to the Binaries of PARA and the necessary Tools update, this CR can be canceled and the changes will be implemented using the Integration Task. | Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC" Realization of Customer request: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"
target is to provide the recent Parameterset in a new format:
CRs shall be created for following tasks
F&C:
*. update minor Revision of recent Parameter set “PARAMPBL_Audi_CBEV_039_056_000.c” 0G à 0H à new Parameter set
*. will be implemented with CR 5533486
Integration:
*. creating of new ODX file with the name: “DB_0003_7101_4KE_A00H_AU516PBCA00H_M3PBCVAR001ECE18HA.odx”
*. using new ODX create (v2.50): url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22ODXCreate%5fV250%5fLizenz%5f20221205.7z%22
*. with new FDS2309: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/CBEV/01%5fFrom%5fCustomer/03%5fTools/ODXCreate/project.pj&selection=%22config%5fFDSProject%5f2309%5fE.7z%22
*. and possibly (depending on answer of Conti): new SA2 code (to be provided by Continental)
*. Preparation of Zip file using Audi Tool: url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/EPB/CustomerDevelopment/Audi/PPE/01%5fFrom%5fCustomer/03%5fTools/ODX/project.pj&selection=%22dsdg22sys42%5fwithout%5fprefix.zip%22
Please use this CR to introduce the odx file format Since this involves changes only to the Binaries of PARA and the necessary Tools update, this CR can be canceled and the changes will be implemented using the Integration Task. |
|
[QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn "systematic root-cause" should be documented in 3x5 Why, and an improvement idea should be proposed.
This CR is to track the implementation of the systematic improvement Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group. | [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn "systematic root-cause" should be documented in 3x5 Why, and an improvement idea should be proposed.
This CR is to track the implementation of the systematic improvement Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group. |
|
[QA][PA2116][SYS.4][GP.2.1.2][GP.2.1.3][GP.2.1.4][SYS.5][GP.2.1.2][GP.2.1.3]Only Duration estimation mentioned in the MS project plan but not the effort (person days) Update MS Project information according to mentioned points. Update MS project information according to the weekness that ASPICE mentioned. | [QA][PA2116][SYS.4][GP.2.1.2][GP.2.1.3][GP.2.1.4][SYS.5][GP.2.1.2][GP.2.1.3]Only Duration estimation mentioned in the MS project plan but not the effort (person days) Update MS Project information according to mentioned points. Update MS project information according to the weekness that ASPICE mentioned. |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED See description | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED See description |
|
Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR to remove the following fault from the following programs:
A100 PBM, A100 SBM, 31XX:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED
The current plan for release is:
- September 7th for 31XX V05.0 Integ 2
- September 9th for A100 PBM V18.0 Integ 1
- September 16th for A100 SBM V18.0 Integ 1 Duplicate of CR 5449398 | Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults The goal of this CR to remove the following fault from the following programs:
A100 PBM, A100 SBM, 31XX:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED
The current plan for release is:
- September 7th for 31XX V05.0 Integ 2
- September 9th for A100 PBM V18.0 Integ 1
- September 16th for A100 SBM V18.0 Integ 1 Duplicate of CR 5449398 |
|
Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. | Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs. Andrew Berg 07-21-21
Proposed_Changes_v2.zip attached.
QAC Report v2.zip attached.
Test Report v2.docx attached.
Andrew Berg 07-14-21
Proposed_Changes_v1.zip attached.
QAC Report v1.zip attached. |
|
Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED following faults are removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED | Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults Below Fault IDs need to be removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED following faults are removed from the DMT:
GROUND_1_DISCONNECTED
GROUND_2_DISCONNECTED |
|
[OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected SW-Resets due to exceptions in Opel-K0 project and below change was introduced with “ALM_Task 5202634: [OPEL K0] [PSW] Proivde interfaces for Tx signals” where the dataset are not aligned to group ID ordering of CAL sub groups. But addition of new Calibration set for AAW does not match to the group ordering, The group ordering for the AAW calibration set must be changed | [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected SW-Resets due to exceptions in Opel-K0 project and below change was introduced with “ALM_Task 5202634: [OPEL K0] [PSW] Proivde interfaces for Tx signals” where the dataset are not aligned to group ID ordering of CAL sub groups. But addition of new Calibration set for AAW does not match to the group ordering, The group ordering for the AAW calibration set must be changed |
|
[OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected 1) In X300_173 testing within Dry-HIL, UNEXPECTED_EXCEPTION failure was seen directly after switching the gearbox from D to P.
In further investigation it was found that it is caused due to alignment issue within Calibration Data as shown in below snap
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible.
Attached are the correct files. Please check and update the Linker contents. (Took 1.199 opel sandbox as base line for changes) [Saritha Tatipally (Z666542), 24-06-2021]--------------------------------------------------------------------------------
Brief analysis summary: [OPEL K0] Need to have alignment fixed within Calibration Data
--------------------------------------------------------------------------------
It was observed while testing on Dry HIL, UnExpected Exception - ALN error at DEAD Address 0x805C002D which is a odd address of calibration.
So alignment of calibration is needed
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Saritha Tatipally
Proposal of next steps (incl. effort/h and verification): Please create TASK 1
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [OPEL K0] Update calibration Linker with alignment
Description :
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible
Owner: Saritha Tatipally
Reviewer: Dileep
Estimated design effort/h:
Estimated implementation effort/h:4
Estimated unit testing effort/h:2
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date: 05-07-2021
------------------------------------------------------ | [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected 1) In X300_173 testing within Dry-HIL, UNEXPECTED_EXCEPTION failure was seen directly after switching the gearbox from D to P.
In further investigation it was found that it is caused due to alignment issue within Calibration Data as shown in below snap
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible.
Attached are the correct files. Please check and update the Linker contents. (Took 1.199 opel sandbox as base line for changes) [Saritha Tatipally (Z666542), 24-06-2021]--------------------------------------------------------------------------------
Brief analysis summary: [OPEL K0] Need to have alignment fixed within Calibration Data
--------------------------------------------------------------------------------
It was observed while testing on Dry HIL, UnExpected Exception - ALN error at DEAD Address 0x805C002D which is a odd address of calibration.
So alignment of calibration is needed
Risk (low/medium/high): Low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):Saritha Tatipally
Proposal of next steps (incl. effort/h and verification): Please create TASK 1
--------------------------------------------------------------------------------
TASK 1
------------------------------------------------------
Title: [OPEL K0] Update calibration Linker with alignment
Description :
It is identified that there is no alignment set for 'Calibration_Flash_text', 'Calibration_Flash_const_text_0', 'Calibration_Flash_const_text_3', 'Calibration_Flash_data', 'Calibration_Ram'. Hence need to update Calibration linker scripts to have the alignment proper.
2) Seen that SSM_PB_PARAM_CALIBRATION_PTR address is wrongly pointing to 0x805C8198 and this need to be corrected to 0x805BC08C.
3) Also it looks PBC_PARAM_CALIBRATION_PTR is not being used within the App and so it can be cleanedup if possible
Owner: Saritha Tatipally
Reviewer: Dileep
Estimated design effort/h:
Estimated implementation effort/h:4
Estimated unit testing effort/h:2
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date: 05-07-2021
------------------------------------------------------ |
|
[xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM) - This CR is to track the improvement from 3x5Why “systemic leg”
Root cause: Data owner and memory stack service provider are not aligned. ?
Per Stephan Scheider, the process is mature for IBC Gen2 core projects, so called “NVRAM Contracts” in DOORs for each data block. Data owners select appropriate failure correction option for memory stack service provider to implement.
This concept should be investigated - then next steps defined for potential roll-out in North America projects Meeting Minutes: Oct-5
Participants: Mark Hollingsworth, Stephan Scheider
Discussion:
Memory stack is a service provider which must contract with datablock owners and implement according to datablock owner request.
Datablock owners must understand impact of NVRAM failures on their data, and select appropriate failure correction option.
The process is mature as explaind for IBC Gen2 core project:
There are NVRAM contracts in DOORS for each datablock.
The contracts formarlizes key points:
1) who is datablock owner
2) what are requirements for datablock protection
The process is informally handled in most existing projects. Someone in project knows NVRAM and should know data owner counterparts.
Possible improvement is to develop a interview style guidance/questionnaire for datablock owners which is similar to the DOORs contract.
Stephan suggest I contact Mel in ADWC2 to see if he can support. | [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM) - This CR is to track the improvement from 3x5Why “systemic leg”
Root cause: Data owner and memory stack service provider are not aligned. ?
Per Stephan Scheider, the process is mature for IBC Gen2 core projects, so called “NVRAM Contracts” in DOORs for each data block. Data owners select appropriate failure correction option for memory stack service provider to implement.
This concept should be investigated - then next steps defined for potential roll-out in North America projects Meeting Minutes: Oct-5
Participants: Mark Hollingsworth, Stephan Scheider
Discussion:
Memory stack is a service provider which must contract with datablock owners and implement according to datablock owner request.
Datablock owners must understand impact of NVRAM failures on their data, and select appropriate failure correction option.
The process is mature as explaind for IBC Gen2 core project:
There are NVRAM contracts in DOORS for each datablock.
The contracts formarlizes key points:
1) who is datablock owner
2) what are requirements for datablock protection
The process is informally handled in most existing projects. Someone in project knows NVRAM and should know data owner counterparts.
Possible improvement is to develop a interview style guidance/questionnaire for datablock owners which is similar to the DOORs contract.
Stephan suggest I contact Mel in ADWC2 to see if he can support. |
|
[xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM) - Improvement to detect identical failure in the plant is described in 3x5 Why.
"Modify EOL test to add power cycle..." EOL test was updated and verified.
This CR is created later to track the improvements via QRCM dashboard | [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM) - Improvement to detect identical failure in the plant is described in 3x5 Why.
"Modify EOL test to add power cycle..." EOL test was updated and verified.
This CR is created later to track the improvements via QRCM dashboard |
|
18A incorrect in ESLM data package nan One task for PXX team to implement the fix
2021-08-04 StolarsK:
Fix was implemented. CR can be closed. | 18A incorrect in ESLM data package nan One task for PXX team to implement the fix
2021-08-04 StolarsK:
Fix was implemented. CR can be closed. |
|
[QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX Due to Resource constraints TSC and System Baseline updates could not be supported at the respective S Gates originally planned.
Agreed that these items should be re-planned to align with S200 (Depending allocation of Resource).
It was noted that System Baseline should not be expected to be delivered at S120 as this requires full confirmation of the TSC attributes and this can not be achieved at this early stage of a project.
This CR has been created specifically to cover following SE/PIL activities:
WPr#55 - TSC Baseline and confirmation [Defered from S120]. Refer to original S120 ALM_Task 5406385.
WPr#31 - System Baseline [Deferred from S120 as can not be completed until TSC has been reviewed and attributes set]. Refer to original S110 ALM_Task 5405979 .
In addition to above PM to raise Action related to:
With Quality consent; update the PV03 WPP to record re-planning of these work products. In addition raise Clarity Risk against the Resource constraints for the PIL/SE role.
Identify on the associated Tasks the target dates for the re-planned Work Products. *
2021-10-05 SINGHR9
*
Related Tasks have been completed and Work Products Delivered.
S200 to be run and checklist is managed separate to this CR.
*
2021-07-07 SINGHR9
Re-plan of key Work Products documented in related ALM_Action 5481501.
Proceed to create tasks for S200 for:
WPr#55 - TSC Baseline and confirmation
WPr#31 - System Baseline | [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX Due to Resource constraints TSC and System Baseline updates could not be supported at the respective S Gates originally planned.
Agreed that these items should be re-planned to align with S200 (Depending allocation of Resource).
It was noted that System Baseline should not be expected to be delivered at S120 as this requires full confirmation of the TSC attributes and this can not be achieved at this early stage of a project.
This CR has been created specifically to cover following SE/PIL activities:
WPr#55 - TSC Baseline and confirmation [Defered from S120]. Refer to original S120 ALM_Task 5406385.
WPr#31 - System Baseline [Deferred from S120 as can not be completed until TSC has been reviewed and attributes set]. Refer to original S110 ALM_Task 5405979 .
In addition to above PM to raise Action related to:
With Quality consent; update the PV03 WPP to record re-planning of these work products. In addition raise Clarity Risk against the Resource constraints for the PIL/SE role.
Identify on the associated Tasks the target dates for the re-planned Work Products. *
2021-10-05 SINGHR9
*
Related Tasks have been completed and Work Products Delivered.
S200 to be run and checklist is managed separate to this CR.
*
2021-07-07 SINGHR9
Re-plan of key Work Products documented in related ALM_Action 5481501.
Proceed to create tasks for S200 for:
WPr#55 - TSC Baseline and confirmation
WPr#31 - System Baseline |
|
[QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project Due to Resource constraints TSC and System Baseline updates could not be supported at the respective S Gates originally planned.
Agreed that these items should be re-planned to align with S200 (Depending allocation of Resource).
It was noted that System Baseline should not be expected to be delivered at S120 as this requires full confirmation of the TSC attributes and this can not be achieved at this early stage of a project.
This CR has been created specifically to cover following SE/PIL activities:
WPr#55 - TSC Baseline and confirmation [Defered from S120]. Refer to original S120 ALM_Task 5406385.
WPr#31 - System Baseline [Deferred from S120 as can not be completed until TSC has been reviewed and attributes set]. Refer to original S110 ALM_Task 5405979 .
In addition to above PM to raise Action related to:
With Quality consent; update the PV03 WPP to record re-planning of these work products. In addition raise Clarity Risk against the Resource constraints for the PIL/SE role.
Identify on the associated Tasks the target dates for the re-planned Work Products. *
2021-10-05 SINGHR9
*
Related Tasks have been completed and Work Products Delivered.
S200 to be run and checklist is managed separate to this CR.
*
2021-07-07 SINGHR9
Re-plan of key Work Products documented in related ALM_Action 5481501.
Proceed to create tasks for S200 for:
WPr#55 - TSC Baseline and confirmation
WPr#31 - System Baseline | [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project Due to Resource constraints TSC and System Baseline updates could not be supported at the respective S Gates originally planned.
Agreed that these items should be re-planned to align with S200 (Depending allocation of Resource).
It was noted that System Baseline should not be expected to be delivered at S120 as this requires full confirmation of the TSC attributes and this can not be achieved at this early stage of a project.
This CR has been created specifically to cover following SE/PIL activities:
WPr#55 - TSC Baseline and confirmation [Defered from S120]. Refer to original S120 ALM_Task 5406385.
WPr#31 - System Baseline [Deferred from S120 as can not be completed until TSC has been reviewed and attributes set]. Refer to original S110 ALM_Task 5405979 .
In addition to above PM to raise Action related to:
With Quality consent; update the PV03 WPP to record re-planning of these work products. In addition raise Clarity Risk against the Resource constraints for the PIL/SE role.
Identify on the associated Tasks the target dates for the re-planned Work Products. *
2021-10-05 SINGHR9
*
Related Tasks have been completed and Work Products Delivered.
S200 to be run and checklist is managed separate to this CR.
*
2021-07-07 SINGHR9
Re-plan of key Work Products documented in related ALM_Action 5481501.
Proceed to create tasks for S200 for:
WPr#55 - TSC Baseline and confirmation
WPr#31 - System Baseline |
|
[Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task Please verify that the provided MCP values are now correct. CR will be shifted to 260_000 sw | [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task Please verify that the provided MCP values are now correct. CR will be shifted to 260_000 sw |
|
[Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task - In Daimler MMA, Pedal Travel sensor, Pressure sensor and BFL Sensor connected Via SENT need to sampled every 1ms, Currently sampled every 5 ms.
- It shall be discussed with Geelay as a base, Task scheduling need to adapted for SENT sensor to fit in Daimler MMA environment.
Note: MPS sensor is not in scope. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Pedal Travel sensor, Pressure sensor and BFL Sensor - along with SENT Handler - shall be executed every 1ms (instead of 5ms).
See attachments for email thread.
2021-07-15 [SwAD] C. Klukowski: The order of the function calls can be taken over from Platform SW, if the information from the email is not sufficient.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Create specified tasks
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [Os] - Update Lsm for Pressure Sensor and BFL Sensor
Description:
UpdateSentHandler, UpdatePedalTravelSensor do not have LSM waypoints (ignore these).
Owner: Matthew Rivers
Reviewer: Lea Friedmann
Estimated design effort/h:
Estimated implementation effort/h: 4
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 16.07.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. PTS, Pressure Sensor
Description:
PTS, Pressure Sensor shall be executed every 1ms (instead of 5ms)
Owner: Carsten Broehl
Reviewer: Krishna Shanmugam
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. SENT Handler
Description:
SENT Handler shall be executed every 1ms (instead of 5ms)
Owner: Krishna Shanmugam
Reviewer: Carsten Broehl
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. Brake Fluid Level Sensor
Description:
Brake Fluid Level Sensor shall be executed every 1ms (instead of 5ms)
Owner: Peter Baumgartner
Reviewer: Krishna Shanmugam
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [Autosar] - Map PTS, Pressure sensor, SENT Handler, and BFL Sensor to the 1ms task
Description:
Runnables shall be executed as follows (in this order):
And inserted here (directly after UpdateAnalogSignalsFastTask):
Owner: Sireesha
Reviewer: Jochen Wagner
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------ | [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task - In Daimler MMA, Pedal Travel sensor, Pressure sensor and BFL Sensor connected Via SENT need to sampled every 1ms, Currently sampled every 5 ms.
- It shall be discussed with Geelay as a base, Task scheduling need to adapted for SENT sensor to fit in Daimler MMA environment.
Note: MPS sensor is not in scope. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Pedal Travel sensor, Pressure sensor and BFL Sensor - along with SENT Handler - shall be executed every 1ms (instead of 5ms).
See attachments for email thread.
2021-07-15 [SwAD] C. Klukowski: The order of the function calls can be taken over from Platform SW, if the information from the email is not sufficient.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Create specified tasks
--------------------------------------------------------------------------------
TASK
------------------------------------------------------
Title: [Os] - Update Lsm for Pressure Sensor and BFL Sensor
Description:
UpdateSentHandler, UpdatePedalTravelSensor do not have LSM waypoints (ignore these).
Owner: Matthew Rivers
Reviewer: Lea Friedmann
Estimated design effort/h:
Estimated implementation effort/h: 4
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 4
[Optional] Planned completion date: 16.07.2021
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. PTS, Pressure Sensor
Description:
PTS, Pressure Sensor shall be executed every 1ms (instead of 5ms)
Owner: Carsten Broehl
Reviewer: Krishna Shanmugam
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. SENT Handler
Description:
SENT Handler shall be executed every 1ms (instead of 5ms)
Owner: Krishna Shanmugam
Reviewer: Carsten Broehl
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [EcuAl] - Update DaVinci Developer w.r.t. Brake Fluid Level Sensor
Description:
Brake Fluid Level Sensor shall be executed every 1ms (instead of 5ms)
Owner: Peter Baumgartner
Reviewer: Krishna Shanmugam
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------
TASK
------------------------------------------------------
Title: [Autosar] - Map PTS, Pressure sensor, SENT Handler, and BFL Sensor to the 1ms task
Description:
Runnables shall be executed as follows (in this order):
And inserted here (directly after UpdateAnalogSignalsFastTask):
Owner: Sireesha
Reviewer: Jochen Wagner
Estimated design effort/h:
Estimated implementation effort/h:
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h:
[Optional] Planned completion date:
------------------------------------------------------ |
|
[Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task [Carsten Broehl (BroehlC), 29-06-2021 13:20]
------------------------------------------------------------------
On IBN Hil it was found that the pressure sensor signal contains wrong (to high) pressure values, while brake pedal is not applied.
Deactivation of the filter function of the press sensor solved the problem.
But it turned out that the filter function was called from the wrong update task.
[Carsten Broehl (BroehlC), 30-06-2021 10:35]
------------------------------------------------------------------
Pressure sensor value is to high, when brake is not applied:
Issue for this behavior is that the update function for the filtered value is called in the same loop with the normal update routine.
The call of the UpdatePressureSensorFiltered function needs to be called from the 1ms Task.
[Carsten Broehl (BroehlC), 09-07-2021 09:55]
------------------------------------------------------------------
The Update function of Update PressureSensor needs to be moved to the 1m Task too: [Carsten Broehl (BroehlC), 03-08-2021 15:41]
------------------------------------------------------------------
Changes were done with CR 5514413 -> please reject CR | [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task [Carsten Broehl (BroehlC), 29-06-2021 13:20]
------------------------------------------------------------------
On IBN Hil it was found that the pressure sensor signal contains wrong (to high) pressure values, while brake pedal is not applied.
Deactivation of the filter function of the press sensor solved the problem.
But it turned out that the filter function was called from the wrong update task.
[Carsten Broehl (BroehlC), 30-06-2021 10:35]
------------------------------------------------------------------
Pressure sensor value is to high, when brake is not applied:
Issue for this behavior is that the update function for the filtered value is called in the same loop with the normal update routine.
The call of the UpdatePressureSensorFiltered function needs to be called from the 1ms Task.
[Carsten Broehl (BroehlC), 09-07-2021 09:55]
------------------------------------------------------------------
The Update function of Update PressureSensor needs to be moved to the 1m Task too: [Carsten Broehl (BroehlC), 03-08-2021 15:41]
------------------------------------------------------------------
Changes were done with CR 5514413 -> please reject CR |
|
[Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task [Carsten Broehl (BroehlC), 16-07-2021 14:13]
------------------------------------------------------------------
Changes implemented with CR 5419359.
CR rejected
[Carsten Broehl (BroehlC), 29-06-2021 13:20]
------------------------------------------------------------------
On IBN Hil it was found that the pressure sensor signal contains wrong (to high) pressure values, while brake pedal is not applied.
Deactivation of the filter function of the press sensor solved the problem.
But it turned out that the filter function was called from the wrong update task.
Please analyze if the pressure sensor filter is working correctly if the filtered update function is called from the 1 ms Task.
[Carsten Broehl (BroehlC), 09-07-2021 09:56]
------------------------------------------------------------------
The Update Presens function will be called from 1 ms instead of 5 ms please adapt the Pressursensor cfg to enable 1ms functionality [Carsten Broehl (BroehlC), 16-07-2021 14:13]
------------------------------------------------------------------
Changes implemented with CR 5419359.
CR rejected | [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task [Carsten Broehl (BroehlC), 16-07-2021 14:13]
------------------------------------------------------------------
Changes implemented with CR 5419359.
CR rejected
[Carsten Broehl (BroehlC), 29-06-2021 13:20]
------------------------------------------------------------------
On IBN Hil it was found that the pressure sensor signal contains wrong (to high) pressure values, while brake pedal is not applied.
Deactivation of the filter function of the press sensor solved the problem.
But it turned out that the filter function was called from the wrong update task.
Please analyze if the pressure sensor filter is working correctly if the filtered update function is called from the 1 ms Task.
[Carsten Broehl (BroehlC), 09-07-2021 09:56]
------------------------------------------------------------------
The Update Presens function will be called from 1 ms instead of 5 ms please adapt the Pressursensor cfg to enable 1ms functionality [Carsten Broehl (BroehlC), 16-07-2021 14:13]
------------------------------------------------------------------
Changes implemented with CR 5419359.
CR rejected |
|
[Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >
Platztest - ECU standalone
Diagnose via Monaco 9.02
Restbussimulation via CANoe 14.0: Kl.15=on, Ubat=12V, VIN=?????????????????, Odo=30km, v=0km/h, Eng_RPM=0;
DiVa 14.0 SP2 Testpattern v1.6.00100
Monaco-OTX: DDS2020_V1_01_000
Act: Action, was wurde gemacht als das Verhalten auftrat? >
DIAGSERVICE [ChangeAuthenticatedState]
Backend_CA_Certificate_Identification_Read PDU [22 01 82]
Beh: Behavior, was ist passiert? >
Negative response received Backend_CA_Certificate_Identification_Read PDU [22 01 82] > [7F 22 10] General Reject
Implementation not available as per B1 content definition agreed with the customer__
--> STARC Issued created for RD/CUU Tracking!
Attachment:
[MMA_B1_Customer_Test_Results_v1.1.zip|CB:/displayDocument/MMA_B1_Customer_Test_Results_v1.1.zip?task_id=1108749&artifact_id=7375579] Tasks are raised to formalize the changes as per the prototype.
CR can be moved to Analysed | [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >
Platztest - ECU standalone
Diagnose via Monaco 9.02
Restbussimulation via CANoe 14.0: Kl.15=on, Ubat=12V, VIN=?????????????????, Odo=30km, v=0km/h, Eng_RPM=0;
DiVa 14.0 SP2 Testpattern v1.6.00100
Monaco-OTX: DDS2020_V1_01_000
Act: Action, was wurde gemacht als das Verhalten auftrat? >
DIAGSERVICE [ChangeAuthenticatedState]
Backend_CA_Certificate_Identification_Read PDU [22 01 82]
Beh: Behavior, was ist passiert? >
Negative response received Backend_CA_Certificate_Identification_Read PDU [22 01 82] > [7F 22 10] General Reject
Implementation not available as per B1 content definition agreed with the customer__
--> STARC Issued created for RD/CUU Tracking!
Attachment:
[MMA_B1_Customer_Test_Results_v1.1.zip|CB:/displayDocument/MMA_B1_Customer_Test_Results_v1.1.zip?task_id=1108749&artifact_id=7375579] Tasks are raised to formalize the changes as per the prototype.
CR can be moved to Analysed |
|
[Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >
Platztest - ECU standalone
Diagnose via Monaco 9.02
Restbussimulation via CANoe 14.0: Kl.15=on, Ubat=12V, VIN=?????????????????, Odo=30km, v=0km/h, Eng_RPM=0;
DiVa 14.0 SP2 Testpattern v1.6.00100
Monaco-OTX: DDS2020_V1_01_000
Act: Action, was wurde gemacht als das Verhalten auftrat? >
DIAGSERVICE [ChangeAuthenticatedState]
Backend_CA_Certificate_Identification_Read PDU [22 01 82]
Beh: Behavior, was ist passiert? >
Negative response received Backend_CA_Certificate_Identification_Read PDU [22 01 82] > [7F 22 10] General Reject
Implementation not available as per B1 content definition agreed with the customer__
--> STARC Issued created for RD/CUU Tracking!
Attachment:
[MMA_B1_Customer_Test_Results_v1.1.zip|CB:/displayDocument/MMA_B1_Customer_Test_Results_v1.1.zip?task_id=1108749&artifact_id=7375579] Tasks are raised to formalize the changes as per the prototype.
CR can be moved to Analysed | [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >
Platztest - ECU standalone
Diagnose via Monaco 9.02
Restbussimulation via CANoe 14.0: Kl.15=on, Ubat=12V, VIN=?????????????????, Odo=30km, v=0km/h, Eng_RPM=0;
DiVa 14.0 SP2 Testpattern v1.6.00100
Monaco-OTX: DDS2020_V1_01_000
Act: Action, was wurde gemacht als das Verhalten auftrat? >
DIAGSERVICE [ChangeAuthenticatedState]
Backend_CA_Certificate_Identification_Read PDU [22 01 82]
Beh: Behavior, was ist passiert? >
Negative response received Backend_CA_Certificate_Identification_Read PDU [22 01 82] > [7F 22 10] General Reject
Implementation not available as per B1 content definition agreed with the customer__
--> STARC Issued created for RD/CUU Tracking!
Attachment:
[MMA_B1_Customer_Test_Results_v1.1.zip|CB:/displayDocument/MMA_B1_Customer_Test_Results_v1.1.zip?task_id=1108749&artifact_id=7375579] Tasks are raised to formalize the changes as per the prototype.
CR can be moved to Analysed |
|
[Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working Please integrate HSM into application in order to support the security features defined in the parent OP
Customer requirements:
/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/c_Fachinhalte/Basisfunktionen/Security/EBS_Security
DCRP- Link:
\BRK\Customer\Daimler\MMA\IBC\02_Project_Management\01_Planning\01_System\IBC Gen2_BRK_MB_MMA_DCRP.xlsx
Internal Milestone DV 2021-12-03 SANSOMEM:
All tasks are complete. CR to be closed.
2021-10-04 SansomeM:
Integration of HSM driver to the Application requires:
- Crypto_30_vHsm module to be added to DaVinci configuration
- RTE update for Crypto_30_vHsm_MainFunction
- OS updates for Main Function task and additional updates required from SSA testing
- EcuM update for Crypto_30_vHsm_Init function
- Build updates for Partitioning Wizard, Compiler_Cfg.h, build configuration in INI file
Where this implementation is outside of the security team tasks will be raised for the relevant teams.
ECUC and GenCode zip files from the working prototype have been added to Attachments.
Prototype, ECU level testing, with these changes implemented and HSM disabled shows no adverse affect on the rest of the application SW performance. | [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working Please integrate HSM into application in order to support the security features defined in the parent OP
Customer requirements:
/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/c_Fachinhalte/Basisfunktionen/Security/EBS_Security
DCRP- Link:
\BRK\Customer\Daimler\MMA\IBC\02_Project_Management\01_Planning\01_System\IBC Gen2_BRK_MB_MMA_DCRP.xlsx
Internal Milestone DV 2021-12-03 SANSOMEM:
All tasks are complete. CR to be closed.
2021-10-04 SansomeM:
Integration of HSM driver to the Application requires:
- Crypto_30_vHsm module to be added to DaVinci configuration
- RTE update for Crypto_30_vHsm_MainFunction
- OS updates for Main Function task and additional updates required from SSA testing
- EcuM update for Crypto_30_vHsm_Init function
- Build updates for Partitioning Wizard, Compiler_Cfg.h, build configuration in INI file
Where this implementation is outside of the security team tasks will be raised for the relevant teams.
ECUC and GenCode zip files from the working prototype have been added to Attachments.
Prototype, ECU level testing, with these changes implemented and HSM disabled shows no adverse affect on the rest of the application SW performance. |
|
[Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working Please implement Feature: SW 1.2 Cyber-Security - B1.1
Customer Featurename:
Customer requirements:
/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/c_Fachinhalte/Basisfunktionen/Security/EBS_Security
DCRP- Link:
\BRK\Customer\Daimler\MMA\IBC\02_Project_Management\01_Planning\01_System\IBC Gen2_BRK_MB_MMA_DCRP.xlsx
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1.1
This CR is to analyze the Trust Model customer requirements, create an impact analysis and determin the resulting CRs required to meet the requirements. ShembekS 0./12/2021 :
As all the Tasks under this CR are now completed. We can close this CR.
Hari Krishna E 15/04/2021:
this CR purpose is to perform the Impact analysis for New ECU Trust Model or Unique ECU ID Chain of trust
this Trust model creates new Chain of Trust for ECUs
• Each ECU will generate its own unique ECU private keys
• All certificates are signed at Daimler ? The suppliers do not need to sign certificates
• Trust Model chain of trust certificates will be injected during Daimler production / After sale process
• The Trust model is supported by ECUs with SSA version 3.x and above
Process to create unique ECU ID chain in development phase and required test steps using the Customer tool/Scripts
1. ECU Create Private & Public Key (on the HSM)
2. ECU Verify keys
3. ECU Create CSR (trigger by Diagnostics)
4. Check CSR (read by Diagnostics & check using customer scripts/NEST)
5. Sign CSR- create ECU certificate & Inject Trust model chain (this step is for test purpose only using customer scripts/NEST)
6. ECU is ready for dispatch
Pre-cond: SSA shall be integrated and trust model related Diag services are available
@CCB, to implement these steps, one CR is required for Security team for the analysis of steps in detai l and to propose integration tasks
Hari Krishna E 28/04/2021:
@CCB, to implement these steps, vector HSM sw provides the necessary Crypto primitives with PKI Key generation option.
hence a SW level implementation/integration details against the mentioned steps has to be investigated (e.g. vHSM technical ref) and required tasks shall be proposed
accordingly, the CR is set to Sw Security.
2021-05-06 SansomeM:
Analysis for SW implementation of the ECU ID Chain of the Trust Model, as described above.
Additional step to configure KeyM component
- Refer to section 4.15 AUTOSAR KeyM configuration in Integration information SSA (from Daimler) document
Task Overview:
- Configure Autosar KeyM for the ECU Trust Model in Host
Estimate: 5 days
1. ECU Create Private & Public Key (on the HSM)
- Question for Vector: Only the ED25519 is available, ED25519ph is not available as a primitive
- Csm Job: Ssa_SigGenerate_PrivateEcuKey
- Csm Prim: SigGenEd25519
- Csm Key: Ssa_PrivateEcuKey
- Crypto (vHSM) Key: Ssa_PrivateEcuKey
- Type: Crypto_30_LibCv_Ssa_TrustModelEcuPrivateKey
- Element: Ssa_TrustModelEcuPrivateKey
- Csm Queue: Needs to be created
- CryIf Channel: Needs to be created
Public key job not required, the primitive ED25519 will create both private and public.
Task Overview: Ssa_KeyM/Csm/CryIf configuration in Host
Estimate: 2 days
2. ECU Verify keys
- Use Csm Key 'Ssa_SignatureRamKey' to load the correct CSM key
- Interface: 'Key_SignatureRamKey'
- Use Csm Job 'Ssa_SigVerify_RamKey' via port from Ssa_KeyM
- Interface: 'CsmSignatureVerify'
- To ensure the sufficient understanding of this work flow to realise the specs, flow/sequence diagram will be created
Task Overview:
- Flow/Sequence Diagram for Verify Keys
- Ssa_KeyM/Csm/CryIf configuration in Host
Estimate: 3 days
3. ECU Create CSR (trigger by Diagnostics)
- Question for Vector: Crypto Primitive 'KeyM_InitCSR' is part of Crypto_30_KeyM, but if this is selected in Crypto_30_vHsm_KeyManagement the only Primitive Ref is '/ActiveEcuC/Crypto_vHSM/CryptoPrimitives/vHsmUsageForbidden'
- Assumption is that the 'Create CSR' functionality that will be triggered by the Diagnostic request 'Trust Model ECU CSR" (DID 0x019A)' is already implemented in SSA.
Task Overview:
- Understanding & Setup of 'ECU Init CSR' (see 'Figure SSA-IS-2452: Process to create ECU CSR' in MSS10815)
- Provide diagnostic interfaces for CSR DID request
- Integration & Testing (assumption is that Create CSR is implemented)
Estimate: 6 days
4. Check CSR (read by Diagnostics & check using customer scripts/NEST)
Task is for testing purposes, out of scope of SW development
5. Sign CSR- create ECU certificate & Inject Trust model chain (this step is for test purpose only using customer scripts/NEST)
Task is for testing purposes, out of scope of SW development | [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working Please implement Feature: SW 1.2 Cyber-Security - B1.1
Customer Featurename:
Customer requirements:
/P_DAI_MMA_IBC/10 External Specifications/Customer Specifications/MMA/c_Fachinhalte/Basisfunktionen/Security/EBS_Security
DCRP- Link:
\BRK\Customer\Daimler\MMA\IBC\02_Project_Management\01_Planning\01_System\IBC Gen2_BRK_MB_MMA_DCRP.xlsx
Maturity Level: ML1 / Note Basic Technology Rollout Plan (BROP) - Milestone B1.1
This CR is to analyze the Trust Model customer requirements, create an impact analysis and determin the resulting CRs required to meet the requirements. ShembekS 0./12/2021 :
As all the Tasks under this CR are now completed. We can close this CR.
Hari Krishna E 15/04/2021:
this CR purpose is to perform the Impact analysis for New ECU Trust Model or Unique ECU ID Chain of trust
this Trust model creates new Chain of Trust for ECUs
• Each ECU will generate its own unique ECU private keys
• All certificates are signed at Daimler ? The suppliers do not need to sign certificates
• Trust Model chain of trust certificates will be injected during Daimler production / After sale process
• The Trust model is supported by ECUs with SSA version 3.x and above
Process to create unique ECU ID chain in development phase and required test steps using the Customer tool/Scripts
1. ECU Create Private & Public Key (on the HSM)
2. ECU Verify keys
3. ECU Create CSR (trigger by Diagnostics)
4. Check CSR (read by Diagnostics & check using customer scripts/NEST)
5. Sign CSR- create ECU certificate & Inject Trust model chain (this step is for test purpose only using customer scripts/NEST)
6. ECU is ready for dispatch
Pre-cond: SSA shall be integrated and trust model related Diag services are available
@CCB, to implement these steps, one CR is required for Security team for the analysis of steps in detai l and to propose integration tasks
Hari Krishna E 28/04/2021:
@CCB, to implement these steps, vector HSM sw provides the necessary Crypto primitives with PKI Key generation option.
hence a SW level implementation/integration details against the mentioned steps has to be investigated (e.g. vHSM technical ref) and required tasks shall be proposed
accordingly, the CR is set to Sw Security.
2021-05-06 SansomeM:
Analysis for SW implementation of the ECU ID Chain of the Trust Model, as described above.
Additional step to configure KeyM component
- Refer to section 4.15 AUTOSAR KeyM configuration in Integration information SSA (from Daimler) document
Task Overview:
- Configure Autosar KeyM for the ECU Trust Model in Host
Estimate: 5 days
1. ECU Create Private & Public Key (on the HSM)
- Question for Vector: Only the ED25519 is available, ED25519ph is not available as a primitive
- Csm Job: Ssa_SigGenerate_PrivateEcuKey
- Csm Prim: SigGenEd25519
- Csm Key: Ssa_PrivateEcuKey
- Crypto (vHSM) Key: Ssa_PrivateEcuKey
- Type: Crypto_30_LibCv_Ssa_TrustModelEcuPrivateKey
- Element: Ssa_TrustModelEcuPrivateKey
- Csm Queue: Needs to be created
- CryIf Channel: Needs to be created
Public key job not required, the primitive ED25519 will create both private and public.
Task Overview: Ssa_KeyM/Csm/CryIf configuration in Host
Estimate: 2 days
2. ECU Verify keys
- Use Csm Key 'Ssa_SignatureRamKey' to load the correct CSM key
- Interface: 'Key_SignatureRamKey'
- Use Csm Job 'Ssa_SigVerify_RamKey' via port from Ssa_KeyM
- Interface: 'CsmSignatureVerify'
- To ensure the sufficient understanding of this work flow to realise the specs, flow/sequence diagram will be created
Task Overview:
- Flow/Sequence Diagram for Verify Keys
- Ssa_KeyM/Csm/CryIf configuration in Host
Estimate: 3 days
3. ECU Create CSR (trigger by Diagnostics)
- Question for Vector: Crypto Primitive 'KeyM_InitCSR' is part of Crypto_30_KeyM, but if this is selected in Crypto_30_vHsm_KeyManagement the only Primitive Ref is '/ActiveEcuC/Crypto_vHSM/CryptoPrimitives/vHsmUsageForbidden'
- Assumption is that the 'Create CSR' functionality that will be triggered by the Diagnostic request 'Trust Model ECU CSR" (DID 0x019A)' is already implemented in SSA.
Task Overview:
- Understanding & Setup of 'ECU Init CSR' (see 'Figure SSA-IS-2452: Process to create ECU CSR' in MSS10815)
- Provide diagnostic interfaces for CSR DID request
- Integration & Testing (assumption is that Create CSR is implemented)
Estimate: 6 days
4. Check CSR (read by Diagnostics & check using customer scripts/NEST)
Task is for testing purposes, out of scope of SW development
5. Sign CSR- create ECU certificate & Inject Trust model chain (this step is for test purpose only using customer scripts/NEST)
Task is for testing purposes, out of scope of SW development |
|
[Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working This CR shall be used:
1. to export a DEXT file for the X0260 diagnostic variant out of the CDD (Diag team)
2. to export the Ecu Individual ACL file for the X0260 diagnostic variant out of the CDD (Diag team)
3. to import the DEXT file into the Vector DaVinci toolchain and to update the Dcm configuration (Diag team)
4. to integrate the Ecu Individual ACL file into the SW (Security team)
5. to generate the system / Autosar SW (Autosar team)
Please, note that Diag team needs to check (and adapt if necessary) that the "ASR3 Legacy Combine DID" attribute is set correctly set. It needs to be ensure that only one callout is generate per a DID that is implemented by the Diagnostic Application itself.
Please, ensure that SwAD is informed about the new RTE interfaces.
Deadlines:
1. Clarification of the content with the customer till August 19. => ALM_Change Request 5631911
2. CDD update on ZF side till August 24. => ALM_Change Request 5631911
3. Security related CDD update by customer till August 27. => ALM_Change Request 5631911
4. CDD import after KM update from August 27 till September 03. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Firoz Kizhakke Mukkat 31.08.2021:
This CR shall be used to import the DEXT file into Davinci Configurator, configure DCM, update Diag SWC with required ports and runnables for the newly added Diag jobs.
This CR shall also be used to update the ACL configuration and SCN DID related memory block configuration (if required) by SSA.
The DEXT file is generated out of the new CDD and is checked with the CR 5631911. This DEXT file shall be used here.
As a special case, for X0260 software, the DXT file import into the tool shall be done together with K-Matrix update (CR 5620681) in order to speed up the process to save the development time.
But the related activities like configuring port types in Dcm, creating ports and runnables in Diag SWC, port connection and task mapping, RTE generation for the new diagnostic jobs shall be done with this CR.
Following Diagnostic jobs will be added with the new DEXT file:
Application DIDs:
$22 20 43 Deactivate_Speed_Limit_Read
$2E 20 43 Deactivate_Speed_Limit_Write
$22 20 90 Adaptions_Read
$22 C0 02 Activation_Status_of_Permanent_DTCs_Read
$22 F1 94 SystemSupplierECUSoftwareNumber_Read
$22 F1 95 SystemSupplierECUSoftwareVersionNumber_Read
$22 FD 01 ZF_UCI_Mode_Read
$2E FD 01 ZF_UCI_Mode_Write
$22 20 06 Vehicle_Speed_Read
SCN (Variant Coding) DIDs:
$22 22 01 Vehicle_Information_Read
$2E 22 01 Vehicle_Information_Write
$22 22 02 Switches_Read
$2E 22 02 Switches_Write
$22 22 03 Physical_Parameters_Read
$2E 22 03 Physical_Parameters_Write
Routine Control jobs:
$31 01 30 50 Sensor_Cluster_Calibration_Start
$31 01 05 00 Activation_Status_of_Permanent_DTCs_Start
$31 01 FD 10 ZF_Valves_Test_Start
$31 02 FD 10 ZF_Valves_Test_Stop
$31 03 FD 10 ZF_Valves_Test_RequestResults
The server runnables (callouts) shall be stubbed in DiagArAdapter_Cfg.c file. Implementation each DIDs/RIDs will be taken care by the corresponding implementation CR(which are already linked to the 'Required For' relationships to this CR )
The SWE1 and SWE2 tasks are not required for this CR. The SWE1 and SWE2 updates for the newly added diagnostic jobs will be done with the corresponding DID/RID implementation CRs.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK DIAG
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0260] Import DEXT file and update Dcm and Diag Swc configuration
Description: Please use this task to configure the port types in Dcm, create ports and implement runnables in Diag SWC.
The list of newly added diagnostic jobs are mentioned in the CR analysis.
Owner: Firoz KizhakkeMukkat
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h: 16
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 16
[Optional] Planned completion date:
------------------------------------------------------
TASK Cyber Security
------------------------------------------------------
Title: [MMA][Security][X0260] Use the new ACL file to update the ACL configuration in SSA
Description: Please use the attached ACL file generated out of latest CDD for X0260 and update the ACL configuration in SSA.
Additionally please do the necessary changes regarding the SCN DID related memory block configuration (if required).
The list of newly added SCN diagnostic jobs are mentioned in the CR analysis.
Owner: Suyash Shembekar
Reviewer: Shwetanshu Kukreti
Estimated design effort/h:
Estimated implementation effort/h: 7
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK Bsw_Autocore
------------------------------------------------------
Title: [MMA][Bsw_Autocore][X0260] DEXT Import: Connect ports, task mapping and generate RTE.
Description: Please use the attached modified arxml files.
This task shall be used to connect the new ports, task mapping to runnbales and generate RTE.
Please use the Task_DiagEvents_D_C0_2 for task mapping. The slot number is irrelevant.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana
Estimated design effort/h:
Estimated implementation effort/h: 7
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------ | [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working This CR shall be used:
1. to export a DEXT file for the X0260 diagnostic variant out of the CDD (Diag team)
2. to export the Ecu Individual ACL file for the X0260 diagnostic variant out of the CDD (Diag team)
3. to import the DEXT file into the Vector DaVinci toolchain and to update the Dcm configuration (Diag team)
4. to integrate the Ecu Individual ACL file into the SW (Security team)
5. to generate the system / Autosar SW (Autosar team)
Please, note that Diag team needs to check (and adapt if necessary) that the "ASR3 Legacy Combine DID" attribute is set correctly set. It needs to be ensure that only one callout is generate per a DID that is implemented by the Diagnostic Application itself.
Please, ensure that SwAD is informed about the new RTE interfaces.
Deadlines:
1. Clarification of the content with the customer till August 19. => ALM_Change Request 5631911
2. CDD update on ZF side till August 24. => ALM_Change Request 5631911
3. Security related CDD update by customer till August 27. => ALM_Change Request 5631911
4. CDD import after KM update from August 27 till September 03. --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Firoz Kizhakke Mukkat 31.08.2021:
This CR shall be used to import the DEXT file into Davinci Configurator, configure DCM, update Diag SWC with required ports and runnables for the newly added Diag jobs.
This CR shall also be used to update the ACL configuration and SCN DID related memory block configuration (if required) by SSA.
The DEXT file is generated out of the new CDD and is checked with the CR 5631911. This DEXT file shall be used here.
As a special case, for X0260 software, the DXT file import into the tool shall be done together with K-Matrix update (CR 5620681) in order to speed up the process to save the development time.
But the related activities like configuring port types in Dcm, creating ports and runnables in Diag SWC, port connection and task mapping, RTE generation for the new diagnostic jobs shall be done with this CR.
Following Diagnostic jobs will be added with the new DEXT file:
Application DIDs:
$22 20 43 Deactivate_Speed_Limit_Read
$2E 20 43 Deactivate_Speed_Limit_Write
$22 20 90 Adaptions_Read
$22 C0 02 Activation_Status_of_Permanent_DTCs_Read
$22 F1 94 SystemSupplierECUSoftwareNumber_Read
$22 F1 95 SystemSupplierECUSoftwareVersionNumber_Read
$22 FD 01 ZF_UCI_Mode_Read
$2E FD 01 ZF_UCI_Mode_Write
$22 20 06 Vehicle_Speed_Read
SCN (Variant Coding) DIDs:
$22 22 01 Vehicle_Information_Read
$2E 22 01 Vehicle_Information_Write
$22 22 02 Switches_Read
$2E 22 02 Switches_Write
$22 22 03 Physical_Parameters_Read
$2E 22 03 Physical_Parameters_Write
Routine Control jobs:
$31 01 30 50 Sensor_Cluster_Calibration_Start
$31 01 05 00 Activation_Status_of_Permanent_DTCs_Start
$31 01 FD 10 ZF_Valves_Test_Start
$31 02 FD 10 ZF_Valves_Test_Stop
$31 03 FD 10 ZF_Valves_Test_RequestResults
The server runnables (callouts) shall be stubbed in DiagArAdapter_Cfg.c file. Implementation each DIDs/RIDs will be taken care by the corresponding implementation CR(which are already linked to the 'Required For' relationships to this CR )
The SWE1 and SWE2 tasks are not required for this CR. The SWE1 and SWE2 updates for the newly added diagnostic jobs will be done with the corresponding DID/RID implementation CRs.
--------------------------------------------------------------------------------
Risk (low/medium/high):
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
TASK DIAG
------------------------------------------------------
Title: [MMA][Diag][SWE3/4][X0260] Import DEXT file and update Dcm and Diag Swc configuration
Description: Please use this task to configure the port types in Dcm, create ports and implement runnables in Diag SWC.
The list of newly added diagnostic jobs are mentioned in the CR analysis.
Owner: Firoz KizhakkeMukkat
Reviewer: Christian Weyand
Estimated design effort/h:
Estimated implementation effort/h: 16
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 16
[Optional] Planned completion date:
------------------------------------------------------
TASK Cyber Security
------------------------------------------------------
Title: [MMA][Security][X0260] Use the new ACL file to update the ACL configuration in SSA
Description: Please use the attached ACL file generated out of latest CDD for X0260 and update the ACL configuration in SSA.
Additionally please do the necessary changes regarding the SCN DID related memory block configuration (if required).
The list of newly added SCN diagnostic jobs are mentioned in the CR analysis.
Owner: Suyash Shembekar
Reviewer: Shwetanshu Kukreti
Estimated design effort/h:
Estimated implementation effort/h: 7
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------
TASK Bsw_Autocore
------------------------------------------------------
Title: [MMA][Bsw_Autocore][X0260] DEXT Import: Connect ports, task mapping and generate RTE.
Description: Please use the attached modified arxml files.
This task shall be used to connect the new ports, task mapping to runnbales and generate RTE.
Please use the Task_DiagEvents_D_C0_2 for task mapping. The slot number is irrelevant.
Owner: Sireesha Basavaraju
Reviewer: Hemanth Ambarukhana
Estimated design effort/h:
Estimated implementation effort/h: 7
Estimated unit testing effort/h:
------------------------------------------------------
Total effort/h: 7
[Optional] Planned completion date:
------------------------------------------------------ |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable Precondition: Pbc Released, set PbcIn.WheelPressurereliabilityFL or FR or RL or RR = ePbcWheelPressureNotReliable and set one PbcIn.WheelPressurereliability after the other to ePbcWheelPressureReliable in
Action: Set 4/3/2 different PbcIn.Wheelspeeds.
Expected Behaviour: RefSpeed is the fastes wheelspeed
Actual Behaviour: Refspeed is the second fastes Wheelspeed
Requirements:
EPBi_Audi_PPE-SwRS_1657
EPBi_Audi_PPE-SwRS_1660
Please see attachment <Uma Reddy HDR> 21:08 IST, 08-Aug-2021:
------------------------------------------------------------------------------
-> With CR: 4613549, the check for rear wheel pressure relaibility.
-> The check needs to be in place.
-----------------------------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
Task:
Title/Header : [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable.
Assign to : Uma Reddy HDR
Estimated Effort : 8h
Verifier : E Harder
-----------------------------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
-----------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:41:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable Precondition: Pbc Released, set PbcIn.WheelPressurereliabilityFL or FR or RL or RR = ePbcWheelPressureNotReliable and set one PbcIn.WheelPressurereliability after the other to ePbcWheelPressureReliable in
Action: Set 4/3/2 different PbcIn.Wheelspeeds.
Expected Behaviour: RefSpeed is the fastes wheelspeed
Actual Behaviour: Refspeed is the second fastes Wheelspeed
Requirements:
EPBi_Audi_PPE-SwRS_1657
EPBi_Audi_PPE-SwRS_1660
Please see attachment <Uma Reddy HDR> 21:08 IST, 08-Aug-2021:
------------------------------------------------------------------------------
-> With CR: 4613549, the check for rear wheel pressure relaibility.
-> The check needs to be in place.
-----------------------------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
Task:
Title/Header : [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable.
Assign to : Uma Reddy HDR
Estimated Effort : 8h
Verifier : E Harder
-----------------------------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
-----------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:41:
Please investigate this point and advise the next steps. |
|
[657][CAT3][TEC] [VW_ID_Buzz_EBB] Speed_DCC functionality- SW Ratio and SW JUMPIN are not changing according to the vehicle speed as expected. The actual implementation only includes the vehicle speed dependency as described in VW_MQB_eBoosterAD_1692 & VW_MQB_eBoosterAD_1709. A continuous change of JumpIn or Ratio during the whole brake maneuver (as described in VW_MQB_eBoosterAD_352 and VW_MQB_eBoosterAD_1708) was not sufficient and also not favored by the customer.
Nevertheless, the implementation should be updated to provide both variations of the feature to fulfill all related requirements (VW_MQB_eBoosterAD_352, VW_MQB_eBoosterAD_1692, VW_MQB_eBoosterAD_1693 & VW_MQB_eBoosterAD_1708, VW_MQB_eBoosterAD_1709, VW_MQB_eBoosterAD_1710). This topic is already solved with CR 6048238. The CR can be rejected. | [657][CAT3][TEC] [VW_ID_Buzz_EBB] Speed_DCC functionality- SW Ratio and SW JUMPIN are not changing according to the vehicle speed as expected. The actual implementation only includes the vehicle speed dependency as described in VW_MQB_eBoosterAD_1692 & VW_MQB_eBoosterAD_1709. A continuous change of JumpIn or Ratio during the whole brake maneuver (as described in VW_MQB_eBoosterAD_352 and VW_MQB_eBoosterAD_1708) was not sufficient and also not favored by the customer.
Nevertheless, the implementation should be updated to provide both variations of the feature to fulfill all related requirements (VW_MQB_eBoosterAD_352, VW_MQB_eBoosterAD_1692, VW_MQB_eBoosterAD_1693 & VW_MQB_eBoosterAD_1708, VW_MQB_eBoosterAD_1709, VW_MQB_eBoosterAD_1710). This topic is already solved with CR 6048238. The CR can be rejected. |
|
[657][CAT3][TEC] [VW_ID_Buzz_EBB] Speed_DCC functionality- SW Ratio and SW JUMPIN are not changing according to the vehicle speed as expected. The new cascade controller is required for winter testing in UN ECE software. Based on software X813 the BC update to a MQB48W X0404 baseline requires the following changes: 1) Interfaces adadtations:
- Moco -> BcMain (Accel and SpeedLimits) -> for Accel: use old Rack model or a patched interface
- BcMain -> BcEbr (SpeedLimit + PosControlPrio) -> use VolAbs interfaces
- BcBlc -> BcEbr (BPA) -> from BcMain via VolAbs interface
- Comms -> BcMain (VehAx) -> stub with 0, this interface is not active yet
2) Parameter:
update of linker command file to adapt for calibration structures
3) Pts update (SA): carry over of CR's 5918983 and 4106018 --------------------------------------------------------------------------------
Brief analysis summary:
The new cascade controller is required for winter testing in UN ECE software. Based on software X813 the BC update to a MQB48W X0404 baseline requires the following changes:
1) Interfaces adadtations:
- Moco -> BcMain (Accel and SpeedLimits) -> for Accel: use old Rack model or a patched interface
- BcMain -> BcEbr (SpeedLimit + PosControlPrio) -> use VolAbs interfaces
- BcBlc -> BcEbr (BPA) -> from BcMain via VolAbs interface
- Comms -> BcMain (VehAx) -> stub with 0, this interface is not active yet
==> task for F&C
2) Parameter:
update of linker command file to adapt for calibration structures
==> task for OS
3) Pts update (SA): carry over of CR's 5918983 and 4106018
==> spawn CR
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Chemnitz
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: [VW MEB MY2023][EBB][F&C] BC update with new cascade controller
--------------------------------------------------------------------------------
Description: see analysis summary
Owner: Oliver Schmitt
Reviewer: David Steinmann
Estimated effort/h: 10
Task: [VW MEB MY2023][EBB][OS] adaptation of BC calibration section
--------------------------------------------------------------------------------
Description: The BC parameter structures are increased and do not fit into the defined memory ranges of the calibration section. Therefore the configuration of the BC parameter structure sizes shall be adapted.
Owner:
Reviewer:
Estimated effort/h:
--------------------------------------------------------------------------------
[Optional] Planed completion date:
-------------------------------------------------------------------------------- | [657][CAT3][TEC] [VW_ID_Buzz_EBB] Speed_DCC functionality- SW Ratio and SW JUMPIN are not changing according to the vehicle speed as expected. The new cascade controller is required for winter testing in UN ECE software. Based on software X813 the BC update to a MQB48W X0404 baseline requires the following changes: 1) Interfaces adadtations:
- Moco -> BcMain (Accel and SpeedLimits) -> for Accel: use old Rack model or a patched interface
- BcMain -> BcEbr (SpeedLimit + PosControlPrio) -> use VolAbs interfaces
- BcBlc -> BcEbr (BPA) -> from BcMain via VolAbs interface
- Comms -> BcMain (VehAx) -> stub with 0, this interface is not active yet
2) Parameter:
update of linker command file to adapt for calibration structures
3) Pts update (SA): carry over of CR's 5918983 and 4106018 --------------------------------------------------------------------------------
Brief analysis summary:
The new cascade controller is required for winter testing in UN ECE software. Based on software X813 the BC update to a MQB48W X0404 baseline requires the following changes:
1) Interfaces adadtations:
- Moco -> BcMain (Accel and SpeedLimits) -> for Accel: use old Rack model or a patched interface
- BcMain -> BcEbr (SpeedLimit + PosControlPrio) -> use VolAbs interfaces
- BcBlc -> BcEbr (BPA) -> from BcMain via VolAbs interface
- Comms -> BcMain (VehAx) -> stub with 0, this interface is not active yet
==> task for F&C
2) Parameter:
update of linker command file to adapt for calibration structures
==> task for OS
3) Pts update (SA): carry over of CR's 5918983 and 4106018
==> spawn CR
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Chemnitz
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: [VW MEB MY2023][EBB][F&C] BC update with new cascade controller
--------------------------------------------------------------------------------
Description: see analysis summary
Owner: Oliver Schmitt
Reviewer: David Steinmann
Estimated effort/h: 10
Task: [VW MEB MY2023][EBB][OS] adaptation of BC calibration section
--------------------------------------------------------------------------------
Description: The BC parameter structures are increased and do not fit into the defined memory ranges of the calibration section. Therefore the configuration of the BC parameter structure sizes shall be adapted.
Owner:
Reviewer:
Estimated effort/h:
--------------------------------------------------------------------------------
[Optional] Planed completion date:
-------------------------------------------------------------------------------- |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps Precondition: RAR conditions with and without HPS
Action: Perform Rollaway reclamp with speed several times with and without HPS
Expected Behaviour:Only two reclamps allowed.
Actual Behaviour: MORE Reclamps are performed
Requirements:
EPBi_Audi_PPE-SwRS_3067
EPBi_Audi_PPE-SwRS_3068
EPBi-Audi-PPE-VC_834 --> 2 Reclamps
EPBi-Audi-PPE-VC_836 --> 2 Reclamps
Further infromation: Task to update VC from 2 reclamps to 4 reclamps | [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps Precondition: RAR conditions with and without HPS
Action: Perform Rollaway reclamp with speed several times with and without HPS
Expected Behaviour:Only two reclamps allowed.
Actual Behaviour: MORE Reclamps are performed
Requirements:
EPBi_Audi_PPE-SwRS_3067
EPBi_Audi_PPE-SwRS_3068
EPBi-Audi-PPE-VC_834 --> 2 Reclamps
EPBi-Audi-PPE-VC_836 --> 2 Reclamps
Further infromation: Task to update VC from 2 reclamps to 4 reclamps |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR Precondition: RAR conditions
Action: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RAR
Expected Behaviour: None defect side performs RAR
Actual Behaviour:Both side do not perform RAR
Further inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.
Please see attachment [Marek Gornisiewicz 11:45 21.01.2022]:
CCB ADTY4.1 MGO:
Failure is understood.
Testcases mistake caused the OP.
Affected testcases can be updated with setting the time of 3 seconds after actuator are applied.
- add proposal for Task creation
Assign to (Owner):M.Gornisiewicz
Start Date (Planned Start Date):21.01.2022
Duration (Remaining & Planned Effort):1h
Fix Date (Planned Prepared Date):21.01.2022
Verify to (Reviewer):Arun Valusa
<Divya Teja Kottakonda> (19.01.22 - 14:21):
--------------------------------------------------------------------------------
In the discussion it was accepted that the delay required to trigger reclamp to fulfil the preconditions was not followed in the test case.
No issue of Host availability.
There is no behavior difference for Host availability None and Release
No software issue found.
The tester accepted and verified changing the testcase which proved the above statement correct
The comments provided in CR_5943775 are proved correct for the raised open point.
Proposal of next steps: CR to be assigned to test team to adapt test cases
-----------------------------------------------------------------------------------
<Divya Teja Kottakonda> (18.01.22 - 18:23):
--------------------------------------------------------------------------------
After discussion with Marek, It is accepted that the testcase would be adapted.
Proposal of next steps: CR to be assigned to test team to adapt test cases
---------------------------------------------------------------------------------
Function & Control CCB - FZI - 17.01.22 - 14:05:
I would expect that the behavior is the same for all scenarios where the Host Availability does not allow an apply. Why is there a difference between "none" and "only release possible"?
SWPM (A. Büttner) (14.01.22 - 14:54):
--------------------------------------------------------------------------------
please check this topic again.
it was initially analyzed with CR 5943775, CR was rejected.
But after discussion between Marek Gornisiewicz and Florian Zimmer this topic shall be analyzed again.
-------------------------------------------------------------------------------- | [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR Precondition: RAR conditions
Action: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RAR
Expected Behaviour: None defect side performs RAR
Actual Behaviour:Both side do not perform RAR
Further inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.
Please see attachment [Marek Gornisiewicz 11:45 21.01.2022]:
CCB ADTY4.1 MGO:
Failure is understood.
Testcases mistake caused the OP.
Affected testcases can be updated with setting the time of 3 seconds after actuator are applied.
- add proposal for Task creation
Assign to (Owner):M.Gornisiewicz
Start Date (Planned Start Date):21.01.2022
Duration (Remaining & Planned Effort):1h
Fix Date (Planned Prepared Date):21.01.2022
Verify to (Reviewer):Arun Valusa
<Divya Teja Kottakonda> (19.01.22 - 14:21):
--------------------------------------------------------------------------------
In the discussion it was accepted that the delay required to trigger reclamp to fulfil the preconditions was not followed in the test case.
No issue of Host availability.
There is no behavior difference for Host availability None and Release
No software issue found.
The tester accepted and verified changing the testcase which proved the above statement correct
The comments provided in CR_5943775 are proved correct for the raised open point.
Proposal of next steps: CR to be assigned to test team to adapt test cases
-----------------------------------------------------------------------------------
<Divya Teja Kottakonda> (18.01.22 - 18:23):
--------------------------------------------------------------------------------
After discussion with Marek, It is accepted that the testcase would be adapted.
Proposal of next steps: CR to be assigned to test team to adapt test cases
---------------------------------------------------------------------------------
Function & Control CCB - FZI - 17.01.22 - 14:05:
I would expect that the behavior is the same for all scenarios where the Host Availability does not allow an apply. Why is there a difference between "none" and "only release possible"?
SWPM (A. Büttner) (14.01.22 - 14:54):
--------------------------------------------------------------------------------
please check this topic again.
it was initially analyzed with CR 5943775, CR was rejected.
But after discussion between Marek Gornisiewicz and Florian Zimmer this topic shall be analyzed again.
-------------------------------------------------------------------------------- |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR Precondition: RAR conditions
Action: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RAR
Expected Behaviour: None defect side performs RAR
Actual Behaviour:Both side do not perform RAR
Further inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.
Please see attachment <Divya Teja Kottakonda> (28.12.21 - 19:00):
--------------------------------------------------------------------------------
Brief investigation comment:
---------------------------------------
The reclamp is not triggered in the mentioned issue because one of the preconditions is not met in the testcase.
As per implementation the condition is that once the brakes are fully applied then after a certain delay time(Reclamp.RAR_FULLY_APPLIED_DELAY=3 ) only RAR preconditions are fullfilled.
This was not followed in the testcase.
There is no software issue observed, The testcases should be adapted
Proposal of next steps :OP can be rejected
Function & Control CCB - FZI - 02.12.21 - 13:29:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR Precondition: RAR conditions
Action: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RAR
Expected Behaviour: None defect side performs RAR
Actual Behaviour:Both side do not perform RAR
Further inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.
Please see attachment <Divya Teja Kottakonda> (28.12.21 - 19:00):
--------------------------------------------------------------------------------
Brief investigation comment:
---------------------------------------
The reclamp is not triggered in the mentioned issue because one of the preconditions is not met in the testcase.
As per implementation the condition is that once the brakes are fully applied then after a certain delay time(Reclamp.RAR_FULLY_APPLIED_DELAY=3 ) only RAR preconditions are fullfilled.
This was not followed in the testcase.
There is no software issue observed, The testcases should be adapted
Proposal of next steps :OP can be rejected
Function & Control CCB - FZI - 02.12.21 - 13:29:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment <Kiran Reddy> (18.01.22 - 20:00):
--------------------------------------------------------------------------------
Brief investigation comment:
The system requirement EPBi-Audi-PPE-SyDesign_1650 related to the software requirement EPBi_Audi_PPE-SwRS_2342 is rejected.
Hence the software requirement should also be rejected.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Reject the CR
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 13.01.22 - 15:01:
Please investigate this point and advise the next steps.
MSP 21.12.2021:
related requirments where reviewed, no contradiction found, SW Bug assumed | [Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment <Kiran Reddy> (18.01.22 - 20:00):
--------------------------------------------------------------------------------
Brief investigation comment:
The system requirement EPBi-Audi-PPE-SyDesign_1650 related to the software requirement EPBi_Audi_PPE-SwRS_2342 is rejected.
Hence the software requirement should also be rejected.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- Reject the CR
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 13.01.22 - 15:01:
Please investigate this point and advise the next steps.
MSP 21.12.2021:
related requirments where reviewed, no contradiction found, SW Bug assumed |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR CR to update SwRS according to finding of CR 5846407:
"The system requirement EPBi-Audi-PPE-SyDesign_1650 related to the software requirement EPBi_Audi_PPE-SwRS_2342 is rejected.
Hence the software requirement should also be rejected."
Description of CR 5846407:
Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment -------------------------------------------------------------------------------------------------------------------------------------------------
[03.06.2022, Z607934]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Consider SyDesign @10.0
Below mentioned requirement need to be rejected.
*. EPBi_Audi_PPE-SwRS_2112
*. EPBi_Audi_PPE-SwRS_2342
---------------------------------------------------------------------------------------------------------------------
Complexity: [Low]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
1. Title/Header: Reject EPBi_Audi_PPE-SwRS_2112 and 2342.
Description:
Below mentioned requirement need to be rejected.
*. EPBi_Audi_PPE-SwRS_2112
*. EPBi_Audi_PPE-SwRS_2342
Acceptance Criteria(s):
*. Rejected system requirement should be reviewed
*. Sw Requirement should be rejected
*. Sw Stakeholder should be informed about rejected requirements.
Review Type: Stakeholder review [NO], Formal review [YES]
Review Selection Reason: Sw Requirement is rejected hence no stakeholder review is necessary.
Review Department(s): SWE.1
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 3 h
-------------------------------------------------------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 27.04.22 - 11:45:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR CR to update SwRS according to finding of CR 5846407:
"The system requirement EPBi-Audi-PPE-SyDesign_1650 related to the software requirement EPBi_Audi_PPE-SwRS_2342 is rejected.
Hence the software requirement should also be rejected."
Description of CR 5846407:
Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment -------------------------------------------------------------------------------------------------------------------------------------------------
[03.06.2022, Z607934]
---------------------------------------------------------------------------------------------------------------------
Brief description of investigation for effort estimation of requirement engineering activities:
---------------------------------------------------------------------------------------------------------------------
Consider SyDesign @10.0
Below mentioned requirement need to be rejected.
*. EPBi_Audi_PPE-SwRS_2112
*. EPBi_Audi_PPE-SwRS_2342
---------------------------------------------------------------------------------------------------------------------
Complexity: [Low]
Experience: [Known Topic]
Carry Over: [Basis available]
---------------------------------------------------------------------------------------------------------------------
Proposal of next step(s):
---------------------------------------------------------------------------------------------------------------------
1. Title/Header: Reject EPBi_Audi_PPE-SwRS_2112 and 2342.
Description:
Below mentioned requirement need to be rejected.
*. EPBi_Audi_PPE-SwRS_2112
*. EPBi_Audi_PPE-SwRS_2342
Acceptance Criteria(s):
*. Rejected system requirement should be reviewed
*. Sw Requirement should be rejected
*. Sw Stakeholder should be informed about rejected requirements.
Review Type: Stakeholder review [NO], Formal review [YES]
Review Selection Reason: Sw Requirement is rejected hence no stakeholder review is necessary.
Review Department(s): SWE.1
==> What to review: Please check against the corresponding ALM_Task Notes to identify and confirm the baselines to be reviewed!
==> What checklists: Please check against the corresponding ALM_Task Notes to identify, confirm and add the checklists!
Estimated effort: 3 h
-------------------------------------------------------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 27.04.22 - 11:45:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment
SWPM (A. Büttner) (24.06.22 - 09:19):
--------------------------------------------------------------------------------
System Requirement 1649 was rejected
Linked Sw Requirements 2112 and 2342 for Option 1 and Option 2 will be rejected as well
this CR shall be used to adapt the SW implementation accordingly.
please also refer to attached emails.
-------------------------------------------------------------------------------- <Kiran Reddy> (07.07.22 - 18:00):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the attached mail conversation, following features needs to be disabled.
1. Parksupport when actuation failed
2. Parksupport when a roll away is detected and first HTR is awaited.
The second feature is already disabled with PARK_REQUEST_HOT_RAR_configured.
To disable first feature
1. Create new parameter PARK_REQUEST_ACT_FAILED_configured and set it to HAMMING_FALSE.
2. Add new input in parksupport wrapper connected to PARK_REQUEST_ACT_FAILED_configured parameter as shown in the image below.
3. Update the model to add new input to the conditions of ActuationParkRequest subsytem as shown in image below.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for Kiran Reddy: Disable Parksupport when actuation failed/ Verifier: TBD (9 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [x] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 24.06.22 - 11:18:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR Precondition: Set precondition for HTR at 500 Deg.
Action: Call PbcCyclic until the first HTR step
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_2342
Further information: Maybe there is a issue on requirement side.
Please see attachment
SWPM (A. Büttner) (24.06.22 - 09:19):
--------------------------------------------------------------------------------
System Requirement 1649 was rejected
Linked Sw Requirements 2112 and 2342 for Option 1 and Option 2 will be rejected as well
this CR shall be used to adapt the SW implementation accordingly.
please also refer to attached emails.
-------------------------------------------------------------------------------- <Kiran Reddy> (07.07.22 - 18:00):
--------------------------------------------------------------------------------
Brief investigation comment:
As per the attached mail conversation, following features needs to be disabled.
1. Parksupport when actuation failed
2. Parksupport when a roll away is detected and first HTR is awaited.
The second feature is already disabled with PARK_REQUEST_HOT_RAR_configured.
To disable first feature
1. Create new parameter PARK_REQUEST_ACT_FAILED_configured and set it to HAMMING_FALSE.
2. Add new input in parksupport wrapper connected to PARK_REQUEST_ACT_FAILED_configured parameter as shown in the image below.
3. Update the model to add new input to the conditions of ActuationParkRequest subsytem as shown in image below.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for Kiran Reddy: Disable Parksupport when actuation failed/ Verifier: TBD (9 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [x] or No [] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 24.06.22 - 11:18:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at negetive PbcIn.LongAcceleration Precondition: Set precondition for ParkSupportRequest with negative PbcIn.LongAcceleration
Action: Set PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_3792
Further information: At positve PbcIn.LongAcceleration Parksupport is requested
Please see attachment Manojvishal Gopalakrishnan 23.07.2021 5.00pm
-------------------------------------------------------------------
Model changes required to in Park request model.
Magnitude of the Inclination signal will resolve this issue.
Scaling need copied from inclination input signal.
Same test case can be used as attached in CR with small adaption of the PBCIn.LongAcceleration signals.
Ref. screenshots are added in Attachments.
-------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
--------------------------------------------------------------------------------
- One task for <Manojvishal>: Implementing Magnitude of PBCIn.LongAcceleration : Verifier: <Florian>(18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required?
(Do we need a PARA build?) Yes [] or No [x] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:40:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at negetive PbcIn.LongAcceleration Precondition: Set precondition for ParkSupportRequest with negative PbcIn.LongAcceleration
Action: Set PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles
Expected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclic
Actual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequested
Requirements:
EPBi_Audi_PPE-SwRS_3792
Further information: At positve PbcIn.LongAcceleration Parksupport is requested
Please see attachment Manojvishal Gopalakrishnan 23.07.2021 5.00pm
-------------------------------------------------------------------
Model changes required to in Park request model.
Magnitude of the Inclination signal will resolve this issue.
Scaling need copied from inclination input signal.
Same test case can be used as attached in CR with small adaption of the PBCIn.LongAcceleration signals.
Ref. screenshots are added in Attachments.
-------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
--------------------------------------------------------------------------------
- One task for <Manojvishal>: Implementing Magnitude of PBCIn.LongAcceleration : Verifier: <Florian>(18 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required?
(Do we need a PARA build?) Yes [] or No [x] (please mark with an "x")
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:40:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of Recalmp with HPS/HPO Acknowledge too late (> 2s) Precondition: Set HPO conditions.
Action: Set PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles set PbcInHpsAcknowledge >= 2 s after Hps request
Expected Behaviour: After 2s a reclamp shall be performed
Actual Behaviour: No reclamp is performed
Requirements:
EPBi_Audi_PPE-SwRS_2818
Please see attachment <Uma Reddy> (27-Jul-2021 - 13:25 IST):
--------------------------------------------------------------------------------
Brief investigation comment:
-> This issue is already raised with VW_MQB_48W & the fix in AUDI PPE is also done with task ALM_Task 5492866.
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
This CR can be rejected.
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:39:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of Recalmp with HPS/HPO Acknowledge too late (> 2s) Precondition: Set HPO conditions.
Action: Set PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles set PbcInHpsAcknowledge >= 2 s after Hps request
Expected Behaviour: After 2s a reclamp shall be performed
Actual Behaviour: No reclamp is performed
Requirements:
EPBi_Audi_PPE-SwRS_2818
Please see attachment <Uma Reddy> (27-Jul-2021 - 13:25 IST):
--------------------------------------------------------------------------------
Brief investigation comment:
-> This issue is already raised with VW_MQB_48W & the fix in AUDI PPE is also done with task ALM_Task 5492866.
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
This CR can be rejected.
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:39:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of HPO request at 11V and Release direction Precondition: Set Pbc is Parkapplied, Set MotorSupplyVoltage and MotorVoltageLeft and Right to 11V
Action: perform release he PBC
Expected Behaviour: No HPO request is requested
Actual Behaviour: Pbc requests HPO
Requirements:
EPBi_Audi_PPE-SwRS_3781
Further information: According the req only below 11V HPO shall be requested
Please see attachment <Uma Reddy HDR> (28-Jul-2021, 18:24 IST):
-----------------------------------------------------------------------------------------------------
Brief Investigation comment:
-> Analysis of trace shows voltage is at 10.99V & HPO release happens according to requirement.
-> Constructed a test case to observe the behavior at 11V & is working according to the requirement. No HPO release at 11v & above.
Attaching the test case as well.
-----------------------------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
This CR can be rejected.
-----------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:38:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of HPO request at 11V and Release direction Precondition: Set Pbc is Parkapplied, Set MotorSupplyVoltage and MotorVoltageLeft and Right to 11V
Action: perform release he PBC
Expected Behaviour: No HPO request is requested
Actual Behaviour: Pbc requests HPO
Requirements:
EPBi_Audi_PPE-SwRS_3781
Further information: According the req only below 11V HPO shall be requested
Please see attachment <Uma Reddy HDR> (28-Jul-2021, 18:24 IST):
-----------------------------------------------------------------------------------------------------
Brief Investigation comment:
-> Analysis of trace shows voltage is at 10.99V & HPO release happens according to requirement.
-> Constructed a test case to observe the behavior at 11V & is working according to the requirement. No HPO release at 11v & above.
Attaching the test case as well.
-----------------------------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
This CR can be rejected.
-----------------------------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 14:38:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working Precondition: Set PbcIn.VariantItem[0] = 255
Action: Call PbcInit, then PbcCyclic
Expected Behavior: PbcOut.FaultStatus[17] = ePbcFaultStateFailed
Actual Behaviour: PbcOut.FaultStatus[17] = ePbcFaultStateNotSupported
Requirements:
EPBi_Audi_PPE-SwRS_2464
EPBi_Audi_PPE-SwRS_2465
EPBi_Audi_PPE-SwRS_2466
EPBi_Audi_PPE-SwRS_3031
EPBi_Audi_PPE-SwRS_3032
Further information: In SyDesign and SW-Rs this Fault shall be on and work a different way as in Core.
But in DMT the related monitors are disabled. The necessary softweareparts are generated out of the DMT/DETconfiguration
Please see attachment <Dadige Aruna> (31.01.22 - 11:55):
--------------------------------------------------------------------------------
Brief investigation comment:
-> As per the confirmation from Martin as there are no specific requirements for fault handling we are proceeding with enabling of EVENT_VARIANT_CODE_INVALID in SW. Please find attached email communication.
-> Tester need to adapt the test case as PbcOut.FaultStatus[17] = ePbcFaultStateNoResult..ePbcFaultStatePassed
-> Please add the attached PBC - DMT.xml file to the Audi_PPE\08_Software\PBC_APPL\01_Requirements integrity archive
-> Implement the SW changes as per new DMT file
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Arun Kumar>: <[Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working> / Verifier: <Harder Eduard> (12 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
--------------------------------------------------------------------------------
SWPM (A. Büttner) (24.01.22 - 14:02):
--------------------------------------------------------------------------------
Martin Spickermann enabled the monitors in DMT according to SyDesign and SwRS and created a new Baseline for DMT (rev.19)
please implement in SW accordingly.
--------------------------------------------------------------------------------
Oliver Lang (19.01.22 - 14:40):
--------------------------------------------------------------------------------
We had the same discussion in VW MQB48-W in CR 5323342 and the outcome was that the System requirements needed to be updated. This was done by Rene with CR 5970971.
When you (or PSM) decides to handle it in the same way this SiL finding can be rejected.--------------------------------------------------------------------------------
Aruna D - 11-24-2021 - 11:30:
-> Sent mail to Anne regarding the confirmation on variant coding implementation. Analysis will be continued once I receive confirmation
SW and Requirements not in line.
actions:
1. DMT update --> System
2. SW updated --> F&C
Function & Control CCB - FZI - 14.07.21 - 15:27:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working Precondition: Set PbcIn.VariantItem[0] = 255
Action: Call PbcInit, then PbcCyclic
Expected Behavior: PbcOut.FaultStatus[17] = ePbcFaultStateFailed
Actual Behaviour: PbcOut.FaultStatus[17] = ePbcFaultStateNotSupported
Requirements:
EPBi_Audi_PPE-SwRS_2464
EPBi_Audi_PPE-SwRS_2465
EPBi_Audi_PPE-SwRS_2466
EPBi_Audi_PPE-SwRS_3031
EPBi_Audi_PPE-SwRS_3032
Further information: In SyDesign and SW-Rs this Fault shall be on and work a different way as in Core.
But in DMT the related monitors are disabled. The necessary softweareparts are generated out of the DMT/DETconfiguration
Please see attachment <Dadige Aruna> (31.01.22 - 11:55):
--------------------------------------------------------------------------------
Brief investigation comment:
-> As per the confirmation from Martin as there are no specific requirements for fault handling we are proceeding with enabling of EVENT_VARIANT_CODE_INVALID in SW. Please find attached email communication.
-> Tester need to adapt the test case as PbcOut.FaultStatus[17] = ePbcFaultStateNoResult..ePbcFaultStatePassed
-> Please add the attached PBC - DMT.xml file to the Audi_PPE\08_Software\PBC_APPL\01_Requirements integrity archive
-> Implement the SW changes as per new DMT file
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- One task for <Arun Kumar>: <[Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working> / Verifier: <Harder Eduard> (12 h)
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x] (please mark with an "x")
--------------------------------------------------------------------------------
SWPM (A. Büttner) (24.01.22 - 14:02):
--------------------------------------------------------------------------------
Martin Spickermann enabled the monitors in DMT according to SyDesign and SwRS and created a new Baseline for DMT (rev.19)
please implement in SW accordingly.
--------------------------------------------------------------------------------
Oliver Lang (19.01.22 - 14:40):
--------------------------------------------------------------------------------
We had the same discussion in VW MQB48-W in CR 5323342 and the outcome was that the System requirements needed to be updated. This was done by Rene with CR 5970971.
When you (or PSM) decides to handle it in the same way this SiL finding can be rejected.--------------------------------------------------------------------------------
Aruna D - 11-24-2021 - 11:30:
-> Sent mail to Anne regarding the confirmation on variant coding implementation. Analysis will be continued once I receive confirmation
SW and Requirements not in line.
actions:
1. DMT update --> System
2. SW updated --> F&C
Function & Control CCB - FZI - 14.07.21 - 15:27:
Please investigate this point and advise the next steps. |
|
[Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working Precondition: Set PbcIn.VariantItem[0] = 255
Action: Call PbcInit, then PbcCyclic
Expected Behavior: PbcOut.FaultStatus[17] = ePbcFaultStateFailed
Actual Behaviour: PbcOut.FaultStatus[17] = ePbcFaultStateNotSupported
Requirements:
EPBi_Audi_PPE-SwRS_2464
EPBi_Audi_PPE-SwRS_2465
EPBi_Audi_PPE-SwRS_2466
EPBi_Audi_PPE-SwRS_3031
EPBi_Audi_PPE-SwRS_3032
Further information: In SyDesign and SW-Rs this Fault shall be on and work a different way as in Core.
But in DMT the related monitors are disabled. The necessary softweareparts are generated out of the DMT/DETconfiguration
Please see attachment 09.01.24 PSM Oliver Klaus
DMT updated and Variant Code invalid active with Op 6325252 | [Issue] of PBC_X01_501_00p - SiL Test - Issue of EVENT_VARIANT_CODE_INVALID is not working Precondition: Set PbcIn.VariantItem[0] = 255
Action: Call PbcInit, then PbcCyclic
Expected Behavior: PbcOut.FaultStatus[17] = ePbcFaultStateFailed
Actual Behaviour: PbcOut.FaultStatus[17] = ePbcFaultStateNotSupported
Requirements:
EPBi_Audi_PPE-SwRS_2464
EPBi_Audi_PPE-SwRS_2465
EPBi_Audi_PPE-SwRS_2466
EPBi_Audi_PPE-SwRS_3031
EPBi_Audi_PPE-SwRS_3032
Further information: In SyDesign and SW-Rs this Fault shall be on and work a different way as in Core.
But in DMT the related monitors are disabled. The necessary softweareparts are generated out of the DMT/DETconfiguration
Please see attachment 09.01.24 PSM Oliver Klaus
DMT updated and Variant Code invalid active with Op 6325252 |
|
[Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest Precondition: PbcOut.ActuatorState_RL/RR = ePbcActuatorStateReleased PSR request condtions
Action: PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles. PbcIn.ParkSupportAck not Acknowledged in Time
Expected Behavior: PbOut.OutOfSpecMsg = ePbcMsgOutOfSpecC
Actual Behaviour: PbOut.OutOfSpecMsg = ePbcMsgOutOfSpecC and ePbcMsgOutOfSpecNone are changing every cycle
Requirements:
EPBi_Audi_PPE-SwRS_3791
Please see attachment <Pruthvi> (01.09.21 - 14:00):
--------------------------------------------------------------------------------
In the above scenario, the toggle of PbOut.OutOfSpecMsg between ePbcMsgOutOfSpecC and ePbcMsgOutOfSpecNone is due to the exit condition of out_of_spec_message_C state.
It is [(HAMMING_FALSE !=is_right_applied) || (HAMMING_FALSE !=is_left_applied)], which is same as the entry condition. This has to be changed as below screenshot.
--------------------------------------------------------------------------------
Task:
Title/Header : [Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest
Assign to : Pruthvi ITC
Estimated Effort : 14h
Verifier : Michael Gerz
Description : [Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:28:
Please investigate this point and advise the next steps. | [Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest Precondition: PbcOut.ActuatorState_RL/RR = ePbcActuatorStateReleased PSR request condtions
Action: PbcInApplyReleaseRequest = ePbcApplyReleaseRequestParkApply for 2 cycles. PbcIn.ParkSupportAck not Acknowledged in Time
Expected Behavior: PbOut.OutOfSpecMsg = ePbcMsgOutOfSpecC
Actual Behaviour: PbOut.OutOfSpecMsg = ePbcMsgOutOfSpecC and ePbcMsgOutOfSpecNone are changing every cycle
Requirements:
EPBi_Audi_PPE-SwRS_3791
Please see attachment <Pruthvi> (01.09.21 - 14:00):
--------------------------------------------------------------------------------
In the above scenario, the toggle of PbOut.OutOfSpecMsg between ePbcMsgOutOfSpecC and ePbcMsgOutOfSpecNone is due to the exit condition of out_of_spec_message_C state.
It is [(HAMMING_FALSE !=is_right_applied) || (HAMMING_FALSE !=is_left_applied)], which is same as the entry condition. This has to be changed as below screenshot.
--------------------------------------------------------------------------------
Task:
Title/Header : [Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest
Assign to : Pruthvi ITC
Estimated Effort : 14h
Verifier : Michael Gerz
Description : [Issue] of PBC_X01_501_00p - SiL Test -Issue of Out Of Spec Message C with not acknowledged ParkSupportRequest
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:28:
Please investigate this point and advise the next steps. |
|
[Issue]of PBC_X01_501_00p - SiL Test - Issue of EVENT_ACTUATOR_POSITION_INCOHERENT,Park Apply operation is not performing after fault recovery Precondition:Set PbcOut.ActuatorState_RL= ePbcActuatorStateReleased, PbcOut.ActuatorState_RR = ePbcActuatorStateParkapplied VIA Diag operation,Then set FaultStatus[10]=ePbcFaultStateFailed,i.e.,EVENT_ACTUATOR_POSITION_INCOHERENT Fault
Action: set FaultRecoveryRequest[10]= ePbcRecoveryRequest and ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply
Expected Behavior:PbcOut.ActuatorState_RL= ePbcActuatorStateParkApplied, PbcOut.ActuatorState_RR = ePbcActuatorStateParkApplied and FaultStatus[10]=ePbcFaultStatePassed
Actual Behavior: PbcOut.ActuatorState_RL= ePbcActuatorStateReleased, PbcOut.ActuatorState_RR = ePbcActuatorStateParkapplied and FaultStatus[10]=ePbcFaultStateFailed
Requirements:-
EPBi_Audi-PPE-DET-PBC_73
EPBi_Audi-PPE-DMT_98
Further Information :
after setting 'FaultRecoveryRequest[10]= ePbcRecoveryRequest',if 'ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply' then FaultStatus[10] should set ePbcFaultStatePassed .
But Here still in Failed sate.
When FaultRecoveryRequest[10] is set to ePbcRecoveryRequest ,then 'FaultStatus[10]' wait in 'NoResult' for 1sec and it will move to again moved to 'Failed'.
In this scenario ApplyReleaseRequest is set to 'ePbcApplyReleaseRequestParkApply' in NoResult or Failed also ,there is no actuation is performing and
FaultStatus[10] is going to failed again.
OP is created once again because of behaviour is still present.
Last OP4422735 / CR4950072 [Marek Gornisiewicz 09:05 25.11.2021]:
CCB ADTY4.1 MGO:
Meanwhil in X01_550_01p it works correctly
Report is here
testcases
-300-216-
-300-217-
-300-218-
CR can be rejected
Sankararao Gudena (14.09.21 - 14:17):
--------------------------------------------------------------------------------
Brief investigation comment:
Tested SIL testcase, working as expected.
Attached test report and traces, Needs to checked from tester side whether tested on correct software or not.
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- CR shall be given back to tester as this scenario working as expected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:29:
Please investigate this point and advise the next steps. | [Issue]of PBC_X01_501_00p - SiL Test - Issue of EVENT_ACTUATOR_POSITION_INCOHERENT,Park Apply operation is not performing after fault recovery Precondition:Set PbcOut.ActuatorState_RL= ePbcActuatorStateReleased, PbcOut.ActuatorState_RR = ePbcActuatorStateParkapplied VIA Diag operation,Then set FaultStatus[10]=ePbcFaultStateFailed,i.e.,EVENT_ACTUATOR_POSITION_INCOHERENT Fault
Action: set FaultRecoveryRequest[10]= ePbcRecoveryRequest and ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply
Expected Behavior:PbcOut.ActuatorState_RL= ePbcActuatorStateParkApplied, PbcOut.ActuatorState_RR = ePbcActuatorStateParkApplied and FaultStatus[10]=ePbcFaultStatePassed
Actual Behavior: PbcOut.ActuatorState_RL= ePbcActuatorStateReleased, PbcOut.ActuatorState_RR = ePbcActuatorStateParkapplied and FaultStatus[10]=ePbcFaultStateFailed
Requirements:-
EPBi_Audi-PPE-DET-PBC_73
EPBi_Audi-PPE-DMT_98
Further Information :
after setting 'FaultRecoveryRequest[10]= ePbcRecoveryRequest',if 'ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply' then FaultStatus[10] should set ePbcFaultStatePassed .
But Here still in Failed sate.
When FaultRecoveryRequest[10] is set to ePbcRecoveryRequest ,then 'FaultStatus[10]' wait in 'NoResult' for 1sec and it will move to again moved to 'Failed'.
In this scenario ApplyReleaseRequest is set to 'ePbcApplyReleaseRequestParkApply' in NoResult or Failed also ,there is no actuation is performing and
FaultStatus[10] is going to failed again.
OP is created once again because of behaviour is still present.
Last OP4422735 / CR4950072 [Marek Gornisiewicz 09:05 25.11.2021]:
CCB ADTY4.1 MGO:
Meanwhil in X01_550_01p it works correctly
Report is here
testcases
-300-216-
-300-217-
-300-218-
CR can be rejected
Sankararao Gudena (14.09.21 - 14:17):
--------------------------------------------------------------------------------
Brief investigation comment:
Tested SIL testcase, working as expected.
Attached test report and traces, Needs to checked from tester side whether tested on correct software or not.
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- CR shall be given back to tester as this scenario working as expected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:29:
Please investigate this point and advise the next steps. |
|
[Issue]of PBC_X01_501_00p - SiL Test - Issue of EVENT_ACTUATOR_STATE_UNKNOWN,Park Apply is not performing on Good side Actuator Precondition:intially PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateReleased,FaultStatus[11]=ePbcFaultStateFailed
Action: set ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply
Expected Behavior:PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateParkApplied
Actual Behavior: PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateReleased
Requirements:-
EPBi_Audi-PPE-SwRS_1477,1638
EPBi_Audi-PPE-DMT_276 ,275
Further Information :
As per requirement EPBi_Audi-PPE-DMT_276 ,275 ,If Left actuator state is Unknown and Right actuator state is Released then Park apply should perform right actuator (which is in released state) and vice versa for right actuator.
But here both sides actuation is not performing
OP is created once again because of behaviour is still present.
Last OP4422665 / CR4950073 [Marek Gornisiewicz 17:19 23.11.2021]:
CCB ADTY4.1 MGO:
Software behaviour in X01_550_00p is working ok.
Report
Testcases
-300-263
-300-264-
CR can be rejected
Sankararao Gudena (14.09.21 - 14:21):
--------------------------------------------------------------------------------
Brief investigation comment:
Tested SIL testcase, working as expected.
Attached test report and traces, Needs to checked from tester side whether tested on correct software or not.
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- CR shall be given back to tester as this scenario working as expected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:29:
Please investigate this point and advise the next steps. | [Issue]of PBC_X01_501_00p - SiL Test - Issue of EVENT_ACTUATOR_STATE_UNKNOWN,Park Apply is not performing on Good side Actuator Precondition:intially PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateReleased,FaultStatus[11]=ePbcFaultStateFailed
Action: set ApplyReleaseRequest=ePbcApplyReleaseRequestParkApply
Expected Behavior:PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateParkApplied
Actual Behavior: PbcOut.ActuatorState_RL= ePbcActuatorStateUnknown, PbcOut.ActuatorState_RR = ePbcActuatorStateReleased
Requirements:-
EPBi_Audi-PPE-SwRS_1477,1638
EPBi_Audi-PPE-DMT_276 ,275
Further Information :
As per requirement EPBi_Audi-PPE-DMT_276 ,275 ,If Left actuator state is Unknown and Right actuator state is Released then Park apply should perform right actuator (which is in released state) and vice versa for right actuator.
But here both sides actuation is not performing
OP is created once again because of behaviour is still present.
Last OP4422665 / CR4950073 [Marek Gornisiewicz 17:19 23.11.2021]:
CCB ADTY4.1 MGO:
Software behaviour in X01_550_00p is working ok.
Report
Testcases
-300-263
-300-264-
CR can be rejected
Sankararao Gudena (14.09.21 - 14:21):
--------------------------------------------------------------------------------
Brief investigation comment:
Tested SIL testcase, working as expected.
Attached test report and traces, Needs to checked from tester side whether tested on correct software or not.
Risk (low/medium/high): med
--------------------------------------------------------------------------------
Proposal of next steps (incl. effort / h and verifier):
- CR shall be given back to tester as this scenario working as expected.
--------------------------------------------------------------------------------
Is a change in the ParameterFile required? (Do we need a PARA build?)
Yes [] or No [x]
--------------------------------------------------------------------------------
Function & Control CCB - FZI - 14.07.21 - 15:29:
Please investigate this point and advise the next steps. |
|
[X400-002][CAT2][TCS][VW_UNECE_EBB][Mesweerte] Mil status ON is not updating when read data by identifier driver warning displays (0x4E01) is requested in Supported sessions 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. Test result:
Tested SW:
Test results reference number: | [X400-002][CAT2][TCS][VW_UNECE_EBB][Mesweerte] Mil status ON is not updating when read data by identifier driver warning displays (0x4E01) is requested in Supported sessions 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. Test result:
Tested SW:
Test results reference number: |
|
Issue of PBC not reacting to HoldApply Requests Please review the attached trace for the issue described below. Expected behavior must be honored by PBC.
Scenario 1 (Trace: HoldAppy_Issue.zip)
Preconditions: Brake module in fallback mode (ESF), vehicle in dynamic state, EPB actuator state is released.
Action: Driver decelerates the vehicle by pressing the brake pedal. ESF function sends the hydraulic pressure, if any, to the front brakes, hydraulically isolates rear brakes and sets PbcInApplyReleaseRequest = DynamicApply to get support from EPB.
Expected behavior: When vehicle enters in static state, host transitions PbcInApplyReleaseRequest from DynamicApply to HoldApply. PBC should increase the CF demand until the HoldApplied state is reached, or set the actuator states to HoldApplied if the CF generated by RWU is equal or greater to the HoldApply demand.
Observed behavior: The EPB releases the clamp force achieved during RWU when HoldApply is requested. Final actuator state is Released.
Scenario 2 (Trace: HoldAppy_Issue_None_to_HoldApply.zip)
Preconditions: Brake module in fallback mode (ESF), vehicle in static state (speed < 5kph), EPB actuator state is released.
Action: Driver presses the brake pedal. ESF function sends the hydraulic pressure, if any, to the front brakes, hydraulically isolates rear brakes and sets PbcInApplyReleaseRequest = HoldApply to hold the vehicle with the EPB.
Expected behavior: PBC should command motors to increase the CF until the HoldApplied state is reached.
Observed behavior: The EPB stays in Released state.
Hint: ESF stands for Epb Support in Fallback mode. HoldApply was implemented in S650 with CR 4671476. <Pruthvi> (28.07.21 - 08:00):
--------------------------------------------------------------------------------
It is observed that GDAInGDHEnable is FALSE through out the test case in both the scenarios. As C.Torres observed GDAInStaticHoldDemand is 10 kN.
In revision 1.18.2.17.11.9.1.7 of 02_Architecture_Design i.e., Ford_S650_PBC_PARA_X01_300_00p build, we enabled GDH and Set STATIC_HOLD_DEMAND to STATIC_DEMAND (18.5KN).
In revision 1.18.2.17.11.9.1.8 of 02_Architecture_Design i.e., Ford_S650_PBC_PARA_X01_400_00p build, we updated STATIC_HOLD_DEMAND value from 18.5 to 8kN.
The reason for the above issue of PBC not reacting to HoldApply Requests is using of incorrect parameter file with HoldApply deactivated in it.
Proposal of next steps:
@Florian Zimmer :Please reject this CR as there is no software update required from PBC end.
@C.Torres: Please inform host to use the latest PBC_APPL and PBC_PARA software(Ford_S650_PBC_APPL_X01_400_00p, Ford_S650_PBC_PARA_X01_400_00p).
--------------------------------------------------------------------------------
<C.Torres (27.07.21 - 23:26)>: Attached is zip file "HoldApply_Issue_with_Demarb-FuncMan-GDA-RWU_signals.zip". Test was performed on an S650 vehicle. GDA and RWU were recorded together and Demarb and FuncMan were recorded together in different traces. From what I could observe, signal GDAInStaticHoldDemand is 10 kN but it should be 8kN, that's a suspicion of incorrect parameter file with HoldApply possibly deactivated.
<C.Torres (19.07.21 - 23:26)>: Attached is zip file "HoldApply_Issue_with_PBA_signals", it contains the requested traces. V14 was recorded with CANape 14 and V17 with CANape V17 but test case is the same.
Test was performed on another S650 vehicle. Host provided a .map file with the addresses of PBA signals, but not all PBA signals matched between .map and PbcInterface.a2l file.
Attached are .map and .a2l files for reference, in case there is any signal missing, please mark it in both files and a new trace will be recorded asap.
<Pruthvi> (14.07.21 - 15:30):
--------------------------------------------------------------------------------
I looked into the attached traces. I don’t see any reason why Hold Apply is not being performed. So I tried to replicate the scenario in my VectorCast environment with latest software available.
For me Hold Apply has performed and the results were as expected.
@Torres Cabrera Christian Alvaro LVN ADBY11 : As we discussed the Open point is based on vehicle test and tested on latest software available, could you please request for a HIL test of the above scenarios and provide the traces of it with PBA internal signals. So that I can find the root cause of the issue.
Function & Control CCB - FZI - 30.06.21 - 08:36:
Please investigate this point and advise the next steps. | Issue of PBC not reacting to HoldApply Requests Please review the attached trace for the issue described below. Expected behavior must be honored by PBC.
Scenario 1 (Trace: HoldAppy_Issue.zip)
Preconditions: Brake module in fallback mode (ESF), vehicle in dynamic state, EPB actuator state is released.
Action: Driver decelerates the vehicle by pressing the brake pedal. ESF function sends the hydraulic pressure, if any, to the front brakes, hydraulically isolates rear brakes and sets PbcInApplyReleaseRequest = DynamicApply to get support from EPB.
Expected behavior: When vehicle enters in static state, host transitions PbcInApplyReleaseRequest from DynamicApply to HoldApply. PBC should increase the CF demand until the HoldApplied state is reached, or set the actuator states to HoldApplied if the CF generated by RWU is equal or greater to the HoldApply demand.
Observed behavior: The EPB releases the clamp force achieved during RWU when HoldApply is requested. Final actuator state is Released.
Scenario 2 (Trace: HoldAppy_Issue_None_to_HoldApply.zip)
Preconditions: Brake module in fallback mode (ESF), vehicle in static state (speed < 5kph), EPB actuator state is released.
Action: Driver presses the brake pedal. ESF function sends the hydraulic pressure, if any, to the front brakes, hydraulically isolates rear brakes and sets PbcInApplyReleaseRequest = HoldApply to hold the vehicle with the EPB.
Expected behavior: PBC should command motors to increase the CF until the HoldApplied state is reached.
Observed behavior: The EPB stays in Released state.
Hint: ESF stands for Epb Support in Fallback mode. HoldApply was implemented in S650 with CR 4671476. <Pruthvi> (28.07.21 - 08:00):
--------------------------------------------------------------------------------
It is observed that GDAInGDHEnable is FALSE through out the test case in both the scenarios. As C.Torres observed GDAInStaticHoldDemand is 10 kN.
In revision 1.18.2.17.11.9.1.7 of 02_Architecture_Design i.e., Ford_S650_PBC_PARA_X01_300_00p build, we enabled GDH and Set STATIC_HOLD_DEMAND to STATIC_DEMAND (18.5KN).
In revision 1.18.2.17.11.9.1.8 of 02_Architecture_Design i.e., Ford_S650_PBC_PARA_X01_400_00p build, we updated STATIC_HOLD_DEMAND value from 18.5 to 8kN.
The reason for the above issue of PBC not reacting to HoldApply Requests is using of incorrect parameter file with HoldApply deactivated in it.
Proposal of next steps:
@Florian Zimmer :Please reject this CR as there is no software update required from PBC end.
@C.Torres: Please inform host to use the latest PBC_APPL and PBC_PARA software(Ford_S650_PBC_APPL_X01_400_00p, Ford_S650_PBC_PARA_X01_400_00p).
--------------------------------------------------------------------------------
<C.Torres (27.07.21 - 23:26)>: Attached is zip file "HoldApply_Issue_with_Demarb-FuncMan-GDA-RWU_signals.zip". Test was performed on an S650 vehicle. GDA and RWU were recorded together and Demarb and FuncMan were recorded together in different traces. From what I could observe, signal GDAInStaticHoldDemand is 10 kN but it should be 8kN, that's a suspicion of incorrect parameter file with HoldApply possibly deactivated.
<C.Torres (19.07.21 - 23:26)>: Attached is zip file "HoldApply_Issue_with_PBA_signals", it contains the requested traces. V14 was recorded with CANape 14 and V17 with CANape V17 but test case is the same.
Test was performed on another S650 vehicle. Host provided a .map file with the addresses of PBA signals, but not all PBA signals matched between .map and PbcInterface.a2l file.
Attached are .map and .a2l files for reference, in case there is any signal missing, please mark it in both files and a new trace will be recorded asap.
<Pruthvi> (14.07.21 - 15:30):
--------------------------------------------------------------------------------
I looked into the attached traces. I don’t see any reason why Hold Apply is not being performed. So I tried to replicate the scenario in my VectorCast environment with latest software available.
For me Hold Apply has performed and the results were as expected.
@Torres Cabrera Christian Alvaro LVN ADBY11 : As we discussed the Open point is based on vehicle test and tested on latest software available, could you please request for a HIL test of the above scenarios and provide the traces of it with PBA internal signals. So that I can find the root cause of the issue.
Function & Control CCB - FZI - 30.06.21 - 08:36:
Please investigate this point and advise the next steps. |
|
[BSW_Test]:[1.121]:Issue with vehicle speed signals update with Hard reset Issue: Vehicle speed signal values are not changing aftera Hard reset
Procedure:
1_S: Provide a vehicle speed by updating Throttle.
2_S: Request the wakeup condition (A Hard Reset - 11 01)
3_V: Verify the Vehicle speeds (LongitudinalVehicleSpeed' (VehSpdLgtForBkp)) are getting updated after 150ms
Expected result: There should be No change in vehicle speed signal within 150ms of time when a hard reset is made
Observed result: The signal is not observed with any change when a hard reset is made, and the changes in speed are observed normally.
References: Geely_Lotus_RBCM_SWRS_Internal_44745
28-Sept-2021:
When wake up condition is done by providing voltage = 0V, the vehicle speed is updated after 300ms SWPM - Y.Meng - 06.01.22 - 17:22:
-------------------------------------------------------
This is depends on the ECU wake up time | [BSW_Test]:[1.121]:Issue with vehicle speed signals update with Hard reset Issue: Vehicle speed signal values are not changing aftera Hard reset
Procedure:
1_S: Provide a vehicle speed by updating Throttle.
2_S: Request the wakeup condition (A Hard Reset - 11 01)
3_V: Verify the Vehicle speeds (LongitudinalVehicleSpeed' (VehSpdLgtForBkp)) are getting updated after 150ms
Expected result: There should be No change in vehicle speed signal within 150ms of time when a hard reset is made
Observed result: The signal is not observed with any change when a hard reset is made, and the changes in speed are observed normally.
References: Geely_Lotus_RBCM_SWRS_Internal_44745
28-Sept-2021:
When wake up condition is done by providing voltage = 0V, the vehicle speed is updated after 300ms SWPM - Y.Meng - 06.01.22 - 17:22:
-------------------------------------------------------
This is depends on the ECU wake up time |
|
[BSW_Test]:[1.121]:Issue with wheel speed signal update with usage mode states Issue: Usage mode signal "VehModMngtGlbSafe1UsgModSts" not getting updated to the states 11, 13
Procedure:
1_S: Set the signal "VehModMngtGlbSafe1UsgModSts" values to 0,1,11,13
2_V: Verify the Vehicle speeds (LongitudinalVehicleSpeed' (VehSpdLgtForBkp)) is able get updated in the above states
Expected result: With the usage mode values 11, 13 also the vehicle speed signal values should get updated.
Observed Result:
Usage mode signal "VehModMngtGlbSafe1UsgModSts" not getting updated to the states 11, 13
References: Geely_Lotus_RBCM_SWRS_Internal_44744
Logs attached. SWPM - Y.Meng - 02.11.21 - 08:18:
----------------------------------------------------------------------------------------
Discuss with Requirment and system team, as no SW implemention in BSW side, related requirement will mark as PSW requirement to analyze.
Sys requirement team will update requirement ID "Geely_EPA_SBM_SysDesign_1191" set PSW team as requirement analyzer.
-----------------------Abhilash-----------------------------------------------------
RbcmChas1Fr03:VehSpdLgtForBkpVehSpdLgtA is implemented based on inputs from PSW team.
So Geely_Lotus_RBCM_SWRS_Internal_44744 is observed as deviation. Need confirmation from PSW team correctness on implementation.
Geely_Lotus_RBCM_SWRS_Internal_44744:
'LongitudinalVehicleSpeed'
The SW shall sent out the vehicle speed in following usage modes:
- driving(ignore car mode),
- active(ignore car mode),
- convenience,
- inactive.
Precondition:
- System is awake. | [BSW_Test]:[1.121]:Issue with wheel speed signal update with usage mode states Issue: Usage mode signal "VehModMngtGlbSafe1UsgModSts" not getting updated to the states 11, 13
Procedure:
1_S: Set the signal "VehModMngtGlbSafe1UsgModSts" values to 0,1,11,13
2_V: Verify the Vehicle speeds (LongitudinalVehicleSpeed' (VehSpdLgtForBkp)) is able get updated in the above states
Expected result: With the usage mode values 11, 13 also the vehicle speed signal values should get updated.
Observed Result:
Usage mode signal "VehModMngtGlbSafe1UsgModSts" not getting updated to the states 11, 13
References: Geely_Lotus_RBCM_SWRS_Internal_44744
Logs attached. SWPM - Y.Meng - 02.11.21 - 08:18:
----------------------------------------------------------------------------------------
Discuss with Requirment and system team, as no SW implemention in BSW side, related requirement will mark as PSW requirement to analyze.
Sys requirement team will update requirement ID "Geely_EPA_SBM_SysDesign_1191" set PSW team as requirement analyzer.
-----------------------Abhilash-----------------------------------------------------
RbcmChas1Fr03:VehSpdLgtForBkpVehSpdLgtA is implemented based on inputs from PSW team.
So Geely_Lotus_RBCM_SWRS_Internal_44744 is observed as deviation. Need confirmation from PSW team correctness on implementation.
Geely_Lotus_RBCM_SWRS_Internal_44744:
'LongitudinalVehicleSpeed'
The SW shall sent out the vehicle speed in following usage modes:
- driving(ignore car mode),
- active(ignore car mode),
- convenience,
- inactive.
Precondition:
- System is awake. |
|
[X400-002][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Detection time for MSG_GETRIEBE_11_CRC fault. 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. CR Analyzed | [X400-002][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Detection time for MSG_GETRIEBE_11_CRC fault. 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. CR Analyzed |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
2) See attachment
3) Please rename the following monitors:
-a) -
4) Please remove the following monitors:
-a) -
5) Please update passing times of the following monitors:
-a) see OP 5046942
6) Please update detection and passing times due to new formulas. GordonR1, 11.07.2021:
Please update monitor times according to attachment VW_MEB_UNECE_EBB_FailsafeManual_Comms_401_e2.xlsx
Vlad Marisescu (19.08.2021):
--------------------------------------------------------------------------------
Brief analysis summary: [UN ECE EBB] [SW X0401] Comms SiSo Freeze Definition
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Tasks:
SiSo/OBD team
1.[UN ECE EBB] [SW X0401] update FSM detection and passing time according to attachment
--------------------------------------------------------------------------------
Owner: Vlad Marisescu Reviewer: Cristian Traier Estimated effort/h: 10h | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
2) See attachment
3) Please rename the following monitors:
-a) -
4) Please remove the following monitors:
-a) -
5) Please update passing times of the following monitors:
-a) see OP 5046942
6) Please update detection and passing times due to new formulas. GordonR1, 11.07.2021:
Please update monitor times according to attachment VW_MEB_UNECE_EBB_FailsafeManual_Comms_401_e2.xlsx
Vlad Marisescu (19.08.2021):
--------------------------------------------------------------------------------
Brief analysis summary: [UN ECE EBB] [SW X0401] Comms SiSo Freeze Definition
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Tasks:
SiSo/OBD team
1.[UN ECE EBB] [SW X0401] update FSM detection and passing time according to attachment
--------------------------------------------------------------------------------
Owner: Vlad Marisescu Reviewer: Cristian Traier Estimated effort/h: 10h |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
GordonR1, 10.01.2022: No required input from Rx-Tx-List or attachment.
2) Please set the passing time of the following fault monitors to 500ms:
MSG_ESC_51_CRC_FAULT
MSG_ESP_21_CRC_FAULT
MSG_GETRIEBE_11_CRC_FAULT
MSG_KLEMMEN_STATUS_01_CRC_FAULT
MSG_M2S_CONTROL_CRC_FAULT
MSG_M2S_ENV_DATA_CRC_FAULT
MSG_M2S_ENV_DATA_FORCE_CRC_FAULT
MSG_M2S_ENV_DATA_FORCE_REAR_CRC_FAULT
MSG_M2S_ENV_DATA_MOTION_CRC_FAULT
MSG_M2S_ENV_DATA_SPEED_FRONT_CRC_FAULT
MSG_M2S_ENV_DATA_SPEED_REAR_CRC_FAULT
MSG_MOTOR_57_CRC_FAULT
MSG_VMM_02_CRC_FAULT
3) Please link the following input validtions to COMMS_E2E_PW_PLAUSIBILITY_FAILURE:
- HMS_ACTIVE_SYSTEM
- HMS_SYSTEM_STATE
- VMM_NOTSTOPP_STATUS
4) Please link the following input validtions to MSG_DATA_BUS_0_GLOBAL_TIMEOUT:
- ENGINE_RUN_STATUS
- HMS_SYSTEM_STATE
5) Please link the following input validtions to CAN_DEVICE_0_BUS_OFF:
- ENGINE_RUN_STATUS
- HMS_SYSTEM_STATE
-
6) Please link the following input validtions to CAN_DEVICE_1_BUS_OFF:
- DRIVE_CYCLE_STATUS
7) Please link the following input validtions to MSG_VMM_02_TIMEOUT, MSG_VMM_02_RC_FAULT, MSG_VMM_02_CRC_FAULT:
- HMS_ACTIVE_SYSTEM
- HMS_SYSTEM_STATE GordonR1, 10.01.2022: Analysis finished from Comms side. | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
GordonR1, 10.01.2022: No required input from Rx-Tx-List or attachment.
2) Please set the passing time of the following fault monitors to 500ms:
MSG_ESC_51_CRC_FAULT
MSG_ESP_21_CRC_FAULT
MSG_GETRIEBE_11_CRC_FAULT
MSG_KLEMMEN_STATUS_01_CRC_FAULT
MSG_M2S_CONTROL_CRC_FAULT
MSG_M2S_ENV_DATA_CRC_FAULT
MSG_M2S_ENV_DATA_FORCE_CRC_FAULT
MSG_M2S_ENV_DATA_FORCE_REAR_CRC_FAULT
MSG_M2S_ENV_DATA_MOTION_CRC_FAULT
MSG_M2S_ENV_DATA_SPEED_FRONT_CRC_FAULT
MSG_M2S_ENV_DATA_SPEED_REAR_CRC_FAULT
MSG_MOTOR_57_CRC_FAULT
MSG_VMM_02_CRC_FAULT
3) Please link the following input validtions to COMMS_E2E_PW_PLAUSIBILITY_FAILURE:
- HMS_ACTIVE_SYSTEM
- HMS_SYSTEM_STATE
- VMM_NOTSTOPP_STATUS
4) Please link the following input validtions to MSG_DATA_BUS_0_GLOBAL_TIMEOUT:
- ENGINE_RUN_STATUS
- HMS_SYSTEM_STATE
5) Please link the following input validtions to CAN_DEVICE_0_BUS_OFF:
- ENGINE_RUN_STATUS
- HMS_SYSTEM_STATE
-
6) Please link the following input validtions to CAN_DEVICE_1_BUS_OFF:
- DRIVE_CYCLE_STATUS
7) Please link the following input validtions to MSG_VMM_02_TIMEOUT, MSG_VMM_02_RC_FAULT, MSG_VMM_02_CRC_FAULT:
- HMS_ACTIVE_SYSTEM
- HMS_SYSTEM_STATE GordonR1, 10.01.2022: Analysis finished from Comms side. |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. This CR shall be used to create an actual Baseline in Doors and generate source code for EBB Sw X0403
Please create a task for System OBD Team to provide the DOORS SISO Baselines TRAND (2022.02.16):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The FailsafeSpecification usually affects constant data and callbacks within the StateManagement and Persistency domain (DmtConfig, DEM, FIM, NVM, RTE).
All direct changes of the DOORS export shall be integrated with this item, so distinct tasks are required for the involved teams.
Other additional configuration changes are noted within the respective task, if applicable (eg as comment 'special work' and SpawnedBy CR relationship).
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps: refer to task proposal for details
--------------------------------------------------------------------------------
- Special works:
Carry-Over CR 5952463.
Takeover det2dav.xsl for TripCounter 2 and RequiredDemCallbackEventStatusChanged in DET.
Carry-Over CR 5900243.
Carry-Over CR 5995627.
Carry-Over task 5997519 | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. This CR shall be used to create an actual Baseline in Doors and generate source code for EBB Sw X0403
Please create a task for System OBD Team to provide the DOORS SISO Baselines TRAND (2022.02.16):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The FailsafeSpecification usually affects constant data and callbacks within the StateManagement and Persistency domain (DmtConfig, DEM, FIM, NVM, RTE).
All direct changes of the DOORS export shall be integrated with this item, so distinct tasks are required for the involved teams.
Other additional configuration changes are noted within the respective task, if applicable (eg as comment 'special work' and SpawnedBy CR relationship).
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Proposal of next steps: refer to task proposal for details
--------------------------------------------------------------------------------
- Special works:
Carry-Over CR 5952463.
Takeover det2dav.xsl for TripCounter 2 and RequiredDemCallbackEventStatusChanged in DET.
Carry-Over CR 5900243.
Carry-Over CR 5995627.
Carry-Over task 5997519 |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
2) See attachment
3) Please rename the following monitors:
-a) -
4) Please remove the following monitors:
-a) -
5) Please update detection and passing times of all monitors due to activation of direct fault healing etc.!
-a) TBD
6) Please consider that this SW now takes MQB EBB as a baseline. 29.10.2021,AdrFan
Please adapt Siso as mentioned in attachment VC_Siso_Definition_VW_UN_ECE_EBB_402_ChangeMonitorTimes.xlsx.
Please set Timeout monitor MSG_ORU_01_TIMEOUT as obsolete for UN ECE EBB project.
Stanca Ionut Adrian (07.10.21 - 18:00):
--------------------------------------------------------------------------------
Brief analysis summary:
adapt Siso as mentioned in attachment VC_Siso_Definition_VW_UN_ECE_EBB_402_ChangeMonitorTimes.xlsx.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task:
1.[UN ECE EBB] [SW X0402]Adapt detection time, passing time and monitoring rate according to attachment
2.Set MSG_ORU_01_TIMEOUT as Obsolete
--------------------------------------------------------------------------------
Owner: Vlad Marisescu
Reviewer: Stanca Ionut Adrian
Estimated effort/h: 4h | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) General
Please collect all required Fault Monitors and Input Validations and create a task for SiSo team.
Please review latest SiSo changes.
Please check, whether the FSM has to be updated.
2) See attachment
3) Please rename the following monitors:
-a) -
4) Please remove the following monitors:
-a) -
5) Please update detection and passing times of all monitors due to activation of direct fault healing etc.!
-a) TBD
6) Please consider that this SW now takes MQB EBB as a baseline. 29.10.2021,AdrFan
Please adapt Siso as mentioned in attachment VC_Siso_Definition_VW_UN_ECE_EBB_402_ChangeMonitorTimes.xlsx.
Please set Timeout monitor MSG_ORU_01_TIMEOUT as obsolete for UN ECE EBB project.
Stanca Ionut Adrian (07.10.21 - 18:00):
--------------------------------------------------------------------------------
Brief analysis summary:
adapt Siso as mentioned in attachment VC_Siso_Definition_VW_UN_ECE_EBB_402_ChangeMonitorTimes.xlsx.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task:
1.[UN ECE EBB] [SW X0402]Adapt detection time, passing time and monitoring rate according to attachment
2.Set MSG_ORU_01_TIMEOUT as Obsolete
--------------------------------------------------------------------------------
Owner: Vlad Marisescu
Reviewer: Stanca Ionut Adrian
Estimated effort/h: 4h |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) Implement all necessary Failsafe changes in Comms code for this Build after SiSo-Freeze, as requested by spawned by SiSo CR .
2) Please rename the following monitors:
-a) ..
3) Please update the (weight and) goal of following monitors in CommsDb:
-a) MSG_M2S_CONTROL_M2S_MASTER_FAILURE_INDICATE --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Adjust timings:
- MSG_DATA_BUS_0_GLOBAL_TIMEOUT: goal=350, passWeight=350
Change PDU to E2E:
- Getriebe_11
- Klemmen_Status_01
- Motor_57
Carry over the signal implementation + invalid faults for:
- GE_Fahrstufe
- MO_Fahrzeugtyp
- MO_Fahrbereitschaft
- MO_Drehzahl_EM
- MO_Uebersetzung_EM
- MO_OBD_Typ
- ZM_Standzeit
Check in the E2E_Parameter_List used for UN ECE EBB in Comms\CommsFaultHandler\Cfg\Doc.
Drop the E2E_Parameter_List used for MQB EBB.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Adriana Copil
Proposal of next steps (incl. effort/h and verification): 1 Task
--------------------------------------------------------------------------------
TASK 1: [COMMS]
------------------------------------------------------
Title: [UN ECE EBB][SW X0401] Comms Failsafe
Description:
Adjust timings:
- MSG_DATA_BUS_0_GLOBAL_TIMEOUT: goal=350, passWeight=350
Change PDU to E2E:
- Getriebe_11
- Klemmen_Status_01
- Motor_57
Carry over the signal implementation + invalid faults for:
- GE_Fahrstufe
- MO_Fahrzeugtyp
- MO_Fahrbereitschaft
- MO_Drehzahl_EM
- MO_Uebersetzung_EM
- MO_OBD_Typ
- ZM_Standzeit
Check in the E2E_Parameter_List used for UN ECE EBB in Comms\CommsFaultHandler\Cfg\Doc.
Drop the E2E_Parameter_List used for MQB EBB.
Owner: Adriana Copil
Reviewer: Ruben Gordon
Estimated effort: 16h
Planned Completion Date: 15th of Oct | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 1) Implement all necessary Failsafe changes in Comms code for this Build after SiSo-Freeze, as requested by spawned by SiSo CR .
2) Please rename the following monitors:
-a) ..
3) Please update the (weight and) goal of following monitors in CommsDb:
-a) MSG_M2S_CONTROL_M2S_MASTER_FAILURE_INDICATE --------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Adjust timings:
- MSG_DATA_BUS_0_GLOBAL_TIMEOUT: goal=350, passWeight=350
Change PDU to E2E:
- Getriebe_11
- Klemmen_Status_01
- Motor_57
Carry over the signal implementation + invalid faults for:
- GE_Fahrstufe
- MO_Fahrzeugtyp
- MO_Fahrbereitschaft
- MO_Drehzahl_EM
- MO_Uebersetzung_EM
- MO_OBD_Typ
- ZM_Standzeit
Check in the E2E_Parameter_List used for UN ECE EBB in Comms\CommsFaultHandler\Cfg\Doc.
Drop the E2E_Parameter_List used for MQB EBB.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Adriana Copil
Proposal of next steps (incl. effort/h and verification): 1 Task
--------------------------------------------------------------------------------
TASK 1: [COMMS]
------------------------------------------------------
Title: [UN ECE EBB][SW X0401] Comms Failsafe
Description:
Adjust timings:
- MSG_DATA_BUS_0_GLOBAL_TIMEOUT: goal=350, passWeight=350
Change PDU to E2E:
- Getriebe_11
- Klemmen_Status_01
- Motor_57
Carry over the signal implementation + invalid faults for:
- GE_Fahrstufe
- MO_Fahrzeugtyp
- MO_Fahrbereitschaft
- MO_Drehzahl_EM
- MO_Uebersetzung_EM
- MO_OBD_Typ
- ZM_Standzeit
Check in the E2E_Parameter_List used for UN ECE EBB in Comms\CommsFaultHandler\Cfg\Doc.
Drop the E2E_Parameter_List used for MQB EBB.
Owner: Adriana Copil
Reviewer: Ruben Gordon
Estimated effort: 16h
Planned Completion Date: 15th of Oct |
|
[X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 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. Retest is failed so new analysis is needed till then this CR is not needed | [X400-001][CAT2][TCS][VW_UNECE_EBB][COMMS]: Issue with Fault Passing time for few CAN Communication Faults. 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. Retest is failed so new analysis is needed till then this CR is not needed |
|
[Issue][ITC][MIL][StateHandler] - PostrunTimer is incrementing by 2 per sample when ExtBrReq or NmKeepAliveRequired signals are active Problempath:
BC/BC_SWCs/BcMain/Subsystem/BcMain/BcMain_LibBlock/BcMain_MediumCyclic/InitShSmcArb/StateHandler/EbbStateDetermination/Postrun_Action/PhaseA_FullBoost
Build version: BC_GEN1_001_753
SWC-PTC-Checkpoint: 1.17
Issue description:
BoostSystemState is in Postrun, FullBoost phase is ongoing and PostrunTimer reached POSTRUN_BB_REDUCTION_MONITOR_END(70sec) with active EBR request and/or IsNmKeepAliveRequired signal. In this case system stays in FullBoost state by incrementing PostrunTimer. As per current implementation, PostrunTimer is incrementing by 2 per sample because counter logic is implemented twice in Postrun chart. Please see the screenshots attached.
Requirements : DE_SH_Postrun_Action_001, DE_SH_Postrun_Action_002, DE_SH_Postrun_Action_003
Testcase details:
Precondition:
NA
Action:
Step 1 : BoostSystemState reaches POSTRUN state and enters FullBoost phase
Step 2 : After 40sec, BrakePedal applied is set and EpbStatus is Open
Step 3 : After 10sec, BrakePedal is released.
Step 4 : After 10sec, ExtBrReq is set to ACTIVE
Step 5 : After 10ms, ExtBrReq is set to VOLUMECOMPENSATION
Step 6 : After 10ms, ExtBrReq is set to RUNOUT
Step 7 : After 10ms, IsNmKeepAliveRequired is set to TRUE
Step 8 : After 10ms, ExtBrReq is set to NOT_ACTIVE
Step 9 : After 10ms, IsNmKeepAliveRequired is set to FALSE
Expected Behaviour:
The PostrunTImer value is incremented by 1 per sample if EBR request and/or IsNmKeepAliveRequired signals are active during FullBoost phase.
At Step 1, PostrPhase = PHASE_FULLBOOST and Here PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_START time (40sec)
At Step 2, Here, when PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_END time (50sec) , MaxBpaTimer starts incrementing by 1 because BPA is true. BcCommunicationRequired is set to TRUE when PostrunTimer = 50sec and MaxBpaTimer is >= POSTRUN_INPUTROD_MONITOR_DURATION(1sec)
At Step 3, Here, when PostrTimer reaches POSTRUN_BB_REDUCTION_MONITOR_START(60s) (or POSTRUN_EPB_APPL_WARNING_DURATION(10s)+POSTRUN_EPB_APPL_MONITOR_END(50s)) time BcCommunicationRequired is set to FALSE and MaxBpaTimer is cleared.
At Step 4, MaxBpaTimer remains 0 because BPA is not applied and PostrunTimer reaches POSTRUN_BB_REDUCTION_MONITOR_END(70s) or PostrunMin time
Here, PostrunTimer incremented by 1 because ExtBrReq is Active.
At Step 5, Here, PostrunTimer incremented by 1 because ExtBrReq is VolumeCompensation.
At Step 6, Here, PostrunTimer incremented by 1 because ExtBrReq is Runout.
At Step 7, Here, PostrunTimer incremented by 1 because ExtBrReq is Runout.
At Step 8, Here, PostrunTimer incremented by 1 because ExtBrReq is NotActive and .IsNmKeepAliveRequired is true
At Step 9, Here, PostrPhase is set to PHASE_SHUTDOWN because ExtBrReq is NotActive and .IsNmKeepAliveRequired is false and PostrunTimer value is saved and used further.
Actual behaviour:
The PostrunTImer value is incrementing by 2 per sample when EBR request and/or IsNmKeepAliveRequired signals are active during FullBoost phase.
At Step 1, PostrPhase = PHASE_FULLBOOST and Here PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_START time (40sec)
At Step 2, Here, when PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_END time (50sec) , MaxBpaTimer starts incrementing by 1 because BPA is true. BcCommunicationRequired is set to TRUE when PostrunTimer = 50sec and MaxBpaTimer is >= POSTRUN_INPUTROD_MONITOR_DURATION(1sec)
At Step 3, Here, when PostrTimer reaches POSTRUN_BB_REDUCTION_MONITOR_START(60s) (or POSTRUN_EPB_APPL_WARNING_DURATION(10s)+POSTRUN_EPB_APPL_MONITOR_END(50s)) time BcCommunicationRequired is set to FALSE and MaxBpaTimer is cleared.
At Step 4, MaxBpaTimer remains 0 because BPA is not applied and PostrunTimer reaches POSTRUN_BB_REDUCTION_MONITOR_END(70s) or PostrunMin time
Here, PostrunTimer incrementing by 2 because ExtBrReq is Active.
At Step 5, Here, PostrunTimer incrementing by 2 because ExtBrReq is VolumeCompensation.
At Step 6, Here, PostrunTimer incrementing by 2 because ExtBrReq is Runout.
At Step 7, Here, PostrunTimer incrementing by 2 because ExtBrReq is Runout.
At Step 8, Here, PostrunTimer incrementing by 2 because ExtBrReq is NotActive and .IsNmKeepAliveRequired is true
At Step 9, Here, PostrPhase is set to PHASE_SHUTDOWN because ExtBrReq is NotActive and .IsNmKeepAliveRequired is false and wrong PostrunTimer value is saved and used further.
Please see results snap attached.
Further Information:
The path PostrTimer < ShParaBus.PostrunMinTime cannot be achieved with default parameter values because, the value of parameters PostrunMinTime and POSTRUN_BB_REDUCTION_MONITOR_END is same which is 70sec. In unit testing, inorder to cover this path the value of POSTRUN_BB_REDUCTION_MONITOR_END paramter must be given less than PostrunMinTime. Please confirm. --------------------------------------------------------------------------------
Brief analysis summary: The state handler model (post run action) must be adapted to solve the issue. In the current implementation the post run timer is increased twice within one execution cycle at the end of the post run phase. The finding is not critical and has no functional influence since it occurs only at the end of phase and the timer is reset at beginning of next phase.
The following statements have to be removed:
In:
StateHandler_Lib/StateHandler/EbbStateDetermination/StateActions/Postrun_Action/PhaseA_FullBoost
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Chemnitz
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: [VW MQB48W][EBB][F&C][StateHandler] - PostrunTimer is incrementing by 2 per sample when ExtBrReq or NmKeepAliveRequired signals are active
--------------------------------------------------------------------------------
Description: see analysis summary
Owner: Jaya Vijayvergiya
Reviewer: Till Goedert
Estimated effort/h: 6
--------------------------------------------------------------------------------
[Optional] Planed completion date:
-------------------------------------------------------------------------------- | [Issue][ITC][MIL][StateHandler] - PostrunTimer is incrementing by 2 per sample when ExtBrReq or NmKeepAliveRequired signals are active Problempath:
BC/BC_SWCs/BcMain/Subsystem/BcMain/BcMain_LibBlock/BcMain_MediumCyclic/InitShSmcArb/StateHandler/EbbStateDetermination/Postrun_Action/PhaseA_FullBoost
Build version: BC_GEN1_001_753
SWC-PTC-Checkpoint: 1.17
Issue description:
BoostSystemState is in Postrun, FullBoost phase is ongoing and PostrunTimer reached POSTRUN_BB_REDUCTION_MONITOR_END(70sec) with active EBR request and/or IsNmKeepAliveRequired signal. In this case system stays in FullBoost state by incrementing PostrunTimer. As per current implementation, PostrunTimer is incrementing by 2 per sample because counter logic is implemented twice in Postrun chart. Please see the screenshots attached.
Requirements : DE_SH_Postrun_Action_001, DE_SH_Postrun_Action_002, DE_SH_Postrun_Action_003
Testcase details:
Precondition:
NA
Action:
Step 1 : BoostSystemState reaches POSTRUN state and enters FullBoost phase
Step 2 : After 40sec, BrakePedal applied is set and EpbStatus is Open
Step 3 : After 10sec, BrakePedal is released.
Step 4 : After 10sec, ExtBrReq is set to ACTIVE
Step 5 : After 10ms, ExtBrReq is set to VOLUMECOMPENSATION
Step 6 : After 10ms, ExtBrReq is set to RUNOUT
Step 7 : After 10ms, IsNmKeepAliveRequired is set to TRUE
Step 8 : After 10ms, ExtBrReq is set to NOT_ACTIVE
Step 9 : After 10ms, IsNmKeepAliveRequired is set to FALSE
Expected Behaviour:
The PostrunTImer value is incremented by 1 per sample if EBR request and/or IsNmKeepAliveRequired signals are active during FullBoost phase.
At Step 1, PostrPhase = PHASE_FULLBOOST and Here PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_START time (40sec)
At Step 2, Here, when PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_END time (50sec) , MaxBpaTimer starts incrementing by 1 because BPA is true. BcCommunicationRequired is set to TRUE when PostrunTimer = 50sec and MaxBpaTimer is >= POSTRUN_INPUTROD_MONITOR_DURATION(1sec)
At Step 3, Here, when PostrTimer reaches POSTRUN_BB_REDUCTION_MONITOR_START(60s) (or POSTRUN_EPB_APPL_WARNING_DURATION(10s)+POSTRUN_EPB_APPL_MONITOR_END(50s)) time BcCommunicationRequired is set to FALSE and MaxBpaTimer is cleared.
At Step 4, MaxBpaTimer remains 0 because BPA is not applied and PostrunTimer reaches POSTRUN_BB_REDUCTION_MONITOR_END(70s) or PostrunMin time
Here, PostrunTimer incremented by 1 because ExtBrReq is Active.
At Step 5, Here, PostrunTimer incremented by 1 because ExtBrReq is VolumeCompensation.
At Step 6, Here, PostrunTimer incremented by 1 because ExtBrReq is Runout.
At Step 7, Here, PostrunTimer incremented by 1 because ExtBrReq is Runout.
At Step 8, Here, PostrunTimer incremented by 1 because ExtBrReq is NotActive and .IsNmKeepAliveRequired is true
At Step 9, Here, PostrPhase is set to PHASE_SHUTDOWN because ExtBrReq is NotActive and .IsNmKeepAliveRequired is false and PostrunTimer value is saved and used further.
Actual behaviour:
The PostrunTImer value is incrementing by 2 per sample when EBR request and/or IsNmKeepAliveRequired signals are active during FullBoost phase.
At Step 1, PostrPhase = PHASE_FULLBOOST and Here PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_START time (40sec)
At Step 2, Here, when PostrunTimer is lesser than POSTRUN_EPB_APPL_MONITOR_END time (50sec) , MaxBpaTimer starts incrementing by 1 because BPA is true. BcCommunicationRequired is set to TRUE when PostrunTimer = 50sec and MaxBpaTimer is >= POSTRUN_INPUTROD_MONITOR_DURATION(1sec)
At Step 3, Here, when PostrTimer reaches POSTRUN_BB_REDUCTION_MONITOR_START(60s) (or POSTRUN_EPB_APPL_WARNING_DURATION(10s)+POSTRUN_EPB_APPL_MONITOR_END(50s)) time BcCommunicationRequired is set to FALSE and MaxBpaTimer is cleared.
At Step 4, MaxBpaTimer remains 0 because BPA is not applied and PostrunTimer reaches POSTRUN_BB_REDUCTION_MONITOR_END(70s) or PostrunMin time
Here, PostrunTimer incrementing by 2 because ExtBrReq is Active.
At Step 5, Here, PostrunTimer incrementing by 2 because ExtBrReq is VolumeCompensation.
At Step 6, Here, PostrunTimer incrementing by 2 because ExtBrReq is Runout.
At Step 7, Here, PostrunTimer incrementing by 2 because ExtBrReq is Runout.
At Step 8, Here, PostrunTimer incrementing by 2 because ExtBrReq is NotActive and .IsNmKeepAliveRequired is true
At Step 9, Here, PostrPhase is set to PHASE_SHUTDOWN because ExtBrReq is NotActive and .IsNmKeepAliveRequired is false and wrong PostrunTimer value is saved and used further.
Please see results snap attached.
Further Information:
The path PostrTimer < ShParaBus.PostrunMinTime cannot be achieved with default parameter values because, the value of parameters PostrunMinTime and POSTRUN_BB_REDUCTION_MONITOR_END is same which is 70sec. In unit testing, inorder to cover this path the value of POSTRUN_BB_REDUCTION_MONITOR_END paramter must be given less than PostrunMinTime. Please confirm. --------------------------------------------------------------------------------
Brief analysis summary: The state handler model (post run action) must be adapted to solve the issue. In the current implementation the post run timer is increased twice within one execution cycle at the end of the post run phase. The finding is not critical and has no functional influence since it occurs only at the end of phase and the timer is reset at beginning of next phase.
The following statements have to be removed:
In:
StateHandler_Lib/StateHandler/EbbStateDetermination/StateActions/Postrun_Action/PhaseA_FullBoost
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): C. Chemnitz
Proposal of next steps (incl. effort/h and verification):
--------------------------------------------------------------------------------
Task: [VW MQB48W][EBB][F&C][StateHandler] - PostrunTimer is incrementing by 2 per sample when ExtBrReq or NmKeepAliveRequired signals are active
--------------------------------------------------------------------------------
Description: see analysis summary
Owner: Jaya Vijayvergiya
Reviewer: Till Goedert
Estimated effort/h: 6
--------------------------------------------------------------------------------
[Optional] Planed completion date:
-------------------------------------------------------------------------------- |
|
PR58364 Jeep Compass ARM calibration update for EMEA variants ARM calibration update driven by customer request to have more sensitive activation and longer pressure duration for the control. [02.07.2021, K.Kampa]: Parameter updates are reasonable. | PR58364 Jeep Compass ARM calibration update for EMEA variants ARM calibration update driven by customer request to have more sensitive activation and longer pressure duration for the control. [02.07.2021, K.Kampa]: Parameter updates are reasonable. |
|
[FCA_WS][SFIT]: For Few faults FSM is in "AGREED" state, Variables related to faultstatus are not found in elf. This CR is used to Plan/Monitor the SWE 1 work for "Manage Vehicle Interface" feature Summary
This CR will be used to update SWE.1 module: "GenC Software Requirements Manage Vehicle Interface" for MY23 AA00 release
Source Requirements Change
Customer Requirements
WS EPS - UDS_DTC_Criteria Matrix_5.21.20.xlsx
DOORS: http://sshruk-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational::1-47c42cc36f5a1680-M-1b5000000006709
System Requirements:
No change in system requirements.
Software Requirement Changes:
Please refer the impact analysis document.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/Steering/Projects/FCA%2dFIAT/WS/PR56368%5fLVS%5fENG%5fBUSDEV%5fMY2023%5fFCA%5fWS%5fEPS%5fBD%5fHRoom%5fNA/30%5fSoftware/3030%5fRequirements/3038%5fImpactAnalysis/3038%5fFCA%5fWS%5fPWB%5fImpact%5fAnalysis/project.pj&selection=%223038%5fFI056368%5f4977142%5fTrailerReverseSteeringControl.docx%22
New requirements need to be added for DEM_IWSS_INVALID_FAULT
Complexity
Low
Fail Safe Manual Changes
Fail safe manual needs to be updates for fault detection and clear timeout values.
Task Identification and Effort Estimation
Task1 – [SWE.1] [MVI] Manage Vehicle Interface
Effort Estimate: 8 Hrs
Task2 -[SWE.1] FSM update - FCA_WS_MY23_AA00
Effort Estimate: 4hrs | [FCA_WS][SFIT]: For Few faults FSM is in "AGREED" state, Variables related to faultstatus are not found in elf. This CR is used to Plan/Monitor the SWE 1 work for "Manage Vehicle Interface" feature Summary
This CR will be used to update SWE.1 module: "GenC Software Requirements Manage Vehicle Interface" for MY23 AA00 release
Source Requirements Change
Customer Requirements
WS EPS - UDS_DTC_Criteria Matrix_5.21.20.xlsx
DOORS: http://sshruk-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational::1-47c42cc36f5a1680-M-1b5000000006709
System Requirements:
No change in system requirements.
Software Requirement Changes:
Please refer the impact analysis document.
url:integrity://skobde-mks.kobde.trw.com:7001/si/viewhistory?project=/Steering/Projects/FCA%2dFIAT/WS/PR56368%5fLVS%5fENG%5fBUSDEV%5fMY2023%5fFCA%5fWS%5fEPS%5fBD%5fHRoom%5fNA/30%5fSoftware/3030%5fRequirements/3038%5fImpactAnalysis/3038%5fFCA%5fWS%5fPWB%5fImpact%5fAnalysis/project.pj&selection=%223038%5fFI056368%5f4977142%5fTrailerReverseSteeringControl.docx%22
New requirements need to be added for DEM_IWSS_INVALID_FAULT
Complexity
Low
Fail Safe Manual Changes
Fail safe manual needs to be updates for fault detection and clear timeout values.
Task Identification and Effort Estimation
Task1 – [SWE.1] [MVI] Manage Vehicle Interface
Effort Estimate: 8 Hrs
Task2 -[SWE.1] FSM update - FCA_WS_MY23_AA00
Effort Estimate: 4hrs |
|
[FCA_WS][SFIT]: For Few faults FSM is in "AGREED" state, Variables related to faultstatus are not found in elf. D2 -- Problem Description (R: PRE):
For below faults, FSM is in "AGREED" state, Variables related to faultstatus are not found in elf.
DEM_PU_BD_L1_FET_B1_OC_FAULT
DEM_PU_BD_L1_FET_B1_SC_FAULT
DEM_PU_BD_L1_FET_B2_OC_FAULT
DEM_PU_BD_L1_FET_B2_SC_FAULT
DEM_PU_BD_L1_FET_B3_OC_FAULT
DEM_PU_BD_L1_FET_B3_SC_FAULT
DEM_PU_BD_L1_FET_T1_OC_FAULT
DEM_PU_BD_L1_FET_T2_OC_FAULT
DEM_PU_BD_L1_FET_T3_OC_FAULT
DEM_PU_BD_L1_FET_TOP_SC_FAULT
DEM_PU_BD_L1_SSPIR_FET_SC_FAULT
DEM_PU_BD_L1_SSPIR_FET1_OC_FAULT
DEM_PU_BD_L1_SSPIR_FET2_OC_FAULT
DEM_PU_BD_L1_SSPIR_FET3_OC_FAULT
DEM_PSU_UC_SUPPLY_FAULT
Requirement which is violated (R: Originator):
GenC_FSM_5090DEM_PU_BD_L1_FET_B1_OC_FAULT
GenC_FSM_5091DEM_PU_BD_L1_FET_B1_SC_FAULT
GenC_FSM_5092DEM_PU_BD_L1_FET_B2_OC_FAULT
GenC_FSM_5093DEM_PU_BD_L1_FET_B2_SC_FAULT
GenC_FSM_5094DEM_PU_BD_L1_FET_B3_OC_FAULT
GenC_FSM_5095DEM_PU_BD_L1_FET_B3_SC_FAULT
GenC_FSM_5096DEM_PU_BD_L1_FET_T1_OC_FAULT
GenC_FSM_5097DEM_PU_BD_L1_FET_T2_OC_FAULT
GenC_FSM_5098DEM_PU_BD_L1_FET_T3_OC_FAULT
GenC_FSM_5099DEM_PU_BD_L1_FET_TOP_SC_FAULT
GenC_FSM_5103DEM_PU_BD_L1_SSPIR_FET_SC_FAULT
GenC_FSM_5100DEM_PU_BD_L1_SSPIR_FET1_OC_FAULT
GenC_FSM_5101DEM_PU_BD_L1_SSPIR_FET2_OC_FAULT
GenC_FSM_5102DEM_PU_BD_L1_SSPIR_FET3_OC_FAULT
GenC_FSM_751DEM_PSU_UC_SUPPLY_FAULT
Expected behavior (R: Originator):
The faults to be tested in current Release:ASY-FI048465-S2-V00FBP2_0311
Operating Environment (R: Originator):
Software Test on release ASY-FI048465-S2-V00FBP2_0311 using the FCA_WS PIL rig with the PIL_Solution_WhiteBox project.
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
Outline the ICA
D4a -- Verified Root Cause (R: PRE):
Describe the result of the root cause analysis --> AGGREGATE RESULT OF ALL ACTION ITEMS HERE
D4b -- Verified Escape Point (R: PRE):
Describe the outcome of the escape point analysis
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
Please add Log Files and Par files captured during the testing and add it as an attachment to the open point. Outline briefly the file added and the content that it describes
D7 -- Lessons Learned (R: PRE):
Describe (where appropriate) particular contributions from individuals or teams. ToDo - Verification to be executed on BA00++ | [FCA_WS][SFIT]: For Few faults FSM is in "AGREED" state, Variables related to faultstatus are not found in elf. D2 -- Problem Description (R: PRE):
For below faults, FSM is in "AGREED" state, Variables related to faultstatus are not found in elf.
DEM_PU_BD_L1_FET_B1_OC_FAULT
DEM_PU_BD_L1_FET_B1_SC_FAULT
DEM_PU_BD_L1_FET_B2_OC_FAULT
DEM_PU_BD_L1_FET_B2_SC_FAULT
DEM_PU_BD_L1_FET_B3_OC_FAULT
DEM_PU_BD_L1_FET_B3_SC_FAULT
DEM_PU_BD_L1_FET_T1_OC_FAULT
DEM_PU_BD_L1_FET_T2_OC_FAULT
DEM_PU_BD_L1_FET_T3_OC_FAULT
DEM_PU_BD_L1_FET_TOP_SC_FAULT
DEM_PU_BD_L1_SSPIR_FET_SC_FAULT
DEM_PU_BD_L1_SSPIR_FET1_OC_FAULT
DEM_PU_BD_L1_SSPIR_FET2_OC_FAULT
DEM_PU_BD_L1_SSPIR_FET3_OC_FAULT
DEM_PSU_UC_SUPPLY_FAULT
Requirement which is violated (R: Originator):
GenC_FSM_5090DEM_PU_BD_L1_FET_B1_OC_FAULT
GenC_FSM_5091DEM_PU_BD_L1_FET_B1_SC_FAULT
GenC_FSM_5092DEM_PU_BD_L1_FET_B2_OC_FAULT
GenC_FSM_5093DEM_PU_BD_L1_FET_B2_SC_FAULT
GenC_FSM_5094DEM_PU_BD_L1_FET_B3_OC_FAULT
GenC_FSM_5095DEM_PU_BD_L1_FET_B3_SC_FAULT
GenC_FSM_5096DEM_PU_BD_L1_FET_T1_OC_FAULT
GenC_FSM_5097DEM_PU_BD_L1_FET_T2_OC_FAULT
GenC_FSM_5098DEM_PU_BD_L1_FET_T3_OC_FAULT
GenC_FSM_5099DEM_PU_BD_L1_FET_TOP_SC_FAULT
GenC_FSM_5103DEM_PU_BD_L1_SSPIR_FET_SC_FAULT
GenC_FSM_5100DEM_PU_BD_L1_SSPIR_FET1_OC_FAULT
GenC_FSM_5101DEM_PU_BD_L1_SSPIR_FET2_OC_FAULT
GenC_FSM_5102DEM_PU_BD_L1_SSPIR_FET3_OC_FAULT
GenC_FSM_751DEM_PSU_UC_SUPPLY_FAULT
Expected behavior (R: Originator):
The faults to be tested in current Release:ASY-FI048465-S2-V00FBP2_0311
Operating Environment (R: Originator):
Software Test on release ASY-FI048465-S2-V00FBP2_0311 using the FCA_WS PIL rig with the PIL_Solution_WhiteBox project.
Test case identification (R: Originator):
D3 -- Established Interim Containment Action (R: PRE):
Outline the ICA
D4a -- Verified Root Cause (R: PRE):
Describe the result of the root cause analysis --> AGGREGATE RESULT OF ALL ACTION ITEMS HERE
D4b -- Verified Escape Point (R: PRE):
Describe the outcome of the escape point analysis
Logged Data (DTC Readout/CAN Log/PAR File)(R: Originator):
Please add Log Files and Par files captured during the testing and add it as an attachment to the open point. Outline briefly the file added and the content that it describes
D7 -- Lessons Learned (R: PRE):
Describe (where appropriate) particular contributions from individuals or teams. ToDo - Verification to be executed on BA00++ |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please tailor and Link the Feature:
SF 7.6 Efficency support
Ensure traceability and consistency.
Customer Featurename:
BRS_StartStopp_Schnittstelle
LAH reference:
for customer requirements, see information from Power BI:
https://app.powerbi.com/groups/me/reports/78f76cb6-334d-4858-9201-a43499256e40/ReportSection385ddd113edfa5f20421?ctid=eb70b763-b6d7-4486-8555-8831709a784e&openReportSource=ReportInvitation
SyRs refernce from DOORS:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705 [04.05.2022],A.Kratzsch:
CR rejected. Linking will be done directly with Tailor and Linking CR:5565861
Status 11.11.2021:
97 customer req.
Effort = #customer Req. * 15min
[09.11.2021],A.Kratzsch:
61 customer Req.
Effort = #custReq * 15min
Status 08.07.2021:
179 customer Req.
Effort = #custReq * 15min | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please tailor and Link the Feature:
SF 7.6 Efficency support
Ensure traceability and consistency.
Customer Featurename:
BRS_StartStopp_Schnittstelle
LAH reference:
for customer requirements, see information from Power BI:
https://app.powerbi.com/groups/me/reports/78f76cb6-334d-4858-9201-a43499256e40/ReportSection385ddd113edfa5f20421?ctid=eb70b763-b6d7-4486-8555-8831709a784e&openReportSource=ReportInvitation
SyRs refernce from DOORS:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705 [04.05.2022],A.Kratzsch:
CR rejected. Linking will be done directly with Tailor and Linking CR:5565861
Status 11.11.2021:
97 customer req.
Effort = #customer Req. * 15min
[09.11.2021],A.Kratzsch:
61 customer Req.
Effort = #custReq * 15min
Status 08.07.2021:
179 customer Req.
Effort = #custReq * 15min |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please create SysRS and SysAD for following System Feature:
SF 7.6 Efficency support Holger Schmidt - PSM - (08.09.2021):
--------------------------------------------------------------------------------
Closed after Review. All linked Work Items / Tasks completed according to predefined Definition of Done.
Work Product archives, revisions and review evidences are documented in the Configuration Item List (Revision 1.2, see member link)
PSM (HSc) (19.07.2021):
--------------------------------------------------------------------------------
Brief analysis summary: Perform Re-Qualification
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): H. Schmidt
Proposal of next steps (incl. effort/h and verification): Generate Tasks for SyRS, FSC, SyAM-Functional, SyAM-Physical, SyDesign, TSC, FTA
-------------------------------------------------------------------------------- | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please create SysRS and SysAD for following System Feature:
SF 7.6 Efficency support Holger Schmidt - PSM - (08.09.2021):
--------------------------------------------------------------------------------
Closed after Review. All linked Work Items / Tasks completed according to predefined Definition of Done.
Work Product archives, revisions and review evidences are documented in the Configuration Item List (Revision 1.2, see member link)
PSM (HSc) (19.07.2021):
--------------------------------------------------------------------------------
Brief analysis summary: Perform Re-Qualification
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Risk (low/medium/high): low
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): H. Schmidt
Proposal of next steps (incl. effort/h and verification): Generate Tasks for SyRS, FSC, SyAM-Functional, SyAM-Physical, SyDesign, TSC, FTA
-------------------------------------------------------------------------------- |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.4 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SysAD reference:
/DOORS-9_Koblenz/03 Customer Projects/VW/P_VW_MQB_48W/30 System/ESC/04 System Architecture/SyDesign
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001129a0
SysAD Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. The SYS.4 interfaces from the System Feature in this Change Request have been covered in the SYS.4 CR from the Work Items tab.
See PTC ID 6197642, url:integrity://skobde-mks-im.kobde.trw.com:7001/im/viewissue?selection=6197642
For Can_RX Interface: Test was executed. The following incidents have been detected:
OP: 6304805 - [VW_MQB48W_ESC][500-006][CAT3][TEC][CanRx Interface] Update test specification for GearPosition interface
OP: 5900706 - [VW_MQB48W_ESC][404-009][CAT3][ADTY2][TEC][CanRx Interface] The RTE signals Rte_Write_S_EngineStartStop_EngineStartStopState and Rte_Write_S_EngineStartStop_EngineStartStopCoded are not available in a2L
See TMP ID: 67480
For Can_TX Interface: Test was executed. The following incidents have been detected:
OP: 5933169[VW_MQB48W_ESC][404-010][CAT3][TEC][CanTx Interface] The CAN output for interfaces are not reacting as expected.
See TMP ID: 67889
For ESC-EPB Interface: Test was executed. No incidents have been detected.
See TMP ID: 67422
For Ignition Status Hardwired Interfrace: Test was executed. No incidents have been detected.
See TMP ID: 67483
For Wheel Speed Interface: Test was executed. No incidents have been detected.
See TMP ID: 68176
For Circuits command and actuation Interface: Test was executed. No incidents have been detected.
See TMP ID: 67486
For Actuation Flow Interface: Test was executed. No incidents have been detected.
See TMP ID: 67481 | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.4 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SysAD reference:
/DOORS-9_Koblenz/03 Customer Projects/VW/P_VW_MQB_48W/30 System/ESC/04 System Architecture/SyDesign
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-001129a0
SysAD Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. The SYS.4 interfaces from the System Feature in this Change Request have been covered in the SYS.4 CR from the Work Items tab.
See PTC ID 6197642, url:integrity://skobde-mks-im.kobde.trw.com:7001/im/viewissue?selection=6197642
For Can_RX Interface: Test was executed. The following incidents have been detected:
OP: 6304805 - [VW_MQB48W_ESC][500-006][CAT3][TEC][CanRx Interface] Update test specification for GearPosition interface
OP: 5900706 - [VW_MQB48W_ESC][404-009][CAT3][ADTY2][TEC][CanRx Interface] The RTE signals Rte_Write_S_EngineStartStop_EngineStartStopState and Rte_Write_S_EngineStartStop_EngineStartStopCoded are not available in a2L
See TMP ID: 67480
For Can_TX Interface: Test was executed. The following incidents have been detected:
OP: 5933169[VW_MQB48W_ESC][404-010][CAT3][TEC][CanTx Interface] The CAN output for interfaces are not reacting as expected.
See TMP ID: 67889
For ESC-EPB Interface: Test was executed. No incidents have been detected.
See TMP ID: 67422
For Ignition Status Hardwired Interfrace: Test was executed. No incidents have been detected.
See TMP ID: 67483
For Wheel Speed Interface: Test was executed. No incidents have been detected.
See TMP ID: 68176
For Circuits command and actuation Interface: Test was executed. No incidents have been detected.
See TMP ID: 67486
For Actuation Flow Interface: Test was executed. No incidents have been detected.
See TMP ID: 67481 |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672' CRs for ADTY and ADBY required. | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672' CRs for ADTY and ADBY required. |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Filter for your test department.
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. This feature will be covered in a later release, after the tailoring activities are completed: CR 6321970 | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Filter for your test department.
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. This feature will be covered in a later release, after the tailoring activities are completed: CR 6321970 |
|
[DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Filter for your test department.
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. Start Stopp did not work in the test vehicles. Spot check was done in X0404 CAT3 release already. No requirements mapped to CASE for this feature. | [DCRP 07.07.06][ESC] Linking: SF 7.6 Efficiency support Please initiate SYS.5 test activity for Feature:
SF 7.6 Efficency support
Customer Featurename:
BRS_StartStopp_Schnittstelle
SyRs reference:
http://skobde-doors9wa.ad.trw.com:8080/dwa/rm/urn:rational:e9aba799-bc96-11e5-b6b9-419012b199da:1-479f06bc41562230-M-00112705
SyRs Filter criteria:
'011_Object State' = ('Approved' OR 'Ready for Approval') AND '015_CM Reference' contains '5525668' OR '5559141' OR '5565672'
Filter for your test department.
Perform Veto Phase.
Create test design and test specification for requirements resulting from above filter.
Create test scripts for resulting test specifications.
Assign resulting test cases to release categories (TSM attribute "065_CATLevel").
If test specification and/or script is already existing, check if test case is still matching to the requirement. If not, adapt test specification and script. Start Stopp did not work in the test vehicles. Spot check was done in X0404 CAT3 release already. No requirements mapped to CASE for this feature. |
|
PRTS 2149023 - EBCM , Flash/KP - EOLT - Flash - EBCM MAC Authentication Failures with Random Keys Please plan thic change implemented for 08/17/2021 release.
*. 0xE2 : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11
*. 0x26C: Update EBCM SSC MSG_MAC_STATUS Calibration value form 0x35 to 0x00. (Applicable to 31XX.2 and C1XX.2)
*. 0x2F : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11
*. 0x64 : No change needed.
*. 0x51B : No change needed.
My comments are in blue:
From: Vihar Vaidya <vihar.vaidya@gm.com>
Sent: Tuesday, August 3, 2021 11:41 AM
To: John Gubesch <john.gubesch@gm.com>; Michael Roberts <michael.c.roberts@gm.com>
Cc: George Elias <george.elias@gm.com>; Park Paul LVN ADWN13 <paul.park@zf.com>; Jonathan Kolenda <jonathan.kolenda@gm.com>; Kirk Amato <kirk.amato@gm.com>; Rollinger James LVN ADWN13 <james.rollinger@zf.com>; Hribar Jeffrey LVN ADBN53 <jeff.hribar@zf.com>; Svirbly Jennifer LVN ADBN51 <jenny.baibak@zf.com>; Bell Lucas LVN ADWN111 <lucas.bell@zf.com>; Nagabhushan Kote LVN ADWN34 <nagabhushan.kc@zf.com>
Subject: RE: 31XX EBCM MAC Authentication Failures
Hello John/Mike,
Yes, I believe these are all the EBCM MAC issues identified from the 31XX 159 testing.
Also, please find my comments in orange.
0xE2 - Mapped to key slot 10 which, per the MACT, aligns with when the ECP_E is the sender. Key Slot should be 11 for ECM. – Will check with ECM team. If this is confirmed with ECM team, EBCM will need to change to Key Slot 11. è Yes
0x26C - Mapped to key slot 7 which is correct. MAC authentication likely needs to be enabled by EBCM if the EPB Secondary Axle Apply feature is enabled for a given program. – Is this message N/A for 31XX program? This message is applicable for 31xx-2. @Nag did you confirm that this frame is being unpacked and that ZF System Safety agrees that MAC is required? I assume that’s the case but just want to confirm. è Yes (this message will be turned ON for 31XX.2 and C1XX.2. (Note:- OFF for BT1XX and BV1XX))
0x64 - Mapped to key slot 11 which is correct. MAC authentication is disabled correctly since, per the SSM_DTC map, no signals within the frame require a Failed Safety or Failed Security Fault Active.
– If MAC is disabled correctly then we can ignore this message failure What is the mechanism to disable MAC “correctly”? How did ZF disable MAC? Just want to confirm that we are all in agreement that this is done the way it needs to be done. è It’s part of Vector Tool configuration. GmSum,è MAC CAL Status value set to 0x35 for this frame to disable the MAC verification.
0x2F - Mapped to key slot 10 which, per the MACT, aligns with when the ECP_E is the sender. Key Slot should be 11 for ECM. - Will check with ECM team. If this is confirmed with ECM team, EBCM will need to change to Key Slot 11. è Yes
0x51B - Mapped to key slot 14 which is correct. MAC authentication should only be enabled for variants where E-Locker is enabled in the software. - Is this message N/A for 31XX program? It is applicable for vehicle variants that have the E-Locker feature. è Yes and no change need.
Most of the other modules on CAN2 are failing to process the MAC for ID $369 which is transmitted by EBCM. Any insight on why this is happening? Per Nag’s comment, EBCM has this mapped to Key Slot 2 per the MACT. Need to confirm which key slot the receiving modules are using.
Thanks and Regards,
Vihar Vaidya Vidya Sgar D [11-Aug-2021] :
-----------------------------------------------------------------------------------------------------------------------------------------
Aim of CR : Update Message ==> Key Slot mapping to fix MAC failures reported by GM
-----------------------------------------------------------------------------------------------------------------------------------------
Input to Start : BSW_BswAutocore_Vector_GM_31XX_1.76 check-point is used
-----------------------------------------------------------------------------------------------------------------------------------------
Anlaysis Comments:
-----------------------------------------------------------------------------------------------------------------------------------------
SwcSumGm Module:
As per CR's Description,
1. 0xE2 (SrlDat20_Prtctd_MSG) : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11 and update ECU name: ECM
2. 0x26C (XferCaseGenInfo_Prtctd_MSG) : Update EBCM SSC MSG_MAC_STATUS Calibration value from 0x35 to 0x00
3. 0x2F (SrlDat19_Prtctd_MSG) : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0x2F from SSC_Key_Slot_10 to SSC_Key_Slot_11 and update ECU name : ECM
--------------------------------------------------------------------------------------------------------------------------------------------
Risk(low/medium/high/Critical):Critical
--------------------------------------------------------------------------------------------------------------------------------------------
Proposal of next steps: Create a Task
--------------------------------------------------------------------------------------------------------------------------------------------
Task :31xx.2: BswAutocore: 0xE2 & 0x2F messages move from SSC_Key_Slot_10 to SCC_Key_Slot_11 and Update 0x26C message's parameter 'SSC_MSG_MAC_STATUS_CalibrationDefault' value from 0x35 to 0x00
--------------------------------------------------------------------------------------------------------------------------------------------
Description:
- Move 0xE2 (SrlDat20_Prtctd_MSG) message from SSC_Key_Slot_10 to SCC_Key_Slot_11
- Move 0x2F (SrlDat19_Prtctd_MSG) message from SSC_Key_Slot_10 to SCC_Key_Slot_11
- Update 0x26C (XferCaseGenInfo_Prtctd_MSG) message's parameter 'SSC_MSG_MAC_STATUS_CalibrationDefault' value from 0x35 to 0x00.
Work Products :
------------------------
- SwcSumGM
Test Criteria:
------------------------
- Flash the SW
- Observe the SW Execution Successful by verifying the Os Counters.
- Perform the shutdown / sleep of the ECU
- Verify the HSM Init state should be 1
- Verify the CAN communication on CANoe tool.
Acceptance criteria:
------------------------------
- Updated BswAutocore modules should not have any generation errors.
- No other change apart from SwcSumGm shall be configured. Unchanged modules should remain same with base work package.
- Generated Files must compiled and should not cause any errors.
- Changes must be tested and a Test Report should be attached to the Task.
- Check point of BswAutocore_Vector must be provided.
-------------------------------------------------------------------------------------------------------------------------------------------------
Owner: Vidya Sagar D
Reviewer: Nagabhushan K
Estimated Design effort/h: 0h
Esitimated implementation effort/h:7h
Estimated unit testing effort/h: 1h
-------------------------------------------------------------
Total effort/h: 8h
------------------------------------------------------------- | PRTS 2149023 - EBCM , Flash/KP - EOLT - Flash - EBCM MAC Authentication Failures with Random Keys Please plan thic change implemented for 08/17/2021 release.
*. 0xE2 : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11
*. 0x26C: Update EBCM SSC MSG_MAC_STATUS Calibration value form 0x35 to 0x00. (Applicable to 31XX.2 and C1XX.2)
*. 0x2F : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11
*. 0x64 : No change needed.
*. 0x51B : No change needed.
My comments are in blue:
From: Vihar Vaidya <vihar.vaidya@gm.com>
Sent: Tuesday, August 3, 2021 11:41 AM
To: John Gubesch <john.gubesch@gm.com>; Michael Roberts <michael.c.roberts@gm.com>
Cc: George Elias <george.elias@gm.com>; Park Paul LVN ADWN13 <paul.park@zf.com>; Jonathan Kolenda <jonathan.kolenda@gm.com>; Kirk Amato <kirk.amato@gm.com>; Rollinger James LVN ADWN13 <james.rollinger@zf.com>; Hribar Jeffrey LVN ADBN53 <jeff.hribar@zf.com>; Svirbly Jennifer LVN ADBN51 <jenny.baibak@zf.com>; Bell Lucas LVN ADWN111 <lucas.bell@zf.com>; Nagabhushan Kote LVN ADWN34 <nagabhushan.kc@zf.com>
Subject: RE: 31XX EBCM MAC Authentication Failures
Hello John/Mike,
Yes, I believe these are all the EBCM MAC issues identified from the 31XX 159 testing.
Also, please find my comments in orange.
0xE2 - Mapped to key slot 10 which, per the MACT, aligns with when the ECP_E is the sender. Key Slot should be 11 for ECM. – Will check with ECM team. If this is confirmed with ECM team, EBCM will need to change to Key Slot 11. è Yes
0x26C - Mapped to key slot 7 which is correct. MAC authentication likely needs to be enabled by EBCM if the EPB Secondary Axle Apply feature is enabled for a given program. – Is this message N/A for 31XX program? This message is applicable for 31xx-2. @Nag did you confirm that this frame is being unpacked and that ZF System Safety agrees that MAC is required? I assume that’s the case but just want to confirm. è Yes (this message will be turned ON for 31XX.2 and C1XX.2. (Note:- OFF for BT1XX and BV1XX))
0x64 - Mapped to key slot 11 which is correct. MAC authentication is disabled correctly since, per the SSM_DTC map, no signals within the frame require a Failed Safety or Failed Security Fault Active.
– If MAC is disabled correctly then we can ignore this message failure What is the mechanism to disable MAC “correctly”? How did ZF disable MAC? Just want to confirm that we are all in agreement that this is done the way it needs to be done. è It’s part of Vector Tool configuration. GmSum,è MAC CAL Status value set to 0x35 for this frame to disable the MAC verification.
0x2F - Mapped to key slot 10 which, per the MACT, aligns with when the ECP_E is the sender. Key Slot should be 11 for ECM. - Will check with ECM team. If this is confirmed with ECM team, EBCM will need to change to Key Slot 11. è Yes
0x51B - Mapped to key slot 14 which is correct. MAC authentication should only be enabled for variants where E-Locker is enabled in the software. - Is this message N/A for 31XX program? It is applicable for vehicle variants that have the E-Locker feature. è Yes and no change need.
Most of the other modules on CAN2 are failing to process the MAC for ID $369 which is transmitted by EBCM. Any insight on why this is happening? Per Nag’s comment, EBCM has this mapped to Key Slot 2 per the MACT. Need to confirm which key slot the receiving modules are using.
Thanks and Regards,
Vihar Vaidya Vidya Sgar D [11-Aug-2021] :
-----------------------------------------------------------------------------------------------------------------------------------------
Aim of CR : Update Message ==> Key Slot mapping to fix MAC failures reported by GM
-----------------------------------------------------------------------------------------------------------------------------------------
Input to Start : BSW_BswAutocore_Vector_GM_31XX_1.76 check-point is used
-----------------------------------------------------------------------------------------------------------------------------------------
Anlaysis Comments:
-----------------------------------------------------------------------------------------------------------------------------------------
SwcSumGm Module:
As per CR's Description,
1. 0xE2 (SrlDat20_Prtctd_MSG) : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0xE2 from SSC_Key_Slot_10 to SSC_Key_Slot_11 and update ECU name: ECM
2. 0x26C (XferCaseGenInfo_Prtctd_MSG) : Update EBCM SSC MSG_MAC_STATUS Calibration value from 0x35 to 0x00
3. 0x2F (SrlDat19_Prtctd_MSG) : Update EBCM “SUM_SSC_KeyMapping” configuration to move 0x2F from SSC_Key_Slot_10 to SSC_Key_Slot_11 and update ECU name : ECM
--------------------------------------------------------------------------------------------------------------------------------------------
Risk(low/medium/high/Critical):Critical
--------------------------------------------------------------------------------------------------------------------------------------------
Proposal of next steps: Create a Task
--------------------------------------------------------------------------------------------------------------------------------------------
Task :31xx.2: BswAutocore: 0xE2 & 0x2F messages move from SSC_Key_Slot_10 to SCC_Key_Slot_11 and Update 0x26C message's parameter 'SSC_MSG_MAC_STATUS_CalibrationDefault' value from 0x35 to 0x00
--------------------------------------------------------------------------------------------------------------------------------------------
Description:
- Move 0xE2 (SrlDat20_Prtctd_MSG) message from SSC_Key_Slot_10 to SCC_Key_Slot_11
- Move 0x2F (SrlDat19_Prtctd_MSG) message from SSC_Key_Slot_10 to SCC_Key_Slot_11
- Update 0x26C (XferCaseGenInfo_Prtctd_MSG) message's parameter 'SSC_MSG_MAC_STATUS_CalibrationDefault' value from 0x35 to 0x00.
Work Products :
------------------------
- SwcSumGM
Test Criteria:
------------------------
- Flash the SW
- Observe the SW Execution Successful by verifying the Os Counters.
- Perform the shutdown / sleep of the ECU
- Verify the HSM Init state should be 1
- Verify the CAN communication on CANoe tool.
Acceptance criteria:
------------------------------
- Updated BswAutocore modules should not have any generation errors.
- No other change apart from SwcSumGm shall be configured. Unchanged modules should remain same with base work package.
- Generated Files must compiled and should not cause any errors.
- Changes must be tested and a Test Report should be attached to the Task.
- Check point of BswAutocore_Vector must be provided.
-------------------------------------------------------------------------------------------------------------------------------------------------
Owner: Vidya Sagar D
Reviewer: Nagabhushan K
Estimated Design effort/h: 0h
Esitimated implementation effort/h:7h
Estimated unit testing effort/h: 1h
-------------------------------------------------------------
Total effort/h: 8h
------------------------------------------------------------- |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. [Abhishek Ojha:29-07-2021]:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The existing OPEL K0 gearboxes needs to be remapped standard gearbox types used in performance SW.
The remapping shallbe done as below:
Values Standard Gbx Type Opel-K0 Gbx Type
0 GEARBOX_CVT -
1 GEARBOX_SELESPEED -
2 GEARBOX_MANUAL ML6C_GEARBOX
3 GEARBOX_AUTOMATIC EDCT_GEARBOX
EK0_GEARBOX
AMN8_GEARBOX
If Variant coding is not valid, the gearbox type provided shall be Automatic gearbox.
Refer the attached mail for reference.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Required task created
------------------------------------------------------ | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. [Abhishek Ojha:29-07-2021]:
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
The existing OPEL K0 gearboxes needs to be remapped standard gearbox types used in performance SW.
The remapping shallbe done as below:
Values Standard Gbx Type Opel-K0 Gbx Type
0 GEARBOX_CVT -
1 GEARBOX_SELESPEED -
2 GEARBOX_MANUAL ML6C_GEARBOX
3 GEARBOX_AUTOMATIC EDCT_GEARBOX
EK0_GEARBOX
AMN8_GEARBOX
If Variant coding is not valid, the gearbox type provided shall be Automatic gearbox.
Refer the attached mail for reference.
--------------------------------------------------------------------------------
Risk (low/medium/high): medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification): Required task created
------------------------------------------------------ |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. [Martin Bienert (bienertm), 05.08.2021, 08:22:20]
In an uphill situation the pressure is released in a torque balanced manner. Therefore the axle torque is necessary as input. In SSM the wrong interface is used for the axle torque. It shall be used GetAxleTorque(), but currently GetCpleRoueGmpReal() is used as it is defined as input in the ACC specification book.
The interface needs to be changed to GetAxleTorque() and it needs to be clarified in which situations GetCpleRoueGmpReal() shall be used
Furthermore the input validation INPUT_VALID_ETAT_POINT_MORT shall be used for the neutral gear.
Please create a task for implementation.
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Martin Bienert
Verifier:
Estimated effort: 1 h
------------------------------- | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. [Martin Bienert (bienertm), 05.08.2021, 08:22:20]
In an uphill situation the pressure is released in a torque balanced manner. Therefore the axle torque is necessary as input. In SSM the wrong interface is used for the axle torque. It shall be used GetAxleTorque(), but currently GetCpleRoueGmpReal() is used as it is defined as input in the ACC specification book.
The interface needs to be changed to GetAxleTorque() and it needs to be clarified in which situations GetCpleRoueGmpReal() shall be used
Furthermore the input validation INPUT_VALID_ETAT_POINT_MORT shall be used for the neutral gear.
Please create a task for implementation.
TASK 1
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Martin Bienert
Verifier:
Estimated effort: 1 h
------------------------------- |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. Aimen Rouissi (05.08.21 - 15:51):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Baselines of the relevant DOORS modules need to be created, exported, and archived.
Afterwards, source code needs to be generated from the DMT baseline.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rouissia
Proposal of next steps (incl. effort/h and verification): Please see created tasks related to this CR.
-------------------------------------------------------------------------------- | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. Aimen Rouissi (05.08.21 - 15:51):
--------------------------------------------------------------------------------
Brief analysis summary:
--------------------------------------------------------------------------------
Baselines of the relevant DOORS modules need to be created, exported, and archived.
Afterwards, source code needs to be generated from the DMT baseline.
--------------------------------------------------------------------------------
Risk (low/medium/high): high
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses): Rouissia
Proposal of next steps (incl. effort/h and verification): Please see created tasks related to this CR.
-------------------------------------------------------------------------------- |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. Rajesh(04-Aug-2021):
----------------------------
Enable/disable the IV "INPUT_VALID_REVERSE_SWITCH" for the signal "MARCHE_AR_BVM" when the Frame BSI_412 received(valid)/not received
Update the RxSignalHandler component (modules RxSignalHandlerBsi412Ocan00SingleSignalGroup_Cfg.c ,RxSignalHandler_Cfg.c)accordingly
---------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):TASK
--------------------------------------------------------------------------------
TASK1 : COMMS
------------------------------------------------------
Title:[OPEL K0 COMMS] Enable/Disable the IV for Reverse Gear Info
Description: Please refer the analysis
Owner: Suraj/Bharath
Reviewer: Rajesh Bommana
Estimated design effort/h:
Estimated implementation effort/h:3
Estimated unit testing effort/h:5
-----------------------------------------------------------------
Total effort/h: 8 [Optional] Planned completion date: 9-Aug-2020
----------------------------------------------------------------- | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. Rajesh(04-Aug-2021):
----------------------------
Enable/disable the IV "INPUT_VALID_REVERSE_SWITCH" for the signal "MARCHE_AR_BVM" when the Frame BSI_412 received(valid)/not received
Update the RxSignalHandler component (modules RxSignalHandlerBsi412Ocan00SingleSignalGroup_Cfg.c ,RxSignalHandler_Cfg.c)accordingly
---------------------------------------------------------------------------------
Risk (low/medium/high):medium
--------------------------------------------------------------------------------
Analysis completed by (applicable only for distributed analyses):
Proposal of next steps (incl. effort/h and verification):TASK
--------------------------------------------------------------------------------
TASK1 : COMMS
------------------------------------------------------
Title:[OPEL K0 COMMS] Enable/Disable the IV for Reverse Gear Info
Description: Please refer the analysis
Owner: Suraj/Bharath
Reviewer: Rajesh Bommana
Estimated design effort/h:
Estimated implementation effort/h:3
Estimated unit testing effort/h:5
-----------------------------------------------------------------
Total effort/h: 8 [Optional] Planned completion date: 9-Aug-2020
----------------------------------------------------------------- |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. 09.08.2021 BoianD: the task has been performed according with expectations
05.08.2021 BoianD: Switch the INPUT_VALID_REVERSE_SWITCH for MSG_BSI_412_TIMEOUT. | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [27.07.2021 - 10:16]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold, HillAssist is active
Actions:
1. Driver is pressing the AcceleratorPedal and wish to drive off
--------------------------------------------------------------------------------
Expected behaviour:
HillAssist should dump pressure if engine torque is high enough to drive away.
--------------------------------------------------------------------------------
Actual behaviour:
HillAssist is not dumping pressure, althought engine torque is available to drive away
.
Please check trace for more details
--------------------------------------------------------------------------------
Additional Informations:
timeout is working as expected, after approx 2 secons.
HillAssist is also active downwards and in flat surface, which is nok. 09.08.2021 BoianD: the task has been performed according with expectations
05.08.2021 BoianD: Switch the INPUT_VALID_REVERSE_SWITCH for MSG_BSI_412_TIMEOUT. |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver Follow up CR of CR 5582554
As the vehicle type of the Opel K0 is a van, the payload can reach high values over 1000 kg which results in a high hold pressure, as the full payload is used for the vehicle weight calculation in SSM.
With this fix an offset for the vehicle weight shall be used instead of the payload. [Martin Bienert (bienertm), 08.10.2021, 07:19:51]
A static offset with 307 kg will be used instead of the delivered payload from Chassinfo | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver Follow up CR of CR 5582554
As the vehicle type of the Opel K0 is a van, the payload can reach high values over 1000 kg which results in a high hold pressure, as the full payload is used for the vehicle weight calculation in SSM.
With this fix an offset for the vehicle weight shall be used instead of the payload. [Martin Bienert (bienertm), 08.10.2021, 07:19:51]
A static offset with 307 kg will be used instead of the delivered payload from Chassinfo |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver Implement clutch interface to allow a comfortable drive off with from active Hill Assist [Martin Bienert (bienertm), 02.03.2022, 14:18:57]
Implement the clutch interface to allow a comfortable drive off without rolling backwards.
1.) Enable CLUTCH_TRAVEL_INTERFACE switch
2.) Use clutch engaged information for setting of DriveOffRequestDriver and HaPressureHoldTimer | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver Implement clutch interface to allow a comfortable drive off with from active Hill Assist [Martin Bienert (bienertm), 02.03.2022, 14:18:57]
Implement the clutch interface to allow a comfortable drive off without rolling backwards.
1.) Enable CLUTCH_TRAVEL_INTERFACE switch
2.) Use clutch engaged information for setting of DriveOffRequestDriver and HaPressureHoldTimer |
|
[Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [15.03.2022 - 10:34]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold via brakepressure on a gradient uphill
--------------------------------------------------------------------------------
Actions:
Stay on gradient with HA active for at least 3 sec
--------------------------------------------------------------------------------
Expected behaviour:
HA will dump pressure after timeout of 3 sec
--------------------------------------------------------------------------------
Actual behaviour:
Pressure is not dumped after 3 sec
-------------------------------------------------------------------------------- [Martin Bienert (bienertm), 17.03.2022, 14:31:50]
The clutch position is invalid during the test. Because of that SSM sets the clutch position to 0. This leads to the problem, that the Hill Assist not starts to increment the pressure hold timer, because "it seems" that the driver wants to launch and the pressure needs to be hold till drive off is finished.
It needs to be said, that this behavior only happens in case of clutch position invalid!
Solution:
The clutch position must not be set to 0 and the Hill Assist must not hold the vehicle longer than 1.5 s in case of invalid CAN signal.
Please create a task for implementation.
TASK
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Martin Bienert
Verifier:
Estimated effort: 4 h
------------------------------- | [Opel K0][300_177][CAT3][ADBY4.3] Vehicle Test -HillAssist is isolating pressure in case of HA maneuver ADBY4.3 - MarxT [15.03.2022 - 10:34]:
--------------------------------------------------------------------------------
Preconditions:
Vehicle is hold via brakepressure on a gradient uphill
--------------------------------------------------------------------------------
Actions:
Stay on gradient with HA active for at least 3 sec
--------------------------------------------------------------------------------
Expected behaviour:
HA will dump pressure after timeout of 3 sec
--------------------------------------------------------------------------------
Actual behaviour:
Pressure is not dumped after 3 sec
-------------------------------------------------------------------------------- [Martin Bienert (bienertm), 17.03.2022, 14:31:50]
The clutch position is invalid during the test. Because of that SSM sets the clutch position to 0. This leads to the problem, that the Hill Assist not starts to increment the pressure hold timer, because "it seems" that the driver wants to launch and the pressure needs to be hold till drive off is finished.
It needs to be said, that this behavior only happens in case of clutch position invalid!
Solution:
The clutch position must not be set to 0 and the Hill Assist must not hold the vehicle longer than 1.5 s in case of invalid CAN signal.
Please create a task for implementation.
TASK
-------------------------------
Title/Header:
Description: see investigation
Assigned to: Martin Bienert
Verifier:
Estimated effort: 4 h
------------------------------- |
|
Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | ANGLE_SENSOR_A1_FAULT and ANGLE_SENSOR_A2_FAULT raise when NARROW XCHECK FAULTis raised, which is not expected Please update test cases according to conclusion in the action linked to the OP. test case update done acc. to task 5949867
test case executed in task 5915305 | Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | ANGLE_SENSOR_A1_FAULT and ANGLE_SENSOR_A2_FAULT raise when NARROW XCHECK FAULTis raised, which is not expected Please update test cases according to conclusion in the action linked to the OP. test case update done acc. to task 5949867
test case executed in task 5915305 |
|
Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM Test Case to be udpated according to action. Bugfix confirmation done in task 8432864. - issue no longer observed.
For more details see task 8432864
ALM_Open Point 5559453 can be closed | Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM Test Case to be udpated according to action. Bugfix confirmation done in task 8432864. - issue no longer observed.
For more details see task 8432864
ALM_Open Point 5559453 can be closed |
|
Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM See issue description in linked OP 5790327 One task for PFS team
2022-08-05 STOLARSK:
Please update FSM according to the proposed changes in ALM_Action 5662796
2022-08-22 STOLARSK:
Task is completed. CR can be closed. | Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM See issue description in linked OP 5790327 One task for PFS team
2022-08-05 STOLARSK:
Please update FSM according to the proposed changes in ALM_Action 5662796
2022-08-22 STOLARSK:
Task is completed. CR can be closed. |
|
Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM FSM has been updated accordingly. Please check the FSM and if necessary retest with FA with updated test case Bugfix confirmation done in task 8432864. - issue no longer observed.
For more details see task 8432864
ALM_Open Point 5559453 can be closed | Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM FSM has been updated accordingly. Please check the FSM and if necessary retest with FA with updated test case Bugfix confirmation done in task 8432864. - issue no longer observed.
For more details see task 8432864
ALM_Open Point 5559453 can be closed |
|
Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM Summary description of problem:
Sample: Based on FSM baseline 290.1 Angle faults which are applicable for FCA Ducato project:
However DEMs which raised after inserting Narrow/Wide fault:
DEM 499
DEM 500.
Based on ASY-FI043840-S2-V00DA00_0250_FaultList.xlsx:
After short investigation it was noticed, that correct faults are in fault list as well:
Inconsistency between FSM and fault list was observed.
.mdf files attached.
Operating Environment
DUT: Real ECU + Simulated Motor + Real TAS
PartNo: ECU: Y19A012E71520319GA0164; Motor: Y19A012E71520319GA0164; Sensor: 1008234819-1; Gbx: N/A; Upper Column: N/A
Execution environment: EPP HiL
ControlDesk Version: 21-Dec-2020
Canalyzer simulation Version: N/A
Other tools: N/A
Test Case ID:
FCA_B250_SYS4_TAS_FIT_102
Applicable Requirements ID:
GenC_FSM_1993
Preconditions:
Normal Operation, fault free system, 13.5V,
driver torque = 2nm;
InputExpected ResultObserved Behavior
1. Set simultanously A1 channel offset to -2.55 deg(half of -5.1 deg) and A2 channel offset to 2.55 deg.
2. Check {Motor Torque}
3. Check {MIL status}
4. Check {DTC}
5. Check {Fault code}
6. Check {System State}
7. Check CapabilityLimit
1. ---;
2. Motor_SensorTorque is smooth with no spikes, no ripples and no abnormal behaviour, value doesn't change;
3. ElectricSteeringFailSts= Fail Not Present
4. DTC 0x620564 raised
5. ANGLE_SENSOR_A1A2_NARROW_XCHECK_FAULTraised within 129ms and set to active;
6. ASSIST_NORMAL_OPERATION
7. CapabilityLimit= 100%
1. ---
2. Motor_TorqueSensor did not change
3. MIL OFF
4. DTC 620564
5. Faults:
DEM 274: ANGLE_SENSOR_A1_FAULT : 47 163ms
DEM 275: ANGLE_SENSOR_A2_FAULT : 47 163ms
DEM 499: ANGLE_SENSOR_NARROW_XCHECK_FAULT : 35 143ms
6. ASSIST_NORMAL_OPERATION
7. Capability 100% One task for PFS team
2022-08-05 STOLARSK:
Task is completed. CR can be closed. | Fiat_Ducato_BD | SYS.4 + SYS.5 | TAS FIT DA00 | After inserting Angle WIDE/NARROW fault, System raises fault which is not assigned to Ducato project in FSM Summary description of problem:
Sample: Based on FSM baseline 290.1 Angle faults which are applicable for FCA Ducato project:
However DEMs which raised after inserting Narrow/Wide fault:
DEM 499
DEM 500.
Based on ASY-FI043840-S2-V00DA00_0250_FaultList.xlsx:
After short investigation it was noticed, that correct faults are in fault list as well:
Inconsistency between FSM and fault list was observed.
.mdf files attached.
Operating Environment
DUT: Real ECU + Simulated Motor + Real TAS
PartNo: ECU: Y19A012E71520319GA0164; Motor: Y19A012E71520319GA0164; Sensor: 1008234819-1; Gbx: N/A; Upper Column: N/A
Execution environment: EPP HiL
ControlDesk Version: 21-Dec-2020
Canalyzer simulation Version: N/A
Other tools: N/A
Test Case ID:
FCA_B250_SYS4_TAS_FIT_102
Applicable Requirements ID:
GenC_FSM_1993
Preconditions:
Normal Operation, fault free system, 13.5V,
driver torque = 2nm;
InputExpected ResultObserved Behavior
1. Set simultanously A1 channel offset to -2.55 deg(half of -5.1 deg) and A2 channel offset to 2.55 deg.
2. Check {Motor Torque}
3. Check {MIL status}
4. Check {DTC}
5. Check {Fault code}
6. Check {System State}
7. Check CapabilityLimit
1. ---;
2. Motor_SensorTorque is smooth with no spikes, no ripples and no abnormal behaviour, value doesn't change;
3. ElectricSteeringFailSts= Fail Not Present
4. DTC 0x620564 raised
5. ANGLE_SENSOR_A1A2_NARROW_XCHECK_FAULTraised within 129ms and set to active;
6. ASSIST_NORMAL_OPERATION
7. CapabilityLimit= 100%
1. ---
2. Motor_TorqueSensor did not change
3. MIL OFF
4. DTC 620564
5. Faults:
DEM 274: ANGLE_SENSOR_A1_FAULT : 47 163ms
DEM 275: ANGLE_SENSOR_A2_FAULT : 47 163ms
DEM 499: ANGLE_SENSOR_NARROW_XCHECK_FAULT : 35 143ms
6. ASSIST_NORMAL_OPERATION
7. Capability 100% One task for PFS team
2022-08-05 STOLARSK:
Task is completed. CR can be closed. |
|
GWM_B30_DP | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
?
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
For procedures ZF Level 2 Prcocess and 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
2. W150j and SWE2, shall follow
C_040_2_SSE_005_EN_SW Architectural Design Procedure
and
Chapter: 3.1. Evaluate Alternative SW Architecture Solutions
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
?
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM? approved | GWM_B30_DP | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
?
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
For procedures ZF Level 2 Prcocess and 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
2. W150j and SWE2, shall follow
C_040_2_SSE_005_EN_SW Architectural Design Procedure
and
Chapter: 3.1. Evaluate Alternative SW Architecture Solutions
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
?
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM? approved |
|
GWM_B30_DP | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
?
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
For procedures ZF Level 2 Prcocess and 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
2. W150j and SWE2, shall follow
C_040_2_SSE_005_EN_SW Architectural Design Procedure
and
Chapter: 3.1. Evaluate Alternative SW Architecture Solutions
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
?
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM? APPROVED | GWM_B30_DP | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code Activities Description:
1. Perform Change Analysis Handling per SW Release and one Build and Clustered Input Changes (Aligned Cluster with System):
?
1.2 Perform Detail Impact Analysis
Based on initial imapct analysis result in SW engineering traceability matrix, the detail analysis can be performed, and create detail Imapct Analysis (IA) doc recoding this release allocated input changes the full impact from W130j-W220j (SWE1-SWE6, MAN3, Safety, Industralization).
For procedures ZF Level 2 Prcocess and 3 WI defined for IA:
1. W140j and SWE1, shall follow
C_066_3_SSE_036_EN Detailed Impact Analysis for SW Requirements Work Instruction
and
Chapter: 3. Impact Analysis on SWE.1 Change Request level
2. W150j and SWE2, shall follow
C_040_2_SSE_005_EN_SW Architectural Design Procedure
and
Chapter: 3.1. Evaluate Alternative SW Architecture Solutions
Input for this WP are:
?
1. SW Release Plan
2. System Requirement & Architecture (Compliance Analyzed)
3. ECU HW design spec (Compliance Analyzed)
4. Customer Requirement (Compliance Analyzed)
5. SW engineering traceability matrix
?
Output of this WP:
1. SW engineering traceability matrix (Update)
2. SW Project Schedule (Update)
3. Imapct Analysis Doc
Responsible: SWPM (Lead), SWRM, FunctionModule Developer, LSE, SWTM, SWTM, Tester
Reviewer/Approver: SWPM? APPROVED |
|
Fault Detecting Data - PRESS_SENS_1_COMM_FAULT/ PRESS_SENS_2_COMM_FAULT The missing fast message fault counts up on occasion on good parts causing FMM data to show that the fault is counting up. The reason is that the software expects data at 1 ms rate, and the sensor sends data at 0.99 ms rate. Also, the clocks of the micro and the sensor are synchronized, and the OS task for 1 ms can be jittery due to interrupts. All this can cause 2 frames to be received in 1 ms update and 0 frames in the next.
The goal of this CR is to eliminate the counting up of the fault. The 2 frames in 1 ms, 0 in the next is expected, and thus shouldn't count up the fault.
A possible solution is the only count up the fault if we miss two frames and more. Don't count up the fault when the counter is 1. Rejecting per 5010997.pdf attached we all agreed to not pursue this type of change at this time. | Fault Detecting Data - PRESS_SENS_1_COMM_FAULT/ PRESS_SENS_2_COMM_FAULT The missing fast message fault counts up on occasion on good parts causing FMM data to show that the fault is counting up. The reason is that the software expects data at 1 ms rate, and the sensor sends data at 0.99 ms rate. Also, the clocks of the micro and the sensor are synchronized, and the OS task for 1 ms can be jittery due to interrupts. All this can cause 2 frames to be received in 1 ms update and 0 frames in the next.
The goal of this CR is to eliminate the counting up of the fault. The 2 frames in 1 ms, 0 in the next is expected, and thus shouldn't count up the fault.
A possible solution is the only count up the fault if we miss two frames and more. Don't count up the fault when the counter is 1. Rejecting per 5010997.pdf attached we all agreed to not pursue this type of change at this time. |
|
Fault Detecting Data - MICRO_CLOCK_PLAUSIBILITY_FAILURE This OP will be closed out once the system has been updated to filter out counts as requested in the one pager. Design approach for filtering out count is not agreed on | Fault Detecting Data - MICRO_CLOCK_PLAUSIBILITY_FAILURE This OP will be closed out once the system has been updated to filter out counts as requested in the one pager. Design approach for filtering out count is not agreed on |