Amaranthus
08-06-2014, 02:19 AM
I had a go tonight at using 'Alignmaster' software to polar align my new AZ-EQ6 mount. But I had some strange behaviour.
I started with my mount level and approximately polar aligned (done via my iPhone's clinometer and compass). [The polar scope is not useful in my current location - Sigma Octantis is blocked by an unfortunately positioned tree!).
What worked:
I started my Synscan handset up, entered all the correct site coordinates, skipped the handset alignment, and switched to PC Direct mode.
I then kicked off Alignmaster, made sure my EQASCOM was working/communicating okay, and set about targeting/centreing two stars chosen from Alignmaster's list. This went fine -- using the GOTO button in Alignmaster, they were duly placed within the field of view of my finder RDS, and so centreing in the 12mm reticle eyepiece was no problem.
What didn't work:
Alignmaster then reported that I was about -1.5 degrees out in AZ and 55 minutes out in ALT. It then prompted me me to begin the polar alignment procedure. It slewed away from the target star, and told me to adjust my ALT to re-centre it in the reticle. This is where things went badly. You see, just adjusting my altitude winch would not centre the star. I had to adjust both ALT and AZ knobs to get it centred. The same deal when I tried to align the AZ. It slewed away from the target star again, but just adjusting AZ was not sufficient to get the target re-centred.
I tried repeating this on 5 or 6 different pairs of stars. By doing the dual ALT and AZ adjustment each time, I was, iteratively able to get the error down to about 10-15 min. But I always had to do the dual ALT-AZ adjustments.
So what has gone wrong? I would have thought the ALT alignment would have only slewed the scope in the ALT direction, and converse with the AZ.
There is only one possibility I can think of at present. Alignmaster asks for my time zone, which is +9.5 (Adelaide) but it won't accept this entry and reverts to +10. Would this 30 minute time error cause the above problem??
Has anyone encountered this before, or knows of a 'fix'? It otherwise seems like pretty useful software, if I can figure this out!
I started with my mount level and approximately polar aligned (done via my iPhone's clinometer and compass). [The polar scope is not useful in my current location - Sigma Octantis is blocked by an unfortunately positioned tree!).
What worked:
I started my Synscan handset up, entered all the correct site coordinates, skipped the handset alignment, and switched to PC Direct mode.
I then kicked off Alignmaster, made sure my EQASCOM was working/communicating okay, and set about targeting/centreing two stars chosen from Alignmaster's list. This went fine -- using the GOTO button in Alignmaster, they were duly placed within the field of view of my finder RDS, and so centreing in the 12mm reticle eyepiece was no problem.
What didn't work:
Alignmaster then reported that I was about -1.5 degrees out in AZ and 55 minutes out in ALT. It then prompted me me to begin the polar alignment procedure. It slewed away from the target star, and told me to adjust my ALT to re-centre it in the reticle. This is where things went badly. You see, just adjusting my altitude winch would not centre the star. I had to adjust both ALT and AZ knobs to get it centred. The same deal when I tried to align the AZ. It slewed away from the target star again, but just adjusting AZ was not sufficient to get the target re-centred.
I tried repeating this on 5 or 6 different pairs of stars. By doing the dual ALT and AZ adjustment each time, I was, iteratively able to get the error down to about 10-15 min. But I always had to do the dual ALT-AZ adjustments.
So what has gone wrong? I would have thought the ALT alignment would have only slewed the scope in the ALT direction, and converse with the AZ.
There is only one possibility I can think of at present. Alignmaster asks for my time zone, which is +9.5 (Adelaide) but it won't accept this entry and reverts to +10. Would this 30 minute time error cause the above problem??
Has anyone encountered this before, or knows of a 'fix'? It otherwise seems like pretty useful software, if I can figure this out!