Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

Welcome to Stargazers Lounge

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customise your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

  • Announcements



Advanced Members
  • Content count

  • Joined

  • Last visited

Community Reputation

1,241 Excellent

About Thalestris24

Profile Information

  • Gender
  • Location

Recent Profile Visitors

2,084 profile views
  1. Hi It might just be a balance issue rather than guiding per se. Run the guiding assistant to see how things are behaving unguided. Also double check cables to make sure there's no snagging or dragging. Louise
  2. Ah ok. Maybe it'll be better with the mono then. In that case the sa100 might be better also. I'll check out the sa100 mounting options on the minicam and the sensor distance tomorrow Thanks again Louise
  3. Ok - I have to multiply the calculator dispersion value by 10 then! Is 40-ish an ok value? If external limitations hold me to that sort of figure, I don't see any way to improve things other than ditching the dslr? I have a mono minicam5s which might be better in some ways (small chip, high qe) but then I'd lose the spectral colours. Thanks Louise
  4. Hmm... hard to tell. Some of them look somewhat like caustics. I think you'll have to do some investigating with single subs and moving/rotating things to see what happens. I'm sure you must have a dew/light shield to help keep any extraneous light sources at bay. I've had problems with reflections caused by an Halpha filter. However, they disappeared with dithering and kappa-sigma stacking. Hope you can sort the problem Louise
  5. Ok, thanks, Vlaiv. I must have entered the sensor width wrong before. The correct value (4272) now gives a lower coverage of 17,772 and 4.2A/pixel but still complains spectrum brightness is on the low side. The seeing value only seems to affect the star FWHM. I put in a value of 5 which gives a fwhm of 2.2 pixels. I'd be guiding with PHD2, as usual Louise
  6. Hi all Was just doing some online calculations with a view to using a SA200 with my 80mm F6 APO Putting it just in front of the t-ring on the FS1100d, gives a sensor distance of ~62.5mm. The calculator returns 4.2A/pixel and a spectrum width of 20268A (2026nm). The only complaint from the calculator was that it might be a bit dim? Can I compensate with longer exposures? Other than that, do the numbers sound ok? Thanks Louise
  7. As FLO says: "The Skywatcher Quattro series are premium quality imaging Newtonians"... I appreciate that compared to a good APO frac the quattros are relatively cheap but still. Look forward to your first images (without aberrations!) Louise
  8. Hi The thing is, though, should you have to do all this with a new scope? Haven't you effectively cut down your aperture? Have other users of the same scope had the same problems or is it just your particular scope? If many other users have had the same problem then surely it must be a design defect or a manufacturing/quality control problem. Other than that, well done for putting so much effort in! Louise
  9. Hi I usually do a quick run with no boxes ticked and check it's solving ok for the selected target. Then I select the first two boxes and re-run. I've never found it necessary to tick the third box. Obviously you need to have the correct fov etc for your setup. If you're not sure of other settings have a read of the lightvortexastronomy tutorial. Louise
  10. Hi Well it's all done from within AT when using AT. Presumably via ascom it knows where the scope is supposed to be pointing and from the first image it takes and solves, knows where it's actually pointing. I can't help with Pointcraft, I'm afraid, but the documentation should explain. Louise
  11. Excellent, Gav!
  12. Hi I use Astrotortilla but I'm not sure of the procedure using APT's Pointcraft. All I do is use Stellarium to select and slew (ctrl 1) to a target. I then use Astrotortilla (via APT) to take an image and solve it. Astrotortilla works out where the scope is actually pointing to then calculates a correction and slews again. It does a second exposure and solve to confirm the scope is now on target. That's it! Usually only takes a couple of minutes in total . Of course, you need good PA and balance and good focus too. Louise ps use Jnow
  13. Hi It could just be electrical interference - check out any nearby mains/psu cables etc. Louise
  14. Hi If you're using platesolving you don't need to do any star alignment (apart from PA, of course), but just make sure the eqmod alignment points are cleared. Louise