Re: PEC Curves vs. Payloads
Thanks Brian. I will check to see if I saved my PHD logs in a usable fashion. Please note the guiding is better with the heavier payload, which is the reverse of the that rule of thumb thing. I always recheck the brain in PHD2 to make sure the camera pixel width, and focal length are correct. The 80mm guide scope has a third? Losmandy scope ring around the focuser outlet, whereas the 50mm does not, so flexure might be a factor.
|
Re: PEC Curves vs. Payloads
As an added thought, balance will affect overall performance. so of course you want to make sure whatever you are using is reasonably balanced
Brian
On Mon, Aug 17, 2020 at 5:46 PM Brian Valente via <bvalente= [email protected]> wrote: Hi John
I don't think weight has any effect on the periodic error.
It would probably help if you uploaded some representative PHD logs to review, who knows why one is better than the other. It's possible it could be the smaller guidescope, but could also be how the guiding assembly is attached, the configuration of your guiding parameters, etc.
On Mon, Aug 17, 2020 at 5:38 PM John Kmetz < jjkmetz54@...> wrote: Hello all:
The recent discussions on PEC curves had led me to some thinking. Do I need to redo the PEC curves when I change payloads? During the winter I primarily use my Celestron C925 Edge HD, especially for galaxy season. And then in the summer I switch to my Explore Scientific ES102mm, for capturing nebulae. As a rough statement I will say the the latter apparatus with counterweights is only half the weight of the former. With the C925 I use an 80mm guide scope with the ES102, a 50mm guide scope. The G11G (w. Gemini 2) I'm using has a one piece worm as far as I know, but I have yet to take it apart in my 3 years of ownership.
Often my best guiding with the C925 is around 0.5 arcsec, while with the ES102 it is about 0.7 arcsec. My assumption was that the smaller guide scope would lead to greater guiding error. But now I am considering whether the total weight could effect the way the gears mesh together, strain on the motors, effects from load balance, etc.
PEMPro is where I get my curves which are then uploaded to the Gemini 2 unit. The best answer would be better safe than sorry and just redo. But other payload combinations are also used and I'm wondering how much weight change makes a difference. Any suggestions or thoughts would be appreciated. I go east heavy in RA, and camera heavy in Dec. Guiding is about the same on either side of the meridian, and best closer to zenith.
Thanks,
John
--
Brian?
Brian Valente portfolio
-- Brian?
Brian Valente portfolio
|
Re: PEC Curves vs. Payloads
Hi John
I don't think weight has any effect on the periodic error.
It would probably help if you uploaded some representative PHD logs to review, who knows why one is better than the other. It's possible it could be the smaller guidescope, but could also be how the guiding assembly is attached, the configuration of your guiding parameters, etc.
On Mon, Aug 17, 2020 at 5:38 PM John Kmetz < jjkmetz54@...> wrote: Hello all:
The recent discussions on PEC curves had led me to some thinking. Do I need to redo the PEC curves when I change payloads? During the winter I primarily use my Celestron C925 Edge HD, especially for galaxy season. And then in the summer I switch to my Explore Scientific ES102mm, for capturing nebulae. As a rough statement I will say the the latter apparatus with counterweights is only half the weight of the former. With the C925 I use an 80mm guide scope with the ES102, a 50mm guide scope. The G11G (w. Gemini 2) I'm using has a one piece worm as far as I know, but I have yet to take it apart in my 3 years of ownership.
Often my best guiding with the C925 is around 0.5 arcsec, while with the ES102 it is about 0.7 arcsec. My assumption was that the smaller guide scope would lead to greater guiding error. But now I am considering whether the total weight could effect the way the gears mesh together, strain on the motors, effects from load balance, etc.
PEMPro is where I get my curves which are then uploaded to the Gemini 2 unit. The best answer would be better safe than sorry and just redo. But other payload combinations are also used and I'm wondering how much weight change makes a difference. Any suggestions or thoughts would be appreciated. I go east heavy in RA, and camera heavy in Dec. Guiding is about the same on either side of the meridian, and best closer to zenith.
Thanks,
John
-- Brian?
Brian Valente portfolio
|
Hello all:
The recent discussions on PEC curves had led me to some thinking. Do I need to redo the PEC curves when I change payloads? During the winter I primarily use my Celestron C925 Edge HD, especially for galaxy season. And then in the summer I switch to my Explore Scientific ES102mm, for capturing nebulae. As a rough statement I will say the the latter apparatus with counterweights is only half the weight of the former. With the C925 I use an 80mm guide scope with the ES102, a 50mm guide scope. The G11G (w. Gemini 2) I'm using has a one piece worm as far as I know, but I have yet to take it apart in my 3 years of ownership.
Often my best guiding with the C925 is around 0.5 arcsec, while with the ES102 it is about 0.7 arcsec. My assumption was that the smaller guide scope would lead to greater guiding error. But now I am considering whether the total weight could effect the way the gears mesh together, strain on the motors, effects from load balance, etc.
PEMPro is where I get my curves which are then uploaded to the Gemini 2 unit. The best answer would be better safe than sorry and just redo. But other payload combinations are also used and I'm wondering how much weight change makes a difference. Any suggestions or thoughts would be appreciated. I go east heavy in RA, and camera heavy in Dec. Guiding is about the same on either side of the meridian, and best closer to zenith.
Thanks,
John
|
Re: Valid Guide Rates for PEC on Gemini Level 4
I think Paul's ideas might be close to the mark. I still don't quite "see" the issue in my mind's eye yet.
I think now that the autoguide speed really applies to using PEC and Autoguiding actively AFTER the PEC curve has
been generated. The autoguide speed has zero to do with taking the PE data. It can't because the video camera is
just capturing the target star location in its image plane. No autoguiding pulses are used at all in taking that tracking
data. That's incorrect if you are using an autoguider to program PEC data. The autoguider keeps the star centered so it MUST send pulse guide commands via the ASCOM interface. The Gemini moves the mount and keeps track of the movement at that autoguider rate. What gets stored are indicators to move forward or backward (at autoguider speed) at each internal clock "tick". Gemini PEC data is recorded based on the autoguide speed. If you change the autoguide speed after collecting periodic error playback will be either under or over-emphasized. Also, when recording and averaging multiple cycles via an autoguider there are other problems besides seeing. You are also inherently introducing phase error from camera delay as well as potential periodic error from uncorrectable frequencies (like the 3.15x frequency). This will lead to an inferior PEC curve, even when averaged. BTW, that was my mistake reducing the autoguider rates to just two options (0.3x and 0.5x). I'll restore the full range in the next PEMPro build. -Ray Gralak Author of APCC (Astro-Physics Command Center): Author of PEMPro V3: Author of Astro-Physics V2 ASCOM Driver: -----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Herman
Sent: Monday, August 17, 2020 4:06 PM
To: [email protected]
Subject: Re: [Losmandy_users_io] Valid Guide Rates for PEC on Gemini Level 4
Thank you for those answers.
I think Paul's ideas might be close to the mark. I still don't quite "see" the issue in my mind's eye yet.
I think now that the autoguide speed really applies to using PEC and Autoguiding actively AFTER the PEC
curve has been generated. The autoguide speed has zero to do with taking the PE data. It can't because the
video camera is just capturing the target star location in its image plane. No autoguiding pulses are used at all
in taking that tracking data.
So the autoguide speed recommendation must have to do after, with PEC turned on. Then I can see how the
autoguide rate might come into play.
However, if the corrections needed to be very fast, say for a very sharp worm or coupler induced error, the
faster your autoguide rate that is "allowed" by Gemini would be able to counteract such severe trouble.
However, in my PEC experience, you want to "smooth out" any sharp impulses. That is why the Gemini-1
provides for you to run multiple PE runs, so the software can just average out the corrections. You do not want
to be "chasing the seeing" as the saying goes.
If you look at the PEC curves that typically go from -2 arcsec to + 2 arcsec over a worm period (4 minutes on
G11) you would not need a very fast autoguide speed, so limiting that to 0.5 sidereal is sensible. Anyway it will
also matter if your FL is very high...so you are more sensitive to star movement. At that point you might want
to allow the autoguider to move the mount faster, at 0.8 of sidereal maybe.
It's all one big experiment for us observers.
Have fun, stay well, and (the lastest issue:thunderstorms!) hope your power stays on!
Michael
On Mon, Aug 17, 2020 at 2:44 PM Brian Valente <bvalente@...> wrote:
UPDATE:
The 0.3x and 0.5x from the documentation are incorrect - those are values from the 492 controller, not
the Gemini.
Brian
On Mon, Aug 17, 2020 at 2:00 PM Paul Kanevsky <yh@...> wrote:
On Mon, Aug 17, 2020 at 04:39 PM, Michael Herman wrote:
So...can someone explain why "autoguide rate" has something to do with PEC?
Hi Michael,
Recording PE data doesn't require knowing the guide rate. Programming PEC data into Gemini -
does.
If you are programming PEC manually (using HC or autoguider corrections) then the corrections
recorded are relative to the guide rate. If you change the guide rate, the correction rates will also need to be
adjusted during PEC playback, and Gemini doesn't do this automatically. So, whatever rate you recorded and
programmed PEC is the rate you should use for PEC playback.
When PEC is programmed from the PC, say using PemPro, the corrections are also sent as the
number of pulses needed for each of the corrections. This is also based on the guiding speed: if the speed is
higher, then fewer pulses are needed, if lower -- more pulses. If the guiding speed is changed after the
programming, the number of pulses of corrections will no longer be right and the corrections will be either faster
or slower than what was programmed.
Regards,
-Paul
--
Brian
Brian Valente
portfolio brianvalentephotography.com <>
--
Michael Herman
mobile: 408 421-1239
email: mherman346@...
|
Re: Storing Losmandy G11G DEC horizontally
Thank you Brian,
Sent from my Galaxy Tab A
toggle quoted message
Show quoted text
-------- Original message --------
From: Brian Valente <bvalente@...>
Date: 8/17/20 5:09 PM (GMT-06:00)
Subject: Re: [Losmandy_users_io] Storing Losmandy G11G DEC horizontally
Hi Deric
horizontal is totally fine
many observatories park it horizontally due to height restrictions
Hello everyone,
It is my understanding that it is best to keep a SCT stored vertically Collector plate up and secondary mirror set all the way back. If I keep it mounted on the G11. Is it okay to keep the DEC and counter weight parked in the horizontal position ? Does this
put stress on the worm gear???
Other than this off the wall question every thing with my G11G is working like a champ. I had a rough start but got it together thanks to everyone here and especially Brian.
THANK YOU
HAPPY SKIES AND KEEP LOOKING UP
--
Brian?
Brian Valente
portfolio
|
Re: Valid Guide Rates for PEC on Gemini Level 4
Thank you for those answers.
I think Paul's ideas might be close to the mark.? I still don't quite "see" the issue in my mind's eye yet. I think now that the autoguide speed really applies to using PEC and Autoguiding actively AFTER the PEC curve has been generated.? The autoguide speed has zero to do with taking the PE data.? It can't because the video camera is just capturing the target star location in its image plane.? No autoguiding pulses are used at all in taking that tracking data.
So the?autoguide speed recommendation must have to do after, with PEC turned on.? Then I can see how the?autoguide rate might come into play.??
However, if the corrections needed to be very fast, say for a very sharp worm or coupler induced error, the faster your autoguide rate that is "allowed" by Gemini would be able to counteract such severe trouble.? However, in my PEC experience, you want to "smooth out" any sharp impulses. That is why the Gemini-1 provides for you to run multiple PE runs, so the software can just average out the corrections.? You do not want to be "chasing the seeing" as the saying goes.??
If you?look at the PEC curves that typically go from -2 arcsec to?+ 2 arcsec over a worm period (4 minutes on G11) you would not need a very fast autoguide speed, so limiting that to 0.5 sidereal is sensible.? Anyway it will also matter if your FL is very high...so you are more sensitive to star movement.? At that point you might want to allow the autoguider to move the mount faster, at 0.8 of sidereal maybe.??
It's all one big experiment for us observers.
Have fun, stay well, and (the lastest issue:thunderstorms!)?hope your power stays on!
Michael
On Mon, Aug 17, 2020 at 2:44 PM Brian Valente < bvalente@...> wrote: UPDATE: The 0.3x and 0.5x from the documentation are incorrect - those are values from the 492 controller, not the Gemini.
Brian
On Mon, Aug 17, 2020 at 2:00 PM Paul Kanevsky < yh@...> wrote: On Mon, Aug 17, 2020 at 04:39 PM, Michael Herman wrote:
So...can someone explain why "autoguide rate" has something to do with PEC??
Hi Michael,
Recording PE data doesn't require knowing the guide rate. Programming PEC data into Gemini - does.
If you are programming PEC manually (using HC or autoguider corrections) then the corrections recorded are relative to the guide rate. If you change the guide rate, the correction rates will also need to be adjusted during PEC playback, and Gemini doesn't do this automatically. So, whatever rate you recorded and programmed PEC is the rate you should use for PEC playback.
When PEC is programmed from the PC, say using PemPro, the corrections are also sent as the number of pulses needed for each of the corrections. This is also based on the guiding speed: if the speed is higher, then fewer pulses are needed, if lower -- more pulses. If the guiding speed is changed after the programming, the number of pulses of corrections will no longer be right and the corrections will be either faster or slower than what was programmed.
Regards,
? ?-Paul
--
Brian?
Brian Valente portfolio
|
Re: Storing Losmandy G11G DEC horizontally
Hi Deric
horizontal is totally fine
many observatories park it horizontally due to height restrictions
Hello everyone,
It is my understanding that it is best to keep a SCT stored vertically Collector plate up and secondary mirror set all the way back. If I keep it mounted on the G11. Is it okay to keep the DEC and counter weight parked in the horizontal position ? Does this put stress on the worm gear???
Other than this off the wall question every thing with my G11G is working like a champ. I had a rough start but got it together thanks to everyone here and especially Brian.
THANK YOU
HAPPY SKIES AND KEEP LOOKING UP
-- Brian?
Brian Valente portfolio
|
Storing Losmandy G11G DEC horizontally
Hello everyone,
It is my understanding that it is best to keep a SCT stored vertically Collector plate up and secondary mirror set all the way back. If I keep it mounted on the G11. Is it okay to keep the DEC and counter weight parked in the horizontal position ? Does this put stress on the worm gear???
Other than this off the wall question every thing with my G11G is working like a champ. I had a rough start but got it together thanks to everyone here and especially Brian.
THANK YOU
HAPPY SKIES AND KEEP LOOKING UP
|
Re: Valid Guide Rates for PEC on Gemini Level 4
UPDATE: The 0.3x and 0.5x from the documentation are incorrect - those are values from the 492 controller, not the Gemini.
Brian
On Mon, Aug 17, 2020 at 2:00 PM Paul Kanevsky < yh@...> wrote: On Mon, Aug 17, 2020 at 04:39 PM, Michael Herman wrote:
So...can someone explain why "autoguide rate" has something to do with PEC??
Hi Michael,
Recording PE data doesn't require knowing the guide rate. Programming PEC data into Gemini - does.
If you are programming PEC manually (using HC or autoguider corrections) then the corrections recorded are relative to the guide rate. If you change the guide rate, the correction rates will also need to be adjusted during PEC playback, and Gemini doesn't do this automatically. So, whatever rate you recorded and programmed PEC is the rate you should use for PEC playback.
When PEC is programmed from the PC, say using PemPro, the corrections are also sent as the number of pulses needed for each of the corrections. This is also based on the guiding speed: if the speed is higher, then fewer pulses are needed, if lower -- more pulses. If the guiding speed is changed after the programming, the number of pulses of corrections will no longer be right and the corrections will be either faster or slower than what was programmed.
Regards,
? ?-Paul
-- Brian?
Brian Valente portfolio
|
Re: Valid Guide Rates for PEC on Gemini Level 4
Hi Michael
Rene is the best person to answer this, but here are a few tidbits of my understanding
When you record PEC using a third party tool like PEMPro, the guide rate affects the speed at which corrections are applied (i'm not sure if it's in the capture, the playback, or both). First part is when you gather the data and then upload to the mount, Gemini needs to be at the same guide rate.?
Then when you're guiding, the guide rate needs to be at the same value as well. if you decide you want to guide at a different rate, you need to disable PEC or re-do it at the new rate. ?
for built-in PEC training, i'm not sure how much the above applies
On Mon, Aug 17, 2020 at 1:39 PM Michael Herman < mherman346@...> wrote: I always learn something new on this forum. I presently avoid needing PEC by the few improvements I made to the RA drive. That hot PE down to the 1 arcsec RMS (~2.4 arcsec Peak to Peak) range, typical of my area's seeing.? I do use autoguiding at 0.5x Sidereal rate to correct other errors like polar alignment error/drift.??
Earlier, I did use the Gemini-1 built in PEC training and built in PEC averaging .? It worked fine.??
However, from this thread, I really don't understand why the autoguide rate has anything at all to do with PEC training.? The autoguider is turned off during PEC data acquisition.? The "autoguide" camera is only used to "watch" the tracked star's RA position during sidereal tracking.? You could even be tracking the star with 2 or 3 second exposures.??
The PEC is fitted to the recorded unguided tracking data later, by either the Gemini built in software or the external PC software.??
So...can someone explain why "autoguide rate" has something to do with PEC??
Thanks, Michael
On Mon, Aug 17, 2020, 12:24 PM Brian Valente < bvalente@...> wrote: Update:
i found that reference in the documentation.
i checked with Ray, i think that may be out of date. the valid range is 0.2x - 0.8x
however, I really recommend you stick with 0.5x for two reasons
1. it's the best balance between slower speed (better for PEC) and faster speed (better for guiding)
2. there may be some parts of the code that are hard-coded to 0.5x. i don't know this for sure, i've only heard this in passing, so it may not be true. So the recommendation is 0.5x
also FYI if you change your guidespeed at any time, you will need to redo your PEC to match the guidespeed
Brian
I have always used 0.8x as the guide rate when training PEC on my G11 with Gemini 1 Level 4.? I was just looking at the Gemini instructions in PEMPro V3 and it has this warning:? The Gemini firmware only supports 0.3x and 0.5x guide rates - 0.5x is recommended.? This conflicts with the description of command ID 502, Guide Speed used for training PEC, in the Gemini Level 4 Users Manual.? That seems to indicate the full 0.2x, 0.5x, and 0.8x range is valid.? Which is it?
--
Brian?
Brian Valente portfolio
-- Brian?
Brian Valente portfolio
|
Re: Valid Guide Rates for PEC on Gemini Level 4
On Mon, Aug 17, 2020 at 04:39 PM, Michael Herman wrote:
So...can someone explain why "autoguide rate" has something to do with PEC??
Hi Michael, Recording PE data doesn't require knowing the guide rate. Programming PEC data into Gemini - does. If you are programming PEC manually (using HC or autoguider corrections) then the corrections recorded are relative to the guide rate. If you change the guide rate, the correction rates will also need to be adjusted during PEC playback, and Gemini doesn't do this automatically. So, whatever rate you recorded and programmed PEC is the rate you should use for PEC playback. When PEC is programmed from the PC, say using PemPro, the corrections are also sent as the number of pulses needed for each of the corrections. This is also based on the guiding speed: if the speed is higher, then fewer pulses are needed, if lower -- more pulses. If the guiding speed is changed after the programming, the number of pulses of corrections will no longer be right and the corrections will be either faster or slower than what was programmed. Regards, ? ?-Paul
|
Re: Valid Guide Rates for PEC on Gemini Level 4
I always learn something new on this forum. I presently avoid needing PEC by the few improvements I made to the RA drive. That hot PE down to the 1 arcsec RMS (~2.4 arcsec Peak to Peak) range, typical of my area's seeing.? I do use autoguiding at 0.5x Sidereal rate to correct other errors like polar alignment error/drift.??
Earlier, I did use the Gemini-1 built in PEC training and built in PEC averaging .? It worked fine.??
However, from this thread, I really don't understand why the autoguide rate has anything at all to do with PEC training.? The autoguider is turned off during PEC data acquisition.? The "autoguide" camera is only used to "watch" the tracked star's RA position during sidereal tracking.? You could even be tracking the star with 2 or 3 second exposures.??
The PEC is fitted to the recorded unguided tracking data later, by either the Gemini built in software or the external PC software.??
So...can someone explain why "autoguide rate" has something to do with PEC??
Thanks, Michael
On Mon, Aug 17, 2020, 12:24 PM Brian Valente < bvalente@...> wrote: Update:
i found that reference in the documentation.
i checked with Ray, i think that may be out of date. the valid range is 0.2x - 0.8x
however, I really recommend you stick with 0.5x for two reasons
1. it's the best balance between slower speed (better for PEC) and faster speed (better for guiding)
2. there may be some parts of the code that are hard-coded to 0.5x. i don't know this for sure, i've only heard this in passing, so it may not be true. So the recommendation is 0.5x
also FYI if you change your guidespeed at any time, you will need to redo your PEC to match the guidespeed
Brian
I have always used 0.8x as the guide rate when training PEC on my G11 with Gemini 1 Level 4.? I was just looking at the Gemini instructions in PEMPro V3 and it has this warning:? The Gemini firmware only supports 0.3x and 0.5x guide rates - 0.5x is recommended.? This conflicts with the description of command ID 502, Guide Speed used for training PEC, in the Gemini Level 4 Users Manual.? That seems to indicate the full 0.2x, 0.5x, and 0.8x range is valid.? Which is it?
--
Brian?
Brian Valente portfolio
|
Re: Valid Guide Rates for PEC on Gemini Level 4
Update:
i found that reference in the documentation.
i checked with Ray, i think that may be out of date. the valid range is 0.2x - 0.8x
however, I really recommend you stick with 0.5x for two reasons
1. it's the best balance between slower speed (better for PEC) and faster speed (better for guiding)
2. there may be some parts of the code that are hard-coded to 0.5x. i don't know this for sure, i've only heard this in passing, so it may not be true. So the recommendation is 0.5x
also FYI if you change your guidespeed at any time, you will need to redo your PEC to match the guidespeed
Brian
I have always used 0.8x as the guide rate when training PEC on my G11 with Gemini 1 Level 4.? I was just looking at the Gemini instructions in PEMPro V3 and it has this warning:? The Gemini firmware only supports 0.3x and 0.5x guide rates - 0.5x is recommended.? This conflicts with the description of command ID 502, Guide Speed used for training PEC, in the Gemini Level 4 Users Manual.? That seems to indicate the full 0.2x, 0.5x, and 0.8x range is valid.? Which is it?
-- Brian?
Brian Valente portfolio
|
Re: Valid Guide Rates for PEC on Gemini Level 4
Hi?sbasprez
you should be fine with up to 0.8x, although 0.5x is definitely recommended
Where did you see this error? I am in PEMPro now (and have used it for years) and never ran across that error message, regardless of what guide rate i put in
Brian
I have always used 0.8x as the guide rate when training PEC on my G11 with Gemini 1 Level 4.? I was just looking at the Gemini instructions in PEMPro V3 and it has this warning:? The Gemini firmware only supports 0.3x and 0.5x guide rates - 0.5x is recommended.? This conflicts with the description of command ID 502, Guide Speed used for training PEC, in the Gemini Level 4 Users Manual.? That seems to indicate the full 0.2x, 0.5x, and 0.8x range is valid.? Which is it?
-- Brian?
Brian Valente portfolio
|
Valid Guide Rates for PEC on Gemini Level 4
I have always used 0.8x as the guide rate when training PEC on my G11 with Gemini 1 Level 4.? I was just looking at the Gemini instructions in PEMPro V3 and it has this warning:? The Gemini firmware only supports 0.3x and 0.5x guide rates - 0.5x is recommended.? This conflicts with the description of command ID 502, Guide Speed used for training PEC, in the Gemini Level 4 Users Manual.? That seems to indicate the full 0.2x, 0.5x, and 0.8x range is valid.? Which is it?
|
Re: How to pause a 492 digital drive
On Fri, Aug 14, 2020 at 08:41 AM, Les Niles wrote:
While I appreciate the theoretical interest, the luddite in me still asks, what is gained by inhibiting the RA motor output, vs. just shutting off power to the 492?
Throwing the slide switch is going to disturb the mount. But I see no reason a normally on (closed) momentary switch can't be wired into the power switch and be used to cut power when desired.?
|
Re: How to pause a 492 digital drive
Another idea to consider:
I thought that the autoguider or motor motion in RA rate of 1X just shuts off the RA motor if it is trying to "slew" in one direction, else 2X sidereal in the other direction.? ? If so perhaps there is a software approach to having RA stand still...
Have fun, Michael
On Fri, Aug 14, 2020, 3:21 PM John Desbiens via <jdlittlewing= [email protected]> wrote: Yea it looks like an RA power interrupt switch on the hand controller is the ticket. Allowing it to track on an alt/az mount moves the object out of the fov faster than if it was off.
Anyway the 492 works pretty nice with encoders, nexus, and sky safari 6. Manual controls induced hesitation, stuttering and backlash. Not to mention the 492 keeps my hands off the mount.
Thanks Everybody,
John
|
Re: How to pause a 492 digital drive
Yea it looks like an RA power interrupt switch on the hand controller is the ticket. Allowing it to track on an alt/az mount moves the object out of the fov faster than if it was off.
Anyway the 492 works pretty nice with encoders, nexus, and sky safari 6. Manual controls induced hesitation, stuttering and backlash. Not to mention the 492 keeps my hands off the mount.
Thanks Everybody,
John
|
Re: Polemaster Adapter for Titan Mounts
Donald,
Anything you can do to make using the scope and mount easier and more accessible will improve the number of observing sessions you get per year, trust me! Before I got the Wheelie Bar and plopped the LWT from the GM8 on it to carry the GM8 or G11 depending on the scope I basically very rarely observed from the driveway unless I could see that the conditions were going to be spectacular. With the Wheelie Bar I leave the GM8 and FC-100DL (or whatever scope I left in the saddle) setup and covered ready for a quick look at the night sky. I takes me maybe 15 minutes to get it setup and polar aligned well enough to have the GOTOS be close enough to see in a longer eyepiece. Then a Gemini sync command and I'm off to the GOTO races. Don't worry about leaving it setup and ready to go good quality gear should not be significantly affected by heat or cold.?
--
Chip Louie - Chief Daydreamer Imagination Hardware
|
Michael Herman
Paul Kanevsky
Chip Louie