[Shane@DBPerformance]

The 1G and 2G have the same 1600hz logging problem due to the hz only being a single byte 8-bit value. The trick done on the 1Gs to get high hz logging was to change the code in the ECU to divided the outputed Hz value in half before putting it to the datastream and then running a modified logger like MMcd that knew to multiple the value by 2 before displaying it. That trick upped the logging limit to 3200hz.

I can tell you how to remove the boost cut limiter or raise it up, if you want to. I put it at that level on purpose incase of overboost. If you airflow gets much higher though, then the boost cut won't be of any use. Eventually you outflow the max value even allowed for the boost cut table.

You could try pulling some timing out or richening it up in the are where it knocks, but you really don't seem to be getting a huge benefit from the alky. And up top where it is running plenty of timing, it wasn't knocking much at all in that log.