Please help to clarify.
If in a model-based mount I set in the Voyager mount setup the flag “(*) Not Sync Mount on Synced Point”, what happens when Dragscript calls for a Platesolve with Sync? Does the latter override the former or is the “no sync” preserved? Yet the Dragscript command should sync the rotator position, yes?
Though I thought I understood this, because my model recently went haywire, I think I would benefit from further understanding anc clarification.
Thank you.
A couple of questions to understand your reasoning:
- what do you need the plate solve with sync out of the sequence if you have a model?
- why do you need to manage the rotator out of the sequence? Do you have to calibrate the guide before the sequence, i.e. out of the sequence?
Answer to your question
what happens when Dragscript calls for a Platesolve with Sync
Voyager will do a plate solve and sync the mount to the coords found. If you have a model the mount driver can do this : (1) add point to the model (2) throw and exception/error and do nothing (3) destroy your model. If you need a plate solve out of the sequence use the Plate Solve Block
Yet the Dragscript command should sync the rotator position, yes?
No, you must use the precise pointing with rotator or leave sequence do it for you
Though I thought I understood this, because my model recently went haywire, I think I would benefit from further understanding anc clarification.
Do not sync if your model/driver doesn’t accept sync like a model point refine ! To know features of your driver you must refer to the brand support/documentations
the
(*) Not Sync Mount on Synced Point”
writing do not exist in Voyager !
If you refer to this 
, this flag remove sync in all the operations inside Voyager excluded the dragscript blocks “Plate Solve with Sync” and “Blind Solve with Sync” which are functions expressly desired by the user and is useful to create a model.
Leo,
Thank you for the very detailed answer. Helpful!
Though my scripts and my runs have been operating essentially flawlessly, it turns out that I did have some misunderstandings, nevertheless. So thank you very much for clarifying.
FYI, I am mostly using 10Micron2000 with Voyager. (I have other mounts as well but they are encoded mounts that behave similarly, such my L-mounts)
Here was my thinking: The only time I felt I needed a Platesolve or Blindsolve in my script was at the beginning of a night’s session (particularly if the mount had been unpowered) to assure that there is a handshake between the mount and the actual sky. I was thinking that was “required” to assure that the mount (and its model) was aligned with the sky.
To answer your first 2 specific questions: 1) I don’t and 2) I don’t. But because of a misunderstanding I had thought otherwise.
Some of our confusion(s) come from using previous software that operated less elegantly than Voyager.
Again, thank you
In this case use the Plate Solving or Blind solving blocks (the ones without sync)
All the best
Leonardo