Date   

Re: Communications Error Messages in AP Ascom Driver

mogollonobs
 

Hi Don,

Sorry to hear of your troubles. You using the current ASCOM Platform 6.4SP1? The reason I ask is that I had an issue, although different, before I updated the platform.

Hope you get it sorted out,
Keith


Communications Error Messages in AP Ascom Driver

Don Anderson
 

I set up my AP 900 GOTO CP3 with version V firmware rig in my basement last night to do some software and firmware upgrades last night on my two laptops (main unit Lenovo i7 Win 10 home with 8 gig ram, backup unit Sony Vaio i5 Win 7 pro with 4 gig ram. I started with my old but trusty Win 7 Pro Sony Vaio laptop which has worked trouble free for years. I updated the AP Ascom driver to the latest 5.20.09 version and did some firmware updates on my focuser hub. When I started everything up, everything worked fine but after a minute or so I got the flashing yellow panel at the top of the driver indicating communication errors. I opened the driver extension windows to the final one and did a reset. Again after a minute or so the yellow warning flashed again. I then rebooted the computer and had the same result. I tried uninstalling the driver and reinstalling. Same problem. I rolled back to different older versions (5.20.08 then 5.10.02) of the driver but had the same problem. I then tried my Lenovo and had the same communication error warning popping up in the driver every minute or so. 

My current hardware configuration is to run the mount through a Keyspan Triplite 19HS (FTDI) singe port USB to serial converter connected to a 7 port powered USB hub to which the mount, focuser, main and guide cameras and filter wheel are connected. I connect the powered hub to the laptop with either a 10' usb cable or a 65' powered usb cable depending on where I am. I was using the 10' cable last night. The mount has its own dedicated pyramid 5 amp power supply.

The above setup has has worked trouble free for years. However, suspecting a hub problem, I disconnected the hub and all accessory equipment and ran the mount directly to the laptop via the Keyspan 19HS serial to USB converter. I had no other device connected at this point. Same problem occurred. I then swapped out the existing Keyspan unit with a new spare unit that I had, and tried a different 10' USB cable as well. Same problem with communication error messages popping up after about a minute. Even with the communication errors, things seem to work ok though. Mount slews to objects in both The SKY 6 and MaximDL 6.08. I then tried cleaning all the relevant electrical plugs and contacts with contact cleaner. Didn't help. 

Any ideas what's wrong?

Don Anderson


Re: New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)

Michael Fulbright <mike.fulbright@...>
 

Thanks Ray I'll get around to the upgrade soon.  Just need to finish this run of nights through the weekend without any hiccups...

Michael

On 3/23/19 5:45 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

> Understood - I have the latest ASCOM but not the latest firmware.
> I will stick with the 1.7.0.10 APCC for now
> since it has been working well.

I think that is risky. The latest firmware has a important fixes and has been in use for a while now. Also, there have been a number of important bug fixes to APCC. The version you are running is a BETA version.

BTW, the M_S slew command that is not responding in your log is most useful when the mount is in a counterweight-up position. It will keep the mount from slewing to the meridian and back again to the counterweight up position.. It doesn't do anything different for counterweight down slews.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Saturday, March 23, 2019 2:32 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Understood - I have the latest ASCOM but not the latest firmware. I will stick with the 1.7.0.10 APCC for now
> since it has been working well.
>
> Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on
> startup if that level isn't detected.
>
> Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high
> severity bug has been discovered and fixed.
>
> Thanks,
> Michael Fulbright
>
>
> On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
>
>
>
>
> Hi Michael,
>
> If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware
> and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware
> installed and also the latest AP V2 ASCOM driver.
>
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center): http://www.astro-
> physics.com/index.htm?products/accessories/software/apcc/apcc
> Author of PEMPro V3: https://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
> > -----Original Message-----
> > From: ap-gto@... [mailto:ap-gto@...]
> > Sent: Saturday, March 23, 2019 1:33 PM
> > To: ap-gto@...
> > Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
> >
> >
> >
> > Ray,
> >
> > I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
> >
> > I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-
> minutes
> > but slews smaller than this fail and the log exception is:
> >
> > 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h
> 03m
> > 17.90s), 61.1058
> > 3 (+61° 06' 21.0")
> > 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> > 12.05s), 61.1958
> > 3 (+61° 11' 45.0")
> > 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> > 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> > 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> > 61.196, 3.085,
> > 0.000. 0.000: PS = WEST: CWUP = False
> > 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> > 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> > 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> > 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew
> State=StartPrimarySlew
> > 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> > 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> > 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> > APCC,11,2749,05:03:17.9#
> > 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> > 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> > 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> > 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> > 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> > 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> > State=WaitStartPrimarySlew
> > 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> > 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form -
> option
> > is disabled or CONTROL key is pressed
> > 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> > 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> > 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> > 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> > 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> > 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> > 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> > 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> > 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> > 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> > 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> > 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> > 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> > 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> > APCC,10,2750,+27*06:40#
> > 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> > 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> > 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The
> operation
> > has timed out.
> > 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> > 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> > 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> > ª
> >
> > I can send you a complete log if it would help - it is rather large so I didn't attach it here.
> >
> > Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews
> that
> > Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was
> successful
> > but then when the slew was requested the mount simply didn't move the small distance required.
> >
> > I went back to 1.7.0.10 and it is working fine.
> >
> > Thank You,
> > Michael Fulbright
> >
> >
> > On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak..com [ap-gto] wrote:
> >
> >
> >
> >
> > Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability
> of
> > the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these
> versions with
> > the latest AP V2 ASCOM driver, v5.20.09.
> >
> > The direct download links are as follows:
> >
> > AP V2 ASCOM Driver (Released February 11, 2019)
> > https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
> >
> > APCC Standard v1.7.1.0 (Released March 14, 2019)
> > http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
> >
> > APCC Pro v1.7.1.1 (Released March 14, 2019)
> > http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
> >
> > APCC version history can be found here:
> > https://www.siriusimaging.com/Help/APCC/version_history.htm
> >
> > If you see any issues please post them here and be prepared to share log files and a way to reproduce
> an
> > issue exactly.
> >
> > Thank you!
> >
> > -Ray Gralak
> > Author of APCC (Astro-Physics Command Center): http://www.astro-
> > physics.com/index.htm?products/accessories/software/apcc/apcc
> > Author of PEMPro V3: https://www.ccdware.com
> > Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
> >
> >
> >
> >
> >
>
>
>
>
>



Re: New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)

Ray Gralak
 

Understood - I have the latest ASCOM but not the latest firmware.
I will stick with the 1.7.0.10 APCC for now
since it has been working well.
I think that is risky. The latest firmware has a important fixes and has been in use for a while now. Also, there have been a number of important bug fixes to APCC. The version you are running is a BETA version.

BTW, the M_S slew command that is not responding in your log is most useful when the mount is in a counterweight-up position. It will keep the mount from slewing to the meridian and back again to the counterweight up position. It doesn't do anything different for counterweight down slews.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, March 23, 2019 2:32 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Understood - I have the latest ASCOM but not the latest firmware. I will stick with the 1.7.0.10 APCC for now
since it has been working well.

Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on
startup if that level isn't detected.

Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high
severity bug has been discovered and fixed.

Thanks,
Michael Fulbright


On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:




Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware
and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware
installed and also the latest AP V2 ASCOM driver.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

> -----Original Message-----
> From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
> Sent: Saturday, March 23, 2019 1:33 PM
> To: ap-gto@yahoogroups.com
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Ray,
>
> I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
>
> I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-
minutes
> but slews smaller than this fail and the log exception is:
>
> 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h
03m
> 17.90s), 61.1058
> 3 (+61° 06' 21.0")
> 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> 12.05s), 61.1958
> 3 (+61° 11' 45.0")
> 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> 61.196, 3.085,
> 0.000. 0.000: PS = WEST: CWUP = False
> 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew
State=StartPrimarySlew
> 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> APCC,11,2749,05:03:17.9#
> 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> State=WaitStartPrimarySlew
> 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form -
option
> is disabled or CONTROL key is pressed
> 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> APCC,10,2750,+27*06:40#
> 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The
operation
> has timed out.
> 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> ª
>
> I can send you a complete log if it would help - it is rather large so I didn't attach it here.
>
> Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews
that
> Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was
successful
> but then when the slew was requested the mount simply didn't move the small distance required.
>
> I went back to 1.7.0.10 and it is working fine.
>
> Thank You,
> Michael Fulbright
>
>
> On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:
>
>
>
>
> Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability
of
> the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these
versions with
> the latest AP V2 ASCOM driver, v5.20.09.
>
> The direct download links are as follows:
>
> AP V2 ASCOM Driver (Released February 11, 2019)
> https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
>
> APCC Standard v1.7.1.0 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
>
> APCC Pro v1.7.1.1 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
>
> APCC version history can be found here:
> https://www.siriusimaging.com/Help/APCC/version_history.htm
>
> If you see any issues please post them here and be prepared to share log files and a way to reproduce
an
> issue exactly.
>
> Thank you!
>
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center): http://www.astro-
> physics.com/index.htm?products/accessories/software/apcc/apcc
> Author of PEMPro V3: https://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
>
>
>





Re: New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)

Michael Fulbright <mike.fulbright@...>
 

Understood - I have the latest ASCOM but not the latest firmware.  I will stick with the 1.7.0.10 APCC for now since it has been working well.

Might want to consider flagging if a given APCC release level requires a certain level of firmware with a popup on startup if that level isn't detected.

Since everything has been working for quite awhile I tend not to upgrade unless the release notes flag a high severity bug has been discovered and fixed.

Thanks,
Michael Fulbright

On 3/23/19 5:23 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware installed and also the latest AP V2 ASCOM driver.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Saturday, March 23, 2019 1:33 PM
> To: ap-gto@...
> Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7..1.0 / v1.7.1.1)
>
>
>
> Ray,
>
> I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.
>
> I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-minutes
> but slews smaller than this fail and the log exception is:
>
> 0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m
> 17.90s), 61.1058
> 3 (+61° 06' 21.0")
> 0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
> 12.05s), 61.1958
> 3 (+61° 11' 45.0")
> 0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
> 0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
> 0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
> 61.196, 3.085,
> 0.000. 0.000: PS = WEST: CWUP = False
> 0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
> 0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
> 0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
> 0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
> 0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
> 0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
> 0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
> APCC,11,2749,05:03:17.9#
> 0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
> 0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
> 0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
> 0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
> 0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
> 0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
> State=WaitStartPrimarySlew
> 0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
> 0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option
> is disabled or CONTROL key is pressed
> 0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
> 0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
> 0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
> 0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
> 0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
> 0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
> 0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
> 0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
> 0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
> 0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
> 0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
> 0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
> 0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
> 0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
> APCC,10,2750,+27*06:40#
> 0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
> 0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
> 0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation
> has timed out.
> 0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
> 0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
> 0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
> ª
>
> I can send you a complete log if it would help - it is rather large so I didn't attach it here.
>
> Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews that
> Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was successful
> but then when the slew was requested the mount simply didn't move the small distance required.
>
> I went back to 1.7.0.10 and it is working fine.
>
> Thank You,
> Michael Fulbright
>
>
> On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
>
>
>
>
> Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of
> the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7..1.1. Please use these versions with
> the latest AP V2 ASCOM driver, v5.20.09.
>
> The direct download links are as follows:
>
> AP V2 ASCOM Driver (Released February 11, 2019)
> https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe
>
> APCC Standard v1.7.1.0 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe
>
> APCC Pro v1.7.1.1 (Released March 14, 2019)
> http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe
>
> APCC version history can be found here:
> https://www.siriusimaging.com/Help/APCC/version_history.htm
>
> If you see any issues please post them here and be prepared to share log files and a way to reproduce an
> issue exactly.
>
> Thank you!
>
> -Ray Gralak
> Author of APCC (Astro-Physics Command Center): http://www.astro-
> physics.com/index.htm?products/accessories/software/apcc/apcc
> Author of PEMPro V3: https://www.ccdware.com
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
>
>
>



Re: New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)

Ray Gralak
 

Hi Michael,

If the mount is timing out is not necessarily a bug in APCC. It suggests you may be running old firmware and so the mount doesn't understand the command. Please make sure you have the latest GTOCP4 firmware installed and also the latest AP V2 ASCOM driver.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Saturday, March 23, 2019 1:33 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)



Ray,

I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.

I discovered it last night after upgrading to 1.7.1.0. Slews will work if the distance is over around 60 arc-minutes
but slews smaller than this fail and the log exception is:

0029137 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m
17.90s), 61.1058
3 (+61° 06' 21.0")
0029138 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.13668 (05h 08m
12.05s), 61.1958
3 (+61° 11' 45.0")
0029139 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
0029140 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
0029141 2019-03-23 16:16:13.074: Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD = 5.137,
61.196, 3.085,
0.000. 0.000: PS = WEST: CWUP = False
0029142 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, IsUnsafeSlew = False
0029143 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, END PierSide/CWUP = WEST, False
0029144 2019-03-23 16:16:13.074: Info, SafeSlewStateMachine, Ending Meridian Delay = 0.00
0029145 2019-03-23 16:16:13.075: Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
0029146 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
0029147 2019-03-23 16:16:13.075: Info, ProcessVPortCommand, APCC Seq= 2749, CMD=GR#
0029148 2019-03-23 16:16:13.075: Info, VPortCheckVPort1(COM21), (RX: GR#), TX:
APCC,11,2749,05:03:17.9#
0029149 2019-03-23 16:16:13.089: Debug, Command Thread, TX=':GM#'|RX='00:00:00.0#'
0029150 2019-03-23 16:16:13.089: Debug, Command Thread, TX = ':HRG#'
0029151 2019-03-23 16:16:13.121: Debug, Command Thread, TX=':HRG#'|RX='-1266*06:14#'
0029152 2019-03-23 16:16:13.121: Debug, Command Thread, TX = ':HDG#'
0029153 2019-03-23 16:16:13.136: Info, SafeSlewStateMachine, Slewing to RA/Dec = 5.1367, 61.1958
0029154 2019-03-23 16:16:13.136: Debug, SafeSlewStateMachine, New SafeSlew
State=WaitStartPrimarySlew
0029155 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Restore = False
0029156 2019-03-23 16:16:13.145: Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option
is disabled or CONTROL key is pressed
0029157 2019-03-23 16:16:13.153: Debug, Command Thread, TX=':HDG#'|RX='+4123*31:36#'
0029158 2019-03-23 16:16:13.153: Debug, Command Thread, TX = '#:GP#'
0029159 2019-03-23 16:16:13.185: Debug, Command Thread, TX='#:GP#'|RX='00:00:56.4#'
0029160 2019-03-23 16:16:13.185: Debug, Command Thread, TX = ':Rr#'
0029161 2019-03-23 16:16:13.201: Debug, Command Thread, TX=':Rr#'|RX='0#'
0029162 2019-03-23 16:16:13.201: Debug, Command Thread, TX = ':Rd#'
0029163 2019-03-23 16:16:13.217: Debug, Command Thread, TX=':Rd#'|RX='0#'
0029164 2019-03-23 16:16:13.217: Debug, Command Thread, TX = ':Sr05:08:12.1#'
0029165 2019-03-23 16:16:13.231: Info, VPort1(COM21), RX: :APCC,2750,GZ#
0029166 2019-03-23 16:16:13.249: Debug, Command Thread, TX=':Sr05:08:12.1#'|RX='1'
0029167 2019-03-23 16:16:13.249: Debug, Command Thread, TX = ':Sd+61*11:45#'
0029168 2019-03-23 16:16:13.262: Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
0029169 2019-03-23 16:16:13.263: Info, ProcessVPortCommand, APCC Seq= 2750, CMD=GZ#
0029170 2019-03-23 16:16:13.263: Info, VPortCheckVPort1(COM21), (RX: GZ#), TX:
APCC,10,2750,+27*06:40#
0029171 2019-03-23 16:16:13.265: Debug, Command Thread, TX=':Sd+61*11:45#'|RX='1'
0029172 2019-03-23 16:16:13.265: Debug, Command Thread, TX = ':M_S#'
0029173 2019-03-23 16:16:13.365: Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation
has timed out.
0029174 2019-03-23 16:16:13.365: Debug, Command Thread, TX=':M_S#'|RX=''
0029175 2019-03-23 16:16:13.366: Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
0029176 2019-03-23 16:16:13.366: Error, mySlewStarted, No response from mount
ª

I can send you a complete log if it would help - it is rather large so I didn't attach it here.

Slews of around 60 arc-minutes or greater are working fine. I only noticed this because the precise slews that
Voyager were doing were failing to get within my threshold (60 arc-seconds). The plate solve/sync was successful
but then when the slew was requested the mount simply didn't move the small distance required.

I went back to 1.7.0.10 and it is working fine.

Thank You,
Michael Fulbright


On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:




Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of
the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with
the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an
issue exactly.

Thank you!

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-
physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver





Re: New Released versions of APCC Standard/Pro (v1.7.1.0 / v1.7.1.1)

Michael Fulbright <mike.fulbright@...>
 

Ray,

  I've encountered what may be an issue with 1.7.1.0 versus 1.7.0.10 Standard.

  I discovered it last night after upgrading to 1.7.1.0.  Slews will work if the distance is over around 60 arc-minutes but slews smaller than this fail and the log exception is:

0029137 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Slewing from RA/Dec = 5.05497 (05h 03m 17.90s), 61.1058
3 (+61° 06' 21.0")
0029138 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Slewing to   RA/Dec = 5.13668 (05h 08m 12.05s), 61.1958
3 (+61° 11' 45.0")
0029139 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Starting Meridian Delay = 0.00
0029140 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Start PierSide/CWUP = WEST, False
0029141 2019-03-23 16:16:13.074:       Info, GetDestinationPierSide, RA,Dec,LST,EastMD,WestMD =   5.137,  61.196,   3.085,
   0.000.   0.000: PS = WEST: CWUP = False
0029142 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine,   IsUnsafeSlew = False
0029143 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine,   END PierSide/CWUP = WEST, False
0029144 2019-03-23 16:16:13.074:       Info, SafeSlewStateMachine, Ending   Meridian Delay = 0.00
0029145 2019-03-23 16:16:13.075:      Debug, SafeSlewStateMachine, New SafeSlew State=StartPrimarySlew
0029146 2019-03-23 16:16:13.075:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,2749,GR#
0029147 2019-03-23 16:16:13.075:       Info, ProcessVPortCommand, APCC Seq=    2749, CMD=GR#
0029148 2019-03-23 16:16:13.075:       Info, VPortCheckVPort1(COM21), (RX: GR#), TX: APCC,11,2749,05:03:17.9#
0029149 2019-03-23 16:16:13.089:      Debug,  Command Thread, TX=':GM#'|RX='00:00:00.0#'
0029150 2019-03-23 16:16:13.089:      Debug,  Command Thread, TX = ':HRG#'
0029151 2019-03-23 16:16:13.121:      Debug,  Command Thread, TX=':HRG#'|RX='-1266*06:14#'
0029152 2019-03-23 16:16:13.121:      Debug,  Command Thread, TX = ':HDG#'
0029153 2019-03-23 16:16:13.136:       Info, SafeSlewStateMachine, Slewing to   RA/Dec = 5.1367, 61.1958
0029154 2019-03-23 16:16:13.136:      Debug, SafeSlewStateMachine, New SafeSlew State=WaitStartPrimarySlew
0029155 2019-03-23 16:16:13.145:      Debug, RestoreFormPosition, EmergencyStop: Restore = False
0029156 2019-03-23 16:16:13.145:      Debug, RestoreFormPosition, EmergencyStop: Not restoring form - option is disabled or CONTROL key is pressed
0029157 2019-03-23 16:16:13.153:      Debug,  Command Thread, TX=':HDG#'|RX='+4123*31:36#'
0029158 2019-03-23 16:16:13.153:      Debug,  Command Thread, TX = '#:GP#'
0029159 2019-03-23 16:16:13.185:      Debug,  Command Thread, TX='#:GP#'|RX='00:00:56.4#'
0029160 2019-03-23 16:16:13.185:      Debug,  Command Thread, TX = ':Rr#'
0029161 2019-03-23 16:16:13.201:      Debug,  Command Thread, TX=':Rr#'|RX='0#'
0029162 2019-03-23 16:16:13.201:      Debug,  Command Thread, TX = ':Rd#'
0029163 2019-03-23 16:16:13.217:      Debug,  Command Thread, TX=':Rd#'|RX='0#'
0029164 2019-03-23 16:16:13.217:      Debug,  Command Thread, TX = ':Sr05:08:12.1#'
0029165 2019-03-23 16:16:13.231:       Info,   VPort1(COM21), RX: :APCC,2750,GZ#
0029166 2019-03-23 16:16:13.249:      Debug,  Command Thread, TX=':Sr05:08:12.1#'|RX='1'
0029167 2019-03-23 16:16:13.249:      Debug,  Command Thread, TX = ':Sd+61*11:45#'
0029168 2019-03-23 16:16:13.262:       Info, ProcessVPortCommand, RX from VPort 1: :APCC,2750,GZ#
0029169 2019-03-23 16:16:13.263:       Info, ProcessVPortCommand, APCC Seq=    2750, CMD=GZ#
0029170 2019-03-23 16:16:13.263:       Info, VPortCheckVPort1(COM21), (RX: GZ#), TX: APCC,10,2750,+27*06:40#
0029171 2019-03-23 16:16:13.265:      Debug,  Command Thread, TX=':Sd+61*11:45#'|RX='1'
0029172 2019-03-23 16:16:13.265:      Debug,  Command Thread, TX = ':M_S#'
0029173 2019-03-23 16:16:13.365:  Exception, ProcessQAC: ComPort Read error. Sent=:M_S#, The operation has timed out.
0029174 2019-03-23 16:16:13.365:      Debug,  Command Thread, TX=':M_S#'|RX=''
0029175 2019-03-23 16:16:13.366:      Debug, Slew Start Callback, New SafeSlew State=WaitPrimarySlew
0029176 2019-03-23 16:16:13.366:      Error,   mySlewStarted, No response from mount
ª

I can send you a complete log if it would help - it is rather large so I didn't attach it here.

Slews of around 60 arc-minutes or greater are working fine.  I only noticed this because the precise slews that Voyager were doing were failing to get within my threshold (60 arc-seconds).  The plate solve/sync was successful but then when the slew was requested the mount simply didn't move the small distance required.

I went back to 1.7.0.10 and it is working fine.

Thank You,
Michael Fulbright

On 3/17/19 6:53 PM, 'Ray Gralak (Groups)' groups3@... [ap-gto] wrote:
 

Astro-Physics would like to thank everyone that helped with beta testing and to announce the availability of the public RELEASE version of APCC Standard v1.7.1.0 and APCC Pro v1.7.1.1. Please use these versions with the latest AP V2 ASCOM driver, v5.20.09.

The direct download links are as follows:

AP V2 ASCOM Driver (Released February 11, 2019)
https://www.siriusimaging.com/apdriver/AstroPhysics_V2_Setup_5.20.09.exe

APCC Standard v1.7.1.0 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Standard_Setup_1.7.1.0.exe

APCC Pro v1.7.1.1 (Released March 14, 2019)
http://www.apastrosoftware.com/apcc_download/APCC_Pro_Setup_1.7.1.1.exe

APCC version history can be found here:
https://www.siriusimaging.com/Help/APCC/version_history.htm

If you see any issues please post them here and be prepared to share log files and a way to reproduce an issue exactly.

Thank you!

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver



Re: M51 and First Light With AP 1100GTO Mount

Stuart Heggie <stuart.j.heggie@...>
 

Ben, I'm running twin rigs now (again). I suggest practicing hanging wallpaper with one hand tied behind your back. That skill will come in handy. ;-)


On Sat, 23 Mar 2019 at 10:44, benjamin.e.c.koltenbah@... [ap-gto] <ap-gto@...> wrote:
 

Thank you all!  I''m sure looking forward to using this mount.

It's my intention to have two rigs running simultaneously.  The Mach1 mount will be used mainly with smaller scopes.  I'm almost ready to run each system independently.

Ben



Re: M51 and First Light With AP 1100GTO Mount

Ben Koltenbah
 

Thank you all!  I''m sure looking forward to using this mount.

It's my intention to have two rigs running simultaneously.  The Mach1 mount will be used mainly with smaller scopes.  I'm almost ready to run each system independently.

Ben



Re: M51 and First Light With AP 1100GTO Mount

Dan Richey
 

Really nice. I used to have a C11. Several generations past. Looks like they have made many improvements on that scope.

Dan Richey


Re: M51 and First Light With AP 1100GTO Mount

Stuart Heggie <stuart.j.heggie@...>
 

Congrats Ben! Great image!


On Fri, 22 Mar 2019 at 13:03, benjamin.e.c.koltenbah@... [ap-gto] <ap-gto@...> wrote:
 

Greetings!

I wanted to post about my successful "first light" using my new AP 1100GTO mount.  It worked flawlessly, and in fact after just a few minutes I forgot that it was even there.  Coupled with a new portable pier, it's a tall system, and I'm pleased that with my Celestron 11" EDGE I can start imaging certain targets many hours before they cross the meridian, thus avoiding a meridian flip.

In many ways I like this even more than my Mach1, particularly with the ALT adjuster, insert for keeping internal cables out of the path of the polar scope, and of course being sturdier with larger payloads.  It does take me longer to set up and tear down than the Mach1, but that's partly due to me not being as familiar with it yet.  This is also a step up for me from GTOCP3 to GTOCP4, where I certainly haven't explored all the benefits of the newer control.

Here is an image of M51 taken with the C11 + 0.7x FR + QSI 683, only 1 hr integration time on L, 2 hrs each on RGB.  I only got good seeing conditions for half a night out of a total of four nights, otherwise I would have preferred a lot more integration time on the L channel, but overall I'm pleased with the result.

Best Regards,
Ben




Re: Edge HD 1100 on AP Mach1 GTO

DFisch
 

George, given the moment arm difference Edge vs RASA and a substantive weight difference I would use the Edge comfortably on Mach1

TJF 📱

On Fri, Mar 22, 2019, 17:29 glutch@... [ap-gto] <ap-gto@...> wrote:
 

So I saw the question about the RASA 11" on the Mach1 and wanted to make sure what I was thinking about doing would work.  I have an Edge HD 1100 by celestron with the Hyperstar that when all is said and done weighs 42 pounds.  I am wanting to do AP work on with this setup on a Mach1 and just wanted to verify that the Mach1 could handle it.

George C. Lutch



Re: M51 and First Light With AP 1100GTO Mount

Robert Chozick
 

Really well done.  Beautiful image. 

Enjoy your new mount.  It is really true that an AP mount takes the mount out of the equation when analyzing any problems with a setup. 

Robert 


On Mar 22, 2019, at 11:25 AM, benjamin.e.c.koltenbah@... [ap-gto] <ap-gto@...> wrote:

 

Greetings!

I wanted to post about my successful "first light" using my new AP 1100GTO mount.  It worked flawlessly, and in fact after just a few minutes I forgot that it was even there.  Coupled with a new portable pier, it's a tall system, and I'm pleased that with my Celestron 11" EDGE I can start imaging certain targets many hours before they cross the meridian, thus avoiding a meridian flip.

In many ways I like this even more than my Mach1, particularly with the ALT adjuster, insert for keeping internal cables out of the path of the polar scope, and of course being sturdier with larger payloads.  It does take me longer to set up and tear down than the Mach1, but that's partly due to me not being as familiar with it yet.  This is also a step up for me from GTOCP3 to GTOCP4, where I certainly haven't explored all the benefits of the newer control.

Here is an image of M51 taken with the C11 + 0.7x FR + QSI 683, only 1 hr integration time on L, 2 hrs each on RGB.  I only got good seeing conditions for half a night out of a total of four nights, otherwise I would have preferred a lot more integration time on the L channel, but overall I'm pleased with the result.

Best Regards,
Ben




Re: M51 and First Light With AP 1100GTO Mount

Roland Christen
 

Congratulations on a great setup. May you have many clear nights ahead.

Rolando



-----Original Message-----
From: benjamin.e.c.koltenbah@... [ap-gto]
To: ap-gto
Sent: Fri, Mar 22, 2019 11:26 am
Subject: [ap-gto] M51 and First Light With AP 1100GTO Mount



Greetings!

I wanted to post about my successful "first light" using my new AP 1100GTO mount.  It worked flawlessly, and in fact after just a few minutes I forgot that it was even there.  Coupled with a new portable pier, it's a tall system, and I'm pleased that with my Celestron 11" EDGE I can start imaging certain targets many hours before they cross the meridian, thus avoiding a meridian flip.

In many ways I like this even more than my Mach1, particularly with the ALT adjuster, insert for keeping internal cables out of the path of the polar scope, and of course being sturdier with larger payloads.  It does take me longer to set up and tear down than the Mach1, but that's partly due to me not being as familiar with it yet.  This is also a step up for me from GTOCP3 to GTOCP4, where I certainly haven't explored all the benefits of the newer control.

Here is an image of M51 taken with the C11 + 0.7x FR + QSI 683, only 1 hr integration time on L, 2 hrs each on RGB.  I only got good seeing conditions for half a night out of a total of four nights, otherwise I would have preferred a lot more integration time on the L channel, but overall I'm pleased with the result.

Best Regards,
Ben






M51 and First Light With AP 1100GTO Mount

Ben Koltenbah
 

Greetings!

I wanted to post about my successful "first light" using my new AP 1100GTO mount.  It worked flawlessly, and in fact after just a few minutes I forgot that it was even there.  Coupled with a new portable pier, it's a tall system, and I'm pleased that with my Celestron 11" EDGE I can start imaging certain targets many hours before they cross the meridian, thus avoiding a meridian flip.

In many ways I like this even more than my Mach1, particularly with the ALT adjuster, insert for keeping internal cables out of the path of the polar scope, and of course being sturdier with larger payloads.  It does take me longer to set up and tear down than the Mach1, but that's partly due to me not being as familiar with it yet.  This is also a step up for me from GTOCP3 to GTOCP4, where I certainly haven't explored all the benefits of the newer control.

Here is an image of M51 taken with the C11 + 0.7x FR + QSI 683, only 1 hr integration time on L, 2 hrs each on RGB.  I only got good seeing conditions for half a night out of a total of four nights, otherwise I would have preferred a lot more integration time on the L channel, but overall I'm pleased with the result.

Best Regards,
Ben




Re: Any special trick to not cross-thread AP1100 counter weight bar

John A. Sillasen
 

That's funny,  Peter. As soon as I read George's post, I sent him  a direct email asking the very same question.  I, too, have a first run build, S/N# 0009. I did upgrade to the GTO-CP4 & while I had the A-P Portable Pier, which I still  have,  I upgraded to the ATS Portable Pier.

Since I travel regularly with my Mach 1 on an Eagle Pier, I can afford to be without my 1100's CounterWeight shaft for an alteration or upgrade of some kind.

Here's hoping one of us gets a positive reply.  I'd much prefer not to muck up the threads on either side.  Since I keep my 1100 as a single unit in a huge  SKB travel or should I say, transportable case, I don't have the option of setting up one half to thread in a shaft. Well, let should say, I really don't want to have to pull the halves apart just to do that.

I made a big enough mistake not getting the thicker CounterWeight shaft and its larger hole CounterWeights.  Each mount has it's own dedicated set of counterweights!  I even got a pair of the new weight Mach 1 counterweights.  I don't want to retrofit everything after all that!


John A. Sillasen


Re: Any special trick to not cross-thread AP1100 counter weight bar during install

topboxman
 

FYI, my message was directed to George, Rolando or other Astro-Physics people. No hurry to respond.

Thanks,
Peter


---In ap-gto@..., <pnagy@...> wrote :

I have a first run AP1100 without the 1/2" lead-in CW shaft. Would it be possible to ship my CW shaft to you for you to put the shaft on your metal lathe to create a lead-in or is it too late?

Thanks,
Peter


Re: Any special trick to not cross-thread AP1100 counter weight bar during install

topboxman
 

I have a first run AP1100 without the 1/2" lead-in CW shaft. Would it be possible to ship my CW shaft to you for you to put the shaft on your metal lathe to create a lead-in or is it too late?

Thanks,
Peter


Re: Edge HD 1100 on AP Mach1 GTO

Roland Christen
 

The Mach1 has the same motors as the 1100 mount, so it's no problem for the electronics or the motors to drive this much weight. The Mach 1 worm wheels are smaller at 150mm versus 183mm for the 1100 mount. The base is smaller at 6" versus 8" for the 1100 mount. I have used my old 10" Mak-Cass on the Mach1 (weight about 45lb) without problem on the Mach1. As far as tracking, if everything is balanced, the mount will track just fine.

Rolando



-----Original Message-----
From: glutch@... [ap-gto]
To: ap-gto
Sent: Wed, Mar 20, 2019 4:47 pm
Subject: [ap-gto] Edge HD 1100 on AP Mach1 GTO



So I saw the question about the RASA 11" on the Mach1 and wanted to make sure what I was thinking about doing would work.  I have an Edge HD 1100 by celestron with the Hyperstar that when all is said and done weighs 42 pounds.  I am wanting to do AP work on with this setup on a Mach1 and just wanted to verify that the Mach1 could handle it.

George C. Lutch




Edge HD 1100 on AP Mach1 GTO

George Lutch
 

So I saw the question about the RASA 11" on the Mach1 and wanted to make sure what I was thinking about doing would work.  I have an Edge HD 1100 by celestron with the Hyperstar that when all is said and done weighs 42 pounds.  I am wanting to do AP work on with this setup on a Mach1 and just wanted to verify that the Mach1 could handle it.

George C. Lutch


17841 - 17860 of 82432