1. New model code added in BEV

1. BEV binary with disabling HPC_C SW version check at the under body station. - Done2. Took a trial on the vehicle level, working fine3. FRONT_ZONE cal file flashing enabled in OFFLINE_FLASHING_API4. Took a trial on the vehicle level, working fine.

1. Vishal sent log regarding MID_ZONE module name error shown on summery screen2. Logs are analysed3. Error corrected in the MID_ZONE state machine VAT.

In MAHINDRA, compliance-related activity is done.

1. the read application software id service in COCKPIT_FLASHING_STATION, as well as already present in UB_TWO_FLASHING_STATION.2. Took trails on the vehicle level

removed - W62AC71, W62AC51 from HUD and AP ecu’s.

1. new model code has been updated in the BEV database2. one model code was added for sunshade calibration

1. New model code added in option type2. VCU 5 seconds delay added before extended session in VCU flashing state machine

1. Trails and errors were done for the VIN compare feature added in VCU. Working fine on the BEV model.

New model code added in BEV

1. Help Adhav with error analysis and troubleshooting of MRV DL32. Services added in SVS for Scorpio n project. CONFIGURABLEPARAMETERSVALUES – write services. SVS_VARIANTCODE – write services.3. EOL log analysed and sent rootcause

1. SRS start com, config added SRS clear code disabled2. Front zone hard reset added3. Option mode added for Rally M110 and W6104. Services added in MiD ZONE

1. The WLC_REAR model code has been removed. AMP model code checked in the database2. Tested the binary on-line working fine

Front Zone hard reset at UB station. SRS parametrization added at UB2 station. Option mode for new model code.

1. HPC_C NRC 37 retry attempt changes trails done on ZIG level through VCU.

1. HPC_C retry for NRC 37 updated state machine. 

1. Unwanted HPC_C services searched and removed from all stations2. HPC_C services are updated3. CLEAR code and bootstrap triggered CV2X services removed.4. HPC_C DID stations updated

1. Report logic bugs checked. After updating binary in DL3, older version shown on report logic screen and in PBF updated version shown. Report logic glitch shown to tushar.

1. MID_ZONE calibration saw bug, so analysed and found.2. Bug corrected from MID zone and HPC_AP SYN retry attempt reduced to 3 times and waitingtime increased to 3 seconds.

1. All in 11 DL3 runtime, firmware and binary updated from V block.

1. HPC_AP trails took on the vehicle level2. Retry attempt increased 3 to 43. Waiting time decreased from 3 to 2 seconds.

HPC_C_MCM and BOOTSTRAP services disabled from UB_TWO_FLASHING_STATION - Tested on vehicle working fine HPC_C_MCM and BOOTSTRAP services enabled from COCKPIT_FLASHING_STATION. - Tested on vehicle working fine

HPC_AP SYN request working fine in log. HPC_C_MCM and BOOTSTRAP services disabled from UB_TWO_FLASHING_STATION and HPC_C_MCM and BOOTSTRAP services enabled from COCKPIT_FLASHING_STATION.

HPCC_MCM services are disabled from COCKPIT_FLASHING_STATION. - Tested on vehicle working fine For HPC_AP SYN retry, I updated the config items. Now it will work, If a SYN ACK does not come, I have added a 3-second wait time as well as 3 retry attempts. - Tested on vehicle working fine

HPCC_MCM services are disabled from COCKPIT_FLASHING_STATION. For HPC_AP SYN retry, I updated the config items. Now it will work, If a SYN ACK does not come, I have added a 3-second wait time as well as 3 retry attempts.

1. HPC_C_MCM service addition in OFFLINE_FLASHING_STATION2. FRONT_ZONE service addition in OFFLINE_FLASHING_STATION3. Took a trail on vehicle level

1. HPC_AP for SYN timeout trails took on vehicle level2. Logs analysed and FB updated.

1. With new runtime, binary and firmware HPC_AP SYN ACK trail took on vehicle level2. Logs analysed.3. FB updated

1. HPC_AP TCP_IP level trails took

1. IEB_ITPMS routine test logs analysed2. Corrected the issue, took trails

HPC_C log analysed and sent mail to EOL team

New IEB routine created and added in FINAL_CALIBRATION_STATION

1. New option type or model addition in M310 and M1102. BMS flashing enabled in UB_TWO_FLASHING_STATION

1. Daily Offline line Cockpit and ZIG flashing failed in morning first attempt. Logs analyse.

1. VCI flashing analysis was done through PBF logs.2. Trace folder not available so not found which state error was trigger.

1. MCU_REAR module flashing enabled from vat side.2. New service addition in HPC_C3. MCU_REAR flashing trail done on vehicle level.

1. BMS state machine checked, analyse fault code set.2. Corrected state machine fault code3. Binary generated and took trials.

1. More error codes added in the FRONT ZONE and 2. More error codes added in the MID ZONE state machines.3. Trials taken4. BEV new model code added in broadcaste decode

FRONT_ZONE state machine updated for error handling

1. MRV New DL3 configured remotely.2. Tested on vehicle working fine.

HPCC 1. HPC_C_APPLICATION_SOFTWARE_ID 2. HPC_C_BOOT_SOFTWARE_ID READ FRONTZONE FRONT_ZONE_TPMS_FRAME_CONFIGURATION WRITE HPCAP HPC_AP_DVR_SETTING WRITE Services added in BEV database. Testing done.

HPC_AP Multiple tester present stop at UB2 station. HPC_AP Same sequence required like UB2 at final line calibration station. HPC_AP two extra read service VIN and 220A should be disable at final line calibration station.

1. HPC_AP open point discussion,2. HPC_AP log analysis3. HPC_AP ECR discussion

Testing done on below points, working fine all points Global Diagnostic request update to put on HOLD As currently HPC_AP does not supportUDS retry & Tester Present time to be reduced to 1.5 secsSequence Update: Its already implemented from Binary Version 5.6.41.95.73(Logs need to share to COE for their confirmation) for HPC_APupdated front zone service in REPAIR_FLASHING_STATION.

UDS retry & Tester Present time to be reduced to 1.5 secsGlobal Diagnostic request update to put on HOLD As currently HPC_AP does not supportSequence Update: Its already implemented from Binary Version for HPC_APUpdated front zone service in REPAIR_FLASHING_STATION.

HPC_AP meeting done with Long hon team, MAHINDRA HPC_AP team and EOL team.

1. 7DF testing done.

1. For improvement purposes, I am sending one binary for 7DF,2.  unable 7DF command for BMS and HPC_AP. Need to check how its performing,3. I enable 7DF command for BMS – 36 4, HPCC 36 2C and HPC_AP 36 2C, Functional 7DF – 36 4. MAHINDRA_5.6.41.95.71.124. I added the HPC_AP config item in CANFD. MAHINDRA_5.6.41.95.71.13 POST_FLASH_CMD added after HPC_AP clear code, HPC_AP test I moved to end before HPC_V hard reset in UB_TWO_FLASHING_STATION HPC_AP services shuffled. 7DF command triggered.

1. 7DF command testing and validation for HPC_AP

1. 7DF command implementation and log analysis

 1.Tester preset should be sent to keep session active every 2 seconds. - Done2. If for a particular diagnostic service request there is no response from ECU, then UDS retry should be done after 5 seconds. - Done3. Testing done on vehicle leve

FRONT_ZONE logs checked from UB-Two station and corrected issue.

1: FRONT_ZONE : FRONT_ZONE_FEATURE_CODE This existing write services has to be removed from cockpit and to be added at UB2 station. 2. FRONT_ZONE : FRONT_ZONE_FEATURE_CODE_SS_DISABLE This new service to be added at cockpit station in FZ module with same 10 sec delay architecture.  - New Test created for config in UB_TWO_STATION3. CRM: CRM_SERIAL_NUMBER this read service has to be added in CRM  4. FRM: FRM_SERIAL_NUMBER this read service has to be added in CRM

In BEV HPCC_MCM_bootstrap trigger service added in COCKPIT_ECU_FLASHING_STATION.

1. HPC_AP 3 sec. delay within the service trail taken,2. PCAP file path integrated in all 10 DL3 in the V block3. Auto negotiation and static negotiation trails took place in UB_TWO_STATION and the OFFLINE Area4. For FIN_ACK, trials took place and logs were sent to Tushar5. DL3 checked in OFFLINE_AREA WIFI issue. There will be an issue with the WIFI card, which needs to be replaced.

1. NAM condition updated in UB_TWO_FLASHING_STATION2. BMS condition checked.3. Testing done.

1. With the existing database, DoIP and CANFD protocol merging trails.

1. DL3 3032 configured and tested

1. DoIP code merge in Existing ICE vehicles. Testing done.

For W616 i checked yesterday binary. Took trails but error comes "NO VCI COMMUNICATION".

Ambient LIGHT calibration test disabled

Given binary I am created for trial purposes. With the new protocol, ICE flashing is happening or not. Please paste both binaries into local share drive.  The BMS CANFD module was added to the initialisation module and disabled. The calibration was MAHINDRA_5.6.41.57.1.1. Given binary I am running in S block for testing purposes. The BMS CANFD START COM test was enabled to the REPAIR_FLASHING_API rest of all ICE modules were disabled. The calibration was MAHINDRA_5.6.41.57.1.2. Given binary I am running in V block for testing purposes.

1. As discussed, please reshuffle the test sequence as per COE requirement. WLC_1, WLC_1,CCm and NAM.2. Routing has to be done after hard reset as per COE confirmation3. As per requirement AFTER HPC_V hard reset given delay   MAHINDRA_5.6.41.95.57.1 – 10 Sec. delay added MAHINDRA_5.6.41.95.57.2 – 20 Sec. delay added MAHINDRA_5.6.41.95.57.3 – 30 Sec. delay added4.  As discussed with Dileep sir changes done HPC_V Hard reset shifted at the end WLC_1 added end before HPC_V hard reset in UB_TWO_FLASHING_STATION WLC_1 added end before HPC_V hard reset in FINAL_CALIBRATION_FLASHING_STATION I added static auto-negotiation code also in this binary. So before integrating this binary, Please make sure the latest runtime 2.0.245.0 and the latest firmware 1.2.52 are required. Else all modules will not communicate. I already added in UB_TWO, one DL3 3045.

1. With DoIP runtime 245 took trails in ICE vehicles. 2. Logs sent to tushar

Calibration: MAHINDRA_5.6.41.95.54Tester present in UB2 station make in series. Mid Zonal disable in PACK - B Front Zone DID sequence change. HPC_C_IS application ID sequence change. Calibration: MAHINDRA_5.6.41.95.551.HPC_V hard reset add in Ub2 station 2. WLC1 and CCM keep at end

For FRONT_ZONE after NRC rest services not executed - CorrectedNew service added in BMS, VCU and FRONT_ZONE

Gate pass renewal procedure done

1. HPC_AP log analysed2. Ethernet link up logs analysed and prepared excel sheet sent to M&M team3. EPS SAS calibration disabled

With new firmware for static negotiation on UB_TWO station 10 trails and OFFLINE_STATION 10 trails taken.

1. HPCC test modified. A new test was created for 16 services and added before the HPCC Bootstrap test.2. Only the feature code of HPCC was added before HPCC bootstrap.3. Yesterday's Log was analysed for HPC_V link-up. created an Excel report and submitted it to Tushar.

1. New firmware for auto-negotiation trails taken.2. New binary trails taken.

I added HPC_C services in UB_TWO_FLASHING_STATION I added fault code to all calibration tests.

FB 24515FB 28555FB 28559FB 28562 

A new model code was added to the broadcast decode. SRS hard reset added in UB_TWO_FLASHING_STATIONTesting done

1. With new runtime S block XUV 700 trails took. Working fine. One config item need to add in database for CANFD support. With all test trails are pending. 

supporting in logs analysis activities for this project.

With new runtime testing done in T block. Some bugs found. Need to clear

New option mod added in VAT database for M110 and M310

provided support in merging the doip branch to main mssi branch

Regarding HPC_AP open points meeting done

1. PCAP path add in ub2 and final station 2. vci retry count increased in final line station 3. new runtime in v block how its behaviour logs collected trails took

For VCU flashing after security and before programming session 5 Sec. delay added in state machine

1. ATP sign-off sheet created and sent to MAHINDRA2. HPC_AP log analysed and sent mail to MAHINDRA3. SBRM module log analysed sent mail to Vikash4. VCU log analysed sent mail to Sagar

1. NRC retry config item updated in binary for HPC_C. Only for testing purposes. Testing done2. Crashing issue testing done. Found root cause.

analize nrc retry issue of Mahindra and find the root cause.

1. On DoIP 2.0.245.0 runtime took a trail on vehicle level 21 trails took but no crash reported.

1. HPC_AP and HPC_AD tests added at the end in REPAIR_FLASHING_STATION 2. NRC retry config item added for HPC_C 3. VCI_COMMUNICATION pop name changed

worked on crashig issue for DoIP project.

1. With new runtime 2.0.244.0 crashing issue was checked. 21 trails took but there is no crashing issue observed in the test sequence.2. For 15 seconds Ethernet link up check code added in VCICONFIG file. took a trail on vehicle level.3. New runtime and for ethernet link-up check code added in UB_2 station. 

1. Yesterday's log was analysed and sent as an excel sheet to the M&M R&D team. Regarding the HPC_V link-up issue.

1. HPC_V trails took on line, 30 trails took to understand HPC_V vci communication issue2. NO VCI communication error message changed in VAT

simulating crashing issue in vehicle and got the route cause.we find out that in routing function it is crashing so provided logs and trace to alex for further investigation.

Runtime crash test with Gaurav and Alex.

1. OCDC, MCU_REAR, BMS variant code removed.2. In repair flashing for HPC_C session and security added.3. TEST_ON_VEHILCE =Y or N no need to change for any station except VCU_FLASHING_STATION

Modified OBD cable, added register and pulled Vbat to Pin8 of OBD cable.

1. For PCAP send to other location. With gaurav DLL took trail2. Runtime crash took trail with HPC_V and HPC_AP only.

added SRS hard reset in FINAL_CALIBRATION_STATION. Testing done

1. DL3 3377 configured tested and handover to Line person on front of sagar2. DL3 3050 reimage and configured. Tested and handover to CME team.3. Gaurav DLL trail taken for PCAP send to share location. Logs shared with him.

worked on .pcap file save to servert task.and supporting pravin for TVS Vitesco ICP security. 

AMP test sequence rearranged in COCKPIT_ECU_FLASHING_STATION. 79 KWA BMS cal flashing enabled in UB2_FLASHING_STATIONTesting done

fixed bug for NRC retry ECR and make installer for testing.

1. With new firmware 1.2.50 and new binary updation took trails on cockpit level.2. 30 with turn off key on CANFD trails taken. With exit button clicked and with runtime close hybrid trails took.3. 10 with turn on key trails took on vehicle level - with click EXIT button4. 10 with turn on key trails took on vehicle level - with click EXIT button and after 2 cycle runtime closed.

Support for Mahindra Diop project for 24V in ethernet activation line issue.

worked on NRC retry ECR and completed the task.

24 V supply go to pin 8 so mahindra ask to understood why 24V supply gone need 12V protocol. Testing we are doing.

Runtime Crashing trails 1. With Repair flashing 4 trails done - On 4th trail runtime crashed2. With repair flashing turn off vehicle - No communication with VCI error occured3. Removed HPC_AD, FRM, CRM and HPCC - 4th trails crashed on HPC_AP start comm 

fixed review comments given by alex for NRC retry code.

1. 100 trails done from CANFD modules no crash occurred2. With 25 modules 7 trails done crashed on DoIP3. With 25 modules Removed HPC_AP config, clear code and hard reset 5 trails done crash occured4. Removed HPC_AP module and rest kept as it is 45 trails done. Crash not occured.

1. HPC_C clear code disabled from COCKPIT_ECU_FLASHING and REPAIR_FLASHING_STATION2. Removed 7DF command in sequence of BMSRemoved Preflash command from BMS flashing

 1. New runtime installed "2.0.242.0" 2.  Below mentioned keyword was added in the station.ini file[BINARY_TRACE]TraceON=0 CANFD: We run only two modules (SRS and MID_ZONAL).1. "Start with CAN FD testing: First reproduce the crash running CAN FD station only. No need to restart runtime. Only run until crash happened and just notice how many runs it took." --> When we do normal trails(Open Runtime-->Scan VIN/MODEL-->TS Started(here runtime is crashing in TS Started) -->RUNTIME IS CRASHED. A pop-up appears, and while clicking on the popup window, the runtime will close. Failed on 1st Attempt. Video attached, 2. Reproduce step 1, but every time turn the key off at the results screens:start runtime - floating - logo - testing - display results - turn key off - press exit - floating logo - turn the key on - testing - display results - turn key off ... repeat until crash or not.--> When we do key on-off trails(Open Runtime-->Scan VIN/MODEL-->TS Started(here runtime is crashing in TS Started) -->RUNTIME IS CRASHED. A pop-up appears, and while clicking on the popup window, the runtime will close. Failed on 1st Attempt. DoIP: All 24 modules 1. "DOIP testing  First reproduce the crash running DOIP station only. No need to restart runtime. Only run until crash happened and just notice how many runs it took." start runtime - floating - logo - testing - display results  - press exit - floating logo - testing - display results ... repeat until crash or not.--> Crashed on 5th trail 2. "5. Reproduce step 4, but every time turn the key off at the results screens:start runtime - floating - logo - testing - display results - turn key off - press exit - floating logo - turn the key on - testing - display results - turn key off ... repeat until crash or not."--> Crashed on 3rd trail Observations: 1. A new pop-up window appeared, but after clicking OK test logiq did not crash but it was redirected to a floating logo screen.

BMS read service added in different test and delay time added. Increased 3 Sec. to 4 Sec. delay between session and security in BMS flashing.New services added,  HPC_C_MCM_ECALL_SOS HPC_C_MCM_ASK_MAHINDRAA

HPC_AP config added in FINAL_CALIBRATION_STATION. If no response from module from HPC_AP, second request triggered after 1.5 Sec.   Calibration: MAHINDRA_5.6.41.95.34

Alex given task for crashing done. CANFD:1. When we do normal trails(Open Runtime-->Scan VIN/MODEL-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Scan VIN/MODEL-->TS Started for 2nd vehicle--)-->IN THIS CASE RUNTIME IS NOT CRASHED.2.  When we do another trail((Open Runtime-->Scan VIN/MODEL-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Scan VIN/MODEL for 2nd vehicle-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Press Runtime Close Button--->CRASHED)-->IN THIS CASE RUNTIME CRASH OBSERVED AT 2ND ATTEMPT. Screenshot attached. DoIP:4. DOIP testing  First reproduce the crash running DOIP station only. No need to restart runtime. Only run until crash happened and just notice how many runs it took. if no crash happened  then stop (no more testing).if crash is happened to to step 5. -->Runtime got crashed at 5th trail, that to pop up appeared while executing test sequence. Screenshot attached. 5. Reproduce step 4, but every time turn the key off at the results screens:start runtime - floating - logo - testing - display results - turn key off - press exit - floating logo - turn the key on - testing - display results - turn key off ... repeat until crash or not. --> Followed mentioned sequence and took trails, it also crashed at 5th trail with same popup appeared while executing test sequence. same screenshot as like step 4.**Extra Sequence 1 as per request for DoIP,(Open Runtime-->Scan VIN/MODEL-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Press Runtime Close Button)---> Its not crashing if we follow above sequence. took 8 trails. **Extra Sequence 2 as per request for DoIP,(Open Runtime-->Scan VIN/MODEL-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Scan VIN/MODEL for 2nd vehicle-->TS Started-->Summary Screen Appeared-->Press Exit Button-->Floating logo re-appeared-->Press Runtime Close Button----->NOT CRASHED)-->Its not crashing if we follow above sequence. took 4 trails.

Worked on Below FBs for Mahindra,FB 24515: ECR: Design FinalizationFB 24513: ECR: Implementation and Design FinalizationFB 28447: ECR: Bug Fixing , Root Cause Analysis & TrailsFB 28446: Bug: Root Cause Analysis

implementing code for NRC retry ECR.

115 Trails taken as alex suggested.start runtime - floating - logo - testing - display results - turn key off - press exit - floating logo - turn the key on - testing - display results - turn key off ... repeat until crash or not.

MID_ZONE hard reset test added in FINAL_CALIBRATION_STATION.NRC 37 when come from module side, message will appear on summery “Security ACCESS Failed”.

-->Took 20 trials on a vehicle with HPCV(GW) ECU routing activation and Start Comm test only.-->Out of 20, 10 trails took by giving Key On Off Reset to the vehicle after each run But kept Runtime always open(No close and open)-->Remaining 10 trails taken without any Key On Off Reset to the vehicle and with Runtime always in open condition.-->Took 20 trails on a vehicle with SRS(CANFD) ECU Start Comm test only.-->Out of 20, 10 trails took by giving Key On Off Reset to the vehicle after each run But kept Runtime always open(No close and open)-->Remaining 10 trails taken without any Key On Off Reset to the vehicle and with Runtime always in open condition.

Today's task,10 With toggle trials taken for crashing issue - Ifreezeenable=0 disable⁠10 Without toggle trials taken for crashing issue - Ifreezeenable=0 disable⁠3 With toggle trials taken for crashing issue - Ifreezeenable=0 Enable⁠5 Without toggle trials taken for crashing issue - Ifreezeenable=0 Enable3 CAN CANFD with toggle trails taken for crash issue - Ifreezeenable=0 Enable

Trails done - VAT changes DoneAll unwanted test and test phases were removed from all stations.All tests are kept in series in REPAIR_FLASHING_STATION.In UB_2_FLASHING_STATION Before HPC_AP routing activation, added 1 sec. delay.BMS flashing enabledNew services added in old databaseFB 28518 updated

POWER_SEAT_CALIBRATION test disabled from FINAL_CALIBRATION_STATION. Binary trails takenAll unwanted stations and tests are removed in VAT.

New runtime 2.0.241.0 and Firmware 1.2.48 integrated in all 10 DL3.HPC_AP unable to communicate with mod log found. FB updated.All station tests are optimised from the VAT side. BMS_FLASHING disabled from UB_2_station, binary generated and trails took on vehicle level

With the new runtime 2.0.241.0 took trails with all stations.Logs analyzed and FB assigned to Dustin.VAT dongle license renewal FB created.

HPC_C new test sequences created for NRC 22 and taking trailsWith new DLL trails tookFB updated 28518, 28446 and 28447

FB raised for runtime crash"Vehicle data not found" issue checked and sent root cause to Mahindra team

New runtime, firmware and DLL installed in 2 DL3s. Trails took on vehicle level.One DL3 was repaired in the V block.Yesterday's binary trails took on the vehicle level.For MAHINDRA VAT dongle and Report logic license renewal - FB raised.

DoIP Changes:New EPS calibration added in FINAL_CALIBRATION_STATIONHPC_V hard reset disabled from FINAL_CALIBRATION_STATION and UB_TWO_FLASHING_STATIONHUD test updated in COCKPIT_ECU_FLASHING_STATION

Help to Gaurav for online debugging

- provide support to dustin for .pcap log file issue.- find the route cause now he will add a log file which contain raw data.- it is helpful to resolve the issue.

VATBIN updation⁠Added HPC_V HARD RESET in UB_TWO_FLASHING_STATION and FINAL_CALIBRATION_FLASHING_STATION at the end.⁠Added ambient light calibration test 5 times.⁠A one-second delay is added after each ambient light calibration test.Took trails on vehicle level

For the PBF issue Gaurav sent a new DLL and took trailsNew runtime and DLL updated in all OFFLINE area DL3'sSupport to Gaurav for debug runtime

After 78 NRC responses 4 seconds delay was added in all module configurations.FRM and CRM are kept in series in UB_TWO_FLASHING_STATION.HPC_AP, FRM, CRM test phase shuffled in UB_TWO_FLASHING_STATION.BMS flashing is disabled in UB_TWO_FLASHING_STATION for testing and trial purposes only. 

3E 80 Tester present checked is it suspend or not? - Working fine.PCAP file logging issue FB updated.Enable to communicate with HPC_AP module on 1st attempt - FB updated.VATBIN tracker update sent to Abhishek and team.The Ethernet connection not working in the OFFLINE area T block. Found root cause and assigned to MAHINDRA TCF

Bug fix of doip and canfd logging issue.also provide temporary dll to log in .pbf.provide support to dustin for .pcap issue.

VAT related changes done - In this binary I removed HPC_AP routing, tester present and config duplicate test from UB_TWO_FLASHING_STATIONICC services ordering has been re-shuffled in UB_TWO_FLASHING_STATIONTook trails on vehicle level - working fine

With runtime 2.0.240.0 taken trails on vehicle level Found issue in PBF - Gaurav sent DLL, and took trails on the vehicle level after the PBF log issue was solved - Failed to generate PBF link traffic updated FBPCAP file checked when HEX file enabled - Failed to generate PCAP updated FBHPC_AP append response from the module, runtime does not consider module response- Solved updated FB.Crashing issue still observed

- finding rout cause for canfd and doip logs.- analysis of crashing issue.

The HPC_AP VIN Readback service was removed from the configuration test and added to the HPC_AP_SPL_CONFIG test.HPC_AP VIN read back test added at the end in UB_TWO flashing station and FINAL_CALIBRATION_STATIONHPC_AP Hard reset test added after clear codeICC hard reset test disabled

The new runtime sent by Dustin 2.0.2039.0 for the HPC_AP combined response issue took trails and Fogbugz updatedFor double logging data in the DoIP module Gaurav sent by DLL - took trails and mail sent to Abhishek and the teamHPC_AP routing activation failed on the first attempt took trails and log updated in FB The PCAP log was not generated properly when HPC_AP (Node) routing failed, FB was updated and assigned to Dustin. 

New Runtime installed in all DL3

1. I updated the CCM TESTER PRESENT Sequence in UB_TWO_FLASHING_STATION2. For a retry attempt a 4.5-second waiting time is added, If the response does not come AFTER 78 NRC from the module in CRM.3. For a retry attempt a 4.5-second waiting time is added, If the response does not come AFTER 78 NRC from the module in HPC_C.4. new background test for 7DF_Disabled. 5. ICC hard reset test seqance updated

Runtime Crashing Issue(Older & Original Upon Exiting a Test Sequence)

FB 28478

1. HUD test sequence change in COCKPIT_ECU_FLASHING_STATION2. HPC_AP service updated3. enabled HPC_V_ROUTINE, HPC_AP Routine, HPC_V_TP, HPC_AP_TP, HPC_AP CONFIG in NODE_TESTING station

1. CCM service sequence updated.2. CRM waiting time after 78, increased from 4 Sec. to 5 Sec.3. HPC_AP_APA_SOFTWARE_READBACK service added in a separate test in FINAL_CALIBRATION_STATION.4. HPC_AP duplicate Tester present, config and clear code test deleted in UB_TWO_FLASHING_STATION5. HPC_AP Tester present, config and clear code test enabled in FINAL_CALIBRATION_STATION6. BMS flashing is disabled, and service time increases from 1500 milliseconds to 2000 milliseconds.a. Calibration: MAHINDRA_5.6.41.95.1.17. BMS flashing is enabled, and service time increases from 1500 milliseconds to 2000 milliseconds.8. HPC_AP Tester present, configuration and Clear code test again added after FRM and CRM configa. Calibration: MAHINDRA_5.6.41.95.19. At cockpit station: AMP ECU feature code write service to be on top and application F181 service to be put at the last10. At UB 2 station: HPC_AP all activities has to be completed 1st start from routing till clear DTC cycle and rest other sequence as it is has to be performed11. HPC_AP timing between 2 services to be updated from 1 to 1.5 sec12. I enabled power seat calibration.

1. HPC_V_A53 timing parameters increase from 1 sec. to 1.5 sec2. HPC_C After 78 responses were received from the module, I increased time from 4 sec. to 5 sec3. I disabled the HPC_C clear code in UB_TWO_FLASHING_STATION.4. Took a trail on vehicle level and offline area

1) Delay between 2 request timing to keep 1 sec instead of 2 sec configured currently for all ECUs2) For clear DTC request max 3 retry to go in case of no response from module for request(max 3 sec), currently in attached PBF from todays logs its taking each ECUs more than 20sec3) Similarly for module reset(ICC & HPC_C) in case no response application wait time is more than 60sec that also has to be restricted to 3 attempts(max 3 sec)4) There were 2 vehicles(PBF attached) where CCM write service/complete sequence not completed where more than 60 sec time taken, this kind of failure also has to be looked. Refer below snap where even after response from module tester sending requests.5) I disabled AMP in UB_TWO_FLASHING_STATION. 6) Also, previous binary I disabled HPC_AP in FINAL_CALIBRATION_STATION.7) Vehicle level trail taken

1. POWER_SEAT calibration enabled in series for FINAL_CALIBRATION_STATION.2. POWER_SEAT calibration enabled in parallel for FINAL_CALIBRATION_STATION.3. Took a trail on vehicle level4. HPC_AP 5 vehicle trail taken with UB_TWO_STATION without BMS flashing

1. The Binary is generated for trial purposes to check HPC_AP on the first attempt to determine why the channel is not open for analysis.2. Added new services in MID_ZONE test3. A new Power seat routine test is created and added in FINAL_CALIBRATION_FLASHING_STATION but for the time being it’s disabled.

1. With the TPMS test sequence updating, 22 NRC comes.2. I will take a trial for TPMS 3. HPC_AP have a readback issue finding the root cause 4. After some service updation taking the trail for HPC_AP5. DL3 3030 has a WiFi card issue, that needs to be changed.6. A new binary needs to be created, Enable only for single flashing- Need to check whether PCAP is logging or not. It's not logging.

1. With new PCAP firmware took a trail2. and analyse it's work properly but for flashing station PCAP not capturing. Report sent on FB

1. Ambient and POT calibration routine sequence updated as we discussed2. 7DF command enabled(Disabled in 19 Version) for BMS and hard reset command added for ICC.3. I updated routine commands for start POT cal and start ambient LED routine4. Ambient light routine bug corrected.

1. ATP sign-off sheet prepared2. For the 59 KWA battery we started old BMS flashing3. For the 79 KWA battery we started new BMS flashing.4. 7DF command disabled for BMS flashing

1. FRONT_ZONE routine to start the power window trail taken2. New BMS flashing procedure enabled and old one disabled in UB2_STATION3. HPC_V, HPC_AP and HPC_AD routine activation and tester present enabled in NODE_TESTING station4. POT_LEARNING START -> 20 sec delay-> POT_LEARNING STOP -> MID_ZONE calibration updated5. Trail taken on vehicle level6. Added a 1-second delay after security in the MZ_POT_CAL routine7. Added a 1-second delay after security in the MZ_AMBIENT_CAL routine8. New service added in HPC_C9. Vehicle level trail taken

1. I updated and handled the fault code for both MZ_CALIBRATION and For FRONT_ZONE power window calibration routine I was updated.2. In the new BMS flashing procedure, the error is fixed.3. BMS flashing phase length increased,4. FRONT_ZONE Clear the power window routine and Start the power window routine with the new state updated5. I changed the FRONT_ZONE routine to start the power window.

1. E6006 error solved in all stations.2. MID ZONE Error code handled.3. HPC_V and HPC_AP test created in NODE_TESTING.4. The MID ZONE routine for Pack C, which is an applicable condition, is added.5. FRONT_ZONE clear power window status check state bypassed.6. As per the log, the APP+CAL BMS flashing procedure was created and added in UB_2_FLASHING_STATION but for the time being disabled. 7. VEHICLE_CANFD_STATION new BMS flashing procedure added.8. UB_2_Station 12 CAN and CANFD module kept in series.

1. HPC_AP trail taken on UB2 line2. AMP, HUD and HPC_C new station created and canlayzer trail taken

1) CAN/CAN FD  frame logging issue | ZIG ECU's2)  HPCAP LOGGING ISSUE - M&M DoiP

ECRs DiscussionOPL DiscussionATP Updation and Sent for approval along with logs.Bug Analysis and Fixing

Meeting with Mahindra Team for ECRs.

Mahindra raised OPL Points and we have analyzed, tracked and closed the concerns and sent ATP for same on 09122024.

involve in bug fixing activity of DoIP project.

1. For runtime crash trial taken2. HPC_AP added in NODE_TESTING stataion3. BMS flashing log check for stuck error

1. VCU_FLASHING_STATION, ZIG_ECU_FLASHING_STATION and COMPLETE_ZIG_ECU_FLASHING_STATION issues corrected. Now VCU will communicate properly2. With gaurav PCAP DLL trials took3. ZIG level trial took

1. Added DID (Services) in AR HUD,2. Config item 27(Decimal) and 1000(Decimal) added in all module,3. After 78 waiting time 6 seconds reduce to 4 seconds in all module.4. Took a trial on vehicle level

1. DoIP Trails taken with PCAP DLL2. SBW, EPS and ICC module added in node testing station4. Trail taken with Canalyser

1. MID_ZONE new service added2. FRONT_ZONE TPMS issue corrected in FINAL_CALIBRATION_STATION.

added functionality to generate .pcap file for Mahindra DoIP project.

bug fixing of Mahindra Doip project.

fixing bug of mahindra doip project

- finding route cause of crashing issue, try to replicate the issue but issue not replicated.- HPC-AP communication issue but vehicles not available so not able to find the route cause.

1. A new routine is added in FINAL_CALIBRATION_STATION,2. New services added in HPC_AP & MID_ZONE

1. Canalyser log with old runtime2. Canalyser with new runtime3. With new binary UB2 station4. With new binary final config station5. With new binary mspt flashing6. With new binary trail taken on both vehicle M110 and M3107. Fpas and rpas services added in Final config station and mspt station

1. UB2 station – Removed HUD,FZ,MZ,ESCL,VCU,HPC_C (Only config) and SRS.2. Created new MSPT station for Chennai same as final config.3. Added HPC_VA53 in final config.

1. FRONT_ZONE flashing and configuration sequence changed from COCKPIT_ECU_FLASHING_STATION. 2. MCU_REAR auto checksum was added to the flashing procedure.3. Timing parameters change in SBW and EPS4. Service updated in SBW5. Trail taken on cockpit level and vehicle level

1) Timing parameters change in ESCL & FZ similar like WLC & NAM to handle no response error coming randomly.2) A DID(HPC_AP_GEAR_DEBOUNCE) converted from read to write.3) ESCL removal from UB2 flashing station as it is already part of cockpit station.4) Front zonal ECU parametrization sequence pushed after HPC_C to have delay between hex file flashing & parameterization.

1. New service added in HPC_AD2. FRONT_ZONE new services added3. Took a trial on vehicle level

1. Updated fault code condition for FCM and FRM for Z1,2. Config item updated for FCM and FRM for Z1.3. HPC_AP trial taken with CANlayser

1. Now I added config item in NAM same as WLC1 and WLC2 for request trigger delay.2. HPC_V, HPC_AP, CRM and FRM services updated.3. We try to parallel config 21 ECU’s.Station: NODE_TESTINGTEST_ON_VEHICLE=Y

1. HPC_V security added in config test in COCKPIT_ECU_FLASHING_STATION, UB_TWO_FLASHING_STATION, REPAIR_FLASHING_STATION and FINAL_CONFIG_FLASHING_STATION.2. HPC_AP VIN ReadBack service moved to end.

fixed time out issue.

1. WLC1 and WLC2 added config items2. HPC_V_A53 4 services added in COCKPIT_ECU_FLASHING_STATION3. HPC_V_A53 1 service added in FINAL_CALIBRATION_STATION4. HPC_V_A53 routing test sequence changed.5. The same configuration item has also been added for the NAM module

1. HPC_V_A53 trail taken2. HPC_AP trail taken on UB2 station3. HPC_V_A53 test updated in NODE_TESTING and COCKPIT_ECU_FLASHING_STATION4. HPC_V_A53 session and security bypass in this binary

1. In this binary changed the HPC_C sequence. 2. FCM and FRM ECU added in Z1 models. 3. Services added in FCM, FRM, SMARTCORE_IC and EPS.4. New model code added in Z1.5. Condition added in FINAL_FLASHING_API, REPAIR_FLASHING_API

1. Auto checksum logic is added in this binary as well as in runtime.2. With new runtime trial taken3. For RX error message with DLL trial taken4. For HPC_V_A53 with .PCAP trial taken5. Crashing issue check in DL3 for V block

1. MID_ZONE Added new services as mentioned in the below mail2. HPC_C services updated.3. In broadcast decode added a new model in option type.4. The HPC_C Test sequence changed/updated.5. DL3 2433 WIFI card changed

1. COMPLETE_ZIG_ECU_FLASHING_STATION minor bug fixes.2. HPC_AD minor services fix3. AMP trial taken4. FINAL_CONFIG_FLASHING trail taken5. HPC_V_A53 trial taken4. HELP to gaurav to fix issue

1. Printer setting configured in remaining 2 DL32. New runtime updated in all 8 DL33. AMP canlyser log taken4. Security changed in VCU flashing for COMPLETE_ZIG_ECU_FLASHING_STATION5. New HPC_AP sequance change trial taken

1. For point number one NRC 78 continuously comes from the module until 2.5 min. this scenario we saw the first time. We are working on the runtime side to optimize time. If NRC 78 comes until 20 sec. then we will bypass this test and go for the next test. - InProgress2. For point number two “Write test did not complete” – We checked there is a phase length issue we solved now.3. TPMS test shifted after all calibration.4. HPC_V_AP and HPC_V_AD routine activation test updated. Routine Activation HPC_V -> HPC_V_AD -> HPC_AP. TESTER_PRESENT HPC_V -> HPC_V_AD -> FRM HPC_AP CRM5. OPL meeting done

1. 6 DL3 we added printer configuration2. we disabled Routine activation for HPC_V_A53. Bugs corrected.3. Service name corrected.4. Decoding of CANFD & DoIP Modules in Broadcast decode func and test whether perfect protocol its executing.

1. For DL3 printer configuration done2. Took a trial working fine3. HPC_V_A53 changed as node or subnode with IP and without IP with Routine activation without routine activation4. Took a trial on cockpit level5. New runtime 234 integrated in one DL36. AMP took a log and sent to M&M team7. HPC_V_A53 services added in state machine and keep as subnode and static IP added and routine activation enabled

1. FRONT_ZONE special config services test and HEX file flashing disabled in UB_TWO_FLASHING_STATION,2. FRONT_ZONE HEX file flashing enabled in COCKPIT_ECU_FLASHING_STATION,3. In FINAL_CALIBRATION_STATION added FRONT_ZONE special config service test and TPMS with 100ms delay4. HPC_V as a gateway -> routine activation and Tester Present after HPC_V_A53 as a gateway -> routine activation and Tester Present sequence updated in NODE_TESTING station 5. updated the security type for Bolero longer variant. New services also added in VAT

1. HPC_V new as node added 2. FRONT_ZONE flashing disabled from COCKPIT_FLASHING_STATION3. AMP serially added in ZIG_ECU_FLASHING_STATION4. GATE PASS renewal procedure partially done5. PRINT_CONFIG added in STATION.INI

1. disabled HPCC_BOOTSTRAP_STATUS_CHECK command from UB_TWO_FLASHING_STATION, FINAL_CONFIG_FLASHING_STATION and REPAIR_FLASHING_STATION2. HPC_C special test we removed session and security,3. In MID_ZONE software NRC issue solved4. FRONT_ZONE special test we removed session and security, 5. On VCU FLASHING if security is not clear then ECATS 6000 error will not shown “SECURITY_ACCESS_FAILURE” error will shown

1. Vehicle level testing done

1. Delay removed before HPC_C reset.2. New station created FINAL_CONFIG_FLASHING_STATION.3. CLEAR CODE SRS, WLC1, WLC2, NAM disabled4. I disabled FRONT_ZONE flashing in FINAL_CONFIG_FLASHING_STATION.

1. UB_TWO_FLASHING_STATION sequence updated. First, we will do 4 ECU FLASHING (BMS, FRONT_ZONE, MCU_REAR and VCU) and then we will start the 24 modules configuration,2. HPC_C hard reset added in COCKPIT_FLASHING_STATION, UB_TWO_FLASHING_STATION and REPAIR_FLASHING_STATION,3. CRM for feature code ReadBack, 100ms delay added,4. Unused and unwanted stations deleted,5. VSCS methods removed from UB_TWO_FLASHING_STATION, VCU_FLASHING_STATION, COCKPIT_ECU_FLASHING_STATION , ZIG_ECU_FLASHING_STATION and REPAIR_FLASHING_STATION,6. Only for FLASHING and configuration of new station created (BMS, FRONT_ZONE, MCU_REAR and VCU)ECU_HEXFILE_FLASHING_STATION TEST_ON_VEHICLE = Y 7. COCKPIT flashing station ECATS 6000 issue solved8. UB_TWO_FLASHING_STATION-> HPC_C hard reset issue solved -> ECATS 6000 error solved(UNEXPECTED RETURN CODE, UNRECOGNIZED_CODE)9. VCU_FLASHING is disabled in ECU_HEXFILE_FLASHING_STATION because VCU flashing is still not supported on DoIP, it's supported by CAN_FD. Today I took a trial on the vehicle level.

1. UB2 flashing trial taken on vehicle level - MCU_REAR FLASHING, FRONT_ZONE FLASHING with all 24 module config trial taken2. COMPLETE ZIG ECU flashing station -> AMP and VCU not communicated. Root cause found both have register and both are working with different register so its not communicated at a time

1. MCU_REAR flashing trial taken on vehicle level with increase delay and updated state machine for hardcoded checksum2. I added FRONT_ZONE flashing in COCKPIT_ECU_FLASHING_STATION.3. PHASE LENGTH increased for MCU_REAR flashing in UB_TWO_FLASHING_STATION and REPAIR_FLASHING_STATION4. PHASE LENGTH increased for FRONT_ZONE flashing in COCKPIT_ECU_FLASHING_STATION , UB_TWO_FLASHING_STATION and REPAIR_FLASHING_STATION.

1. DL3 3051 LAN driver installed2. DL3 3051 configured from V block3. DL3 3047 have scanning issue, CABLE reconnected after it worked

Client Meeting for OPL PointsIssues identification and Way ahead analysis for its resolution.VAT DB ModificationsInter team meetings with MSSNA for DoIP Implementation issues.VAT DB Updation & assistance in Runtime Debugging and Issues erradication.

Working on DoIP OPL Points.

checking timing issue and also resolving the bugs.

wotking on open bugs and given support for integration of new module HPC-A53.

working on Mahindra DoIP project and resolving the open points(bugs).

internal meeting on Mahindra doip open points.

VAT AuthoringIssues Analysis & DebuggingProject Management

worked on the utility to prove out the MCU checksum calculation logic.implemented the code and provide that to alex, further he will work on the runtime implementation part.

MCU flashing procedure checksum calculation implementation.After all 6 block transfers, we need to calculate checksum of all blocks at one time

1. MCU_REAR flashing procedure updated2. 7DF command issue solved in complete zig flashing station3. FRONT_ZONE flashing procedure implemented in VAT

Trial taken on vehicle level

1. MCU_REAR flashing procedure created2. Services updation did in HPC_C

Give support to gaurav for debugging issue

Took a trial on vehicle level

1. Fault code added in the routine state machine.2. Message updated in all routine state machine

1. IEB all routine timer, fault check and message updated2. IEB routine sequance updated

Took a trail on cockpit level, UB2 station and FINAL_CALIBRATION_Station took a trail on vehicle level

1. In FRONT_ZONE routine 200ms for retry status delay added.2. In FRONT ZONE routine for POWER WINDOW and Active suspension calibration timer and fault code status check state added3. FRONT_ZONE 2 Read services test added in series on UB2 Station and REPAIR_FLASHING_STATION4. HPC_C Bootstrap trigger test added in series on UB2 and REPAIR_FLASHING_STATION5. ZIG_ECU_FLASHING_STATION and COMPLETE_ZIG_ECU_FLASHING_STATION condition corrected

Vehicle level trial taken

1) TPMS DIDs which is now linked to front zone has be part of both station I) UB_TWO_FLASHING_STATION & II) FINAL_CALIBRATION_STAION except offline station where front zone parametrization also getting done.2) IEB routines also to be differentiated as front zone separately as in case any failure in one other calibration can proceed3) DIDs(HPC_C_MCM_BOOTSTRAP_TRIGGER, & HPC_C_MCM_BOOTSTRAP_STATUS) from HPC_C to be executed at UB2 station not at offline stage.4) For any routine in case if result is not coming as success, then timeout, you put max 15 sec. for now, in case any feedback will inform you. - FRONT ZONE done5) Also consider result byte for other than success case like if result says failure, then declare instead of waiting for success response. - FRONT ZONE done6) from Front Zone to be executed at UB2 station not at offline stage FRONT_ZONE_FPAS_SW_VERSION :- DID - 0399, Length - 3, Type - Read FRONT_ZONE_RPAS_SW_VERSION :- DID - 0398, Length - 3, Type – Read

Testing on vehicle level

1.HPC_C_ Services clean up2.Option mode for calibration3.200msec delay to be changed to 100 msec in FZ & MZ write read services.4.100msec delay also to be added in all FZ & MZ calibrations sequence between 2 services

1. Help to gaurav to debug issue

1. HPC_C unwanted 40 services filtered and deleted

1. HPC_C unwanted 40 services filtered and deleted

Took a trial on vehicle level

1. New services added in HPC_C and VCU,2. Complete BEV services verification done,3. FRONT_ZONE and MID_ZONE new special test added in REPAIR_FLASHING_STATION, ZIG_ECU_FLASHING_STATION, COMPLETE_ZIG_ECU_FLASHING_STATION and COCKPIT_ECU_FLASHING_STATION.4. TPMS merged in FRONT_ZONE module,5. MBFM disabled in FINAL_CALIBRATION_STATION. 6. Station: FINAL_CALIBRATION_STATIONTEST_ON_VEHILCE=Y

1. FRONT_ZONE services write after 200 ms - ONLY WRITE or WRITE and READ both2. Service addition in HPC_C3. Station differentiation4. HPC_AP with all 23 modules test

1.added new services in HPC_C. Yesterday’s changes disabled.2. the HPC_C phase length is insufficient to execute all services. So I increased now

1. Took a trail on vehicle level

1. I disabled FRONT ZONE and MID ZONE clear DTC from OFFLINE_FLASHING_STATION and FINAL_FLASHING_STATION.2. HUD and HPCC phase length increased due to the phase time-out issue that occurred on the previous binary.3. Added POST FLASH COMMAND in BMS4. After FRONT_ZONE and MID_ZONE config added 10 Sec. delay5. After 10 Sec. FRONT_ZONE and MID_ZONE Hard reset test added

1. With new firware for HPC_V,HPC_AD,HPC_AP, FRM and CRM took a trail on vehicle level2. FRONT ZONE new routine calibration trail taken3. Runtime crashing issue checked

1. From offline area HPCC phase lenght increased and HUD added serially

Vehicle level trial taken

1. In this binary, we added the FRONT_ZONE routine for Semi-active suspension learningStation: FINAL_CALIBRATION_STATIONTEST_ON_VEHICLE = N2. New model code added3. HPCC test added before BMS FLASHING.Station: FINAL_FLASHING_STATIONTEST_ON_VEHILCE=Y4. For Only VCU FLASHING on CANFD.Station: FINAL_FLASHING_STATIONTEST_ON_VEHILCE=N

1. Firmware updated and tested for HPC_AD and HPC_AP2. Took a trail on JIG level VCU flashing successfully done3. Took a trail on vehicle level for VCU but its inturrupted

1. VCU flashing procedure updated auto check sum added2. New services added in HPCC

Vehicle level took a trail

1. Front Zone routine test created.2. VCU flashing commands updated

Help to gaurav and Tushar to debug on live session

VCU trial taken on vehicle

1. VCU flashing procedure corrected.

1. New DLL .PCAP trail taken for HPC_AD, HPC_AP, FRM,CRM and HPCV

Mahindra DoIP Project bug fixing. 

Mahindra Project DoIP runtime bug fixes.

DoIP Project bug Fixing from runtime side.

DoIP project bug fixing.

I was in Mahindra for crashing and ECU id printing issue, crashing issue not replicated and due to vehicle unviability.

1. With new firmware trail taken on vehicle but no difference found with previous logs

1. VCU flashing procedure updated and recreated2. Front zone new service added

Vehicle level trail taken

1. Today I added 3 new services in FRONT_ZONE,2. CRM 2 services removed,3. BMS Flashing one config file updated4. In first binary, HPC_AD after added HPC_AP5. In second binary, HPC_AP after HPC_AD added. Before trail, please update firmware version DL3

1. Vehicle level trail taken

1. As per mail new HUD services were added to the VAT database.2. HPC_C one service is updated.3. FRONT_ZONE calibration enabled for testing purposes.FINAL_CALIBRATION_FLASHINGTEST_ON_VEHICLE=N4. I have disabled VCU flashing,

1. VCU Flashing procedure written in VAT

Vehicle level trail taken

1. FRM and CRM kept in parallel for Tester Present, Configuration and Clear code2. New services added in HPC_AD, HPC_C and IEB3. FINAL_CALIBRATION_STATION routine we added on DoIP. Collect code disabled. 7 DF command enabled in FINAL_FLASHING_STATION.4. Activated HPC_V routing activation and HPC_V TP5. We merged IEB, and SRS routine with HPC_AP and TPMS in this binary

1. Took a vehicle level trails

1. In this binary I added HPC_AP after TPMS config then we are starting Tester present for IEB and SRS.2. In second binary HPC_C services corrected and HPC_AP clear code test added on last. 5 sec. delay added after config before start IEB SRS Tester present3. ECATS error corrected.4. found issue in configuration of IEB and SRS. Issue solved. Now at a time all IEB, SRS, HPC_AP and SRS will work in FINAL_CALIBRATION_STATION5. Unwanted delay removed.

1. Took a trail on vehicle level for checked HPC_C bootstrap service, IEB collect code test

1. For IEB Collect Code mode changed2. HPC_C phase changed3. HPC_C bootstrap test created4. AMP Clear code test disabled from OFFLINE AREA

1. Support to Gaurav and tushar to debug crashing issue

1. Vehicle level trail done for VAT changes2. OFFLINE cockpit area level trail done for VAT changes

1. Runtime crash issue checked invalid data corrected from API2. For OFFLINE_FLASHING_STATION Clear code test disabled3. COLLECT CODE test corrected. Binary sent.

1. delay 6-6 trail took on cokcpit level2. Took a trail on vehicle level for IEB updated routine

1. Collect code and clear code test added for IEB routine2. With 1 sec. delay and without 1 sec.

1. Hardware part related internal meeting done with Tushar2. Excel sheet prepair for min. required hardware parts, warranty parts.3. VAT binary tracker excel updated

Trail took on vehicle level

1. HPC_AD, HPC_AP, FRM,CRM Clear code test created2. All 23 modules test created.

1. With DLL files took a trail on vehicle level2. HPC_AD, HPC_AP, FRM,CRM trail took on vehicle

1. HPC_AD, HPC_AP, FRM,CRM config state machine created, services added

Remotely support given to Sagar for vehicle level testing

1. Support to tushar and gaurav,2. taking multiple trials with HPC_AD, FRM, CRM and HPC_AP3. TP we got success with HPC_AD,FRM and CRM with station4. TP we got success with HPC_AP on another station

Need dimension of DL3 and Docking Station FB created

1. Trail taken on vehicle

1. FINAL_FLASHING_STATION added BMS flashing with 7DF command.BMS flashing+15 modules on DoIP+5 modules on CANFD2. VEHICLE_CANFD_STATION added BMS flashing with 7DF command.3. FINAL_FLASHING_STATION disabled BMS flashing with 7DF command.VEHICLE_CANFD_STATION enabled BMS flashing without 7DF command.

1. Took a trail on vehicle

1. 15+5 modules changes did. Discovery function enabled and static IP removed, tester IP changed2. BMS flashing added in FINAL_FLASHING_STATION

1. For HPC_AP and HPC_AD trail taken on vehicle, database updated. We took trail as Node or as Subnode but no response from module2. IEB, SRS, EPS, AMP, HUD and HPC_C test set as serail due to unable to capture module respnosne after 78. Trail taken3. Clear code added for IEB, SRS, EPS, AMP, HUD and HPC_C. Trail taken4. Multiple TP removed from HUD and HPC_C trail taken5. FRM and CRM test enabled trial taken but module not responding on request

1. For HPC_AP and HPC_AD database updated. as Node or as Subnode2. IEB, SRS, EPS, AMP, HUD and HPC_C test set as serail due to unable to capture module respnosne after 783. Clear code added for IEB, SRS, EPS, AMP, HUD and HPC_C4. Multiple TP removed from HUD and HPC_C5. FRM and CRM test enabled

1. Trail taken on vehicle

1. HPCV Static IP changed in VAT database2. HPCV discovery test disabled3. The discovery test was Disabled from all stations and for the HPC_V Module static IP was added. Module Config Phase length decreased.4. added Tester present test for HPC_AD and HPC_AP as subnodes. VCI config Phase length updated to 1500. Multiple TP added in HUD and HPC_C.5. Config divided into 3 phases. HPC_AP and HPC_AD static IP added. Routine Activation test created for HPC_AP and HPC_AD.

1. With multiple TP trail done on vehicle2. With Single TP trail done vehicle3. EPS flashing trial done

1. With multiple TP added in all module. binary created2. With Single TP add in all module. binary created

HPC_V trail taken

1. EPS flashing trail taken but updated HPC_V was not available2. Clear code trail taken3. Parallel config 14 module trail taken with Wireshark4. Serail flashing trail taken with Wire shark logs sent to Tushar

1. Clear code test added in OFFLINE and FINAL FLASHING station2. New station created for serial config all module3. 14 module on parallel config updated

1. EPS flashing procedure updated

Testing & ValidationBug finding & its eradication.Client Meetings for technical topics.

1. 2-2 Trail taken with runtime 228 and 2332. EPS flashing taking trail on vehicle- Module is responding NRC system team is checking logs

1. New model code check in MID zone2. EPS flashing updated 

1. Support to gaurav for runtime debugging

1. 220 New services added in HPCC2. 5 new services added in WLC_13. 5 new services added in WLC_24. EPS flashing file imported in VAT.5. EPS flashing sequance checked

1.Front Zone two routine Trail took  on vehicle

1. Front Zone two routine state machine and test created2. EPS Flashing procedure created.

1. IEB routine test taken on vehicle2. 20 module on FINAL_FLASHING_STATION added trail taken on vehicle3. BMS flashing trail 59KW and 79KW taken4. With runtime 228 and 231 4-4 trail taken on vehicle log send to gaurav

1. IEB routine EPB ASSEMBLY updated in state machine2. 20 module on FINAL_FLASHING_STATION added3. BMS flashing procedure updated

1. IEB routine state machine updated new EPB assembly routine trail taken on vehicle2. For Pedal sensor, pressure sensor, G sensor and IEB assembly routine result check routine trail taken on vehicle

1. IEB routine state machine updated new EPB assembly routine added2. For Pedal sensor, pressure sensor, G sensor and IEB assembly routine result check state added in state machine

1. BMS flashing trail taken with MAHINDRa inhouse tool. Logs shared to MAHINDRA team2. HPCV 5.6.1 on trail taken with HPC_AD and HPC_AP but there is issue in HPC_V3. With new runt time trail taken 231. Logs checked and found RX old message issue is solved

1. HPC_AD and HPC_AP Enabled in VAT.

1. BMS flashing Trail took on vehicle

1. BMS flashing procedure updated in VAT

1. Taking trail over vehicle2. Still flashing not happened. NRC come from module

1. BMS flashing procedure corrected

timeout issue route cause finding.

timeout issue route cause finding.

Vehicle level trail taken

1. BMS flashing procedure added in VAT database

1. Help to gaurva for testing and validation

Vehicle level trail taken

1. Corrected HPC_C all services,2. Added new HPC_C services for IC,3. Corrected OFFLINE_FLASHING_STATION, added condition for MID_ZONE module.

1. With new run time 229 took a trail.2. Observation and logs sent to Tushar and Gaurav3. SRS routine state machine took  a trail on vehicle

1. SRS routine state machine updated.

1. Routine SRS took a trail on vehicle level

1. Routine SRS VAT changes done

1. New binary generated. All modules on DoIP. Trail took on vehicle level.2. SRS routine trail took on vehicle 

1. New binary generated. All modules on DoIP.

1. Took  a trail on vehicle level2. New DLL tested for CAN crashing issue3. New DLL tested for SRS routine

1. FINAL_FLASHING_STATION ->               TEST_ON_VEHICLE=Y -> Added Classic CAN module AMP, CCM, ICC and HUD.2. HUD error message corrected from VAT.3. OFFLINE_FLASHING_STATION ->               TEST_ON_VEHICLE=Y -> Added Classic CAN module HUD.4. New model code added in broadcast decode

To Gaurav and Tushar debugging support given

1. Took a trail over vehicle

1. OFFLINE_FLASHING_STATION bugs corrected2. FINAL_CALIBRATION_STATION bugs corrected3. HUD, AMP, ICC VAT error corrected

Vehicle level took a trail

1. OFFLINE_FLASHING_STATION added CAN and CANFD module which abhishek told2. New Routine state machine and test created3. For Specific CAN module over DoIP station updated

Gave support to Tushar and gaurav to debug issue

1. New 113 services added in module

Support to gaurav for preparation DL3

1. Offline station updated as per customer requirements2. New Clear code test added in Final flashing API

1. With 227 runtime and VCI Config changes took a trail on vehicle level

1. With Single Single CAN ECU took a trail on vehicle level2. With new DLL took a trail on vehicle level logs shared to Gaurav3. With new runtime 226 took a trail on vehicle level4. With new DLL took a trail on vehicle level logs shared to gaurav

1. With runtime 224 and 225 took a trail on vehicle level to understand RX_OLD_MESSAGE error. 5-5 trail taken on vehicle level2. Took a trail on cockpit level with 6 pole. HUD all services are working fine. Log shared to Tushar

1. HUD enabled with 7D0 and disbaled with 7D0 binary created2. Single Single CAN module station created and generated binary 

DL3 kept on faulty and good condition docking station SD card files collected and share to bill

Took a trail on vehicle level related new station as well as HUD single test and new services in final flashing station

1. Time sheet filled2. SAS calibration imported in vat database3. TPMS test added in final flashing API4. New station created added TPMS and SAS calibration module5. HUD seperate test created6. New services tested on vehicle level

-Rectify Runtime bug and analysis.

1. Took a trail on cockpit level2. SAS calibration trail took on vehicle level

1. New MBFM module added with services

1. Services added and verified with API

1. DL3 2205 configured

1. Scan format changed as per customer requirement

1. Binary created for Specific module AMP,HUD, ICC and CCM took a trail on vehicle2. Binary created with added config item 7D0 took a trail on vehicle3. OCDC error solve in binary

1. Binary created for Specific module AMP,HUD, ICC and CCM2. Binary created with added config item 7D0

1. 3 DL3 configured from V block

2. Binary created for new station as per client requierment, Took a trail on vehicle level

1. Binary created for new station as per client requierment

1. New services added in All ECU trail taken2. For CANFD module 5 enabled and binary given trail taken3. HPC_C on doip and canfd shared binary trail taken4. HPC_C can shared binary trail taken

1. Internal mahindra open points discussed

1. New services added in All ECU2. For CANFD module 5 enabled and binary given3. HPC_C on doip and canfd shared binary4. HPC_C can shared binary5. Internal mahindra open points discussed

1. All services validated trail taken2. For HPCV 5.4.3 support binary created trail taken

1. All services validated2. For HPCV 5.4.3 support binary created

1. Servcies verified

1. Vehicle level took trails, got Positive response from CAN modules

1. Multiple times TP removed with all CAN module

1. Took a trail on vehicle level2. Seems CAN module sending multiple TP because 7F NRC occured in CAN modules

1. For HPC_V 5.4.3 support to DoIP protocol. So station differentiate with CAN and CANFD modules

1. Took a trail on offline area with DLL file for API glitch2. Took a trail in OFFLINE area with OFFLINE_CANFD_TEST_STATION, VEHICLE_CAN_STATION_VEHICLE_CANFD_STATION

1. New services added in DoIP Database in ALL modules except HPC_AP,HPC_AD

1. Only HPCV with Front zone module on doip trail taken2. HPCV WLC_2 trail taken3. DoIP on HPCV and HUD trail taken on 6 pole connector4. All modules on DoIP in offline area trail taken

1. Waiting for trail on vehicle but vehicle was not available2. Services cross-checked with Abhishek

1. On vehicle level trail taken for CAN module activate on CANFD HPCV2. On Vehicle level trail taken on All modules except CAN on DoIP HPCV3. On Vehicle level trail taken on all modules on CANFD HPCV4. On VEhicle level trail taken on all modules on DoIP HPCV

1. intermittent crash happened with DoIP and Classic CAN took a trail on vehicle2. Summary created with sagar

1. New binary created with HPC_V as CANFD,2. New binary created with DoIP with AMP module

1. 3 new binaries created for VEHICLE_CAN, VEHICLE_CANFD and OFFLINE_CANFD station, trail taken on vehicle level.2. New services added in binary trail taken on vehicle level.

1. 3 new binaries created for VEHICLE_CAN, VEHICLE_CANFD and OFFLINE_CANFD station2. New services added in binary

1. With HUD and ICC API enabled, a new station was created. Binary generated. Took trail.2. HUD and ICC VSCS separate binary generated. Took trail.3. Except ICC and HUD all ECU-enabled binary is generated. Took trail.

1. With HUD and ICC API enabled, new station generated and binary generated2. HUD and ICC VSCS seperate binary generated3. Except ICC and HUD all ECU enabled binary generated

1. API enabled binary created with DoIP CANFD supported took a trail on vehicle level2. API enabled binary created with each classic CAN enabled with HPCV module and took trail on vehicle level3. taking trail on vehicle level Runtime crash issue found in HUD and ICC module

1. API enabled binary created with DoIP CANFD supported2. API enabled binary created with each classic CAN enabled with HPCV module

1. Customer meetings OFFLINE & ONLINE.2. Runtime/VAT & Vehicle Issue Analysis and Troubleshooting.3. New Test Development in VAT.4. Co-ordination with MSSNA for any Runtime Issue Discussion and Followup for till its resolution.5. Testing & Validation.6. Worked on FBs Mentioned below,a. FB 28076b. FB 28004C. FB 27973d. FB 27933e. 27959

1. With API enabled trial taken

1. API-enabled trail taken2. Classic CAN module binary created but it was crashed on vehicle level

1. 2 modules each 5 binary created with VSCS method2. API enabled.3. Classic CAN module binary created.

1. 3E TP repeated from some ECU, so service not executing due to 7F 27 7F. Debug with Tushar and Gaurav

Took trail on vehicle level found issue in HPCV

1. Module name corrected in VSCS method2. Two TEST Enabled for crashing issue check and took trail on vehicle level3. Found issue in API from MAHINDRA side

Took a trail on vehicle level

1. VSCS method added for all test,2. Module name updated

troubleshooting the issue and try to find the route cause.

fixing bugs in runtime code.

DoIP Issue Analysis for GW , Nodes & Sub node modules.Identifying exact root cause of issue and its troubleshooting.Testings, Validations and Log analysis and Confirmation.

1. HPC_AD trail taken with different binaries2. Module name changed3. Web API state machine added4. Unwanted station removed5. Help to gaurav for live debugging

1. HPC_AD trail taken with different binaries2. Module name changed

1. With new binary took trail on vehicle level2. HPC_AD 4 binary test on Zig

1. HPC_AD trail taken,2. Debug with gaurav try to find issue but found some issue in ECU3. DoIP database updated, condition added in offline and vehicle station

1. With new runtime 223, HPC_AD trail taken in offline as well as vehicle level. 2. Ping was not happen Wiring have some issue

1. CAN_FD trail taken with new binary but same result shown2. residence engg. invoice submitted to Vikram

1. Tried to take trail on offline zig for HPC-AD but wiring have issue

1. HPC_AD tried to take a trail but due cable issue communication not happened with IGNIAS Tool2. Wireshark installed in DL3 and tried to take a trail - Successful but data not visible properly3. Residential engineer, Q7 board related, WIFI card related follow up taken from internal team

debugging HPC-AD communication issue.

try to establish communication with HPC-AD module.but due to harness wire issue we are not able to communicate with HPC-AD.

Worked on below items,1. Failure log analysis and findings for further development and fixes.2. Worked on FB 28004. Its in progress.3. Client Meetings.

1. HPC-AD tried to ping through main OBD cable,2. HPC-AD tried to ping through OFFLINE ZIG OBD cable,3. HPC-AD tried to ping through direct cable,

1. HPCV discover function after HPC-AD as node with discovery funtion trail taken2. HPC-AD as static IP added in config item trail taken

1. HPCV diagnostic trail taken on offline bench2. DLL file added for HPC-AD as 3E 803. DLL file added for HPC-AD as default session start

1. HPC-AD as subnode took trail on vehicle level and offline bench2. Canalyser and wireshark through collected log

1. Wiring harness corrected from offline bench setup2. Took trail on offline setup

1. HPCV and HPC-AD trail took on vehicle2. HPCV and HPC-AD trail took on offline bench3. Observed wiring harness issue

1. Tried took trail on vehicle level due to inspection V block was closed2. Report Logiq license renewal from Abhishek laptop

Took DoIP trails with tushar

1) hardcoded 10 01 request in startcom function.2) hardcoded 3E 80 request in startcom function.3) analyze both the logs.

VAT AuthoringTesting & Validation Issue Analysis & troubleshooting.

1. Requirement Analysis Done.2. Client Meetings.3. VAT DB Implementation according to Customer technical requirements.4. Worked on Multiple FBs(screenshot attached)5. Specifically worked on VAT Tests Authoring, Testing, Validations & Troubleshooting at customer location.

went to Mahindra for DoIP testing and analysis.

DoIP validation in mahindra.taken trail on vehicle and test bench.  

1. DoIP database updated2. HPC Ad keep as gateway module3. Config items we cross verify4. 24V Tech Pro VCI report submitted to MSS

1. After Scan VIN MODEL Broadcast decode error shown on DL3 screen, checked in database found wrong QR code generated.2. DL3 3031 followed JIM instruction, SD card data uploaded in Fogbugz for next update3. ESCL option type updated in broadcaste decode4. New Option type added in ESCL 5. ABS and ESP option type checked, found 4 wrong option type. Now updated

1. Gate pass renewal process done,2. New Model code added in regular W6,3. New DID added in all CANFD and CAN supported ECU through VSCS method in DoIP database,4. Took trail on M110 vehicle

1. Took trail on W610 Classic CAN DID wrt happened2. DL3 3031 checked with Jim instruction but still DW2 not boot up

1. With new binary took a trail on vehicle2. Classic CAN WRT RD done3. New DID in request sent in HPCC4. New DID read in ESCL5. Feature code wrt in ICC

1. Vehicle have issue so today trail not happened

1. CANFD module name confirmed from Abhishek2. Cockpit level flashing done3. SRS flashed with same binary which flash with inhouse tool vikas

1. SRS flashing took the trail on the JIG level, Flashing done but some checksum algorithm mismatch from M&M side. We are cross verifying with MRV team,2. DL3 1158 scanner issue solved.

1. SRS trail took on offline area, flashing partially happened2. Logs sent to Tushar3. Only 2nd flashing block is transferring 1st and 3rd block not transfering.

1. With new firmware took trail on dummy barcode, its show error message on screen 2. I discussed with compliance team regarding my gate pass documents, they told come on Friday with PF challan they will discuss with further process3. EV vehicle was not available on today, tomoorow wil plan for take trail on vehicle

1. ATP excel sheet prepared and logs attached in MAHINDRA MAHLE share drive2. Today also vehicle is not available, Cockpit is not available3. SRS communication offline zig have no electricity so today not possible to take trail

1. Checking for vehicles and cockpit for taking trails but vehicle and cockpit is not available2. SRS zig level checking there voltage and resistance

1. CANFD vehicle level logs analysed2. Preparing in ATP excel sheet3. S block material list prepared

1. Tried to took trail on zig level and vehicle level but vehicle and cockpit was not available.2. UB_TWO_STATION added in DL3 11583. Regarding DL3 3048 and Q7 board mail sent to US team4. Regarding zig SRS issue mail sent to MAHINDRA team

1. SRS, FZ and MZ trail taken on Zig level. Flashing read and write services are happened.2. SRS not communicating issue found.3. Ignore RX message validate runtime4. DL3 2048 battery replaced5. Vehicle level trail taken with disabled write service Model DID

1. SRS flashing trail took on a zig level it failed for communication time2. Vehicle level trail tried to take but vehicle was not available

1. Took trail on CAN and CANFD ECU on zig level2. One DL3 is handover to them3. All steps writen and given to line person4. 2 OBD cables bring from MAHINDRA T block

1. SCAN BARCODE and write DID in ECU test checked and validated. Done2. SRS, Mid Zone and Front Zone flashing trail done.3. Mid zone flashing done, sent log to tushar4. HUD and AMP communication establishment done

1. MID zone ECU and SRS flashing trail took,2. Zig have issue so SRS not flash,3. MID zone ECU have some issue so flashing not happened.4. Logs sent to MAHINDRA MAHLE share drive

1. T block and V block, OBD cable-related open points discussed in the meeting2. Vehicle level trail took3. S block DL3-related open points discussed

1. SRS flashing trail took on a zig level it failed for communication time2. MID zone flashing trail took but it failed on reprogramming session3. All logs sent on Mahindra mahle share drive

1. With runtime 218 took trail, MLOG ecu response id now visible issue solved2. In trace folder missing bytes shown in response issue solved3. MID zone module flash with mahindra inhouse tool and collected trace. Sent to tushar4. Regarding OBD cable open points discussed with sameer and tushar

1. SRS File tested with Mahikndra inhouse tool and sent to tushar

1. Front zone module with 7DF trail took, sent log to tushar

1. DL3 2300 Configured setup and handover to S block offline area2. Tried to take trail on offline zig + Cockpit level for checking 7DF command in flashing sequance but zig and cockpit area some floor related work is started so both requirement not meet

1. Took trail with new runtime 2.0.217.0 on offline zig with cockpit with new runtime and binary2. Unexpected delay removed check - ECU sending possitive response3. On HUD configure time wrong message shown after validated - checked4. Link traffic generating properly checked - 2nd byte of DID not visible5. runtime 214 and runtime 217 compared both have history response shown on mLOG6. Unexpected return code removed from VCU checked7. Runtime frozen issue saw - logs and bug report send to tushar8. Info added in Line item 28 bolero neo

1. Taken trail with new runtime for front zone module flashing2. Taken trail with new runtime on offline zig level3. Taken trail with new runtime on vehicle level

1. Vehicle level trail taken with new binary for CAN ECU and HPCC 2. Offline zig level trail taken with OFFLINE_CAN_STATION for HUD and AMP ECU3. DoIP trail taken logs send on MAHINDRA MAHLE share drive

1. With new runtime 2.0.214.0 took trail on Zig level2. 1. With new runtime 2.0.214.0 took trail on Vehicle level3. Logs sent to tushar

1. Front Zonal module setup done in MAHLE warehouse2. Started debugging and checking why its stuck in flashing

1. CANFD trail taken on vehicle level2. Front Zonal ECU brought from MAHINDRA plant and kept in MAHLE warehouse

1. DL3 3029 configured with latest runtime and vatbin2. For SRS VIN WRITE, with new binary taken trail on ZIG level3. FB 27694 updated4. For FRONT ZONE Module flashing trail taken on cockpit5. For FRONT ZONE Module flashing trail taken on offline area with wiring harness6. FZM ECU bringing from mahindra

1. New DL3 without domain configured2. New DL3 without domain, checked task manager activity -> CPU consumtion without installed TL, with installed TL 3. Took trail and checked task manager to non domain TL with offline and vehicle level4. Analysed and send logs to tushar

1. Connected cokpit CANFD channel and CANFD offline zig took trail over OFFLINE_CAN_STATION and OFFLINE_CANFD_STATION but runtime was frozen2. Took trail over offline zig using CANFD modules but runtime seems frozen3. Took trail over cockpit using CANFD modules but runtime seems freez4. All logs sent to tushar

1. COCKPIT and offline zig trail taken2. Seperate ECU station created for Zig and COCKPIT3. Combined station created for COCKPIT and ZIG4. Logs share to tushar

1. Took trail on vehicle level with 213 runtime,2. FZM communication working or not on vehicle level

1. Took trail on single module FZM on offline area2. Took trail on SRS and EPS on vehicle level3. Analys canlayser log and DL3 logs on offline as well as vehicle level

1. With runtime 2.0.213.0 tester present enabled and took trail2. Link traffic log not visible3. log analysis and send to tushar4. Only SRS enabled, tester present enabled configuration enabled and send binary to vikas5. Only EPS enabled, tester present enabled configuration enabled and send binary to vikas

1. 7DF_command enabled and took trail with 2.0.212.0 runtime2. All logs collected with MAHINDRA inhouse tool3. Tester present enabled and took trail4. On front zone module flashing happened or not took trail on single module

1. Config item and module updated for VSCS method2. Trail taken on vehicle level with old binary

1. Updated VSCS module for write and read services,2. Trail taken on vehicle level with old and new runtime

1. DL3 3029 configured2. Try to take trail on new W6 EV but vehicle was not available so taking tomorrow

1. DL3 -3029 today we handover to MAHINDRA IT team to add in MAHINDRA domain2. VSCS method intergrate for write data in 16 ECU

1. Took trail with CAN_FD protocol found intermidiate response with ECU2. Send logs to tushar for analysis and update fogbugz

1. Updated VCI firmware version2. Taken trail with CAN_FD and UDS_DoIP protocol on front zone module3. Found bugs and updated in Fogbugz

1. Front Zone module flashing taken trail with VSCS method2. Added 7DF command and taken trail3. Added VIN model write service test and taken trail4. Sent all logs to tushar

1. New option modes added in MAHINDRA database for W62. Collected MAHINDRA EOL CAN_FD setup files

1. CAN_FD trail taken for VCI locked2. Trace sent to tushar3. CAN_FD flashing trail taken but .HEX file was not configured from MAHINDRA side

1. CAN_FD 10 trail taken with different scenario2. DL3 2208 WIFI card changed3. Regarding new OBD connector mail sent to MAHINDRA team

1. CAN_FD trail taken with Canalyser on live with US team2. New runtime trail taken ECU id shown properly3. CAN_FD VCI communication happened for 3 times4. With different scenerio trail pending

1. Hardware class changed and taken trail on FrontZoneModule to communicate but still response not come from ECU side2. Shown MAHLE devices to Prabhakaran in MAHINDRA3. All trails file sent to tushar to update FB

1. BDR file and updated scan.ini file send to tushar for update FB 27562

1. CANFD ini files and database shared to tushar2. DoIP trail taken as per suggest dustin but same i3000 error shown on screen Trace, Error Logs, INI files shared to tushar for FB updation

1. 27581 FB updated,2. DWPIF activated taken trail for CANFD,

1. Checked DL3 configuration,2. Took trail on offline setup,3. ECATS folder updated in MAHINDRA MAHLE share drive for further analysis

read specification document of DoIP protocol.

internal meeting with US and undersnad the issue of mahindra DoIP project.

Offline flashing testing.

fixed issue for FB27822

analysis of FB27822.

analysis of FB27755.

analysis of bug FB27755.

find the issue in code for FB27755.

committed code and created new runtime for Mahindra.

with UDS_DoIP(HW CLASS=21) VCI locking issue is there, need to resolve from firmware side.

1. State machine changed directly send 22F190 command2. Trail taken with canalyser and peck tool3. Log and screenshot shared to internal teams4. FB raised

1. PEAK tool through command executing2. VAT binary through taken trail but tester present not implemented in ECU because communication establishment not happened3. Need to change state machine and command

1. With new ECU CANFD trail taken but due to Bootloader software is not present communication not hapened

1. DoIP trail taken for CANFD and DoIP

1. Front zone module ECU and wiring harness continuty check with MAHLE DoIP OBD cable2. Resister connected to wiring harness 60 OHM supply required from DL3 to Front ZONE module ECU

1. Collected logs with different test cases, need to analyze properly.2. Verified MAHLE OBD Cable continuity(From Amphenol to OBD Connector) and it looks ok as per provided diagram.3. Need to verify MAHINDRA Harness OBD Connector to splitted wires continuity.4. Need to verify end to end continuity(MAHLE OBD Amphenol Connector to MAHINDRA Splitted Wires) to clearly understand each pin

1. With new binary CAN FD trail taken,2. With New OBD cable and old OBD cable trail taken on CAN FD3. Log sent to tushar4. Prepare canalyzer for taking trail on FrontZone module to collect LOGS

1. DL3 3051 offline taken trail

1. DoIP related 2-2 trail with new binary and new runtime i taken on W6 and Z1

DoIP Requirement UnderstandingCustomer meetingsVAT Authoring for CANFD TRAILS