Mount does not support the required PulseGuide interface

[adavoli]

I have a Paramount MX, SBIG ST-i autoguider and have been learning how to use SGP which brings me to PHD2.  I started off having tremendous success but now I feel like things are going backwards.  I have been busy taming the rats nest on my rig but I have not changed any settings in any of my software (at least I don't remember changing anything).  For some strange reason when I try to connect to PHD2 I get an error that the mount does not support the required "PulseGuide" interface.  I have the settings in TSX set to use "DirectGuide".   I tried re-installing the "ASCOM 2x Mount Adapter Setup".  I struggled with the re-install and it gave me some errors.  I did a "run as administrator" and got the ASCOM driver to delete the old files and re-install.  This did not fix the issue.  Any advice you can share on this topic would be greatly appreciated.  I can't upload a log file since it isn't generating one.  Would it help if uploaded a log file from last week when everything was working?  

Is the order of connecting devices important? in other words do I connect using TSX, SGP or PHD2 first?  

Is it possible I changed something in SGP that is causing this problem?

I did some research on this forum and my theory is that the ASCOM driver is the problem but I can't seem to fix it.  

Thank you in advance for your time.

Anthony

[adavoli]

PROBLEM SOLVED> Not sure how that box in the ASCOM driver became UNCHECKED but I found the box to click and am back up and running.  

[Andy Galasso]

Anthony,

Glad to hear you got it sorted out.

I'm going to post some links in case anybody else encounters this problem and lands here in this discussion thread.

   PHD2 SkyX ASCOM Info: https://github.com/OpenPHDGuiding/phd2/wiki/SkyX-Settings

   PHD2 Mount info: https://github.com/OpenPHDGuiding/phd2/wiki/Mounts

I can't upload a log file since it isn't generating one.

Actually, PHD2 always generates a debug log file (useful in these kinds of situations.) Log file upload instructions are here:

   https://openphdguiding.org/getting-help/

Andy

[bw_msgboard]

Hi Anthony.  Actually, you’re only part-way to being fixed J  .  You also need to set this option:

 

 

Unless this is set, PHD2 won’t be able to get pointing information from the mount so it won’t be able to adjust for meridian flips or different Dec pointing positions.  For reasons that are incomprehensible to me, the default settings for this driver say “don’t allow ASCOM pulse-guiding and don’t tell the applications where the scope is pointing.”  Amazing.

 

These little gotchas are covered in this document:

 

https://github.com/OpenPHDGuiding/phd2/wiki/SkyX-Settings

 

Have fun,

Bruce

 

---

--
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 open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/d66dfb49-5b11-49bb-8a6a-a9b78a74ebc2%40googlegroups.com.

[Brian Valente]

just for my own curiosity where is the enable pulse guide/enable ascom check box?

is that the direct guide option?

Brian

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/C604DEC9351C477699EB12864DE9723D%40HomeDesktop.

--

Brian 

Brian Valente

portfolio brianvalentephotography.com 

[bw_msgboard]

Well, the whole thing is as clear as mud to me. J  This UI is presented by their ASCOM driver, so I guess you’re telling it to use Direct Guide and report pointing position to client apps.  I don’t really get it, but it seems to work.

 

Bruce

 

---

To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i51bmYSC7UGsb807spo98FPJQB8kq2q0kXE7%2Bn0A14xQw%40mail.gmail.com.