Date   

Re: Upcoming solar eclipse

Karen Christen
 

The AP folks – Roland, Marj, George, Christine, and Karen – will be in Casper, WY for ASTROCON, and then outside the city for the eclipse.  Sorry we’ll miss you, Chris!
Karen

 

From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 02, 2017 4:21 PM
To: ap-gto@...
Subject: RE: [ap-gto] Upcoming solar eclipse

 

 

Victor, Idaho.  Just outside the main gate of Yellowstone.

 

Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.

 

 

-Christopher Erickson
Observatory engineer
Summit Kinetics

Waikoloa, HI 96738
www.summitkinetics.com

 

 


From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred

 

Virus-free. www.avg.com


Re: PEMPro without a keypad?

Christopher Erickson
 

You don't need a keypad to operate PEMPro and analyze your PEM curve and optionally create and save a new one.
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 



From: ap-gto@... [mailto:ap-gto@...]
Sent: Tuesday, July 4, 2017 4:24 PM
To: ap-gto@...
Subject: [ap-gto] PEMPro without a keypad?

Hi all,


I'm waiting for my new mount to arrive, so I decided to look through the APCC manual while I wait. I read through a brief discussion of PEMPro, and if I'm reading it correctly, the preferred method to record PEM is to use the keypad in order to record more than one worm cycle. I didn't order a keypad because I'll be imaging with a computer. Is it possible to use a virtual keypad (either ASCOM or APCC keypad window) to get a multi-cycle PEM recording?


I am aware that the mount comes preprogrammed for my specific mount, but I assume that I'll want to do a new recording at some point in the future.


Thanks,

Dave


Virus-free. www.avg.com


PEMPro without a keypad?

Dave Bartolini
 

Hi all,


I'm waiting for my new mount to arrive, so I decided to look through the APCC manual while I wait. I read through a brief discussion of PEMPro, and if I'm reading it correctly, the preferred method to record PEM is to use the keypad in order to record more than one worm cycle. I didn't order a keypad because I'll be imaging with a computer. Is it possible to use a virtual keypad (either ASCOM or APCC keypad window) to get a multi-cycle PEM recording?


I am aware that the mount comes preprogrammed for my specific mount, but I assume that I'll want to do a new recording at some point in the future.


Thanks,

Dave


odd parking position discrepancy

john
 

Hi,


John Collins from Oregon here. Wondering if anyone has seen/fixed this:

Historically, my CP3-controlled setup (AP 1600GTO, CDK17, STX camera) would maneuver all night and return to park with no discrepancy at all using SkyX native driver. Setting up a new observatory with CP4, APCC Pro, and V2 driver, I'm seeing a discrepancy creep into results. I have a digital level on the cw shaft....physically set RA and DEC to 0.00 degrees at park 4.....if I so much as nudge the scope out of park, then repark using APCC pro for both moves, I have a 0.4 degree RA and a 1.1 degree DEC error when apcc reports parked. These discrepancies repeat reliably...that is, there doesn't seem to be some loose thingy flapping around...the errors are quite deliberate. The weird part is that SkyX pro "likes" the erroneous numbers better, showing the scope parked right-on-the money, whereas there is a slight offset in SkyX when the park 4 numbers are "correct".

I'm sitting here in daylight just fiddling...will experiment tonight as to what actually works........

This may be part of CP4/APCC new-guy syndrome, so feel free to bop me on the head if needed...never saw this issue with CP3, but then I didn't have this resolution before either. I've done the balance, lash, etc........drawing a blank at this point. Any ideas?


thanks

John Collins

Oregon

________________


Re: Upcoming solar eclipse

CurtisC
 

Menan, Idaho, for me.


Re: FIXED!! fiasco with apcc/V2 driver virtual ports

Ray Gralak
 

Hi John,

I'm glad that you were able to fix the problem!

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

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Monday, July 3, 2017 2:28 PM
To: ap-gto@yahoogroups.com
Subject: [ap-gto] FIXED!! fiasco with apcc/V2 driver virtual ports



Hi

To everyone that responded, thank you. The virtual ports issue was pretty persistent...uninstalling, scrubbing
the registry, and reinstalling the FTDI drivers fixed things perfectly. Comms are back to normal now. Another
lesson in Leave-No-Stone-Unturned: since the physical port appeared to be working, I had ruled out the FTDI
stuff and concentrated on the virtual ports as the issue. If only I understood all this...........

In any case, all fixed....

John Collins

Eugene, Oregon

____________________________

On 6/29/2017 6:43 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto]
wrote:
Hi John,

First, I assume you have connected APCC to the mount or driver will not connect.

If that's not the problem, are you using a USB/serial device? Some are known to use a new virtual port
every time, thus eventually using all the virtual ports.

Then, try this:

1) Open Device Manager

2) From the View menu, select 'Show Hidden Devices'

3) Expand 'Ports (COM & LPT)' category from the list

4) Right-click on all the devices and remove them (no need to tick to
delete the driver)

5) From the Action menu, select 'Scan for New Devices'

Then enable the checkbox "Auto-Config" in the AP V2 driver and try connecting. If that doesn't work
uncheck the option and set the first two ports to ports you don't think have ever been used, like maybe
COM20 and COM21. Create the ports in APCC to make sure they work. Make sure you are connected to the
mount in APCC or driver will not connect. Then try connecting using one of the AP ASCOM driver utilities,
like AP Jog.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
http://www.astro-physics.com/index.htm?products/accessories/software/a
pcc/apcc Author of PEMPro: http://www.ccdware.com Author of
Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author
of PulseGuide: http://www.pulseguide.com Author of Sigma:
http://www.gralak.com/sigma


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Thursday, June 29, 2017 12:49 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi Ray,

Thanks for the effort, but I think I may not have been clear.

The entire setup of apcc pro, V2, skyX and the CP4 were operating
well...I was even marvelling at how simple the setup had been.
Something has happened that is causing a problem....in bullet point form:

* previously working system is started after standing for
days...everything fires up, but the V2 Com port # indicator in APCC
pulsed on/off 4 times then threw the "no mount on com port" error.
The mount is operating properly.

* V2 com port intermittently connected in response to manual
"connect", eventually throwing a "create virtual port before trying to connect"
after several tries...the apcc virtual ports page showed no virtual
ports (had been com 9 and com 11)...com 9 and 11 missing from
drop-down list

* Device manager shows virtual ports 9 and 10 but apcc has com 9 and
11 removed from drop down list AND not created in apcc --- situation
is deteriorating

*tried the "now" button...nothing--I've ended up with com 9 and 11
half-selected--new selections seem locked out

*tried delete all and delete residual, nothing. Uninstalled,
scrubbed, reinstalled apcc and V2....problem persists....I expect
some config file is being left behind at uninstall---configs
reappeared on reinstall, complete with virtual ports issue

*After reinstall, virtual ports do not appear in device manager

* tried com 11...connected, but pulsed and died, throwing error

*tried "now".....nothing. Manually selected com 15.....worked for one
session.....restarted apcc and com 15 started the pulse-and-die behavior.

I suspect the ultimate solution is to uninstall/reinstall, however
there seems to be a file or files that remain after uninstall, which
preserves the problem. I can handle the reinstallation easy-peasy,
but not sure where the files that store configs may be. I'd like to
do a thorough reinstall. Whatever the original cause, I have no idea.

What do I have to delete/uninstall to kill my original config--I'll
reenter info from scratch.

thanks

John Collins

__________________________________________________________

On 6/29/2017 6:09 AM, 'Ray Gralak (Groups)' groups3@gralak.com
[ap-gto]
wrote:
Hi John,

While the V2 driver did not connect when apcc called, it did
connect manually using the connect button.......tried fiddling with
the V2 com port timeout setting--no discernable change.
A number of builds ago, a "Now" button, as in "configure now", was
added in
APCC's "AP V2 Driver" group box. When clicked, APCC will find free
virtual ports and automomagically configure everything in the ASCOM
driver, including setting the virtual port number. You should not
even need to open the AP V2 driver's setup window. This was done to make it extremely simple to
configure all settings.
Best regards,

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

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Thursday, June 29, 2017 12:15 AM
To: ap-gto@yahoogroups.com
Subject: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi,

John Collins from Eugene, Oregon here. Operations just went
downhill incredibly fast....I had been running apcc pro ver
1.5.0.20 with the V2 driver ver 5.09.09 just fine using USB
control. Started up tonight and apcc started, then called the V2
driver as always, however, the V2 virtual com port# window pulsed
on/off 4 times and threw an "error connecting to the AP V2
driver-no mount on the com port". I checked port #'s, aok.
Restarted pc and apcc showed no virtual com ports....win
10 dev mgr showed com9 and com 10 virtual ports. APCC would not
delete or recreate the ports--com 9 and 10 were not in apcc's port
selection drop down....probably since they were considered in use(?).

While the V2 driver did not connect when apcc called, it did
connect manually using the connect button.......tried fiddling with
the V2 com port timeout setting--no discernable change.

Tried the "use ascom object" check box as suggested--no change.

Uninstalled and reinstalled apcc pro (checked the install/reinstall
virtual ports box) and V2 driver....no change.......apcc calls the
driver, but no data loaded into display windows. APCC pro does have
all the mount data displayed via the physical port. Now the V2
driver is not even trying to connect.

I smell a rat in my pc but can't find it........

any ideas?

will try going back to the native skyX driver for the moment

many thanks

John Collins

____________________________________________________



------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@gralak.com>
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list see
http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links





------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@gralak.com>
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list see
http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links






FIXED!! fiasco with apcc/V2 driver virtual ports

john
 

Hi

To everyone that responded, thank you. The virtual ports issue was pretty persistent...uninstalling, scrubbing the registry, and reinstalling the FTDI drivers fixed things perfectly. Comms are back to normal now. Another lesson in Leave-No-Stone-Unturned: since the physical port appeared to be working, I had ruled out the FTDI stuff and concentrated on the virtual ports as the issue. If only I understood all this...........

In any case, all fixed....

John Collins

Eugene, Oregon

____________________________

On 6/29/2017 6:43 PM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto] wrote:
Hi John,

First, I assume you have connected APCC to the mount or driver will not connect.

If that's not the problem, are you using a USB/serial device? Some are known to use a new virtual port every time, thus eventually using all the virtual ports.

Then, try this:

1) Open Device Manager

2) From the View menu, select 'Show Hidden Devices'

3) Expand 'Ports (COM & LPT)' category from the list

4) Right-click on all the devices and remove them (no need to tick to delete the driver)

5) From the Action menu, select 'Scan for New Devices'

Then enable the checkbox "Auto-Config" in the AP V2 driver and try connecting. If that doesn't work uncheck the option and set the first two ports to ports you don't think have ever been used, like maybe COM20 and COM21. Create the ports in APCC to make sure they work. Make sure you are connected to the mount in APCC or driver will not connect. Then try connecting using one of the AP ASCOM driver utilities, like AP Jog.

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


-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Thursday, June 29, 2017 12:49 PM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi Ray,

Thanks for the effort, but I think I may not have been clear.

The entire setup of apcc pro, V2, skyX and the CP4 were operating
well...I was even marvelling at how simple the setup had been. Something
has happened that is causing a problem....in bullet point form:

* previously working system is started after standing for
days...everything fires up, but the V2 Com port # indicator in APCC
pulsed on/off 4 times then threw the "no mount on com port" error. The
mount is operating properly.

* V2 com port intermittently connected in response to manual "connect",
eventually throwing a "create virtual port before trying to connect"
after several tries...the apcc virtual ports page showed no virtual
ports (had been com 9 and com 11)...com 9 and 11 missing from drop-down list

* Device manager shows virtual ports 9 and 10 but apcc has com 9 and 11
removed from drop down list AND not created in apcc --- situation is
deteriorating

*tried the "now" button...nothing--I've ended up with com 9 and 11
half-selected--new selections seem locked out

*tried delete all and delete residual, nothing. Uninstalled, scrubbed,
reinstalled apcc and V2....problem persists....I expect some config file
is being left behind at uninstall---configs reappeared on reinstall,
complete with virtual ports issue

*After reinstall, virtual ports do not appear in device manager

* tried com 11...connected, but pulsed and died, throwing error

*tried "now".....nothing. Manually selected com 15.....worked for one
session.....restarted apcc and com 15 started the pulse-and-die behavior.

I suspect the ultimate solution is to uninstall/reinstall, however there
seems to be a file or files that remain after uninstall, which preserves
the problem. I can handle the reinstallation easy-peasy, but not sure
where the files that store configs may be. I'd like to do a thorough
reinstall. Whatever the original cause, I have no idea.

What do I have to delete/uninstall to kill my original config--I'll
reenter info from scratch.

thanks

John Collins

__________________________________________________________

On 6/29/2017 6:09 AM, 'Ray Gralak (Groups)' groups3@gralak.com [ap-gto]
wrote:
Hi John,

While the V2 driver did not connect when apcc called, it did connect
manually using the connect button.......tried fiddling with the V2 com
port timeout setting--no discernable change.
A number of builds ago, a "Now" button, as in "configure now", was added in
APCC's "AP V2 Driver" group box. When clicked, APCC will find free virtual ports
and automomagically configure everything in the ASCOM driver, including setting the
virtual port number. You should not even need to open the AP V2 driver's setup
window. This was done to make it extremely simple to configure all settings.
Best regards,

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

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Thursday, June 29, 2017 12:15 AM
To: ap-gto@yahoogroups.com
Subject: [ap-gto] fiasco with apcc/V2 driver virtual ports



Hi,

John Collins from Eugene, Oregon here. Operations just went downhill
incredibly fast....I had been running apcc pro ver 1.5.0.20 with the V2
driver ver 5.09.09 just fine using USB control. Started up tonight and
apcc started, then called the V2 driver as always, however, the V2
virtual com port# window pulsed on/off 4 times and threw an "error
connecting to the AP V2 driver-no mount on the com port". I checked
port #'s, aok. Restarted pc and apcc showed no virtual com ports....win
10 dev mgr showed com9 and com 10 virtual ports. APCC would not delete
or recreate the ports--com 9 and 10 were not in apcc's port selection
drop down....probably since they were considered in use(?).

While the V2 driver did not connect when apcc called, it did connect
manually using the connect button.......tried fiddling with the V2 com
port timeout setting--no discernable change.

Tried the "use ascom object" check box as suggested--no change.

Uninstalled and reinstalled apcc pro (checked the install/reinstall
virtual ports box) and V2 driver....no change.......apcc calls the
driver, but no data loaded into display windows. APCC pro does have all
the mount data displayed via the physical port. Now the V2 driver is
not even trying to connect.

I smell a rat in my pc but can't find it........

any ideas?

will try going back to the native skyX driver for the moment

many thanks

John Collins

____________________________________________________



------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@gralak.com>
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links





------------------------------------
Posted by: "Ray Gralak &#92;(Groups&#92;)" <groups3@gralak.com>
------------------------------------

To UNSUBSCRIBE, or for general information on the ap-gto list
see http://groups.yahoo.com/group/ap-gto
------------------------------------

Yahoo Groups Links




Re: Strange behaviour

Roland Christen
 

Hello Stephane,

You can easily determine if the encoders are causing this by simply disconnecting the encoder box from the CP4.
One question I have: Did this occur when you had the CP3 attached to your mount?

Finally, it will not do much good to ask this on the user group since it is a technical issue. It would be better if you directed an e-mail to Howard at AP. Email: howard@...

Howard will be able to link to your CP4 and check the parameter settings of your mount. probably a simple adjustment is all that is needed. Don't try to fix this by doing anything with the gear mesh or balance.

Rolando



-----Original Message-----
From: Stephane CHARBONNEL scharbonnel949@... [ap-gto]
To: ap-gto
Sent: Mon, Jul 3, 2017 4:47 am
Subject: [ap-gto] Strange behaviour



Hello,

I will try to explain my observation in english.
I use GTO CP4 on 3600GTO mount with RA / DEC Encoders turned at ON with APAE v2.0. This observation can be seen with or without APCC. So it is not an APCC problem.

In Fact, if my mount is very well balanced (current has about the same value towards East or West for a slew), I can observe big oscillations of my mount after a pointing, more and more effective towards +/-6 hour angle (where mount is mechanically well balanced). This is observed at x600 and effectively not at x12. So, at very low speed (little corrections) there is no problem and the contact is always exist. But at high speed, I think encoders on RA axis want to correct too fast just after a pointing so the correction is violent and the system enters in oscillations. When oscillations has begun, there is oscillations also on DEC axis.

I have found two manners to correct this :
* A strong imbalance but it is not a sustainable solution and the problem exists at hour angle around +/-6H.
* I remesh the worm gear (I found it is difficult for me ( ;-) because I don't know when I must stop pressure) and current has considerably increase and is very different following the direction even my well balanced mount (when I realize a slew, I have 1.3A towards West and 3.1A towards East). But at this moment, I haven't oscillations whatever the position of pointing.

So, I would like to know if I must keep a worm gear strongly remeshed as this or if you think it is because RA Encoders want to correct too fast just after pointing for my 3600GTO with encoders.

Regards
Stephane



Strange behaviour

Stephane Charbonnel
 

Hello,

I will try to explain my observation in english.
I use GTO CP4 on 3600GTO mount with RA / DEC Encoders turned at ON with APAE v2.0. This observation can be seen with or without APCC. So it is not an APCC problem.

In Fact, if my mount is very well balanced (current has about the same value towards East or West for a slew), I can observe big oscillations of my mount after a pointing, more and more effective towards +/-6 hour angle (where mount is mechanically well balanced). This is observed at x600 and effectively not at x12. So, at very low speed (little corrections) there is no problem and the contact is always exist. But at high speed, I think encoders on RA axis want to correct too fast just after a pointing so the correction is violent and the system enters in oscillations. When oscillations has begun, there is oscillations also on DEC axis.

I have found two manners to correct this :
* A strong imbalance but it is not a sustainable solution and the problem exists at hour angle around +/-6H.
* I remesh the worm gear (I found it is difficult for me ( ;-) because I don't know when I must stop pressure) and current has considerably increase and is very different following the direction even my well balanced mount (when I realize a slew, I have 1.3A towards West and 3.1A towards East). But at this moment, I haven't oscillations whatever the position of pointing.

So, I would like to know if I must keep a worm gear strongly remeshed as this or if you think it is because RA Encoders want to correct too fast just after pointing for my 3600GTO with encoders.

Regards
Stephane


Re: Upcoming solar eclipse

Chris Patrick
 

On 32,000 unpopulated ('cept for cattle and sheep) acres, with maybe 150 guests of the ranch! I'm (and a couple of others) bringing telescopes for outreach to the guests! Nyah, Nyah, Nyah! 😁


Re: Upcoming solar eclipse

Christopher Erickson
 

Victor, Idaho.  Just outside the main gate of Yellowstone.
 
Supposed to be one of the two most likely places along the eclipse path to be cloud free.  The other is Eastern Oregon.
 
 
-Christopher Erickson
Observatory engineer
Summit Kinetics
Waikoloa, HI 96738
www.summitkinetics.com
 



From: ap-gto@... [mailto:ap-gto@...]
Sent: Sunday, July 2, 2017 8:31 AM
To: ap-gto@...
Subject: [ap-gto] Upcoming solar eclipse

Where is the AP gang going to be for the eclipse?

 

Fred


Virus-free. www.avg.com


Upcoming solar eclipse

fl.lusen
 

Where is the AP gang going to be for the eclipse?

 

Fred


Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Worsel
 

Geof

No worries!

If I had a dollar for every time someone spelled Bryan the other way, I could buy a really big telescope. 8-)


Bryan


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

Sorry Bryan,

I keep spelling your name wrong... 😞

Regards,


Geof



Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Geof Lewis
 

Sorry Bryan,

I keep spelling your name wrong... 😞

Regards,


Geof


From: ap-gto@... <ap-gto@...> on behalf of Geof Lewis geoflewis@... [ap-gto] <ap-gto@...>
Sent: 02 July 2017 18:33
To: ap-gto@...
Subject: Re: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
 
 

Thanks Brian,

Of course my C14 is pre-owned with me being several generations along from it being new. I will be booking it in with a local optics specialist here in the UK whilst I'm over in the USA for the eclipse. Hopefully he can identify what is the problem and fix it for me.

Regards,


Geof


From: ap-gto@... <ap-gto@...> on behalf of bryancashion@... [ap-gto] <ap-gto@...>
Sent: 02 July 2017 18:17
To: ap-gto@...
Subject: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
 
 

Geof


"frequent loss of collimation on a meridian flip" is unusual and should not occur for reasonably high quality OTAs.  I'd suggest looking into why that is happening.

Possibilities

Collimation knobs too loose OR too tight OR both
Secondary mirror not fully tight in its holder
Looseness somewhere in optical train
???

Bryan


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

<snip>

My primary concern is (or at least was) the meridian flip process, which is not a problem when imaging with my 4"APO, but my C14 frequently loses collimation when I flip it, so I'm trying to avoid doing that; hence my original question about SGP maybe not working well with the AP V2 driver if I want to initiate a capture session with the C14 East pointing East. That's probably not such a huge deal as I can elect to start with it West pointing East (normal configuration), then track well past the meridian without risk of pier crashes. It just means that I'll maybe lose my west horizon a bit earlier as the scope falls below the walls of the observatory with the CWs very high towards the end of a capture sequence.

I'm going to download SGP and trial that in the Fall, but it's good to have alternatives, so thanks again for the recommendations.
Best regards,

Geof


Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Geof Lewis
 

Thanks Brian,

Of course my C14 is pre-owned with me being several generations along from it being new. I will be booking it in with a local optics specialist here in the UK whilst I'm over in the USA for the eclipse. Hopefully he can identify what is the problem and fix it for me.

Regards,


Geof


From: ap-gto@... on behalf of bryancashion@... [ap-gto]
Sent: 02 July 2017 18:17
To: ap-gto@...
Subject: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
 
 

Geof


"frequent loss of collimation on a meridian flip" is unusual and should not occur for reasonably high quality OTAs.  I'd suggest looking into why that is happening.

Possibilities

Collimation knobs too loose OR too tight OR both
Secondary mirror not fully tight in its holder
Looseness somewhere in optical train
???

Bryan


---In ap-gto@..., wrote :


My primary concern is (or at least was) the meridian flip process, which is not a problem when imaging with my 4"APO, but my C14 frequently loses collimation when I flip it, so I'm trying to avoid doing that; hence my original question about SGP maybe not working well with the AP V2 driver if I want to initiate a capture session with the C14 East pointing East. That's probably not such a huge deal as I can elect to start with it West pointing East (normal configuration), then track well past the meridian without risk of pier crashes. It just means that I'll maybe lose my west horizon a bit earlier as the scope falls below the walls of the observatory with the CWs very high towards the end of a capture sequence.

I'm going to download SGP and trial that in the Fall, but it's good to have alternatives, so thanks again for the recommendations.
Best regards,

Geof


Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Worsel
 

Geof

"frequent loss of collimation on a meridian flip" is unusual and should not occur for reasonably high quality OTAs.  I'd suggest looking into why that is happening.

Possibilities

Collimation knobs too loose OR too tight OR both
Secondary mirror not fully tight in its holder
Looseness somewhere in optical train
???

Bryan


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

<snip>

My primary concern is (or at least was) the meridian flip process, which is not a problem when imaging with my 4"APO, but my C14 frequently loses collimation when I flip it, so I'm trying to avoid doing that; hence my original question about SGP maybe not working well with the AP V2 driver if I want to initiate a capture session with the C14 East pointing East. That's probably not such a huge deal as I can elect to start with it West pointing East (normal configuration), then track well past the meridian without risk of pier crashes. It just means that I'll maybe lose my west horizon a bit earlier as the scope falls below the walls of the observatory with the CWs very high towards the end of a capture sequence.

I'm going to download SGP and trial that in the Fall, but it's good to have alternatives, so thanks again for the recommendations.
Best regards,

Geof


Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Geof Lewis
 

Hi Ray,
Good idea thanks, I'll do that. I really appreciate your help.
Regards,

Geof 


From: ap-gto@... on behalf of 'Ray Gralak (Groups)' groups3@... [ap-gto]
Sent: Sunday, July 2, 2017 4:49:50 PM
To: ap-gto@...
Subject: RE: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
 
 

Hi Geof,

I think that you'll find SGPro very capable for a product at its price point.

You might find it useful to join the Main Sequence forums in case you run into problems. A quick
search of the forum might give you an immediate answer to a question. Or, you can of course post
questions there if you can't find an answer:

http://forum.mainsequencesoftware.com/

Best regards,

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

> -----Original Message-----
> From: ap-gto@... [mailto:ap-gto@...]
> Sent: Sunday, July 2, 2017 8:42 AM
> To: ap-gto@...
> Subject: Re: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
>
>
>
> Thanks Charlie and everyone else that contributed to this thread, all of which has been helpful to
me.
> I have decided to download SGP (already done earlier today), so I'm now on the 45 day trail count
down. I
> decided that there was nothing better for it than trying it out and seeing what works and what
doesn't. Now I
> have to learn how to configure it so it's probably going to be a few weeks (maybe months) before
I'll have the
> answers to my questions, but I will post what I learn in due course, so anyone interested please
watch this
> space.
> Best regards,
>
> Geof
>
> _____________________________
> From: acf900gto@... [ap-gto]
> Sent: Sunday, July 2, 2017 4:20 pm
> Subject: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
> To:
>
>
>
>
> A lot of postings concerning SGP and meridian flips and some have provided incorrect or only
partial
> information. I have been using SGP with my AP1100GTO mount for more than two years. SGP is a
> remarkably capable imaging platform.
>
>
> When it comes to meridian flips, here's what happens. Firstly, SGP has the option to automate the
meridian
> flip or not. When the automatic meridian flip option is enabled it will perform a series of
actions.
>
> When the target crosses the meridian, SGP checks side-of-pier. If you started in a CW up
position, SGP will
> recognize that and not perform a meridian flip. If you started in the typical CW down position,
SGP will see
> that the side-of-pier is incorrect and issue a slew to the target coordinates with the assumption
that the
> ASCOM driver or mount controller will perform the flip.
>
> When the slew completes, SGP will perform one or more of the following tasks, depending on
options:
>
> 1. Rotate the camera 180 degrees;
> 2. Perform a plate solve (built-in plate solving with PlateSolve2);
> 3. Auto center the camera to the target coordinates to a high precision (for me, +/- 2 arc sec);
> 4. Select filter for the next sub
> 5. Auto focus (built-in auto focusing);
> 6. Resume auto guiding (PHD2)
> 7. Initiate next sub.
>
> Additionally, SGP can be told to "wait for meridian." This says "if the target will cross the
meridian during the
> next sub's exposure, defer the next sub until meridian passage and then perform a standard
meridian flip."
> So if you are shooting a 30 min NB sub, you could potentially track 29 minutes past the meridian.
If that
> would be a problem, enable wait for meridian.
>
> Charlie
>
>
>
>
>


Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Ray Gralak
 

Hi Geof,

I think that you'll find SGPro very capable for a product at its price point.

You might find it useful to join the Main Sequence forums in case you run into problems. A quick
search of the forum might give you an immediate answer to a question. Or, you can of course post
questions there if you can't find an answer:

http://forum.mainsequencesoftware.com/

Best regards,

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

-----Original Message-----
From: ap-gto@yahoogroups.com [mailto:ap-gto@yahoogroups.com]
Sent: Sunday, July 2, 2017 8:42 AM
To: ap-gto@yahoogroups.com
Subject: Re: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)



Thanks Charlie and everyone else that contributed to this thread, all of which has been helpful to
me.
I have decided to download SGP (already done earlier today), so I'm now on the 45 day trail count
down. I
decided that there was nothing better for it than trying it out and seeing what works and what
doesn't. Now I
have to learn how to configure it so it's probably going to be a few weeks (maybe months) before
I'll have the
answers to my questions, but I will post what I learn in due course, so anyone interested please
watch this
space.
Best regards,

Geof

Get Outlook for iOS <https://aka.ms/o0ukef> _____________________________
From: acf900gto@gmail.com <mailto:acf900gto@gmail.com> [ap-gto] <ap-gto@yahoogroups.com>
Sent: Sunday, July 2, 2017 4:20 pm
Subject: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
To: <ap-gto@yahoogroups.com>




A lot of postings concerning SGP and meridian flips and some have provided incorrect or only
partial
information. I have been using SGP with my AP1100GTO mount for more than two years. SGP is a
remarkably capable imaging platform.


When it comes to meridian flips, here's what happens. Firstly, SGP has the option to automate the
meridian
flip or not. When the automatic meridian flip option is enabled it will perform a series of
actions.

When the target crosses the meridian, SGP checks side-of-pier. If you started in a CW up
position, SGP will
recognize that and not perform a meridian flip. If you started in the typical CW down position,
SGP will see
that the side-of-pier is incorrect and issue a slew to the target coordinates with the assumption
that the
ASCOM driver or mount controller will perform the flip.

When the slew completes, SGP will perform one or more of the following tasks, depending on
options:

1. Rotate the camera 180 degrees;
2. Perform a plate solve (built-in plate solving with PlateSolve2);
3. Auto center the camera to the target coordinates to a high precision (for me, +/- 2 arc sec);
4. Select filter for the next sub
5. Auto focus (built-in auto focusing);
6. Resume auto guiding (PHD2)
7. Initiate next sub.

Additionally, SGP can be told to "wait for meridian." This says "if the target will cross the
meridian during the
next sub's exposure, defer the next sub until meridian passage and then perform a standard
meridian flip."
So if you are shooting a 30 min NB sub, you could potentially track 29 minutes past the meridian.
If that
would be a problem, enable wait for meridian.

Charlie





Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

Geof Lewis
 

Thanks Charlie and everyone else that contributed to this thread, all of which has been helpful to me.
I have decided to download SGP (already done earlier today), so I'm now on the 45 day trail count down. I decided that there was nothing better for it than trying it out and seeing what works and what doesn't. Now I have to learn how to configure it so it's probably going to be a few weeks (maybe months) before I'll have the answers to my questions, but I will post what I learn in due course, so anyone interested please watch this space.
Best regards,

Geof

_____________________________

From: acf900gto@... [ap-gto] <ap-gto@...>
Sent: Sunday, July 2, 2017 4:20 pm
Subject: [ap-gto] Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)
To: <ap-gto@...>


 

A lot of postings concerning SGP and meridian flips and some have provided incorrect or only partial information.  I have been using SGP with my AP1100GTO mount for more than two years.  SGP is a remarkably capable imaging platform.


When it comes to meridian flips, here's what happens.  Firstly, SGP has the option to automate the meridian flip or not.  When the automatic meridian flip option is enabled it will perform a series of actions.

When the target crosses the meridian, SGP checks side-of-pier.  If you started in a CW up position, SGP will recognize that and not perform a meridian flip.  If you started in the typical CW down position, SGP will see that the side-of-pier is incorrect and issue a slew to the target coordinates with the assumption that the ASCOM driver or mount controller will perform the flip.

When the slew completes, SGP will perform one or more of the following tasks, depending on options:

1.  Rotate the camera 180 degrees;
2.  Perform a plate solve (built-in plate solving with PlateSolve2);
3.  Auto center the camera to the target coordinates to a high precision (for me, +/- 2 arc sec);
4.  Select filter for the next sub
5.  Auto focus (built-in auto focusing);
6.  Resume auto guiding (PHD2)
7.  Initiate next sub.

Additionally, SGP can be told to "wait for meridian."  This says "if the target will cross the meridian during the next sub's exposure, defer the next sub until meridian passage and then perform a standard meridian flip."  So if you are shooting a 30 min NB sub, you could potentially track 29 minutes past the meridian.  If that would be a problem, enable wait for meridian.

Charlie




Re: APCC, AP V2 ASCOM driver, SGP, AP1200 GTOCP3 (M-chip)

acf900gto@...
 

A lot of postings concerning SGP and meridian flips and some have provided incorrect or only partial information.  I have been using SGP with my AP1100GTO mount for more than two years.  SGP is a remarkably capable imaging platform.

When it comes to meridian flips, here's what happens.  Firstly, SGP has the option to automate the meridian flip or not.  When the automatic meridian flip option is enabled it will perform a series of actions.

When the target crosses the meridian, SGP checks side-of-pier.  If you started in a CW up position, SGP will recognize that and not perform a meridian flip.  If you started in the typical CW down position, SGP will see that the side-of-pier is incorrect and issue a slew to the target coordinates with the assumption that the ASCOM driver or mount controller will perform the flip.

When the slew completes, SGP will perform one or more of the following tasks, depending on options:

1.  Rotate the camera 180 degrees;
2.  Perform a plate solve (built-in plate solving with PlateSolve2);
3.  Auto center the camera to the target coordinates to a high precision (for me, +/- 2 arc sec);
4.  Select filter for the next sub
5.  Auto focus (built-in auto focusing);
6.  Resume auto guiding (PHD2)
7.  Initiate next sub.

Additionally, SGP can be told to "wait for meridian."  This says "if the target will cross the meridian during the next sub's exposure, defer the next sub until meridian passage and then perform a standard meridian flip."  So if you are shooting a 30 min NB sub, you could potentially track 29 minutes past the meridian.  If that would be a problem, enable wait for meridian.

Charlie