Date   

Re: GTO CP3 connection problem via COM port in Windows 10

Ray Gralak
 

Besides the philosophical discussion here -- which I agree with, these folks are right that Voyager needs to run as
admin per the developer. The licensing portion of the software and the integrated Web Dashboard UI have
requirements on that, and a few others.
I suspected that. The developer has chosen a licensing scheme that requires administrative access. It is nothing to do with
communication to astronomy equipment. Running a web UI/API does not require administrative rights either. This sounds like
some poor design decisions.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, March 14, 2020 7:19 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

Besides the philosophical discussion here -- which I agree with, these folks are right that Voyager needs to run as
admin per the developer. The licensing portion of the software and the integrated Web Dashboard UI have
requirements on that, and a few others.

Lets not derail the discussion though. It needs to run this way, and if everything else one needs runs as Admin it
will work just fine. I have imaged for hundreds of hours with AP mounts, APCC, PHD2, SkyX, and Voyager all
running as admin.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, March 14, 2020 7:13 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.
Other ASCOM applications don't need to be run as administrator, and in fact should not need to be run as
administrator. The only exception is that sometimes an application needs to run *once* as administrator to
complete registration.

So what requires Voyager have to run as administrator? Certainly if it is just talking to an AP mount it does not
need to run as administrator. Cameras neither, because other applications (e.g. SGPro and SkyX) do not need to
run as administrator that access cameras, filter wheels, domes, weather stations, plate solvers, etc.

-Ray Gralak
Author of APCC (Astro-Physics Command Center):
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0 <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaa
aa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMC
Il7HM%3D&amp;reserved=0>
Author of PEMPro V3:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01%7
C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C6371983
51972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&;data=02%7C01%
7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198
351972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%
3D&amp;reserved=0
<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&
;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%
3D&amp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Nagy
Sent: Saturday, March 14, 2020 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.

I suggest Henry create a new thread at Voyager forum. There was a similar issue reported at Voyager forum and
this is one example and hopefully this will fix it for you:

https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum.starkeeper.it%2Ft%2Fnew-problem-
connecting-to-mach1gto-since-upgrading-windows-7-to-windows-
&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198351972854681&amp;sdata=23mG1p9rVQFG72aCFvHrPA2FHCrrfjThsc5k8SvppdQ%3D
&amp;reserved=0
<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum.starkeeper.it%2Ft%2Fnew-problem-
connecting-to-mach1gto-since-upgrading-windows-7-to-windows-
&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637198351972854681&amp;sdata=23mG1p9rVQFG72aCFvHrPA2FHCrrfjThsc5k8SvppdQ%3D
&amp;reserved=0>
10/1162/8

Scroll down to about 9/13 as shown at right side. Here is one of the snippet:

"A Teamviewer session with Leo has fixed all the problems! I am very grateful. For posterity, the problem with the
web server is to do with the port. For some reason on my PC the port I need to use is 8081, not the default 80.
Leo
figured out the problem so its all working fine now!"

Read the whole thread.

Peter





Re: GTO CP3 connection problem via COM port in Windows 10

Bill Long
 

Besides the philosophical discussion here -- which I agree with, these folks are right that Voyager needs to run as admin per the developer. The licensing portion of the software and the integrated Web Dashboard UI have requirements on that, and a few others. 

Lets not derail the discussion though. It needs to run this way, and if everything else one needs runs as Admin it will work just fine. I have imaged for hundreds of hours with AP mounts, APCC, PHD2, SkyX, and Voyager all running as admin. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, March 14, 2020 7:13 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
 
> There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
> ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.

Other ASCOM applications don't need to be run as administrator, and in fact should not need to be run as administrator. The only exception is that sometimes an application needs to run *once* as administrator to complete registration.

So what requires Voyager have to run as administrator? Certainly if it is just talking to an AP mount it does not need to run as administrator. Cameras neither, because other applications (e.g. SGPro and SkyX) do not need to run as administrator that access cameras, filter wheels, domes, weather stations, plate solvers, etc.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=LJ%2FPZ1VVuCJVXgGUumw2B3PxVRvP47TwEzHEMCIl7HM%3D&amp;reserved=0
Author of PEMPro V3:  https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ccdware.com&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=eEW7dcRsi8kNcrtHscBpIqPekW1%2FdsA3RpG1rmuri10%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=T7o1GhnqdxuDxtrWKhFp%2F4Tl6gC6%2BGtoep%2FOI3HzTx0%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Nagy
> Sent: Saturday, March 14, 2020 6:00 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
>
> There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
> ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.
>
> I suggest Henry create a new thread at Voyager forum. There was a similar issue reported at Voyager forum and
> this is one example and hopefully this will fix it for you:
>
> https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fforum.starkeeper.it%2Ft%2Fnew-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-&amp;data=02%7C01%7C%7C4754c20f8ce84ef9e50c08d7c8866c5a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637198351972854681&amp;sdata=23mG1p9rVQFG72aCFvHrPA2FHCrrfjThsc5k8SvppdQ%3D&amp;reserved=0
> 10/1162/8
>
> Scroll down to about 9/13 as shown at right side. Here is one of the snippet:
>
> "A Teamviewer session with Leo has fixed all the problems! I am very grateful. For posterity, the problem with the
> web server is to do with the port. For some reason on my PC the port I need to use is 8081, not the default 80. Leo
> figured out the problem so its all working fine now!"
>
> Read the whole thread.
>
> Peter
>





Re: GTO CP3 connection problem via COM port in Windows 10

Ray Gralak
 

Henry,

Did you try my instructions?

This is a not a problem with the mount or AP software. This has to do with the COM port connection to the mount. Are you using a USB/serial converter?

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Henry Kwok
Sent: Saturday, March 14, 2020 6:48 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the
problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of
Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt
after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts.
Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up
something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator
mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here
rather than on the Voyager forum.

Cheers

Henry


Re: GTO CP3 connection problem via COM port in Windows 10

Ray Gralak
 

There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.
Other ASCOM applications don't need to be run as administrator, and in fact should not need to be run as administrator. The only exception is that sometimes an application needs to run *once* as administrator to complete registration.

So what requires Voyager have to run as administrator? Certainly if it is just talking to an AP mount it does not need to run as administrator. Cameras neither, because other applications (e.g. SGPro and SkyX) do not need to run as administrator that access cameras, filter wheels, domes, weather stations, plate solvers, etc.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Peter Nagy
Sent: Saturday, March 14, 2020 6:00 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2
ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.

I suggest Henry create a new thread at Voyager forum. There was a similar issue reported at Voyager forum and
this is one example and hopefully this will fix it for you:

https://forum.starkeeper.it/t/new-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-
10/1162/8

Scroll down to about 9/13 as shown at right side. Here is one of the snippet:

"A Teamviewer session with Leo has fixed all the problems! I am very grateful. For posterity, the problem with the
web server is to do with the port. For some reason on my PC the port I need to use is 8081, not the default 80. Leo
figured out the problem so its all working fine now!"

Read the whole thread.

Peter


Re: GTO CP3 connection problem via COM port in Windows 10

Bill Long
 

I recently bought a used Mach 1 with CP3 V2, and I cannot reproduce this issue on Windows 10. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Henry Kwok <henry.ck.kwok@...>
Sent: Saturday, March 14, 2020 6:48 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] GTO CP3 connection problem via COM port in Windows 10
 
Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts. Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here rather than on the Voyager forum. 

Cheers

Henry


Re: GTO CP3 connection problem via COM port in Windows 10

Henry Kwok
 

Hi Ray and Peter,

Voyager must run in administrator mode.

The person on the Voyager forum is me. Leo has fixed most of the problem for me. As it turns out, most of the problem was due to the upgrade process from Windows 7 to Windows 10. I have since done a clean install of Windows 10, and after Leo tweaked the settings everything is working 99% of the time now.

The only exception is the problem I described above i.e. the driver will not connect to the mount on the first attempt after a reboot, but will connect subsequently without changing any settings between the 1st and 2nd attempts. Therefore I know it has nothin to do with COM port selection. It is almost as if it needs one attempt to wake up something (hardware or software I am not sure).

The problem does not appear limited to Voyager as it will also happen with APJog (which I set to administrator mode) as well, therefore I think it is a problem with hardware-driver interaction and I have elected to post here rather than on the Voyager forum. 

Cheers

Henry


Re: GTO CP3 connection problem via COM port in Windows 10

Peter Nagy
 

There are good number of people I know of uses Voyager running as admin with A-P mounts and A-P V2 ASCOM driver without issues like myself. Developer of Voyager said that Voyager must run as admin.

I suggest Henry create a new thread at Voyager forum. There was a similar issue reported at Voyager forum and this is one example and hopefully this will fix it for you:

https://forum.starkeeper.it/t/new-problem-connecting-to-mach1gto-since-upgrading-windows-7-to-windows-10/1162/8

Scroll down to about 9/13 as shown at right side. Here is one of the snippet:

"A Teamviewer session with Leo has fixed all the problems! I am very grateful. For posterity, the problem with the web server is to do with the port. For some reason on my PC the port I need to use is 8081, not the default 80. Leo figured out the problem so its all working fine now!"

Read the whole thread.

Peter


Re: Keypad Upgrade for Using Mach2

Robert Berta
 
Edited

Terri Zittritsch You can run Sky Safari on Windows 10 platform.....I do. You have to first install a free program called XePlayer which creates an Android partition on your computer. After that you can run any Android app from your Windows platform. You need to install the PlayStore and any of your favorite Android aps also including an Android file reader so you can see the files you save, etc. The files you install are in the Android partition so can't be seen or read with a regular Windows file reader. I have Sky Safari Pro latest version and I connect to my AP 900 and AP 1100 mounts for control of the telescope mounts from SS. I also use it with a Celestron fork mount and an Ioptron MiniTower Pro for field use and public outreach. I have both a CP3 for the 900 and CP4 for the 1100.  Astro Physics still hasn't quite figured out the wireless on the CP4 (it suffers from drop outs) but with a SkyFi I can wirelessly control the mounts from my Windows 10 computer as well as a Samsung tablet and Samsung cell phone.  The latest SkyFi units are very robust and can be used a long way from the mount. The only thing missing on Sky Safari is that you can only park and unpark from Park 4....Sky Safari knows about that and plans to offer more park positions in the future. Not a big deal though.....I initialize with the hand control and than connect with Sky Safari.  I park in position 3 and restore from that due to the setup in my observing setup so don't use park 4.


Re: GTO CP3 connection problem via COM port in Windows 10

Ray Gralak
 

Hi Henry,

Before connecting the driver open Windows Device Manager and find the COM port(s) that are present on your system. Then open the AP V2 Driver ASCOM Setup. The driver does not automatically discover which port the mount is using so you must select the proper COM port. Select each port and click "Check Port" until you locate the port. Then close the window. The driver should now connect

Also, do not run Voyager or any other ASCOM client as administrator. It should not be required to run any ASCOM client applications as administrator as that may cause a second instance of the driver to start if you also have another application connected.

If you still have problems with take notice of the COM port the driver is trying to connect with to make sure it matches the COM port the mount is connected to. If you are using a USB/serial converter sometimes they try to allocate a new COM port every time they run or after booting. If you have one that does that then try updating its device driver. If that doesn't help try a different USB/serial converter, or if you have a desktop get a serial port add in card.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of PEMPro V3: https://www.ccdware.com
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Henry Kwok
Sent: Saturday, March 14, 2020 12:51 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] GTO CP3 connection problem via COM port in Windows 10

Hi Ray (or anyone else who can help):

Since I have upgraded to Windows 10 (from Windows 7) I have a problem connecting to the mount via COM port
using ASCOM.
Basically the first attempt at connecting to the mount after a fresh boot up of the machine will always fail.
However, if I try again the second time it will work.

For example, I normally start APJog, then click connect. It will launch the mount ASCOM driver window, but it will
fail to detect the mount.
To solve the problem I will have to click connect again (which does nothing), then click disconnect (so to close the
mount driver window), then click connect again and then everything will work fine from there.

I have also tried to connect to the mount from Voyager - and I see the same problem (i.e. first attempt at connecting
to the mount after a fresh boot will fail).

This is a fatal issue, but more a nuisance.

I have noticed this problem since upgrading to Windows 10. Windows device manager does not report any error.

BTW, Voyager always run in administrator mode. I have set APJog to run as administrator as well, because if I
don't and try to run Voyager after APJog the mount will not connect.

Is there some setting I am missing?

Thanks


Re: Mach2

Terri Zittritsch
 

Hi Jerome, I like it very much.  Very solid.   I also purchased spikes for the feet as I wasn't sure how the swiveling foot pads will work.     Given I purchased the center extension, I probably didn't need the extendable legs.   Everything fits together nicely.  Comes with a nice case.


More AP900 Goodness - Caroline's Rose

Dean Jacobsen
 

I'm still restoring my Astrobin gallery after the loss of everyone's pictures.  Sometimes I find an old image that I think I can do better on now.

This is NGC 7789 aka Caroline's Rose from September 2018 with the FSQ-106 at f/5. 

https://www.astrobin.com/full/365581/C/

The low resolution images don't do this open cluster justice so this one has been posted as a 100% resolution image.  Click on the "Full resolution" button in the upper right corner.

I love the smattering of red giants in this one.

Equipment and exposure details are listed on the "Technical card" page.
--
Dean Jacobsen
http://astrophoto.net/wp/ 
Image Gallery - http://astrophoto.net/wp/image-gallery/
Astrobin - https://www.astrobin.com/users/deanjacobsen/ 


GTO CP3 connection problem via COM port in Windows 10

Henry Kwok
 

Hi Ray (or anyone else who can help):

Since I have upgraded to Windows 10 (from Windows 7) I have a problem connecting to the mount via COM port using ASCOM.
Basically the first attempt at connecting to the mount after a fresh boot up of the machine will always fail.
However, if I try again the second time it will work.

For example, I normally start APJog, then click connect. It will launch the mount ASCOM driver window, but it will fail to detect the mount.
To solve the problem I will have to click connect again (which does nothing), then click disconnect (so to close the mount driver window), then click connect again and then everything will work fine from there.

I have also tried to connect to the mount from Voyager - and I see the same problem (i.e. first attempt at connecting to the mount after a fresh boot will fail).

This is a fatal issue, but more a nuisance.

I have noticed this problem since upgrading to Windows 10. Windows device manager does not report any error.

BTW, Voyager always run in administrator mode. I have set APJog to run as administrator as well, because if I don't and try to run Voyager after APJog the mount will not connect.

Is there some setting I am missing?

Thanks


Re: Mach2

 

Nice!  I'm really looking forward to getting mine.  
Is that a T-Pod 130 tripod?  I've been thinking of eventually getting a 110.  How do you like it?  
Jerome


Re: Mach2

Cheng-Yang Tan
 

Very nice! My colleague received his as well. I’m sure I’ll get to see it in person very soon.

On Saturday, March 14, 2020, 12:59 PM, Harley Davidson <astrocnc@...> wrote:

Very nice!!!

tony

On 3/14/2020 1:08 PM, Terri Zittritsch wrote:


Re: Mach2

Harley Davidson
 

Very nice!!!

tony

On 3/14/2020 1:08 PM, Terri Zittritsch wrote:

I’ve gotten several personal messages asking me to post pictures.   Here you go:
https://drive.google.com/file/d/1yldIol7IwBtdcCPXYaQDLo21BOGmGIq1/view?usp=drivesdk

https://drive.google.com/file/d/15911KnglxkSsxn_Bguba9E1VCbesTxhd/view?usp=drivesdk

T



Re: Keypad Upgrade for Using Mach2

Wayne Hixson
 

A question I have is exactly where model corrections for guiding and pointing are applied? In the software or in the GTOCP5 itself?

Wayne


On Mar 14, 2020, at 9:43 AM, Dominique Durand via Groups.Io <dom33.durand@...> wrote:

Terri, And yes, almost everything can work together, current users make it a permanent experience and I am sure that the Mach2 encoder system makes this even more secure. It's good to already have the Mach2 manual ... I would like to already have this version even if it may not be the final one.Good continuation in your discovery of the extended possibilities of Mach2 and APCC-Pro.


Mach2

Terri Zittritsch
 


Re: Keypad Upgrade for Using Mach2

Dominique Durand
 

Terri, And yes, almost everything can work together, current users make it a permanent experience and I am sure that the Mach2 encoder system makes this even more secure. It's good to already have the Mach2 manual ... I would like to already have this version even if it may not be the final one.Good continuation in your discovery of the extended possibilities of Mach2 and APCC-Pro.


Re: Keypad Upgrade for Using Mach2

Terri Zittritsch
 
Edited

Dean, For new A-P mount owners/users like me it would be interesting to understand your flow, using the keypad plus software and why.   I've only just recently understood that the keypad/hand controller can co-exist with a computer on the GTOCP5 controller.      I've also giddily found that I might be able to use sky safari along with APCC even though Sky Safari isn't on the windows platform.
  
I've finished consuming the APCC-Pro, Mach-5, V2 manuals (The apcc-pro is a beast) and have started things like horizon and meridian modeling (things I can do without clear skies).       I'll have a hand controller, and use SGPro and well as one of my planetarium programs.. (sky safari is my favorite).    I currently use SGPro for all image sequencing, target centering and focusing and phd2 for guiding.

T


Re: Dumb(?) question re start-up of my AP900GTO CP4

Charles Thompson
 

George is fantastic!



Thanks,
Charles

Sent from mobile device.


-------- Original message --------
From: Stuart <stuart.j.heggie@...>
Date: 3/13/20 2:54 PM (GMT-06:00)
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Dumb(?) question re start-up of my AP900GTO CP4

Success!!! First of all, MAJOR shout-out to George for walking me through a HUGE number of things that sped me down the learning curve. 

Turns out I had the time off by 12 hours as in 2:26:30 vs. 14:26:30 (so also confirmed the "dumb" part of my situation). 

BUT, George gave me a crash course in APCC Pro that really boosted my  confidence there and readiness for a night out with the new scope and mount. Yah!


On Fri, 13 Mar 2020 at 12:05, Stuart via Groups.Io <stuart.j.heggie=gmail.com@groups.io> wrote:
Don, I don't think there is a N/S switch on the CP4.


On Thu, 12 Mar 2020 at 22:23, Don Anderson via Groups.Io <jockey_ca=yahoo.ca@groups.io> wrote:
Stuart
Any chance the N/S switch got bumped to the wrong position?

Don Anderson


On Thursday, March 12, 2020, 03:03:19 p.m. MDT, uncarollo2 <chris1011@...> wrote:


Testing Park3 is definitely a good idea. For any new startups I generally run the mount thru all park positions before going to any object.
 
If Venus coordinates are correct, then something else is wrong. Probably not battery or database. I suggest getting in touch with George at AP and having him advise some other tests. You could very easily have one of your settings of time, date, location wrong, something that isn't obvious to you but may be to a second person. It's happened to me when I had the clock set to 3 o-clock, forgetting that it should have been 15:00 hours.
 
Rolando
 
 
-----Original Message-----
From: Christopher Erickson <christopher.k.erickson@...>
To: main <main@ap-gto.groups.io>
Sent: Thu, Mar 12, 2020 10:50 am
Subject: Re: [ap-gto] Dumb(?) question re start-up of my AP900GTO CP4

I would still perform the easy test of sending it to park 3 to see what happens.


-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Thu, Mar 12, 2020, 10:38 AM Stuart <stuart.j.heggie@...> wrote:
Okay - have confirmed that I have the right Lat/Long and the keypad has the right values for , say, Venus but claims it is below the horizon when I issue the slew command via the keypad. That's after confirming it is in Park 4 and knows it is in Park 4. 

So ... new battery (I have one in hand that I ordered, worried about this happening) and reload the db?


On Thu, 12 Mar 2020 at 15:03, Stuart Heggie <stuart.j.heggie@...> wrote:
Thanks Rolando. I will check that too. Just got home. 

Stuart

On Thu, Mar 12, 2020 at 3:01 PM uncarollo2 <chris1011@...> via Groups.Io <chris1011=aol.com@groups.io> wrote:
bring up an object but before sending it there press the < button to see the object data. If it looks wrong, it could be that your keypad battery has died and you will need to re-load the database plus put in a new battery.
 
Rolando
 
 
-----Original Message-----
From: Stuart <stuart.j.heggie@...>
To: main <main@ap-gto.groups.io>
Sent: Thu, Mar 12, 2020 7:40 am
Subject: Re: [ap-gto] Dumb(?) question re start-up of my AP900GTO CP4

Interesting possibility. I woke up in the night thinking that very thing but confirmed this morning that I'm indeed using Park 4. (I started using Park 1 with tracking off with the same result and then switched to Park 4).


On Thu, 12 Mar 2020 at 13:06, Christopher Erickson <christopher.k.erickson@...> wrote:
Try sending it to Park 3 and see where it goes. Maybe you have misremembered Park 4...


-Christopher Erickson
Observatory engineer
Waikoloa, HI 96738
www.summitkinetics.com
   

On Thu, Mar 12, 2020, 6:25 AM Stuart <stuart.j.heggie@...> wrote:
All - my AP900GTO CP4 has been idle for over a year and with power OFF. I am putting it back into operation and am having a weird time getting the scope to find targets (like at all).
  • When I power up, the hand controller signals that I am set to EXT and to hit MENU to use the hand controller. I do that.
  • Then it prompts for my Location (I only have one): I select '1' and GOTO
  • I checked the Lat/Long and it is my home location. I adjusted it very slightly as the mount is in a slightly different location than it was).
  • I checked the Time and Date and they were off by a few days (odd?) - I corrected them both.
  • At this point, I loosen both clutches fully, signal I want the mount to go to Park 4 and hold the mount while it whirs away and when it is done, I use a bubble level to position it in Park 4. I tighten the clutches gently, issue a second Park 4 command, check the level then lock in down firmly (hand tightening only of course)
THEN the weird part: I hit menu till I'm at the top menu, I select Object then pick some object I know is up in the sky (I'm in a dome shielded from any risk of pointing at the sun and the scope is covered anyway). Let's pick Venus for example (tho it failed on the moon when the moon was up also). In most cases the hand controller declares the object I can see naked eye (Venus, the Moon, Betelgeuse, ...) is below the horizon. Or it slews and slews way off the target.

Is it possible my hand controller db is corrupted from the long time powered down? 

--

Stuart
http://www.astrofoto.ca/stuartheggie/

--

Stuart
http://www.astrofoto.ca/stuartheggie/
--

--

Stuart
http://www.astrofoto.ca/stuartheggie/


--

Stuart
http://www.astrofoto.ca/stuartheggie/


--

Stuart
http://www.astrofoto.ca/stuartheggie/

12061 - 12080 of 81039