Date   

Re: Lunar Tracking Rate #ASCOM_V2_Driver

Mike Miller
 

Ahh, that would do it! The only app I had connected was APJog, which I used for nudging.  In the future I will get the moon framed and disconnect APJog before hitting the button.

If I am gong to do some imaging instead of just a quick EAA, I will use Horizons to get the rates perfect. This was kind of a on-a-whim thing, and I was out in the field without internet access.

Thanks for your help!

-mike


Re: Notified!😍 #mach2gto #Mach2GTO

Terri Zittritsch
 
Edited

On Tue, Mar 10, 2020 at 01:59 AM, uncarollo2 <chris1011@...> wrote:
The RA and Dec drift rates indicate fairly large Polar Alignment error. It means your Polemaster is giving you a significant PA error for whatever reason. That's why I don't rely on electronic devices for polar alignment. If you want the drift rate to be zero, then you have to do drift alignment where you twiddle with the Alt and Az adjusters until the drift rates are zero (which is the definition and goal of drift alignment). Ray Graylack's Pempro does that without muss or fuss in surprisingly short time. Once I have drift alignment zeroed in, I simply attach my right angle Polar scope, place Polaris at the correct point on the dial via the push-pull adjustment and I'm good to go from then on using only the Polar scope. Of course with guiding the drift doesn't matter, but for best performance it is good to have essentially zero drift. Yerkes observatory did it in the late 1800's and they had some pretty crude methods with that 40" refractor mount. But it was good enough to allow unguided imaging for considerable time exposures.
 
Every generation of astro-imagers has to go thru this learning process, and the fundamentals never change. The 2.5 arc sec P-P excursions are almost exactly what the seeing was for that night, so that will be the best you will get under those conditions. No way anything less than a $1million active guiding system along with high power laser for forming an artificial star will do any better.
 
By the way, your Vermont skies are not too bad. In the last week I had 1.2 arc sec FWHM resolution with no guiding (simple model in the keypad only) for 2 nights, then the seeing morphed into 7.5 arc sec FWHM stars when the trade winds picked up. Sky was crystal clear but stars looked like small shaggy dogs.
 
Rolando
Thank you again Roland for your personal time here.    I think what you're telling me is that by drift aligning, and then adjusting your polar scope to put polaris in the correct position based on the drift alignment, that you're calibrating your polar scope for refraction effects at your location.   I guess you're actually moving your reticle to match where polaris is after drift aligning.   I know Polemaster is supposed to be able to account for some refractive effect, but likely not super-accurate and just some kind of calculated estimate.    Are you also saying that for a particular location, refractive effects are constant?

If the offset due to refractive effects is constant, then maybe I can estimate in polemaster.    Right now I have no idea what this might look like (how much).   I guess maybe a drift align one night with polemaster monitor running will give me my answer.     The other complication is that I have no pier or 100% stable setup.   I wonder how much error results from using a tripod vs. a pier,  and then how much variation this causes throughout the night.    


T


Re: PHD2 versus ASCOM driver

Terri Zittritsch
 

On Tue, Mar 10, 2020 at 02:51 AM, Wayne Hixson wrote:
Thanks Roland. Of your suggestions, I’ll I’ve done so far is add a 1500 ms delay between 3 second exposures and getting the best guiding I’ve ever seen by far as I am live stacking M94 in SharpCap.  About 0.5” RMS over at least an hour with only occasional tiny corrections. 0.32” RA and 0.34” Dec.  OAG with an Ultrastar binned 2x2, 130GTX with field flattener, or 871 mm fl. Love it!
 
PS I used the Polemaster about 4 hours ago and just checked, the little green Pole square is still overlapping the red axis target circle by about 33%. 
 
Enjoy your time in Hawaii and I am looking forwards to using the keypad for modeling!
 
Congratulations Wayne, this is great news!   I can't wait to try the updated settings.  I've never done the delay between pulses either, but it certainly makes sense.

Thanks to Roland for the guiding education, maybe I can finally stop overdosing myself when at the telescope now (smile).

T


Re: PHD2 versus ASCOM driver

 

FYI in recent releases, PHD can recognize if you are using encoders, and changes the default algorithm to lowpass2 for precisely the reasons Roland outlined

when you use the new profile wizard, it will calculate the correct step sizes, but it will not add time between your frames.

Wayne you might want to try bin 1 on your ultrastar. those are already pretty big pixels. Sounds like you have the time courtesy of the mount's accuracy that you can increase your exposure time if need be (and reduce time delay between exposures if need be)


Brian



On Mon, Mar 9, 2020 at 11:52 PM Wayne Hixson via Groups.Io <wayneh9026=yahoo.com@groups.io> wrote:
Thanks Roland. Of your suggestions, I’ll I’ve done so far is add a 1500 ms delay between 3 second exposures and getting the best guiding I’ve ever seen by far as I am live stacking M94 in SharpCap.  About 0.5” RMS over at least an hour with only occasional tiny corrections. 0.32” RA and 0.34” Dec.  OAG with an Ultrastar binned 2x2, 130GTX with field flattener, or 871 mm fl. Love it!

PS I used the Polemaster about 4 hours ago and just checked, the little green Pole square is still overlapping the red axis target circle by about 33%. 

Enjoy your time in Hawaii and I am looking forwards to using the keypad for modeling!

Wayne


On Mar 9, 2020, at 10:21 PM, uncarollo2 <chris1011@...> via Groups.Io <chris1011=aol.com@groups.io> wrote:


 
We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?
hello Wayne,
 
One setting I recommend for Encoder Mounts is to use a 1.5 to 2 second delay time between guide exposures. Click on the little brain in PHD2 and bring up the Advanced Setting/Camera Settings. Set the Time Lapse to 1500 to 2000. Your guide exposures can be set to anything from under 1 sec to 5 sec or more. I usually use 2 sec exposures unless the seeing is jumping around, in which case a longer exposure is used.
 
I normally use 1x Sidereal guide rate, but you can use .5x also if the seeing is good. There is no need to go slower to .25x.
 
Calibration steps are 300msec at 1x sidereal, 600msec at .5x.
 
I use either Lowpass 2 or Hysteresis. In Lowpass2 my settings are normally Aggressiveness 50 to 80% depending on seeing. Higher if good, lower if poor seeing. Min Move depends on seeing as reported in Guiding Assistant. Usually set to 0.2 pixels for my setup which has 2 arc sec per pixel. Max Duration is 2500msec. Both axes are set the same, no Backlash Compensation is used (set it to 0).
 
I have used all the other algorithms with success. Settings vary by scope focal length and seeing conditions. In all cases use a 1500 to 2000 Time Lapse in order to let the mount settle between guide exposures and not try to chase the seeing. An encoder mount will reverse Dec very accurately for even 1/4 arc sec move commands, but not in zero time. When the mount gets a very tiny Dec move command to reverse it will so in a controlled manner at a controlled rate. It is not instant, so the Time Lapse lets the Dec axis get there and settle before getting another small move command.
In a non-encoder mount there is a delay time, but also a crossover hysteresis where it may take 2, 3 or more small move commands before the axis actually reverses. This is different in an encoder mount where only 1 command is needed for full reversal, or any move deemed necessary by the software. For instance if the guide star is 1 arc sec off the centerline and Aggress is set to 100%, then the software sends a -1 arc sec move command, and the mount will move the axis exactly 1 arc sec, no more, no less.
In RA it's always instant because the belt tension (or gear mesh) is always on in the direction of movement. It simply slows down or speeds up. In Dec it's also instant if moving in the same direction each time, but takes some 100 +milliseconds when reversing.
Reversing Dec axis is like taking a Tylenol pill for a headache. You take 1 pill and wait for the headache to go away, and it will after a bit of time. If you don't wait and think I took one pill, still have the headache and take another and another until the headache goes away, you have overdosed yourself. The first one + time lapse delay was actually best for your health.
 
So for Dec we don't call it backlash since there isn't any when reversing. In encoder terms it's called Settling Time. There is even settling time for RA during dither recovery where the mount is commanded to move many arc seconds. For instance, if the dither is 15 arc seconds and the guide rate is 0.5x, it will take the mount approximately 2 seconds to get back to the zero line (0.5x = 7.5 arc sec per sec). If you have a guide rate set for 0.5 seconds with no Time Lapse delay dialed in, the mount will get numerous 15 arc second move commands and will indeed overshoot at the end.
 
Hope this helps.
 
Rolando
 
-----Original Message-----
From: Wayne Hixson via Groups.Io <wayneh9026=yahoo.com@groups.io>
To: main <main@ap-gto.groups.io>
Sent: Mon, Mar 9, 2020 9:05 am
Subject: [ap-gto] PHD2 versus ASCOM driver

Had a really good night with the Mach2 under clear but moonlit skies. PHD2 ran reasonable well with default settings, but  ran into a couple issues. First, it warned me I should disable Synchronous Pulseguide in the driver, I couldn’t find that setting and not sure I want to disable even if I could!

Second I had several times where I got a warning message that mount wasn’t responding to pulseguide commands and I had to disconnect/reconnect to resume.

We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?

wayne 



--
Brian 



Brian Valente


Re: PHD2 versus ASCOM driver

Wayne Hixson
 

Thanks Roland. Of your suggestions, I’ll I’ve done so far is add a 1500 ms delay between 3 second exposures and getting the best guiding I’ve ever seen by far as I am live stacking M94 in SharpCap.  About 0.5” RMS over at least an hour with only occasional tiny corrections. 0.32” RA and 0.34” Dec.  OAG with an Ultrastar binned 2x2, 130GTX with field flattener, or 871 mm fl. Love it!

PS I used the Polemaster about 4 hours ago and just checked, the little green Pole square is still overlapping the red axis target circle by about 33%. 

Enjoy your time in Hawaii and I am looking forwards to using the keypad for modeling!

Wayne


On Mar 9, 2020, at 10:21 PM, uncarollo2 <chris1011@...> via Groups.Io <chris1011@...> wrote:


 
We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?
hello Wayne,
 
One setting I recommend for Encoder Mounts is to use a 1.5 to 2 second delay time between guide exposures. Click on the little brain in PHD2 and bring up the Advanced Setting/Camera Settings. Set the Time Lapse to 1500 to 2000. Your guide exposures can be set to anything from under 1 sec to 5 sec or more. I usually use 2 sec exposures unless the seeing is jumping around, in which case a longer exposure is used.
 
I normally use 1x Sidereal guide rate, but you can use .5x also if the seeing is good. There is no need to go slower to .25x.
 
Calibration steps are 300msec at 1x sidereal, 600msec at .5x.
 
I use either Lowpass 2 or Hysteresis. In Lowpass2 my settings are normally Aggressiveness 50 to 80% depending on seeing. Higher if good, lower if poor seeing. Min Move depends on seeing as reported in Guiding Assistant. Usually set to 0.2 pixels for my setup which has 2 arc sec per pixel. Max Duration is 2500msec. Both axes are set the same, no Backlash Compensation is used (set it to 0).
 
I have used all the other algorithms with success. Settings vary by scope focal length and seeing conditions. In all cases use a 1500 to 2000 Time Lapse in order to let the mount settle between guide exposures and not try to chase the seeing. An encoder mount will reverse Dec very accurately for even 1/4 arc sec move commands, but not in zero time. When the mount gets a very tiny Dec move command to reverse it will so in a controlled manner at a controlled rate. It is not instant, so the Time Lapse lets the Dec axis get there and settle before getting another small move command.
In a non-encoder mount there is a delay time, but also a crossover hysteresis where it may take 2, 3 or more small move commands before the axis actually reverses. This is different in an encoder mount where only 1 command is needed for full reversal, or any move deemed necessary by the software. For instance if the guide star is 1 arc sec off the centerline and Aggress is set to 100%, then the software sends a -1 arc sec move command, and the mount will move the axis exactly 1 arc sec, no more, no less.
In RA it's always instant because the belt tension (or gear mesh) is always on in the direction of movement. It simply slows down or speeds up. In Dec it's also instant if moving in the same direction each time, but takes some 100 +milliseconds when reversing.
Reversing Dec axis is like taking a Tylenol pill for a headache. You take 1 pill and wait for the headache to go away, and it will after a bit of time. If you don't wait and think I took one pill, still have the headache and take another and another until the headache goes away, you have overdosed yourself. The first one + time lapse delay was actually best for your health.
 
So for Dec we don't call it backlash since there isn't any when reversing. In encoder terms it's called Settling Time. There is even settling time for RA during dither recovery where the mount is commanded to move many arc seconds. For instance, if the dither is 15 arc seconds and the guide rate is 0.5x, it will take the mount approximately 2 seconds to get back to the zero line (0.5x = 7.5 arc sec per sec). If you have a guide rate set for 0.5 seconds with no Time Lapse delay dialed in, the mount will get numerous 15 arc second move commands and will indeed overshoot at the end.
 
Hope this helps.
 
Rolando
 
-----Original Message-----
From: Wayne Hixson via Groups.Io <wayneh9026@...>
To: main <main@ap-gto.groups.io>
Sent: Mon, Mar 9, 2020 9:05 am
Subject: [ap-gto] PHD2 versus ASCOM driver

Had a really good night with the Mach2 under clear but moonlit skies. PHD2 ran reasonable well with default settings, but  ran into a couple issues. First, it warned me I should disable Synchronous Pulseguide in the driver, I couldn’t find that setting and not sure I want to disable even if I could!

Second I had several times where I got a warning message that mount wasn’t responding to pulseguide commands and I had to disconnect/reconnect to resume.

We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?

wayne 


Re: Notified!😍 #mach2gto #Mach2GTO

Roland Christen
 

 
In looking at my graph without guiding input, the center of my RA trace drifted around 6.25 arc seconds in 11 minutes (in RA).    In DEC, the trace shows only  about 3.75 arc seconds of drift in 11 minutes.      The peak to peak of the each graph was similar, and more than 2.5 arc seconds P-P.     I sent this to you in a screen shot.   I expect this is telling me that the seeing was poor at best, based on these values.
The RA and Dec drift rates indicate fairly large Polar Alignment error. It means your Polemaster is giving you a significant PA error for whatever reason. That's why I don't rely on electronic devices for polar alignment. If you want the drift rate to be zero, then you have to do drift alignment where you twiddle with the Alt and Az adjusters until the drift rates are zero (which is the definition and goal of drift alignment). Ray Graylack's Pempro does that without muss or fuss in surprisingly short time. Once I have drift alignment zeroed in, I simply attach my right angle Polar scope, place Polaris at the correct point on the dial via the push-pull adjustment and I'm good to go from then on using only the Polar scope. Of course with guiding the drift doesn't matter, but for best performance it is good to have essentially zero drift. Yerkes observatory did it in the late 1800's and they had some pretty crude methods with that 40" refractor mount. But it was good enough to allow unguided imaging for considerable time exposures.
 
Every generation of astro-imagers has to go thru this learning process, and the fundamentals never change. The 2.5 arc sec P-P excursions are almost exactly what the seeing was for that night, so that will be the best you will get under those conditions. No way anything less than a $1million active guiding system along with high power laser for forming an artificial star will do any better.
 
By the way, your Vermont skies are not too bad. In the last week I had 1.2 arc sec FWHM resolution with no guiding (simple model in the keypad only) for 2 nights, then the seeing morphed into 7.5 arc sec FWHM stars when the trade winds picked up. Sky was crystal clear but stars looked like small shaggy dogs.
 
Rolando
 
 
-----Original Message-----
From: Terri Zittritsch <theresamarie11@...>
To: main <main@ap-gto.groups.io>
Sent: Mon, Mar 9, 2020 1:45 pm
Subject: Re: [ap-gto] Notified!😍 #mach2gto #mach2gto

On Sun, Mar 8, 2020 at 05:31 PM, uncarollo2 <chris1011@...> wrote:
1) Polemaster does not necessarily insure good polar alignment. Only drift alignment can reduce drift.
 
2) Having perfect polar alignment does not insure zero drift due to atmospheric refraction
 
3) doing a drift alignment can produce zero drift for both RA and Dec if you use the right method, but this zero drift will only occur in the area around the zenith. In other parts of the sky the stars do not move at sidereal rate, and will also drift slowly in Dec. This is fundamental, and no amount of polar alignment will prevent drift.
 
4) In our new keypad software we have added the King rate which reduces the RA drift in those parts of the sky where the sidereal rate is incorrect, however the King rate does not address Dec drift. We have modeling software in the new keypad which can be used to compensate for drift in both axes, and can allow unguided imaging. You can also go full model with APCC Pro, but I would recommend using that for permanent setups where you can spend some time getting a really good all-sky model.
 
Rolando 
 
Hi Rolando,
In looking at my graph without guiding input, the center of my RA trace drifted around 6.25 arc seconds in 11 minutes (in RA).    In DEC, the trace shows only  about 3.75 arc seconds of drift in 11 minutes.      The peak to peak of the each graph was similar, and more than 2.5 arc seconds P-P.     I sent this to you in a screen shot.   I expect this is telling me that the seeing was poor at best, based on these values.   I was still getting round stars (while actively guiding).   Such is life in Vermont under the jet stream!

I'm happy to report that I've successfully installed APCC, and set it up and at least tested it out without any clear sky.    Everything connects as it should.    Called George today, who was very helpful, to provided guidance on some of the finer points.    Now just waiting for clear skies.

Terri


Re: PHD2 versus ASCOM driver

Roland Christen
 

 
We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?
hello Wayne,
 
One setting I recommend for Encoder Mounts is to use a 1.5 to 2 second delay time between guide exposures. Click on the little brain in PHD2 and bring up the Advanced Setting/Camera Settings. Set the Time Lapse to 1500 to 2000. Your guide exposures can be set to anything from under 1 sec to 5 sec or more. I usually use 2 sec exposures unless the seeing is jumping around, in which case a longer exposure is used.
 
I normally use 1x Sidereal guide rate, but you can use .5x also if the seeing is good. There is no need to go slower to .25x.
 
Calibration steps are 300msec at 1x sidereal, 600msec at .5x.
 
I use either Lowpass 2 or Hysteresis. In Lowpass2 my settings are normally Aggressiveness 50 to 80% depending on seeing. Higher if good, lower if poor seeing. Min Move depends on seeing as reported in Guiding Assistant. Usually set to 0.2 pixels for my setup which has 2 arc sec per pixel. Max Duration is 2500msec. Both axes are set the same, no Backlash Compensation is used (set it to 0).
 
I have used all the other algorithms with success. Settings vary by scope focal length and seeing conditions. In all cases use a 1500 to 2000 Time Lapse in order to let the mount settle between guide exposures and not try to chase the seeing. An encoder mount will reverse Dec very accurately for even 1/4 arc sec move commands, but not in zero time. When the mount gets a very tiny Dec move command to reverse it will so in a controlled manner at a controlled rate. It is not instant, so the Time Lapse lets the Dec axis get there and settle before getting another small move command.
In a non-encoder mount there is a delay time, but also a crossover hysteresis where it may take 2, 3 or more small move commands before the axis actually reverses. This is different in an encoder mount where only 1 command is needed for full reversal, or any move deemed necessary by the software. For instance if the guide star is 1 arc sec off the centerline and Aggress is set to 100%, then the software sends a -1 arc sec move command, and the mount will move the axis exactly 1 arc sec, no more, no less.
In RA it's always instant because the belt tension (or gear mesh) is always on in the direction of movement. It simply slows down or speeds up. In Dec it's also instant if moving in the same direction each time, but takes some 100 +milliseconds when reversing.
Reversing Dec axis is like taking a Tylenol pill for a headache. You take 1 pill and wait for the headache to go away, and it will after a bit of time. If you don't wait and think I took one pill, still have the headache and take another and another until the headache goes away, you have overdosed yourself. The first one + time lapse delay was actually best for your health.
 
So for Dec we don't call it backlash since there isn't any when reversing. In encoder terms it's called Settling Time. There is even settling time for RA during dither recovery where the mount is commanded to move many arc seconds. For instance, if the dither is 15 arc seconds and the guide rate is 0.5x, it will take the mount approximately 2 seconds to get back to the zero line (0.5x = 7.5 arc sec per sec). If you have a guide rate set for 0.5 seconds with no Time Lapse delay dialed in, the mount will get numerous 15 arc second move commands and will indeed overshoot at the end.
 
Hope this helps.
 
Rolando
 
-----Original Message-----
From: Wayne Hixson via Groups.Io <wayneh9026@...>
To: main <main@ap-gto.groups.io>
Sent: Mon, Mar 9, 2020 9:05 am
Subject: [ap-gto] PHD2 versus ASCOM driver

Had a really good night with the Mach2 under clear but moonlit skies. PHD2 ran reasonable well with default settings, but  ran into a couple issues. First, it warned me I should disable Synchronous Pulseguide in the driver, I couldn’t find that setting and not sure I want to disable even if I could!

Second I had several times where I got a warning message that mount wasn’t responding to pulseguide commands and I had to disconnect/reconnect to resume.

We have another clear night expected tonight before the rains return. Any suggestions on these issues specifically or settings for PHD2 more generally?

wayne 


Re: Mach 1 Question

Dale Ghent
 

On Mar 9, 2020, at 9:31 PM, Woody Schlom <woody_is@cox.net> wrote:

I believe the optional larger shaft is shorter than the standard Mach1 shaft. But of course the larger CW’s are much larger and heavier too. And for guiding, you want a short shaft anyway.
Yeah it's shorter than the standard 1.125" shaft. It's actually a design feature of the Mach1 that you can remove the saddle from the top of the dec axis to expose the center hole that goes down through that axis, and insert the 10.7" x 1.875" cw shaft completely in there where it screws into the opposite, internal side of the same receiver that you screw the cw shaft into normally.

/dale


Re: Mach 1 Question

Bill Long
 

Yep I have a bunch of CW's for my 1100. I ordered the same size shaft that the 1100 has and the stop for it. 

Looking at the upgraded Az adjustment plate. If its a pain to adjust this, I may buy that. The mount is from 2010 so I dont think it has it stock.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Woody Schlom <woody_is@...>
Sent: Monday, March 9, 2020 6:33 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 Question
 

Bill,

 

Yes.  That’s all you need – so long as you already have the proper CW’s.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Bill Long
Sent: Monday, March 9, 2020 6:25 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Mach 1 Question

 

I picked up the long 1.875" shaft and another stop. Should be good to go. 🙂 

 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Dale Ghent <daleg@...>
Sent: Monday, March 9, 2020 6:20 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 Question

 


Grats on the expansing A-P arsenal. Yeah, you need to get one of the three varieties of 1.875" diameter CW shafts here:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fmach1-upgrades-parts%2F&amp;data=02%7C01%7C%7C7c3da4ca50b3426a3cd608d7c4913e9d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637194000400123663&amp;sdata=7Am2U6ITuCkt3FMpFKiJk54QDaWtUor10KUxkA4z5fM%3D&amp;reserved=0

If your Mach1 came with CW shaft and shaft safety stops that lack the delrin washer, ask A-P to send you a set as well.

> On Mar 9, 2020, at 8:43 PM, Bill Long <bill@...> wrote:
>
> Hey all,
>
> Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?
>
> Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.
>
> -Bill
>




Re: Mach 1 Question

Woody Schlom
 

Bill,

 

Yes.  That’s all you need – so long as you already have the proper CW’s.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Bill Long
Sent: Monday, March 9, 2020 6:25 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] Mach 1 Question

 

I picked up the long 1.875" shaft and another stop. Should be good to go. 🙂 

 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Dale Ghent <daleg@...>
Sent: Monday, March 9, 2020 6:20 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 Question

 


Grats on the expansing A-P arsenal. Yeah, you need to get one of the three varieties of 1.875" diameter CW shafts here:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fmach1-upgrades-parts%2F&amp;data=02%7C01%7C%7C7c3da4ca50b3426a3cd608d7c4913e9d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637194000400123663&amp;sdata=7Am2U6ITuCkt3FMpFKiJk54QDaWtUor10KUxkA4z5fM%3D&amp;reserved=0

If your Mach1 came with CW shaft and shaft safety stops that lack the delrin washer, ask A-P to send you a set as well.

> On Mar 9, 2020, at 8:43 PM, Bill Long <bill@...> wrote:
>
> Hey all,
>
> Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?
>
> Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.
>
> -Bill
>




Re: Mach 1 Question

Woody Schlom
 

Bill,

 

I don’t know the size of the 1100 CW’s, but I got the larger shaft for my Mach1.  I think it’s about 1 ¾” diameter.  The only other thing you might need is the endcap – if the shaft doesn’t already come with it.

 

I believe the optional larger shaft is shorter than the standard Mach1 shaft.  But of course the larger CW’s are much larger and heavier too.  And for guiding, you want a short shaft anyway.

 

Woody

 

From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Bill Long
Sent: Monday, March 9, 2020 5:43 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Mach 1 Question

 

Hey all,

 

Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?

 

Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.

 

-Bill


Re: Mach 1 Question

Bill Long
 

I picked up the long 1.875" shaft and another stop. Should be good to go. 🙂 


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Dale Ghent <daleg@...>
Sent: Monday, March 9, 2020 6:20 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] Mach 1 Question
 

Grats on the expansing A-P arsenal. Yeah, you need to get one of the three varieties of 1.875" diameter CW shafts here:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fmach1-upgrades-parts%2F&amp;data=02%7C01%7C%7C7c3da4ca50b3426a3cd608d7c4913e9d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637194000400123663&amp;sdata=7Am2U6ITuCkt3FMpFKiJk54QDaWtUor10KUxkA4z5fM%3D&amp;reserved=0

If your Mach1 came with CW shaft and shaft safety stops that lack the delrin washer, ask A-P to send you a set as well.

> On Mar 9, 2020, at 8:43 PM, Bill Long <bill@...> wrote:
>
> Hey all,
>
> Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?
>
> Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.
>
> -Bill
>





Re: Mach 1 Question

Dale Ghent
 

Grats on the expansing A-P arsenal. Yeah, you need to get one of the three varieties of 1.875" diameter CW shafts here:

https://www.astro-physics.com/mach1-upgrades-parts/

If your Mach1 came with CW shaft and shaft safety stops that lack the delrin washer, ask A-P to send you a set as well.

On Mar 9, 2020, at 8:43 PM, Bill Long <bill@outlook.com> wrote:

Hey all,

Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?

Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.

-Bill


Re: Mach 1 Question

thefamily90 Phillips
 

You just need the bar that fits the opening in the counterweight , nothing more. I have had mine for many many years and I love it!
Not sure about the scope. I use mine for AP 130 F/8.35 and AP 155 F/7 scopes. I move up to my AP 900 GOTO for my AP 10” Maksutov (first run).

Jim


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Bill Long <bill@...>
Sent: Monday, March 9, 2020 8:43:01 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: [ap-gto] Mach 1 Question
 
Hey all,

Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?

Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.

-Bill


Mach 1 Question

Bill Long
 

Hey all,

Just picked up a used Mach 1 mount to take place of my Paramount MyT I had as my second mount. Nothing against the MyT, I just like my A-P mounts better. Anyhow, I want to be able to use the existing counterweights I have for my 1100. In this case do I just need the bigger bar, and nothing more -- or do I need to replace something else as well?

Looking forward to getting this lovely used mount out for a fresh curve and some good imaging nights with the iDK. One more question would a 10" iDK weighing in at about 45-50 pounds fully loaded be fine on the Mach 1? Its a pretty compact scope, so I would think so -- but it doesnt hurt to ask.

-Bill


Re: First Clear Night with Mach2

Wayne Hixson
 

Ray, that explains it exactly - thanks! In fact I did have a new site I created and not entered the coordinates. I bet it was the active site when I booted up.


Re: First Clear Night with Mach2

Terri Zittritsch
 

Wayne,
Congratulations on getting some clear skies!     I was hoping for another night tonight myself, but alas Vermont weather doesn't cooperate often.   I found the same as you, that the mount didn't ever require more than one plate solve to get an object centered.   

Terri  


Re: Notified!😍 #mach2gto #Mach2GTO

Terri Zittritsch
 

On Sun, Mar 8, 2020 at 05:31 PM, uncarollo2 <chris1011@...> wrote:
1) Polemaster does not necessarily insure good polar alignment. Only drift alignment can reduce drift.
 
2) Having perfect polar alignment does not insure zero drift due to atmospheric refraction
 
3) doing a drift alignment can produce zero drift for both RA and Dec if you use the right method, but this zero drift will only occur in the area around the zenith. In other parts of the sky the stars do not move at sidereal rate, and will also drift slowly in Dec. This is fundamental, and no amount of polar alignment will prevent drift.
 
4) In our new keypad software we have added the King rate which reduces the RA drift in those parts of the sky where the sidereal rate is incorrect, however the King rate does not address Dec drift. We have modeling software in the new keypad which can be used to compensate for drift in both axes, and can allow unguided imaging. You can also go full model with APCC Pro, but I would recommend using that for permanent setups where you can spend some time getting a really good all-sky model.
 
Rolando 
 
Hi Rolando,
In looking at my graph without guiding input, the center of my RA trace drifted around 6.25 arc seconds in 11 minutes (in RA).    In DEC, the trace shows only  about 3.75 arc seconds of drift in 11 minutes.      The peak to peak of the each graph was similar, and more than 2.5 arc seconds P-P.     I sent this to you in a screen shot.   I expect this is telling me that the seeing was poor at best, based on these values.   I was still getting round stars (while actively guiding).   Such is life in Vermont under the jet stream!

I'm happy to report that I've successfully installed APCC, and set it up and at least tested it out without any clear sky.    Everything connects as it should.    Called George today, who was very helpful, to provided guidance on some of the finer points.    Now just waiting for clear skies.

Terri


Re: Lunar Tracking Rate #ASCOM_V2_Driver

Ray Gralak
 

After a couple of seconds, the ASCOM driver would set back to Sidereal with no errors reported.
Do you have any applications connected at the time? It could be that one of them is setting the rate back to sidereal. Any slews will also reset to rate to sidereal (APJog, for instance issues slews).

BTW, the mount's lunar rate is just an average rate. If you want to track the moon in both axes a little better consider using the Horizons application that comes with APCC.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
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 Mike Miller
Sent: Monday, March 9, 2020 12:04 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] Lunar Tracking Rate #ASCOM_V2_Driver

I was trying to do some EAA on the moon over the weekend with my Mach1, and I found that anytime I clicked the
Lunar Tracking button in the ASCOM driver, it would reset back to Sidereal after a few seconds.

Custom rate did work correctly.

My procedure this night:
1. Polar align via Sharpcap
2. Use SGP to solve and sync
3. GoTo RA/Dec of moon in APCC
4. APJog to nudge moon into center of frame
5. Press Lunar Tracking button in ASCOM driver

After a couple of seconds, the ASCOM driver would set back to Sidereal with no errors reported.


Re: First Clear Night with Mach2

Ray Gralak
 

Hi Wayne,

I did some troubleshooting and found the Actual Mount Location showed 0 latitude and 0 longitude.
I checked my site info and it was ok, but couldn't sync it to the mount. Probably missed something easy. Restarted
Latitude and Longitude can only be set one time after each power cycle. If there was no site defined the lat/long might default to 0.

Anyway, once the mount is initialized you cannot change Lat/Long unless you power cycle, which explains the behavior you were seeing.

-Ray Gralak
Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc
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 Wayne Hixson via Groups.Io
Sent: Monday, March 9, 2020 2:42 PM
To: main@ap-gto.groups.io
Subject: [ap-gto] First Clear Night with Mach2

Halleluiah - The skies opened up enough to run the Mach2, albeit with a very bright Moon in the middle of the sky
area I can see! It was one of 4 new pieces of gear I was hoping to actually try after the long cloudy period - the
QHY Polemaster, Optec Saggita OAG, QHY 268C OSC camera, and the Mach2. I'll focus (pun intended) on the
Mach2. Note this is based on a very limited experience, but the mount has lived up to my expectations and even
surprised me with some features

Summary:
- I got through all the testing I'd planned by 12:30 - a first!
- The encoders' capability to keep track of the scopes position is a godsend.
- The ability to loosen and tighten clutches and altitude by hand only is a pleasant unanticipated surprise
- Motors are quiet and fast, even at 12v
- Guiding seems improved

I run the system remotely (100 ft from the dining room to the deck) with a Primaluce Eagle 3S mounted atop a
130GTX. I'm using USB through-the-mount to connect to the GTOCP5. Did a rough alignment with the
Polemaster - nice to have that built-in attach point. The altitude adjuster is easier to use than on my AP1100,
being only two larger knobs instead of 4 smaller ones to loosen and lock the axis. No wrenches required.

I did a GOTO the Moon, but I saw from the APCC model that t was going the wrong way. I ran to the deck and
found the mount stopped because the camera USB cable had impacted the top of the railing. Darn camera is
really long! One pleasant finding was the USB cable on the camera was not bent or damages when it impacted
as I had set the clutches by hand only and the controller may have sensed the impact and stopped. And since the
mount retains its location, I loosened the clutch and repositioned the mount and didn't have to do any manual re-
park, unpark and re-sync operation.

I did some troubleshooting and found the Actual Mount Location showed 0 latitude and 0 longitude. I checked my
site info and it was ok, but couldn't sync it to the mount. Probably missed something easy. Restarted CP5 and PC
and all was OK again. Even after all that, a GOTO the Moon put the moon in the camera FoV. Note: I had a similar
issue with the CP4 and the AP1100 in that sometimes it would show an altitude of zero when the mount was in
Park 3. This always seemed to be on initial start up and was rare.

The rest of the evening was spent first in camera testing (plate solves, V- curves, focusing and live image
stacking). The mount responded to all demands. My software (Voyager) does precise GOTOs for targets and focus
stars. Never once did it require more than one extra plate solve to pinpoint the location and mostly it was close
enough the first time.

Finally connected to PHD2 and used default settings. I know Roland had some suggested settings but I didn't
have them handy so just rolled with it. I use an Ultrastar guide camera. Did a calibration in several different
locations and always got RMS of under one arcsecond.

Finally ran Sharpcap and did some live stacking of M53. Ran about 30 minutes with guiding and even though the
sky was really washed out by moonlight every frame stacked

Parked and shut everything down. Very pleased with this first admittedly limited experience. Hope to try more
tonight!

Wayne

10781 - 10800 of 79702