Kevin_A
The same here the summer was already bad and from fall until now it was hardly more than a handful of nights. Since I started with a few large panoramas, it will take some time until I have collected enough data.
I also had problems with Plate Solve - the system was constantly getting lost and no longer knew where it was. Sometimes nothing helped and then, as if by magic, everything worked again the next time. Currently I only have the problem that the correct object is not named in the autorun, every object is named Polaris.
The problem is obvious: with AsiAir, ZWO wants to appeal to a wide audience. But with more compatibility comes more and more problems. Instead of solving the problems, new products are constantly being brought onto the market. It will be fun when an AM7 comes along, which will appeal to a different audience.
There can be problems with any product. It just depends on how the manufacturer reacts.
ZWO can now benefit free of charge from our experience in optimizing guiding. And the only right thing to do is to inform the users. A blog post with a tutorial would be the first step. Simply inform that this type of mount behaves differently, explain the correlations and name new standard settings as a starting point.
In a second step, this must be transferred to AsiAir. If an AM5 / 3 is connected, other basic settings must be displayed and, over time, further options for optimizing the system.
