Recently Browsing 0 members
No registered users viewing this page.
I would like to share my third image.
I finally had a "lucky week", since my last session, December 18th. I managed 5 clear nights out of the past 6 (has to be a record, at least for me and my area) and I was able to finish a couple of projects I had started long ago and start a few new ones.
This is M33, also known as the Triangulum Galaxy, taken over 10 nights, under my Bortle 5/6 home sky.
Total integration time: 10h 14m 00s.
Here are the acquisition details:
Mount: Sky-Watcher NEQ6 Pro
Telescope: Tecnosky 80/480 APO FPL53 Triplet OWL Series
Camera: D5300 astromodified
Reducer/flattener: Tecnosky 4 elements, 0.8x
Guide-scope: Artesky UltraGuide 60mm f/4
Guide-camera: ZWO ASI 224MC
2020/11/08: Number of subs/Exposure time: 11@240s. Notes: L-Pro filter, no Moon
2020/11/09: Number of subs/Exposure time: 10@240s. Notes: L-Pro filter, no Moon
2020/11/20: Number of subs/Exposure time: 15@240s + 4@300s. Notes: L-Pro filter, Moon 30% illuminated
2020/11/21: Number of subs/Exposure time: 22@300s. Notes: L-Pro filter, Moon 45% illuminated
2020/11/24: Number of subs/Exposure time: 20@300s. Notes: L-Pro filter, Moon 75% illuminated
2020/12/13: Number of subs/Exposure time: 12@300s. Notes: L-Pro filter, no Moon
2020/12/14: Number of subs/Exposure time: 8@300s. Notes: L-Pro filter, no Moon
2020/12/18: Number of subs/Exposure time: 6@300s. Notes: L-Pro filter, Moon 20% illuminated
2021/01/10: Number of subs/Exposure time: 9@300s. Notes: L-Pro filter, no Moon
2021/01/11: Number of subs/Exposure time: 15@300s. Notes: L-Pro filter, no Moon
Total exposure time: 36840s = 10h 14m 00s.
Pre and post-processing: PixInsight 1.8.8-7.
Image was Drizzle Integrated and then cropped to original sensor size (6016x4016), without resampling. So, it appears as if taken ad double the focal length (768mm instead of 384mm). Image scale 1.04 arc-sec/pixel.
Here's a link to the full resolution image: Triangulum Galaxy (M33)
Thanks for looking!
Hi all, just getting straight to the point.
Just got a Rasp Pi 400 (equivalent to Pi4-4GB), and looking to get into guiding through this as it's obviously a popular (and successful) technique.
Plan is to have the RPi as mini computer at home, running it with RaspPiOS (supplied on µSD with the full kit), then use it with a SECOND micro SD card for astro - I figure having another SD to run Astroberry (as on SGL) may ignore any issues with the family using the pi for other stuff in the house, giving a stand-alone 'computer' as the OS and files would be available on different SD's.
From this point, I'd setup as follows:
Connect the RPi directly via USB to the mount (it's the newer SW-AZ-EQ6Pro with the USB-B port on the mount)
Guidescope (240mm f/4) with T7C (equivalent to ZWO Mini) again USB-B direct to RPi
Nikon DSLR (either on telescope or using camera lenses) connected to RPi via Nikon USB (using the 3 USB points on the RPi-400) to control capture and later using this for plate-solving (but that's not for just right now!)
I don't spy any flaws in the plan, it's just going to be a matter of testing and setting things up hoping to follow the guide for Astroberry as linked to SGL below...
Or is there an alternative OS? From brief reading, Astroberry includes KStars & PHD2 which is what I've got for use on the macbook (although not used in earnest as it doesn't appear to like the cold too much!)
What about guiding software - I know KStars comes with it's own, and can run PHD2 from within, with PHD2 being the industry standard (and simplest?) to use?
Control will then be sitting in the warm via OS-X, which seems to be again a common technique as I've had posts on my other questions about this!
Hello, does anyone know if my imaging train looks correct, and if it does, why am i still getting these coma errors?
Could it be incorrect backfocus? Searching the internet makes me think my dslr is 44mm, adding the t ring (even tried a 1mm spacer too) gets me to the required 55mm (assuming that's correct)
I have no idea how to solve this and i feel like I'm just throwing money down the drain fighting this in vien. Help would be much appreciated.
Skywacher Evostar 72ed
Reducer rotator for 72ed (needs this for extra distance to achieve focus, the reducer and adapter alone doesn't allow for enough outwards travel)
Reducer/corrector for ed72
Canon eos 650d
Hi guys, hoping you can help with the tracking problems I'm coming across with my astrophotography setup. I've been using it since August 2020 and have kind of put up with the problem until last night where I think it's getting worse...
Specs below (let me know if you need anything else):
William Optics Zenithstar 61 II (360mm F6.1) - Zenithstar 61Adjustable Field Flattener iOptron SkyGuider Pro Camera Mount Full Package K&F Concept Aluminium Tripod with 2kg weight Canon EOS 250d (cropped sensor 1.6x) The problem:
I take roughly 40 pics with each being 1 minute long at 1600 ISO and stack them on DeepSkyStacker. From a few people I know on the internet, it seems as though, with a very similar setup and same focal length, they can get around 3 mins of exposure with no problem. And that's without a guide camera.
With my 1 minute exposure, roughly 10 of 40 images are reasonable but the rest have star trailing or double stars (see attached downscaled, unedited pics of Orion nebula)
What I think it could be:
My first idea was the tripod, it's not the best but it's not cheap plastic, and it should be fine for a 1 min exposure. Then I thought it could be the iOptron tracker that could be faulty?
Every screw has been tightened, there's no play in any of the adapters/mounts.
I thought I'd post this here to see if anyone else has the same problem or has more experience/knowledge that could help. Also to see if there's an obvious problem before I spend hundreds on a new tripod or send the tracker back for a replacement.
Any help would be much appreciated!