Recently Browsing 0 members
No registered users viewing this page.
I'm super happy to have found this forum of night sky enthusiasts and look forward to learning and sharing on this site! I am an amateur stargazer fortunate to live in a rural area with great dark skies. I'm used to using a GoTo Celestron.
Unfortunately I'm having a problem with a newly purchased Orion SkyQuest XTg 10.
I've only used it a couple of times. Recently, when I turn on the power, the hand controller (a SynScan V4 GoTo, version 04.39.04) states a message "Both axes...no response!" which means the motors won't work.
I've unplugged all the cords & replugged to no avail. The power comes from a new Orion Dynamo Pro, 12 V, Lithium Power Supply which was recommended.
Does anyone have any ideas what the problem might be?
Thank you 🌟
For deep sky observations, can you make suggestion which will be more fitted with my behavior: mobility is not a big concern as a least 11" aperture is must whereupon computerized stuff is no good choice for me.
The Tadpole Nebula and the Flaming Star Nebula captured over three nights of the unexpected nice weather we had a couple of weeks ago.
A number of firsts with this image:
1. My first mosaic - keeping it simple with two panes!
2. First time I left my imaging rig outside... (I used a telegizmo cover) and it was perfect, allowing me to get imaging very quickly on each night
3. First time using powerful scripting tools in my capture software, APT, to move to the second pane and starting imaging automatically...worked really well!
APP was used for pre-processing and stitching the mosaic together, while Pixinsight was used for image processing. A total of 10.9 hours integration time.
Full details on Astrobin
Thanks for looking!
Like the lunatic that I am, I decided to get the scope out last week during that storm that was passing through. The skies were clear and there was no moon about, so I figured why not! Only problem was the 17-20 mph winds, lol.
I got 2 hrs of subs but had to throw away half of them due to guiding problems more so than the wind, amazingly. This was the 2nd time in a row i'd had Dec guiding problems, and that's after about 2 years of not having a single problem guiding. After the 1st hr of wasted subs, I turned off Fast Switching in Dec and chose to only Dither in RA, and the Dec problems mostly went away, at least to allow me to capture 1 hr of 'still dodgy but just about useable' subs. Once M42 disappeared behind the neighbour's roof, I then re-calibrated on the Celestial Equator (Dec 0) and when I switched to the Pinwheel Galaxy I was able to guide as normal again (with Fast Switching and Dithering in both RA and Dec both turned on again) and didn't lose any subs, despite the wind, so I've decided that from now on I won't be calibrating at the target itself, i'm always going to do it at Dec 0.
I decided to throw this in with another 1 hr of subs (plus 10 x 30s for the core) that I took back in Jan 2017 (has it really been that long?!). That hr also had issues, with some weird streaking in the lower left that I could never work out what caused it. The D5300 hadn't been modified at that stage either. So I fired it all in to APP and decided to stack it anyway, and give it a quick process. Then chose to crank it up to 11 on the colour front, just for laughs.
It won't be going on the wall anytime soon, lol, but I suppose it came out a bit better than I was expecting, all things considered.
20 x 360s with an IDAS-D1
D5300, 80ED, HEQ5-Pro.
Stacked in APP, processed in PS.
edit - I forgot to downscale it - so no pixel peeping allowed ?