I reviewed this thread because of your post. I am not addressing the flip topic of the thread but, rather, the “sync” aspect. I advise a different 10Micron ASCOM driver setting than that shown by RobertM. I happen to do my model in Model Creator and, as he stated, I want to leave that model alone and untouched. It is important to assure that you leave UNCHECKED the box “Use Sync as Refine” but you still should allow for “Enable Sync” by leaving that Checked. (Surely both boxes are checked during the construction of the model, which I happen to do only once, manually, and outside of Voyager).
For reference, I happen to operate unguided. My GM2000 has operated and pointed flawlessly for well over a year with various automation software and, of course, Voyager. The mount’s model remains stable, unaltered, and uncorrupted. I hope these settings (shown below) are correct and I hope are helpful. My presumption is basic: you want to allow Voyager to allow that the coordinates of the driver are synced to the mount (and are based on the “solve”).
Pana, I think this is essentially answering your question but I view it somewhat differently.
I use MW4 for my model and I also do unguided without problems. My question about the sync has more to do if you indeed need to uncheck any box on the sync thread of the ascom driver. Voyager has an option in the mount thread do not sync mount on solved point. So if voyager doesn’t try to sync the mount why do we have to uncheck the box? The rest you wrote and I understand und do exactly like that. But this play with the ascom driver checking the box to do the model and unchecking for voyager is what I don’t understand.
I think you are talk about this, if you check this flag Voyager never send a sync to the Mount driver in any place where the precise pointing are asked (onthefly,sequence,focusing … etc etc) and will use the closed loop pointing by offset.
If you are using a model and you cannot add or you dont want to add point for refine the model when Voyager ask a sync to mount then flag on Not Sync (Pointing Model Running) option
If you remove the Enable Sync at driver level and continue to use the Sync at Voyager level probably an exception will thrown at driver level.
