wimvb

Just remember that with a CMOS camera, you should never scale darks. Leave that option unchecked in the calibration process. You can of course, create a dark library and do so on a cloudy night in a darkened room. Less risk of light leaks that way.

What's even more impressive is that the zwo filter wheel and oag fit in this scheme. No extra adapters needed, just attach one to the other. They seem to have thought this through.

Some cameras have good enough sensitivity in the red part of the spectrum to capture H-alpha, even without removal of the ir filter. What camera do you use?

Then you should try 200 frames, still just over one hour. Image quality (measured as signal-to-noise ratio) is determined by total integration time = nr of frames*exposure time. If you want to catch more of the weak parts, you will need to increase the exposure time. And take flats of course. When I imaged with my pentax dslr + 135 mm lens, I took flats by pointing my camera at a door that was evenly lit. Even though the door was blueish, the flats worked. Just make sure any shadow is not in the field of view. This method may leave some gradient, but will help you get rid of dust bunnies. Maybe useful until you get that lightbox.

And for good measure you can also wrap the front of the camera (with cap on) with double layers of aluminium foil. Plastic caps are not light proof, especially infra red light can make it through the plastic.

Where's the fun in that? For me processing raw data is where the challenge is in AP. Data capture is very much a mechanical activity, while processing is the artistic part of our hobby. The problem with this set of scripts is that you hand over control allmost completely. One of the advantages of Pixinsight is that it lets you take control of all the details in post processing. Daunting at first, but powerful once you understand. Besides, every image has its own challenges, which I don't think you can solve by applying a single script. Some of the shortcomings of the scripts shown in the video were the cropping of all four edges equally (that would have clipped your M42), leaving a stacking artefact on the right hand side in the image, the green cast that could have been removed much more efficiently without creating a purple/magenta background, etc. For a beginner I can recommend the videos by Richard Bloch (just Google Richard Bloch PixInsigt), and Kayron Mercieca (lightvortexastronomy.com), as well as our in house guru Harry Page.

Put a little more work into it. Noise reduction, colour contrast and repaired the stars.

I had a look at it myself, but unfortunately none of the vendors ship to Sweden. Over here, these usually are a lot more expensive. Btw, I can only recommend PixInsight, it has a different philosophy than other apps, but it has everything included. No need to get plugins or addons. It's well worth the money.

First impression: Great image. Unfortunately it still suffers from the dust bunny in the top half Simple stretch and some HDR compression in PixInsight

Here's how I take flats. https://www.astrobin.com/326547/?nc=user IKEA Floalt + embroidery hoop with 4 layers of white cotton. The Floalt has intensity and light temperature control. Together with the automatic exposure control in Ekos/Kstars, it produces good flats.

It depends. There is a thread in the imaging section about these. The consensus seems to be that if the leds are situated at only one side, illumination will be uneven, and it won't work. But if illumination is even across the surface, it will work if you cover the panel with white paper. Have a look here

I have to agree. For deconvolution to work, you need to have a good signal to noise ratio. It can work without a mask, but it's a lot easier with. If you increase the regularisation (nr of layers and strength/layer) you can push deconvolution to target stars only. This is one way to reduce stars before stretching. On this image, I would mainly use it to do just that. More data under more favourable conditions is the best way to improve the galaxy.

+1 This galaxy is usually the target of large reflectors, not refractors. Excellent result, and I admire the commitment.

Good catch under those conditions. You may be able to squeeze a little more out of your data with deconvolution and star reduction.

Congrats on your success. Incidentally, ngc 185 was also one of my first deep sky objects with computer controlled targeting + astro camera. It may not be the fanciest target out there, but it's one you have to do just because you can, imo.

Nice! The inverted image shows more depth (3D) on my screen than the regular one. Probably due to the deeper shadows.

Here's the image with only a crop and a basic stretch applied. The vignetting and dust bunny are obvious. DBE removes the vignetting, which makes the dust bunny even more obvious, as it becomes the darkest area in the image. and as received (stretched):

Dynamic Background Equalisation: a tool in Pixinsight to remove gradients in the image. The shadow of dust near the camera sensor. This will cause a dark area in the image. Only flats will help even these out. "no can do". I toned it down as much as possible. It's just below the bright stars above the galaxy. I can post an image where it's still visible.

Here's my attempt in PixInsight Crop DBE x2 Background neutrlisation Photometric Colour Calibration Split Luminance RGB: Star repair script Masked stretch Further star repair Luminance: Histogram transformation Curves Transformation HDR transformation Curves Transformation LRGB combination LRGB: LRGB combination Star reduction 50 % resampled

Downloaded. Some first remarks 1. the target is a bit off center, but it fits the fov very well 2. you need to take flats. There is strong vignetting, which combined with large offsets between subs, creates a gradient that even DBE in PixInsight struggles with. I had to apply two passes of DBE to get a reasonably flat background. There is also a dust bunny in the image that can't be removed.

I timed it just now again, from parked position. I used a previous capture of the Sunflower galaxy. It solved it in 7 seconds, but at the same time ASTAP failed to do the refinement solution with the ccd simulator. My local astrometry on the Rock64 took 13 seconds to solve the image from ccd simulator. I need more clear nights ...

As far as I know, the SA only has one motor: RA. It can't correct for any drift in DEC, which you will get if polar alignment is off. It will correct RA drift, and fluctuations in RA tracking.

I loaded a fits image, and 6 secs later it hade a solution. I used standard settings in the indi simulator which is configured with my asi camera and skywatcher scope parameters. In all fairness, the target image wasn't very far from the park position of the scope, so that helped. I haven't tested it with my real mount and camera yet, so I don't know how it will perform in the field. Normally the solver won't need to do a blind solve, because it will use the scope position as a start in solving. Anyway, I'm satisfied with this feature.

That's about where I am too. I use 2 Rock64s for the gear with INDI/Ekos. Now with having ASTAP for platesolving, this has become very powerful (blind solve in 6 secs on a Rock64), and I don't have to use Kstars on my laptop anymore. I just RDP directly into one of the Rocks. But having the weather station and SQM wireless, frees up usb and allows me to run them standalone. The next step for me is to get the weather station working with the Ekos observatory module the way I want it. In the mean time I also have a 64GB emmc module incoming that hopefully is faster and more reliable than the microSD card.

Weewx only seems to capture data from devices that are directly connected to it, not through wifi.