nice, i love it when it isn't my code's fault.

kur4o could we get around that? dump the timer ram to see if its active and wait if it is? whats its location?

the only difference between getting ready for read or write is we don't upload the code to set VPP voltage for read (since it's not necessary), i can't imagine that has any effect

that sucks, maybe i broke flash read at some point, but i don't remember changing it. i don't think many people use it

your original bin will probably be in here, no need to read it
...

i should also mention the knock events near 20-25 map column are mostly during decel, and not much actual knock retard will occur from those

your log is a good example of a well running maf engine with really mild modifications that probably doesn't need much tuning.

load both your logs into eehack at the same time and run the analyzer...