Coordination with Ram and VCI mapping VCI1000 - 702435

1. -SSO login: Dealer code character limit increased from 5 to 6.-Auto VIN detection: Raider vehicle selection is enabled when the SKU starts with N6191840 or N6191120.-Application version update: Version name updated to V2.1.1, and version code updated to 164.

Supported Karthick for the following activity:1. VCI 701269 and 002635 Activation2. Checking regarding the email sub: VHR not reflect at N1 repots and reported3. Exported Feb. Month VHR Report and shared

Coordination with Karthick for the below activities:1. Check last login with VCI TechPRO_005507 as it was mentioned as missed. Dealer Code14585 - SRI SARAVANA AUTOMOTIVE LLP2. Enabled notification to monitor when someone uses the VCI to login

1. The given VIN spreadsheet is imported to the campaign name – Apache RTR 160 4V Flashing starting trouble. Modified the import functionality to handle the duplicate VIN import.2. In the spreadsheet, 608 duplicate VINs are found from 1,16,403 VIN entries.3. VCI 702316 activated to account ss.suresh@tvsmotor.com in e-ridescan

1. Fix search in Campaign VIN Listing2. Fix duplicate VIN insert issue.

Coordinated with Karthick and provided technical support on the following,1. To check Login issue in ridescan for Dealer code 69297, Mode service, Branch Divya Motor and identified issue. From MahleForum TVSDealerSSO API, it shows the message Your account has been deactivated. Please contact your administrator.2. Shared Dummy VINs & SKU for OBD2B

 RIDE Scan 2.0 Video upload to the video library in both UAT and Production 

GTS Procedure addition for DTC P0506,P0507 in Production

1. In the DMS flash file upload interface, allow .bin file extension to upload the flash file.2. Uploaded the flash file U597_CLUSTER_APP.bin for the N597 vehicle

1. Report of 7-Series VCI dealers list to share with TVSM2. Report of 8-Series VCI dealers list to share with TVSM (in both Ridescan and its Mini Version)3. Report of 9-Series VCI dealers list to share with TVSM

1. Fixing the VIN attribute API response for frame MD626AK17M2A03664, which does not show Mikuni vehicle info. This is because the TVSM VIN attributes JSON file returns the EMS controller type value with extra space (" Mikuni").2. Prepared 0-series VCI dealers list and shared with Karthick, TVSM

- Campaign VIN Creation - Issue with import option as duplicate VIN constraint. Modified the import logic to exclude duplicate VINs separately and imported valid VINs to be inserted.- Imported the VIN list from Karthick.

Campaign Dashboard - Modification to display the previous day and current day flashing count for each campaign card. Verifying the total flash counts w.r.t the days the flashing is done.

Ridescan 2.0 App: Validate Cluster Flashing Report - Update ECU Type in ECU Flash Report Screen in Mahle DMS- Check 7 VINs that flashed in the Campaign flow- Verified 5 VINs that are sent to TVS DMS successfully and 2 VINs are not due to 500 response from TVS API. 

Discussed with Karthick and enabled the campaigns - Jupiter 125 EMS Flashing Campaign, Jupiter 110 EMS Flashing, Raider EMS Flashing Campaign, Raider CMS Flashing Campaign

Ridescan 2.0 App: Mahle Forum GTS Issue- Validate Mahle Forum API based on the feedback from TVSM- Coordinated with RajaGanesan (TZ) about the issue in the app

Backend Campaign Creation in Production per Karthick's request:- Jupiter 125 EMS Flashing Campaign & Imported 10,414 VINs & disabled it.- Jupiter 110 EMS Flashing Campaign & Imported 15,631 VINs & disabled it- Raider EMS Flashing Campaign & Imported 1,549 VINs & disabled it- Raider CMS Flashing Campaign & Imported 13,553 VINs & disabled it

- In the DMS Portal, modified the VIN Creation page to download a sample template to import VINs - Handled batch update process for huge volume of data to be imported for performance issue

- Apache 160 4V RM (Vitesco) controller type mapping to pull the vehicle info for VIN Based flashing- PTC User creation, VCI Mapping, enabling TVSM engineer login- Worked on a report to pull the information of each dealer having 0-series & 7-series.

Zero Series VCI Issue discussion with Mahle internal team and TVS team.

VHR Data on Production:- Support on verifying VHR Data for VINs MD634BE82R2AA5852, MD634BE82P2D21219- Prepared a report of VHR data from 1st Dec to 11th Dec and shared with Karthick

API Modification: Zero series VCI firmware update skip count

Firewall Network Migration Activity - Sitecore websites from TVSM (Stakeholder- Deepalakshmi)- MAHLE Support to verify the RR310 Cluster Upgrade orders

1. Ridescan2.0 Release To field: - Backend changes for the App Update mechanism from v10.6 to v2.0.0 (10.7) - Releasing App v2.0.1 with 0'series firmware update fix- Coordination with the app development team (TZ)2. Ridescan 2.0 QR Code link Page Update with release notes and latest APK update to download from the page.

DTC Error Code PDF Changes:1. Generate separate PDFs for Active Procedure2. Generate separate PDF for Confirmed Procedure3. API Changes to pull PDF w.r.t state (Active/Confirmed)

I  supported to verify the VIN Test Entry for cluster upgrade orders (MD638BS13M1H11887), as requested by Mr Amit from TVSM and IP whitelisting.

Continuation of Updating all new vehicle images in UAT & DMS and TVSM Samachar: Generate QR Code link to download Ridescan 2.0 APK

DTC Procedure Module Development- Alpha Testing on DTC procedure creation and PDF generation- APP-level testing via API

1. Ridescan 2W: Update all new vehicle images in UAT & DMS since Ridescan 2.0 app release planned on 3rd Dec.2. TVSM Samachar: Generate QR Code link to download Ridescan 2.0 APK 

1. DTC Procedure Module Development - Continuation- PDF Creation for each DTC Error Code2. API development- Get an Encrypted Key for the VIN request- Regenerate and Get an encrypted key for the VIN request

DTC Procedure Module Development- PDF Creation for each DTC Error Code

Support for Mikuni Vehicle Mapping as the Vehicle Info not coming for VIN MD621BP20M1L44171 due to controller type value issue from TVSM VIN attribute country VIN

DTC Procedure Module Development - Continuation:- Admin: Interface Development to feed Procedure Content (Add/Edit/listing)- Table Design & Store Data 

DTC Procedure Module Development -  An interface to manage the DTC Procedure content dynamically. 

1. Discussion with Karthick on the DTC Procedure for PDF linking 2. Disabling VCI Firmware update for 9-series based on RajaGanesan request in UAT3. Modified TVSM Device List API response to send empty array instead of null value as requested by RajaGanesan. These updates are done for ridescan in app DEV, UAT, PROD and ridescan mini app.4. Tech support - In UAT, linked VCI 010983 and 900139 under Karthick's account as requested by him

Tech support to Karthick in checking any Cluster flashing done for VIN MD637GE52R2E06641

1. Assign MD621BP2XR3H08787 as XL OBD II for campaign-based flashing validation2. Assign MD621BP2XR3H08787 as XL 100 OBD I for campaign-based flashing validation3. Fixing to fetch Vehicle Info for VIN MD621BP2XR3H08787  

1. Fetch correct Vehicle info for the VIN MD625AF94R1C20010 - Raider SEDEMAC With UDS. We tried to detect vehicles by auto VIN detection with DMS. The actual vehicle is  Raider SEDEMAC With UDS vehicle id = 42. But we got the response as Non-UDS vehicle with the vehicle id = 37. Karthick,  want to change the Raider SEDEMAC with UDS always when detecting Raider SEDEMAC UDS or NON UDS2. Checking and FIx for VIn MD638DS10R1H19190

Modification to getVehicleBasedInfo API for the sequence order changes in both UAT and Prod as follows,K-Line Engine Management System -> KEMSEngine Management System -> EMSEngine Management System OBD II -> EMS-OBDIIAnti-Lock Braking System -> ABSAnti-Lock Braking System (BOSCH) -> BABSAnti-Lock Braking System (KLine) -> KABSInstrument Cluster -> ICUIntegrated Starter Generator (ISG) -> ISG

VIN-Based Diagnostics - Technical support- VIN-based diagnosis showing OBD II but in the ECU list, OBD II is not there. Analyzed and changed the ECU ID from OBD1 to OBD2 and fetched it as an OBD2 flash file by adding RTR310_OBD2 as the model in the flash file list in both staging and DMS.-  Fix to Fetch Vehicle info for VIN MD625AF99N1P11048 - Campaign-based flashing Testing for Ronin Cluster flashing for VIN MD637AN17N2L02227- Modified to send CMS instead of ICU to the M1 Solution TVS DMS Server

1. Shared VHR report with Karthick from 1st April to 15th November till 12:45 PM2. Adding user email account s.harivaishnavi@tvsmotor.com to the engineer list 

1. VIN Based Diagnosis – In the API vehicle details not coming properly for RR310 series. So, discussed with Karthick and Raj and mapped all RR310 vehicles as RR310 REFRESH.  We choose the OBD flag based on the variant selection only for RR310 vehicles. 2. VIN Based Diagnosis API – Hard Coded the API to give vehicle info for RR310 series and Jupiter 125 Smart Connect instead of Jupiter 125.

DMS login fix - checked and resolved login issue that is using VCI 900115

1. Correction of automatic vehicle info for VIN MD626AK42R1D12756 - Jupiter smart connect but showing Jupiter 125 2. DMS VCI Mapping - 702294 to S.a.madhanasundar@tvsmotor.com

Campaign Based Flashing - Technical Support to TZ & Validation (MD626AK4XN1G10658)

Select Vehicle Type Dialog: Implemented in VIN-based diagnosis to enable selecting the vehicle type as either MIKUNI OBD I or Other ECUs. (refer the attached videos) Vehicle Health Report: Added the option to the reason list while choosing the vehicle. Screen Switching: Ensured tester presence and handled screen switching across all flashing screens. CVN & CAL_ID Issue: Fixed on XL 100 OBD II flash. Waiting response handled : Waiting response (7F3178) handled properly. Bluetooth Library: Updated for improved response performance. Version Update: Updated version code to 159 and version name to 2.0.7.

DMS Access to two user email accounts as requested by karthick (TVSM).

1. Disabled 52 VCIs linked with Karthick's engineer account in UAT & enabled VCIs 001888, 003415, 009577,7011362. Linked VCI TechPRO_001946 and TechPRO_701453 under Karthick account for RTR 310 ABS Flashing in UAT3. Disabling login for older app versions to make dealers to update the latest Ridescan2.0 version Apps4. Disabling login for Ridescan Mini App as no longer support to force users to use Ridescan2.0 as one common App.  

Raider125 (Sedemac with UDS) OBD2 Enablement:1. Vehicle ECU Mapping2. Vehicle ECU Function Mapping3. LP, DTC, Write Date, RC, IOC Parameters Addition

As discussed with TVS team, blocking the Ridescan old application till app version 1.6 by restricting the user login to make use of latest Ridescan2.0 app.  In addition, blocked the use of Ridescan Mini App to make the users to use Ridescan2.0 app. 

Sync up call with TVSM team - Ankit, Karthick, Ram- Campaign VIN List Timestamp to check- Campaign Flash Data Push Mechanism twice a day for handling TVS DMS downtime for JC Closure- Keyless ECU status- VHR PDF File Size Reduction- Ridescan2.0 Mikuni Issue status

VIN BASED VHR (EVERYTHING WILL BE VIN BASED)

VIN BASED AUTO VEHICLE SELECTION 

UI UX UPGRADE 

Discussion with TZ team (Rajaganesan) & Karthick about the concepts & logic of allowing flashing & diagnosis screens based on API response key attributes - flash_eligible and flash_status for handling scenarios of before and after flashing.

1) In Campaign Creation/Edit screens, introducing the ECU flashing type configurations to allow respective flashing for auto-vin detection flow.  2) Also modified the Vehicle Variant selection in the forms with the vehicle list used in VIN Attribute JSON file from TVS to control & restrict wrong ECU flashing

1) In backend, capturing the type of flashing done to the flashing report for M1 solution and updating the campaign VIN status from planned state to completed state.2) API level changes to receive type of ECU flashing done, 3) Managing campaign info message and error message display in the App screen from backend 

Backend support & coordination with Rajaganesan for validating the campaign flow working after the implementation done in Ridescan app by checking both positive and negative scenarios.

Continued the backend support given to Karthick & Rajaganesan (TZ) for Vehicle level testing.

Backend Support given to Karthick & Rajaganesan (TZ) for  Vehicle level testing (Jupiter Vehicles).

Technical Support to team on VIN Attributes API Implementation with Vehicle Info to pull the respective vehicle details for auto-navigation functionality.

Campaign Based Flashing Module: UI Design refinements with following additional functionalities- Implementation of Filters on VIN List Screen- Applied Filters are campaign name, flash status, VIN state (Active/Inactive)- Apply Filter by campaign code/name navigating from Dashboard Screen- Retaining Applied Filters on page refresh/reload by maintaining in local storage- Testing & Fixes the implementation

1. Creation of Campaign Module in Backend DMS portal with UI layout in UAT 2.Manage Campaign Interface with create/edit/delete options3. Manage Campaign VIN List Interface with add VIN with import feature, edit & delete options4. Create Dashboard for campaign listings5. Made Refinements by testing entire campaign module level features for usability issues. 

Campaign Based VIN Flashing - API Changes with mock data for App Integration- To show the VIN has enabled for campaign - To show the VIN has completed the flashing through Campaign 

Validating the modified VIN Attribute API to pull Vehicle Info based on Sign VIN mapped.

Continuing the changes implemented in VIN Attributes API to pull one vehicle info by matching with Sign VIN mapped to pull LP, DTC, WDID, RC, IOC 

For Ridescan 2.0 - Modification of Vin based flashing API, - Mapping Sign VIN in Vehicle Info table- Modify VIN Attributes API to pull one vehicle info by matching with Sign VIN mapped to pull LP, DTC, WDID, RC, IOC 

For VIN based flashing backend changes, prepared list of available vehicles to map Sign VIN with country code & shared with Karthick for inputs

Regarding VIN Based Flashing API, explained Karthick about the feasibility and the approach of mapping Sign VIN of country code mapping to Mahle Vehicle table to get desired results.

Modification of Vin based flashing API with the particular vehicle Info with Vimal about mapping requirement

Ridescan 2.0 - Additional API /  Modification discussed with Rajaganesan from TZ.

Campaign Based Flashing Development Plan discussion with Vimal for timeline.

Campaign Based Flashing Discussion with Mr. Ankit & Team