What interface are you using?
There are too many factors that ISTA P could fail... and it's one of the reasons why I dislike ISTA P in the first place.
If you have a working WinKFP with new daten, you would just need a flash of the DME, coding and then DME-CAS align and you're set.
You changed the DME for misfire reasons?
Based on those rock steady KL15 and KL30 values, I'm guessing either an emulator is at play, or a voltage simulator was used in place of a power supply. To use ISTA-P, you really need to be using an ICOM and a strong power supply.
Last edited by RocketSurgeon; 02-17-2017 at 01:24 PM.
I'm assuming you're using a D-CAN cable. There's a bug with the stock firmware on those that causes faulty data to be written to the MSS6x DMEs when flashing ('06' is written every 253 bytes instead of the correct data). That naturally causes the signature check to fail.
Either flash using an ICOM interface or update the ATMega chip on your cable with the firmware from the Ediabaslib project. Use the instructions under step 2 here: https://ediabaslib.codeplex.com/wiki...ringTitle=Home (ignore all the bluetooth stuff).
Yep, probably why I bricked an 08 M5 SMG module 2 years ago trying to flash with K+DCAN.
I've upgraded since. Omitec, ICOM, etc.
Ah, so it's more of a firmware issue..
I had assumed it was a lack of buffer memory to maintain speed... or along those lines. My Omitec cable has a 29F400BB chip inside, which I assumed was there to help. But I'm not experienced enough to know. Useless now to try to convert my K+DCANs.