Jump to content

SkySurveyBanner.jpg.21855908fce40597655603b6c9af720d.jpg

Steenamaroo

Members
  • Posts

    94
  • Joined

  • Last visited

Everything posted by Steenamaroo

  1. @vlaiv - Thanks for the information, although your descriptions explain why the background would become darker, or lighter, over time. If evening one's images started bright due to light pollution or transparency, and got darker because conditions improved, shouldn't the galaxy and stars have become brighter? Conversely if evening two's images started dark and became brighter due to conditions worsening, wouldn't the galaxy and stars have become faint over time too? As I say, folks, both nights were shooting the same target at the same time, and the target was more or directly overhead, far from the horizon. Position in the sky was the same for both sessions. @Swillis My understanding with dark frames is that I don't really need bias frames if I have dark frames, and I do need dark frames because without them hot pixels are a bit of an issue. How do you mean `Firstly, the temperature cannot be matched to the lights`? The temperature of the sensor? I take my darks on site with the same exposure length as the lights, so it should be the same?
  2. Thanks for the thoughts, folks. I'll try to cover everything. @Stefan - I realise increasing ISO increases noise, but also that stacking reduces noise. I wasn't necessarily expecting a good result from the second set, but certainly the stack should always be better than the subs, no? Admittedly I didn't check the histogram, although clipping there would indicate overexposure? Agreed - Checking histogram in future is a good idea, but I'm pretty sure I've seen people's subs as bright as/brighter than, the ones I've shown here. @happy-kat - Agreed - 3200 is pushing it. Thank you though. I suppose I was kind of baffled as to why it seemed impossible to overexpose. Maybe that's just my lack of experience with fainter DSO's but gradually increasing exposure duration and ISO I expected to, at some point, look at a sub and think, "wow, that's way too far". That didn't happen. Comparing the first sub from night one and night two, I don't think it looks like I did an 8X on exposure and a 4X on ISO, even taking the Barlow into account. "5 darks would just add noise, flats are good to use" How's that? Darks are pretty much essential since I've quite a few dead pixels, and my understanding is, just as with lights, more = better? "Sky conditions can change throughout a night and be different between days even if it look clear" I suppose that's true. That said, these were two ridiculously clear nights. Pretty much no twinkling - definitely no visible cloud or haze/mist...nothing like that. "Did your secondary mirror get dew on it?" I have no idea - Maybe that's something to watch. Thanks for the thought! Local light pollution usually isn't great - There's usually someone with a security light on all night or whatever but for these two nights there was nothing. It really was as dark as it gets here. I think that's why I'm a bit bummed. I expected stack 2 to be more impressive but too noisy and then I'd do night three probably with 10 minute + 800 ISO, and a lot more stacks, but the results from these two nights kind of threw me a bit. @Elp - Targets were about as overhead as it gets. M81+M82 between 22:00 and 00:00 in UK. Moving closer to, or farther from, the horizon or any source of light pollution would make sense but, unfortunately, that wasn't the case here.
  3. Hi all, I don’t really have a specific issue but was hoping someone might help with general advice for astrophotography. I’m using a 130pds with Canon 500D, shooting raw, on a belt driven guided Vixen-GP. Guiding is SVBony SV-106 50mm with qhy5l-ii-c. I did two test sessions - One on Monday night, one on Tuesday. Both nights were remarkably clear. (I know...hard to believe!) The first night I captured m81+m82 together, prime, with 1 minute 800 ISO images over about 90 minutes. I know that’s not a huge amount, but enough to gain some experience+confidence, I think. I learned that 1 minute at 800 probably isn’t enough but, regardless, the first subs looked usable. I noticed, after the session, that subs became darker as time went on. Shooting between around 22:00 and midnight that made some sense, as the sky was getting darker, but the subject (m81+m82) and stars got substantially darker too. I expected the backdrop would darken over time but the target+stars should remain around the same brightness. Am I wrong? The stack of these images really pleased me, though - Although the target galaxies weren’t particularly bright or well developed, the image was nice and clear and the backdrop smooth and dark. A success, from my perspective. For the second night I decided to improve by increasing the sub lengths and also decided to 2X Barlow and focus on just m82. I’m aware Barlow would make the subs much darker than at prime so I did some tests at 3 minute exposure. Not seeing a huge difference in target brightness I tried 4, 5, 6…and finally 8 minute. Surprised at how little difference there was I tested increasing ISO bit by bit too. I ended up taking 8 minute exposures at 3200 ISO, wondering why the target and stars still looked so faint. I only got around 10 subs but, this time, I noticed they became brighter as the night went on - The exact opposite of what happened the night before, shooting at the same time (22:00 to midnight) The stack this time was very disappointing - Very grainy/noisy, backdrop nowhere near as dark - Pretty much monochrome looking - It looked like something from the guide-cam but noisier! I’m stacking with DSS, took 5 or more dark frames for each session, and used the same flat frames for both sessions. I also tried stacking both sessions without flats, which didn’t account for the difference. Environment was the same both nights - Same setup position, same neighbourhoods lights (or unusual lack thereof!), no rising moon… I suppose my questions are Why would my lights get darker (background, stars, and target) as the night went on on night one? Why would my lights get lighter (background, stars, and target) as the night went on on night two? Why would night one stack perfectly but night two stack looks terrible? Safe to say 3200ISO was pushing it but the stack should still look better than any sub, no? Many thanks to anyone who read my wall o' text. First session first sub First session last sub First session stack Second session first sub Second session last sub First session stack
  4. Hi folks, Just following up on this. I've had much more success over the last few nights. I think this issue was caused mainly by two things. One : Not giving the mount a rough idea of where it's pointing first - Thanks @BCN_Sean Two : I started using dark frames when solving. I noticed a few white specs - dead pixels maybe? - and it seems like these were really causing issues. I had a few failed solves which succeeded when I retried with darks in use. Thanks to everyone who commented and offered help! Much appreciated, folks.
  5. @bottletopburly- I wasn't aware of that. Certainly something to try. Thank you. @alacant- As far as I know the values read and shown are correct. If I'm wrong of course I want to know, but everything seemed to match up with manufacturers specs.
  6. I've tried to snatch some breaks in the cloud here and there but, honestly, it's been a real pain trying to get more than 10 or 15 minutes without cloud or rain. From the brief windows that I did get, I think I can confirm that it'll plate solve just fine if it knows what it's looking at already. If it doesn't, it wont. Kind of seems like that defeats the purpose a little, since the setup procedure for go-to use would involve slewing to some star then solving so it can realise it's not actually at that star then correct for it. @BCN_Sean- it was your comment that made me realise this, combined with noticing that every time I try to begin polar alignment, ekos decides my mount is somewhere else. I mean, I'll point the mount/scope at the polaris, tell ekos I'm at polaris...sync to polaris, set home polaris... If I click 'goto polaris' it goes 'beep beep' you're already there. Then I do polar alignment and the instant I click start it goes boom...your mount is somewhere else now, then fails. I've no idea what that somewhere else is or how to override it, other than manually slew to 'the pole', then going over and manually fixing the mount so it's actually at the pole again, in order to do polar alignment with successful solving. I guess now that I know that I can just do that but I sort of thought that's what 'sync' was for. Looking forward to the next clear night.
  7. Hey, Thanks @BCN_Sean - That's really helpful! I'll give all of those things a go. Thank you.
  8. I only have one camera of that make/model, and 190 is correct for the guide scope - Corrected to 188.something on successful solve, but thank you for that info.
  9. Oh, I see it now. Looks like it's all auto-filled and not editable.
  10. I can't see where I'd input that information, but I know I have never entered that manually so you might be on to something.
  11. Not sure there's anything helpful in there but attached none the less. The current coordinates aren't meaningful, of course, as I just booted up to grab that screenshot.
  12. Alright, that's good info. Thanks folks. To be honest I've never imaged over multiple sessions but I understand you'd want the greatest accuracy possible if you were doing that, so using the main scope in that case makes sense. For now, though, I'd just like to get solving working via guide scope as it did before, for goto convenience and/or single evening imaging. Last night was clouded out but I will be back after the next clear sky.
  13. Hi, I'm not sure I understand? For imaging I'm using a DSLR so framing a shot would be manual rotation of the DSLR plus a few nudges of the mount control to get it just right. The guidescope and main scope are trained on the same point, so there shouldn't really be a difference whether I solve for mount position (and goto) with one or the other, right? I'm a beginner...Do people point their guide scopes at more star-rich areas than the imaging target when needed?
  14. Ok, something else to try. Thank you. I'll try everything suggested here next time there's a clear sky. Not looking great for tonight but who knows...I'll keep an eye out.
  15. Thanks again @AstroMuni I'm afraid I can rule out cloud - Last night was one of the rare clear nights while I was out. Here are some screenshots of my settings. The only thing I toggled throughout the evening was Solving Method Internal Solver / Online Astrometry.
  16. Fair enough. It might reveal something interesting. Thanks for the suggestion.
  17. If it's useful information, my guidescope info is shown as follows. Nothing here has changed since it worked well. Focal 190 (188) Aperture 50 F/D 3.8 FOV 86.8 x 65.1
  18. @wimvb- That's reassuring. Thank you for the info. I didn't try uploading to astrometry.net myself - That would have been too obvious. 😂 Will certainly do that next time. Thank you. "The internal solver can be a bit sensitive to fov, which needs to be near or larger than 1 degree." That's interesting. I'm not sure what I can do about that, if anything? @david_taurus83- Reassuring to hear about near-pole alignment, and potential go-to issues. That makes more sense, hearing your explanation. Thank you.
  19. Hi folks. Thanks for the replies. @alacant- Seems so obvious, now that you've said it. 😂 I'll save some images next time I'm trying...Next time the sky is clear. @AstroMuni- Yes, I'm trying to polar align and platesolve using the guidescope and QHY camera, which is what I've always done. Main scope, guide scope, and finder scope, are all pretty well trained on the same point. I have imaged before with this rig - Not much, admittedly, but enough to know. My main scope is a 130pds, since you asked, but it's not a part of the platesolving/polar alignment chain.
  20. I should add, when it does work it tells me focal length is 188, so I'm confident the specs I'm inputting for the guidescope are correct, or close enough.
  21. Hi all, Hoping someone might be able to offer some advice regarding successful polar alignment/plate solving in Ekos. I previously had no issue but had a real fight on my hands tonight, and I don't know why. I have a QHY5LII on SVBony SV106 (50/190). Kstars + Ekos is on an Astroberry install on a PI4, all up to date. What changed? My previous setup was Ubuntu Mate with a year old install of Ekos/Kstars. I switched to Astroberry this week which brought all the software up to date. I have downloaded all the required fits files so tonight's attempts were split between astrometry online, and internal. I found that internal would work maybe one time out of ten, and I don't think online worked once. I'm told that there may not be enough stars although, from previous experience, this isn't the case. Tracking is working well, the image is in good enough focus, and the stars are all clearly visible and it was a nice clear night. Interestingly when reading online for help I found many people saying not to bother trying to solve/align at the pole star, as it will most likely fail. Prior to this evening, I had never solved or carried out alignment anywhere but at the pole star! Regardless, I did move over and try a range of other areas with no real change to the results. If you got this far, thanks for reading. Hopefully there's some setting or option that I've overlooked.
  22. I'm not sure how useful this is to you but I can +1 Ekos/KStars. I find their polar alignment routine very easy indeed and guiding, while it took some trial and error, has been pretty successful. I did, however, buy a dedicated Pi4 for my mount, so I have my guide scope/cam and my mount control unit (eq5 kit) connected to the Pi via USB. That means that A: the whole thing is permanently set up - just carry it outside and add power, and B: as long as I'm within wi-fi range I can just screen share to the Pi from phone, mac, windows...whatever. As I say, that might not be useful info to you but I liked the idea of having the whole setup static and dedicated.
  23. Hey all. I finally got another opportunity to get a proper test done and everything went really well. Here's the calibration plot. All this 'practice' meant that set up only took about 15-20 minutes, so that's great. I figured I'd take some shots of M42 and see what I could get. Didn't invest a huge amount of time as it was a first trial but I'm damn pleased with what I got! Thanks once again to everyone who offered advice and help here. (and yes...take flats next time)
  24. I've only had one opportunity to test and that was it, but I was able to calibrate and produce similar results three or four times in a row. This week has been wall to wall cloud, unfortunately, but next chance I get will be confirmation night (I'll report back) and then after that maybe I'll take a photo of something. 😀
  25. Impossible to say what will happen in 50 to 100 years but there's hardly a digital data, or analog a/v, format from the past that can't be accessed by someone, somewhere. Enthusiasts keep old computer platforms alive and there are always public services for the restoration/recovery/backup of obsolete a/v formats. Your job, everyone here, is to have at least two copies of everything! That big hard drive you keep all your stuff on is great until it breaks, and they don't always need a reason to break. Spinning media (physical disc) is a lot more volatile than SSD, particularly where movement, shock, changes in temperature, etc, are concerned, but anything can break without obvious reason. Cost used to be an issue but you could get multiple terrabytes of storage now for not a lot of money. For extra protection, and some amount of convenience, you can get a NAS and regularly update it with important data. That could be your shoebox.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.