KDS 2.0 | How to Submit an Error Log Report Using Log Collection – Customer Support | Europe & General

This guide explains how to activate Log Collection, reproduce a symptom while capturing screens with the floating widget, and submit an Error Report on KDS 2.0. Use this procedure not only for Vehicle Diagnosis failures and ECU Upgrade failures, but for any software or communication issue occurring in KDS 2.0 (including S/W Management, Digital Field Fix, Software Running / Updating, Specification, and e-Report).

Applicable Environment: Kia KDS 2.0 Tablet App & VCI II(2) / VCI3 (VCI III)
Target Version Code (App Prefix): NEK · NUK · NNK · NCK (Overseas Regions — Excluding Domestic Korea & China)

KDS 2.0 closes unexpectedly (force close)?

If KDS 2.0 closes by itself (force close) while in use, the Error Report sent through Log Collection alone is often not enough to find the cause. A dump log (system log) of the tablet is also needed.

The dump log is created as a ZIP file. Attach it under Attachments (optional) > Select in Step 3-2 of this guide. A dump log ZIP file is often larger than the 20 MB total listed in this guide. If it cannot be attached, send it through your Distributor / NSC. Your Distributor / NSC will then escalate the file to GIT.

For the detailed procedure, see: KDS 2.0 | How to Collect a Dump Log When the App Force Closes (Samsung Tablet)

On this page

1. Video Manual & Workflow Summary
2. Step 1: Activate Log Collection Mode
3. Step 2: Reproduce Symptom & Capture Screens via Floating Widget
4. Step 3: Submit Error Report & Attach Files (Up to 20 MB)
5. Step 4: Contact Your Distributor / NSC (Escalation to GIT)
6. Troubleshooting & Related Guides

1. Video Manual & Workflow Summary

Watch the video guide below or follow the step-by-step instructions to activate logging, reproduce the issue, submit the log package, and escalate the case through your local Distributor / NSC.

Phase	Menu / Action	Key Point
Step 1. Enable Logging	Configuration > Log Collection > Run > Start	Tap < (Back) to return to the Main Screen. Verify the floating widget at the bottom-right.
Step 2. Reproduce & Capture	Reproduce issue 2–3 times + Tap Screen Capture on floating widget	Floating widget screenshots (`Log_*.png`) are automatically bundled with the log file (`gdsnLog.git`).
Step 3. Submit Error Report	Floating Widget > Error Report > Submit	Select Error Type, enter description, optionally attach separate files up to 20 MB, and tap Submit.
Step 4. Escalate	Contact Distributor / NSC → GIT	Provide the VIN or Report No. to your Distributor / NSC so they can escalate the case to GIT.

2. Step 1: Activate Log Collection Mode

Before reproducing the symptom on the vehicle or tablet, enable Log Collection so KDS 2.0 records all communication and system events from the beginning of the procedure.

Step 1-1. Open Configuration on the KDS 2.0 Main Screen

On the KDS 2.0 main screen, tap Configuration (gear icon) located in the bottom-right corner of the bottom navigation bar.

Step 1-2. Select Log Collection and Tap Run

In the left-hand menu of Configuration, select Log Collection (1), then tap the Run button (2) at the bottom of the screen.

KDS 2.0 Configuration - Select Log Collection and Tap Run

Step 1-3. Tap Start and Return to the Main Screen

Review the Error log acquisition guide by major function (1) and tap Start (2) at the bottom-right. Once returned to the Configuration screen, tap the < (Back) icon at the top-left to go back to the KDS 2.0 Main Screen.

KDS 2.0 Log Collection Guide Modal - Tap Start

Function Category	When to Complete Log Collection
Fault Code Searching	Complete log collection after executing the fault code (DTC) search where the failure occurs.
Data Analysis	Complete log collection after selecting and diagnosing the target sensor / data item.
S/W Management & ECU Upgrade	Complete log collection after executing the S/W Management event or ECU Upgrade where the error occurs.
Actuation Test	Complete log collection after selecting and executing the actuation test item.
ETC (All Other KDS 2.0 Issues)	For Digital Field Fix, Software Running / Updating, Specification, e-Report, or VCI connection issues, reproduce the symptom and then complete log collection.

3. Step 2: Reproduce Symptom & Capture Screens via Floating Widget

When Log Collection mode is active, a floating logging widget remains visible in the bottom-right corner of the screen across all KDS 2.0 menus. Reproduce the issue 2 to 3 times so the error state is thoroughly recorded.

Required Tip: Capture Error Screens Using the Bottom-Right Floating Widget

Whenever an error code, pop-up message, or abnormal screen appears during symptom reproduction, tap Screen Capture on the bottom-right floating widget.
A confirmation message (“screenshot has been created and attached.”) will appear, and every captured screenshot (Log_YYYYMMDD_HHMMSS.png) is automatically bundled together with the generated log file (gdsnLog.git) when you open the Error Report.

Floating Widget Controls (Bottom-Right Corner)

Cancel (Power Icon): Stops Log Collection mode immediately without submitting a report.
Screen Capture (Viewfinder Icon — Badge 1): Captures the current KDS 2.0 screen and automatically attaches Log_YYYYMMDD_HHMMSS.png to the active log package.
Error Report (Compose Icon — Badge 2): Opens the Error Report submission screen after you finish reproducing the symptom.

KDS 2.0 Floating Widget - Screen Capture and Error Report

4. Step 3: Submit Error Report & Attach Files (Up to 20 MB)

Immediately after reproducing the symptom, tap Error Report on the bottom-right floating widget while the tablet is connected to a stable Wi-Fi / Internet network.

Step 3-1. Record the Report No., Select Error Type, and Enter Error Description

User Information & Report No. (Badge 1): Verify the auto-populated vehicle and user fields, and write down or photograph the Report No. (e.g., 261027-D82N). You will need this reception number when contacting your Distributor / NSC.
Select Error Type (Badge 2): Check all categories that match your issue:
- Diagnosis (DTC Analysis, Data Analysis, Actuation Test...)
- S/W Management / Digital Field Fix
- ECU Upgrade / Software Running / Updating
- Specification / e-Report / ETC.
Error Description (Badge 3): Enter a clear Title and detailed Contents (target system/ECU name, error code, and exact reproduction steps).

KDS 2.0 Error Report Top - Report No., Error Type, and Description

Step 3-2. Verify Bundled Log Data, Attach Additional Files (Up to 20 MB), and Tap Submit

Log Data — Auto-Bundled Files (Badge 1): Scroll down to confirm that the screenshots captured via the floating widget (Log_YYYYMMDD_HHMMSS.png) and the diagnostic log file (gdsnLog.git) are automatically listed together under Log Data.
Attachments (optional) — Separate File Upload up to 20 MB (Badge 2): If you have additional reference files stored on the tablet (such as external camera photos, short video clips of the vehicle symptom, or PDF documents), tap Select under Attachments (optional) to attach separate files up to 20 MB in total.
E-Mail & Required Consent (Badge 3): Verify your email address and check the mandatory box: “(Required) Do you agree to send error report?”
Submit (Badge 4): Tap Submit and wait until the upload completion message appears. Do not close KDS 2.0 or turn off Wi-Fi during transmission.

KDS 2.0 Error Report Bottom - Log Data, Attachments up to 20 MB, Consent, and Submit

5. Step 4: Contact Your Distributor / NSC (Escalation to GIT)

Important Post-Submission Escalation Process (Dealer → Distributor / NSC → GIT)

Submitting the Error Report uploads the log package to the server, but to initiate a technical investigation, you must notify your local Distributor or National Sales Company (NSC).
Please provide the Vehicle Identification Number (VIN) or the Error Report Reception Number (Report No.) / User ID (E-Mail) to your Distributor / NSC. Your Distributor / NSC will then escalate the inquiry to GIT for technical log analysis.

Information to Provide	Details & Where to Find It
1. Error Report Reception No. (`Report No.`) or User ID	Displayed at the top-left of the Error Report screen under User Information (format: `YYMMDD-XXXX`, e.g., `261027-D82N`), or the registered KDS 2.0 User ID / E-Mail used for submission.
2. Vehicle Identification Number (VIN)	17-character VIN of the vehicle where the Diagnosis or ECU Upgrade issue occurred (plus Model, Model Year, and Engine type).
3. Target System & Symptom Summary	Name of the system/ECU (e.g., Engine, MDPS, ADAS), function executed (Diagnosis, ECU Upgrade, S/W Management), and any error code displayed on screen.

6. Troubleshooting & Related Guides

Troubleshooting: “To use the app, please set all permissions in the GITMCommManager.Service to Allow”

If a Notice pop-up appears when tapping Start in Log Collection stating that GITMCommManager.Service permissions are required, open the tablet’s Android Settings > Apps > GITMCommManagerService > Permissions and set all permissions (Nearby devices, Location, Notifications, Storage/Files) to Allow. Then return to KDS 2.0 and tap Start again.