Rallemikken

They are all accesible in the Indi Control Panel, but I guess you are familiar with that if you have used this software before. When it comes to odd equipment, I sometimes spend a little time searching for clues regarding chipsets and such. (sudo) lsusb and dmesg are two terminal commands that can help. Then it's google. PS: It don't hurt to present the camera with another driver. These things are not written in stone. One thing is the outside, the inside can hide parts and electronics used by other manufacturers. If it works at all with another driver, try to tweak it. Things to do on a cloudy night.

No clipping. See image. If I touched the left handle here, I would start clipping the black immediatly. The righthand one could tolerate some adjustment, but for this purpose I always use the handle in the middle. Zoom in heavily on a neutral spot in the background. 200-400%. Choose one channel, and move the slider in the middle a little bit while prewiev is enabled. I rarely move more than 0.05%. There is no right or wrong way in dealing with this issue; this is how I do it.

I've imaged with modified Canon's for several years. Firstly I'd suggest you try out Siril, and it's "Photometric color calibration" tool. If that fails, use the standard color calibration tool. This will most likely give you a neutral background. For fine-tuning I use the "levels"-tool in my image manipulation software (Gimp). Choose the channel you want to reduce or increase, and move the middle slider a little bit sideways. Easy does it.

Mine is 0.22.2 on a Linux desktop. The galaxies are faint, and Stellarium handles that with the sliders shown. And you must tick those catalouges you want visible.

First you must tick the "Deep Sky Objects" icon on the bottom toolbar. Then you can adjust what to see, and how much (sensivity) under the square icon (speech bubble-like) on the vertical left side toolbar. At least, this is how it looks like on my desktop install.

...anfd some of these Canon DSLR's don't play well unless you remove the SD (or CF) card. And they don't play well if the power supply don't provide enough current. Regardless if you have a 220v/12V/USB supply, the battery indicator on the camera should show full.

I won't, but it would be nice. Looks good. KStars and Ekos does have some faults. Their sky-atlas is a disaster, and the whole user interface may be regarded as a little childish. That said, I can't see any feature in NINA that lacks in KStars/Ekos. People may use whatever OS they want, but I will encourage all to try Linux to get a taste of if. I left Microsoft 20 years ago myself, but still do support for friends and family with Windows. Computerwise, I consider the Windows/Linux divide as parallel universes. Grab an old laptop, install the latest Linux Mint, and go for an adventure!!

Exactly! And check the angle of the focus tube, it must be spot-on in both axis. These are the two things you should start with on a newt.

You said it yourself. Allow me to elaborate: Do you regard the control of your AP-rig as missioncritical? I do. Windows was never considered. Soon ending my third full season, and never missed a minute of capture time. How? Linux. It never stops to amaze me. Highly technically skilled folks, able to master a complicated AP-setup, and they lay their software foundations on Windows?

First you must check that your image viewer renders the native .cr2-images from Canon without any messing around. Then you must check the EXIF-data of each sub, to get a grip of what's happening. Did you capture with the camera in "M"-mode? Only mode usable on this camera for astro images.

That's the RA axis. Maybe at one time a motor was fastened to the cam and meshed to the gear? Would make long-time exposures possible if PA was on spot.

We'll all have to start somewhere. I'm no familiar with any other than DSLR's, but one thing springs to mind: The galaxy as a whole seems transparent. You have those beautiful red regions that I'll never find in such a small target, but the spiral arms lack some depth and content. My guess is that you have lost some of that in focusing on the background, that is, you have clipped the black or lacked in bringing it forward. When you image a target like this there will always be a compromise between a dark, colorless background and the faintest details in the motif. The sky is never pitch black, nor is it colorless.

Must disagree. The "quality rating thing" in Siril is far better, but it require you to do the stacking in three steps: Preprocessing and registration, quality sorting (throwing out bad frames manually) and finally stacking. Supereasy and not hard to learn once you get the grips of it. As a beginning, take the Siril script "OSC_Preprocessing.ssf" and comment out (or delete) the line beginning with "stack r_pp_light". Save the file as "OSC_Preprocessing_no_stack.ssf" in the same folder. See if you find your way from here!

Soon ending my third full season with a HEQ5 and a 200PDS. Finderscope with guidecamera and DSLr's. Among them a hefty 5D MkII. No problems, as long as you shield it from the wind. And the tripod stands firm. Best is a fixed pillar. I have a StellaLyra 6" f/4 with the 0.9 cc as a supplement for those wide angles. Use the 200PDS most. You need this focal lenght for galaxies and small stuff.

I do. Nice guide. I have an obsy where I sometimes use my overclocked Pi4 with full Linux/Kstars/indi setup. It's borderline on cpu-cycles, guiding became erratic when I slowed down the computer. I went back to my trusted desktop, I like to use Stellarium and the browser while capturing. A Pi5 should handle this well. I use both Raspberry Pi's and Orange Pi's for several tasks. One OrangePi Zero2 as a standalone indi-server on my StarTracker. Common for all is that I use some Debian Bookworm-based distro, that be Raspberry OS, pure Debian or Armbian. They all have the complete indi-suite in their repo's, no need to use scripts or compile. I have my obsy connected to my home router with an outdoor USB wifi-dongle on a powered hub (the Pi's don't have more than 4 USB-ports, you will need a hub anyway). It picks up time with NTP, Network Time Protocol. No need for GPS dongles. Just give the Pi time to pick up the time before you start KStars. A minute or two. And my obsy is rooted. Coordinates don't change. I always start with a headless network install. On first boot I install the Xfce4 desktop and Synaptic. It automatically pulls in X11, i don't think Xfce run on Wayland. Then it's just a matter of installing what you need, remember to activate the "contrib" and "non-free" in /etc/apt/sources.list. I use x11vnc everywhere. The inbuildt vnc-server in Raspberry Pi OS is a flavour of RealVNC which isn't open source, nor freely available elsewhere. I prefer to stick to one solution and use that everywhere, and learn to use it well. I have added the x11vnc server as a startup application in my Xfce desktop. The server starts up when I fire up the Pi. I have learned to migrate my settings, especially the index-files for platesolving. I can move them from one machine to another, that be a Raspberry or Orange, or a desktop or laptop. They are situated in the same places within your home-folder. A Pi is never further away from disaster than a faulty SD-card. Good work, should wish more people used KStars/Ekos. Never let me down. Never missed an hour capture time. For four seasons! More than 120 pictures so far!