And one small problem I came across using the new shooting plan. It works great and the chosen framing is preserved as long as the imaged area is enlarged even a little bit beyond the sensor size. In that case, the new frame can be moved and rotated to optimize framing. However, if the frame is NOT enlarged and moved away from the initial target to include other celestial objects in the frame, then the orientation of the frame is lost when the plan executes.
I experienced that while shooting the Owl nebula (M97) and also including M108 in the image. Both will fit on the sensor field without the need to enlarge the field. However, some rotation of the field and moving its center to the middle between both objects is required. By doing so, Seestar now recognizes a new object, PGC 34322 as the object the telescope is pointing at. And when the plan executes, the previously chosen framing is lost. I ended up with an image of the starfield between M97 and M108 that just neatly excluded both of my targets from the frame.
You will likely need to modify the code to preserve the programmed frame rotation. When I shoot manually, this is not a problem, only when a plan is executed.
