Multiecuscan

Please excuse me if I'm being dense but I can't get A KKL USB lead to work with ecuscan.

I am trying to connect to the engine ECU on a Fiat Doblo with an unmodified KKL interface.

I am using the driver which came with the lead (I have tried downloading drivers from FTDI as suggested elsewhere but the files don't seem to be executable.)

I have used device manager to reduce the transmit and receive buffers to minimum levels - there is no option for setting latency. The interface shows as being COM15.
Device manager lists the interface under 'ports (com and lpt)'.

When I run ecuscan software, the KKL shows as being on COM3 when scanning for interfaces. If i test the interface, I get...

Min latency usually 0 or 1
Max latency 2-6

1000ms timer = 1000ms
250 = about 7ms
750 = about 4ms
100 = -1ms

If i test the interface on COM15, it times out.

...I haven't got a clue what that means or how to alter any of it !

I am testing the interface without connecting it to the vehicle - is this correct ?

When connected to the car ECU, an F11 scan finds nothing.

Help please !

Hello

What Doblo you?
Because the Type 152 and Type 263 can only interface with an ELM or OBDkey
read.
Since these models are read with CAN Bus and not with KWP2000

Greetings Eddy

Wow I feel like a complete idiot I missed that when I looked at the compatability table before I ordered the lead.
Thanks, I'll get hold of an ELM.

I have since had a quick look to see exactly which type it is...I thought the type referred to the first 3 numbers of the chassis no ?

From my VIN plate, I see 186 (engine number)
223 (model/chassis number)

Do I need to look somewhere else ?

Thanks if you can help

Hello

In a type 223 with the KKL you should connect to your engine control unit get!

once more
- Com ports checked?
- KKL interface plugged in OBD socket
- Dashboard lights on
- Connect (F10)

Greetings Eddy

Yes you're right I can see it now in the list - I had discounted models listed as 'Cargo' since mine is not a van !

No, I get no connection at all and nothing showing if I scan for modules.

Anything else I could try in windows/ecuscan settings ?

Hello

Question?
- Your KKL interface properly recognized? (Windows / Control Panel)
- Have you voted in Multiecuscan / Settings / Interface, the correct interface and the correct COM port?
- Just select times, the engine control unit directly from your Doblos without the scan function

Greetings Eddy