Date   

Re: Lens Cleaner

myrussellm
 

Larry 

For the Purists AP provided a " care of your Telescope article in 2014, its still available from them but essentially the instructions for lense cleaning is attached.

As the victime of a previous owners rather aggressive " cleaning" of an AP178 I can sympathise with Jerry


Re: Ser No 900349

Karen Christen
 

Hey, now.  ;-)

 

Karen

AP

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of khursh via groups.io
Sent: Saturday, July 18, 2020 9:50 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Ser No 900349

 

I reported it to the admins. I guess I'm a "Karen" now.


--
Karen Christen
Astro-Physics


Re: Comet NEOWISE/Milky way

Astrobob
 

A friend sent this to me. Good for a laugh!

 

Bob

 

Sent from Mail for Windows 10

 


FITS Image Header Issues Using APPM-Help!

lmbrabec@...
 

Hello all:  I'm new to the forum and just got my Mach2 up and running and learning the ropes with APPM.  I've been working on an issue where plate solving is failing.  My camera set-up in APPM is: ASCOM Camera, ASI Camera (1), ZWO ASI294MC Pro.  Current versions I'm using is: ASCOM 6.4.1.2695, and the ZWO camera ASCOM driver is the most current 1.0.4.3.  I'm also using APCC-Pro version 1.8.2.1, and APCC V2 driver 5.3.10. I'm also using the PinPoint (Full Version) for the plate solver.

The error message during plate solving that I get is "plate solve failed! The plate's exposure start time is required for catalog proper motion calculation".  I also got same message when trying the "plate solve" under the Run tab in APPM.  I pulled in an older FITS image that had been imaged with SharpCap software and using the "image link test" in the Plate Solve Settings tab and everything looked good (plate solved).  I've attached a PDF of the failed image FITS Image Header captured through APPM and the FITS Image Header captured with SharpCap. 

Looking at the "Date-Obs." row in the FITS image header for the image that failed to plate solve and said that exposure start time is needed the format used was: "7/20/2020 10:53:41 AM'.  I am also noticing that there is no RA and DEC information in the FITS file.  The FITS Image Header from the SharpCap acquired image showed for "Date-Obs." row: "2019-10-25T02:02:11.2774146'. 

I'm also attaching a PDF of camera settings used in APPM and the plate solve results along with the FITS Image Headers of the successful plate solve (SharpCap acquired), and failed through APPM.  I ran this by the PinPoint forum and they mentioned that the Date-Obs. format is incorrect for the failed plate solve and that the FITS image information does not come from Pin Point but the acquisition software?  Thanks in advance for your help!  I'm loving the Mach2 so far and looking forward to learning the modeling capabilities.  Scott


Re: C11HD on Mach2 #Mach2GTO

Dominique Durand
 

Thanks Stuart, Greg, Rolando
Correct polar alignment without more and APPM modeling 90 points, 48 West and 42 East.

Dominique


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

Howard Hedlund
 

APCC and the Driver show sidereal as the SELECTED tracking rate.  That is the tracking rate even while slewing, and the mount must keep track of the sidereal motion of the sky during the time it takes to slew.

 

TheSkyX is failing to stop its button slew as Rolando has pointed out.  Now that I’m back in the Saddle, I plan to address a number of such issues with outside developers.  Please be patient with me.  I have a lot of catch-up!

 

Mag. 7 Skies!

 

Howard Hedlund

Astro-Physics, Inc.

Phone: 815-315-7015

www.astro-physics.com

Please include this e-mail with your response.

 

P Consider the environment before printing this e-mail.

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Wayne Hixson via groups.io
Sent: Monday, July 20, 2020 10:02
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

 

When I tried this yesterday although SkyX reported slewing even after button release, APCC and ASCOM driver showed tracking at 

sidereal rate. 



On Jul 20, 2020, at 7:56 AM, uncarollo2 <chris1011@...> via groups.io <chris1011@...> wrote:



We will look into this. Meanwhile can you use the jog buttons in APCC?

 

It may be that SkyX is configured to send a "move" command but not a "quit move" command when the button is released. Therefore the mount continues to move at the button rate.

 

Rolando

 

 

 

-----Original Message-----
To: main@ap-gto.groups.io
Sent: Sun, Jul 19, 2020 7:22 am
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: C11HD on Mach2 #Mach2GTO

Roland Christen
 

Looks very good for starters.

Rolando



-----Original Message-----
From: Dominique Durand via groups.io <dom33.durand@...>
To: main@ap-gto.groups.io
Sent: Mon, Jul 20, 2020 4:25 am
Subject: [ap-gto] C11HD on Mach2 #Mach2GTO

[Edited Message Follows]
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/0/

Happy amateur astronut
Dominique


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

Roland Christen
 

SkyX is failing to send the proper stop slew command. It's not a failing of the mount, it's an improper command in SkyX.

Rolando



-----Original Message-----
To: main@ap-gto.groups.io
Sent: Sun, Jul 19, 2020 3:04 pm
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: strange behavior of Mach2 in Skyx #Mach2GTO: slewing instead of tracking

Wayne Hixson
 

When I tried this yesterday although SkyX reported slewing even after button release, APCC and ASCOM driver showed tracking at 
sidereal rate. 


On Jul 20, 2020, at 7:56 AM, uncarollo2 <chris1011@...> via groups.io <chris1011@...> wrote:


We will look into this. Meanwhile can you use the jog buttons in APCC?

It may be that SkyX is configured to send a "move" command but not a "quit move" command when the button is released. Therefore the mount continues to move at the button rate.

Rolando



-----Original Message-----
To: main@ap-gto.groups.io
Sent: Sun, Jul 19, 2020 7:22 am
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

Roland Christen
 

We will look into this. Meanwhile can you use the jog buttons in APCC?

It may be that SkyX is configured to send a "move" command but not a "quit move" command when the button is released. Therefore the mount continues to move at the button rate.

Rolando



-----Original Message-----
To: main@ap-gto.groups.io
Sent: Sun, Jul 19, 2020 7:22 am
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: C11HD on Mach2 #Mach2GTO

Greg Vaughn
 

Dominique,

 

Thanks very much for sharing your results!

 

These are very pleasing, especially the clusters with the depth and colors of the stars!

 

Did you do a model in APCC (under APPM) or did you just do a very precise polar alignment or did you do both.   If you did a model, how many points did you measure over how large an azimuthal area?

 

I have an EDGE 11 HD and a Mach2 and am interested in trying unguiding imaging as well.   I ask about azimuthal area, because I only have about a 90deg window for observation and focus most of my points there – so just comparing number of points is not a good comparison for me.

 

Thanks in advance.

 

Cheers,

Greg

 

Greg Vaughn

Alexandria, VA

 


Virus-free. www.avast.com


Re: C11HD on Mach2 #Mach2GTO

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

Dominique, these are all exceptional. I could not get any of your links to work but went to Astrobin and found you and the images there. 


On Mon, 20 Jul 2020 at 05:26, Dominique Durand via groups.io <dom33.durand=yahoo.com@groups.io> wrote:
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
[URL=https://astrob.in/full/h1sgqo/0/][IMG]https://astrob.in/h1sgqo/0/rawthumb/gallery/get.jpg?insecure[/IMG][/URL]

M92
[URL=https://astrob.in/full/vfeboh/0/][IMG]https://astrob.in/vfeboh/0/rawthumb/gallery/get.jpg?insecure[/IMG][/URL]

NGC6384
[URL=https://astrob.in/full/5c5wt2/0/][IMG]https://astrob.in/5c5wt2/0/rawthumb/gallery/get.jpg?insecure[/IMG][/URL]

Happy amateur astronut
Dominique


--

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


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

7241 - 7260 of 79016