All axis controllers are expected to use TAI date to understand and process tracking commands, which contain a position, a velocity, and a time at which the position applies. Tracking commands specify a path of constant velocity:
Where position0, velocity0 and tai0 are the values in the track command.
The axis controller is expected to interpolate between adjacent tracking commands, so that the commanded path is more complicated than the equation shown above. But to do that interpolation correctly, it is necessary for the axis controller to know the current TAI date.
Unfortunately it appears that the rotator does not know anything about TAI time. It should read time from the CLOCK_TAI system clock for processing track commands.
It would also be helpful if it used CLOCK_TAI for other times, such as the timestamp in the telemetry header. The standard unix real time clock (which is what the rotator is using) is not well defined near a leap second, whereas CLOCK_TAI is completely uniform and unaffected by leap seconds.