Bugs analysis and fixing.VAT DB modification and testing.

EVSC Testing, Fault Analysis & Debugging Support.

Worked on DICV EOL FB And released as per requirement to customer.FB 25250FB 27815FB 27816

Worked on K-Factor Issue analysis and finding way ahead.Screen Modifications.

Worked on Opened FBs for EOLAlso INS DTC BS4 Failure Analysis and troubleshooting.

Worked on FB 27446. EVSC Topic.1. Customer Meetings.2. Complete Requirement Understanding.3. Requirement Analysis.4. Point by Point Explanation with MSSU5. Queries Resolution.

Worked on FB27447. OBD2 Label Mismatch Issue analysis, debugging and fixing with co-ordination of MSSU.

1. New model addition in broadcast decode for W6 and Z1

Worked on Cummins INS issue analysisAccordingly carried out VAT changes and tested. in progress

1. Coordination with Paul (DICV) to follow-up on the status of V305 flashing.2. For OBDII, check the order number 20286960 and verify that the API for the vehicle station is taking OBDII A2L File properly.

Station Vehicle Rework 12 Fix: - PO Mapping Functionality- Back documentation review - Testing & Deployment.

Analyzed the BS3 Vehicle DCM Mismatch and the analysis report log was shared with Aleks by Tushar.

worked on FB 27074 & 27084

Bug Fixing, Alpha Testing, Deployment & Testing:For Station 10 & 12 - PO & VIN Validation scenario, fixing the Issue of fetching Activities log table records for pulling the engine dataset released in CDMT by passing VIN when the PO is empty (which is not present in the table) and sending the required valid data in the API response. 

27099 - ECUPROG-EOL-OBD II -Vehicle DCM flashing

Worked on FB27074-Multiple stations need to be handeled

Had a meeting with Tushar and Jackson from DICV and we have done the final configuration changes of the partial logs folder path in station INI and verified the file moving from the test cell primary report folder to RL system partial logs folder and then processed it & moved it to processed files folder. 

Supported DICV in deleting the released part numbers in the CDMT production system

EOL ReportLogiq Review: Coordinated with Tushar and reviewed the changes done and showed the tool displaying the log reports. Also discussed was the search option in the RL tool for VIN and PO search as well.

CDMT Latest Files Deployment with the VIN Validation changes done for Station 10 & 12 on 25th July 

Review and reconfigure the Report Logiq application along with Umar in RL EOL Server with its intended RL DB in EOL DB Server created for RL. Made the RL tool work with the log files by placing it manually.

EOL ReportLogiq Continued with the configuration of the incoming_files folder shared path in EOL RL Dev Server and station.ini file changes and tried to upload service transferring the files from the test machine to the RL server machine. (Discussion: Myself/Tushar/Jackson)

Validation of Same VIN with Different PO - Change in existing logic to apply this condition only when entered PO is already present in the activity table. If  PO does not already exist in the table, the VIN validation with PO will not apply. (Implementing this change after discussion/confirmation with Paul for stations 10 & 12) and deployment of the latest code in CDMT Dev Server.

1. ReportLogiq Configuration in Test Machines2. Creating an incoming_files folder in the shared network path in Aftersales Dev Server to receive the log files from Test machines3. Tried creating a map drive in the test machine and tried to connect shared path in the aftersales dev server but failed due to accessibility issues between two different system networks.

Worked on FBFB27072FB27074FB27085(Partially)

CDMT Support in deleting BS4 Engine HEX Files & its Part numbers released in Release Mechanism as requested by the DICV team.

In CDMT EOL API, Added additional validation logic for the VIN Validation against PO to prevent the use case of human error in entering the same VIN for different PO which pulls the same ESN to be written in ECU.  

Technical discussion on FB27074 - ECUPROG-EOL-For Different PO same data fetching and displaying in Data fetching screen. Further investigation, found that VIN validation against PO logic is required to avoid the use case of human error in entering the same VIN with a different PO which pulls the same ESN to be written in ECU.Participants: Vengat, Tushar, Paul, Jackson

Rectified FBs Testing, Validation and Debugging if any.

Worked on FB 27074270722712726905

Technical support was given to Paul by removing all BSIV Engine (HEX File) Part numbers that are already released in CDMT. It was accomplished in the backend DB table by writing SQL queries to remove all older records in different inter-referenced associated tables. 

Technical Support (to Paul): Some engine order numbers have not been fetched from GetFlashingData API since those order numbers are created in the system 2021. After updating the order in the table, we observed that it can be fetched from the API and is working in TestLogiq.Remark: Given the solution to update the records to get the record set refreshed in DB table.

Bug Fix:Fetching Engine HEX Flash file always only from VAR_PART_NO_2 as confirmed by Paul. (It was reverted back from looking at multiple column values such as VAR_PART_NO_2, VAR_PART_NO_3, etc..)

"FB26866 Validation & Debug Session with DICV- Engine Timestamp & Vehicle Timestamp Validation for Back documentation"

DICV Meeting for DB Migration 

FB# 26866 Timestamp changes - Back documentation- API modification with new Test Names for all stations