phd guiding forum

5 Tips for Better PHD2 Guiding

PHD2 is a telescope autoguiding software that automates the process of tracking a guide star. This is an important aspect of deep sky astrophotography because it allows you to focus on capturing successful long exposure images and get the most out of your telescope mount .

PHD2 is easy enough for a beginner to use right away, yet also includes sophisticated guiding analysis tools that experienced users will appreciate. The software is available for Windows, Linux and Mac operating systems. The built-in help file inside PHD2 contains a wealth of information, or you can download the instruction manual here .

My autoguiding graph in PHD2 using the Sky-Watcher EQ6-R Pro telescope mount

PHD2 Guiding Settings for Astrophotography

I have found PHD2 Guiding to be an incredible tool for my backyard deep sky astrophotography. I have been using this software for a long time, starting with the original PHD “1” verion. The latest version of the software (PHD2) has been totally overhauled by a team of passionate developers that aim to make autoguiding even better.

Download the latest version of PHD2 Guiding

The guys over at the Astro Imaging Channel released an informative video featuring one of the team members of PHD who worked on the software.  Andy Galasso quickly reveals just how passionate he is about the project, and how knowledgeable he is with the PHD guiding software.

The video is quite long, but contains a wealth of information about autoguiding with PHD:

The intelligent folks over at PHD can explain the full power of PHD2 guiding better than I can, but I thought I would share what I personally took away from this enlightening presentation.  Before adjusting the settings in PHD2 Guiding, it is important to make sure that your equipment is prepared for imaging.  This includes accurate Polar Alignment and balancing the weight of your payload.

How to use PHD2 Drift Alignment

Here are the top 5 tips I gathered from watching Andy explain exactly how to use PHD2 guiding for best results:

Use the Guiding Assistant

Find this feature under Tools > Guiding Assistant

As Andy puts it, you’ll want to observe an unguided star motion to see what you are up against. This gives you a window into the amplitude of the RA (Right Ascension) periodic error.  Again, explore this tool for a more detailed insight into your particular mount’s characteristics.

The Right Ascension Max Drift rate displayed in the guiding assistant will display a recommended guide exposure length.  Very handy!

Create a New Profile using the Wizard

The built-in equipment profile wizard in PHD2 guiding allows you to tell PHD exactly which hardware you are using.  Here you can set all of the specific details of your gear.  This includes entering in your guide scope focal length and autoguiding camera pixel size.

At this point it will also prompt you to build a dark frame library.  You’ll want to make sure that PHD2 Guiding is making the necessary corrections relevant to your unique setup.

Use Auto Star Select

PHD 2 Guiding has an advanced feature that calculates the best possible star in your field of view to use for guiding.  It will select a star based on algorithms to avoid over saturated or poorly sized stars.  Why not let PHD choose the best possible star, rather than guessing yourself!

In the past, I would try to select a star that was “medium-sized” and near the center of the frame.  This guessing game no longer takes place thanks to the auto star select feature within PHD2 Guiding.

Try using longer guide exposures

In the video, Andy explains that his tests show that using longer guide exposures results in fewer pulse corrections needed. This was a big eye-opener for me, as I had never given much thought to the guide exposure length I would use.  Generally, my guide exposures were about 1 to 1.5 seconds.  The diagram below illustrates how longer guide exposures can provide a smoother graph:

He recommends using longer guide exposures for improved performance. Earlier, I mentioned using the guiding assistant to give you a recommended guide exposure length.  In the example used for Andy’s equipment, that was an exposure of 2.7 seconds.  As a rule of thumb, do not expose so long that the stars begin to over saturate, or PHD will not be able to provide an accurate pulse correction.

Use the graph. Over/Under Correcting

When looking at the graph in PHD, remember that blue is RA , and red is DEC .  If your graph displays a zigzag pattern like the one below, it is a good sign that you are over-correcting.  Toggle the “corrections” check box to get a visual reference for exactly what PHD is doing.

If you are over correcting, the solution is to decrease the aggressiveness and increase your RA minimum motion.  On the other side of the coin, if you are under-correcting, your graph will look like the image below:

For more information about autoguiding with PHD2 Guiding, please visit the Open PHD Guiding Google Group Forum or the Stark Labs Astronomy Software Forum on Yahoo .  These forums offer answers to many of the troubleshooting issues you may experience while using PHD for astrophotography.

Clearly, I am still learning the ins and outs of this software myself.  I hope to improve my knowledge of PHD2 this year to get the most out of this amazing free resource for astrophotographers.

Improved Autoguiding with the iOptron CEM60

In October 2017, I tested out a new astrophotography mount, the iOptron CEM60 .  One of my main goals was to see if this mount could outperform my Sky-Watcher HEQ-5 Pro in terms of autoguiding, and overall tracking performance.

Have a look at the PHD2  graph I was able to achieve while imaging early on in my testing.  The total RMS error was less than 1 second, and noticeably better than anything I had seen using the HEQ-5 Pro. 

However, the fact that I was now pulse guiding via ASCOM to the mount directly may have made a difference as well.  (This can be done on the Sky-Watcher HEQ5 as well)

PHD Guiding with the Sky-Watcher EQ6-R

A new telescope mount presents an opportunity to compare guiding performance. The Sky-Watcher EQ6-R was very impressive in terms of autoguiding performance right out of the gate. Using the default settings with PHD and the generic ST-4 mount connection, I was able to achieve an impressive guiding graph.

In the screenshot below, you’ll notice that the total RMS error is 0.16 (0.63″). This resulted in an incredibly sharp image with round, pinpoint stars in each frame. Autoguiding with a telescope mount like this means that you will never have to discard image exposures due to bad guiding, and elongated stars. 

My PHD guiding graph using the Sky-Watcher EQ6-R mount

Related Posts:

• Using PHD2 Guiding with the Lodestar X2 Guide Camera
• Autoguiding Camera for the ASIair – ZWO ASI290mm Mini
• Astrophotography Resources: Software and Tools 

New to phd2

Scott SCHNEIDER

Bruce Waddington

On Oct 7, 2023, at 12:14 PM, Bruce Waddington < [email protected] > wrote:

I don't know how to interpret your comment of "aside from the obvious balancing the mount".  If you already know the scope is out of balance, I think it would make sense to fix that first.  There are many times during your session when the guide star made a big excursion in Dec - not because of a guide correction and the Dec motor wasn't even running at the time.  This shows up in the Guiding Assistant session as well as many other places when guiding was active.  The direction of movement changed so I don't know how this could be explained by a balance problem.  A common cause with an OAG is cable routing problems that allow a cable to tug slightly on the guide camera.  Here are some examples (Dec is in green) - the first one happened during the GA run:

<Dec_GA.jpg> And here are some more while you were imaging:

<Dec_Excursions.jpg> These are the easiest things to identify although they can be challenging to fix.  You can do it yourself using the LogViewer tool and the associated log analysis tutorial: https://openphdguiding.org/tutorial-analyzing-phd2-guiding-results/ https://openphdguiding.org/phd2-log-viewer/ Regards, Bruce On Friday, October 6, 2023 at 12:02:20 PM UTC-7 [email protected] wrote: Hi  I just uploaded my guide logs from last night.  Just wondering if there are some things I could do to improve guiding, aside from the obvious balancing the mount... Thanks https://openphdguiding.org/logs/dl/PHD2_logs_QGCB.zip

-- You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] . To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/4a27f347-84ae-4fca-ae49-661c09e9283fn%40googlegroups.com . <Dec_GA.jpg> <Dec_Excursions.jpg>

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/2778a669-8fc5-45d0-bfbc-863fb81306d8n%40googlegroups.com .

You should start by seeing if you can get a periodic error correction (PEC) programmed in your mount.  You can use PemPro for that (free trial) and see if it improves your mount’s RA tracking.  PHD2 has nothing to do with that, it’s between the mount controller and PemPro.  Don’t get it confused with PHD2’s Predictive Periodic Error Correction (PPEC) which is completely separate and can be used whether the mount has PEC enabled or not.

You adjust the mount guide speed using the mount driver or the hand-controller.  PHD2 never changes the mount guide speed, it only reads the setting from the mount driver.  Once that’s set, run the PHD2 Calibration Assistant and it will offer to adjust your settings because of the new mount guide speed – let it make those adjustments.

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/C0715CEE-7FB2-459C-ADD5-69996CFD2BB7%40gmail.com .

To view this discussion on the web visit   https://groups.google.com/d/msgid/open-phd-guiding/004a01d9fa56%241b7a9490%24526fbdb0%24%40earthlink.net .

• Imaging - Tips, Tricks and Techniques

• Remember me Not recommended on shared computers

Forgot your password?

PHD Guiding Basic Use and Troubleshooting

• phd guiding
• long exposure imaging

By IanL June 20, 2013 in Imaging - Tips, Tricks and Techniques

Recommended Posts

• Popular Post

Pleas for help with PHD guiding seem to come up more often than almost other imaging topic. I make no claims to be the ultimate expert on the subject, but I have travelled some way along the road from guiding failure to success, and so I thought it might be good to share a few pointers I've picked up along the way.

(By failure I mean I was getting one 1 minute exposure out of every five where the stars were slightly less egg-shaped than the rest. By success I mean I now discard one 10 minute exposure out of every thirty due to a guiding issue).

Firstly, I am going to cover the basics of a good guiding set-up, since many problems that are blamed on PHD are actually external issues related to the equipment being used or abused. After that I’ll take a look at how to diagnose and fix guiding problems with PHD.

If you are imaging DSOs, you will inevitably be drawn to the idea of guiding in order to be able to make longer exposures. That said, if you aren't ready to invest in a guiding rig yet, you certainly can improve your exposure length by better polar alignment and by using Periodic Error Correction (PEC) if your mount supports it. Eventually you will reach the limits of what is possible, or more likely the limits of your patience due to the amount of effort required before you can start imaging.

Personally, I skipped the middle bits and went straight to guiding! Polar alignment of my NEQ6 mount consists of putting the tripod on some painted marks on the patio and spending five minutes using EQMOD and the polar scope to do a rough alignment. I don’t drift align and I don’t use PEC; I rely on my guiding rig entirely.

As we will discover, the longer the effective focal length of your imaging scope, the more likely it is you will also need to get good polar alignment, to use PEC as well as guiding, or drop five or ten grand on a new mount! That said, using a short focal length scope on a decent mount and with an effective guider makes the mysteries of polar alignment and PEC a lot less important when starting out.

Do I Really need Two Cameras?

You cannot image and guide at the same time using one camera. The guide camera image needs to be read-out every few seconds to spot when guiding corrections are needed. The imaging camera needs to take a long exposure, and reading out the image ends that exposure, so you can’t do both at once!

The only exceptions are self-guiding cameras, which consist of two cameras in one housing (see below), and some old cameras where one set of pixels was read out for guiding and another set used for imaging. The latter type wasn't particularly successful and I don’t think you can get them any more.

There are many cameras on the market that can be used for guiding. Many people start by experimenting with webcams. These can work if your guide scope has a particularly fast focal ratio, but the lack of a long-exposure feature usually means you will be looking for a proper guide camera fairly quickly.

If you are a planetary imager, you may already have a colour planetary camera; provided it can be set to take long exposures of at least a few seconds in duration and has an appropriate driver for PHD (or other guiding software), it will work as a guide camera,

Alternatively you can buy a dedicated mono guide camera for between £100 and £150; keep an eye on the second hand market as these come up for sale regularly.

The final option is an auto guider, which tend to be more expensive than the cameras above. The advantage of an auto guider is that you do not need a laptop to guide; all the brains are built into the camera and guiding commands are sent via the ST4 port to the mount without a computer involved**. I haven’t used an auto guider but reports of their success tend to be mixed; either they work or they don’t, and if they don’t it can be hard to diagnose the issue. On the plus side, most auto guiders can also be used as a ‘dumb’ guide camera in conjunction with PHD or other software.

** Note that not all cameras with a built in ST4 port have auto-guiding capabilities, so check the specifications.

How to Choose the right Guiding Set-up

There are three basic methods of guiding with various pros and cons:

1. Using a separate guide-scope and guide camera.

A second, cheap telescope or finder and a cheap(ish) guide camera is mounted piggyback on top of the imaging scope, or side-by-side using a dual bar.

Pros: Relatively cheap to purchase. Quick and easy to set up and use. Two telescopes on one mount looks really cool, like some kind of awesome space cannon.

Cons: Flexure, mirror shift, flexure and flexure.

When to use: On lower end mounts like the HEQ5, NEQ6 and cousins, a separate guide scope works best with shorter-focal length scopes.

2. Using an off-axis guider (OAG).

An OAG sits between the focuser and the imaging camera. It uses a small prism to deflect part of the incoming light into the guide camera.

Pros: Relatively cheap to purchase. Much less weight on the mount as there is no second scope. Reduces problems with flexure and mirror shift.

Cons: Some people swear by OAGs, others swear at them. They have a reputation for being fiddly to set up and use for beginners, as you must get both the main camera and the guide camera parfocal and also locate a suitable guide star by moving and rotating the prism.

When to use: A better option for long focal length scopes, and a much better option for moving-mirror scopes like SCTs.

3. Using a self-guiding imaging camera.

A camera with a main imaging sensor, and a second (smaller) guiding sensor next to it.

Pros: Much less weight on the mount as there is no second scope. Reduces problems with flexure and mirror shift. Much easier to set up than an OAG.

Cons: Only a few higher end (expensive!) CCD cameras available.

Exposures Deeper than your Pockets?

If you are just starting out in deep-sky imaging, it is important to realise than long-focal length imaging is hard on low-end mounts. Very hard. Don’t be fooled by all those glossy adverts in the magazines, anything in the sub £2,000 bracket is definitely low-end. Don’t take that remark the wrong way! Mass-market GOTO mounts have made deep-sky imaging accessible to us mere mortals, but understanding the capabilities and limitations of your equipment is key to success in this game.

The first tip is to learn your craft using a short focal-length, fast f-ratio scope. Guiding is much easier, and you’ll get better results with shorter exposures (a virtuous circle). Aim for a focal length of no more than 800mm and an f-ratio of no more than f/6 (and if you have the budget to get to f/5 or f/4 with decent optics, so much the better).

If you have an existing longer-focal length scope you might use a focal reducer, or if you are looking for a new scope, invest in a mid-range refractor (the ubiquitous Skywatcher 80ED with the matching 0.85x focal reducer/flattener is where many people start out, but there are many similar models to choose from at a variety of price points from reasonable to eye-watering!)

I learned lesson this the hard way. I started out with lunar and planetary imaging through an ancient 8”, f/10 SCT (a relic of the pre-GOTO age). The 2,000mm of focal length was great for that sort of thing, but as I soon discovered when I purchased a shiny new NEQ6, it isn't so great for learning how to do deep-sky imaging:

- 2,000mm is probably approaching (if not beyond) the limit of what an NEQ6 can track in the hands of an expert imager with years of experience. In the hands of a beginner like me, results were frustratingly poor and I wasted many nights getting nowhere fast.

- f/10 is very slow for DSO imaging, necessitating long exposures. But long exposures were not possible (see above). A vicious circle not a virtuous one.

Minimise Weight

All mounts will quote a maximum weight that they can carry. Firstly, check whether the quoted weight is just that of the scope and other equipment or whether it also includes the counterweights (which has been the case in some more dubious marketing materials).

The next tip is that once you know the maximum equipment carrying weight of your mount, divide it in half. That is the target weight for all of your imaging equipment; the imaging scope, guide scope, cameras, dovetail bars, scope rings and anything else you want to hang off the mount. You will be much more likely to succeed with grossly over mounted equipment than you will with a mount that is struggling at close to its maximum carrying capacity.

I know the feeling well, “If I buy the HEQ5 instead of the NEQ6 I can spend the extra money on a bigger scope..” Bad decision. Buy the big mount and the small scope; if you’re serious about imaging there will always be another scope along later!

Managing weight is always a compromise. Finder-guiders are cheap and lightweight but may have too short a focal length for your imaging scope (see below). Losmandy-style dovetail plates and solid tube-rings add weight, but lightweight alternatives may make it hard to avoid flexure (again see below). You will find it helpful to weigh your components or check the specifications of any potential purchases and keep a running tally of the total.

Choose the right Guide Scope and Camera

In order to have the best chance of guiding successfully, you need to match your guide scope/camera to your imaging scope/camera. Now I know you may have read some received wisdom that when using PHD Guiding you don’t need to worry about matching the guider and imager; that is true but only up to a point.

The next tip is to is to match the pixel scales of the guider and imager. By ‘pixel scale’ I mean the angular resolving power of the scope/camera combination in arcseconds**.

If you are using an OAG or a self-guiding camera, even though you are guiding and imaging through one scope, it is still worth understanding whether your imaging camera, guide camera and scope work well together or not. (It is unlikely that you will have a problem unless you have a ridiculous difference in pixel sizes between the two, but knowledge is power!)

PHD Guiding can track the centroid (centre point) of a guide star to ‘sub pixel accuracy’. Basically it is able to calculate the position of the guide star down to a fraction of a camera pixel. This leads people to the erroneous conclusion that they don’t need to worry about matching pixel scales of guider and imager because PHD can “track to a 10th of a pixel” or even “a 50th of a pixel” (depending on who you ask).

In theory that is true, but in practice you are not likely to get PHD guiding reliably to more than one quarter of a camera pixel. So a good rule of thumb is your imaging pixel scale should be no more than four times your guiding pixel scale. You might be able to exceed 4x by some margin, but sticking to less than that will make your life much easier.

So how do you calculate your pixel scale?

pixel scale in arcseconds per pixel = (camera pixel size in µm / scope focal length in mm ) x 206.3

So I image with a Canon EOS 500D with pixels that are 4.7µm square and a Skywatcher Evostar 80ED and 0.85x Reducer with an effective focal length of 510mm:

(4.7µm / 510mm) x 206.3 = 1.9 arcseconds per pixel

I guide with a QHY5 with pixels that are 5.2µm square and an Orion ST80 with an effective focal length of 400mm:

(5.6µm / 400mm) x 206.3 = 2.67 arcseconds per pixel

If you don’t feel like doing the maths, use my Imaging Toolbox to do the hard work for you. The upshot is that I my imaging resolution is about one and a half times my guiding resolution (2.67 / 1.9 = 1.41). That is well within the 4 x rule we established above.

Don’t forget, you can use a Barlow lens or a focal reducer to adjust the relative pixel scales of imager and guider. For example, the quality of the image through the guider is not critical so a cheap Barlow can be used cut the number of arcseconds per pixel if needed.

Now there is a lot more that could be said about the optimal pixel size of imaging cameras vs different scopes, but that is another topic. The best advice I have read is that your first priority is to have a scope and camera combination that can fit your target in the frame, and to worry about everything else later! Again using the Imaging Toolbox you can try different combinations of scope and camera to see what works.

** One arcsecond is 1/3600th of a degree, which is a pretty small angle.

Eliminating Flexure

Differential Flexure occurs when the imaging rig and the guiding rig end up pointing in different directions over the course of one exposure. There are two main causes of flexure:

- The guiding rig and the imaging rig are not joined together in a mechanically sound way. As the mount moves to track the sky, gravity or cables pull on one part more than the other and they end up pointing in different directions. Usually this is simply a matter of loose mechanical connections between the two scopes allowing them to bend or twist out of alignment.

- Parts of one of the rigs move, causing the image to shift. The two most common causes of this are the mirror shifting or flopping in SCTs (and other moving mirror scopes), or a drooping focuser tube which bends under gravity. Technically these are not ‘Differential Flexure’ but the net effects are the same, as are the solutions.

The fundamental problem is that PHD will be successfully keeping the guide star in one spot on your guide image, but because the guide scope image is moving relative to the main scope image, the main image ends up trailing.

If you are using an SCT or similar scope, an OAG or self-guiding camera is the surest way to address this problem. As the mirror flops under gravity, the guider sees the image shifting in exactly the same way as the imager does and compensates for it.

If you are using a piggy-back or side-by-side guide scope, you may find that you get good results when the scope is pointing in one direction, but not in another. This is often a sign of mechanical flexure of some sort, as the effect of gravity causes things to bend more in some orientations than others.

The next tip for guide scope users is to sort out your mechanical connections:

- The biggest culprit is adjustable three-point guide-scope rings (like a set of giant finder-rings). The ones with plastic screws are an absolute disaster, and even the plastic-tipped metal screw variety can cause problems. Avoid at all costs and use a set of solid scope rings for your guide scope: We've all got a set of three-pointers in the bottom of the junk box having learned the hard way!

(You do not have to have the guide scope and image scope perfectly aligned for short focal length exposures of 10 or 20 minutes, and with a decent guide camera you won’t need to hunt around for a guide star.)

- If you are using a finder-guider, try to use a pair of solid rings. Avoid three-point finder rings if possible (especially plastic screws), and never use a the rubber o-ring type of finder holder that you get on many cheap scopes!

- Check for cable snags or pulls. It is tempting to leave a nice long loop of cable from the cameras to the computer to avoid it snagging on the mount, but the weight of the cables can be enough to cause flexure. The best solution is to run the cables from the cameras up the scope tube to the midpoint of the scope without leaving a big loop, fix them there with Velcro or a tie and then run back to the computer from that point.

- After that you will need to look at the connections between mechanical components for signs of flexure. If you can hold the imaging scope in one hand, the guide scope in the other and make them move visibly by applying gentle to moderate force, you may well have an issue! Even if things look solid, it only takes a few arcseconds of flexure to ruin an exposure, and the amount of movement between the scopes needed to cause that is imperceptible to the human eye. Tighten up bolts (but beware of over-tightening and stripping threads), file any contact surfaces flat, add shims, washers, extra bolts, screws and brackets as needed to keep everything rock solid.

- Check your focusers for droop. The focus tube will be pulled downwards under gravity and as the scope rotates it can cause the guide image or the main image to shift. Make sure your focuser tensioning screws are properly adjusted; you should be able to point the scope straight up and not have the weight of the camera cause it to slip. Also apply the lock screw as part of the focusing process if you have one. Using it can cause the focus to shift in cheaper models, but it will reduce the tendency to droop or slip, so learn where to set the focus point to allow for this final shift. Ultimately you may need to fit an upgraded focuser if you have a heavy camera.

Other Causes of Trailing that are not Guiding-related

Camera non-orthogonality causes elongated stars. This means that the camera sensor is not exactly perpendicular to the telescope’s focal plane, so the stars get stretched in the direction of greatest tilt. You can diagnose this problem as follows:

- Aim the telescope at a group of bright stars about 40 or 50 degrees above the horizon and take a short exposure of a few seconds, long enough to capture the stars but short enough that you would not get trailing due to poor tracking. Look at the image and see if all the stars are elongated in the same direction. If so, it is likely that you have non-orthogonality.

- Now rotate the camera through 90 degrees with respect to the telescope and take a second short image. Figure out which direction is ‘down’ towards the ground in each of your pair of images. If the elongation in both images is in the up/down direction, then you most likely have a problem with the focuser or other element drooping under gravity.

- If the direction of elongation changes as you rotate the camera, then you probably have a mechanical problem in the imaging train. Very occasionally the problem can be with the camera sensor not being parallel to the mounting ring on the camera body, but it is more likely that something is cross-threaded or not fully screwed together. I recently had a problem with a retaining ring in a light pollution filter that was not fully screwed in and this caused the camera to about 0.5mm off true.

My next tip is to obtain a set of digital callipers. These are invaluable in checking orthogonality of the various elements in the imaging train, as it can be pretty hard to spot small misalignments by eye. Use them to measure the gaps between the same points all the way around the focus tube or other element to ensure that it is the same. As a bonus, you can use them to measure and subsequently set the focus position of your scope at the start of the night.

Optical aberrations such as coma can cause elongated stars. This is easy to diagnose as aberrations cause elongation in different directions across the image (typically pointing outwards from the centre towards the corners), whereas guiding issues will cause trailing or elongation in the same direction for all stars in the image.

Vibration is a common problem that is easily mistaken for poor guiding. There are two main causes of vibration:

- Environmental causes, typically you, dear reader. You need to do your best to isolate your mount from external sources of vibration. A solid tripod or pier, anti-vibration pads, etc. The list of cures for vibration is endless and I’ll leave you to do your research on that one. If your imaging software allows it, program in a pause before the first image is taken. Use that time to walk away from your scope since your size tens are more likely than not to be a source of problems even on a solid concrete pad.

- Camera-induced vibration is typically a problem for DSLR imagers. When starting an exposure, the mirror makes a very satisfying ‘clunk’ as it flips up out of the way before the shutter opens. That tends to induce plenty of vibration in the imaging rig. Most astro-DLSR applications have the ability to program a pause between the mirror lock-up and opening the shutter. I recommend setting this pause to at least five or ten seconds to allow vibration to die down.

Wind is also a big issue. If you find you are getting erratic guiding or stars that look like they have been drawn with a spirograph (wiggly lines all over the place), it may well be that the wind is causing your scope to wave around like a windsock. Bigger the scopes like Newtonians have more surface area and can suffer from this problem more. Look for a sheltered spot or wait for better weather.

Poor Seeing is also a problem. There are techniques that can help with this (see below) but you will find that the quality of your guiding definitely varies according to the seeing conditions. If you get it right, you’ll end up with bigger (but still round) stars on nights of poor seeing, but if you get it wrong you can end up with trailing or wiggly lines as above.

ST4 Cable or ASCOM Pulse Guiding?

As you may be aware, there are two typical methods of sending guide corrections to the mount. Some cameras may be connected directly to the mount by means of an ST4 cable, so guiding corrections are sent by means of electronic signals to the mount controller board. Alternatively, guide corrections may be sent through software via the mount driver (typically the ASCOM platform and drivers on a Windows PC).

Which is ‘better’? The reality is that neither method is intrinsically better than the other. There is no performance advantage in using an ST4 cable over using ASCOM pulse guiding, as the time taken for corrections to reach the mount is minuscule compared to the duration of even a 1 second guiding exposure.

If you are using an auto guider which calculates its own guiding corrections on the camera, then using ST4 may make things simpler as you can do away with one set of drivers on the laptop (or not use a laptop at all if capturing images directly on a DSLR memory card). We are talking about PHD guiding here though, so I’ll assume that isn't the case.

- If you wish to use an ST4 cable with PHD guiding, you should select ‘On Camera’ from the PHD ‘Mount’ menu to tell it to send guide commands via the camera’s ST4 port.

- If you wish to use ASCOM pulse guiding you would select ‘ASCOM’ from the mount menu, and choose the appropriate mount from the dialog when you press the ‘connect to mount’ icon on the PHD tool bar.

- For non-ASCOM mounts supported by PHD, you’d choose the appropriate mount from the menu instead.

To PEC or not to PEC?

Periodic Error Correction (PEC) is a feature of some mounts and/or their drivers. All mounts will suffer from Periodic Errors in tracking in the RA axis, which relate to the rotation of the RA gears (gear periods, hence the name). As the gears rotate, machining imperfections in the gears cause the tracking to drift East and West of the correct position in a repeating cycle. The PE of a high end mount might be a few arcseconds, but on a low end mount (sub £2,000) a PE of 10 arcseconds is considered ‘good’, and figures much higher than that are not uncommon.

PEC records those errors by monitoring guiding corrections for at least one full cycle of RA worm gear. Subsequently the mount (or driver) plays back those errors to correct the tracking before it drifts off target. When used properly, PEC should be superior to guiding alone since it prevents most of the tracking errors before they happen, not after they are detected.

Whether you should use both PEC and guiding together is an ecumenical question! If used properly, then PEC should give superior performance to guiding alone, but I am definitely in the camp that thinks it is rather a lot for a beginner to take in conjunction with learning the ropes of guiding.

If you are using an HEQ5, NEQ6 or related mount with the EQMOD drivers on your laptop and you also want to use EQMOD’s PEC features, you should definitely use ASCOM pulse guiding. The drivers have been written to properly combine the PEC corrections with pulse guide commands from PHD (or any other software that produces pulse guide commands). This avoids conflicts between PEC and PHD which could otherwise over or under-correct guide errors, whereas using an ST4 cable with EQMOD PEC may result in such problems.

(Thanks to Chris Shillito, EQMOD guru and all-round good guy, for his many patient posts on this subject which I am paraphrasing here).

Proper Preparation makes for Pixel Perfect Performance

My next tip is to do as much testing as possible during the daytime. It is much easier to solve problems when you are warm, indoors and have plenty of time. Trying to solve problems in the dark, cold and when you feel like you are wasting precious imaging time is a recipe for silly mistakes.

- Do a dry run of your entire set-up and imaging routine. Check you know where all the cables go and that they are not loose or prone to disconnection. Check that all the software can see the cameras, mount, etc. Ensure that all drivers are installed and properly configured. Last of all do a complete ‘systems check’ to ensure that everything works together. I have had many issues where individual components work fine, but fail when asked to work together, e.g. EQMOD works on its own, but not with PHD connected, or APT works but not with EQMOD, etc.

- Check your guiding rig can achieve focus. You may find that you don’t have sufficient back-focus on your guide scope or finder and you need to add an extension tube. Focus on a distant object in daylight to verify this.

- Note the focus position of your guide scope and your imaging scope. You can get close during the day but you will need to refine this by focusing on a star. Again I have wasted many hours struggling to get cameras focused; unlike eyepieces it can be incredibly hard to tell where the focus point is until you are almost there, and how do you even know if you have a star in frame if you are way out of focus?

- Once you do have good focus on both scopes, measure the length of focus tube that is out of the focuser body. You could mark it with a pen (not good for resale value), or make a focus measure with a strip of metal or stiff plastic that just fits between the camera and the focuser body when you are in focus. You can sit it on the focuser tube and instantly get close to the focus point with no effort.

- Review the software settings described in the sections below until you are familiar with them and have a reasonable idea of what they do. It can be very confusing at the outset with so many knobs and dials to fiddle with, so try to learn as much as you can during the day or when it is cloudy.

- Test that PHD can connect to your camera and mount, and that it can send guide commands which are acted upon:

Camera: Firstly connect to the camera by pressing the ‘camera’ icon on the left of the PHD tool bar. A dialog box will pop up and give you a choice of camera types to choose from. You’ll have to read the manual (or search the forums) for advice on which option is the right one for your camera as they do vary, and debugging camera drivers can take a fair bit of time when you first start out!

It is worth knowing that some cameras allow you to adjust the camera gain (brightness) from within PHD using the ‘Cam Dialog’ button at the right of the PHD tool bar, but for other cameras you can only adjust the settings at the point where you first connect to it. If so, you will need to use the camera button to disconnect/reconnect the camera each time you want to make an adjustment.

You will not see anything on screen when you connect to the camera. The next thing you need to do is press the ‘Loop’ button, the blue circular arrow third along on the tool bar. This will start taking repeated exposures (by default 1 second exposures). You can test whether the camera is working by covering and uncovering the scope (the PHD display should go black when covered and brighten up when uncovered). If you see nothing, then it is time to check your drivers, adjust dialog settings to increase/decrease gain, etc.

Mount: Next you should test your mount connection. Make sure you select the appropriate mount from the PHD ‘Mount’ menu and then click the ‘Telescope’ icon second from left on the tool bar. You may be presented with a dialog to choose the mount driver depending on the model; again check the forum for advice on your specific mount.

Test Guiding: The final check (for now) is to ensure that your guide commands are making it through to the mount. Once you have successfully connected to the mount, you should set it to sidereal tracking rate (using EQMOD, the mount handset or whatever method is appropriate to your mount).

Listen carefully to the mount and you will probably be able to hear the mount motors driving the mount as it tracks (it may be a very quiet singing/whistling sound for example). You won’t see the mount visibly moving though, as it will take 24 hours to rotate 360 degrees in RA.

Next go to the PHD ‘Tools’ menu and select ‘Manual Guide’. You will see four buttons to send short guide commands in North, South, East and West Directions. Start by repeatedly clicking the ‘West’ button and listening carefully to the tracking mount. You should hear the motor sounds change slightly as you click, which indicates that the guide command was received and acted upon. Next try the ‘East’ button. In this case you may hear the motor sounds change or more likely stop momentarily. Finally try the ‘North’ and ‘South’ buttons and you should hear the Dec motor starting up and stopping.

Bear in mind these sound are quite subtle and you may not be able to detect them. If you can point the main scope at a distant object and use a high-power eyepiece, you can visually check whether the mount is moving when you click the manual guide buttons. If not, you will have to wait until you can get it out under the stars, but it is better for your sanity if you can confirm that PHD is in control of your mount during the hours of daylight.

Aligning the Mount for Imaging

Now when I said Polar Alignment wasn't that important, I didn't mean you can forget about it entirely. You should certainly perform a reasonable polar alignment using the polar scope and the appropriate procedure for your mount for two main reasons:

1. Whilst some new mounts and/or software can get your scope’s GOTO aligned however bad your polar alignment, most mounts still rely on a reasonable polar alignment to get the process started. If you can’t get your scope’s alignment routine going, you aren't going to be imaging very much.

2. Both equatorial mounts and fork mounts on wedges rely on polar alignment to track the sky properly. If you have a poor polar alignment, your exposures may well suffer from field rotation. Basically the stars will not stay as pinpoints but will form short curved arcs instead. This is more likely the longer the exposure length and/or the longer the focal length of your imaging scope. With a short focal length scope for (say) ten minute exposures, a polar alignment done with just the polar scope will be fine. If you’re imaging with a long focal length scope and going for hour-long exposures, then you may well need to drift align to avoid field rotation.

It is worth noting that using a guide scope that is not aligned with the imaging scope can also cause field rotation, but the same caveats apply, i.e. for a short focal length/short exposure don’t worry about it too much.

Before we go any further, there are some important points to understand about how the mount’s mechanics work:

- All mounts track by means of motors which drive a system of gears; one motor and set of gears for the RA axis to track in the East-West direction, and one motor and set of gears for the Dec axis to track in the North-South direction. In a mass-produced mount, those gears are manufactured to a price; they are not hand-crafted things of beauty and they will have various imperfections that cause tracking errors.

- In even the most perfectly made set of gears, there is an amount of ‘backlash’. Put simply, there has to be a gap between the gears; if they fitted together perfectly then the gears would be unable to turn at all. That gap causes problems when the gears reverse direction, since the gear has to turn a certain amount to stop pressing on one side of the teeth and start pressing on the other, so there is a delay before the gears start moving the opposite way. A high-end set of gears will have a small amount of backlash, but guess what? We’re not dealing with a high-end set of gears and there can be a lot of backlash in a typical low-end mount, especially if it wasn't well adjusted at the factory.

- Backlash should not be a problem for tracking in RA. When tracking, the mount should always be driving the scope from East to West and will not reverse. There may be a small amount of backlash at the start of tracking if the mount’s last GOTO was from West to East, but this is quickly taken up. PHD guiding will speed up the RA motor if it needs to move West to correct a guide error. It will stop the RA motor if it needs to correct to the East, and wait for the sky to ‘catch up’. In other words once tracking has started, the RA gears will never reverse and enter into backlash.

- The same cannot be said of the Dec axis. In this case, if PHD needs to guide North, it drives the Dec motor North, and if it needs to guide South it drives the motor the opposite way. If your set-up constantly requires PHD to keep guiding in opposite directions in Dec, the gears will spend a lot of time in backlash, which delays the guiding corrections from taking effect and may cause PHD to over or under-correct the error.

The ideal situation is that all Dec guiding corrections be made in one direction only (North or South, it matters not) so that the gears stay out of backlash. PHD will do its best to make that happen (unless you tell it not to), but there are things you can do to assist it.

The next tip is not to sweat too much over drift alignment. If you have been imaging using an unguided mount, you may well have put a lot of effort in to drift aligning the mount to maximise exposure time. Contrary to your expectations, when guiding a small amount of polar misalignment is not a major problem when guiding a short focal-length imaging scope..

If your target is drifting slightly in declination (either North or South) that will ensure that ensure that guide corrections are made in one direction only, thus keeping the Dec drive out of backlash. All things in moderation though:

- You don’t want such a misalignment as to cause visible field rotation during your exposures.

- Nor do you want so much misalignment that you cause PHD’s calibration routine to fail (see below). If you have severe drift in Dec, PHD may interpret the drift as resulting from its calibration commands and will end up under-correcting when guiding in Dec.

As stated previously, I find that a polar scope alignment works really well for my short-focal length imaging, but the longer your focal length, the more critical a good Polar Alignment becomes, and thus part of the reason why imaging at long focal lengths is hard.

If you do have perfect polar alignment (i.e. you are drifting so little it produces no visible effect on the image during one exposure), you can switch off Dec guiding altogether. Click on the ‘Brain’ icon on the PHD tool bar and set ‘Dec Guide Mode’ to ‘Off’. This might be the case if you have a permanent observatory with a pier and a rock-solid mount adjustment. For the rest of us, it is probably quicker to leave ‘Dec Guide Mode’ on ‘Auto’. and let PHD work out what to do for the best.

Balancing the Mount

The next tip, if using an equatorial mount, is to think about Balancing it, or should I say not balancing it! The mount manual will probably explain that it is important to check the balance of the mount, so that the RA and Dec axes will stay in a horizontal position when the clutches are unlocked. It is certainly true that you do not want a massive imbalance in either axis, especially if using heavy equipment, as this will put a lot of strain on the gears and motors and may lead to premature wear.

That said, obtain perfect balance is actually bad for tracking and guiding performance on low-end mounts:

- The usual advice is that the mount should be “East-side heavy”, so that it is working to lift whatever is on the east side of the mount. So if the scope is on the East side of the mount (pointing West of the meridian) then you should move the counterweights up the counterweight shaft slightly higher than the perfect balance point. Conversely, when the counterweights are on the East side of the mount (scope pointing East of the meridian), move them down the shaft below the perfect balance point.

You are aiming to have the RA worm (one of the gears) drive the main RA worm gear. By keeping the RA axis imbalanced to the East, you force the gears to stay in contact with each other (‘driven’ imbalance). This tends to smooth out any sudden movements more than the opposite (‘resistive’) imbalance. In the resistive set-up, the worm gear may slip or jolt suddenly due to uneven machining. This can also happen with driven imbalance, but most people report better results with driven imbalance than resistive imbalance.

My personal experience with my NEQ6 is that so long as I have some imbalance in RA, it doesn't particularly matter which side is heavy. In fact when I am within 30 minutes of having to do a meridian flip, I will often pre-emptively do a ‘forced flip’ between exposures (so I can get back to a frosty beverage of my choice and watching the TV on the nice warm sofa).

The scope ends up on the ‘wrong’ side of the mount (East Side pointing East) with the counterweights higher than the scope until it tracks through the meridian. I’d expect at least one bad exposure as the weights drop through horizontal and the gears switch from one face to the other, but it never happens. Again I suspect that using a short focal length imaging scope gives me a lot of room for manoeuvre!

- The same sorts of consideration apply to the Dec worm and worm gear (unless you are not guiding in Dec of course). You need to imbalance the Dec axis by moving the scope forwards/backwards (or adding weights) depending on which direction you are pointing relative to the zenith so that you achieve driven resistance.

If you have southward drift:

- If the scope is pointing South of the zenith, imbalance the scope so that the North (lower) end is heavy.

- If pointing North of the Zenith, again imbalance so that the North (higher) end is heavy.

If your polar alignment is causing a gradual northward drift instead, then you reverse the imbalance:

- Pointing South of zenith, South/higher end heavy.

- Pointing North of zenith, South/lower end heavy.

PHD Basic Settings

We looked at a few of the basic PHD settings during testing above, so hopefully you already know how to get your camera and mount connected to PHD ready to start guiding. Next we will look at a few of the more important settings.

Exposure Length

In the middle of the PHD tool bar is the ‘Exposure’ drop-down, which allows you to choose the length of the guiding exposures in seconds. Setting the exposure length is a trade-off between several factors:

- You need a long enough exposure to produce a measurable guide star. If your exposure length is too short (and/or your camera gain too low), you will either get no stars or stars that are too faint to use reliably. If you find you are able to lock on to a star and calibrate, but then get frequent ‘Star Lost’ errors flashing up, it may be that your chosen star is too faint. Increase the exposure length (and/or gain).

(Bear in mind that cloud can cause the same problem as it drifts across and dims the guide star from time to time, so check the skies, especially for high, thin cloud which can be hard to spot. Also check your guide-scope for dewing which has much the same effect.)

- You need a short enough exposure not to saturate the guide star. If your exposure length is too long (and/or your camera gain is too high) you may get a ‘Star Saturated’ error from PHD. This means that one or more of the star’s pixels has reached maximum brightness and PHD cannot calculate the star’s centroid accurately. Reduce the exposure time and/or reduce the gain.

- You need an exposure length that is short enough that PHD can detect and correct guiding errors before they become visible on your main image. In an ideal world we’d take guide exposures as frequently as possible, but in practice there is a minimum length of exposure dictated by the need to pick up a guide star (see above). Furthermore it can be advantageous to have a longer exposure to reduce the effect of seeing. Really short exposures can end up with PHD “chasing the seeing” and poor guiding, whereas a slightly longer exposure averages out the seeing and gives a better estimate of the guide star’s centroid.

- When you have selected a guide star, the star’s ‘Signal to Noise Ratio’ is displayed at the bottom left of the PHD window on the status bar. There is no hard and fast rule as to what this number should be. Generally speaking a higher number is always better, provided you are not getting ‘Star Saturated’ errors from PHD. Use the SN number to tweak your exposure length, camera gain and focus until you get a reliable lock with no ‘Star Lost’ or ‘Star Saturated’ errors.

If you are really struggling to get an acceptable SN number with your camera, you can go in to the ‘Brain’ icon on the tool bar and change the ‘Noise Reduction’ setting from ‘none’ to ‘2x2’ or ‘3x3’. This increases SN by ‘binning’ pixels in software at the cost of reduced guiding accuracy. If trying the 2x2 setting, multiply the camera pixel size by 2 (or by 3 if using 3x3 setting) and calculate the guider pixel scale using the equation we discussed above. If you are still within the 4x pixel scale rule of thumb, you will probably be OK.

- The best advice I can give you for exposure length is to start with a two or three second exposure and work from there by reference to the guiding graph, which we’ll look at below. Over a few sessions you’ll get the hang of the right exposure length for your equipment.

- Bear in mind my earlier comments that if you are pushing the envelope and imaging at a long focal length, you may need a more sensitive guide camera, a longer focal length and/or faster f-ratio guide scope (hard to do both), to use PEC in addition to guiding or simply a higher quality mount.

The next tip is that it might help defocus the guide scope slightly. If you are having problems with saturated stars, or you are exceeding the 4x pixel scale rule, this may help. Defocusing will spread the light of the star over more camera pixels which can prevent saturation, and also makes it easier for PHD to detect the centroid of the guide star more accurately. Don't go mad with defocusing or PHD won't be able to lock onto the star and you may start getting ‘Star Lost’ errors if your SN figure drops too much due to de-focusing.

In all cases your guide star still needs to have a brighter central peak and not turn into a hollow doughnut, but a bit of defocus on the guide scope may help where you have SN to spare. You can use the ‘Star Profile’ option on the ‘Tools’ menu to check the profile of your guide star once selected. It should have a peak in the middle like a mountain. If it is flat on top you have a saturated star, and if there is a dip you need to focus more.

Brightness Slider

Next to the exposure drop-down is a brightness slider. It is essential to realise that this slider only increases or decreases the brightness of the guide image display . It has absolutely no effect on the camera settings or the actual brightness of the guide image . You can use the slider to make it easier to see stars on screen, but if the stars are too faint (or bright) for guiding you have to adjust the camera gain or exposure length, as this slider has no effect on guiding performance,

Towards the right hand side of the tool bar is the ‘Take Dark’ button. You should definitely use this. Click the button when ready to start guiding. PHD will instruct you to cover the guide scope and then take a series of dark frames. Finally it will remind you to uncover the guide scope again (been there, bought the t-shirt!)

Failing to take a dark can cause two problems:

- Firstly you may end up selecting a hot pixel as your guide star. Normally PHD will spot this and complain, but you may waste a lot of time trying to calibrate on it if it doesn't (or even guide on it if retaining an existing calibration). The guiding graph looks great since the hot pixel stays dead centre of the lock box, but the final images do not!

- Secondly as you guide, a hot pixel may be close to the guide star, and PHD may intermittently include the hot pixel as part of the star image causing the centroid position to jump around erroneously.

Bear in mind that whenever you change exposure length or camera settings, you should re-take your dark using this button.

Getting ready to Guide

So now you are ready to go. You have found your target for the night, you have framed it nicely and focused your imaging camera and set the basic PHD guiding parameters above. The next steps are as follows:

- Click the ‘Loop’ button to start taking guide exposures. Hopefully you will see a choice of guide stars in the PHD screen. If you don’t go back a few steps and adjust the exposure/camera gain and try again (re-taking your dark if needed).

- Click on the brightest star but avoid using a star that is close to the edge of the image, as it may drift out of view over the course of the imaging session (especially if you are dithering your images). Check that PHD is not complaining about the star being saturated, and ensure that PHD has found the star (it should draw a green box around it if it is happy).

- Avoid picking a star that is close to another star, and also avoid using any known double stars. In both cases you may end up with erroneous/fluctuating centroid calculations and spurious guide commands.

Calibration

- Next click on the ‘PHD’ button and PHD will start the calibration process. It will attempt to move the star some distance East and West in RA, and then North and South in Dec in order to figure out which guide commands move in which orientations and also how long guide pulses need to be..

A pair of lines will be drawn in a cross indicating the initial position of the guide star, and you will see the status bar indicating which guiding commands are being sent. All being well you will see the star and the green box gradually drift along one of the lines, stop and drift back again, and then do the same along the other line.

This process can take several minutes to complete successfully so be patient. A good calibration will usually require somewhere between seven and forty steps in each direction. If the calibration completes in less than seven steps in any direction, you are unlikely to get good guiding performance and you should change the calibration step size (see below). If the calibration takes more than forty steps in any given direction it will still work, but again you may want to change the calibration step size to save time. My experience is that a good calibration takes about 15-20 steps and between five and ten minutes to complete.

If the calibration fails with PHD complaining that the star didn't move enough, then you have one of two problems. Either the calibration step size is too small (see below), or your guide commands on one or both axes are not being acted upon. We talked about using the ‘Manual Guiding’ option on the ‘Tools’ menu to verify that PHD can control the mount, so if you haven’t done so already, put a high-powered eyepiece in your imaging scope, centre a star and then use those controls to make sure the scope moves in all four directions when commanded.

The final thing to be aware of is that you should recalibrate PHD whenever you slew to a new imaging target (unless it is within a few degrees of your original target). You do this by clicking the ‘Brain’ button on the tool bar and ticking the ‘force calibration’ button. You will not be able to successfully guide if you try to keep the same calibration in different parts of the sky.

Similarly if you perform a meridian flip on an equatorial mount, you should probably re-calibrate. There is an option on the ‘Brain’ dialog to reverse the existing calibration after a flip, but my experience is that it is better to spend five or ten minutes recalibrating rather than spending ten minutes exposing only to discover you have to recalibrate anyway!

Calibration Step Size and Guiding Rate

If you are have a good guide star (good SN figure, not saturated), and PHD is definitely able to command the mount but calibration fails, then it is a fair bet that the Calibration Step Size number needs to be adjusted. Click on the ‘Brain’ icon on the tool bar to bring up the advanced PHD settings.

The “Calibration Step Size’ determine the length of the calibration guide pulses. The default setting is 500ms (half a second). This may or may not be the right amount:

- The bigger the pixel scale of your guiding rig, the longer the step size should be. I use 2,000 to 2,500ms for my 400mm/5.6µm guide scope at 2.67 arc-second per pixel. If your pixel scale is a bigger number, increase the step size, if smaller decrease it.

- The closer you are to the celestial pole, the longer the step size should be. Typically I use 2,000ms near the celestial equator and increase that to 2,500ms as I approach the pole. The appropriate range will vary according to the pixel scale of your guiding rig.

- Your mount, or mount driver may allow you to set a custom guiding rate. The best starting point is to set your guiding rate to 1x, which means that when guiding East the mount will stop completely, and when guiding West it will move at 2x sidereal rate. Many mounts offer 0.5x guiding rates (and others), which are helpful when hand guiding, but probably not that much use when using PHD. keep it simple and use the 1x guide rate.

The next tip is that you should experiment with the calibration step size and keep notes of what works for each declination. Provided you are calibrating in more than seven steps you should be OK, but if you are exceeding 40 steps you can almost certainly save time by increasing step size. I aim for 10-20 steps at most.

Guiding (at Long Last!)

Once PHD completes calibration, it will immediately start guiding. The pair of lines will turn green and guide commands will be sent. Time to start imaging at last.

I know it has taken a long time to read to this point, but in reality and with a bit of practice, the time from finishing centring and focussing my imaging target in the main scope to having PHD guiding merrily away takes me seven minutes on average, and for about 6 minutes and 30 seconds of that time, PHD is calibrating without any input from me!

As far as guiding goes, the next thing you need to do is monitor the PHD status bar for a minute or two to make sure you are not getting ‘Star Lost’ or ‘Star Saturated’ errors. The occasional ‘Star Lost’ error is nothing to fret about usually, but if they are flashing up repeatedly you should do some troubleshooting (check exposure and gain as described above, look out for high cloud and dewing on the guide-scope).

Interpreting the PHD Graph

The most useful tool for checking your guiding performance in the field is the guiding graph. Go to the ‘Tools’ menu and select ‘Enable Graph’.

What you will see is a graph showing your guiding performance in RA (the blue line) and in Dec (the Red line). The name of the game is to try to keep the two lines as close as possible to the centre line running from left to right across the chart.

The horizontal scale button (‘100’ above) allows you to zoom in and out by reference to guiding cycles. By default 100 guiding cycles are shown across the chart, this isn't a fixed time scale as such and the longer your individual guide exposures, the longer those 100 cycles will take. You can click the scale button to zoom out and see more cycles, but to be honest the default 100 cycles is most useful for diagnosing guider problems.

The vertical scale button (RA/Dec) allows you to switch between RA/Dec corrections and x/y pixel corrections. Again the first mode is most useful since you want to see what is going on with your RA guiding and Dec guiding separately, whereas the x/y mode isn't (necessarily) much help in that regard.

Again the vertical scale is not too helpful at first sight. Each dotted line corresponds to one pixel of error on the guide camera. Since you have calculated the pixel scale of your guide camera already, you can multiply it by the number of divisions to find your maximum guide error. In the graph above I was using my ST80 and QHY5, and the blue RA line averages out at about 0.2 pixels above/below the line, making for an error of:

2.67 arcseconds per pixel x 0.2 divisions = 0.53 arcseconds.

This is what we call the “Root Mean Square” or RMS error, which basically means we square the all the errors (positive stay positive, negative x negative becomes positive), add them together, average the total and take the square root. If we didn't calculate the RMS then the negative errors (below the line) would cancel out the positive errors (above the line) and our average error would be close to zero, which clearly it is not!

Helpfully PHD calculates the RMS error for whatever you can see on the current graph scale and puts it on the bottom left of the graph below the buttons. It only does this for the RA error however (the blue line) as it is assume you will not be making major Dec corrections at all (not always true though!)

The other figure just below RMS is the ‘OSC Index’, i.e. the oscillation index. Again this is only calculated for the RA axis. The OSC index is the probability that guiding will change direction at the next step (i.e. the blue line will cross the centre of the graph)

A mount with no Periodic Error would have a figure of 0.5, i.e. equally likely to have to correct in either direction, but a figure between 0.25 and 0.4 for a real mount is generally considered okay but there isn't a hard and fast rule about the OSC index:

- If you have a small RMS figure and a large OSC index you should be okay. The mount is constantly flipping between guide directions but only by a small amount.

- If you have a large RMS figure and a large OSC index, that would tend to suggest the poor guiding is due to lack of stability in the set-up, and that could be down to mechanical/balance problems, wrong exposure/gain on the camera creating a noisy guide star, incorrect guiding parameters or just really bad seeing conditions.

Unhelpfully in my example, the OSC index is greater than 0.5, which suggests the mount is correcting more in RA in one direction than the other over time. I'm man enough to admit I don’t know what that means! What I do know is that I got really good imaging results from that session so clearly it wasn't a problem to worry about.

Common Issues from the Graph

- First of all, please bear in mind that you can have a pretty ugly looking guiding graph that produces little or no visible effect on the actual image. The opposite is also true of course! You need to convert the pixel lines on the vertical scale and/or the RMS error to arcseconds of error by performing the guider pixel scale multiplication described above. Now compare that to the pixel scale of your imaging rig. You may find that what looks like a major guiding issue is actually less than a pixel or two of error on your final image.

For example, looking at the RA error in the graph above:

0.2 RMS pixels error x 2.67 arcseconds per pixel = 0.53 arcseconds of error on the guider image

0.53 arcseconds of error / 1.9 arcseconds per pixel imager scale = 0.28 pixel RMS error on final image

Looking at my graph, I can see that the RA error is roughly evenly distributed above and below the line so I should double the RMS error, meaning my stars are perhaps half a pixel wider than they should be in RA. The Dec error looks pretty much the same. Sounds pretty good to me, and indeed it looks good on the final result.

(If the guide error was predominantly above the line, or predominantly below the line, we could use the smaller 0.28 pixel RMS value instead).

- If one or other of the RA/Dec lines is shooting off the graph it may mean that corrections in that axis are not being sent to the mount or are not being responded to. Again perform the manual guiding checks to ensure everything is working as you would expect. Also check that you haven’t turned off Dec guiding under the ‘Brain’ button. If everything checks out, ensure your clutches are tight on the mount and look for other signs of flexure or equipment flapping about.

(if you are using dithering, it is normal to have the RA and/or Dec lines shoot away from the centre line whilst dithering is in progress, and then drop back to the centre line as dithering finishes and guiding settles. It does tend to make me jump off the sofa when I see it happening on my remote monitoring screen though!)

Tweaking Guiding Parameters

The next tip is that your results may well vary according to the Alt and Az of the target. I consistently get better results on higher targets nearer to the meridian. Targets lower in the east produce rougher guide graphs. Whether that is due to poor seeing due to more atmosphere in the way of the guide star, something mechanical or perhaps needing to tweak the guiding parameters I know not.

If your guiding graph is zig-zagging all over the place and you are getting many arcseconds of error, and assuming you have checked all the basics above, then you may need to tweak some of the guiding parameters. Helpfully the main parameters that you may need to change can be adjusted using the controls directly below the guiding graph:

- RA Aggressiveness: How much of the calculated RA correction to apply. Start with the default figure of 100%, as hopefully PHD knows what it is doing. If you find that guiding in RA (blue line) is constantly overshooting the mark and then rapidly zig-zagging back the other way, try reducing this to a lower figure, perhaps 70-80%. If you think your mount has sloppy gears, maybe try going to 110 or 120% to see if you can compensate.

- RA Hysteresis: How much of the previous RA guiding trend to take into account. Good guiding is smooth and doesn't respond to rapid changes in guide direction (usually caused by seeing or poor SN from the guide star). If you think that guiding is too jerky with sudden rapid corrections, increase this number, or decrease it to make guiding more responsive. Aggressiveness and Hysteresis go hand in hand and you should normally reduce or increase them together in small increments until you get best results.

- Min Motion: The smallest guide error that should result in a correction being made. This is in pixels and applies to both the RA and Dec axes. So if I set min motion to 0.1 pixels, then PHD would not try to correct any errors until they were more than that value, and for my guider scale of 2.67 arcseconds per pixel, that means PHD would not try to correct any errors less than about a quarter of an arcsecond in size. Again this is useful for smoothing out jerky guiding if your mount is poor or you don’t have a good guider set-up.

- Max RA Duration: This sets the maximum single guiding correction that PHD will send in a single cycle (in this case 1,000ms = 1 second guide pulse). Generally you shouldn’t make this value too large (maybe less than half a second), since PHD will issue another correction if it needs to, but if the first correction is too large and overshoots you’re already in trouble. (In this case, the rest of the guiding is working well and PHD never gets anywhere near the perhaps excessive 1 second maximum I have set, but your mileage will vary!)

- Max Dec Duration: This is the same as above. The default setting is smaller than the default for RA out of the box, and I've never needed to change it.

To be honest I think that is the final tip: If it ain’t broke, don’t fix it! It can be very tempting to dive in and start fiddling with the advanced parameters in PHD in the hope of finding a magic formula for pixel perfect guiding. In reality 90% of the guiding problems are external to PHD guiding. Only when you have investigated and fully understood all those externalities will you be able to make an informed decision as to what to tweak in PHD itself.

There are many other resources on-line covering advanced PHD fettling, and plenty of people on the forum willing to offer you customised advice and assistance, so please don’t hesitate to ask for help. You’ll probably find their advice more useful if you have done a bit of homework first.

Link to comment

Share on other sites.

• Replies 104
• Created 10 yr
• Last Reply 1 yr

Top Posters In This Topic

Popular Days

IanL 13 posts

alcol620 7 posts

Russe 6 posts

GaryCH 6 posts

Mar 25 2015

Mar 21 2015

Sep 24 2013

Popular Posts

June 20, 2013

Pleas for help with PHD guiding seem to come up more often than almost other imaging topic. I make no claims to be the ultimate expert on the subject, but I have travelled some way along the road fro

Thank you Ian for such a comprehensive post about PHD :-) This post will be stickied for immortality!

An excellent guide, should be made a sticky! I have a little extra for the pot in regard to PHD and finderguiders, the following link contains posts from Craig Stark (the author of PHD) as to the sett

Posted Images

Thank you Ian for such a comprehensive post about PHD :-)

This post will be stickied for immortality!

An excellent guide, should be made a sticky!

I have a little extra for the pot in regard to PHD and finderguiders, the following link contains posts from Craig Stark (the author of PHD) as to the settings that should be used for 50mm finderguiders:

http://www.cloudynig...psed/sb/5/o/all

Also, how to work out whether you're getting backlash. It manifests itself in the form of an slow drift in dec, followed by an overcorrection. If left for long enough you will notice a sawtooth pattern forming in the graph history.

Great write up Ian, many thanks for that!

Unhelpfully in my example, the OSC index is greater than 0.5, which suggests the mount is correcting more in RA in one direction than the other over time. I'm man enough to admit I don’t know what that means!

Could that not be simply refraction towards the lower east or west?

Roberto Coleschi

Great guide, and Imaging Toolbox is a wonderful aid, thanks..

Fantastic, I'm just about to start with PHD.

• 2 weeks later...

Thanks! Great guide!!!

• 2 months later...

Just spotted a small error:

That should actually read " (5.2µm / 400mm) x 206.3 = 2.67 arcseconds per pixel "

Thanks for a great tutorial. I read through it yesterday and although I have been guiding for over a year I but picked up some great tips from this.Last night I got by far the best guiding I have ever achieved,so thanks a lot Ian for taking the time to post this

What is a good SNR in PHD?

Hi! I calculated my pixel scale for my guiding rig and I get 4.28" ( Starlight Xpress Lodestar with ST-80). How big should my Calibration Step Size be? 4000?

Hard to say.  Even Craig Stark doesn't really say.  The bottom line is that bigger SNR numbers are better than smaller numbers. So when you are selecting a guide star, setting exposure/gain and focussing the guide scope just pick the combination that gives you the biggest SNR you can find that night.  If you get 'Star Saturated' errors then your chosen star is too bright, the gain/exposure is too high/long or maybe de-focus a tiny amount.  If you get 'Star Lost' errors a lot, then you need to do the opposite and try to get a brighter star, increase gain/exposure or focus better.  Make sure you don't have dew on the guidescope objective and check for high clouds.

Yes I'd say that somewhere between 3,000 and 4,000 is a good starting point for that pixel scale.  Remember 15-20 steps in each direction should give a good calibration.

Ok - my SNR is about 25-30 on 0.5s exposures with a QHY5 on a 9x50 finder scope.

Hard to say.  Even Craig Stark doesn't really say.  The bottom line is that bigger SNR numbers are better than smaller numbers. So when you are selecting a guide star, setting exposure/gain and focussing the guide scope just pick the combination that gives you the biggest SNR you can find that night.  If you get 'Star Saturated' errors then your chosen star is too bright, the gain/exposure is too high/long or maybe de-focus a tiny amount.  If you get 'Star Lost' errors a lot, then you need to do the opposite and try to get a brighter star, increase gain/exposure or focus better.  Make sure you don't have dew on the guidescope objective and check for high clouds. Yes I'd say that somewhere between 3,000 and 4,000 is a good starting point for that pixel scale.  Remember 15-20 steps in each direction should give a good calibration.

I've set the Calib. Rate to 3500, but PHD only takes 3-4 steps in each direction. Nevertheless i managed to image for nearly 10 mins without star trails (Perseus Region). Next I slewed to Cepheus and had small trails. I presume that if i lower the rate more steps will be taken, right?

Right.  Fewer than 7-8 steps is likely to result in a poor calibration.  As you've found, it might work sometimes.  I'd decrease the step size a bit (maybe try 3,000 and see) before you change anything else.

I've been thinking about getting into guiding lately and this guide has been the perfect intro. Thank you Ian.

Have played with PHD yesterday night. Finally foxed out some settings. I've successfully used ASCOM pulse guide settings and am now calibrating how ever long I want to. Nice to be in control.

I'm now aiming at 15 to 20 steps. My RMS was between 0.12 to 0.32 - nice and smooth graph.

The ST4 settings though fail on me. I've tried all 0.25 to 1.0 settings but none achieve enough movement, so the calibration fails. Confusing, but doesn't really matter. This actually means that I can get rid of my ST4 cable, isn't it?

By the by, I now usually calibrate at 0.5s, which usually gives me nice SNR's around 30 or more. This speeds up the process quite nicely as well.

I changed the rate to 3000 but the steps didn't go over 5. But I tested on more than 10 different regions of the sky for 10 mins each and the stars were perfectly sharp. I even imaged M52 with the Bubble Nebula. Any suggestions or should I leave at as it is?

As I said in the guide "If it ain't broke, don't fix it!"  If you are getting reliable guiding at 5 steps then leave things as they are.  Calibration is a means to an end, not the objective.

If you do run in to trouble later, then try reducing the step size more until you get the recommended 10-15 steps, but don't fiddle with it for no particular reason; plenty of other problems to solve further down the line so get on with imaging.

You'll get more steps if you change the EQMOD pulse guide settings from 0.9 to 0.1 and go down from 50ms to 20ms.

Unless you're guiding per ST4, then you'd reduce the rate from 1x to 0.25x

Thank you very much for this excellent and detailed instruction guidelines.

I plan to implement some (or all) of the above during my next observing session, as my gear for guiding is ready for setup.

The only Q I have is regarding the SW installation procedure, as I got confused by the various components mentioned...

i.e. PHD app., ASCOM app., EQMOD drivers, manufacturer drivers etc.

Can you comment and advice on what is necessary to install (Win 7) and in what order?...

I use NEQ6 and plan to attach the Orion's StarShoot cam connected to a separate small scope fixed to the side of the OTA.

Hi Lan, Thank you very much for this excellent and detailed instruction guidelines. I plan to implement some (or all) of the above during my next observing session, as my gear for guiding is ready for setup. The only Q I have is regarding the SW installation procedure, as I got confused by the various components mentioned... i.e. PHD app., ASCOM app., EQMOD drivers, manufacturer drivers etc. Can you comment and advice on what is necessary to install (Win 7) and in what order?... I use NEQ6 and plan to attach the Orion's StarShoot cam connected to a separate small scope fixed to the side of the OTA. Thanks, Romi

I am assuming you are using the standard Orion Starshoot Autoguider ( http://www.telescope.com/Orion-StarShoot-AutoGuider/p/52064.uts )?

Are you using the handset to control the mount, or are you using EQMOD?  (EQMOD runs on a laptop and replaces the handset for all mount control operations.  You would typically have an EQMOD adaptor plugged in between the laptop and the mount's handset port if so).

I haven't used a Starshoot, but roughly speaking if you are using the handset you would set things up as follows:

- Install PHD guiding.

- Install the camera drivers from the supplied CD.

- Connect the Starshoot's USB port to the laptop and complete the set-up procedure.

- Connect the camera's ST4 port to the mount's ST4/auotguider port using the supplied ST4 cable (looks a bit like a telephone cable).

- You'd then press the camera button to connect to the camera in PHD and select the Starshoot Autoguider from the camera driver list.

- You would then select 'On Camera' from PHD's 'Mount' menu and then press the mount button to connect.

Guiding commands will be sent from PHD via the camera through the ST4 cable directly to the mount.

On the other hand if you are using EQMOD, then it is a bit more complicated:

- You'd need to download the ASCOM V6 platform ( http://ascom-standards.org/ ) and install it.

- Then you'd need to download EQMOD ( http://eq-mod.sourceforge.net/ ) and install it (specifically the EQASCOM software, everything else is optional).

- Installing and setting up EQMOD is a bit beyond what I can cover in this post - there are manuals on the site and plenty of guidance.

- You would then need an EQDIRECT adaptor to replace the handset (or use the handset in PC Direct Mode, but this is unsupported).  Details here  http://eq-mod.sourceforge.net/reqindex.html .

- Most likely you'd also want a planetarium (either Cartes du Ciel  http://www.ap-i.net/skychart/start , or Stellarium  http://www.stellarium.org/  AND Stellariumscope http://www.welshdragoncomputing.ca/ ), plus you'd probably also need a gamepad to control the mount via EQMOD (this is optional as you can use the buttons on screen, but it does make life a lot easier).

- Once you have set up EQMOD and learned how to use it, which is probably several days of effort in its own right, then you can get on with guiding.

- You'd install the Starshoot drivers, connect the camera USB and connect to the PC as above.

- What is different this time is that you would select 'ASCOM' from PHD's 'Mount' menu, press the mount button and select your NEQ6 as the mount.

In this scenario the guiding commands are sent via software from PHD through ASCOM to EQMOD, which processes them and sends the instructions via the EQDIRECT connection to the mount.

As you can see, the ST4 option is the simplest way to get started, as there is far less software to install, test and learn.  If you already know how to use the mount handset then I would go down the ST4 route to get started since you'd have far less to learn and worry about at this stage.

EQMOD is a really good way of controlling the mount as it opens up lots of other options (such as using a planetarium to find and slew to targets, or using Astrotortilla to do plate solving and find them automatically, etc.).  EQMOD has now got a new AutoPEC feature which makes it simpler to set up PEC without needing to use external software to record and analyse the mount's period error.  In the long run EQMOD is definitely worth the effort to learn, but there are definitely more things to go wrong up front.

Great explanations Lan !!

I do use the handset and not the EQMOD at this stage (and bought the standard Orion Starshoot Autoguider as you mentioned above).

So, (only to make sure I understand the whole thing):

1. If I use the handset on the mount (e.g. SynScan), which is the way I currently work, I should connect the ST4 cable from the cam to the mount (should I still connect

   the USB cable?) and set the PHD to "on Camera",

2. If (in the future) I would start controlling the mount with EQMOD (following your instructions in this regard), then I should connect the USB (do not connect the ST4)

    and select 'ASCOM' from PHD's 'Mount' menu etc.

You have truly simplified the technical process for me here.

Thanks a lot.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Already have an account? Sign in here.

Recently Browsing    0 members

• No registered users viewing this page.

Similar Content

Phd guiding help.

By gustavo_sanchez , April 8, 2013

• travelscope 70

Tagged with:

• gso 0.5x reducer
• 2,817 views

• April 9, 2013
• Existing user? Sign In
• Code of Conduct
• Online Users
• All Activity
• Unread Content
• Unread Topics
• Content I Started
• Content I Posted In
• My Activity Streams
• Astronomy Tools
• Clear Outside
• Useful Links
• Astro Society Finder
• Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings , otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use .

TheSkySearchers

Come join the friendliest, most engaging and inclusive astronomy forum geared for beginners and advanced telescope users, astrophotography devotees, plus check out our "Astro" goods vendors.

Skip to content

• Home Portal Board index General Astronomy Astrophotography Guiding

PHD2 Guiding Tips

TSS Awards Badges

TSS Photo of the Day

Post by JayTee » Fri Aug 09, 2019 12:12 am

• 1. Increase the guide speed in the mount to 0.9x sidereal. This can help to mitigate the Dec backlash problem in the mount and will let you use shorter exposure times.
• 2. Try binning the guide camera at 2x2. To do this, create a new profile with 2x2 binning and the new guide speed you set in step 1.
• 3. Disable star-mass detection for now – that’s on the Guiding tab of the Advanced Dialog
• 4. When it’s time to do a calibration, *always* move the mount north as the last step before starting the calibration. You can do that with a slew or by using the hand-controller. Just be sure you can see the stars moving on the display.
• 5. Try to use guide cam exposures of 1-2 seconds with this setup. Longer exposures give the mount too much time to wander off track, which can affect both guiding and calibration.
• 6. Re-run the Guiding Assistant with the new set-up and accept its recommendations. Re-run the backlash test and look at the graph to see how the mount behaved.- you can do this even if something went wrong with the test. For that matter, you can use the ‘Review Previous’ button in the GA to see what happened in earlier tests.
• 7. Don’t monkey around with the guide parameter settings, that’s just making things worse. You need to develop a clear view of what your mount is capable of doing before trying to figure out how best to work around its problems. The Guiding Assistant runs will do that for you – you should expect a lot of uncorrected periodic error in RA and a lot of Dec backlash. If the Dec backlash is too large for PHD2 to handle with Dec backlash compensation, you can guide in only one Dec direction. There are instructions in the Help guide for that and it can work very well for you – lots of people do it.

Re: PHD2 Guiding Tips

Post by Juno16 » Fri Aug 09, 2019 12:51 am

Post by yobbo89 » Sat Aug 24, 2019 2:07 pm

Post by XCalRocketMan » Sun Aug 25, 2019 12:13 am

yobbo89 wrote: ↑ Sat Aug 24, 2019 2:07 pm I have one tip that may or may not help people guiding with an asi zwo camera, give ascom driver a go instead of the native zwo driver , and use 8 bit instead of 16 bit. this will help avoid those driver crashes or long hangs

Post by UlteriorModem » Sun Aug 25, 2019 2:18 am

Post by yobbo89 » Sun Aug 25, 2019 7:04 am

UlteriorModem wrote: ↑ Sun Aug 25, 2019 2:18 am Good pointers! Only thing I have to add is to make sure the mount is pretty well polar aligned before you start any of this. Otherwise you will end up chasing your tail

Post by fatboy1271 » Tue Aug 27, 2019 3:20 am

XCalRocketMan wrote: ↑ Sun Aug 25, 2019 12:13 am yobbo89 wrote: ↑ Sat Aug 24, 2019 2:07 pm I have one tip that may or may not help people guiding with an asi zwo camera, give ascom driver a go instead of the native zwo driver , and use 8 bit instead of 16 bit. this will help avoid those driver crashes or long hangs

Post by seigell » Mon Sep 16, 2019 11:59 am

Post by seigell » Mon Sep 16, 2019 12:07 pm

• When in doubt, Create a NEW "Equipment Profile" and fill it out accurately. Then run the Guiding Assistant, and follow its suggested settings.

Post by Brian » Mon Sep 30, 2019 3:19 pm

Post by Mike_Lewis » Sun Nov 17, 2019 4:16 pm

Post by JayTee » Sun Nov 17, 2019 9:37 pm

Post by JayTee » Thu Dec 19, 2019 1:43 am

Post by Larry 1969 » Thu Mar 05, 2020 7:51 pm

Post by JayTee » Thu Mar 05, 2020 10:23 pm

Post by turonrambar » Sat Apr 17, 2021 9:12 pm

Post by chartram » Tue Nov 15, 2022 11:28 pm

Mike_Lewis wrote: ↑ Sun Nov 17, 2019 4:16 pm I attended a lecture on PHD2 Best Practices this weekend. The speakers were none other than Andy Galasso and Bruce Waddington, so I take the information imparted as gospel. Most of what they explained was information I have been long been aware of, but one thing surprised me; PHD2 works best with imperfect polar alignment. They suggest that PA should be off by 5 to 10 arc minutes. The reasoning is that such misalignment keeps the guiding pulses coming and the error becomes "predictable" to the software and keeps the drive gears engaged resulting in more stable guiding. I immediately thought about all of the hours I've spent in my life (before I bought PoleMaster) working at getting my PA error under 1 arc minute, my old standard. Completely unnecessary. I do wonder if that error is appropriate if guiding a scope at f/10 or so, but didn't find a chance to ask.

Return to “Guiding”

• ↳   Donations
• General forums
• ↳   Welcome Introductions
• ↳   Beginners forum
• ↳   Misc
• ↳   Off-Topic
• ↳   Forum tips & tricks
• ↳   Feedback
• ↳   Vendors
• ↳   Articles and Reviews
• ↳   TSS Classifieds
• ↳   Star Parties
• ↳   PLEASE READ FIRST
• ↳   Star Parties in the US
• ↳   Virtual Star Parties
• ↳   Star Parties in the UK & Ireland
• ↳   Star Parties in Canada
• ↳   Star Parties in Australia
• General Astronomy
• ↳   General Astronomy Subforums
• ↳   Astronomy Reports
• ↳   Astronomy Software
• ↳   Astronomy Sketching
• ↳   Astronomy News
• ↳   Astronomy Books
• ↳   Astronomy Websites
• ↳   Eclipses
• ↳   General Observing
• ↳   Astrophotography
• ↳   Beginner Astrophotography
• ↳   Astrophotography Photos
• ↳   Deep Sky Images
• ↳   Lunar images
• ↳   Nightscape Images
• ↳   Solar images
• ↳   Solar System images
• ↳   Remote Imaging - Images and Discussions
• ↳   EAA Images
• ↳   Image processing
• ↳   (EAA) discussion
• ↳   AP equipment / AP Software & Apps
• ↳   Guiding
• ↳   Discussion area
• ↳   Astrophysics
• ↳   Lunar
• ↳   Solar
• ↳   Solar System
• ↳   Deep sky
• ↳   Space Exploration
• ↳   Astronomical Events
• Telescopes and Mounts
• ↳   Telescopes
• ↳   Telescope Types
• ↳   Reflector Telescopes
• ↳   Refractor type Telescopes
• ↳   Catadioptric telescopes
• ↳   Telescope Brands
• ↳   Celestron telescopes
• ↳   Explore Scientific telescopes
• ↳   Meade telescopes
• ↳   iOptron telescopes
• ↳   Orion telescopes
• ↳   Skywatcher telescopes
• ↳   Classic/Vintage scopes
• ↳   Other telescopes
• ↳   Mounts
• ↳   Celestron mounts
• ↳   Explore Scientific mounts
• ↳   iOptron mounts
• ↳   Meade mounts
• ↳   Orion mounts
• ↳   Skywatcher mounts
• ↳   Other brands of mounts
• ↳   Eyepieces
• ↳   Binoculars
• ↳   General Optics
• Other Equipment
• ↳   Other Accessories
• ↳   The DIY corner
• ↳   Home observatories
• ↳   ATM
• ↳   Other "Do It Yourself" projects
• TSS Photo of the Day & Viewing Report of the Day
• ↳   APOD Daily winners!
• ↳   Your picks for APOD!
• ↳   VROD Daily winners!
• ↳   Your picks for VROD!
• TSS Contests & Challenges
• ↳   Announcements
• ↳   TSS Monthly DSO Challenge
• ↳   Challenge Guidelines
• ↳   Submissions
• ↳   Challenges Q&A and target suggestions.
• ↳   Messier Contests
• ↳   Messier Awards Program Rules
• ↳   Messier Visual Reports
• ↳   Messier Sketches
• ↳   Messier AP Images
• ↳   Messier EAA Images
• ↳   AP Processing Challenge
• ↳   Carbon Star Hunt Challenge
• ↳   TSS Quizzes
• Home Portal Board index
• All times are UTC

Powered by phpBB ® Forum Software © phpBB Limited

Prosilver Dark Edition by Premium phpBB Styles

Privacy | Terms

• Latest topics
• Advanced search
• Constellations
• Top pick nominations
• Image of the day
• Remote astrophotography
• Astrophotographers list
• Contributors list (beta)
• English (US)
• English (GB)

Image Index:

The Image Index is a system based on likes received on images, that incentivizes the most active and liked members of the community. Learn more.

Contribution Index (beta) :

The Contribution Index (beta) is system to reward informative, constructive, and valuable commentary on AstroBin. Learn more.

• Equipment forums /
• Open PHD Guiding project PHD2 /
• Seeking Beta Testers for Advanced PHD2 Planetary Guiding Module – Enhance Your Solar, Lunar, and Planetary Imaging

Seeking Beta Testers for Advanced PHD2 Planetary Guiding Module – Enhance Your Solar, Lunar, and Planetary Imaging Open PHD Guiding project PHD2 · Leo Shatz · ... · 14 · 1096 · 2

Notifications, astrobin is in read only mode.

This page or operation is not available at the moment, because AstroBin is in READ ONLY mode. For more information, please check out our Twitter feed: https://twitter.com/AstroBin_com

This feature is only offered at higher membership levels.

Would you be interested in upgrading? AstroBin is a very small business and your support would mean a lot!

This feature is only offered at the AstroBin Ultimate membership level.

Only group members can post in a group's forum.

Please join or request to join the group, and then you'll be able to post a new topic.

Are you really sure?

If this user has been harassing you, and you shadow-ban them, all their activities on your content will be invisible to everyone except themselves.

They will not know that they have been shadow-banned, and the goal is that eventually they will get bored while having caused no harm, since nobody saw what they posted.

This operation will reload the current page. If you have any unsaved information in a form, it will be lost.

You can also dismiss this window, and your operation will be applied at the next page navigation.

This operation cannot be undone!

Are you sure?

Report abuse.

When you report abuse on some content on AstroBin, the content will be hidden until a moderator reviews it. Abuse reports are anonymous and the content's owner will not be notified.

Please specify a reason for this abuse report.

Slideshow settings

Iotd/tp stats (last [x] days).

Please note: The following tables are updated every 24 hours.

Distribution of astrophotographers

Distribution of subject types, distribution of data sources.

Breaking News

Phd2 v2.6.8 released.

PHD2 is open source telescope guiding software that simplifies the process of tracking a guide star, letting you concentrate on other aspects of deep-sky imaging or spectroscopy. The latest v2.6.8 release offers new functionality for Altair and QHY cameras, better tolerance of INDI/ASCOM mount drivers that incorrectly report guide speed and an updated Traditional Chinese translation.

The Open PHD Guiding project began in 2009 when Craig Stark of Stark Labs, the author of PHD Guiding and Nebulosity, released the source code of his popular PHD Guiding application. In 2012 the project was picked up by Bret McKee who did a major refactoring of the code, reworking much of the internal infrastructure and introducing the multi-threaded architecture in use by the application today.

In 2013 the project maintenance role transitioned to the current maintainers, Andy Galasso and Bruce Waddington , who have overseen the development of the application since then. The application today is the result of contributions from more than 40 developers and translators.

Developers interested in working on the project are encouraged to send pull requests via the PHD2 project page on GitHub and to participate in the PHD2 Forum. Additional information for developers is available in the PHD2 Wiki. The team is also looking for translators to translate PHD2 and to keep the existing non-English translations up to date.

Comments are closed.

• Documentation
• Getting Help

About the Open PHD Guiding Project

The Open PHD Guiding project began in 2009 when Craig Stark of Stark Labs , the author of PHD Guiding and Nebulosity, released the source code of his popular PHD Guiding application. In 2012 the project was picked up by Bret McKee who did a major refactoring of the code, reworking much of the internal infrastructure and introducing the multi-threaded architecture in use by the application today.

In 2013 the project maintenance role transitioned to the current maintainers, Andy Galasso and Bruce Waddington, who have overseen the development of the application since then. The application today is the result of contributions from more than 40 developers and translators. See Help – About in the PHD2 menu for the full list of contributors.

Developers interested in working on the project are encouraged to send pull requests via the PHD2 project page on github , and to participate in the PHD2 Forum . Additional information for developers is available in the PHD2 Wiki .

We are also looking for translators to translate PHD2 and to keep the existing non-English translations up to date.

If you are an experienced PHD2 user, we would sincerely appreciate your help advising and supporting newer users in the PHD2 forum.

The developers would like to add a special acknowledgement of the contribution of the Predictive PEC guide algorithm by the team at the Max Planck Institute, Intelligent Systems.  This contribution from the academic community highlights a benefit of developing astronomy software within a collaborative, non-commercial framework.

News & Resources

December 22, 2023 - PHD2 v2.6.13 Released

December 21, 2019 - PHD2 Best Practices

December 7, 2019 - macOS Catalina

April 26, 2018 - Polar Alignment tool video tutorials

June 12, 2016 - PHD2_Broker package available

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

Releases: OpenPHDGuiding/phd2

Lots of improvements to the Guiding Assistant Updated camera support: Altair, QHY, SBIG, SSAG (Mac), ZWO ASI New ToupTek camera support for Windows New MallinCam SkyRaider camera support for Mac INDI SBIG AO support Better detection of problems like runaway guiding, excessive backlash, and calibration problems Improved backlash compensation New Meridian flip calibration tool New ZFilter guide algorithm Guide algorithm None has been removed INDI improvements Various minor user interface fixes Updated Help file Updated translations

CameraSupport - OpenPHDGuiding/phd2 GitHub Wiki

Phd2 camera support.

Please help us keep this page up to date! You can edit this page if you have a github account. If you do not have a github account and do not want to get one, then please post on the PHD2 Forum and let us know what you would like to see updated.

NOTE : If you do not see your camera in the list below, or if it is marked as not supported, you may still be able to use it with PHD2. If the camera has an available ASCOM driver (Windows) or an INDI driver (Linux), then you can use the camera with PHD2.

SBIG Cameras

SBIG cameras only allow a single application at a time to access the camera. If the camera is one of the self-guiding models with a built-in guide camera, then the imaging app controlling the imaging chip will need to provide access to the guide camera. The only app we know of with this capability is Sequence Generator Pro which exposes the internal guide camera to PHD2 as an ASCOM camera.

Starlight Xpress Cameras

On Windows you can connect to your SX camera in two ways: with the ASCOM driver or the PHD2 built-in driver, "Starlight Xpress SXV". If you are using the ASCOM driver and want to use a Bad-pixel map in PHD2, then make sure that you disable the ASCOM driver options Square Lodestar Pixels and Gaussian Blur as these options will interfere with PHD2 being able to identify hot pixels.

ZWO Cameras

ZWO ASI cameras are supported natively on Windows, Mac, and Linux. The cameras can also be accessed with ASCOM or INDI camera drivers. On Linux, the USB 2.0 cameras may require that you flash the firmware version labeled "compatible" Forum Thread .

ToupTek Cameras

On Windows ToupTek camera support is built-in to PHD2, or you can use the ToupTek's ASCOM camera driver. Linux native support should also work, but it has not been tested yet. On Mac, you'll need the 64-bit version of PHD2 as ToupTek no longer provides SDK support for 32-bit Macs.

iOptron iGuider

The camera's gain and exposure time can be set by clicking the camera properties button on the toolbar. See this forum post for a description of how the camera's exposure time relates to PHD2's exposure duration setting.

Here is the information from iOptron showing the camera's available gain and exposure values:

Moravian Cameras

• The Moravian SDK is Windows-only, so native Moravian camera support is only available on Windows. Use the Moravian INDI driver for Mac and Linux.
• Currently PHD2's native support covers the gXusb-type cameras -- everything but the large cooled C3 and C4 cameras.
• Cameras connected through the Moravian Camera Ethernet adapter are not supported, though we could add support for that if there is a demand.

⚠️ **GitHub.com Fallback** ⚠️