Trouble-shooting

Calibration and "First Use" Problems

If you are just starting to use PHD2 or are connecting to new equipment for the first time, you may have trouble getting the guider calibration done.  This problem usually takes one of two forms, each requiring different responses:
  1. The star moves during calibration but it moves "too far" or "too little."  This is easy to fix - simply adjust the 'calibration step-size' parameter in the 'Mount' tab of Advanced Settings. The help content there describes how this parameter is used, and you should be able to resolve the problem quickly.
  2. The star doesn't move at all or it moves only very small amounts and in unpredictable ways.  Actually, the small movements in this scenario are often the result of seeing deflections and the mount isn't really moving at all.  Dealing with this sort of problem is described next.
In nearly all cases, the "no movement" problem is caused by failures in the hardware or, even more likely, problems in the cabling and connections.  The best tool for trouble-shooting this is the 'Manual Guide' option under the 'Tools' menu, as described in the Tools section of this help document.  Simply use the directional controls in the 'Manual Guide' window to send commands directly to the mount.  If the mount does not respond, you know you have either hardware or connectivity problems to resolve - nothing to do with PHD2.  If you're using a Shoestring device to connect to the mount, watch its indicator lights to see if the commands are reaching it.  Similarly, your ST-4 compatible guide camera may have indicator lights to show when guide commands are being received.  If you're using an ASCOM connection to the mount, be sure the COM port assignments are correct.  You can also use some of the ASCOM-supplied tools like POTH to be sure the ASCOM driver is communicating correctly with the mount.  

Program "Hangs" and Camera Download Problems

In some cases, you may experience problems where guider images aren't downloaded or displayed.  In extreme cases, this may even cause PHD2 or other camera-related applications to be non-responsive (i.e. to "hang").  Again, this is almost always due to hardware, camera driver, or connectivity issues, with one of the most common culprits being a faulty USB cable or device.  It is highly unlikely to be caused by an application like PHD2, so you should begin your investigation at the lower levels of the system. You can start by confirming that the guide camera is working - try using a short, direct cable from the camera to the computer and taking exposures with the "native" or test application that came with the camera.  If the camera is functional, you can start moving "upstream" by looking at USB hubs and cables, swapping them one at a time to see if you can isolate the problem.  It's worth remembering that we work in a "hostile environment" while doing our imaging, and many of the components we use are not designed for cold, outdoor conditions. So something that worked just last week or last month may no longer be reliable.

Poor Guiding Performance

Once you've gotten everything running, you will probably get reasonably good guiding results almost immediately.  You will have to decide what "good enough" means, and everyone's standard is likely to be different.  But if you find your imaging results are not acceptable because the stars are streaked or elongated, you'll need to take a systematic approach to correcting the problems.  This can be a complex task and not something to be covered here.  However, you can get help on the web from a variety of sources, with the document by Craig Stark being one of the best:  
http://www.cloudynights.com/page/articles/cat/fishing-for-photons/what-to-do-when-phd-guiding-isnt-push-here-dummy-r2677.

Problem Reporting

If you encounter application problems that are specific to PHD2, you are encouraged to report them to the open-phd-guiding Google group: https://groups.google.com/forum/?fromgroups=#!forum/open-phd-guiding.  Obviously, the more information you can provide, the more likely we will be able to resolve the problem.  Using the following guidelines will help in that regard:
  1. Try to reproduce the problem - if we have a clear set of steps to follow, we are more likely to find a solution quickly.  If you can reproduce it, try to reduce things to the minimum number of steps.  Remember, we won't have your hardware or computer environment when we try to reproduce it ourselves.
  2. Try to be complete about describing your configuration - operating system, equipment types, PHD2 version, etc.
  3. Attach the PHD2 debug log from the session in which you encountered the problem.  You can find the debug log in the PHD2 folder in your Documents folder. If you can't reproduce the problem, try to estimate the time of day when you first saw it - this could help us find evidence in the debug log without having to sift through hundreds of lines of output.