Loading ...
Sorry, an error occurred while loading the content.

Re: [ASCOM] Problem with PulseGuide in the 4.0.1 Platform Gemini Driver

Expand Messages
  • mike halderman
    Did this ever get resolved? I m not sure if I saw all of the messages in this thread. I see the same problem, the gemini continues to move after PulseGuide.
    Message 1 of 8 , May 2, 2005
    • 0 Attachment
      Did this ever get resolved? I'm not sure if I saw all of the messages
      in this thread. I see the same problem, the gemini continues to move
      after PulseGuide.

      -mike

      --- In ASCOM-Talk@yahoogroups.com, "jeffrach2000" <herman@c...> wrote:
      >
      > Ajai,
      >
      > I'm the Guidedog user Steve is referring to. Just made my way to
      > this group. Steve, thanks for posting this.
      >
      > No, the Gemini driver is NOT sending the :Qx commands. The Generic
      > LX200 driver does, however. Its sends two of them, just as you
      > described.
      >
      > I have verified this by using a serial port sniffer.
      >
      > Jeff
      >
      >
      > --- In ASCOM-Talk@yahoogroups.com, "Steve Barkes" <sbarkes@c...>
      > wrote:
      > > Ajai,
      > > I don't have a Gemini mount so have no way to test this. I
      > tried using
      > > the Gemini driver on my LX200 but of course it didn't recognize
      > the mount.
      > > My user noted the issue with the Gemini driver, and confirmed
      that
      > the
      > > problem did not occur when using the Generic LX200 driver. Have
      > you tested
      > > the PulseGuide on a mount with the latest platform install to
      > verify that it
      > > does in fact work? I'm kinda stuck in the middle now. Can I
      give
      > him your
      > > email so that you can work directly with him?
      > >
      > > Sorry for the delayed response, but my Intenet connection from
      > work was down
      > > all day. So I had to do WORK ;-) That's just not right!!
      > >
      > > Steve
      > >
      > > _____
      > >
      > > From: Ajai Sehgal [mailto:ajai@s...]
      > > Sent: Monday, April 11, 2005 1:20 PM
      > > To: ASCOM-Talk@yahoogroups.com
      > > Subject: RE: [ASCOM] Problem with PulseGuide in the 4.0.1
      Platform
      > Gemini
      > > Driver
      > >
      > >
      > > Steve,
      > >
      > > I have looked into the source for the Gemini driver and it should
      > be sending
      > > not one but 2 "Q" (stop all motion) once the duration of the
      pulse
      > expires.
      > > This is done on an asynchronous timer (I use the Windows SetTimer
      > from the
      > > User32 library) in accordance with the Telescope V2 ASCOM spec
      > since the
      > > Gemini can support moves in N-S and E-W simultaneously. The
      > PulseGuide
      > > method returns immediately to you after sending the #Mx command
      > and there is
      > > a timer call back that sends the #Q's when the timer goes off.
      If
      > you are
      > > single stepping through your code you will NOT see the #Q's as
      > they are
      > > asynchronous.
      > >
      > > Ajai
      > >
      > > _____
      > >
      > > From: Ajai Sehgal [mailto:ajai@s...]
      > > Sent: Monday, April 11, 2005 10:41 AM
      > > To: 'ASCOM-Talk@yahoogroups.com'
      > > Subject: RE: [ASCOM] Problem with PulseGuide in the 4.0.1
      Platform
      > Gemini
      > > Driver
      > >
      > > Steve,
      > >
      > > I will look into it. As for my "good reason" for pulling the
      > sources: I
      > > was spending an inordinate amount of time supporting people who
      > were having
      > > problems with their Gemini and my ASCOM driver only to discover
      > that they
      > > were not using my released ASCOM driver but a "slightly modified"
      > version.
      > > If I am going to support my driver I need to control the source
      > code.
      > >
      > > Ajai
      > >
      > > _____
      > >
      > > From: Steve Barkes [mailto:sbarkes@c...]
      > > Sent: Sunday, April 10, 2005 7:09 PM
      > > To: ASCOM-Talk@yahoogroups.com
      > > Subject: [ASCOM] Problem with PulseGuide in the 4.0.1 Platform
      > Gemini Driver
      > >
      > > I had a user trying to use my GuideDog autoguiding software with
      a
      > MI-250
      > > (Gemini 3) mount. When a guiding correction was made, the scope
      > continued
      > > to move in the same direction. I'm using the Ascom PulseGuide
      > method. I
      > > looked for the Gemini source code, but it's not included in the
      > platform
      > > anymore. A Google search showed a post from Bob Denny that the
      > source for
      > > the Gemini driver had been dropped from the platform for "a good
      > reason".
      > > Not sure what that reason was but the source would have been
      > helpful in
      > > trying to debug my user's problem.
      > >
      > > I suggested to him to try the Generic LX200 driver which he did.
      > This
      > > worked for him. Apparently the latest Gemini driver issues the
      > Guide Rate,
      > > and movement commands, but doesn't issue the stop command #Qe
      (Qn,
      > Qs....)
      > > Here's a cut and past from his last email:
      > >
      > > I think I found the problem. The Gemini driver does not issue a
      > Qe# (or w,
      > > n, s depending on the direction) at the end of the pulse. It
      only
      > issues a
      > > #RG:#Me.
      > >
      > > The Generic LX200 driver does this correctly. :#RG:#Me:#Qe
      > >
      > > Steve Barkes
      > > Las Cruces, NM
      > > http://www.barkosoftware.com/GuideDog
      > >
      > >
    Your message has been successfully submitted and would be delivered to recipients shortly.