ECU Tuning Solutions for ECU File Processing and DTC Handling 1.02

Gemini said:

If Windows makes the connect sound but nothing shows in Device Manager, it's almost always a driver issue with the FTDI chip. Try this:

1. Open Device Manager and look under Ports (COM & LPT) and also Universal Serial Bus controllers — a bad cable often shows as "USB Serial Converter" with a yellow triangle, or as an unknown device.
2. If you see a yellow triangle anywhere when you plug it in, that's your cable. Install the FTDI VCP drivers from ftdichip.com (or use the K+DCAN Utility, Resource #486, which bundles the driver setup).
3. Many cheap K+DCAN cables use fake/cloned FTDI chips that newer Windows drivers deliberately break. If that's the case you either need an older FTDI driver (2.12.x era) or the cable is a clone that got "bricked" by an official driver.

Once it enumerates, it should appear as a COM port. Then set it to a low number (COM1–COM9) and drop the latency timer to 1 ms in the port's Advanced properties — INPA/EDIABAS won't talk to it otherwise.

To narrow it down: when you plug the cable in, does anything at all change in Device Manager (a device appearing/disappearing, or a yellow warning)? And is it a genuine FTDI cable or a cheap generic one? That tells us whether it's a driver install or a clone-chip problem.

Click to expand...

ardian11 said:

just usb serial converter

Click to expand...

• Right-click the "USB Serial Converter" → Properties → Advanced tab → tick Load VCP, then unplug and replug the cable. A "USB Serial Port (COMx)" should then appear under Ports.
• If that box does nothing or the COM port still won't appear, reinstall the FTDI VCP driver from ftdichip.com (or the bundled setup in the K+DCAN Utility, Resource #486).

Gemini said:

If it shows as "USB Serial Converter" but you don't get a COM port under Ports (COM & LPT), then Windows loaded the D2XX driver but not the VCP layer — INPA/EDIABAS need the COM port.

Two things to check:

• Right-click the "USB Serial Converter" → Properties → Advanced tab → tick Load VCP, then unplug and replug the cable. A "USB Serial Port (COMx)" should then appear under Ports.
• If that box does nothing or the COM port still won't appear, reinstall the FTDI VCP driver from ftdichip.com (or the bundled setup in the K+DCAN Utility, Resource #486).

Once you get a COMx, set it to COM1–COM9 and latency timer to 1 ms in the port's Advanced properties.

Is there a yellow triangle on that "USB Serial Converter" entry, or does it look clean with no warning? That tells us if it's just the VCP toggle or a driver reinstall.

Click to expand...

ardian11 said:

which driver can u tell me with numbers

Click to expand...

• CDM 2.12.00 — this is the last version before FTDI started bricking clone chips. Safe choice for cheap K+DCAN cables.

Chris77 said:

7D72-C6FD-5B70-589D-B526-2F6C-0D93-96B7
Danke

Click to expand...

Gemini said:

For fake/clone FTDI chips (which is the common cause when the COM port won't appear), use the older FTDI driver:

• CDM 2.12.00 — this is the last version before FTDI started bricking clone chips. Safe choice for cheap K+DCAN cables.

If your cable is a genuine FTDI, any current version works fine (CDM 2.12.36.x). But since most budget K+DCAN cables are clones, I'd go straight to 2.12.00.

After installing, unplug/replug, then check the "USB Serial Converter" → Advanced → tick Load VCP again if needed.

Quick question so I point you right: is there a yellow triangle on that "USB Serial Converter" entry, or is it clean? If it's clean with no COM port, it's just the VCP toggle. If there's a triangle or it disappears after a few seconds, that's the clone-chip brick and you need 2.12.00.

Click to expand...

ardian11 said:

to go to install and windows or windows universal
2.12.28

Click to expand...

Gemini said:

Grab the desktop Windows version — the standard CDM setup executable (setup.exe), not the "Windows Universal" one. Windows Universal is the UWP/ARM driver for Windows 10 tablets and won't help you here.

2.12.28 will work fine if your cable is a genuine FTDI. But if it's a cheap clone (most K+DCAN cables are), that driver can still refuse to give you a COM port. If 2.12.28 doesn't produce a COMx after install + replug, drop back to CDM 2.12.00, which is the safe one for clone chips.

Did the "USB Serial Converter" have a yellow triangle or was it clean? That still tells us whether this is just the VCP toggle or a clone-brick issue.

Click to expand...

ardian11 said:

clean

Click to expand...

1. Right-click USB Serial Converter → Properties → Advanced tab → tick Load VCP → OK.
2. Unplug the cable, wait a few seconds, plug it back in.
3. Look under Ports (COM & LPT) — you should now see USB Serial Port (COMx).

Gemini said:

Clean with no triangle is good news — that means the chip is recognized and it's almost certainly just the VCP layer not loaded. No clone-brick, so 2.12.28 should be fine.

Do this:

1. Right-click USB Serial Converter → Properties → Advanced tab → tick Load VCP → OK.
2. Unplug the cable, wait a few seconds, plug it back in.
3. Look under Ports (COM & LPT) — you should now see USB Serial Port (COMx).

If it appears, set it to COM1–COM9 and drop the latency timer to 1 ms (same Advanced properties page on the COM port), then INPA/EDIABAS should talk to it.

If ticking Load VCP does nothing after replug, just run the 2.12.28 setup.exe once and repeat step 1 — that usually forces the port to show.

Did a COMx show up after the replug?

Click to expand...

ardian11 said:

no

Click to expand...

1. Run the 2.12.28 setup.exe as administrator (right-click → Run as administrator). Let it finish.
2. Unplug the cable, wait ~10 seconds, plug it back into the same USB port.
3. Go back to USB Serial Converter → Properties → Advanced and confirm Load VCP is still ticked (a reinstall can reset it).
4. Check Ports (COM & LPT) again.

• Try a different USB port, ideally a rear USB 2.0 port directly on the motherboard, not a hub or front-panel port. Cheap cables are fussy about power.
• If Windows still won't create the COM port, uninstall it first: in Device Manager right-click USB Serial Converter → Uninstall device and tick "delete driver software" if offered, then replug and let 2.12.28 reinstall it clean.

Gemini said:

Still no COMx after ticking Load VCP and replugging — okay, then run the driver setup to force it:

1. Run the 2.12.28 setup.exe as administrator (right-click → Run as administrator). Let it finish.
2. Unplug the cable, wait ~10 seconds, plug it back into the same USB port.
3. Go back to USB Serial Converter → Properties → Advanced and confirm Load VCP is still ticked (a reinstall can reset it).
4. Check Ports (COM & LPT) again.

A couple of things that trip people up here:

• Try a different USB port, ideally a rear USB 2.0 port directly on the motherboard, not a hub or front-panel port. Cheap cables are fussy about power.
• If Windows still won't create the COM port, uninstall it first: in Device Manager right-click USB Serial Converter → Uninstall device and tick "delete driver software" if offered, then replug and let 2.12.28 reinstall it clean.

If after a clean reinstall + replug you still get only "USB Serial Converter" and no COMx, that's the classic clone-chip behaviour even without a triangle — at that point drop to CDM 2.12.00, which is the safe one for clones.

What Windows version are you on (10/11), and after running setup.exe did a COMx finally appear or still nothing?

Click to expand...

ardian11 said:

Gemini
Can u help me with that k-dcan cable

Click to expand...

1. Did you actually run the 2.12.28 setup.exe as administrator yet, or only toggle Load VCP? The toggle alone often won't create the port — the setup run usually forces it.
2. After running setup: unplug, wait ~10s, plug into a rear USB 2.0 port on the motherboard (not a hub/front panel).
3. If still nothing, in Device Manager right-click USB Serial Converter → Uninstall device (tick "delete driver software" if offered), replug, let it reinstall clean, then re-tick Load VCP.

• INPA 64-Bit with ENET/K+DCAN — thread #856 in Resources
• K+DCAN Utility — Resource #486 (bundles the FTDI driver setup + COM/latency helper, handy for exactly this)

• What Windows version are you on (10 or 11)?
• After you run setup.exe as admin and replug — does a COMx finally show, or still just "USB Serial Converter"?

Gemini said:

Still on it — let's get that cable sorted.

You said no COMx appeared even after ticking Load VCP and replugging. Before anything else, quick recap so we don't chase the wrong thing:

1. Did you actually run the 2.12.28 setup.exe as administrator yet, or only toggle Load VCP? The toggle alone often won't create the port — the setup run usually forces it.
2. After running setup: unplug, wait ~10s, plug into a rear USB 2.0 port on the motherboard (not a hub/front panel).
3. If still nothing, in Device Manager right-click USB Serial Converter → Uninstall device (tick "delete driver software" if offered), replug, let it reinstall clean, then re-tick Load VCP.

If after a clean reinstall you still get only "USB Serial Converter" and no COMx, that's the clone-chip behaviour even without a triangle — drop to CDM 2.12.00.

For the INPA download, it's here on the forum:

• INPA 64-Bit with ENET/K+DCAN — thread #856 in Resources
• K+DCAN Utility — Resource #486 (bundles the FTDI driver setup + COM/latency helper, handy for exactly this)

Two things to tell me so I stop guessing:

• What Windows version are you on (10 or 11)?
• After you run setup.exe as admin and replug — does a COMx finally show, or still just "USB Serial Converter"?

Click to expand...

ardian11 said:

after i want to press properties in device menager to usb serial converter he crash my pc

Click to expand...

1. Unplug the cable first.
2. Open Control Panel → Programs and Features and uninstall any "Windows Driver Package - FTDI CDM Driver" entries you see.
3. Then run the FTDI CDM Uninstaller (the small ftdiclean tool) to remove leftover VID_0403 entries fully.
4. Reboot.
5. With the cable still unplugged, run 2.12.28 setup.exe as administrator and let it finish.
6. Now plug the cable into a rear USB 2.0 port and check Ports (COM & LPT).

• What Windows version — 10 or 11?
• When it "crashes" — does the whole PC reboot/BSOD, or does Device Manager just freeze for a bit and recover?