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_winners.thumb.jpg.9deb4a8db27e7485a7bb99d98667c94e.jpg

Recommended Posts

I connect my mount to PHD2 using ASCOM and most nights I have the error "Star did not move enough" as well as "Suspicious blah blah, axis may not be perpendicular". This does not happen when I connect the mount via ST4 cable. I read somewhere that I can do a Calibration Sanity Check in PHD2. I am however unable to find that function in the software. Is it some pop up feature or does it have a location in the settings/brain icon?

Any help will be highly appreciated.

Share this post


Link to post
Share on other sites

Please post the guide log with the calibration causing a problem. You can find them from the help menu option to open the log files folder.

Share this post


Link to post
Share on other sites

When you swap between on-camera (ST4) & Ascom control, have you re-configured PHD2 in the connect equipment settings ?   If everything else is the same i.e. same camera, guide scope etc., then you calibrate by selecting looping, click on a likely target, then hold down the shift key while clicking on guiding. This will force a re-calibration. 

Share this post


Link to post
Share on other sites
On 05/09/2018 at 04:42, astrosathya said:

Star did not move enough" as well as "Suspicious blah blah, axis may not be perpendicular

Hi, did you also increase the ra rate and dec rate value under ascom pulseguide settings?  It's recommended to increase   to about 0.5. 

Edited by Atreta

Share this post


Link to post
Share on other sites
6 hours ago, Atreta said:

Hi, did you also increase the ra rate and dec rate value under ascom pulseguide settings?  It's recommended to increase   to about 0.5. 

Ah, no, I haven't I'll do that tonight and check

 

Share this post


Link to post
Share on other sites
On 05/09/2018 at 08:42, astrosathya said:

I connect my mount to PHD2 using ASCOM and most nights I have the error "Star did not move enough" as well as "Suspicious blah

If you move the mount with the on screen handset North just before you calibrate it takes the backlash out of the DEC, otherwise the software is trying to move the star and it can't so it gives up..click on N until it moves the star,then callibrate..hope it helps

  • 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 Alex the great
      Hello everybody on this community, very happy I recently joined stargazers lounge.com
      Last November I was able to modify my EQ5 mount via shoestring astronomy GPUSB (ST4 mount-USB laptop, my guiding camera is connected to the laptop by USB and PHD2 as guiding software) so I can autoguide it for long periods 6 minutes and more, I was really happy that this project was achieved and now I can get more details out of deep sky objects.
      My question is how can I go GOTO with this set up, trying to find objects to image is really time demanding without GOTO, and my goal is to take advantage of time to get those photons.
      I installed already ASCOM but I didn't connect with the USB connection (I think only work with serials cable)
      Thanks in advance for your valuable comments
    • By BUDA
      Hi All!

      I have guiding problem with the following guider setup: 9x50 finder + ZWO ASI 120mm mini + PHD2.
      The imaging scope is a 6' newtonian + canon dslr on a HEQ5, driven by a laptop via diy EQDIR cable.
      When the mount is set up and running correctly, polar aligned and all... I connect the guider camera
      and mount with phd2. All nice and easy, I run a calibration, then it starts to guide. All seems ok.

      Then I am starting to take pictures. The first seems OK, then the second have the star trails...
      I check phd2 and there is a message: the camera (ASI) did not take a picture for "xy" seconds so it is disconnected.
      Grrr.... I reconnect try to set up a longer period for "xy" in the settings as mentioned in the message.
      And all the same again and again. Whatever I add for connection timeout for the camera, it just reaches that
      and disconnect the camera.
      PHD + philips toucam has worked for me flowlessly. I changed to PHD2 because I gave myself a birthday present,
      the little ZWO camera. (and PHD did not recognize it)
      Do you have any idea what can be the problem? I will contact PHD2 help also, but maybe somebody had already
      the same problem and figured out how to overcome. I am almost sure I make some dumb mistake in the PHD2
      software settings, however I tried to change only what was needed.
    • By Pitiss
      I have recently bought a Orion Starshoot Autoguider. I downloaded phd 2, eqmod and ascom stuff. After a small research I found out my mount (exos 2 gt) doesn't support computer acces without firmware upgrade and fancy cables but I have the st4 port so it shouldn't be a problem. In phd I choose camera as Starshoot Autoguider and mount On-Camera. Aux mount and AO are both none. My wiring is one cable to pc from camera and another to st4 port from camera. When I started looping I selected the star with no problem. I choosed the one star alignment option from my hand controller and after centering the Archturus in the middle of view I pressed ok and it was successfull. I started guiding and after a while I get the error: RA calibration failed star didn't move enough.
    • By Tom Shinal
      Can Nebulosity and Ph.D operate simultaneously and share a single camera. Running Win 10.
       
    • 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.
×
×
  • Create New...

Important Information

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