Page 1 of 1

No Connection to ECU via K-Line Adapter – Fiat Barchetta

Posted: 10 Jun 2025, 06:38
by dominicgroza72
Hello everyone,

I'm trying to connect to the Engine ECU on my Fiat Barchetta using a 3-pin adapter connected to a K-Line interface (via USB). I'm using MultiECUScan, which successfully detects the USB interface, but when I try to connect to the ECU, I get no response. FiatEcuScan gives the same results

Just to clarify:

Ignition is ON
Adapter is connected to the 3-pin diagnostic port
Interface is recognized in MultiECUScan

i've installed ftdi drivers, set the port to com5 (seen on some threads), set the latency timer to 1msec.
I've attached some photos that show my actual settings.

Has anyone run into this issue before? Could it be a wiring issue, incorrect adapter, or something else I'm missing?



Thanks in advance for any help or suggestions!

Re: No Connection to ECU via K-Line Adapter – Fiat Barchetta

Posted: 10 Jun 2025, 07:51
by s130
Are you sure you have the correct COM port. To check go to Windows Device Manager and see which port the KKL interface is actually connected to.

These is also in MES settings the Scan For Interfaces button.

If you can see the KKL device in Device Manager but MES can not locate then you need to resolve this problem first.

Re: No Connection to ECU via K-Line Adapter – Fiat Barchetta

Posted: 10 Jun 2025, 12:41
by dominicgroza72
s130 wrote: 10 Jun 2025, 07:51 Are you sure you have the correct COM port. To check go to Windows Device Manager and see which port the KKL interface is actually connected to.

These is also in MES settings the Scan For Interfaces button.

If you can see the KKL device in Device Manager but MES can not locate then you need to resolve this problem first.
Yes, i am sure. MES locates the port, when i Scan for Interfaces

Re: No Connection to ECU via K-Line Adapter – Fiat Barchetta

Posted: 10 Jun 2025, 16:52
by s130
Try using a slower BAUD rate. Try 9600 and other rates.

Re: No Connection to ECU via K-Line Adapter – Fiat Barchetta

Posted: 11 Jun 2025, 08:51
by dominicgroza72
Looks like i was trying to connect to a different module than the one selected in MES. I was connected physically to the ABS module but in MES had Engine selected. It all works now :D