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

polaris_jerry

EQ6 Synscan pointing the wrong way

Recommended Posts

Hi All

I need the combined brains and experience of SGL please, I'm stuck!!

I've been an astronomer for 30+ years and have had several Skywatcher telescopes over time, including my current EQ6-Pro for about 10 years.  This is largely irrelevant to my post, except that I hope to convey that I'm not a total novice to getting telescopes to work as they should...although I feel like I am today.

I recently picked up a very battered early-version EQ6 with 10" reflector, cheap.  It hadn't been looked after well and when I first fired it up...it didn't fire up at all.  No life.  I noticed that the power supply wasn't suitable as it only had a 0.5A output.  So after digging out a spare one from the cupboard outputting 12V 1.25A, the Synscan chirped into life.

My first attempt to slew the mount was met with a horrible grinding noise and refusal to move.  Needless to say, I didn't do that again.  Clearly the motor/gear train was seized.  So a quick look on the internet brought up the amazing website posted by Astro Baby, with step by step instructions on how to strip and rebuild an EQ5 or EQ6 mount.  This kept me entertained for a couple of nights, followed by a lovely smooth running mount slewing in RA and DEC as it should.  Many thanks Astro Baby!

Last night was the first clear night, so I took the mount out, popped the 10" scope on (had a full respray, new finder, new focuser and laser collimation), and awaited the fall of darkness.  Here comes the rub.

I roughly aligned the mount on Polaris, not bothering too much for this first test.  The Synscan controller is (unfortunately) running Version 2.05, which is one of the early versions that are not flash upgradable.  Although I didn't realise this until after I had downloaded all of the upgrade files from OVL's website.  ?

When I picked the first alignment star (Capella, rising nicely in the north-east sky), the mount did something completely unexpected and slewed around to east of the meridian and pointed somewhere in the direction of Alcor!  What the ...?  After several unsuccessful attempts at carrying out an alignment, I gave up and looked online for any similar problems.  I've checked and confirmed all of the following things are correct:

  • Location - yep as per my Cumbria coordinates
  • Date - yep in the right format (mm/dd/yyyy) that good old confusing American format
  • Time - yep I tried with BST and without BST (not really expecting any significant difference)
  • Made sure the mount was in the "parked" position (weights down, scope pointing towards Polaris) before turning the mount on
  • Tried all sorts of initial alignment stars, but none of them were in the right area of the sky at all

Unfortunately, I haven't been able to find anything on the web that offers a solution.

I did wonder if I've done something during the disassembly of the mount - but I know the mount doesn't have encoders on it.  I didn't see anything that looked like a counter of any kind?

I don't think it can be anything to do with the power supply...surely that couldn't introduce such a wild error in pointing?  It's like the handset has no idea where it is.

Any help would be much appreciated.  This was going to be a second mount for me, but at this rate it's going to go on the scrap heap.

I did think about buying a V3 handset, but didn't want to commit another £120 in case it's something in the mount itself that's the problem.

Yours hopefully
Jeremy

 

Share this post


Link to post
Share on other sites

Don't assume that the psu isn't the cause of the problems, it usually is.  The output of the psu you quoted is only 1.25A, the mount needs a psu with a regulated output of 11-15v 2 amps minimum to operate correctly.

Share this post


Link to post
Share on other sites

Might be a dumb answer, but have you checked the motors were reconnected the correct way round on the board? It's fairly common for me with 3D printer builds to get it backwards on the first go.

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks both, I'll try it with the PSU I that I use on my EQ6-Pro just to make sure it's not that.

You've got me thinking now about the connection of the motors...maybe it was just that!!  Boy will I feel sheepish if its that!  ?

Share this post


Link to post
Share on other sites

Just swapped over the connectors...I think I had the RA and Dec connected to the wrong parts of the board! Duh!!  It looks like it's pointing where Capella should be now.  Thanks a million upahill!

  • Like 2

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 PlanetGazer
      I was hesitant to write this earlier, but I wanted to try all possible ways to get my new SkyWatcher 250P GOTO allgined, but to no avail.
      I have followed the instruction manuals of both the synscan and SW, and managed to get the message "alignment successful" multiple times on the handset or the app. The closest I got when I tried to dial a different star was a 20 to 25 degrees off on the azimth axis. Most times it's off by a margin on both axes.
      I have tried aligning around 30 times on more than 5 diffrenet occasions, different locations as well. I end up ignoring the thing and switch to navigating manually as the eager friends want to observe instantly, but we ran out of objectes and the planets are not close anymore, so I figured it's time to get deeper DSO's and sort out the GOTO.
      Here is what I do:
      • I level the scope to the zero reading on top of the base
      • I make sure the base is level with a spirit level I bought recently
      • I point the scope northish, but latley I bought compass to pinpoint north
      • I plug all equipments in and then switch on the power from a lead acid battery
      • I enter the date ( US fromat, month before day 😕 )
      • enter correct time zone obviously
      • the coordinates in the format of E 000 00 , N 00 00 
      • As for  elevation I use "my  elevation" app, not sure if it's accurate. Does this entry have to be that accurate?
      • I tried both brightest star and the 2 star align methods on the handset (which seems to be the same thing apart from the brightest method having an extra menu asking for which direction you are pointing at)
      I even used the synscan app and the synscan pro, and tried the 3 star align method. The app uses location and enters all data automatically
      •I use the top and right arrows as the last press before centring the star in the eyepiece as  recommended by the manual
       
      These are the steps I follow when I align , is there anythung I missed? Your kind help is much appreciated.
       
      Update: issue solved, check the reply in the second page
       
    • By Oslet
      Sooo...I'm getting quote frustrated here. This spring I tested my HEQ5 with guiding. The synscan controller was connected to the computer trough the USB plug on the hand controller. This worked like a charm in my living room. On the new controllers you dont need the rs cable. But when I tried the whole thing with guide cameara for some live shooting, it just did not work. I get something wrong with the com port in decice manager, driver not working. I have tried 3 different drivers. The whole thing responded, connected and was guiding when i did a dummy test before the summer. So setup is pc-synscan via usb for pulse guiding. Can it be a problem with windows 10? What t h.... just happened? Where can I find a driver that works? And believe me it worked 5 months ago, argh. Thanks for any respons and support
    • By tooth_dr
      I scrapped all the Oiii and Sii data I previously took during a full moon (about 15 hours worth) and retook it all when the moon was a bit smaller at 76%.  Ha was taken during 98% and 67% moon.  All the lights were taken on the following nights: 12th, 19th and 20th September 2019.
      Integration times, all in 600s subs unbinned:
      Ha = 28.33 hours
      Oiii= = 5.67 hours
      Sii = 5.67 hours
       
      The Ha data is really nice, and unsurprisingly the Oiii and Sii is not as strong (or nice).
      I'm missing that (vital) step in my processing routine of getting the Sii and Oiii properly stretched to match the Ha, before combining.  I dont really know how to deal with the weaker data properly.  Any pointers would be appreciated.
      What I do currently:
      All the data is loaded into APP into separate channels/sessions.
      The data is stacked and registered against the best Ha sub
      This produces individual stacks of Ha, Sii and Oiii that are all registered
      Each channel is processed with DPP in APP and then saved as a 16bit TIFF
      Each is opened in PS
      Stars removed with AA and any remnants removed and tidied up
      I then open a blank RGB document in PS
      I paste Ha into Green, Sii into Red and Oiii into Blue
      Adjust the selective colour settings to get 'Hubble palette'
      Adjust levels, curves, saturation until looks ok
      All the Ha Sii Oiii data is then combined together in a single 'super' stack in APP using quality weighted algorithm to create a 'luminance'
      That luminance layer is adjusted using levels, curves, and NC tools such as local contrast enhancement and deep space noise reduction (using masks to apply as required)
      The luminance is pasted onto the above colour layer, and incrementally added using gaussian blur
      Cropped and saved.
       
       
      Here it is anyway   I haven't intended on any more exposure time for this one, but will consider it, if the expert opinion dictates otherwise!
       
      CS
      Adam
       


    • By CrystalFox
      Hello guys,
      I recently got into astronomy so I bought my first telescope. I've read through several articles and the recommendation for a beginner's telescope (value/price) was Celestron Astromaster 130EQ-MD. I bought this from someone who was not really using it and it is in a very good condition. Prior to actually purchasing this, I've watched countless videos on how the telescope works, what needs to be done - latitude, RA/DEC alignment, polar alignment, etc..
      After reading through all available manuals and videos, I finally brought it home from the seller (they've had it for around 5 years but it wasn't used much). After setting up the tripod, mounting the telescope and familiarising myself with all the different knobs, I pointed the mount/telescope towards north. The first thing I had to do was setting up the latitude. Since I am based in London, the latitude is around 52 degrees. Afterwards, I had to align the declination axis so the telescope can be balanced. As I understand it, you should be able to move it to any position on the axis and it should stay in that position. If the front or rear was heavier, I would either pushing or pulling the telescope after unlocking the brackets holding it together. This is where the issues began, I could balance the telescope so it doesn't move while in the horizontal position, however, when pointing it towards north, it would exclusively lean towards one direction - to the left. If the telescope was pointing to north, north-east or east, it would pull towards the west all the time. It is probably easier to show it in the video. I've spent three days trying to balance the telescope by using different methods and it just would not work. 
      I've also tried balancing the RA axis first. This could be somehow done, but the declination axis would still pull the telescope to the left.
      It is extremely frustrating as I don't know what could be causing this. Balancing the telescope should be relatively easy from what I have heard - either push it or pull it depending on where the weight is. However, I have been really struggling to get it set-up.
      I would be thankful for any suggestions and please feel free to ask any questions so I can help with finding out what is wrong.
       
      Thank you.
      VID_20190918_202940.mp4


    • By Phillips6549
      With several clear nights over the past week,  I've been playing with the Synscan Pro app (Android) in conjunction with a Synscan WiFi adapter on an EQ3Pro mount.  I have to say I'm generally quite impressed.  Much cheaper than buying a traditional handset.  
      However,  this evening I was trying to "creep up" on the Andromeda Galaxy by star hopping towards it via Mirach,  Mu Andromedae and Nu Andromedae.  Mirach was no problem but the other stars were not available for selection in the app.  Am I missing something?  I couldn't find any way to enter an SAO number or any other catalogue number to find the minor stars.  
      Is this a limitation of the app?  Or the adapter perhaps?  Or is it me? 
      Clear skies, 
      Mark. 
×
×
  • Create New...

Important Information

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