Datasets:

Soaponhub

/

hope

like 0

ID: 5532050

ID: 5532050, Summary: C1+ CV01 - Open phase faults during vehicle integration, State: ALM_Analysed, Project: /Steering/Projects/ZF/PR52697_Global_Support_to_Division_T_GenC1Plus, Company: ZF, Team: 3550602, Classification: Incident / Problem / Bug, Comments: , Description: 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):, Conclusion: 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.iCtrlrQuadAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap More details in the attached message., LogType: Fault Detection Log

Provide the details for the given ID

Summary: C1+ CV01 - Open phase faults during vehicle integration

ID: 5532050, Summary: C1+ CV01 - Open phase faults during vehicle integration, State: ALM_Analysed, Project: /Steering/Projects/ZF/PR52697_Global_Support_to_Division_T_GenC1Plus, Company: ZF, Team: 3550602, Classification: Incident / Problem / Bug, Comments: , Description: 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):, Conclusion: 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.iCtrlrQuadAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap More details in the attached message., LogType: Fault Detection Log

Provide the details for the given Summary

LogType: Fault Detection Log, Company: ZF, Summary: C1+ CV01 - Open phase faults during vehicle integration

ID: 5532050, Summary: C1+ CV01 - Open phase faults during vehicle integration, State: ALM_Analysed, Project: /Steering/Projects/ZF/PR52697_Global_Support_to_Division_T_GenC1Plus, Company: ZF, Team: 3550602, Classification: Incident / Problem / Bug, Comments: , Description: 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):, Conclusion: 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.iCtrlrQuadAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrQuadAxisPropGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisIntglGainMapMotorTune.EDCCoreMotorTune.EdcDetrCurCtrl.iCtrlrDrctAxisPropGainMap More details in the attached message., LogType: Fault Detection Log

Provide the details for the given input

ID: 5532549

ID: 5532549, Summary: [Opel K0][Requirement] - Drop and replace SSM_PB related modules, State: ALM_Realized, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544056, Classification: Requirements, Comments: , Description: 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 , Conclusion: Brief analysis summary:Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.TASKDrop 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 AkojuReviewer: Mehta Jay Estimated design effort/h: 1hrEstimated implementation effort/h: 3hrEstimated unit testing effort/h: 0, LogType: Requirement Log

Provide the details for the given ID

Summary: [Opel K0][Requirement] - Drop and replace SSM_PB related modules

ID: 5532549, Summary: [Opel K0][Requirement] - Drop and replace SSM_PB related modules, State: ALM_Realized, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544056, Classification: Requirements, Comments: , Description: 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 , Conclusion: Brief analysis summary:Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.TASKDrop 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 AkojuReviewer: Mehta Jay Estimated design effort/h: 1hrEstimated implementation effort/h: 3hrEstimated unit testing effort/h: 0, LogType: Requirement Log

Provide the details for the given Summary

LogType: Requirement Log, Company: PSA, Summary: [Opel K0][Requirement] - Drop and replace SSM_PB related modules

ID: 5532549, Summary: [Opel K0][Requirement] - Drop and replace SSM_PB related modules, State: ALM_Realized, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544056, Classification: Requirements, Comments: , Description: 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 , Conclusion: Brief analysis summary:Need to drop the sub components Ssm_Pbi and SsmPbWrp from Opel K0 - EPBi Folder and share it from BrkSW Pool.TASKDrop 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 AkojuReviewer: Mehta Jay Estimated design effort/h: 1hrEstimated implementation effort/h: 3hrEstimated unit testing effort/h: 0, LogType: Requirement Log

Provide the details for the given input

ID: 5532680

ID: 5532680, Summary: [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering, State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/ESC, Company: VW, Team: 3361822, Classification: Incident / Problem / Bug, Comments: , Description: Preconditions / Ausgangsituation: Vehicle: AERO / ID.Buzz054 / ID.Buzz089SW SCS: M521 /b521SW EBB: 657-002 / b651Maneuver name: HBAActions / Aktionen:1. HBA triggering2. xxx3. xxx4. xxx5. xxxExpected Behavior / erwartetes Sollverhalten:HBA should stay active / HBA should not become active without driver intentActual Behavior / Istverhalten:2021-07-01_AERO_009_248.MDF2021-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):xxxImpact / Einfluss:xxx, Conclusion: 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, LogType: Other

Provide the details for the given ID

Summary: [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering

ID: 5532680, Summary: [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering, State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/ESC, Company: VW, Team: 3361822, Classification: Incident / Problem / Bug, Comments: , Description: Preconditions / Ausgangsituation: Vehicle: AERO / ID.Buzz054 / ID.Buzz089SW SCS: M521 /b521SW EBB: 657-002 / b651Maneuver name: HBAActions / Aktionen:1. HBA triggering2. xxx3. xxx4. xxx5. xxxExpected Behavior / erwartetes Sollverhalten:HBA should stay active / HBA should not become active without driver intentActual Behavior / Istverhalten:2021-07-01_AERO_009_248.MDF2021-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):xxxImpact / Einfluss:xxx, Conclusion: 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, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: VW, Summary: [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering

ID: 5532680, Summary: [0521][CASE][VW_MEB41x_SCS]MCP oscillations cause HBA exit and HBA triggering, State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/ESC, Company: VW, Team: 3361822, Classification: Incident / Problem / Bug, Comments: , Description: Preconditions / Ausgangsituation: Vehicle: AERO / ID.Buzz054 / ID.Buzz089SW SCS: M521 /b521SW EBB: 657-002 / b651Maneuver name: HBAActions / Aktionen:1. HBA triggering2. xxx3. xxx4. xxx5. xxxExpected Behavior / erwartetes Sollverhalten:HBA should stay active / HBA should not become active without driver intentActual Behavior / Istverhalten:2021-07-01_AERO_009_248.MDF2021-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):xxxImpact / Einfluss:xxx, Conclusion: 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, LogType: Other

Provide the details for the given input

ID: 5532710

ID: 5532710, Summary: HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code , State: ALM_Closed, Project: /Steering/Projects/HKMC/SK/PR45616_MY2018_HKMC_SK_EPS_CD_Hroom_AP, Company: HKMC, Team: 1963171, Classification: Incident / Problem / Bug, Comments: , Description: 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 Requirements3.2. Manage Requirements and Traceability3.3. Software Requirements Style3.4. Handling of software requirement sources3.5. Handling of Signals and Parameters for software requirements3.6. Handling of Attributes for software requirementsAttributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes1.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 requirement3.2. Removing a SW release from a requirement3.3. Maintaining requirements assigned to multiple SW releases – functional change3.4. Maintaining requirements assigned to multiple SW releases – no functional change3.5. Maintaining requirements assigned to multiple SW releases – bug fix2. 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 review3.1.1. Prepare the review of software requirements3.1.2. Perform technical and formal review3.1.3. Organize Review by stakeholder3.1.4. Stakeholder Review3.1.5. Finalize SW Requirements review3.2. Organize an informal software requirements review4. Review invitationInput for this WP are:?1. SW Release Plan2. System Requirement & Architecture (Compliance Analyzed)3. ECU HW design spec (Compliance Analyzed)4. Customer Requirement (Compliance Analyzed)5. Impact Analysis6. SW engineering traceability matrix?Output of this WP:1. SW Requirement2. SW Requirement Baseline3. FSF Manual (Updates)Responsible: SW Feature Manager, SW FM DeveloperSupport: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ?, Conclusion: Change to Analysed, LogType: Other

Provide the details for the given ID

Summary: HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code

ID: 5532710, Summary: HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code , State: ALM_Closed, Project: /Steering/Projects/HKMC/SK/PR45616_MY2018_HKMC_SK_EPS_CD_Hroom_AP, Company: HKMC, Team: 1963171, Classification: Incident / Problem / Bug, Comments: , Description: 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 Requirements3.2. Manage Requirements and Traceability3.3. Software Requirements Style3.4. Handling of software requirement sources3.5. Handling of Signals and Parameters for software requirements3.6. Handling of Attributes for software requirementsAttributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes1.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 requirement3.2. Removing a SW release from a requirement3.3. Maintaining requirements assigned to multiple SW releases – functional change3.4. Maintaining requirements assigned to multiple SW releases – no functional change3.5. Maintaining requirements assigned to multiple SW releases – bug fix2. 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 review3.1.1. Prepare the review of software requirements3.1.2. Perform technical and formal review3.1.3. Organize Review by stakeholder3.1.4. Stakeholder Review3.1.5. Finalize SW Requirements review3.2. Organize an informal software requirements review4. Review invitationInput for this WP are:?1. SW Release Plan2. System Requirement & Architecture (Compliance Analyzed)3. ECU HW design spec (Compliance Analyzed)4. Customer Requirement (Compliance Analyzed)5. Impact Analysis6. SW engineering traceability matrix?Output of this WP:1. SW Requirement2. SW Requirement Baseline3. FSF Manual (Updates)Responsible: SW Feature Manager, SW FM DeveloperSupport: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ?, Conclusion: Change to Analysed, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: HKMC, Summary: HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code

ID: 5532710, Summary: HKMC_SK PE | FA00 | SWE5 | DTC&MIL Mapping Test - DTC&MIL mapping fails or inconsistencies between FSM and the code , State: ALM_Closed, Project: /Steering/Projects/HKMC/SK/PR45616_MY2018_HKMC_SK_EPS_CD_Hroom_AP, Company: HKMC, Team: 1963171, Classification: Incident / Problem / Bug, Comments: , Description: 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 Requirements3.2. Manage Requirements and Traceability3.3. Software Requirements Style3.4. Handling of software requirement sources3.5. Handling of Signals and Parameters for software requirements3.6. Handling of Attributes for software requirementsAttributes shall be set according to the work instruction C_066_3_SSE_026_EN_SW_Attributes1.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 requirement3.2. Removing a SW release from a requirement3.3. Maintaining requirements assigned to multiple SW releases – functional change3.4. Maintaining requirements assigned to multiple SW releases – no functional change3.5. Maintaining requirements assigned to multiple SW releases – bug fix2. 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 review3.1.1. Prepare the review of software requirements3.1.2. Perform technical and formal review3.1.3. Organize Review by stakeholder3.1.4. Stakeholder Review3.1.5. Finalize SW Requirements review3.2. Organize an informal software requirements review4. Review invitationInput for this WP are:?1. SW Release Plan2. System Requirement & Architecture (Compliance Analyzed)3. ECU HW design spec (Compliance Analyzed)4. Customer Requirement (Compliance Analyzed)5. Impact Analysis6. SW engineering traceability matrix?Output of this WP:1. SW Requirement2. SW Requirement Baseline3. FSF Manual (Updates)Responsible: SW Feature Manager, SW FM DeveloperSupport: SW Requirement Porject Manager, SWPM, SW Safety Engineer, SW Test Enineer ?, Conclusion: Change to Analysed, LogType: Other

Provide the details for the given input

ID: 5532752

ID: 5532752, Summary: [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 parkapplyExpected 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 ePbcActuatorStateUnknown11/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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply

ID: 5532752, Summary: [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 parkapplyExpected 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 ePbcActuatorStateUnknown11/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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply

ID: 5532752, Summary: [Issue] of PBC_040 - SIL Test - Actuator change to Unknown at RAR and HostAvailability NONE/APPLY/RELEASE, before RAR or Parkapply, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 parkapplyExpected 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 ePbcActuatorStateUnknown11/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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given input

ID: 5532782

ID: 5532782, Summary: [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity , State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 finishedActual behaviour: Actuation stops and affected actuator is unknownFurther Information/Requirements: If actuation is possible shall not stop..Please see attachment 1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document., Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity

ID: 5532782, Summary: [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity , State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 finishedActual behaviour: Actuation stops and affected actuator is unknownFurther Information/Requirements: If actuation is possible shall not stop..Please see attachment 1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document., Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity

ID: 5532782, Summary: [Issue] of PBC_040 - SIL Test - Actuation stops even if actuation is possible due to change of Hostavailablity , State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: 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 finishedActual behaviour: Actuation stops and affected actuator is unknownFurther Information/Requirements: If actuation is possible shall not stop..Please see attachment 1/11/21: Analyzed by Mark Lubbers. Changes made to Design Document., Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps., LogType: Other

Provide the details for the given input

ID: 5532789

ID: 5532789, Summary: [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions:Precondition for RARAction:Set all speeds >= 15 km/hExpected Behaviour: No RAR perfomedActual behaviour: RAR is performedFurther 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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.12/02/21: Change Implemented per associated task., LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h

ID: 5532789, Summary: [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions:Precondition for RARAction:Set all speeds >= 15 km/hExpected Behaviour: No RAR perfomedActual behaviour: RAR is performedFurther 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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.12/02/21: Change Implemented per associated task., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h

ID: 5532789, Summary: [Issue] of PBC_040 - SIL Test - RAR perform with speed >= 15 km/h, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions:Precondition for RARAction:Set all speeds >= 15 km/hExpected Behaviour: No RAR perfomedActual behaviour: RAR is performedFurther 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, Conclusion: EPB System CCB - JAS - 11.08.21:Please investigate this point and advise the next steps.12/02/21: Change Implemented per associated task., LogType: Other

Provide the details for the given input

ID: 5532795

ID: 5532795, Summary: [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early, State: ALM_Rejected, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions: Init with Fully released actuators.Action:Apply Release under several condition.Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNoneActual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleasedFurther 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, Conclusion: 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), LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early

ID: 5532795, Summary: [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early, State: ALM_Rejected, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions: Init with Fully released actuators.Action:Apply Release under several condition.Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNoneActual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleasedFurther 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, Conclusion: 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), LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early

ID: 5532795, Summary: [Issue] of PBC_040 - SIL Test - PowerLatchRequest = ePbcPowerLatchNotRequested too early, State: ALM_Rejected, Project: /EPB/CustomerDevelopment/Ford/P708-eDIH-Livonia, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Preconditions: Init with Fully released actuators.Action:Apply Release under several condition.Expected Behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested two cycles after last PbcOut.MotorComamd = ePbcMotorCommandNoneActual behaviour: PbcOut.EcuPowerLatchRequest = ePbcPowerLatchNotRequested after last Pbcout.Actuatorstae = ePbcActuatorStateParkApplied ORePbcActuatorStateReleasedFurther 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, Conclusion: 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), LogType: Other

Provide the details for the given input

ID: 5533018

ID: 5533018, Summary: [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected, State: ALM_Rejected, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488194, Classification: Incident / Problem / Bug, Comments: [rausch fabian kbl adws31 (rauschf), aug 30, 2021 7:18:38 am cest]as confirmed in the attached email the issue is solved. cr was moved to rejected. [scafes alexandru tms (z0022277), aug 27, 2021 11:52:52 am cest]integration & build, a scafes 27.08.21 it have been confirmed that the issue was solved. see the email attachment. i propose the cr for rejection.[andre andreas kbl adws32 (andrea), aug 27, 2021 8:42:20 am cest]brksw integration & services ccb - aa (27.08.21 - 08:41):reinvestigate this cr according new information., Description: When trying o connect CANApe with generatedDA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured. Please analys and implment necessary Changes in A2l, Conclusion: [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): mediumAnalysis completed by (applicable only for distributed analyses):Alexandru ScafesProposal 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., LogType: Other

Provide the details for the given ID

Summary: [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected

ID: 5533018, Summary: [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected, State: ALM_Rejected, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488194, Classification: Incident / Problem / Bug, Comments: [rausch fabian kbl adws31 (rauschf), aug 30, 2021 7:18:38 am cest]as confirmed in the attached email the issue is solved. cr was moved to rejected. [scafes alexandru tms (z0022277), aug 27, 2021 11:52:52 am cest]integration & build, a scafes 27.08.21 it have been confirmed that the issue was solved. see the email attachment. i propose the cr for rejection.[andre andreas kbl adws32 (andrea), aug 27, 2021 8:42:20 am cest]brksw integration & services ccb - aa (27.08.21 - 08:41):reinvestigate this cr according new information., Description: When trying o connect CANApe with generatedDA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured. Please analys and implment necessary Changes in A2l, Conclusion: [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): mediumAnalysis completed by (applicable only for distributed analyses):Alexandru ScafesProposal 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected

ID: 5533018, Summary: [Daimler_MMA_IBC] VX1000 connection setting in A2l shall be corrected, State: ALM_Rejected, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488194, Classification: Incident / Problem / Bug, Comments: [rausch fabian kbl adws31 (rauschf), aug 30, 2021 7:18:38 am cest]as confirmed in the attached email the issue is solved. cr was moved to rejected. [scafes alexandru tms (z0022277), aug 27, 2021 11:52:52 am cest]integration & build, a scafes 27.08.21 it have been confirmed that the issue was solved. see the email attachment. i propose the cr for rejection.[andre andreas kbl adws32 (andrea), aug 27, 2021 8:42:20 am cest]brksw integration & services ccb - aa (27.08.21 - 08:41):reinvestigate this cr according new information., Description: When trying o connect CANApe with generatedDA31_P05_M10_S02_VT2_200_010_000_RTP.A2L, following error is occured. Please analys and implment necessary Changes in A2l, Conclusion: [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): mediumAnalysis completed by (applicable only for distributed analyses):Alexandru ScafesProposal 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., LogType: Other

Provide the details for the given input

ID: 5533022

ID: 5533022, Summary: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504600, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), sep 16, 2021 3:35:27 pm cest]preintegration of 5655446 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_boot#d=preinteg_vw_mqb_esc_a. checkpoint number is 1.13.1.1.1.13., Description: [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):FLASH_TEST_GutfallKommentar 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 ABResponse (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 3100000 (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., Conclusion: Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not ImplementedDescription:· 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:, LogType: Memory

Provide the details for the given ID

Summary: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory

ID: 5533022, Summary: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504600, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), sep 16, 2021 3:35:27 pm cest]preintegration of 5655446 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_boot#d=preinteg_vw_mqb_esc_a. checkpoint number is 1.13.1.1.1.13., Description: [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):FLASH_TEST_GutfallKommentar 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 ABResponse (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 3100000 (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., Conclusion: Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not ImplementedDescription:· 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:, LogType: Memory

Provide the details for the given Summary

LogType: Memory, Company: VW, Summary: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory

ID: 5533022, Summary: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504600, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), sep 16, 2021 3:35:27 pm cest]preintegration of 5655446 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_boot#d=preinteg_vw_mqb_esc_a. checkpoint number is 1.13.1.1.1.13., Description: [Error Description]: VW80126.Gutfall (80126/VW80126.Gutfall):FLASH_TEST_GutfallKommentar 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 ABResponse (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 3100000 (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., Conclusion: Title: [VW KPM] [SV][BL][CAN] F1AB nach CheckMemory - Block Invalidation not ImplementedDescription:· 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:, LogType: Memory

Provide the details for the given input

ID: 5533019

ID: 5533019, Summary: [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504591, Classification: Incident / Problem / Bug, Comments: , Description: Perform an analysis for the issue below and suggest the next steps. [Error Description]: Kontaktdaten:E-Mail: VWAG R: WOB, EESN Sys-VQBeanstandung vom Sys-VQ-PrüfplatzPMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):Aktivierung aller Produktionsmodes in erlaubter SessionKommentar 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 FEResponse (6): 62 04 FE 00 00 0000000 (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]:, Conclusion: 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., LogType: Other

Provide the details for the given ID

Summary: [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF

ID: 5533019, Summary: [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504591, Classification: Incident / Problem / Bug, Comments: , Description: Perform an analysis for the issue below and suggest the next steps. [Error Description]: Kontaktdaten:E-Mail: VWAG R: WOB, EESN Sys-VQBeanstandung vom Sys-VQ-PrüfplatzPMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):Aktivierung aller Produktionsmodes in erlaubter SessionKommentar 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 FEResponse (6): 62 04 FE 00 00 0000000 (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]:, Conclusion: 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: VW, Summary: [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF

ID: 5533019, Summary: [VW KPM] [SV][PMode][CAN] PMode Parameter FF FF FF, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504591, Classification: Incident / Problem / Bug, Comments: , Description: Perform an analysis for the issue below and suggest the next steps. [Error Description]: Kontaktdaten:E-Mail: VWAG R: WOB, EESN Sys-VQBeanstandung vom Sys-VQ-PrüfplatzPMode.00.01.0.040.010 (PMode/PMode_ab_V8.1/physikalisch):Aktivierung aller Produktionsmodes in erlaubter SessionKommentar 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 FEResponse (6): 62 04 FE 00 00 0000000 (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]:, Conclusion: 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., LogType: Other

Provide the details for the given input

ID: 5533079

ID: 5533079, Summary: [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488191, Classification: Incident / Problem / Bug, Comments: [christian weyand (weyandc), jun 2, 2021 11:40:40 am cest]ccb-dc, weyandc: cr is closed after review.- [autosar] changes have been checked in with task 5292076. the task is linked to cr 5290840 which is linked to the same build as this cr.- [diag] related gaps regarding swe2, swe3 and swe4 will be handled with spawned cr 5323111.- [swad] task was canceled. the requested action will be performed with spawned cr 5346776 for sw_ad_backlog_x0200 with id 5323597.[christian rauh (rauhc), may 20, 2021 2:54:46 pm cest]dc-ccb: cr set to planned.[christian rauh (rauhc), may 20, 2021 2:54:24 pm cest]dc-ccb: cr approved.[christian rauh (rauhc), apr 14, 2021 3:28:49 pm cest]dc-ccb: please analyse and propose next steps., Description: This CR shall be used to implement the following diagnostic jobs:1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz2. 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., Conclusion: 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, DiagTestMgmtUnitDIAG 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 53004693. Diag framework adaptations:=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469AUOTSAR 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_Ő_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):mediumAnalysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via TeamsProposal of next steps (incl. effort/h and verification):TASK 1/5Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203Description:- 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 AmbarukhanaReviewer: Sireesha Basavaraju, C. WeyandEstimated 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/5Title: [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. HornungReviewer: C. WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 26.05.2021TASK 3/5Title: [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. WeyandReviewer: A. ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 28.05.2021TASK 4/5Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl frameworkDescription: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, DiagTestMgmtUnitGeneral: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.arxml2. 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 CommandInterfaceTestGroup:- 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" parameterInputOutputControlById.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_GENERALREJECTTestSpecification_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 entered2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd- just return FALSE3. 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 DigajerlaReviewer: C. WeyandEstimated 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/5Title: [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. KlukowskiReviewer: C. Bayer, C. WeyandEstimated 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), LogType: Other

Provide the details for the given ID

Summary: [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented

ID: 5533079, Summary: [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488191, Classification: Incident / Problem / Bug, Comments: [christian weyand (weyandc), jun 2, 2021 11:40:40 am cest]ccb-dc, weyandc: cr is closed after review.- [autosar] changes have been checked in with task 5292076. the task is linked to cr 5290840 which is linked to the same build as this cr.- [diag] related gaps regarding swe2, swe3 and swe4 will be handled with spawned cr 5323111.- [swad] task was canceled. the requested action will be performed with spawned cr 5346776 for sw_ad_backlog_x0200 with id 5323597.[christian rauh (rauhc), may 20, 2021 2:54:46 pm cest]dc-ccb: cr set to planned.[christian rauh (rauhc), may 20, 2021 2:54:24 pm cest]dc-ccb: cr approved.[christian rauh (rauhc), apr 14, 2021 3:28:49 pm cest]dc-ccb: please analyse and propose next steps., Description: This CR shall be used to implement the following diagnostic jobs:1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz2. 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., Conclusion: 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, DiagTestMgmtUnitDIAG 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 53004693. Diag framework adaptations:=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469AUOTSAR 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_Ő_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):mediumAnalysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via TeamsProposal of next steps (incl. effort/h and verification):TASK 1/5Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203Description:- 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 AmbarukhanaReviewer: Sireesha Basavaraju, C. WeyandEstimated 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/5Title: [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. HornungReviewer: C. WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 26.05.2021TASK 3/5Title: [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. WeyandReviewer: A. ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 28.05.2021TASK 4/5Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl frameworkDescription: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, DiagTestMgmtUnitGeneral: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.arxml2. 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 CommandInterfaceTestGroup:- 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" parameterInputOutputControlById.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_GENERALREJECTTestSpecification_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 entered2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd- just return FALSE3. 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 DigajerlaReviewer: C. WeyandEstimated 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/5Title: [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. KlukowskiReviewer: C. Bayer, C. WeyandEstimated 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), LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented

ID: 5533079, Summary: [Defect]: [Diag] ESP178: Session Handling-OTX - Check reprogramming precondition Not Implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488191, Classification: Incident / Problem / Bug, Comments: [christian weyand (weyandc), jun 2, 2021 11:40:40 am cest]ccb-dc, weyandc: cr is closed after review.- [autosar] changes have been checked in with task 5292076. the task is linked to cr 5290840 which is linked to the same build as this cr.- [diag] related gaps regarding swe2, swe3 and swe4 will be handled with spawned cr 5323111.- [swad] task was canceled. the requested action will be performed with spawned cr 5346776 for sw_ad_backlog_x0200 with id 5323597.[christian rauh (rauhc), may 20, 2021 2:54:46 pm cest]dc-ccb: cr set to planned.[christian rauh (rauhc), may 20, 2021 2:54:24 pm cest]dc-ccb: cr approved.[christian rauh (rauhc), apr 14, 2021 3:28:49 pm cest]dc-ccb: please analyse and propose next steps., Description: This CR shall be used to implement the following diagnostic jobs:1. Check Reprogramming Preconditions - StartRoutine: $31 01 02 03 zz2. 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., Conclusion: 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, DiagTestMgmtUnitDIAG 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 53004693. Diag framework adaptations:=> Please, refer to the task description of the [SWE3/4][Diag] task for details: ALM_Task 5300469AUOTSAR 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_Ő_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):mediumAnalysis completed by (applicable only for distributed analyses): WeyandC, SwAD part confirmed by C. Klukowski, Autosar task proposal confirmed by S. Basavaraju via TeamsProposal of next steps (incl. effort/h and verification):TASK 1/5Title: [MMA][Autosar][X0200] Connect ports between Dcm and SWC DIAG and map ports to OS tasks for routine 0x0203Description:- 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 AmbarukhanaReviewer: Sireesha Basavaraju, C. WeyandEstimated 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/5Title: [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. HornungReviewer: C. WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 26.05.2021TASK 3/5Title: [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. WeyandReviewer: A. ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date: 28.05.2021TASK 4/5Title: [MMA][Diag][SWE3/4][X0200] Implement routine 0x0203 "Check Reprogramming Preconditions" and adapt RoutineControl frameworkDescription: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, DiagTestMgmtUnitGeneral: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.arxml2. 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 CommandInterfaceTestGroup:- 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" parameterInputOutputControlById.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_GENERALREJECTTestSpecification_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 entered2. Implement Update_Interface with subsystem scope: UpdateChkPrgrPrecnd- just return FALSE3. 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 DigajerlaReviewer: C. WeyandEstimated 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/5Title: [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. KlukowskiReviewer: C. Bayer, C. WeyandEstimated 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), LogType: Other

Provide the details for the given input

ID: 5533074

ID: 5533074, Summary: [Defect]: [Diag] ESP178: ID-Data services not implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488189, Classification: Incident / Problem / Bug, Comments: [christian rauh (rauhc), may 7, 2021 10:03:58 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), may 5, 2021 8:43:38 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.127.[christian weyand (weyandc), may 5, 2021 8:49:00 am cest]dc-ccb: owner of reviewer 5197065 was changed as originally intended reviewer is not available.[(system user) user for queue manager (scs_queuemanager), may 4, 2021 9:05:55 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.126.[christian rauh (rauhc), apr 28, 2021 6:55:54 am cest]dc-ccb: cr approved.[christian rauh (rauhc), jan 12, 2021 11:15:15 am cet]dc-ccb: please analyse and propose next steps., Description: Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Maturity 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'; DiagPlease 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 16Link 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 stagesAcceptance 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>'.', Conclusion: Brief analysis summary:22.04.2021Ashwini DigajerlaDig 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): lowAnalysis completed by (applicable only for distributed analyses): Ashwini Digajerla . TASKTitle: [SWE1/4][Diag] SF 8.8 System Diagnostic Function Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131Link 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 HornungReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date:TASKTitle: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131Please, 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 WeyandReviewer: Ahmed ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 7h[Optional] Planned completion date: 30.04.2021 TASKTitle: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:Implement Diag application part to support DIDs 0xF104 and 0xF131 . The task shall be used:1. to update the design model2. to implement the requested functionality including QAC, polyspace and log file analysis3. 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 ElxsiReviewer: Ashwini DigajerlaEstimated design effort/h:6Estimated implementation effort/h:6Estimated unit testing effort/h:18Total 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 16Description: Please import and map requirements.Owner:Caesar KlukowskiReviewer: Christoph Bayer, Christian WeyandTotal 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 16Description:->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 BasavarajuReviewer: Hemanth Ambarukhana KrishnaTotal effort/h: 8[Optional] Planned completion date: 30.4.2021, LogType: Other

Provide the details for the given ID

Summary: [Defect]: [Diag] ESP178: ID-Data services not implemented

ID: 5533074, Summary: [Defect]: [Diag] ESP178: ID-Data services not implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488189, Classification: Incident / Problem / Bug, Comments: [christian rauh (rauhc), may 7, 2021 10:03:58 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), may 5, 2021 8:43:38 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.127.[christian weyand (weyandc), may 5, 2021 8:49:00 am cest]dc-ccb: owner of reviewer 5197065 was changed as originally intended reviewer is not available.[(system user) user for queue manager (scs_queuemanager), may 4, 2021 9:05:55 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.126.[christian rauh (rauhc), apr 28, 2021 6:55:54 am cest]dc-ccb: cr approved.[christian rauh (rauhc), jan 12, 2021 11:15:15 am cet]dc-ccb: please analyse and propose next steps., Description: Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Maturity 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'; DiagPlease 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 16Link 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 stagesAcceptance 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>'.', Conclusion: Brief analysis summary:22.04.2021Ashwini DigajerlaDig 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): lowAnalysis completed by (applicable only for distributed analyses): Ashwini Digajerla . TASKTitle: [SWE1/4][Diag] SF 8.8 System Diagnostic Function Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131Link 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 HornungReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date:TASKTitle: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131Please, 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 WeyandReviewer: Ahmed ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 7h[Optional] Planned completion date: 30.04.2021 TASKTitle: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:Implement Diag application part to support DIDs 0xF104 and 0xF131 . The task shall be used:1. to update the design model2. to implement the requested functionality including QAC, polyspace and log file analysis3. 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 ElxsiReviewer: Ashwini DigajerlaEstimated design effort/h:6Estimated implementation effort/h:6Estimated unit testing effort/h:18Total 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 16Description: Please import and map requirements.Owner:Caesar KlukowskiReviewer: Christoph Bayer, Christian WeyandTotal 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 16Description:->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 BasavarajuReviewer: Hemanth Ambarukhana KrishnaTotal effort/h: 8[Optional] Planned completion date: 30.4.2021, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Defect]: [Diag] ESP178: ID-Data services not implemented

ID: 5533074, Summary: [Defect]: [Diag] ESP178: ID-Data services not implemented, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488189, Classification: Incident / Problem / Bug, Comments: [christian rauh (rauhc), may 7, 2021 10:03:58 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), may 5, 2021 8:43:38 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.127.[christian weyand (weyandc), may 5, 2021 8:49:00 am cest]dc-ccb: owner of reviewer 5197065 was changed as originally intended reviewer is not available.[(system user) user for queue manager (scs_queuemanager), may 4, 2021 9:05:55 pm cest]preintegration of 5204252 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.126.[christian rauh (rauhc), apr 28, 2021 6:55:54 am cest]dc-ccb: cr approved.[christian rauh (rauhc), jan 12, 2021 11:15:15 am cet]dc-ccb: please analyse and propose next steps., Description: Aim (Objective and Rationale): Feature implementation of [DCRP 46.1] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Maturity 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'; DiagPlease 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 16Link 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 stagesAcceptance 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>'.', Conclusion: Brief analysis summary:22.04.2021Ashwini DigajerlaDig 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): lowAnalysis completed by (applicable only for distributed analyses): Ashwini Digajerla . TASKTitle: [SWE1/4][Diag] SF 8.8 System Diagnostic Function Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE1) Please, provide Sw requirements for the customer requirements that specify diagnostic service: 0xF104,0xF131Link 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 HornungReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 4h[Optional] Planned completion date:TASKTitle: [SWE2/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:(SWE2) Please update SwAD model according to derived requirements. The CR is used to implement diagnsotic service :0xF104,0xF131Please, 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 WeyandReviewer: Ahmed ElfekyEstimated design effort/h:Estimated implementation effort/h:Estimated unit testing effort/h:Total effort/h: 7h[Optional] Planned completion date: 30.04.2021 TASKTitle: [SWE3/4][Diag] SF 8.8 System Diagnostic Function - Read ID-Data: Remaining jobs, Cluster ID 16Description:Implement Diag application part to support DIDs 0xF104 and 0xF131 . The task shall be used:1. to update the design model2. to implement the requested functionality including QAC, polyspace and log file analysis3. 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 ElxsiReviewer: Ashwini DigajerlaEstimated design effort/h:6Estimated implementation effort/h:6Estimated unit testing effort/h:18Total 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 16Description: Please import and map requirements.Owner:Caesar KlukowskiReviewer: Christoph Bayer, Christian WeyandTotal 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 16Description:->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 BasavarajuReviewer: Hemanth Ambarukhana KrishnaTotal effort/h: 8[Optional] Planned completion date: 30.4.2021, LogType: Other

Provide the details for the given input

ID: 5533127

ID: 5533127, Summary: [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504646, Classification: Incident / Problem / Bug, Comments: [simo mannan kbl adwc54 (simom1), jul 28, 2021 3:35:45 pm cest][autosar & 3rd party sw ccb 2021-07-28] simom1: cr closed.[(system user) user for queue manager (scs_queuemanager), jul 28, 2021 2:15:58 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.72.[(system user) user for queue manager (scs_queuemanager), jul 27, 2021 6:55:52 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.71.[simo mannan kbl adwc54 (simom1), jul 26, 2021 6:08:37 pm cest][autosar & 3rd party sw ccb 2021-07-26] simom1: cr approved.[ujawane riya kbl adwc54 (ujawanr1), jul 26, 2021 10:03:19 am cest]cr assigned. proceed with the analysis., Description: 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., Conclusion: 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): lowAnalysis completed by (applicable only for distributed analyses):Proposal of next steps (incl. effort/h and verification): Implement proposed task, LogType: Other

Provide the details for the given ID

Summary: [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler

ID: 5533127, Summary: [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504646, Classification: Incident / Problem / Bug, Comments: [simo mannan kbl adwc54 (simom1), jul 28, 2021 3:35:45 pm cest][autosar & 3rd party sw ccb 2021-07-28] simom1: cr closed.[(system user) user for queue manager (scs_queuemanager), jul 28, 2021 2:15:58 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.72.[(system user) user for queue manager (scs_queuemanager), jul 27, 2021 6:55:52 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.71.[simo mannan kbl adwc54 (simom1), jul 26, 2021 6:08:37 pm cest][autosar & 3rd party sw ccb 2021-07-26] simom1: cr approved.[ujawane riya kbl adwc54 (ujawanr1), jul 26, 2021 10:03:19 am cest]cr assigned. proceed with the analysis., Description: 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., Conclusion: 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): lowAnalysis completed by (applicable only for distributed analyses):Proposal of next steps (incl. effort/h and verification): Implement proposed task, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: VW, Summary: [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler

ID: 5533127, Summary: [VW][MQB48W][ESC][X0401-010_X330] ESP_StartStopp_Info = Systemfehler, State: ALM_Closed, Project: /BRK/Customer/VW/MQB48-W/ESC, Company: VW, Team: 2504646, Classification: Incident / Problem / Bug, Comments: [simo mannan kbl adwc54 (simom1), jul 28, 2021 3:35:45 pm cest][autosar & 3rd party sw ccb 2021-07-28] simom1: cr closed.[(system user) user for queue manager (scs_queuemanager), jul 28, 2021 2:15:58 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.72.[(system user) user for queue manager (scs_queuemanager), jul 27, 2021 6:55:52 pm cest]preintegration of 5541855 was successful. a checkpoint has been created on path #/brk#customer/vw/mqb48-w/esc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_vw10_p03_m10_vtx_401_xxx_xxx_a. checkpoint number is 1.633.1.215.2.71.[simo mannan kbl adwc54 (simom1), jul 26, 2021 6:08:37 pm cest][autosar & 3rd party sw ccb 2021-07-26] simom1: cr approved.[ujawane riya kbl adwc54 (ujawanr1), jul 26, 2021 10:03:19 am cest]cr assigned. proceed with the analysis., Description: 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., Conclusion: 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): lowAnalysis completed by (applicable only for distributed analyses):Proposal of next steps (incl. effort/h and verification): Implement proposed task, LogType: Other

Provide the details for the given input

ID: 5533486

ID: 5533486, Summary: Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC", State: ALM_Checked, Project: /EPB/CustomerDevelopment/Audi/CBEV, Company: CustomerDevelopment, Team: 1872073, Classification: Requirements, Comments: [gerz michael kbl adby212 (wyrthm), aug 11, 2021 11:51:44 am cest]f&c ccb - mg - 11.08.2021 - 11:51cr closed., Description: 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, Conclusion: 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): mediumProposal 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., LogType: Other

Provide the details for the given ID

Summary: Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"

ID: 5533486, Summary: Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC", State: ALM_Checked, Project: /EPB/CustomerDevelopment/Audi/CBEV, Company: CustomerDevelopment, Team: 1872073, Classification: Requirements, Comments: [gerz michael kbl adby212 (wyrthm), aug 11, 2021 11:51:44 am cest]f&c ccb - mg - 11.08.2021 - 11:51cr closed., Description: 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, Conclusion: 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): mediumProposal 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC"

ID: 5533486, Summary: Customer Request: parameter set in new format: BRSMLB51AB-1235: "Umsetzung UNECE Datensatzupdate PBC", State: ALM_Checked, Project: /EPB/CustomerDevelopment/Audi/CBEV, Company: CustomerDevelopment, Team: 1872073, Classification: Requirements, Comments: [gerz michael kbl adby212 (wyrthm), aug 11, 2021 11:51:44 am cest]f&c ccb - mg - 11.08.2021 - 11:51cr closed., Description: 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, Conclusion: 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): mediumProposal 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., LogType: Other

Provide the details for the given input

ID: 5533541

ID: 5533541, Summary: [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn, State: ALM_Rejected, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: , Classification: Quality, Comments: , Description: "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, Conclusion: Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group., LogType: Other

Provide the details for the given ID

Summary: [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn

ID: 5533541, Summary: [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn, State: ALM_Rejected, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: , Classification: Quality, Comments: , Description: "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, Conclusion: Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: EngineeringQuality, Summary: [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn

ID: 5533541, Summary: [QRCM] GM T1XX - Motor Position Sensor (MPS) Failure to Learn, State: ALM_Rejected, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: , Classification: Quality, Comments: , Description: "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, Conclusion: Reject this CR for Preventive Action. SW can handle any specified range of error adjustment. 2% was specificed by Systems group., LogType: Other

Provide the details for the given input

ID: 5461318

ID: 5461318, Summary: [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), State: ALM_Closed, Project: /Steering/Projects/Geely/Lotus_EPA/PR55729_LVS_ENG_APP_Geely_Lotus_EPA_EPS_BD_SYS_HRoom_AP, Company: Geely, Team: 4247386, Classification: Quality, Comments: , Description: Update MS Project information according to mentioned points., Conclusion: Update MS project information according to the weekness that ASPICE mentioned., LogType: Other

Provide the details for the given ID

Summary: [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)

ID: 5461318, Summary: [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), State: ALM_Closed, Project: /Steering/Projects/Geely/Lotus_EPA/PR55729_LVS_ENG_APP_Geely_Lotus_EPA_EPS_BD_SYS_HRoom_AP, Company: Geely, Team: 4247386, Classification: Quality, Comments: , Description: Update MS Project information according to mentioned points., Conclusion: Update MS project information according to the weekness that ASPICE mentioned., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Geely, Summary: [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)

ID: 5461318, Summary: [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), State: ALM_Closed, Project: /Steering/Projects/Geely/Lotus_EPA/PR55729_LVS_ENG_APP_Geely_Lotus_EPA_EPS_BD_SYS_HRoom_AP, Company: Geely, Team: 4247386, Classification: Quality, Comments: , Description: Update MS Project information according to mentioned points., Conclusion: Update MS project information according to the weekness that ASPICE mentioned., LogType: Other

Provide the details for the given input

ID: 5533620

ID: 5533620, Summary: Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given ID

Summary: Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults

ID: 5533620, Summary: Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given Summary

LogType: Fault Detection Log, Company: GM, Summary: Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults

ID: 5533620, Summary: Integration OP A100/BEV3 PBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given input

ID: 5533633

ID: 5533633, Summary: Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given ID

Summary: Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults

ID: 5533633, Summary: Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given Summary

LogType: Fault Detection Log, Company: GM, Summary: Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults

ID: 5533633, Summary: Integration OP A100/BEV3 SBM - Remove Ground Disconnected Faults, State: ALM_Closed, Project: /IBC/Customer/GM/A100, Company: GM, Team: 2612757, Classification: Requirements, Comments: , Description: The goal of this CR is to disable/remove Ground monitor failsafes from A100 PBM, A100 SBM and 31XX.2 programs., Conclusion: 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., LogType: Fault Detection Log

Provide the details for the given input

ID: 5461337

ID: 5461337, Summary: [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected, State: ALM_Closed, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544059, Classification: Incident / Problem / Bug, Comments: [karthik kamasamudram (z0016377), jul 6, 2021 6:01:30 am cest]closed by swpm[(system user) user for queue manager (scs_queuemanager), jul 2, 2021 2:38:54 pm cest]preintegration of 5472204 was successful. a checkpoint has been created on path #/scs#customer/psa/opel_x250/05_software/view_mainline/mmc_appl#d=preintegration_opel_x250. checkpoint number is 1.2.1.372., Description: 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,, Conclusion: The group ordering for the AAW calibration set must be changed, LogType: Fault Detection Log

Provide the details for the given ID

Summary: [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected

ID: 5461337, Summary: [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected, State: ALM_Closed, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544059, Classification: Incident / Problem / Bug, Comments: [karthik kamasamudram (z0016377), jul 6, 2021 6:01:30 am cest]closed by swpm[(system user) user for queue manager (scs_queuemanager), jul 2, 2021 2:38:54 pm cest]preintegration of 5472204 was successful. a checkpoint has been created on path #/scs#customer/psa/opel_x250/05_software/view_mainline/mmc_appl#d=preintegration_opel_x250. checkpoint number is 1.2.1.372., Description: 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,, Conclusion: The group ordering for the AAW calibration set must be changed, LogType: Fault Detection Log

Provide the details for the given Summary

LogType: Fault Detection Log, Company: PSA, Summary: [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected

ID: 5461337, Summary: [OPEL K0][X300_173][CAT2][ADTY3][TEC]: UNEXPECTED_EXCEPTION - fault is seen unexpected, State: ALM_Closed, Project: /SCS/Customer/PSA/K0, Company: PSA, Team: 3544059, Classification: Incident / Problem / Bug, Comments: [karthik kamasamudram (z0016377), jul 6, 2021 6:01:30 am cest]closed by swpm[(system user) user for queue manager (scs_queuemanager), jul 2, 2021 2:38:54 pm cest]preintegration of 5472204 was successful. a checkpoint has been created on path #/scs#customer/psa/opel_x250/05_software/view_mainline/mmc_appl#d=preintegration_opel_x250. checkpoint number is 1.2.1.372., Description: 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,, Conclusion: The group ordering for the AAW calibration set must be changed, LogType: Fault Detection Log

Provide the details for the given input

ID: 5533777

ID: 5533777, Summary: [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM), State: ALM_Defined, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: 3383777, Classification: Incident / Problem / Bug, Comments: [hollingsworth mark lvn aqdb3 (z0053591), sep 20, 2021 10:56:45 pm cest]comment below is a mix-up. this issue is not for steven helinski.this topic is within nvram (memo-team) stephan scheider from my team ( alfter ingo dr. kbl adwc) will support here, he is vacation and will be back 4th october.?but i still can't assign correct owner to this cr. [hollingsworth mark lvn aqdb3 (z0053591), aug 31, 2021 2:55:58 pm cest] - not able to add the correct owner, steve helinski (aka helinski steven lvn adwn21 <steven.helinski@zf.com>), probably because of the project this cr is in., Description: - 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, Conclusion: Meeting Minutes: Oct-5Participants: 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 owner2) 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., LogType: Other

Provide the details for the given ID

Summary: [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM)

ID: 5533777, Summary: [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM), State: ALM_Defined, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: 3383777, Classification: Incident / Problem / Bug, Comments: [hollingsworth mark lvn aqdb3 (z0053591), sep 20, 2021 10:56:45 pm cest]comment below is a mix-up. this issue is not for steven helinski.this topic is within nvram (memo-team) stephan scheider from my team ( alfter ingo dr. kbl adwc) will support here, he is vacation and will be back 4th october.?but i still can't assign correct owner to this cr. [hollingsworth mark lvn aqdb3 (z0053591), aug 31, 2021 2:55:58 pm cest] - not able to add the correct owner, steve helinski (aka helinski steven lvn adwn21 <steven.helinski@zf.com>), probably because of the project this cr is in., Description: - 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, Conclusion: Meeting Minutes: Oct-5Participants: 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 owner2) 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: EngineeringQuality, Summary: [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM)

ID: 5533777, Summary: [xxxxxxx] [NA] GM T1XX - MEC counter corrupted during EOL test (NVRAM), State: ALM_Defined, Project: /BrkEngEQFS/EngineeringQuality, Company: EngineeringQuality, Team: 3383777, Classification: Incident / Problem / Bug, Comments: [hollingsworth mark lvn aqdb3 (z0053591), sep 20, 2021 10:56:45 pm cest]comment below is a mix-up. this issue is not for steven helinski.this topic is within nvram (memo-team) stephan scheider from my team ( alfter ingo dr. kbl adwc) will support here, he is vacation and will be back 4th october.?but i still can't assign correct owner to this cr. [hollingsworth mark lvn aqdb3 (z0053591), aug 31, 2021 2:55:58 pm cest] - not able to add the correct owner, steve helinski (aka helinski steven lvn adwn21 <steven.helinski@zf.com>), probably because of the project this cr is in., Description: - 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, Conclusion: Meeting Minutes: Oct-5Participants: 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 owner2) 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., LogType: Other

Provide the details for the given input

ID: 5533814

ID: 5533814, Summary: 18A incorrect in ESLM data package, State: ALM_Closed, Project: /Steering/Projects/FCA-FIAT/MP/PR55906_LVS_ENG_APP_FCA_598_EPS_CD_SYS_HRoom_NA, Company: FCA-FIAT, Team: 4038904, Classification: Incident / Problem / Bug, Comments: , Description: , Conclusion: One task for PXX team to implement the fix 2021-08-04 StolarsK: Fix was implemented. CR can be closed., LogType: Other

Provide the details for the given ID

Summary: 18A incorrect in ESLM data package

ID: 5533814, Summary: 18A incorrect in ESLM data package, State: ALM_Closed, Project: /Steering/Projects/FCA-FIAT/MP/PR55906_LVS_ENG_APP_FCA_598_EPS_CD_SYS_HRoom_NA, Company: FCA-FIAT, Team: 4038904, Classification: Incident / Problem / Bug, Comments: , Description: , Conclusion: One task for PXX team to implement the fix 2021-08-04 StolarsK: Fix was implemented. CR can be closed., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: FCA-FIAT, Summary: 18A incorrect in ESLM data package

ID: 5533814, Summary: 18A incorrect in ESLM data package, State: ALM_Closed, Project: /Steering/Projects/FCA-FIAT/MP/PR55906_LVS_ENG_APP_FCA_598_EPS_CD_SYS_HRoom_NA, Company: FCA-FIAT, Team: 4038904, Classification: Incident / Problem / Bug, Comments: , Description: , Conclusion: One task for PXX team to implement the fix 2021-08-04 StolarsK: Fix was implemented. CR can be closed., LogType: Other

Provide the details for the given input

ID: 5461871

ID: 5461871, Summary: [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given ID

Summary: [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX

ID: 5461871, Summary: [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: ZF, Summary: [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX

ID: 5461871, Summary: [QA][WPA][PV03][S110-S120] System Baseline Work product to be released_ReAX, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given input

ID: 5461909

ID: 5461909, Summary: [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given ID

Summary: [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project

ID: 5461909, Summary: [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: ZF, Summary: [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project

ID: 5461909, Summary: [QA][WPA][S120][PV03] TSC needs an update with the changes to PV03 for ReAx project, State: ALM_Closed, Project: /Steering/Projects/ZF/ReAx/PR47704_Core_ZF_ReAx_EPP, Company: ZF, Team: 2294505, Classification: Quality, Comments: [singh rajinder ext ext (singhr9), sep 29, 2021 4:05:42 pm cest]task for s150/s200 c40 checklist has been moved to pv03 master cr4767460, Description: 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., Conclusion: *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, LogType: Other

Provide the details for the given input

ID: 5462588

ID: 5462588, Summary: [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488200, Classification: Refactoring, Comments: [pahl lars kbl adws12 (pahll), aug 3, 2021 9:04:12 am cest]cr not finished for 250_020 sw freeze. therefore cr will be shifted to 260_000 sw[pahl lars kbl adws12 (pahll), jul 19, 2021 10:59:31 am cest]19.07.2021 lpa:cr not finished until 250_010 software freeze. therefore this cr will be shifted to 250_020 software, Description: Please verify that the provided MCP values are now correct., Conclusion: CR will be shifted to 260_000 sw, LogType: Other

Provide the details for the given ID

Summary: [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task

ID: 5462588, Summary: [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488200, Classification: Refactoring, Comments: [pahl lars kbl adws12 (pahll), aug 3, 2021 9:04:12 am cest]cr not finished for 250_020 sw freeze. therefore cr will be shifted to 260_000 sw[pahl lars kbl adws12 (pahll), jul 19, 2021 10:59:31 am cest]19.07.2021 lpa:cr not finished until 250_010 software freeze. therefore this cr will be shifted to 250_020 software, Description: Please verify that the provided MCP values are now correct., Conclusion: CR will be shifted to 260_000 sw, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task

ID: 5462588, Summary: [Daimler MMA][SADM][PressSens] Move update filter function to 1 ms Task, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 4488200, Classification: Refactoring, Comments: [pahl lars kbl adws12 (pahll), aug 3, 2021 9:04:12 am cest]cr not finished for 250_020 sw freeze. therefore cr will be shifted to 260_000 sw[pahl lars kbl adws12 (pahll), jul 19, 2021 10:59:31 am cest]19.07.2021 lpa:cr not finished until 250_010 software freeze. therefore this cr will be shifted to 250_020 software, Description: Please verify that the provided MCP values are now correct., Conclusion: CR will be shifted to 260_000 sw, LogType: Other

Provide the details for the given input

ID: 5463830

ID: 5463830, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given ID

Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working

ID: 5463830, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given Summary

LogType: Diagnostic Error, Company: Daimler, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working

ID: 5463830, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Root & Backend CA Certificate Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given input

ID: 5463915

ID: 5463915, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given ID

Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working

ID: 5463915, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given Summary

LogType: Diagnostic Error, Company: Daimler, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working

ID: 5463915, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue RoutineControl Authenticate Diagnostic User or Tester Diagnostic service not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [jilg christian kbl adws12 (jilgc), jul 13, 2021 10:09:52 am cest]cr closed in daily cyber security call.[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 5:42:42 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.218.[shembekar suyash slh (shembeks), jul 12, 2021 3:39:00 pm cest]cr moved to planned state so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:38:35 pm cest]cr moved to approved so new task can be started.[shembekar suyash slh (shembeks), jul 12, 2021 3:36:24 pm cest]cr moved back to alm_checked to create task.[rivers matthew kbl adwb22 (riversm), jul 12, 2021 3:22:22 pm cest][riversm 12.07.2021] -task proposal:title: [bug fix] - regenerate os/rte modules in davinci configuratordescription: an update to the task priority has create a change in the rte, which was not checked in.rte shall be generated and changes checked inowner: sireesha[(system user) user for queue manager (scs_queuemanager), jul 12, 2021 12:25:40 pm cest]preintegration of 5325138 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.217.[suyash shembekar (shembeks), jul 1, 2021 4:38:12 pm cest]local authentication issue is fixed so did 0x182 and rid 0x0260 is now working.following fixes are beedn identified :1. update security modules with correct configuration for random number2. add initialisation sequence for random seed init3. update os configuiration to add expiry points to csm and crypto main funcations and change priority of security task4. update rte configuration to reconnect the manufacturing service notification calls.[suyash shembekar (shembeks), jun 16, 2021 11:27:03 am cest]this issue is stilll under investigation and on root cause has been identified yet.during debugging 2 issues are found ( validity flag in structure crypto_30_libcv_keystorage[] and fauilre in certp_bergetelement()).this is reported to vector with tkt id cs0451455 and cs0451438. while response awaited from vector further investigation is in progress.[hari elaprolu (elaproh1), jun 15, 2021 10:51:04 am cest]hke: aanalysis/investigation has already been started in june 9th 2021, Description: Pre: Precondition, Randbedingungen, z.B. Kl 15 ein, Außentemp.,... >Platztest - ECU standaloneDiagnose via Monaco 9.02Restbussimulation 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.00100Monaco-OTX: DDS2020_V1_01_000Act: 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 RejectImplementation 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], Conclusion: Tasks are raised to formalize the changes as per the prototype.CR can be moved to Analysed, LogType: Diagnostic Error

Provide the details for the given input

ID: 5463979

ID: 5463979, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), nov 23, 2021 5:58:53 pm cet]preintegration of 5148808 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx_261_000_000_b. checkpoint number is 1.3.2.232.1.11.[rivers matthew kbl adwb22 (riversm), nov 17, 2021 9:35:51 am cet][riversm - 17.11] - added dependency to cr 5848560, which will provide new rom layout/bootloader for hsm[rivers matthew kbl adwb22 (riversm), nov 11, 2021 2:59:06 pm cet]tasktitle: [partitioning] - map vhsm filesdescription:please provide the mapping for the new hsm files.see cr attachments for screenshot of correct mapping.the following files are affected (ram -> ram__dspr0__mr_c0_qm, rom -> rom__pflash0__c0_mr_d):crypto_30_vhsm_cfg.ocrypto_30_vhsm_irq.ocrypto_30_vhsm_keyman....crypto_30_vhsm.ocrypto_30_vhsm_jobs.ocrypto_30_vhsm_ipc.oowner: fabian rauschreviewer:estimated design effort/h:estimated implementation effort/h:estimated unit testing effort/h:total effort/h:[optional] planned completion date:[sansome mark slh adwy13 (sansomem), oct 20, 2021 2:00:39 pm cest]all tasks have been checked by team responsible, moved to planned[sansome mark slh adwy13 (sansomem), oct 4, 2021 10:56:12 am cest]tasks agreed to be raised in security planning meeting (30/09/21). move cr to approved., Description: Please integrate HSM into application in order to support the security features defined in the parent OPCustomer 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.xlsxInternal Milestone DV, Conclusion: 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., LogType: Other

Provide the details for the given ID

Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working

ID: 5463979, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), nov 23, 2021 5:58:53 pm cet]preintegration of 5148808 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx_261_000_000_b. checkpoint number is 1.3.2.232.1.11.[rivers matthew kbl adwb22 (riversm), nov 17, 2021 9:35:51 am cet][riversm - 17.11] - added dependency to cr 5848560, which will provide new rom layout/bootloader for hsm[rivers matthew kbl adwb22 (riversm), nov 11, 2021 2:59:06 pm cet]tasktitle: [partitioning] - map vhsm filesdescription:please provide the mapping for the new hsm files.see cr attachments for screenshot of correct mapping.the following files are affected (ram -> ram__dspr0__mr_c0_qm, rom -> rom__pflash0__c0_mr_d):crypto_30_vhsm_cfg.ocrypto_30_vhsm_irq.ocrypto_30_vhsm_keyman....crypto_30_vhsm.ocrypto_30_vhsm_jobs.ocrypto_30_vhsm_ipc.oowner: fabian rauschreviewer:estimated design effort/h:estimated implementation effort/h:estimated unit testing effort/h:total effort/h:[optional] planned completion date:[sansome mark slh adwy13 (sansomem), oct 20, 2021 2:00:39 pm cest]all tasks have been checked by team responsible, moved to planned[sansome mark slh adwy13 (sansomem), oct 4, 2021 10:56:12 am cest]tasks agreed to be raised in security planning meeting (30/09/21). move cr to approved., Description: Please integrate HSM into application in order to support the security features defined in the parent OPCustomer 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.xlsxInternal Milestone DV, Conclusion: 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working

ID: 5463979, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Security event logging & DID 0x018F not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [(system user) user for queue manager (scs_queuemanager), nov 23, 2021 5:58:53 pm cet]preintegration of 5148808 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx_261_000_000_b. checkpoint number is 1.3.2.232.1.11.[rivers matthew kbl adwb22 (riversm), nov 17, 2021 9:35:51 am cet][riversm - 17.11] - added dependency to cr 5848560, which will provide new rom layout/bootloader for hsm[rivers matthew kbl adwb22 (riversm), nov 11, 2021 2:59:06 pm cet]tasktitle: [partitioning] - map vhsm filesdescription:please provide the mapping for the new hsm files.see cr attachments for screenshot of correct mapping.the following files are affected (ram -> ram__dspr0__mr_c0_qm, rom -> rom__pflash0__c0_mr_d):crypto_30_vhsm_cfg.ocrypto_30_vhsm_irq.ocrypto_30_vhsm_keyman....crypto_30_vhsm.ocrypto_30_vhsm_jobs.ocrypto_30_vhsm_ipc.oowner: fabian rauschreviewer:estimated design effort/h:estimated implementation effort/h:estimated unit testing effort/h:total effort/h:[optional] planned completion date:[sansome mark slh adwy13 (sansomem), oct 20, 2021 2:00:39 pm cest]all tasks have been checked by team responsible, moved to planned[sansome mark slh adwy13 (sansomem), oct 4, 2021 10:56:12 am cest]tasks agreed to be raised in security planning meeting (30/09/21). move cr to approved., Description: Please integrate HSM into application in order to support the security features defined in the parent OPCustomer 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.xlsxInternal Milestone DV, Conclusion: 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., LogType: Other

Provide the details for the given input

ID: 5464018

ID: 5464018, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [rauh christian kbl adwc31 (rauhc), sep 20, 2021 10:41:15 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), sep 14, 2021 9:37:44 am cest]preintegration of 5631593 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.347.[weyand christian kbl adwc31 (weyandc), sep 1, 2021 4:54:05 pm cest]ccb-dc, weyandc: cr is approved.[weyand christian kbl adwc31 (weyandc), aug 31, 2021 1:56:22 pm cest]weyandc: the acl related files "esp178_02.02.05_diag_005003.zip" were exported with ptc cr 5631911 out of cdd version 02.02.05 (= ptc revision 1.23) for x0260 diagnostic variant 0x005003. please, find the zip file attached to this cr.[weyand christian kbl adwc31 (weyandc), aug 18, 2021 8:27:45 am cest]ccb-dc, weyandc: please, analyze and propose next step(s)., Description: 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 56319112. CDD update on ZF side till August 24. => ALM_Change Request 56319113. Security related CDD update by customer till August 27. => ALM_Change Request 56319114. CDD import after KM update from August 27 till September 03., Conclusion: 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_WriteRoutine 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_RequestResultsThe 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 DIAGTitle: [MMA][Diag][SWE3/4][X0260] Import DEXT file and update Dcm and Diag Swc configurationDescription: 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 KizhakkeMukkatReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h: 16Estimated unit testing effort/h:Total effort/h: 16[Optional] Planned completion date: TASK Cyber SecurityTitle: [MMA][Security][X0260] Use the new ACL file to update the ACL configuration in SSADescription: 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 ShembekarReviewer: Shwetanshu KukretiEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date: TASK Bsw_AutocoreTitle: [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 BasavarajuReviewer: Hemanth AmbarukhanaEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date:, LogType: Other

Provide the details for the given ID

Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working

ID: 5464018, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [rauh christian kbl adwc31 (rauhc), sep 20, 2021 10:41:15 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), sep 14, 2021 9:37:44 am cest]preintegration of 5631593 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.347.[weyand christian kbl adwc31 (weyandc), sep 1, 2021 4:54:05 pm cest]ccb-dc, weyandc: cr is approved.[weyand christian kbl adwc31 (weyandc), aug 31, 2021 1:56:22 pm cest]weyandc: the acl related files "esp178_02.02.05_diag_005003.zip" were exported with ptc cr 5631911 out of cdd version 02.02.05 (= ptc revision 1.23) for x0260 diagnostic variant 0x005003. please, find the zip file attached to this cr.[weyand christian kbl adwc31 (weyandc), aug 18, 2021 8:27:45 am cest]ccb-dc, weyandc: please, analyze and propose next step(s)., Description: 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 56319112. CDD update on ZF side till August 24. => ALM_Change Request 56319113. Security related CDD update by customer till August 27. => ALM_Change Request 56319114. CDD import after KM update from August 27 till September 03., Conclusion: 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_WriteRoutine 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_RequestResultsThe 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 DIAGTitle: [MMA][Diag][SWE3/4][X0260] Import DEXT file and update Dcm and Diag Swc configurationDescription: 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 KizhakkeMukkatReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h: 16Estimated unit testing effort/h:Total effort/h: 16[Optional] Planned completion date: TASK Cyber SecurityTitle: [MMA][Security][X0260] Use the new ACL file to update the ACL configuration in SSADescription: 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 ShembekarReviewer: Shwetanshu KukretiEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date: TASK Bsw_AutocoreTitle: [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 BasavarajuReviewer: Hemanth AmbarukhanaEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date:, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: Daimler, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working

ID: 5464018, Summary: [Defect]: [Daimler][MMA][Issue]: CYS Issue Access Control List Version Information not working, State: ALM_Closed, Project: /BRK/Customer/Daimler/MMA/IBC, Company: Daimler, Team: 5259065, Classification: Incident / Problem / Bug, Comments: [rauh christian kbl adwc31 (rauhc), sep 20, 2021 10:41:15 am cest]dc-ccb: cr closed after formal review.[(system user) user for queue manager (scs_queuemanager), sep 14, 2021 9:37:44 am cest]preintegration of 5631593 was successful. a checkpoint has been created on path #/brk#customer/daimler/mma/ibc/05_software/view_mainline/mmc_appl#d=iqm_preinteg_da31_p05_m10_s02_vtx. checkpoint number is 1.3.3.347.[weyand christian kbl adwc31 (weyandc), sep 1, 2021 4:54:05 pm cest]ccb-dc, weyandc: cr is approved.[weyand christian kbl adwc31 (weyandc), aug 31, 2021 1:56:22 pm cest]weyandc: the acl related files "esp178_02.02.05_diag_005003.zip" were exported with ptc cr 5631911 out of cdd version 02.02.05 (= ptc revision 1.23) for x0260 diagnostic variant 0x005003. please, find the zip file attached to this cr.[weyand christian kbl adwc31 (weyandc), aug 18, 2021 8:27:45 am cest]ccb-dc, weyandc: please, analyze and propose next step(s)., Description: 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 56319112. CDD update on ZF side till August 24. => ALM_Change Request 56319113. Security related CDD update by customer till August 27. => ALM_Change Request 56319114. CDD import after KM update from August 27 till September 03., Conclusion: 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_WriteRoutine 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_RequestResultsThe 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 DIAGTitle: [MMA][Diag][SWE3/4][X0260] Import DEXT file and update Dcm and Diag Swc configurationDescription: 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 KizhakkeMukkatReviewer: Christian WeyandEstimated design effort/h:Estimated implementation effort/h: 16Estimated unit testing effort/h:Total effort/h: 16[Optional] Planned completion date: TASK Cyber SecurityTitle: [MMA][Security][X0260] Use the new ACL file to update the ACL configuration in SSADescription: 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 ShembekarReviewer: Shwetanshu KukretiEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date: TASK Bsw_AutocoreTitle: [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 BasavarajuReviewer: Hemanth AmbarukhanaEstimated design effort/h:Estimated implementation effort/h: 7Estimated unit testing effort/h:Total effort/h: 7[Optional] Planned completion date:, LogType: Other

Provide the details for the given input

ID: 5464023

ID: 5464023, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: [harder eduard kbl adby212 (hardere), sep 29, 2021 10:32:48 am cest]<function & control ccb - eha - (29.09.21 - 10:32):closed after task review.[(system user) user for queue manager (scs_queuemanager), sep 28, 2021 11:17:50 am cest]preintegration of 5506274 was successful. a checkpoint has been created on path #/epb#productdevelopment/epbi/08_software#d=iqm_preinteg_audi_ppe_b. checkpoint number is 1.28.3.2.3.2.2.93.[gerz michael kbl adby212 (wyrthm), sep 9, 2021 4:48:29 pm cest]f&c ccb - mg - 09.09.2021 - 16:48task created., Description: Precondition: Pbc Released, set PbcIn.WheelPressurereliabilityFL or FR or RL or RR = ePbcWheelPressureNotReliable and set one PbcIn.WheelPressurereliability after the other to ePbcWheelPressureReliable inAction: Set 4/3/2 different PbcIn.Wheelspeeds.Expected Behaviour: RefSpeed is the fastes wheelspeedActual Behaviour: Refspeed is the second fastes WheelspeedRequirements: EPBi_Audi_PPE-SwRS_1657EPBi_Audi_PPE-SwRS_1660Please see attachment, Conclusion: <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 HDREstimated Effort : 8hVerifier : E HarderIs 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., LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable

ID: 5464023, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: [harder eduard kbl adby212 (hardere), sep 29, 2021 10:32:48 am cest]<function & control ccb - eha - (29.09.21 - 10:32):closed after task review.[(system user) user for queue manager (scs_queuemanager), sep 28, 2021 11:17:50 am cest]preintegration of 5506274 was successful. a checkpoint has been created on path #/epb#productdevelopment/epbi/08_software#d=iqm_preinteg_audi_ppe_b. checkpoint number is 1.28.3.2.3.2.2.93.[gerz michael kbl adby212 (wyrthm), sep 9, 2021 4:48:29 pm cest]f&c ccb - mg - 09.09.2021 - 16:48task created., Description: Precondition: Pbc Released, set PbcIn.WheelPressurereliabilityFL or FR or RL or RR = ePbcWheelPressureNotReliable and set one PbcIn.WheelPressurereliability after the other to ePbcWheelPressureReliable inAction: Set 4/3/2 different PbcIn.Wheelspeeds.Expected Behaviour: RefSpeed is the fastes wheelspeedActual Behaviour: Refspeed is the second fastes WheelspeedRequirements: EPBi_Audi_PPE-SwRS_1657EPBi_Audi_PPE-SwRS_1660Please see attachment, Conclusion: <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 HDREstimated Effort : 8hVerifier : E HarderIs 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable

ID: 5464023, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Refspeed calculation at ONE PbcIn.WheelPressureReliability = ePbcWheelPressureNotReliable, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: [harder eduard kbl adby212 (hardere), sep 29, 2021 10:32:48 am cest]<function & control ccb - eha - (29.09.21 - 10:32):closed after task review.[(system user) user for queue manager (scs_queuemanager), sep 28, 2021 11:17:50 am cest]preintegration of 5506274 was successful. a checkpoint has been created on path #/epb#productdevelopment/epbi/08_software#d=iqm_preinteg_audi_ppe_b. checkpoint number is 1.28.3.2.3.2.2.93.[gerz michael kbl adby212 (wyrthm), sep 9, 2021 4:48:29 pm cest]f&c ccb - mg - 09.09.2021 - 16:48task created., Description: Precondition: Pbc Released, set PbcIn.WheelPressurereliabilityFL or FR or RL or RR = ePbcWheelPressureNotReliable and set one PbcIn.WheelPressurereliability after the other to ePbcWheelPressureReliable inAction: Set 4/3/2 different PbcIn.Wheelspeeds.Expected Behaviour: RefSpeed is the fastes wheelspeedActual Behaviour: Refspeed is the second fastes WheelspeedRequirements: EPBi_Audi_PPE-SwRS_1657EPBi_Audi_PPE-SwRS_1660Please see attachment, Conclusion: <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 HDREstimated Effort : 8hVerifier : E HarderIs 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., LogType: Other

Provide the details for the given input

ID: 5464033

ID: 5464033, Summary: [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., State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/EBB, Company: VW, Team: 3361602, Classification: Incident / Problem / Bug, Comments: , Description: 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)., Conclusion: This topic is already solved with CR 6048238. The CR can be rejected., LogType: Other

Provide the details for the given ID

Summary: [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.

ID: 5464033, Summary: [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., State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/EBB, Company: VW, Team: 3361602, Classification: Incident / Problem / Bug, Comments: , Description: 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)., Conclusion: This topic is already solved with CR 6048238. The CR can be rejected., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: VW, Summary: [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.

ID: 5464033, Summary: [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., State: ALM_Closed, Project: /BRK/Customer/VW/ID_Buzz/EBB, Company: VW, Team: 3361602, Classification: Incident / Problem / Bug, Comments: , Description: 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)., Conclusion: This topic is already solved with CR 6048238. The CR can be rejected., LogType: Other

Provide the details for the given input

ID: 5464061

ID: 5464061, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditions with and without HPSAction: Perform Rollaway reclamp with speed several times with and without HPSExpected Behaviour:Only two reclamps allowed.Actual Behaviour: MORE Reclamps are performedRequirements:EPBi_Audi_PPE-SwRS_3067EPBi_Audi_PPE-SwRS_3068EPBi-Audi-PPE-VC_834 > 2 ReclampsEPBi-Audi-PPE-VC_836 > 2 Reclamps Further infromation:, Conclusion: Task to update VC from 2 reclamps to 4 reclamps, LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps

ID: 5464061, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditions with and without HPSAction: Perform Rollaway reclamp with speed several times with and without HPSExpected Behaviour:Only two reclamps allowed.Actual Behaviour: MORE Reclamps are performedRequirements:EPBi_Audi_PPE-SwRS_3067EPBi_Audi_PPE-SwRS_3068EPBi-Audi-PPE-VC_834 > 2 ReclampsEPBi-Audi-PPE-VC_836 > 2 Reclamps Further infromation:, Conclusion: Task to update VC from 2 reclamps to 4 reclamps, LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps

ID: 5464061, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of maximum number of reclamps, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditions with and without HPSAction: Perform Rollaway reclamp with speed several times with and without HPSExpected Behaviour:Only two reclamps allowed.Actual Behaviour: MORE Reclamps are performedRequirements:EPBi_Audi_PPE-SwRS_3067EPBi_Audi_PPE-SwRS_3068EPBi-Audi-PPE-VC_834 > 2 ReclampsEPBi-Audi-PPE-VC_836 > 2 Reclamps Further infromation:, Conclusion: Task to update VC from 2 reclamps to 4 reclamps, LogType: Other

Provide the details for the given input

ID: 5464071

ID: 5464071, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditionsAction: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RARExpected Behaviour: None defect side performs RARActual Behaviour:Both side do not perform RARFurther inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.Please see attachment, Conclusion: [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 creationAssign to (Owner):M.GornisiewiczStart Date (Planned Start Date):21.01.2022Duration (Remaining & Planned Effort):1hFix Date (Planned Prepared Date):21.01.2022Verify 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 ReleaseNo 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., LogType: Other

Provide the details for the given ID

Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR

ID: 5464071, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditionsAction: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RARExpected Behaviour: None defect side performs RARActual Behaviour:Both side do not perform RARFurther inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.Please see attachment, Conclusion: [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 creationAssign to (Owner):M.GornisiewiczStart Date (Planned Start Date):21.01.2022Duration (Remaining & Planned Effort):1hFix Date (Planned Prepared Date):21.01.2022Verify 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 ReleaseNo 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., LogType: Other

Provide the details for the given Summary

LogType: Other, Company: CustomerDevelopment, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR

ID: 5464071, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of Reclamp with Hostavailablity at Only release before RAR, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: , Description: Precondition: RAR conditionsAction: Set PbcInHosavailabilityLeft Or Right = ePbcAvailabilityRelease, then perform RARExpected Behaviour: None defect side performs RARActual Behaviour:Both side do not perform RARFurther inofrmation: If PbcInHosavailabilityLeft Or Right = ePbcAvailabilityNone it works as expected.Please see attachment, Conclusion: [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 creationAssign to (Owner):M.GornisiewiczStart Date (Planned Start Date):21.01.2022Duration (Remaining & Planned Effort):1hFix Date (Planned Prepared Date):21.01.2022Verify 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 ReleaseNo 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., LogType: Other

Provide the details for the given input

ID: 5464080

ID: 5464080, Summary: [Issue] of PBC_X01_501_00p - SiL Test - Issue of ParkSupportRequest at HTR, State: ALM_Closed, Project: /EPB/CustomerDevelopment/Audi/PPE, Company: CustomerDevelopment, Team: , Classification: Incident / Problem / Bug, Comments: [zimmer florian kbl adby212 (zimmerf1), jan 19, 2022 9:49:38 am cet]function & control ccb - fzi - 19.01.22 - 09:49:cr has been canceled according to investigation result., Description: Precondition: Set precondition for HTR at 500 Deg.Action: Call PbcCyclic until the first HTR stepExpected Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportRequested for 2 PbcCyclicActual Behaviour: PbcOut.ParkSupportRequest = ePbcParkSupportNotRequestedRequirements: EPBi_Audi_PPE-SwRS_2342Further information: Maybe there is a issue on requirement side.Please see attachment, Conclusion: <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): mediumProposal of next steps (incl. effort / h and verifier):- Reject the CRIs 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, LogType: Other

Provide the details for the given ID