Thomas wrote: Thomas, There's some information about this in the PHD2 User Guide: Equipment Connection (scroll down to Mount Selection). Specifically, chose "AstroPhysics GTO V2 Mount (ASCOM)" to foll

Hi Henry, Could you post your PHD2 Debug Log and Guide Log from the session in the PHD2 forum. We can analyze the logs and check to see if it is related to the mount or if it is something else. Andy

Hi David, You may want to post you PHD2 logs (Guide log and Debug Log) in the PHD2 forum (instructions here). We can help analyze the problem from the PHD2 perspective. One of the other PHD2 developer

Jinyoung, Congratulations on the new mount! >>> Haven't cared about guiding rate (x0.5 - default) but saw that A-P driver is set to x1.0 guiding rate. Should be matched to x1.0 ? You should definitely

I had an incident last night that wreaked havoc with my imaging sequence. The imaging app issued a slew to the AP ASCOM driver at 2017-10-09 00:27:00.982, and at 2017-10-09 00:27:02.562 the driver rep

Hi Howard, Thanks for looking into it and confirming the issue. Looking forward to hearing what you learn from Ray. Andy

Thanks Ray. I have upgraded and will post another log if I see it again. Andy

That is good news. Thank you both for looking into it. Andy

In PHD2 there's a check-box labeled "Enable mount guide output" on the Guiding tab of the Advanced settings window (click the brain button). You can leave your aggressiveness setting alone and just us

>>> Matt wrote: >>> When I do a calibration with my 1100 with Absolute Encoders I get a text book result. No backlash. The guiding assistant after a 8 min run a few nights back said I had 248 rms erro

>> Matt wrote: >> Andy from PHD says that it is a delayed reaction from the DEC axis then overcorrecting. Matt, sorry for the apparent misunderstanding but I did not say that! Based on what you showed