Recently Browsing 0 members
No registered users viewing this page.
I have had a real problem with my AZ EQ6 GT:
I have found that the MOUNT guide rate in RA is 1/3 the guide rate in DEC. EQMOD is set to 0.9 in both axis?? This seems to have happened when I tried guiding with AA& instead of the normal PHD2?
Is there a mount direct command to alter the RA guide rate. Bit like the mount commands to dim the polar scope and set park position.
You know one of these serial commands the no one ever uses??
All the best
By Alex the great
Hello everybody on this community, very happy I recently joined stargazers lounge.com
Last November I was able to modify my EQ5 mount via shoestring astronomy GPUSB (ST4 mount-USB laptop, my guiding camera is connected to the laptop by USB and PHD2 as guiding software) so I can autoguide it for long periods 6 minutes and more, I was really happy that this project was achieved and now I can get more details out of deep sky objects.
My question is how can I go GOTO with this set up, trying to find objects to image is really time demanding without GOTO, and my goal is to take advantage of time to get those photons.
I installed already ASCOM but I didn't connect with the USB connection (I think only work with serials cable)
Thanks in advance for your valuable comments
So I routinely have issues with guiding. Last night, I was getting some solid sub exposures of 5 minutes on the Flaming Star Nebula. When it got to about 15-20minutes of the meridian, I began getting trails on my stars. Then after the flip, I was still getting trails despite PHD reporting all's well. I moved over to the Horsehead Nebula and tried 5 minutes there, and it behaved itself. Then I tested it on the Jellyfish Nebula and it also behaved (just about - minor trails). But it just did not want to dig it with the Flaming Star Nebula, which was practically near the zenith (about 2:30am 30/11/19).
I tried recalibrating PHD (I use Pulseguide so the scope knew where it was). I then also recalibrated PHD at Alnitak so it was near the celestial equator (as the PHD best practices recommend). I even checked my Polar Alignment (done with a Polemaster), which was fine. I couldn't find anything wrong.
The guide scope was slightly off alignment with the main OTA, but that wasn't making any differences before the Meridian.
I did find the helical focuser of the Starwave 50mm guide scope I was using to have some movement in it again when I manipulated the guide camera. So that's something I need to look into. But before I start throwing money at this issue, I see the terms "flexure" and "differential flexure" coming up. Can anyone shed light on what this means please?
I tried manipulating the OTA in its tube rings, that didn't yield any movement either. The piggyback scope is secure, the g/scope is secure in its rings as well, there's no movement in the OTA focus rack and the cameras are secure in their tubes.
I do have my guide rings quite far back on the body of the telescope to assist with fitting the guide scope piggyback.
Video of g/scope play:
Flaming Star Nebula. 5 minute sub, post Meridian Flip, about 2:50am (30/11/19). Note the plate solve compass in the top left. Drift appears to be in S/W direction.
Position of tube rings (they're now at the focus end).
I think I am leaning towards needing to move my tube rings (once I remember to get the tools from work).
(brand new) Skywatcher EQ6-R Pro, SW Evostar Pro 80ED, Altair 0.8x R/F, Canon 600D, Altair Starwave 50mm Guide Scope, Altair AR130 Mono Guide Cam.
By John Lawley
Hi - I've not posted here before as only just launched into this hobby, although I've always been massively interested in astronomy.
I had first light on my rig last night, which is:
Esprit 100, HEQ 5 Pro, ZWO EAF, ZWO mini filter wheel, skywatcher 50ED guidscope with ASI120, ZWO1600mm Pro, Lynx dew controller w 2 astro zap tapes
A big endeavour to get that lot working from zero experience, but I love a challenge and have really enjoyed the computer side (I'm a grade A nerd)...
So - what went well... I got the guide scope in focus (was stressing about this), and also the main scope. Even more awesomely, the autofocus routine in SGP is working perfectly Filter wheel also working perfectly and I'm getting lovely smooth pics from the main camera (I've already done the flats and darks while I was waiting for clouds to clear). Final good thing (well, good-ish), is that I got the platesolving working eventually, and was able to get the scope to align from Park to the Soul Nebula and centre fine. For some reason the "number of attempts" in my SGP profile hadn't applied, so it was giving up after 1 go, but I got it working in the end.
So the bad...
I couldn't take any data because every time it finished the platesolving and started PHD2, PHD2 would start the calibration process and then halfway through, the sidereel tracking on the EQMOD panel would turn off. Obviously, that would lead to a "lost the star" error. Is there some reason why sidereel tracking would turn off like that? I'm generally a bit confused as to whether I should be controlling the telescope from SGP (i.e. unpark) or using the park and unpark + tracking button on the EQMOD panel. Both PHD 2 and SGP are setup to use EQMOD ASCOM HEQ5/6?
So at the moment I can't do anything, because there's no way of guiding without it turning tracking off
Also I was cold. Very Very Cold.