I did find and fix this problem last night. Thanks for
reporting it. The fix will be available in the next build.
Author of APCC (Astro-Physics Command Center):
Author of PEMPro: http://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver:
Author of PulseGuide: http://www.pulseguide.com
Author of Sigma: http://www.gralak.com/sigma
> -----Original Message-----
> From: ap-gto@...
> Sent: Tuesday, August 23, 2016 11:22 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] APCC 184.108.40.206 New release (was
Funny Slewing under APCC
> Meridian Delay)
> Thank you for the response.
> I am still learning APCC so I'm just looking for
clarification if I'm using best practices
> or not.
> Previously with 220.127.116.11 I used the following to
achieve slews to a CW up position in
> the East:
> - "Enable Meridian Tracking Limits" was DISABLED
> - "Counterweight Up Slews within:" - both East and
West Limits checkboxes
> - I had NOT defined a custom meridian limits with the
graph in the center of the tab -
> it was the default.
> - I used the "Meridian Delay" spinbox to set the
meridian delay to +2 hours and hit
> 'Set' - the Current meridian delay above it changed
> - Now I could do slews to a CW up position on the
East side of the mount.
> Yesterday I upgraded to 18.104.22.168 and last night I
tried the above procedure and
> everything worked the same, until I did a slew. As
soon as I initiated a slew (using
> Cartes du Ciel via ASCOM) the 'Current' Merdian Delay
would reset to 0.0 and the
> mount moved to the target so the CW would be down.
> I primarily would just like to understand why this
operation worked in 22.214.171.124 and
> didn't work in 126.96.36.199.
> Secondarily - I'd like to understand why a slew from
a CW up position to another CW
> up position still first moves the mount in RA to the
meridian, then moves back to the
> target CW up position. Perhaps I had misunderstood
the reason for the 188.8.131.52
> release - I thought it was to address this behavior.
> Thank You,
> Michael Fulbright
> On 8/23/2016 1:10 PM, 'Ray Gralak (Groups)'
groups3@... [ap-gto] wrote:
> If you had Meridian limits enabled, then that is the
correct behavior. APCC will
> change the meridian delay to the limit for the
destination after the slew completes.
> Nothing changed in the slew behavior between 184.108.40.206
and 220.127.116.11. There is
> built-in protection to prevent continuous slews so
not sure how what you say could
> have happened. There can be a button delay, depending
on how busy your computer
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center):
> Author of PEMPro: http://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver:
> Author of PulseGuide: http://www.pulseguide.com
> Author of Sigma: http://www.gralak.com/sigma
> > -----Original Message-----
> > From: ap-gto@...
> > Sent: Tuesday, August 23, 2016 7:08 AM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] APCC 18.104.22.168 New release
(was Funny Slewing
> under APCC
> > Meridian Delay)
> > I tried the 22.214.171.124 APCC Standard release last
night and had some odd
> > behavior and wanted to clarify a few things.
> > I have only had my new Mach1 for about a week -
I started with APCC
> > Standard V 126.96.36.199 installed as well as the
latest ASCOM V2 driver
> > (5.09.01) and the GTOP4 control box. I have the
latest 6.2 ASCOM installed.
> > Here is my first question - I didn't see any
information on upgrading
> > APCC so I just installed the new 188.8.131.52 w/o
removing the 184.108.40.206
> > version - is this correct?
> > Here is the behavior I saw after installing
220.127.116.11 - perhaps the
> > answer is simply I didn't upgrade correctly - if
there is an upgrade
> > procedure online I would appreciate a link.
> > 1) With 18.104.22.168 if I wanted to image a target in
the East with the CW up
> > I just went to the 'Meridian' tab in APCC and
entered a positive
> > Meridian Delay. This has worked fine with
22.214.171.124, aside from the fact
> > any slews from a CW up position to another with
the CW up would first
> > slew to the meridian. Last night (with 126.96.36.199)
I entered a Meridian
> > Delay and it would appear in the box and you
could see the yellow line
> > shift in the display below. However, as soon as
I would do a slew the
> > box would goto '0.0' and the yellow line would
move back to the
> > meridian. In essence, the Meridian Delay was
cleared. This is
> > different behavior than what I saw in 188.8.131.52.
> > 2) When I used the ASCOM V2 driver 'jog' buttons
with 600x move speed
> > there seemed to be large lag between releasing a
button and the mount
> > stopping. Once the mount did not stop at all and
I had to hit the
> > 'STOP' button on APCC (STOP button on V2 driver
> > Previously with 184.108.40.206 I did not observe a lag
like this. Side note -
> > being able to use a gamepad to move the scope
around would really be
> > welcome here. I've posted a separate message on
this forum about the
> > problem I ran into implementing this myself with
the throttling of the
> > MoveAxis ASCOM Scope method speed on DEC.
> > 3) I got around #1 be defining a Meridian across
all inclinations on the
> > Meridian tab and enabling it. I was then able to
slew to a CW up
> > position. However when I tried a small slew (to
center frame) from a CW
> > up position to another CW up position the mount
slewed back to the
> > meridian, then slewed to the new target position
(with the CW up). This
> > is the same as the 220.127.116.11 behavior.
> > It is #3 that has me wondering if my upgrade
procedure was incorrect
> > since it is exhibiting old behavior and #3 is
what the .10 release was
> > intended to correct.
> > Please let me know if there is any additional
information that is
> > required and I can pull it together. I am new to
> > ecosystem and am not sure the proper channels to
address ASCOM driver
> > and other software issues.
> > Michael Fulbright
> > mike.fulbright@...