Skip to main content
KDS 2.0
KDS 2.0 View All
GPMS
GPMS View All

VCI II(2) Troubleshooting - Connection, Firmware, Power, Communication & Repair Guide

Oscar Eom
Updated
0

Overview

This guide provides troubleshooting procedures and hardware repair (RMA) criteria for the official Kia diagnostic interface VCI II(2) (serial number prefix: NGD) regarding wireless connection (Wi-Fi Direct / Bluetooth), device detection failures in the KDS 2.0 diagnostic application, vehicle communication (CAN/OBD), firmware updates, and power issues.

It helps field technicians quickly determine whether an issue is a software or communication cache problem that can be resolved immediately on site through self-service steps, or a hardware fault requiring board replacement or internal repair.

Applicable Hardware & Specifications:

  • Applicable Serial Number Prefix: NGD (North America)
  • Supported Diagnostic Software: KDS 2.0 (Target Version Code: NNK,NCK)

If the symptom persists after completing the self-service checks and hardware inspection/repair is required, please refer to the Official Repair (RMA) Submission Guide below.

 
 

1. Bluetooth / Wireless Communication Failure & Device Not Detected in KDS 2.0

Symptom: VCI II(2) is connected to the vehicle OBD port but does not appear in the Device Manager list in the KDS 2.0 diagnostic application, VCI II(2) is not found in the tablet's Android Bluetooth search, pairing remains stuck in a connecting state, or the wireless connection drops intermittently during diagnostic work.

Self-Service Workaround (try these steps in order before requesting repair):

  1. Verify Bluetooth Pairing Security PIN Code:
    When connecting manually or pairing for the first time, enter the PIN code 0701.
  2. Unpair Existing Device on Tablet:
    On the tablet, go to [Settings → Connections → Bluetooth] and Unpair (Forget) any registered VCI II(2) device (NGD*).
  3. [Key Step] Clear Communication Service App (GITMCommManager.Service) Data & Cache:
    If VCI II(2) is properly connected to the vehicle OBD port but does not appear in the available device list of the diagnostic application, temporary data corruption in the Android background communication service may be the cause. Clear the data and cache as follows:

    Important: Communication Manager Service App Reset Procedure

    1. Open the Android Settings app on the tablet.
    2. Navigate to Apps (or Applications).
    3. Search for and select GITMCommManager.Service App (or GITMCommManagerService).
    4. Under Permissions, confirm that Nearby devices, Location, and Bluetooth permissions are all set to [Allow].
    5. Go to Storage and tap Clear data and Clear cache.
  4. Reboot Tablet PC and Reconnect VCI II(2):
    After clearing the data and cache, you must reboot the tablet PC. With the vehicle ignition ON (IG ON), disconnect the VCI II(2) from the OBD port, reconnect it firmly, and search and connect the device under [Configuration → Device Manager → VCI II] in KDS 2.0.
  5. Cross-Check with Dedicated USB Wired Cable:
    If wireless connection continues to fail, connect the tablet and VCI II(2) directly using the dedicated USB cable to verify whether it is recognized normally in KDS 2.0.

When to Request Repair (Hardware Fault Criteria):

  • VCI II(2) is not detected or pairing continues to fail across multiple tablets even after clearing GITMCommManager.Service data/cache and rebooting the tablet
  • Communication fails even when connected via the dedicated USB wired cable
  • Communication repeatedly drops within seconds of connecting and the top LED blinks red

If the above symptoms persist, replacement of the internal wireless board (wireless communication module) is required. Please submit your device for official repair.

Back to top

 

2. Power Failure, No Boot & LED Status Indicator Meanings

Symptom: VCI II(2) does not power on when connected to the vehicle OBD-II terminal, no normal startup beep sound is heard, or VCI II(2) intermittently resets (turns off and on) when lightly touched or when the cable is moved while connected to the OBD terminal.

On-Site Checks Before Requesting Repair:

  1. Cross-Check on Another Vehicle: Connect the VCI II(2) to another normal vehicle's OBD port to determine whether the power supply issue is specific to the vehicle's OBD terminal or a device fault.
  2. Check Vehicle OBD Fuse: Check the vehicle-side OBD-II port power fuse for a blown fuse (refer to the vehicle workshop manual).
  3. Check Connector Movement: If lightly moving the connector body while plugged into the OBD port causes the power to turn off or the LED to flicker, there is an internal connector solder joint contact defect that cannot be repaired by the user.

VCI II(2) LED Status Indicator Colors and Actions

LED Color Status Meaning Action
White VCI II(2) is powered on but not yet connected to the tablet. If this is the first-time setup or if communication fails, navigate to [Configuration → Device Manager] to establish the connection.
Green VCI II(2) is successfully connected to the tablet and communicating with the vehicle. No action needed; the device is functioning correctly.
Red VCI II(2) has lost communication. Disconnect the VCI II(2) from the vehicle OBD-II connector, wait a few moments, and then reconnect it.
Blue VCI II(2) is performing an ECU upgrade. Allow the upgrade process to complete without interruption.
Yellow VCI II(2) is in Flight Record mode, communicating only with the Trigger Module and not the tablet. To resume communication with the tablet, disconnect the Trigger Module from the vehicle power outlet (cigar jack).

When to Request Repair (Hardware Fault Criteria):

  • VCI II(2) does not power on in any vehicle or no startup beep sound is heard at all
  • VCI II(2) intermittently loses power when the OBD connector is lightly touched or repositioned (internal power board or connector solder defect)

Power-related hardware defects require internal power board inspection and re-soldering repair. Please submit your device for official repair.

Back to top

 

3. Vehicle Communication (CAN/OBD) Failure & DoIP (Ethernet) Limitation Notice

Symptom: Tablet and VCI II(2) connect normally via wireless or USB, but cannot communicate with the vehicle, Auto VIN recognition fails, ECU search shows unsupported systems, or a "Vehicle Communication Error" pop-up occurs during diagnosis.

Self-Service Workaround:

  1. Confirm that the vehicle ignition switch is in the ON (IG ON) position (many controllers do not communicate in ACC state).
  2. Verify that the vehicle battery voltage is stable.
  3. Check the vehicle's OBD port and VCI II(2) connector pins for bent pins, debris, or poor contact.
  4. Connect the VCI II(2) to a different normal vehicle to cross-check whether the issue is specific to the vehicle or a device fault.

[Mandatory Warning] Do NOT Send VCI II(2) for Repair Due to DoIP (Ethernet) ECU Upgrade Failures

  • VCI II(2) Hardware Specification Limitation: VCI II(2) does not have built-in Ethernet (DoIP) communication. DoIP (Ethernet)-based ECU upgrades (such as CCU or infotainment) cannot be performed using a standalone VCI II(2) over wireless (Wi-Fi Direct / Bluetooth).
  • Required Equipment: When performing Ethernet-based ECU upgrades, you must connect an external ECI communication adapter module or use a VCI3 (VCI III) device with built-in DoIP support.
  • Preventing Unnecessary Repair Submissions: Ethernet (DoIP) ECU update failure is not a VCI II(2) hardware defect. Submitting the unit for repair due to this reason will result in a No Trouble Found (Normal) judgment, and inspection fees and round-trip shipping costs may be charged.

When to Request Repair (Hardware Fault Criteria):

  • Basic CAN/OBD diagnostic communication and Auto VIN recognition consistently fail across multiple different normal vehicles (possible internal CAN transceiver IC fault)
  • The OBD connector pins on the VCI II(2) are visibly bent or broken

Back to top

 

4. Firmware Update Error & Interrupted Update Recovery

Symptom: While performing a VCI II(2) firmware update in KDS 2.0, the update stops at a certain percentage or displays a failure pop-up, or the device fails to operate normally after an abnormally interrupted update.

Important: Firmware Update Stability Precautions

  • Wired USB Connection Recommended: Updating over wireless (Bluetooth / Wi-Fi Direct) carries a risk of data loss; always connect the dedicated USB wired cable directly.
  • Maintain Stable Power Supply: Do not turn off the vehicle ignition (IG ON) or disconnect the device from the OBD port while the update is in progress.

Firmware Update Retry Procedure:

  1. Completely close the running KDS 2.0 app on the tablet PC.
  2. Firmly connect the VCI II(2) to the vehicle OBD port to supply power (keep IG ON), and connect it directly to the tablet using the dedicated USB cable.
  3. Launch the KDS 2.0 app.
  4. Navigate to [Configuration → Device Manager → Select VCI II → Update] in order to retry the firmware update from the beginning over the wired connection.
  5. Once the update starts from the confirmation (OK) pop-up, do not operate the tablet or device until completion.

When to Request Repair (Hardware Fault Criteria):

  • Firmware update repeatedly fails at the same progress point even with a dedicated USB wired connection and stable power supply
  • VCI II(2) does not power on or is not recognized at all in KDS 2.0 after an interrupted update (internal flash memory or mainboard damage)

Back to top

 

5. Physical Damage, Cracked Case & Warranty Seal Policy

Symptom: Cracked or broken housing/case due to drop impact or external pressure during diagnostic work, broken OBD connector pins, damaged USB port, or internal damage from water, oil, or cleaning fluid ingress.

Caution: Paid Repair Criteria & Prohibition of Unauthorized Disassembly

  • Malfunctions or physical damage caused by user carelessness (drops, impact, breakage, liquid ingress) or unauthorized disassembly/modification are excluded from free warranty coverage even within the warranty period and will be processed as paid repairs.
  • If the security seal label on the VCI II(2) body is damaged or there are signs that the case was arbitrarily disassembled, the unit may be excluded from warranty repair. Do not disassemble the unit yourself; please submit it for official repair.

Back to top

 

Quick Reference Table

Symptom Try Self-Service Check First When Hardware Repair Submission Is Required
Wireless pairing failure / Not detected in KDS 2.0 Confirm PIN 0701, clear GITMCommManager.Service data/cache and reboot tablet, check dedicated USB cable connection Not detected across multiple tablets after reboot, wired USB connection also fails (wireless board replacement required)
No power / Power turns off when moved Cross-check on another normal vehicle OBD port, check vehicle OBD power fuse, check connector movement No power in any vehicle, no startup beep, power turns off when connector is moved (power board replacement or re-soldering required)
Vehicle communication failure / Auto VIN failure Confirm vehicle IG ON and battery voltage, inspect OBD connector pins for bending/debris, cross-check on another vehicle Basic CAN diagnostic communication consistently fails across multiple vehicles (internal CAN IC or mainboard repair required)
DoIP (Ethernet) ECU upgrade failure Not eligible for repair submission. VCI II(2) does not support built-in DoIP; connect an external ECI adapter or use VCI3 (VCI III) Not a VCI II(2) hardware defect. Submitting for repair may incur inspection fees and shipping costs.
Firmware update error / Interrupted Direct dedicated USB wired connection + vehicle IG ON, then retry via [Configuration → Device Manager → VCI II → Update] Repeatedly fails at the same point over wired connection, fails to boot/recognize after update (flash memory or board repair required)
Physical damage / Liquid ingress / Broken connector pins No self-service workaround (do not disassemble) Immediate official repair submission required (user-induced damage is processed as paid repair)

Back to top

 

Official Repair (RMA) Submission Guide

If the symptom persists after completing the on-site checks and hardware inspection/repair is required, please submit your VCI II(2) through the official regional escalation channel below:

  • Official Overseas Escalation Channel: All dealers must submit repair requests through their regional Distributor / NSC. Your Distributor / NSC will then escalate and ship the device to the designated regional GIT entity: GIT America (GITA) for North America, GIT Europe (GITE) for Europe, GIT India (GITI) for India, GIT China (GITB) for China, or GIT HQ Repair Center (Korea) for General regions and Eastern European exception countries (Dealer → Distributor / NSC → GIT).
  • Detailed Procedures & Customs Rules: For regional return shipping addresses, Commercial Invoice requirements, and DAP Incoterms rules, please refer to the official Repair Process & Policies article.

Back to top

Related articles

Comments

0 comments

Please sign in to leave a comment.

Customer Support & Inquiries Dedicated Kia Diagnostic Technical Support
AI Chat How can we help you?
Submit a request
gitdocs Product Manuals