Date   

C11HD on Mach2 #Mach2GTO

Dominique Durand
 
Edited

Hi,
Here is a little feedback on the use of my Mach2.
The modeling goes pretty well with SGP / Platesolve2.
After photoshoots with the AP130GT, I switched to the C11HD with still use without autoguiding. With 1960 focal length with the reducer or 2800 focal length without the reducer, the quality of monitoring must be up to par.
Here are 2 clusters M13 and M92 made with exposures of 60 seconds and a galaxy NGC6384 made with exposures of 180 seconds.
The problems to be solved are more at the level of C11 than Mach2.
M13
https://astrob.in/full/h1sgqo/0/

M92
https://astrob.in/full/vfeboh/0/

NGC6384
https://astrob.in/full/5c5wt2/G/

Happy amateur astronut
Dominique


Re: Comet NEOWISE (C/2020 F3)

Ray Gralak
 

Hi Chanan,

Sorry but the AP V2 ASCOM driver only supports tracking rates for GTOCP3 control boxes with Rev S or later firmware.

You might try downloading my PulseGuide program from http://www.pulseguide.com.

-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 chanan2009@gmail.com
Sent: Saturday, July 18, 2020 11:27 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Comet NEOWISE (C/2020 F3)

Hi All,

I just got an AP900 GTOCP2 from a friend. I used this mount 10 years ago and have forgotten a few of the
basics. I was looking to track Comet Neowise and completely forgot how to figure out what Custom RA and Dec
information to enter into the AP V2 ASCOM Driver window. I did visit the JPL Horizons website and downloaded
the data but was not sure which data to use.

Hope someone will help me figure it out. I did once, for the life of me cannot remember what I did.

Clear skies,
Chanan


Re: Comet NEOWISE (C/2020 F3)

Chanan Greenberg
 

It is an AP900 connected via the AP V2 ASCOM Driver - it is not APCC standard or pro download from the AP website


On Sun, Jul 19, 2020 at 6:52 PM Worsel via groups.io <bryancashion=yahoo.com@groups.io> wrote:
Chanan

Do you have APCC Standard or Pro?  If you do, the included Horizons program will extract the JPL data and set up the mount for you.

Demos at https://www.astro-physics.info/index.htm?tech_support/software/apcc/apcc-download

See section 13 in Standard or Section 14 in Section in Pro

If you do not have APCC, then I am sure Ray can provide insight on how to use the Custom tracking rates.



Bryan


Re: Comet NEOWISE (C/2020 F3)

Worsel
 

Chanan

Do you have APCC Standard or Pro?  If you do, the included Horizons program will extract the JPL data and set up the mount for you.

Demos at https://www.astro-physics.info/index.htm?tech_support/software/apcc/apcc-download

See section 13 in Standard or Section 14 in Section in Pro

If you do not have APCC, then I am sure Ray can provide insight on how to use the Custom tracking rates.



Bryan


Re: Comet NEOWISE (C/2020 F3)

Chanan Greenberg
 

This is a sample of the data I get from JPL
There is RA ICRF / Apparent RA and dRA*COS D  - I know there is an interface to newer versions that converts all this automatically via an interface. But i do not have that. Can someone help me figure out the custom RA and DA rate or at least how to calculate them?

*******************************************************************************
JPL/HORIZONS                 NEOWISE (C/2020 F3)           2020-Jul-19 17:55:59
Rec #:90004465 (+COV) Soln.date: 2020-Jul-18_14:19:12     # obs: 372 (113 days)
 
IAU76/J2000 helio. ecliptic osc. elements (au, days, deg., period=Julian yrs):
 
  EPOCH=  2459064.5 ! 2020-Aug-03.0000000 (TDB)    RMSW= n.a.
   EC= .9991691234351144   QR= .2946512233784272   TP= 2459034.1790709617
   OM= 61.00939569131192   W= 37.27847625028863    IN= 128.9374034572737
   A= 354.6269516206773    MA= .004474958062287851 ADIST= 708.9592520179763
   PER= 6678.2984358648    N= .000147586           ANGMOM= .013202626
   DAN= .32816             DDN= 2.87401            L= 35.4432405
   B= 28.1073672           MOID= .36253801         TP= 2020-Jul-03.6790709617
 
Comet physical (GM= km^3/s^2; RAD= km):
   GM= n.a.                RAD= n.a.
   M1=  10.7     M2=  14.9     k1=  17.75  k2=  5.      PHCOF=  .030
 
COMET comments 
1: soln ref.= JPL#14, data arc: 2020-03-27 to 2020-07-18
2: k1=17.75, k2=5., phase coef.=0.03;
*******************************************************************************
 
 
*******************************************************************************
Ephemeris / WWW_USER Sun Jul 19 17:55:59 2020 Pasadena, USA      / Horizons
*******************************************************************************
Target body name: NEOWISE (C/2020 F3)             {source: JPL#14}
Center body name: Earth (399)                     {source: DE431}
Center-site name: (user defined site below)
*******************************************************************************
Start time      : A.D. 2020-Jul-19 00:00:00.0000 UT
Stop  time      : A.D. 2020-Aug-19 00:00:00.0000 UT
Step-size       : 1 minutes
*******************************************************************************
Target pole/equ : No model available
Target radii    : (unavailable)                                           
Center geodetic : 238.110000,37.3378000,0.0000000 {E-lon(deg),Lat(deg),Alt(km)}
Center cylindric: 238.110000,5077.34335,3847.2668 {E-lon(deg),Dxy(km),Dz(km)}
Center pole/equ : High-precision EOP model        {East-longitude positive}
Center radii    : 6378.1 x 6378.1 x 6356.8 km     {Equator, meridian, pole}
Target primary  : Sun
Vis. interferer : MOON (R_eq= 1737.400) km        {source: DE431}
Rel. light bend : Sun, EARTH                      {source: DE431}
Rel. lght bnd GM: 1.3271E+11, 3.9860E+05 km^3/s^2                         
Small-body perts: Yes                             {source: SB431-N16}
Atmos refraction: NO (AIRLESS)
RA format       : HMS
Time format     : CAL 
RTS-only print  : NO       
EOP file        : eop.200717.p201008                                           
EOP coverage    : DATA-BASED 1962-JAN-20 TO 2020-JUL-17. PREDICTS-> 2020-OCT-07
Units conversion: 1 au= 149597870.700 km, c= 299792.458 km/s, 1 day= 86400.0 s 
Table cut-offs 1: Elevation (-90.0deg=NO ),Airmass (>38.000=NO), Daylight (NO )
Table cut-offs 2: Solar elongation (  0.0,180.0=NO ),Local Hour Angle( 0.0=NO )
Table cut-offs 3: RA/DEC angular rate (     0.0=NO )                           
*******************************************************************************
Initial IAU76/J2000 heliocentric ecliptic osculating elements (au, days, deg.):
  EPOCH=  2459064.5 ! 2020-Aug-03.0000000 (TDB)    RMSW= n.a.         
   EC= .9991691234351144   QR= .2946512233784272   TP= 2459034.1790709617
   OM= 61.00939569131192   W= 37.27847625028863    IN= 128.9374034572737       
  Equivalent ICRF heliocentric equatorial cartesian coordinates (au, au/d):
   X=-8.321621038925854E-02  Y=-8.646020467729936E-01  Z= 3.618176019624061E-02
  VX=-1.306354356457230E-02 VY=-2.045458056181457E-02 VZ=-9.533388646221023E-03
Comet physical (GM= km^3/s^2; RAD= km):                               
   GM= n.a.                RAD= n.a.                                           
   M1=  10.7     M2=  14.9     k1=  17.75  k2=  5.      PHCOF=  .030           
************************************************************************************************************************************
 Date__(UT)__HR:MN     R.A._____(ICRF)_____DEC R.A.__(a-apparent)__DEC dRA*cosD d(DEC)/dt L_Ap_Sid_Time            delta      deldot
************************************************************************************************************************************
$$SOE
 2020-Jul-19 00:00 *m  09 01 50.18 +48 07 02.9 09 03 11.57 +48 02 20.9 543.8484  -35.6628 11 41 25.4736 0.71619678171961 -20.7392241
 2020-Jul-19 00:01 *m  09 01 51.08 +48 07 02.3 09 03 12.48 +48 02 20.3 543.8628  -35.7024 11 42 25.6378 0.71618846394532 -20.7348636
 2020-Jul-19 00:02 *m  09 01 51.99 +48 07 01.7 09 03 13.38 +48 02 19.7 543.8771  -35.7421 11 43 25.8021 0.71618014791953 -20.7305061


Re: ASCOM 6.5 released, upgrade or not?

Cheng-Yang Tan
 

Hi Ray,
   Thanks for the warning. I'll wait until you confirm it's good to do so.

Thanks!

cytan

On Sunday, July 19, 2020, 08:11:26 PM CDT, Ray Gralak <groups3@...> wrote:


Confirmed. Do not update to ASCOM platform 6.5 yet.

-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 Ray Gralak
> Sent: Sunday, July 19, 2020 2:32 PM
> Subject: Re: [ap-gto] ASCOM 6.5 released, upgrade or not?
>
> >    ASCOM 6.5 is released. Should I upgrade or wait?
>
> Wait for now. I'm looking into it now. The downloaded file is not digitally signed which is a big red flag.
>
> -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 Cheng-Yang Tan via groups.io
> > Sent: Saturday, July 18, 2020 8:44 PM
> > Subject: [ap-gto] ASCOM 6.5 released, upgrade or not?
> >
> > Hi guys,
> >    ASCOM 6.5 is released. Should I upgrade or wait?
> >
> >
> > cytan
> >
>
>
>





Re: ASCOM 6.5 released, upgrade or not?

Ray Gralak
 

Confirmed. Do not update to ASCOM platform 6.5 yet.

-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 Ray Gralak
Sent: Sunday, July 19, 2020 2:32 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] ASCOM 6.5 released, upgrade or not?

ASCOM 6.5 is released. Should I upgrade or wait?
Wait for now. I'm looking into it now. The downloaded file is not digitally signed which is a big red flag.

-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 Cheng-Yang Tan via groups.io
Sent: Saturday, July 18, 2020 8:44 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] ASCOM 6.5 released, upgrade or not?

Hi guys,
ASCOM 6.5 is released. Should I upgrade or wait?

https://ascom-standards.org/Help/Platform/html/3417e177-f705-497d-8127-fb30e8519d50.htm

cytan


Re: ASCOM 6.5 released, upgrade or not?

Ray Gralak
 

ASCOM 6.5 is released. Should I upgrade or wait?
Wait for now. I'm looking into it now. The downloaded file is not digitally signed which is a big red flag.

-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 Cheng-Yang Tan via groups.io
Sent: Saturday, July 18, 2020 8:44 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] ASCOM 6.5 released, upgrade or not?

Hi guys,
ASCOM 6.5 is released. Should I upgrade or wait?

https://ascom-standards.org/Help/Platform/html/3417e177-f705-497d-8127-fb30e8519d50.htm

cytan


Re: understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

Ray Gralak
 

Andrea,

For now don't worry about the limit settings in the AE tab. It serves a different purpose than the Meridian Limits.

Meridian limits are soft limits that APCC uses to stop tracking and control when mount flips will occur.

The AE tab allows you to set up hard axis limits in the firmware. You can leave that for later.

-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 andlucchett@gmail.com
Sent: Sunday, July 19, 2020 1:49 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

Ray/Mojo,
I think in my case it is also my level of english understanding that plays a role :-)
I went several times through the documentation but I am still confused.

I wanted also to check that the version of the APCC manual is updated for the Mach2 (the version I am following
is the one dated 5/25/2020).
I've found slightly different set up in the APCC pro manual, set up guide (which is dated 2019 before the mach2),
and the mount manual that came with the mount.

But What is really confusing me is the "AE" panel and "Meridian" panel: they are described separately and I don't
understand if one setting in one panel is going to influence the other one.
from what I understood:
- setting meridian tracking limit flag (operation) set the ability to use limits in general and must be checked
-using the meridian delay allows to configure a fix meridian delay on the west
-variable limits in EAst/west can be set with the Meridian tracking limits panel.

still missing the AE panel settings.

also, I can read in the manual for the limit tab: "Note: The RA Limits that you set here will override any custom
Meridian Limits you may have set on the Meridian Tab. "
does this apply also for the AE panel settings, which is the panel available for the mach2?
but the meridian tracking limit flag (operation) must be flagged for the RA limits to be applied?



Thank you very much,
Andrea



Re: understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

Andrea Lucchetti
 

Ray/Mojo,
I think in my case it is also my level of english understanding that plays a role :-)
I went several times through the documentation but I am still confused.

I wanted also to check that the version of the APCC manual is updated for the Mach2 (the version I am following is the one dated 5/25/2020).
I've found slightly different set up in the APCC pro manual,  set up guide (which is dated 2019 before the mach2), and the mount manual that came with the mount.

But What is really confusing me is the "AE" panel and "Meridian" panel: they are described separately and I don't understand if one setting in one panel is going to influence the other one.
from what I understood:
- setting  meridian tracking limit flag (operation) set the ability to use limits in general and must be checked
-using the meridian delay allows to configure a fix meridian delay on the west
-variable limits in EAst/west can be set with the Meridian tracking limits panel.

still missing the AE panel settings.

also, I can read in the manual for the limit tab: "Note: The RA Limits that you set here will override any custom Meridian Limits you may have set on the Meridian Tab. "
does this apply also for the AE panel settings, which is the panel available for the mach2?
but the meridian tracking limit flag (operation) must be flagged for the RA limits to be applied?



Thank you very much,
Andrea


Re: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Ray Gralak
 

Andrea,

Instead, please try the AP Jog utility to see if the behavior is better. It is included with the ASCOM driver.

AP Jog serves the same function as the Jog feature in SkyX. I saw weird behavior when I tried to use jog in SkyX earlier so there may be some issues within SkyX.

-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 andlucchett@gmail.com
Sent: Sunday, July 19, 2020 1:04 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Hi Ray, thank you for the reply.
I did actually connect to the AP V2 driver, as this was the recommended way to work.

the potential issue I am reporting is based on the following clues:

-when the jog buttons are clicked in Skyx, the mount status changes from "Tracking at sidereal rate" to "slewing":
that should be ok while pushing the buttons, but it should come back to sidereal tracking as soon as the slew is
ended (button released). This was the behavior I always saw with my former paramount ME.
-there is no way from this point on for the status in skyx to change back to "tracking at sidereal rate", it sticks to
"slewing" no matter what you do.

-I noticed the behavior just as consequence of bad images: the images , about 30 s exposure, showed trailing.
After realizing the issue in skyx, disconnecting and reconnecting, the mount returned to track well. I did the same
"mistake" again yesterday at a star party: started getting trailed images, I checked in skyx and the mount was in
"slewing" state. I had again used the jog in skyx (I am used to it because of my previous mount...). I disconnected
the mount, reconnected it, and it returned tracking ok.
thank you,
Andrea


Re: understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

Ray Gralak
 

Hi Morris,

What exactly is a "meridian delay?"
Meridian delay is an offset from the meridian the defines the pier side to which the mount will slew the scope.

Why is the number in your example picture negative? Shouldn't it delay the meridian flip by a positive number of
hours?
It's defined by effectively adjusting the internal clock time by the offset. So a negative value effectively is like turning back the clock 1 hour so it takes an additional hour to reach the flip point. It was done this way to be compatible with the way it was done previously (by adjusting mount time) before the command was added to the firmware.

BTW, the mount will not "flip" the scope automatically when reaching the meridian delay offset. A slew to a RA/Dec or Alt/Az coordinate will be needed to cause the mount to flip. If you are using APCC you can do that, but it's not recommended because the scope might be in the middle of an exposure if you are imaging.

(Probably a different topic.) On my mounts there are certain positions near the zenith where the long AP180 will
crash the camera into one of the pier struts, and I'd love to find a way to prevent that from happening. I also
That's a good point. There isn't a way to prevent that now. I'll ask if that is a feature I can add to APCC.

haven't figured out a procedure for making those nice horizon maps that you have in that example.
You can draw by hand, or in the daytime slew your scope to your horizon obstructions and add horizon points.

-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 Mojo Jones
Sent: Sunday, July 19, 2020 12:18 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

On 7/19/2020 9:29 AM, Ray Gralak wrote:


You can set the meridian delay on the Meridian tab


I've been struggling with the same understanding problems as Andrea. It might help to have some definitions
handy.

What exactly is a "meridian delay?"

Suppose I start imaging an object 30 minutes before it crosses the meridian. Is this delay the amount of time the
mount will wait before flipping? That's what "meridian delay" sounds like.

Why is the number in your example picture negative? Shouldn't it delay the meridian flip by a positive number of
hours?

What if I want to start imaging with counterweight up, and let it track into the west as it crosses the meridian?
How do I do that?

These terms have very specific meanings, and I'm struggling to attach precise definitions to them. I apologize for
that.

(Probably a different topic.) On my mounts there are certain positions near the zenith where the long AP180 will
crash the camera into one of the pier struts, and I'd love to find a way to prevent that from happening. I also
haven't figured out a procedure for making those nice horizon maps that you have in that example.

I'm sure this is all in the documentation, so I'll go hunt there. "How to build a map of forbidden zones" or "how to
map your obstructed horizon." If you have pointers they'd be welcome. :)

Best regards,
Mojo

--
Morris Jones, Monrovia, CA
BridgeMojo <http://bridgemojo.com>
Old Town Sidewalk Astronomers <http://otastro.org>
Mojo's Blog <http://mojo.whiteoaks.com>


Re: Comet NEOWISE (C/2020 F3)

Willie Strickland
 

I found myself in the same position last night.  Due to family commitments I have been absent from imaging for an extended period.  I thought I remembered as well, but when I entered the correction, the scope began a significant slew.  Oops.

Willie


Re: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Andrea Lucchetti
 

Hi Ray, thank you for the reply.
I did actually connect to the AP V2 driver, as this was the recommended way to work.

the potential issue I am reporting is based on the following clues:

-when the jog buttons are clicked in Skyx, the mount status changes from "Tracking at sidereal rate" to "slewing": that should be ok while pushing the buttons, but it should come back to sidereal tracking  as soon as the slew is ended (button released). This was the behavior I always saw with my former paramount ME.
-there is no way from this point on for the status in skyx to change back to "tracking at sidereal rate", it sticks to "slewing" no matter what you do.

-I noticed the behavior just as consequence of bad images: the images , about 30 s exposure, showed trailing. After realizing the issue in skyx, disconnecting and reconnecting, the mount returned to track well. I did the same "mistake" again yesterday at a star party: started getting trailed images, I checked in skyx and the mount was in "slewing" state. I had again used the jog in skyx (I am used to it because of my previous mount...). I disconnected the mount, reconnected it,  and it returned tracking ok.
thank you,
Andrea


Re: ASCOM 6.5 released, upgrade or not?

George LaBelle
 

You know the saying? "If it ain't broke, don't fix it".

I'm not until I have to. You just don't need something breaking right in the middle of imaging season.
--
George
Prineville, Oregon


Re: understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

 

On 7/19/2020 9:29 AM, Ray Gralak wrote:
You can set the meridian delay on the Meridian tab

I've been struggling with the same understanding problems as Andrea. It might help to have some definitions handy.

What exactly is a "meridian delay?"

Suppose I start imaging an object 30 minutes before it crosses the meridian. Is this delay the amount of time the mount will wait before flipping? That's what "meridian delay" sounds like.

Why is the number in your example picture negative? Shouldn't it delay the meridian flip by a positive number of hours?

What if I want to start imaging with counterweight up, and let it track into the west as it crosses the meridian? How do I do that?

These terms have very specific meanings, and I'm struggling to attach precise definitions to them. I apologize for that.

(Probably a different topic.) On my mounts there are certain positions near the zenith where the long AP180 will crash the camera into one of the pier struts, and I'd love to find a way to prevent that from happening. I also haven't figured out a procedure for making those nice horizon maps that you have in that example.

I'm sure this is all in the documentation, so I'll go hunt there. "How to build a map of forbidden zones" or "how to map your obstructed horizon." If you have pointers they'd be welcome. :)

Best regards,
Mojo


Re: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Ray Gralak
 

Andrea,

 

After looking at logs of commands sent via SkyX's native interface to the AP Mounts, I think the implementation seems to have a few issues. We’ll have to contact Software Bisque to work out those issues.

 

Instead, try connecting to the mount through the AP V2 ASCOM driver. Here is how you will want to setup SkyX:

 

 

-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 andlucchett@...

> Sent: Sunday, July 19, 2020 5:23 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

>

> Hi,

> I am using my Mach 2 with APCC pro and skyx.

> Everything seems to work, except for one strange behavior:

>

> -if I use the jog buttons in skyx, the mount get stuck  in a slewing mode, with a wrong tracking speed (not

> sidereal). There is nothing at this point I can do to put the mount back in tracking mode: The only possibility is to

> disconnect the mount from skyx.

>

> Except for this the mount point, sync, track, and autoguide using pulse guide just fine.

>

> Can this be a bug related to the young mach2?

>

> Thank you very much,

> Andrea


Re: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Ray Gralak
 

Hi Andrea,

-if I use the jog buttons in skyx, the mount get stuck in a slewing mode, with a wrong tracking speed (not
sidereal). There is nothing at this point I can do to put the mount back in tracking mode: The only possibility is to
disconnect the mount from skyx.
Following up on the last post I just made, I looked at SkyX's jog functions and they look like they are simple slews so they should work.

What makes you think the mount is not back in sidereal tracking after completing the jog operation?

-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 andlucchett@gmail.com
Sent: Sunday, July 19, 2020 5:23 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Hi,
I am using my Mach 2 with APCC pro and skyx.
Everything seems to work, except for one strange behavior:

-if I use the jog buttons in skyx, the mount get stuck in a slewing mode, with a wrong tracking speed (not
sidereal). There is nothing at this point I can do to put the mount back in tracking mode: The only possibility is to
disconnect the mount from skyx.

Except for this the mount point, sync, track, and autoguide using pulse guide just fine.

Can this be a bug related to the young mach2?

Thank you very much,
Andrea


Re: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Ray Gralak
 

Hi Andrea,

-if I use the jog buttons in skyx, the mount get stuck in a slewing mode, with a wrong tracking speed (not
sidereal). There is nothing at this point I can do to put the mount back in tracking mode: The only possibility is to
disconnect the mount from skyx.
It's probably not a bug in the Mach 2. Some of the commands have changed in the new firmware that the Mach 2 uses. It might take a bit of time before SkyX is updated so for jogging you should consider using APCC's move buttons. You can connect both SkyX and APCC to the mount at the same time.

-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 andlucchett@gmail.com
Sent: Sunday, July 19, 2020 5:23 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Hi,
I am using my Mach 2 with APCC pro and skyx.
Everything seems to work, except for one strange behavior:

-if I use the jog buttons in skyx, the mount get stuck in a slewing mode, with a wrong tracking speed (not
sidereal). There is nothing at this point I can do to put the mount back in tracking mode: The only possibility is to
disconnect the mount from skyx.

Except for this the mount point, sync, track, and autoguide using pulse guide just fine.

Can this be a bug related to the young mach2?

Thank you very much,
Andrea


Re: understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

Ray Gralak
 

Hi Andrea,

 

> I don't want to set meridian limits for each declination, I have a nomad set up and just need to program a fixed

> delay of let say 1 hour.

 

You can set the meridian delay on the Meridian tab. You can tell that a meridian delay is in effect by the yellow line on the sky view graph as shown in the screen shot I’ve included. That said, you should take some time to learn how to fully setup meridian tracking limits for your Mach2.

 

 

-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 andlucchett@...

> Sent: Sunday, July 19, 2020 5:12 AM

> To: main@ap-gto.groups.io

> Subject: [ap-gto] understanding how to set meridian limits for AP MAch 2 #APCC #Mach2GTO

>

> Hi,

> I have a brand new Mach2 +APCC and I am struggling with meridian limits.

>

> I am really confused about the options in AE tab (RA limits), and the Meridian TAB.

> .they all need to be configured?

> -how the two tab settings interact?

> -"operation" & "Meridian delay" within the Meridian TAB: are the two boxes alternatives?

>

> I don't want to set meridian limits for each declination, I have a nomad set up and just need to program a fixed

> delay of let say 1 hour.

>

> Thank you very much,

> Andrea

7361 - 7380 of 79124