RE: [MaxImDL] Re: PulseGuide in MaximDL


Jun 22, 2008

 


----------------------------

#32583 Jun 22, 2008

Doug,



I have written a custom ASCOM driver that supports PulseGuide.



The ASCOM spec states that:



This method returns immediately if the hardware is capable of

back-to-back moves, i.e. dual-axis moves. For hardware not having the

dual-axis capability, the method returns only after the move has

completed.



Since my hardware supports back to back moves my driver returns

immediately. However MaximDL 4.62 never calls the IsPulseGuiding

property and so the guide is assumed to be complete. This happens when

trying to set up with Manual Guide and also when guiding itself.



PHD Guiding follows the spec and calls IsPulseGuiding to validate the

guide is in progress.



This seems to be a significant bug in the ASCOM handling of PulseGuiding.



Comments please.



----------------------------

#32607 Jun 24, 2008

Did you enable the simultaneous axis movement option in the guider

settings page of Maxim?



John



--- In MaxImDL@yahoogroups.com, "slowworm196807" yahoo@...> wrote:

>

> Doug,

>

> I have written a custom ASCOM driver that supports PulseGuide.

>

> The ASCOM spec states that:

>

> This method returns immediately if the hardware is capable of

> back-to-back moves, i.e. dual-axis moves. For hardware not having the

> dual-axis capability, the method returns only after the move has

> completed.

>

> Since my hardware supports back to back moves my driver returns

> immediately. However MaximDL 4.62 never calls the IsPulseGuiding

> property and so the guide is assumed to be complete. This happens when

> trying to set up with Manual Guide and also when guiding itself.

>

> PHD Guiding follows the spec and calls IsPulseGuiding to validate the

> guide is in progress.

>

> This seems to be a significant bug in the ASCOM handling of

PulseGuiding.

>

> Comments please.

>



----------------------------

#32610 Jun 25, 2008

What mount are we talking about here? Is it the Celestron Driver and those mounts?



Steve



.







Did you enable the simultaneous axis movement option in the guider

settings page of Maxim?



John

--- In MaxImDL@yahoogroups.com, "slowworm196807" yahoo@...> wrote:

>

> Doug,

>

> I have written a custom ASCOM driver that supports PulseGuide.

>

> The ASCOM spec states that:

>

> This method returns immediately if the hardware is capable of

> back-to-back moves, i.e. dual-axis moves. For hardware not having the

> dual-axis capability, the method returns only after the move has

> completed.

>

> Since my hardware supports back to back moves my driver returns

> immediately. However MaximDL 4.62 never calls the IsPulseGuiding

> property and so the guide is assumed to be complete. This happens when

> trying to set up with Manual Guide and also when guiding itself.

>

> PHD Guiding follows the spec and calls IsPulseGuiding to validate the

> guide is in progress.

>

> This seems to be a significant bug in the ASCOM handling of

PulseGuiding.

>

> Comments please.

>



Contact Us
This Site's Privacy Policy
Google's privacy policies

S
e
n
i
o
r
T
u
b
e
.
o
r
g