I believe I have setup Voyager settings correctly to get ready to image very soon. I have tested indoors in my house and things appear to work pretty well.
I know you have an A-P Mach1 and I was wondering if you ever use Meridian Delay feature either with ASCOM driver or Keypad? Anyway, my first target to image is NGC 7479 which is also known as (AKA) Superman Galaxy. The nearest star for Robofocus is Markab which is very close to NGC 7479. Initially I set the Meridian Delay to default of “0” in A-P V2 ASCOM driver. I started Voyager and connected all necessary devices successfully. Then from “On-the-Fly” window, I initiated a GoTo to NGC 7479 and the mount slewed successfully to the target. Then from the “Setup” window and from “AutoFocus” tab of this window, I clicked on “Point Closest Focus Star with RoboStar” button and it very quickly slewed to Markab star so it appears to be working very well.
Then I repeated this test by setting Meridian Delay of A-P V2 ASCOM driver to “6” so that the first slew to target object (NGC 7479 in this case), the scope would slew under the mount and I was able to do that successfully. Next was to select “Point Closest Focus Star with RoboStar” from “Setup” window, it took a really long time for Voyager to properly find the nearest RoboStar and when it finally finished calculating, it slewed to an unknown star at other side of the Meridian which was pretty far from target object.
My goal is to image NGC 7479 using Meridian Delay of “6” meaning the scope starts under the mount so that when the imaging session is finished, the scope will be above the mount and I am trying to avoid Meridian Flipping during imaging session and use RoboStar for auto focusing during the sequence. It seems that Voyager may be a little confused about Astro-Physics Meridian Delay feature when the scope is currently under the mount.
Have you every tried what I am trying and would it work? If you are not sure what I am trying to do, please feel free to ask.