KDS 2.0 | Information Required for Technical Inquiries When an Error Occurs – Customer Support | GIT America

Before submitting an inquiry about an error that occurred 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 was used, provide the selected add-on information

4. Detailed steps leading up to the issue and the time 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 (e.g. 240308-181119.json)
-> If a file exists for the time when the app terminated, please submit that 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.
System logs must be collected. For Samsung tablets, system logs can be collected by following the instructions at the links below.
Korean: https://support-kia.gitauto.com/hc/ko/articles/29729325313817

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

2. Errors that occur 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 reception number associated with it
- When reporting an error, capture and submit a screenshot of the error

3. Logs for each function

The log collection function described in 2. Errors that occur while performing a function (excluding abnormal app termination) collects logs for diagnostic functions such as Main, S/W Management, and ECU. For other functions, you must collect additional logs from the applicable path below.

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

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

(3) For an E-Report–related error, 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/