Multiplication of hits if readout is running too long

When running a scan, that has a lot of data and/or where the readout is active for a long time, hits are probably mapped to the wrong scan paramters. This results for example in stacked scurves in a threshold scan of the full linear front end with VCAL_step size of 5:

This might be the result of an overflowing counter?