Kev11
31-10-2013, 09:14 PM
Without GoTo I would not have considered observing double stars because of the time costs of star hopping or using setting circles. The other problem with double stars, as experienced observers will know, is the archaic and esoteric nomenclature based on discoverers’ names. Eventually, I worked out, as I am sure many others have, that with the help of Simbad, most (not all) can be associated with SAO numbers.
So far, so good: SynScan has SAO Catalogue in my version (3.27). The problems started almost as soon as I began in the observatory – there are gaps in the SAO list in my SynScan e.g. nothing between 288103 and 288827 and lots of other, seemingly random, “missing” stars. It doesn’t seem to be related to magnitude since SAO194544 mags. 8.5 & 8.5 is there; SAO168011 mags. 6 & 8 is not.
I wonder whether anyone can throw some light (sorry!) on this? Is it a possible problem with my SynScan? Is it another example of the neglect of the Southern skies by Northern hemisphere suppliers (it took me ages and lots of searching IIS forums to finally twig that the Octans asterism in the polar scope on my HEQ5 was upside down in the home position as shown in the manual)?
While I am on this subject: is it a fact that SynScan will only slew to objects in its database? To get around the missing SAO numbers I attempted to enter the RA and Dec coordinates, which only seems possible through the User Objects function, another frustration, by the way. SynScan would not respond to coordinates which didn’t match something in one of its catalogues.
I would rather not use a laptop to drive the scope with Stellarium or similar because of the extra power supply issues, but mainly because even the dimmest red screen plays havoc with the dark-adaption of my elderly eyes.
Any help or explanation gratefully received.
So far, so good: SynScan has SAO Catalogue in my version (3.27). The problems started almost as soon as I began in the observatory – there are gaps in the SAO list in my SynScan e.g. nothing between 288103 and 288827 and lots of other, seemingly random, “missing” stars. It doesn’t seem to be related to magnitude since SAO194544 mags. 8.5 & 8.5 is there; SAO168011 mags. 6 & 8 is not.
I wonder whether anyone can throw some light (sorry!) on this? Is it a possible problem with my SynScan? Is it another example of the neglect of the Southern skies by Northern hemisphere suppliers (it took me ages and lots of searching IIS forums to finally twig that the Octans asterism in the polar scope on my HEQ5 was upside down in the home position as shown in the manual)?
While I am on this subject: is it a fact that SynScan will only slew to objects in its database? To get around the missing SAO numbers I attempted to enter the RA and Dec coordinates, which only seems possible through the User Objects function, another frustration, by the way. SynScan would not respond to coordinates which didn’t match something in one of its catalogues.
I would rather not use a laptop to drive the scope with Stellarium or similar because of the extra power supply issues, but mainly because even the dimmest red screen plays havoc with the dark-adaption of my elderly eyes.
Any help or explanation gratefully received.