Re: [ASCOM] Re: how to build my mount driver compatible with ascom
- On 07/11/12 8:57 PM, Adam wrote:
> I have noticed that on platforms/applications that do not supportyeah, great but which set of the bajillion lx200 commands need to be
> ASCOM the Meade LX200 is usually supported. If one were to implement the
> LX200 serial port protocol getting your hardware to work on those
> platforms/applications is a bit easier. ...
implemented and what are the quirks that have to be emulated properly
for various apps to function?
john r pierce N 37, W 122
santa cruz ca mid-left coast
- Very few (if any?) apps try to *set* a guide rate.
(the Meade Autostars don't let you change the guide rate remotely)
Instead, they do a "calibration" step, whereby they move a little bit around a target star, and use the measured effect (as seen by their camera) to determine the existing guide rate.
The user may have some input into the process by setting "gain" and/or "aggressiveness" and some hysteresis parameters.
Some Meade Autostars do allow handbox-setting of guide rates.
have fun at GSSP
--- In ASCOM-Talk@yahoogroups.com, John R Pierce <pierce@...> wrote:
> On 07/18/12 5:51 AM, Tim Long wrote:
> > Regarding PulseGuide; the nice thing about designing your own system is
> > that you control these design decisions, so yes, you can assume (or
> > rather_require_) that the guide rate is at most 1x sidereal. What you
> > describe is pretty similar to how the 'classic' LX200 works. If you plan
> > to fix your guide rate at 1x sidereal then you can just return
> > CanSetGuideRates=false and make sure you return the expected values for
> > GuideRateRightAscension and GuideRateDeclination.
> so, can I assume that apps that want to set the guide rate will set and
> then query it to see what values they actually got? I very well may
> only have a rather coarse set of speeds between 0 and 1X
> (I'm going to be offline til sunday night, going to GSSP 2012,
> john r pierce N 37, W 122
> santa cruz ca mid-left coast