Of course the whole logic could be delegated to the rotator drivers themselves, kind of similar to how mount drivers handle meridian flips. Actually that could probably make more sense since different rotators may have different capabilities.
That's exactly the conception behind the buildup of the rotator control in KStars. It follows the idea of subsidiarity principle: EKOS is responsible for the highest level of control (setting angles, starting rotations, calibrating, define flip policies and so on), whereas lower level functions or settings are delegated to the device. A good rotator device should manage the reversal angle in the firmware. So indeed, the right place for this setting is the device driver.

Read More...