Hi everyone,
I fully agree with the observations made in this thread regarding the behavior of the CAA after a meridian flip. The automatic 180° rotation is often unnecessary and, in many cases, actually doubles the workload, since we’re forced to capture flats for both orientations. This also complicates the calibration and processing workflow in tools like PixInsight.
The current “180° only” option is not sufficient. In practice, we still see rotations greater than 270°, which can be dangerous for cabling and the optical train. The CAA logic must be improved to always choose the shortest path and avoid excessive movement.
It's also crucial that the CAA does not rotate within the same session unless the user explicitly requests it. This is key to maintaining consistent framing and avoiding unnecessary interruptions.
Some additional improvements that I consider essential:
Allow users to enable or disable automatic rotation after meridian flip.
Let us define a manual reference position ("home" or 0°) and set limits for movement, for example ±90°, to prevent cable snags or potential collisions.
Give the option to disable rotation when slewing to a target using SkyAtlas, as sometimes we only want to point without altering the camera angle.
Include the rotation angle in the filename or FITS header, which is extremely helpful when stacking images from different sessions or nights.
Thanks to the ZWO team for listening to the community. I hope these enhancements can be implemented soon so we can fully enjoy the CAA’s potential without sacrificing reliability or workflow efficiency.
Clear skies!