KDS 2.0 | Information Required for Technical Inquiries When an Error Occurs – Customer Support | Europe & General

Before submitting an inquiry about an error encountered while using KDS 2.0 or GENESIS Smart, please provide the following information and logs.

[Required Basic Information]

1. Confirm that the program is up to date

2. Vehicle Model information
Vehicle Model/model year/engine displacement

3. System information
System selected when performing the diagnostic function
If an add-on is used, provide the selected add-on information

4. Detailed procedure leading to the issue and the time when it occurred
Example: The error occurs when selecting Vehicle Type / FCS / ENGINE / performing FCS
Provide a video or screenshot showing the issue

[Required Log Information]

1. If the app terminates abnormally

(1) When the Main App terminates abnormally
1) Folder path: NvciData\log\errorlogger\main
2) File name: date_time.json( ex. 240308-181119.json)
-> If a file exists for the time when the app terminated, please send the file.

(2) If there is no log in the path above, an app other than the Main App may have terminated abnormally, or the app may have been terminated by the system.
A system log must be collected. For Samsung tablets, the system log can be collected as described at the link below.
Korean: https://support-kia.gitauto.com/hc/ko/articles/29729325313817

English: https://support-kia.gitauto.com/hc/en-gb/articles/29729325313817

2. Errors occurring while performing a function (excluding abnormal app termination)

(1) Obtain the logs using the log collection function in the diagnostic app.

Instructions: Sending the error log report on KDS 2.0/KDS2.0<- Click here.
(2) After uploading the log, provide the VIN or log submission number
- When reporting an error, capture and submit a screenshot of the error

3. Logs for individual functions

The log collection function described in 2. Errors occurring while performing a function (excluding abnormal app termination) collects logs for diagnostic functions such as Main, S/W Management, and ECU. For other functions, additional logs must be obtained from the paths shown below.

(1) If an error occurs in the Smart Launcher app, collect all files from the path below
NvciData\log\gitlog\smartlauncher\

(2) If an error occurs in the Smart Warranty app, collect all files from the path below
NvciData\log\gitlog\smartwarranty\

(3) If an E-Report-related error occurs, collect all files from the path below
nvci\temp\eLog\

(4) If a Bearing Clearance Measurement result file upload fails (BCT), collect all files from the path below
nvci/upload/bearingGap/

(5) If an Atkinson Inspection result file upload fails (PNSS), collect all files from the path below
nvci/upload/yfinspection/

(6) If a CPO result file upload fails, collect all files from the path below
nvci/upload/CrosCert/