Maximum time step

Discontinuity handling relies on submodels detecting the event that leads to a discontinuity. But the solver can take large integration steps, so a crossing event may be missed entirely if no solver step falls inside the narrow region where the event occurs.

This can happen in models with cyclic characteristics — e.g. a rotating machine with a cam profile. The cam's tabulated data spans angles in [0, 360] degrees, but a machine running at 6000 RPM rapidly accumulates far larger angle values (e.g. ~360000 degrees). If the solver takes only about one integration step per cam revolution, an aliasing effect results: the cam submodel produces a constant radius, as if the cam were a perfect circle, because the crossing/discontinuity events tied to the cam profile are never actually registered.

Mitigation: constrain the solver's maximum time step so that at least one step falls within each cyclic period, ensuring discontinuity events tied to fast-cycling phenomena are properly detected rather than aliased away.