I’ve noticed that if I set the minimum time increment for the *Static step lower than 1e-5 x time period of the step, the solver ignores this and doesn’t reduce the time increment below 1e-5 anyway. Because of that, it’s possible to end up with “increment size smaller than minimum” error message even when the current time increment is far from what was set as minimum. For example, in one analysis I set minimum time increment to 1e-9 (time period was 1) and I got the aforementioned error message when time increment reached only 0.329e-5.
my intention is that the lowest minimum time increment is 1.e-6 of the time step for a *static problem and 1.e-10 for a *dynamic problem. This was not very consistent so far (sometime 1.e-5 was used) but I changed that now in my development code. The reason for these limits is that if the calculation does not converge for a time increment that small, it usually means that something is wrong with the model and it will seldom converge for an even smaller value. Furthermore, the limits can be circumvented by subdividing the step into smaller steps.