Jump to content

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.

sgl_2019_sp_banner.thumb.jpg.a0ff260c05b90dead5c594e9b4ee9fd0.jpg

Recommended Posts

The thread has been linked, from experience the EQ3-2, with an upgraded tripod and patience can work and can guide as accurately as an HEQ5.

This was 5-minute guided exposures on an EQ3-2 with a 130P-DS

M3.png

That said, having gone from EQ3-2 to HEQ5, I would not go back.

Why - reliability. With the HEQ5 you get  a higher ratio of successes to failures; also the HEQ5 can take more weight.

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
On 20/03/2019 at 08:02, masjstovel said:

@Knight of Clear Skies ive decided to go for the 150 PDS with EQ5 and then add the synscan goto st another time. I made a post on the equipment beginner  forum, and were told it then would be exaclty the same performance as a EQ5 pro synscan goto. Correct?

With 9 kg limit on the mount i guess that would be stable enough with a 988grams nikon d810 added. 

No i havent even considered that. Thank you! What is a coma corrector? 

I also wonder what adaptor(s) i need to mount a Nikon full frame

Two things come to mind with this plan,

1) I have a friend who uses a 150PDS on a HEQ5 Pro and it works but will struggle with a small amount of wind, as a result I don't see that mount guiding a 150PDS. The SW 72ED is your very best bet in that price range with an EQ5. You really dont want to start AP at that longer focal length at any rate. 

2) You will not get a nice stars across the entire sensor with a 150PDS / 130PDS and a full frame camera like the D810. 

3) Don't get hung up on aperture for Astro Imaging its not factor. F-ratio is the thing you need to look at. F5 - F7 being the sweet spot for a beginner. 

 

Do you already own the D810? If not then its not one I would recommend for AP. If you already have one though its not terrible either. 

Edited by Adam J
  • Like 1

Share this post


Link to post
Share on other sites

@Uranium235 Thanks for the input!

Well unfortunately it's too late now, i ordered the package with an EQ-5 a little over a week ago :S I would love the HEQ5, but for me this "adventure" started out like;
"I would love a telescope. Couldn't cost more than a couple of hundred dollars, could it?"
"Ok, I need an equatorial mount. Couldn't cost more than a couple of hundred dollars more, could it?"
"OK, the eq-mount isnt heavy enough……… And so on. 

So i had to set a limit somewhere. 
I will likely spend another $1000 dollars on a HEQ5 and sell my EQ5 for half the price i bought it for in the future, but its at least a calculated risk i am aware of:) I will look for for sale-adds for the HEQ5 mount, and go for it if the price is right!

 

@Icesheet Wow, thanks, that's a really great offer! PM sent. I started thinking im the only one in Norway interested in this field. 
 

@Adam J As i mentioned to Uranium235, i've already ordered the 150PDS and the EQ-5. 150/750  will be F/5 so im in the right range at least?
I do already own the D810 as i'm mainly doing photography from beforehand. You dont reccomend it because its full frame, or is there some other reason? 

Share this post


Link to post
Share on other sites

I suspect people who struggle with wind live in windy places. I have no trouble using a 150PL on a HEQ5 and a mate uses a 200P on his, but we are in the midlands, not on the coast.

neil

Share this post


Link to post
Share on other sites
Posted (edited)

Update: 
The 150PDS is in tha house now. I bought a "used" Synscan Goto Upgrade kit for approximately 220$ which i installed tonight. 
The neighbours must think i've gone mad if they saw me do the polar alignment, luckily its dark.
 

I tried taking some shots (light frames) of the Pinwheel Galaxy, M101 just for testing. Tried 30sec exposures, 800, 1600 and 4000 ISO but i couldnt see the Galaxy at all. I thought i would see at least some traces of it. Was I off, or is it because of the light-pollution? I Attached some unedited jpeg's here. I would be impressed, but does anyone know if M101 would be in this frame, or which star this bright one is? I was on the porch stepping around, so they are alittle blurry.

_BEH7485.JPG

_BEH7486.JPG

_BEH7487.JPG

 

Edited by masjstovel

Share this post


Link to post
Share on other sites

Doesn't look right to me, plus M101 is quite challenging even without the moon around.

Compare the stars in this pic:

M101_March_19.jpg

Ah Astrometry.net solved it:

image.png.2f5e816e7714e451063580d05c5134bf.png

You are about three frames too low and about a frame too far to the right.

Did you do a three-star alignment before doing the GOTO?

  • Like 1

Share this post


Link to post
Share on other sites

Ok I AM impressed:) Thanks again for the replies guys.

I did a 2-star alignment. First i checked if the mount was leveled, and did a polar alignment as best i could. after the alignment it said i was 1 and some degrees off East, and 4 and some degree off North , which i dont understand why. I find it difficult to know if its Polaris i'm looking at or something else. Also my app puts it at about 2 o'clock in the "Polar-Wheel", but i dont how it is in the polar finder since the image is "mirrored" and all that. I copied what i saw on my app.

I used Mizar and Vega for the 2-star alignment. When i chose Vega at first, the Scope went veeery far off. Like 130 degrees off, pointing down to the ground. This got me thinking of probably a very stupid question, but is there a right way and a wrong way to attach the scope, directionaly? i mean you have 2 options 180 degrees.

After centering Vega, it moved to what i at least think was very close to Mizar, just had to calibrate it a little bit closer.

But then when you say im 3 frames too low and to far to the right, then there must be something I'm doing wrong?

Another thing that made me worry. If i released the RA and DEC locking knob, and turned on the scope, at some point the scope would crash in the tripod legs. It didn't happen but if i continued turning it would. The Synscan doesnt "know" this and stops and goes the other way around if its obstructed? Is this a common thing, or am i doing something wrong here too? 

Share this post


Link to post
Share on other sites

You need two stars about 30 degrees well away from the pole star. Mizar is too close to the pole star to give a really good alignment.

You should start with the scope parked which normally means on top of the mount and pointing at Polaris. Best way to do this is check mount is parked, if not park it, then manually slew it to point at polaris and on top. Unpark and it now ought to slew to approximately the right spot.

Share this post


Link to post
Share on other sites

I used ASTAP on your image, and it solved it immediately.  It's very easy to use, and is completely self contained.    http://www.hnsky.org/astap.htm

I popped the result into Cartes du Ciel and this is the result (your image is the lower box).

Platesolving seemed complicated at first, but it saves hours and hours.

 

Untitledc.jpg

  • Like 2

Share this post


Link to post
Share on other sites

Looking at that I bet your second star alignment was on the  lower star circled in yellow, rather than Mizar (circled above).

That would explain the short move ending up exactly where it did rather than on M101.

If it was on Mizar it should have been an obvious wide double with Alcor.

image.png.c5d652c511809d53fc004916e4dc3f20.png

  • Like 2

Share this post


Link to post
Share on other sites

Stub Mandrel could well be right, it's easy to align on the wrong star. Sometimes I use a laser pointer to check the scope is pointing where I think it is, if I can find a straight edge on the mount to rest it against.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MartinB
      This has been a bit of a project.  Last year I worked out that my 200mm Canon F2.8 lens and ASI1600 would frame the whole of the Veil complex quite nicely.  I captured Ha and OIII data for the east and west nebulae with a Tak FSQ 106 and added this into the widefield image.  Although the Tak data had to be shrunk down it did add a bit of extra resolution where it was needed.  
      The difficulty for me has been the processing.  I have found it really difficult to tease out the faint wisps of detail and have tried the usual routines of micro contrast adjustments using curves along with Scott Rosen's Screen blend/mask inversion method but the results weren't great owing to the close proximity of faint and bright nebulosity.  I'd heard about the PI process tool for removing stars, Starnet, so loaded this and had a rare foray into PI.  This proved very helpful.  It was a luminence created from Ha and OIII using the 200mm lens with the Tak data mixed in.  Then the starless layer was added in PS with the screen blend mode at 50% opacity.  The nebulosity detail was so well preserved I didn't need a mask.  After blending I reduced the stars a bit more using the starless layer again and darken as the blend at 50%.  I should really unleash some of the stars to add a bit of "punch" but I've wrestled with this data enough for now!  I plan to use it further as I look deeper into the Gorgon that is PixInsight!
      Telescope: Tak 106 for E and W veils.  Canon 200mmL lens
      Camera: ZWO ASI 1600 pro mono cmos, Gain 150, offset 50
      Filters: Baader 7nm OIII and Ha
      E+W Veil 10x30 mins each channel for each nebula.  Whole complex 50x5mins for each channel
      Captured with SGP, calibrated, aligned and combined with PI, processed mainly with PS but PI for Starnet.  Ha mapped to red and OIII to both blue and green

       
    • By MarsG76
      The Omega Nebula, aka The swan Nebula, M17/NGC6618 imaged in Narrowband and combined in Hubble palette style. The photo was imaged with a astromodded and cooled DSLR through a 8" SCT across multiple networks gets from 28 July - 8 August 2019.
    • By MarsG76
      The Omega Nebula, aka The swan Nebula, M17/NGC6618 imaged in Narrowband hAo3hB as RGB. The photo was imaged with a astromodded and cooled DSLR through a 8" SCT across multiple networks gets from 28 July - 4 August 2019.
    • By Astronut_Al
      Hi everyone, 
      Can anyone confirm (or refute) - have I imaged Ganymede and Europa in orbit around Jupiter or is that just wishful thinking? (Only equipment used was a Lumix G7 with 150mm zoom lens - effectively 300mm with 2x crop factor - and of course a tripod).
      It appears to be the case and yet I can't quite allow myself to believe it...
      Thanks from an old newbie.



    • By GWalles
      This is currently a work in progress. Playing around with Photoshop CC to try and extract more detail from this image. This image is not as cropped as the others I have posted.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.