Date   

Re: FITS Image Header Issues Using APPM-Help!

Michael Hambrick <mike.hambrick@...>
 

I am running Windows 10, Version 1909 since February 5, 2020. The latest update was 2020-07 and I installed it last Friday (July 18). The infamous 2020-04 (also flagged as a bad actor by the folks at Diffraction Ltd) was installed on April 14, 2020.


Best Regards

Michael Hambrick
ARLANXEO
TSR Global Manufacturing Support
PO Box 2000
Orange, TX 77631-2000
Phone: +1 (409) 882-2799
email: mike.hambrick@...


Re: FITS Image Header Issues Using APPM-Help!

lmbrabec@...
 

Ray:  I should have added that it says 2019 Microsoft for the version.  Sorry about that!  Scott


Re: FITS Image Header Issues Using APPM-Help!

lmbrabec@...
 

It says version 1909 (OS build 18363.959) so its not version 2004. I agree with you as I had success this morning trying the NASA internet option in APPM.  It ran great, but the FITS Image Header is full of information and has the proper format for the image start time that I'm not seeing when I run the ASCOM camera driver with the ZWO camera.  Scott


Re: FITS Image Header Issues Using APPM-Help!

Ray Gralak
 

BTW, what version of Windows are you running?

Type "WinVer" from a command prompt to get the exact version and post the information. If it's version 2004 that could be the problem.

-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 lmbrabec@hotmail.com
Sent: Monday, July 20, 2020 3:06 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] FITS Image Header Issues Using APPM-Help!

Thanks so much Ray and Michael for the help! The first time I tried APPM was on 7/15 and then again today to
see if the FITS Image Headers still caused issues and on both dates it was the same issue. I also tried using the
NASA option this morning and ran a small model (38 or so points) and everything ran fine so it seems like it is
maybe ASCOM/camera driver maybe? As far as version of PinPoint It is the most recent as I just purchased and
downloaded it on 6/24/2020 and for PinPoint Astrometric Engine version is 6.1.5. I'm also attaching some of the
feedback I got from the PinPoint forum (I hope that's o.k.). I figured it would be better that way for you to see
what the PinPoint experts had to say. The last Windows 10 x64 update I got was on July 14th.

Thanks in advance! Scott


Re: FITS Image Header Issues Using APPM-Help!

Ray Gralak
 

Scott,

 

As I said APPM sets the DateTime via ExposureStartTime in PinPoint before doing the plate solve.

 

Sorry, I don't have any other suggestions and I don't see that behavior. Here's a screen shot just done using Nasa SkyView and PinPoint just a moment ago:

 

 

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

> Sent: Monday, July 20, 2020 3:06 PM

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

> Subject: Re: [ap-gto] FITS Image Header Issues Using APPM-Help!

>

> Thanks so much Ray and Michael for the help!  The first time I tried APPM was on 7/15 and then again today to

> see if the FITS Image Headers still caused issues and on both dates it was the same issue.  I also tried using the

> NASA option this morning and ran a small model (38 or so points) and everything ran fine so it seems like it is

> maybe ASCOM/camera driver maybe?  As far as version of PinPoint It is the most recent as I just purchased and

> downloaded it on 6/24/2020 and for PinPoint Astrometric Engine version is 6.1.5.  I'm also attaching some of the

> feedback I got from the PinPoint forum (I hope that's o.k.).  I figured it would be better that way for you to see

> what the PinPoint experts had to say.  The last Windows 10 x64 update I got was on July 14th.

>

> Thanks in advance!  Scott


Re: FITS Image Header Issues Using APPM-Help!

lmbrabec@...
 

Thanks so much Ray and Michael for the help!  The first time I tried APPM was on 7/15 and then again today to see if the FITS Image Headers still caused issues and on both dates it was the same issue.  I also tried using the NASA option this morning and ran a small model (38 or so points) and everything ran fine so it seems like it is maybe ASCOM/camera driver maybe?  As far as version of PinPoint It is the most recent as I just purchased and downloaded it on 6/24/2020 and for PinPoint Astrometric Engine version is 6.1.5.  I'm also attaching some of the feedback I got from the PinPoint forum (I hope that's o.k.).  I figured it would be better that way for you to see what the PinPoint experts had to say.  The last Windows 10 x64 update I got was on July 14th.

Thanks in advance!  Scott


Re: Ser No 900349

Michael Dolenga
 

I think it would be hilarious if someone named Karen posted a video of herself complaining to the manager of the internet about the memes. 


On Monday, July 20, 2020, 12:58:47 PM PDT, Karen Christen <karen@...> wrote:


To be frank, I think Karen memes are funny as heck.  :-D  No offense taken, ever.

Karen

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of khursh via groups.io
Sent: Monday, July 20, 2020 2:14 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Ser No 900349

 

To you and all the Karens out there, I am truly sorry this was done to you. I'm sure Kevins are next.


--
Karen Christen
Astro-Physics


Re: FITS Image Header Issues Using APPM-Help!

Michael Hambrick <mike.hambrick@...>
 

Hi Scott
 
Did you happen to do a Windows update just prior to all of this ? I downloaded the latest Windows update (2020-07) on Friday night, and the next time I started up my laptop was Saturday night getting ready for a night of imaging. MaxIm DL went absolutely crazy on me. I shut everything down a rebooted my laptop and then everything worked fine after that.

I think I had a similar issue once several months trying to run PinPoint Astrometry on an image.


Best Regards

Michael Hambrick
ARLANXEO
TSR Global Manufacturing Support
PO Box 2000
Orange, TX 77631-2000
Phone: +1 (409) 882-2799
email: mike.hambrick@...




From:        lmbrabec@...
To:        main@ap-gto.groups.io
Date:        2020-07-20 12:54 PM
Subject:        [ap-gto] FITS Image Header Issues Using APPM-Help!
Sent by:        main@ap-gto.groups.io




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: FITS Image Header Issues Using APPM-Help!

Ray Gralak
 

Hi Scott,

I've never seen that error. Which version of PinPoint are you using?

APPM sets the pinpoint property ExposureStartTime with the current date/time (as a double, not a string) when providing an image to PinPoint for plate solving. The Time/Date property should be set internally by PinPoint.

-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 lmbrabec@hotmail.com
Sent: Monday, July 20, 2020 10:46 AM
To: main@ap-gto.groups.io
Subject: [ap-gto] FITS Image Header Issues Using APPM-Help!

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: Ser No 900349

KHursh
 

Thumbs up


Re: Ser No 900349

Karen Christen
 

To be frank, I think Karen memes are funny as heck.  :-D  No offense taken, ever.

Karen

 

From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of khursh via groups.io
Sent: Monday, July 20, 2020 2:14 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Ser No 900349

 

To you and all the Karens out there, I am truly sorry this was done to you. I'm sure Kevins are next.


--
Karen Christen
Astro-Physics


Re: Ser No 900349

KHursh
 

To you and all the Karens out there, I am truly sorry this was done to you. I'm sure Kevins are next.


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

3881 - 3900 of 75668