That would assume the resulting FOV is going to be inverted, so there needs to be some kind of an acknowledgement from the user they are OK with that. The "preserve rotator angle" checkbox in the meridian flip options could be adapted for that purpose (when checked it kind of assumes the user is OK with flipped images).

Once we have this and Ekos needs to change the rotator angle beyond the rotation limits:
1. Ekos tries to move the rotator to position x
2. Rotator drivers could return some special code/enum to indicate rotation request is rejected because of the limits.
3. Ekos instructs the rotator to move to position (x - 360). Or switch the rotator to the "reverse" mode and move it by the needed amount.

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.

Read More...