Checklist and Required Tablet Files When ECU Upgrade Events Are Not Showing Up (GDS Smart / KDS 2.0 / GENESIS Smart) – GIT FAQ | Asia/Pacific, Europe, Africa, Middle East

ECU UPGRADE TROUBLESHOOTING · EUROPE & GENERAL

If a target ECU Upgrade event does not appear on GDS Smart, KDS 2.0, or GENESIS Smart, this guide provides the step-by-step verification checklist—covering vehicle/ROM ID compatibility, GSW Dealer TSB publishing (Copy/Discard & Re-copy), and the latest Internet Update—followed by the exact tablet PC database files (GSW*.sqlite, GSW*_L.sqlite) and ECU log folder (NvciData/log/ecu) required for root-cause analysis if the issue persists.

On this page

Step 1: Verify Vehicle Specification, ROM ID, History, and Manual Mode
Step 2: Verify GSW Dealer TSB Release Status (Copy / Discard & Re-copy)
Step 3: Perform the Latest Internet Update & Refresh Event List
Step 4: Required Tablet PC Files & Case Information If Events Still Do Not Appear

1. Step 1: Verify Vehicle Specification, ROM ID, History, and Manual Mode

When an ECU Upgrade event is not listed on GDS Smart, KDS 2.0, or GENESIS Smart, first verify the following vehicle and event conditions:

TSB Target Specification: Confirm that the vehicle model, model year, engine/powertrain, target control unit part number, and current ROM ID match the exact applicability criteria specified in the Technical Service Bulletin (TSB).
ECU Upgrade History: Go to ECU Upgrade > ECU Upgrade History on GDS Smart, KDS 2.0, or GENESIS Smart to check whether the target event has already been completed on the vehicle.
Manual Mode Visibility: Switch from Auto Mode to Manual Mode in the ECU Upgrade menu and check whether the target event appears under the corresponding system category.

2. Step 2: Verify GSW Dealer TSB Release Status (Copy / Discard & Re-copy)

In Europe, India, and General regions, an ECU Upgrade event linked to a TSB is displayed on dealer and distributor tablets only after the Distributor (NSC) copies and publishes the TSB from the GSW Distributor TSB board to the Dealer TSB (TSB Local) board.

Distributor TSB Copy Check: Verify whether the Distributor (NSC) has copied and submitted the relevant TSB to the Dealer TSB board on GSW (refer to How to Copy TSB document from TSB board to TSB Local board).
Re-copy After HQ Revision or Distributor Code Change: Even if the TSB was previously copied, if Hyundai/Kia/Genesis HQ has modified or redistributed the TSB—or if the Distributor Code has changed—simply editing the existing Dealer TSB may not synchronize the event.

Important: When a TSB is revised/redistributed by HQ or after a Distributor Code change, the Distributor must discard the existing Dealer TSB and copy it again from the Distributor TSB board to publish it cleanly.

3. Step 3: Perform the Latest Internet Update & Refresh Event List

Newly released or updated ECU Upgrade events require the latest Resource package on the tablet PC.

Install Latest Internet Update: Connect the tablet PC to a stable Wi-Fi network, run Internet Update on GDS Smart, KDS 2.0, or GENESIS Smart, and confirm that the latest Resource version is installed.
Refresh Cached Event List (Optional): If the latest update is installed but the event list does not refresh, close the diagnostic app completely, open the My Files app on the tablet, delete Internal storage/nvci/update/event.lst, and restart the app to re-download the event list from the server.

4. Step 4: Required Tablet PC Files & Case Information If Events Still Do Not Appear

If the ECU Upgrade event still does not appear after completing Steps 1 through 3, please collect the following 3 items from the tablet PC along with the required case details and submit them to GIT Technical Support for root-cause analysis.

A. Required Tablet PC Files to Collect (3 Items)

Target Item	Tablet Storage Path (My Files)	File Examples & Notes
1. GSW System DB File	`Internal storage/nvci/systemdb/system/GSW{Region/Maker}.sqlite`	e.g., `GSWKME.sqlite`, `GSWHME.sqlite`, `GSWHMC.sqlite`, `GSWKMC.sqlite`, `GSWHMI.sqlite`, `GSWKIN.sqlite`, `GSWHMA.sqlite`, `GSWKMA.sqlite`
2. GSW Local DB File (_L)	`Internal storage/nvci/systemdb/system/GSW{Region/Maker}_L.sqlite`	e.g., `GSWKME_L.sqlite`, `GSWHME_L.sqlite`, `GSWHMC_L.sqlite`, `GSWKMC_L.sqlite` (paired `_L.sqlite` file in the same folder)
3. Entire ECU Log Folder	`Internal storage/NvciData/log/ecu` (Entire folder)	Compress the entire `ecu` folder into a `.zip` file (see How to get ECU logs from your tablet)

B. Required Case Information to Submit Together

VIN (Vehicle Identification Number): Full 17-character VIN of the affected vehicle, plus model and model year.
TSB No. & Missing Event No.: Official TSB number, Campaign/Issue number, and the specific ECU Upgrade Event number(s) not showing up (e.g., Event #1371, #1373).
GSW Account & Distributor/Dealer Code: The Distributor Code / Dealer Code and the GSW login ID (or test account information) used on GDS Smart, KDS 2.0, or GENESIS Smart when the symptom occurred.
Screenshots: Screenshots of the GSW Dealer TSB page and the diagnostic app screen showing the current Resource version and ECU Upgrade list.

Note: Both the GSW*.sqlite and GSW*_L.sqlite files in nvci/systemdb/system/ are required together with the compressed NvciData/log/ecu folder so our engineering team can compare the tablet's synchronized TSB/event database against the GSW server release data.

Related to