[inspi1981]

I did it at least 20 times with cable from Alli without issue

[darknmy]

I did it at least 20 times with cable from Alli without issue

I think it's a USB issue or I might be very unlucky with a shit ftdi chip. though it's not a white board or ftdi clone.

I had this issue on USB modems and USB HUBs. USB is very sensitive so to speak...

Nevertheless I've learned something - don't fuck around with Ecus that will stop your car.

Serial - OBD2 cable would be

[Enabled]

The person you talked to is over reacting.

K-line communication is simple RXD/TXD serial communication. A proper usb KKL cable or proper K+DCAN can handle it just fine. It's when we get to low and high speed CANBUS that I warn people not to use cheap K+DCAN to flash. Big difference between K-Line and CANBUS.

[darknmy]

What a freaking nightmare this was...

I connected DME and the guy for 1h got only errors and could not do shit. So he says to me - take it out, I will try to restore it from BDM or smtn.
I take it out and see pin 32 bent. Now, he says, you're fu*ked.

Because I was trying to connect on the desk, pin 32 was not aligned and got bent after connecting.

Now lucky me I managed to carefully straighten it, open DME, push the pin out. Put all back in and carefully connect.

Vuala motherfu*ker the Ecu write began.

For some reason I had wrong config and the guys computer did not get errors. He told that I could fix it if I would look for it for days. Eventually I would find the problem.

#FML -120€ and 2h work

[Enabled]

Was he kind enough to tell you what your config problem was?

Glad it's resolved though.

[darknmy]

Not really. I saw he used 14400 bps Com1 and 1ms latency K+DCAN usb cable.

He manually copied all contents SP-DATEN to EDIABAS, NFS and INPA, then he imported all the data to WinKFP

Something with the config on my side was off. either sp-data or ediabas version or conf, though I had Hardware=obd and everything