A tick is usually dependent on the CPU architecture and frequency. Maybe Ugnius can shed some light on this, but usually the safe assumption is that a tick is quick enough relatively to a combustion cycle.

The initial table is applied first CPU/ECU cycle when it detects a deviation. The incremental table is then applied every cycle there's still a deviation, and the correction amount is based on the deviation value.

So it’s impossible to get the absolute load to the maximum of 4? What happens when I supercharge my engine? At load 2 you should be well above 400bhp, so I'd struggle to get there first :) The factory ECU may have some limitations which is the reason why people go stand-alone ECU with the extreme b...

To jump from 65535 (2^16-1) to 131071 (2^17-1) you'd need one more bit, so that number will require 17 bits instead of 16 which would require fundamental design changes of the ECU logic.

You may need to go do the Advanced features and allow for unsafe values.

Take a log and make sure you have commanded AFR, actual AFR, long therm fuel trims, short therm fuel trims among the usual things. I suspect you have a leak somewhere in the intake.

The time is already there on the first column of the log.
Select the log you want to export and use the icons at the bottom of the page to export that log into CSV format. You may need to edit that file in an excel/openoffice application to trim the unnecessary intervals out.

To avoid such issues always use the graph/visualize function for your load curve (and not only load) and make sure it is smooth. If it's choppy then the ECU logic will indeed apply some corrections/interpolations to it in its continuous struggle of anticipating what's going to happen at, say, 5k rpm...

Yes, you're perfectly safe with that tune.

Just run a base OTS map and see from there. A better flowing intercooler will reduce the strain on the turbo a bit but not much, it's still going to be within the range of the WGDC tables of these tunes.