Reshot the darks and bias files and got this:
I tried M97 again last night without much success. I then turned attention to M51 and got a different result:
Initial (no flats/bias/darks):
I then changed the Bayer matrix to GBRG and got this from the same data though with flats/bias/darks added):
Someone suggested this was walking noise (though dither was enabled) or USB noise. Any thoughts?
Yes, internal guider. Tonight I lowered the settling time to 15 seconds and added a delay of 30 seconds between shots. We'll see if that does better than before.
I found where I can set the Bayer matrix in the driver.
I removed the LP filter to help with light.
The gain was purely a guess. Tonight I'm using "10" and see the histogram being very roughly 1/3 from the left. Promising.
The FITS preview that comes up after each sub looks good with little amp glow tonight. Promising, too.
Autostakkert 3 shows the FITS subs looking pretty good.
When I bring in/look at individual subs in DSS they look pretty smooth. Once stacked, however, ugh....
Last night I was able to get 2minute subs, guided. The end result is no improvement, though. Resulting image still effectively gray scale even though I see color pixels.
I also noticed something that seemed really strange. Normally, when shooting with my DSLR, it takes an image, Ekos then delays the next image until dithering is complete. Last night with the QHY, it just started the next image immediately. This resulted in many, many bad frames. The obvious "solution" is to put in a delay larger than the total dithering and settling time, but doesn't seem right. Is it, do you know?
I'm going to keep mucking about with these images. Maybe something will come to light.
Ahhh...so in the source then! Okay, that being the case there's nothing to be done.
Thanks for that.
What I mean by crappy - see attached. That is a single frame and a DSS stack with adjustments applied for clarity. Noisy, lack of detail, and amp glow upper right and middle left? I shot 135 frames, 30s unguided, along with darks, flats, and bias, and stacked them both in DSS and Astro Pixel Processor. DSS actually gave the better result but it's still crappy. Now, it could be the debayering went awry or my DSS settings are just wrong - I've not processed images from this type of cam before and this was my first go.
Also, thank you for the most excellent presentation video - I've watched it before. Excellent and meaningful answer to the popular question of how long should the exposures be and why.
It's supposed to be clear here tonight so with luck I'll be able to guide.
Does anyone have any suggestions for settings to use an uncooled planetary camera (QHY5iii-224C) for DSO just so I can put a check-mark in my experiment book? It uses the IMX224 chip, small, I know, but M97 image scale is perfect with this cam and my 80mm APO (similar to my much larger and heavier C8 DSLR combo). The cam can go to 1200seconds, but that's nuts. I experimented last night with 30s unguided, and while I got the target, it looks like crap. Since I forgot to remove the imaging LP filter, I'm thinking that likely partly explains the poor result. Not changing anything from default in Ekos might explain some more.
I get another chance Monday night according to the weather report. So, any suggestions on settings?
I don't know, but they don't resemble any satellite trails I've ever imaged.
I tried the linear interpolation setting - no go.
I see the compression artifacts that get better with zooming in, but I'm curious about the streaks as illustrated in the attached pic. I'm beginning to think they really are airplanes.
I just enabled HiPS overlay with DSS colors, and for the most part it looks gorgeous. However, the sky is also filled with pixel anomalies, and when you zoom in some resolve into streaks, sometimes two or three parallel like at M97, for example. They look weirdly like my pics when an airplane flies through.
What are these and can they be disabled/gotten rid of?
My Nikon D5100 works fine using the relay shutter release for long exposures, but now I want to do some flats and it just doesn't. Basically, I try to do 1/500, 1/1000, 1/2000, etc. and it always takes about 1 second. This is true whether I disable Force Bulb Mode or not.
I disconnected the relay, both ends, and now it won't take pictures at all, looking for /dev/ttyUSB0.
I have tried both the Nikon and gphoto drivers to no avail.
I would expect Ekos to query the HC especially when using a mount-specific driver. Of course I don't know the mechanics of how the driver talks to the mount or what information it would be able to read.
Does the CEM25 have encoders? I know some mounts do, but I don't know about the CEM25.
Doing some testing this morning and am left wondering about the purge/write data. Is there just one file???
I ask because when I powered up my CEM25p, I checked the home position, and it was correct. I slewed randomly, then through the HC sent it back to its home position - no problem.
I then connected the mount to the Pi, unparked and then parked without first randomly slewing. The mount slewed approximately 90 degrees in RA. I find that very odd, though it is consistent with what I've experienced when switching from one mount to another.
Purging the data, clicking on current, and then write data seems to have "fixed" the issue, for now. However, I'm concerned when I go to use my other mount - will it go rogue if I don't purge/set current/write? Is there not a config file for each profile? Could this be an oversight or perhaps a bug?
My CEM25p does well with my Windows laptop I don't recall having an issue except when wind caught my C8 like a sail and cammed the worm gear. That hurt.
I recall, too, when I first started trying to do polar alignment with Ekos, it seemed like the mount had lost its mind. Turned out I had Ekos slew West, but this triggered a meridian flip, so it would beep and then slew back. Much scrambling because I know if the mount crashes it can be damaged. Thankfully, I was set straight here.
I *think* it could be a driver issue maybe? It seems like the Home position in the HC is getting clobbered. I will have to double check this, but yesterday I attempted to slew the LX70 - it slewed to the wrong location. I then connected my CEM25p, created a new profile (I had not done this yet with the latest version of Astroberry), powered it up, and told it to slew to the same location. It also slewed to the wrong location. Through Ekos, I told it to park. Almost cammed the worm again as it tried to slew to China. Powered off, reset to index marks, powered on, set home position - CEM25p then was able to slew to correct location. More testing needed, I think.
My LX70 mount test last night was a success once I got past the park thing. Again, more testing needed, but I was able to get at least some results -