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_imaging_challenge_banner_dslr_mirrorlesss.thumb.jpg.5b348d6a5e7f27bdcb79e9356b7fc03b.jpg

MeyGray3833

AZ-EQ6 will not guide or calibrate in Y Axis

Recommended Posts

Hello.

I have an unusual problem with my AZ-EQ6.

I decided that I wanted to try pulse guiding rather than ST4, to get rid of a cable.

I use MaxIm for all my controls, capture, guiding, pointing etc. and I use the EQMod ASCOM scope driver.

My initial pulse guiding efforts worked ok, the mount would move and guide etc, no worries. I was not pleased with the pulse guiding results after some fluffing around so I moved back to ST4 and this seems to be where my issues started. 

Now, whether I choose ST4 or pulse guiding, my mount will no longer calibrate in the Y axis (Dec, I believe), or for that matter, guide. I have tried the move commands from inside MaxIm guide tab and X responds to a 10 pixel move but not Y.

I tested with both PHD 1 & 2 with the same results. 

If it were a hardware issue, as in the mount has a Dec problem, would I be able unable to operate the mount with the hand controller or on screen motion buttons, both of which slew the mount fine? I could understand if the guide port were malfunctioning that ST4 would possibly have an issue but not when the mount slews as directed, so pulse guiding should work.

Could it simply be that my EQMod driver has got confused and needs to be re-set, or am I looking down the barrel of sending my mount back to the dealer?

Does any of this make sense?

Thoughts and feedback most welcome. 

Share this post


Link to post
Share on other sites

Hello there, Are you using an EQDIRECT cable, or going via the handset in PC-Direct mode? :hello2:

 

Share this post


Link to post
Share on other sites

EQDirect. I have been using EQMod and this combination of software for many years. Never had a problem until recently.

Share this post


Link to post
Share on other sites

I know its a daft one but if you look in EQMOD set up(spanner thingy) are there ticks against Ascom Pulseguide settings especially DEC Rate and what value does the DEC rate show - on mine its x0.90 but I do PulseGuiding.  I would expect these to be zero and unticked for ST4 as I thought the commands were direct from the camera ST4 port to the mount St4 port. But not sure if , as you say,EQMOD is trying to get in on the game and confusing the mount. Maybe recheck all software is working the same - ST4.

Plus dont forget to use EQMOD set up to alter EQMOD back to ST4 - see picture

Sorry in advance.

pulse.jpg

Edited by stash_old

Share this post


Link to post
Share on other sites

Plus there is an EQMOD tool box that lets you alter config files (save orig firs) but edi that under expert guidance (not me)

Share this post


Link to post
Share on other sites

My observatory is in a remote location to me and it is a 120 km round trip so I was trying to get some info first.

I think I will fire up the pc and mount, park it in the home position (as I use a custom park) and then shut it all down except for the pc and dump the EQMod config and check all other software and start again. I would have thought if there was a mount problem, then the Dec motor would not work at all.

Thanks for the input so far.

Share this post


Link to post
Share on other sites
12 hours ago, MeyGray3833 said:

My observatory is in a remote location to me and it is a 120 km round trip so I was trying to get some info first.

I think I will fire up the pc and mount, park it in the home position (as I use a custom park) and then shut it all down except for the pc and dump the EQMod config and check all other software and start again. I would have thought if there was a mount problem, then the Dec motor would not work at all.

Thanks for the input so far.

And I think my Obsys is far away being 120feet :laugh2:

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 Forunke
      Ok, so this is a really annoying bug / problem that I have with my setup:
      From time to time, in non regular intervals the image my guiding cam (ZWO ASI120) send seems to get flipped / mirrored or looks like it's from a completely different patch of sky.
      When I'm paying attention to the guide images I can clearly see that the image seems to be flipped in some way.
      It only happens for 1 frame PHD send a warning ( No star found / Star lost Mass changed) and after that everything is fine again. My gear is all connected to a single USB3 Hub which then runs via powered USB3 cable to my Pc.
      I'm not binning and have the noise reduction off (though PHD might got hickups while processing) but it still happens. Sometimes there are minutes between two events sometimes it happens 5 times in a row.
      It also seems like it's only happening during guiding, I haven't seen it happen during calibration yet...
       
      I'm completely clueless what's happening or how to get rid of it, any help / idea is greatly appreciated.
    • By Fieldsy
      Hi guys and girls
      My qhy5l ii connects to phd2 but I dont see any image or able to click the  cam controls next to brain as it's still grey in colour. If I start up ezplanet the camera works fine and I have a display on computer. st4 cable use or dont the phd2 tutorial says burn it but in vid it's still connected to his cam?
    • By kman42
      I have an EQ5 telescope mount which i use for astrophotography. I have modified it with a motorised RA axis using a bipolar stepper motor - my thread for the build is here .
      I want to expand the mount's tracking ability by motorising the DEC axis and using a guide scope/camera. I generally use the mount in fairly remote locations so would like to use a raspberry Pi for portability.
      I understand that I'll need to use a Raspberry Pi Camera Module for the guide camera. 
      The capability I want is:
      1. guide the mount along RA and DEC axes using a guide star as feedback
      2. track the mount using the RA axis only, and if possible continuously take 20-30 second exposures on the guide camera (this functionality is optional, but would assist in polar alignment of the mount)
      I don't want any GOTO capability. I am very new to RPi and need some help:
      - do I need to write code for this, or is there existing programming available for what I want to do?
      - is it possible to avoid the use of screens (in the field)? My preferred option would be to flick a switch to start and stop the guiding, with another switch for alignment mode (or something simple like this).
      - do I need to use any particular stepper motors/drivers for raspberry Pi? I'm using a bipolar stepper motor running quarter steps, with an A4988 stepper driver
      - is the RPi 3 Model B+ the unit I should buy?
      Thanks
       
    • By Cemers1
      Hi Guys, hoping someone can help me with the guiding issues Iv'e been having. First of all my setup is:
      Explore Scientific ED80 Triplet  Skywatcher EQ5 mount with synscan  Orion mini 50mm guide scope Altair GPCAM2 AR0130 Mono (as the guide camera) I did my polar alignment and 3-star alignment, which was spot on. So I set up the GPCAM2 and opened PHD2 where I selected "Altair Camera" and "On-Camera". It was all in focus, kept it on the default settings and I selected "auto select star", then it said I was guiding (I can hear the mount making small adjustments). A message popped up saying I needed to increase the max RA duration, then I needed to increase the max DEC duration, which I did gradually by 1000ms each time the message appeared. Still no progress.
      So I restarted the process with the max RA and DEC duration as 8000ms and it said I needed to eliminate the source of the problems.
      (I HAVE ATTACHED IMAGES OF THIS)
       
      I'm not sure why it not working and if I'm doing something wrong. But if someone knows where I'm going wrong, or has any advise it will be greatly appreciated!

      Oh and just let me know if you need any more info, because Iv'e probably missed something out. 
      Thanks again ?

    • By ACross
      Hi All, I am posting what I suspect is a newbie mistake question but hoping that someone can assist with the issue of flats.
      Although I have been fumbling around the sky, taking snaps at leisure, recently I became serious.  I have read up about the different calibration files (flats, darks, bias) and they seemed to make sense; different ways to capture the image defects and extract those from the image of the sky. After a few weeks (months) of further fumbling I went back to the very first target to receive my attention, M42 Orion Nebula.
      In short, I took 20x 30s exposures in LRGB  and ran these along with 20x LRGB each of darks, bias and flats. To obtain the flats I used a diffuse sheet of perspex (lightbox material) and an LED video lamp that has 180 white LEDs, turned to its lowest setting. Attached below is the stacked Luminance flat and the light image. In the lights I am getting very strong marks from dust and I had thought that the flats would subtract this but looking at the flats the marks are completely different shapes and do nothing to remove them from the lights.
      The attached has been further stretched to show the issue. Now, I am obviously doing something wrong but I have no idea what, any pointers from the vast pool of knowledge will be much appreciated.
      Thanks, Anthony
       


×
×
  • Create New...

Important Information

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