Date   

Re: AP1200 not parking correctly

Mike Dodd
 

On 9/10/2021 12:01 PM, George wrote:
Mike,

The best position is Park 5...scope level on east side and pointing
north. Doesn't have the cable swings.
If I do Park 5 and then loosen the clutches and re-level the axes, how do I do the equivalent as my hand box's "Resume From ref Park1" in the ASCOM driver GUI?

Should I just "Unpark from last parked" and then do a recal in SkyX? That definitely would make the process simple and straightforward. I'm confused by the "ref" in the hand box's "Resume From ref Park1" menu item.

Thanks, George.

--- Mike


Re: AP1200 not parking correctly

George
 

Mike,

The best position is Park 5...scope level on east side and pointing north. Doesn't have the cable swings.

Regards,

George

George Whitney
Astro-Physics, Inc.
Phone:  815-222-6538 (direct line)
Phone:  815-282-1513 (office)
Email:  george@astro-physics.com

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Mike Dodd
Sent: Friday, September 10, 2021 10:57 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] AP1200 not parking correctly

On 9/10/2021 10:44 AM, Ray Gralak wrote:
Hi Mike,

I doubt the alternate COM port had anything to do with this. Were you
using APCC?
No. Just APJog and the ASCOM driver GUI.

If you park again, do you get the same Alt/Az readbacks?
Yes. But I discovered the problem -- I must have bumped the RA axis yesterday. When I connected the hand box and parked to Park1 (I know, should be Park4, but I need to re-jigger some cables to safely reach
Park4) the CW shaft was noticeably not horizontal.

I put my machinist's level on the CW shaft and re-leveled it (along with re-doing the Dec level), and then did a Resume from Park1 on the hand box.

After power-off/power-on and the hand box unplugged, I connected with APJog and used the ASCOM driver buttons to slew the mount to Az=90, Alt=0, and not only did the scope look right, the roof controller detected the correct "at-park safe" position from the magnet switches.

So all looks good. Tonight I'll do a recal in SkyX, then hopefully everything will be returned to normal.

--- Mike


Re: AP1200 not parking correctly

Mike Dodd
 

On 9/10/2021 10:44 AM, Ray Gralak wrote:
Hi Mike,

I doubt the alternate COM port had anything to do with this. Were you
using APCC?
No. Just APJog and the ASCOM driver GUI.

If you park again, do you get the same Alt/Az readbacks?
Yes. But I discovered the problem -- I must have bumped the RA axis yesterday. When I connected the hand box and parked to Park1 (I know, should be Park4, but I need to re-jigger some cables to safely reach Park4) the CW shaft was noticeably not horizontal.

I put my machinist's level on the CW shaft and re-leveled it (along with re-doing the Dec level), and then did a Resume from Park1 on the hand box.

After power-off/power-on and the hand box unplugged, I connected with APJog and used the ASCOM driver buttons to slew the mount to Az=90, Alt=0, and not only did the scope look right, the roof controller detected the correct "at-park safe" position from the magnet switches.

So all looks good. Tonight I'll do a recal in SkyX, then hopefully everything will be returned to normal.

--- Mike


Re: AP1200 not parking correctly

Ray Gralak
 

Hi Mike,

I doubt the alternate COM port had anything to do with this. Were you using APCC?

If you park again, do you get the same Alt/Az readbacks?

-Ray

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Mike Dodd
Sent: Thursday, September 9, 2021 6:38 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] AP1200 not parking correctly

Tonight my AP1200 mount displays an incorrect Az/Alt or RA/Dec when in
my custom Park position. Last night everything was fine.

The ONLY thing that changed today was the port number on an Edgeport
USB-serial box. Last night it was COM4, but today I changed it to COM18
to avoid problems with Win10 updates changing plug-and-play ports.
Tomorrow I will connect the cable to the PC's COM1 port to see if that
makes any difference. I'll be astounded if it does.

I ran the ASCOM driver setup utility, and changed the port there to
COM18, and the utility reported "Mount found!" See the attached screen shot.

My custom park position is due-east -- Az=90, Alt=0. I have magnetic
switches for my roof controller to verify the mount is parked in this
position. I connected to the mount with the AP Jog utility , and slewed
the mount to the correct physical position, confirmed visually and with
the roof controller's magnetic switches.

But the driver shows Alt=-06:27, Az=80:56. and the RA/Dec are wrong, too.

I double-checked my site lat/long in the driver setup utility, and they
are correct. I also clicked the "Set Lat/Long from Mount" button, and
the utility still showed the correct coordinates.

In the ASCOM driver, I clicked the "Re-Sync Mount to PC Time" button.
The driver displays the correct time and time zone.

What could have gone wrong? I understand how incorrect site coordinates
or the wrong time would throw things off, but they all check out.

Thanks for any and all help.

--- Mike





Re: APCC Pro "Lastest Install" not Latest #APCC

Ray Gralak
 

available. I uninstalled, and tried it again with the same results. Fortunately, I still had the v1.9.0.5 install file
and reinstalled it. It appears that the wrong file is linked on the AP website.
The APCC Pro and Standard files linked from the AP website have been updated.

Note that you can also use "Check for Updates" in APCC's help menu to get you a link to the latest from within APCC.

BTW, 1.9.0.5a was copied over to 1.9.0.5, so they are the exact same installer.

-Ray



-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of psparkman via groups.io
Sent: Thursday, September 9, 2021 5:36 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC Pro "Lastest Install" not Latest #APCC

I just downloaded the latest APCC Pro v1.9.0.5a from the AP website. It downloads as ApccProLatest.
However, when I install it, it installs version v1.9.0.1 and has the banner at the top that says an update is
available. I uninstalled, and tried it again with the same results. Fortunately, I still had the v1.9.0.5 install file
and reinstalled it. It appears that the wrong file is linked on the AP website.


AP1200 not parking correctly

Mike Dodd
 

Tonight my AP1200 mount displays an incorrect Az/Alt or RA/Dec when in my custom Park position. Last night everything was fine.

The ONLY thing that changed today was the port number on an Edgeport USB-serial box. Last night it was COM4, but today I changed it to COM18 to avoid problems with Win10 updates changing plug-and-play ports. Tomorrow I will connect the cable to the PC's COM1 port to see if that makes any difference. I'll be astounded if it does.

I ran the ASCOM driver setup utility, and changed the port there to COM18, and the utility reported "Mount found!" See the attached screen shot.

My custom park position is due-east -- Az=90, Alt=0. I have magnetic switches for my roof controller to verify the mount is parked in this position. I connected to the mount with the AP Jog utility , and slewed the mount to the correct physical position, confirmed visually and with the roof controller's magnetic switches.

But the driver shows Alt=-06:27, Az=80:56. and the RA/Dec are wrong, too.

I double-checked my site lat/long in the driver setup utility, and they are correct. I also clicked the "Set Lat/Long from Mount" button, and the utility still showed the correct coordinates.

In the ASCOM driver, I clicked the "Re-Sync Mount to PC Time" button. The driver displays the correct time and time zone.

What could have gone wrong? I understand how incorrect site coordinates or the wrong time would throw things off, but they all check out.

Thanks for any and all help.

--- Mike


Re: APCC Pro "Lastest Install" not Latest #APCC

Michael 'Mikey' Mangieri
 

Yes, I was just about to report this as well !

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of psparkman via groups.io
Sent: Thursday, September 9, 2021 8:36 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] APCC Pro "Lastest Install" not Latest #APCC

 

I just downloaded the latest APCC Pro v1.9.0.5a from the AP website.  It downloads as ApccProLatest.  However, when I install it, it installs version v1.9.0.1 and has the banner at the top that says an update is available.  I uninstalled, and tried it again with the same results.  Fortunately, I still had the v1.9.0.5 install file and reinstalled it.  It appears that the wrong file is linked on the AP website.


APCC Pro "Lastest Install" not Latest #APCC

psparkman@...
 

I just downloaded the latest APCC Pro v1.9.0.5a from the AP website.  It downloads as ApccProLatest.  However, when I install it, it installs version v1.9.0.1 and has the banner at the top that says an update is available.  I uninstalled, and tried it again with the same results.  Fortunately, I still had the v1.9.0.5 install file and reinstalled it.  It appears that the wrong file is linked on the AP website.


Re: Which Camera?

M Hambrick
 

I guess SBIG must have heard some of Chris' complaints because their newer models seem to be getting lighter and more streamlined. My STXL16200 weighs in at over 7 pounds, but their newer cameras are much lighter in the 2 - 3 pound range. They also seem to be trying to reduce the backfocus length in their cameras.

Mike


Re: appm trailing stars at specific DEC

Roland Christen
 

I don't suppose you are there by the scope when it does this, so you can't really tell me what is happening at the motor level in each axis?

Roland


-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 5:42 pm
Subject: Re: [ap-gto] appm trailing stars at specific DEC

Thanks Roland

Howard and others helped us previously to tune 17", so I wasn't thinking of you specifically ;)



On Thu, Sep 9, 2021 at 1:53 PM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
By anyone, you probably mean me. If you have a lot of moment arm on the mount (lots of heavy counterweights far down on the cwt shaft), then you might have a situation where the scope is doing a bit of pendulum motion. Can't tell which axis by your image, but probably RA. You say Dec 50 and 70, but it's probably when the counterweight shaft is near horizontal and the scope is pointing near the meridian. That's the place where all the moments add to give you the least stability and the most moment reaction on the RA axis.

We can tame that, so i can provide you with some specific instructions that you can enter via APCC.

Roland



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 3:25 pm
Subject: [ap-gto] appm trailing stars at specific DEC

Hi everyone

(logs/images at the end of post)

Has anyone else seen this? ideas or suggestions appreciated

Building a model in APPM 1.9.0.1, stars in images are trailing at specific sky areas specifically at DEC 50 and parts of DEC 70

I have a long (to me) 30 second settle time for the mount, and enabled "required high accuracy slews" - still end up with long streaking stars of a consistent distance. 

this example crop is @ 100%
image.png

 
during the settling time, APPM will display "Slew warning". the log shows coordinates oscillating in RA  - example log excerpt at the end of this post

Outside of DEC 50 and 70, model images look fine, round stars, etc.

I even bumped up settle time to 120 seconds, which lessened the number of these, but still see them

Important detail: We switched from CDK17 to CDK20, and went through balancing and polar alignment, etc. It's been suggested that some of our mount parameters may need to be tweaked by AP experts. 


example "Slew Warning" 
0000262 2021-09-01 19:05:06.330:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.63s /  -70° 00' 00.2")
0000263 2021-09-01 19:05:08.130:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.49s /  -69° 59' 59.6")
0000264 2021-09-01 19:05:09.725:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.06s /  -70° 00' 00.3")
0000265 2021-09-01 19:05:11.331:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 41.59s /  -70° 00' 00.4")
0000266 2021-09-01 19:05:13.174:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.37s /  -69° 59' 59.3")
0000267 2021-09-01 19:05:14.794:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.44s /  -69° 59' 59.7")
0000268 2021-09-01 19:05:16.386:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.31s /  -69° 59' 59.9")
0000269 2021-09-01 19:05:18.202:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 39.33s /  -70° 00' 00.1")
0000270 2021-09-01 19:05:19.804:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")
0000271 2021-09-01 19:05:21.372:     Severe,    SLEW WARNING, Slew did not reach destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")

Image files of entire run (including good and failed fits) and log:

--
Brian 



Brian Valente

--
Roland Christen
Astro-Physics


--
Brian 



Brian Valente

--
Roland Christen
Astro-Physics


Re: appm trailing stars at specific DEC

 

Thanks Roland

Howard and others helped us previously to tune 17", so I wasn't thinking of you specifically ;)



On Thu, Sep 9, 2021 at 1:53 PM Roland Christen via groups.io <chris1011=aol.com@groups.io> wrote:
By anyone, you probably mean me. If you have a lot of moment arm on the mount (lots of heavy counterweights far down on the cwt shaft), then you might have a situation where the scope is doing a bit of pendulum motion. Can't tell which axis by your image, but probably RA. You say Dec 50 and 70, but it's probably when the counterweight shaft is near horizontal and the scope is pointing near the meridian. That's the place where all the moments add to give you the least stability and the most moment reaction on the RA axis.

We can tame that, so i can provide you with some specific instructions that you can enter via APCC.

Roland



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 3:25 pm
Subject: [ap-gto] appm trailing stars at specific DEC

Hi everyone

(logs/images at the end of post)

Has anyone else seen this? ideas or suggestions appreciated

Building a model in APPM 1.9.0.1, stars in images are trailing at specific sky areas specifically at DEC 50 and parts of DEC 70

I have a long (to me) 30 second settle time for the mount, and enabled "required high accuracy slews" - still end up with long streaking stars of a consistent distance. 

this example crop is @ 100%
image.png

 
during the settling time, APPM will display "Slew warning". the log shows coordinates oscillating in RA  - example log excerpt at the end of this post

Outside of DEC 50 and 70, model images look fine, round stars, etc.

I even bumped up settle time to 120 seconds, which lessened the number of these, but still see them

Important detail: We switched from CDK17 to CDK20, and went through balancing and polar alignment, etc. It's been suggested that some of our mount parameters may need to be tweaked by AP experts. 


example "Slew Warning" 
0000262 2021-09-01 19:05:06.330:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.63s /  -70° 00' 00.2")
0000263 2021-09-01 19:05:08.130:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.49s /  -69° 59' 59.6")
0000264 2021-09-01 19:05:09.725:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.06s /  -70° 00' 00.3")
0000265 2021-09-01 19:05:11.331:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 41.59s /  -70° 00' 00.4")
0000266 2021-09-01 19:05:13.174:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.37s /  -69° 59' 59.3")
0000267 2021-09-01 19:05:14.794:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.44s /  -69° 59' 59.7")
0000268 2021-09-01 19:05:16.386:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.31s /  -69° 59' 59.9")
0000269 2021-09-01 19:05:18.202:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 39.33s /  -70° 00' 00.1")
0000270 2021-09-01 19:05:19.804:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")
0000271 2021-09-01 19:05:21.372:     Severe,    SLEW WARNING, Slew did not reach destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")

Image files of entire run (including good and failed fits) and log:

--
Brian 



Brian Valente

--
Roland Christen
Astro-Physics



--
Brian 



Brian Valente


Re: Interesting way to image with a cheap mount

Dean Jacobsen
 

On Thu, Sep 9, 2021 at 12:52 PM, Roland Christen wrote:
Nice trick, no?
No.
 
--
Dean Jacobsen
Astrobin Image Gallery - https://www.astrobin.com/users/deanjacobsen/


Re: 47 Tucanae with 155EDF refractor

Bill Long
 

Just to add, the 3.5" focuser from AP is excellent! I had 11lbs of camera, wheel, OAG, and guide camera on it with no problem at all. Very robust. 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Marj Christen <marj@...>
Sent: Thursday, September 9, 2021 2:54 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] 47 Tucanae with 155EDF refractor
 

Christopher, the 4” focuser is no longer available, but our newer 3.5” focuser would be an appropriate replacement. We do not have them in stock at the moment, but they are in production. Click the Notify Me button on the webpage and we will contact you when it is available. The upgrade is very quick and easy.

https://www.astro-physics.com/s35focer-ft

 

 

Clear Skies,

Marj Christen

Astro-Physics

11250 Forest Hills Road

Machesney Park, IL 61115

Phone: 815-282-1513

www.astro-physics.com

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Roland Christen via groups.io
Sent: Wednesday, September 8, 2021 8:43 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] 47 Tucanae with 155EDF refractor

 

 

his may be an odd question, but can an AP155EDFS be "rebuilt" into an AP155EDF? 

Yes, you simply replace the 2.7" focuser with the 4". 6 screws hold it on. Nothing else needs to be changed.

 

Rolando

 

 

-----Original Message-----
From: Christopher M <mirfak@...>
To: main@ap-gto.groups.io
Sent: Wed, Sep 8, 2021 8:22 pm
Subject: Re: [ap-gto] 47 Tucanae with 155EDF refractor

This may be an odd question, but can an AP155EDFS be "rebuilt" into an AP155EDF?  I believe the lense assembly is the same.  I assume it would require some changes to the OTA tube, possibly baffling (?), and whatever, to accomodate replacement of the smaller focuser to the larger 4" focuser.  I don't have either but I do know someone who has an EDFS.
Christopher


--
Roland Christen
Astro-Physics


Re: 47 Tucanae with 155EDF refractor

 

Christopher, the 4” focuser is no longer available, but our newer 3.5” focuser would be an appropriate replacement. We do not have them in stock at the moment, but they are in production. Click the Notify Me button on the webpage and we will contact you when it is available. The upgrade is very quick and easy.

https://www.astro-physics.com/s35focer-ft

 

 

Clear Skies,

Marj Christen

Astro-Physics

11250 Forest Hills Road

Machesney Park, IL 61115

Phone: 815-282-1513

www.astro-physics.com

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Roland Christen via groups.io
Sent: Wednesday, September 8, 2021 8:43 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] 47 Tucanae with 155EDF refractor

 

 

his may be an odd question, but can an AP155EDFS be "rebuilt" into an AP155EDF? 

Yes, you simply replace the 2.7" focuser with the 4". 6 screws hold it on. Nothing else needs to be changed.

 

Rolando

 

 

-----Original Message-----
From: Christopher M <mirfak@...>
To: main@ap-gto.groups.io
Sent: Wed, Sep 8, 2021 8:22 pm
Subject: Re: [ap-gto] 47 Tucanae with 155EDF refractor

This may be an odd question, but can an AP155EDFS be "rebuilt" into an AP155EDF?  I believe the lense assembly is the same.  I assume it would require some changes to the OTA tube, possibly baffling (?), and whatever, to accomodate replacement of the smaller focuser to the larger 4" focuser.  I don't have either but I do know someone who has an EDFS.
Christopher


--
Roland Christen
Astro-Physics


Re: appm trailing stars at specific DEC

Roland Christen
 

By anyone, you probably mean me. If you have a lot of moment arm on the mount (lots of heavy counterweights far down on the cwt shaft), then you might have a situation where the scope is doing a bit of pendulum motion. Can't tell which axis by your image, but probably RA. You say Dec 50 and 70, but it's probably when the counterweight shaft is near horizontal and the scope is pointing near the meridian. That's the place where all the moments add to give you the least stability and the most moment reaction on the RA axis.

We can tame that, so i can provide you with some specific instructions that you can enter via APCC.

Roland



-----Original Message-----
From: Brian Valente <bvalente@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 3:25 pm
Subject: [ap-gto] appm trailing stars at specific DEC

Hi everyone

(logs/images at the end of post)

Has anyone else seen this? ideas or suggestions appreciated

Building a model in APPM 1.9.0.1, stars in images are trailing at specific sky areas specifically at DEC 50 and parts of DEC 70

I have a long (to me) 30 second settle time for the mount, and enabled "required high accuracy slews" - still end up with long streaking stars of a consistent distance. 

this example crop is @ 100%
image.png

 
during the settling time, APPM will display "Slew warning". the log shows coordinates oscillating in RA  - example log excerpt at the end of this post

Outside of DEC 50 and 70, model images look fine, round stars, etc.

I even bumped up settle time to 120 seconds, which lessened the number of these, but still see them

Important detail: We switched from CDK17 to CDK20, and went through balancing and polar alignment, etc. It's been suggested that some of our mount parameters may need to be tweaked by AP experts. 


example "Slew Warning" 
0000262 2021-09-01 19:05:06.330:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.63s /  -70° 00' 00.2")
0000263 2021-09-01 19:05:08.130:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.49s /  -69° 59' 59.6")
0000264 2021-09-01 19:05:09.725:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.06s /  -70° 00' 00.3")
0000265 2021-09-01 19:05:11.331:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 41.59s /  -70° 00' 00.4")
0000266 2021-09-01 19:05:13.174:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.37s /  -69° 59' 59.3")
0000267 2021-09-01 19:05:14.794:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.44s /  -69° 59' 59.7")
0000268 2021-09-01 19:05:16.386:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.31s /  -69° 59' 59.9")
0000269 2021-09-01 19:05:18.202:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 39.33s /  -70° 00' 00.1")
0000270 2021-09-01 19:05:19.804:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")
0000271 2021-09-01 19:05:21.372:     Severe,    SLEW WARNING, Slew did not reach destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")

Image files of entire run (including good and failed fits) and log:

--
Brian 



Brian Valente

--
Roland Christen
Astro-Physics


Re: Which Camera?

Bill Long
 

As soon as my Atik APX60 arrives and I get some test time in I'll share some data. Need to first light a new (to me) toa 150 and it's 67 flattener so that'll be the scope. Mach 2 of course will drive it all.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Roland Christen via groups.io <chris1011@...>
Sent: Thursday, September 9, 2021 1:45 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Which Camera?
 
I have a QSI that I love using. It is robust, extremely well done mechanically and just works. Thus I am interested in the Atik Cmos version which I didn't realize was in production. I don't know much about Moravian, but it looks promising as well.

As far as SBIG, I still have my trusty STL11K which works perfectly (if you ignore the high noise level), and is only a bit clunky mechanically. When used with my 17" F8 astrograph it has provided the highest resolution of any of the scopes I have access to - under 0.8 arc sec FWHM when seeing is perfect.

Rolando

-----Original Message-----
From: Seb@stro <sebastiendore1@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 3:27 pm
Subject: Re: [ap-gto] Which Camera?

IMO, the fact that ZWO/QHY have the edge on getting new products out at crazy rate / competitive prices comes at the cost of instabilities that usually come along with any brand new fast-to-market line of products. I too have experienced their quirks (guiding with QHY5III-174M, imaging with ASI183MC PRO) but it was no surprise to me as my expectations were set accordingly when I bought them in the first place. Good engineering takes time, research, experimentation, iterations, extensive testing, writing design and support documentation, etc. and that costs money. Did I say that takes time ? That statement generalizes to both hardware and software, of course. 

And add to that the fact that the usual "premium astrocams" companies were mostly all into CDD until very recently and probably had to rethink big portions of their business model, product engineering and manufacturing lines, it's no surprise they are coming up "late" relative to the chinese brands. They probably will have a few things to sort out after initial launch too, but I suspect of least importance.

I usually am not an "early adopter" either (although I did buy a Mach2 from the second run :D ) so I too decided to be patient and wait for the premium, usually more stable products to arrive before pulling the trigger on my next camera purchase. That and to encourage "domestic" enterprises whenever possible... Same logic as for the mount in the end. So I am waiting for SBIG (DL), Moravian, ATIK/QSI, (FLI ?) and the like to come up on the CMOS menu and get reports from "EA" users.

What would greatly simplify choices is if we could buy an AP-GTCAM one day...! ;-)

Sébastien

--
Roland Christen
Astro-Physics


Re: Which Camera?

Roland Christen
 

I have a QSI that I love using. It is robust, extremely well done mechanically and just works. Thus I am interested in the Atik Cmos version which I didn't realize was in production. I don't know much about Moravian, but it looks promising as well.

As far as SBIG, I still have my trusty STL11K which works perfectly (if you ignore the high noise level), and is only a bit clunky mechanically. When used with my 17" F8 astrograph it has provided the highest resolution of any of the scopes I have access to - under 0.8 arc sec FWHM when seeing is perfect.

Rolando

-----Original Message-----
From: Seb@stro <sebastiendore1@...>
To: main@ap-gto.groups.io
Sent: Thu, Sep 9, 2021 3:27 pm
Subject: Re: [ap-gto] Which Camera?

IMO, the fact that ZWO/QHY have the edge on getting new products out at crazy rate / competitive prices comes at the cost of instabilities that usually come along with any brand new fast-to-market line of products. I too have experienced their quirks (guiding with QHY5III-174M, imaging with ASI183MC PRO) but it was no surprise to me as my expectations were set accordingly when I bought them in the first place. Good engineering takes time, research, experimentation, iterations, extensive testing, writing design and support documentation, etc. and that costs money. Did I say that takes time ? That statement generalizes to both hardware and software, of course. 

And add to that the fact that the usual "premium astrocams" companies were mostly all into CDD until very recently and probably had to rethink big portions of their business model, product engineering and manufacturing lines, it's no surprise they are coming up "late" relative to the chinese brands. They probably will have a few things to sort out after initial launch too, but I suspect of least importance.

I usually am not an "early adopter" either (although I did buy a Mach2 from the second run :D ) so I too decided to be patient and wait for the premium, usually more stable products to arrive before pulling the trigger on my next camera purchase. That and to encourage "domestic" enterprises whenever possible... Same logic as for the mount in the end. So I am waiting for SBIG (DL), Moravian, ATIK/QSI, (FLI ?) and the like to come up on the CMOS menu and get reports from "EA" users.

What would greatly simplify choices is if we could buy an AP-GTCAM one day...! ;-)

Sébastien

--
Roland Christen
Astro-Physics


Re: Which Camera?

Sébastien Doré
 

IMO, the fact that ZWO/QHY have the edge on getting new products out at crazy rate / competitive prices comes at the cost of instabilities that usually come along with any brand new fast-to-market line of products. I too have experienced their quirks (guiding with QHY5III-174M, imaging with ASI183MC PRO) but it was no surprise to me as my expectations were set accordingly when I bought them in the first place. Good engineering takes time, research, experimentation, iterations, extensive testing, writing design and support documentation, etc. and that costs money. Did I say that takes time ? That statement generalizes to both hardware and software, of course. 

And add to that the fact that the usual "premium astrocams" companies were mostly all into CDD until very recently and probably had to rethink big portions of their business model, product engineering and manufacturing lines, it's no surprise they are coming up "late" relative to the chinese brands. They probably will have a few things to sort out after initial launch too, but I suspect of least importance.

I usually am not an "early adopter" either (although I did buy a Mach2 from the second run :D ) so I too decided to be patient and wait for the premium, usually more stable products to arrive before pulling the trigger on my next camera purchase. That and to encourage "domestic" enterprises whenever possible... Same logic as for the mount in the end. So I am waiting for SBIG (DL), Moravian, ATIK/QSI, (FLI ?) and the like to come up on the CMOS menu and get reports from "EA" users.

What would greatly simplify choices is if we could buy an AP-GTCAM one day...! ;-)

Sébastien


appm trailing stars at specific DEC

 

Hi everyone

(logs/images at the end of post)

Has anyone else seen this? ideas or suggestions appreciated

Building a model in APPM 1.9.0.1, stars in images are trailing at specific sky areas specifically at DEC 50 and parts of DEC 70

I have a long (to me) 30 second settle time for the mount, and enabled "required high accuracy slews" - still end up with long streaking stars of a consistent distance. 

this example crop is @ 100%
image.png

 
during the settling time, APPM will display "Slew warning". the log shows coordinates oscillating in RA  - example log excerpt at the end of this post

Outside of DEC 50 and 70, model images look fine, round stars, etc.

I even bumped up settle time to 120 seconds, which lessened the number of these, but still see them

Important detail: We switched from CDK17 to CDK20, and went through balancing and polar alignment, etc. It's been suggested that some of our mount parameters may need to be tweaked by AP experts. 


example "Slew Warning" 
0000262 2021-09-01 19:05:06.330:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.63s /  -70° 00' 00.2")
0000263 2021-09-01 19:05:08.130:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.49s /  -69° 59' 59.6")
0000264 2021-09-01 19:05:09.725:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.06s /  -70° 00' 00.3")
0000265 2021-09-01 19:05:11.331:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 41.59s /  -70° 00' 00.4")
0000266 2021-09-01 19:05:13.174:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.37s /  -69° 59' 59.3")
0000267 2021-09-01 19:05:14.794:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.44s /  -69° 59' 59.7")
0000268 2021-09-01 19:05:16.386:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 37.31s /  -69° 59' 59.9")
0000269 2021-09-01 19:05:18.202:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 39.33s /  -70° 00' 00.1")
0000270 2021-09-01 19:05:19.804:    Warning,    SLEW WARNING, Slew has not reached destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")
0000271 2021-09-01 19:05:21.372:     Severe,    SLEW WARNING, Slew did not reach destination: Target=( 18h 58m 39.41s /  -70° 00' 00.0") -- Mount=( 18h 58m 38.41s /  -70° 00' 00.1")

Image files of entire run (including good and failed fits) and log:

--
Brian 



Brian Valente


Re: Interesting way to image with a cheap mount

Bill Long
 

Yeah that's definitely a thing. I'm of course opposed to such things, but I also am the type that will spend hours working to squeeze every tiny bit of performance from optics and gets OCD about stars in images. To me it's all a part of the learning journey in the hobby. But for some the shortcuts are very compelling.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Roland Christen via groups.io <chris1011@...>
Sent: Thursday, September 9, 2021 12:52 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] Interesting way to image with a cheap mount
 
I recently saw an image taken with a cheap mount that shows nice tight round stars, even though the mount might have a fair amount of tracking error that bloats the stars and makes them oval during long exposures. How is that possible, you ask?

The idea is to take the images, stack them and remove the stars with software now available. Then take a series of very short RGB exposures, stack them, extract the stars and paste them on the previous long exposures. Presto - you have a premium image with nice tight round stars. And people will point to your image and proclaim that you don't need fancy equipment to get perfect results. Of course the background image is not sharp, but who looks at that when the stars are tiny and round! Nice trick, no?

Rolando

--
Roland Christen
Astro-Physics

5541 - 5560 of 86336