There are a lot of scheme on ista-d unfortunately I'm not able to understand them 
.
P.s. CarlOs have You tested improvements after upgrading the Ecu with ista_p?
I'm hesitant, Ista-p indicates that I've an old map on both engine and frame ecu; but the bike hasn't problems. I saw that usually ista-p fails and You've to use Winkfp to arrange them.
Hi
Well, I did do the Ista-P programming, and yes, I also had the DWA / Alarm flash failure and had to use Winkfp, but it was fine. There's a youtube video of me doing it and not really knowing what I'm doing as it's my first time.
Not sure I noticed any real differences though.
I have the Kess v2 & K Tag and they can do checksum correction, so I can read/modify/flash the ECU, but I don't have a good knowledge of the maps themselves. I'm working on a datalogger project at the moment so I can get lots of stuff recorded before I try to modify maps. Hopefully by the time I come to modify maps, I'll have a better understanding of how it all works. I know it's purely alpha-n, with fuel trim corrections in closed loop which I think are used to calculate typical BMW style additive & multiplicative trims which operate over the full range (i.e. including open loop). Those trim values can be read with tool32 / testo / kwp2000 anyway (kwp2000 $22 $40 $00 for analog values or 44,40,04 .. one is analog one is digital...)
My data logger should give me important stuff like (AFR (actual, from Zeitronic/wideband)), fuel trims, whether it was operating in open loop or closed loop, ignition angle, injector duration, etc. Oh and road speed, engine temperature, and throttle position of course.
It would be nice to find the bits where I don't like how it rides (part throttle cruise), and see what it's doing and maybe what I can set my sights on figuring out how to change.
I know people already offer remaps but it's a learning exercise on my 60,000 mile bike
