|
Re: PEMpro V3 how to make a curve? step by step please.
I'll email him - he's helped before via team viewer. but currently - I'm kinda in limbo. My imaging camera was in for repair. I just got a email that it's back in the US at my dealer. I will have it back installed early next week. Once I get my gear reconfigured. I will test again and if need be will contact George again.
On Tue, Dec 5, 2017 at 4:09 PM, chris1011@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: AP900 RA Slew noise
It's not on the web site. You have to
call.
-Christopher Erickson
Observatory engineer Summit Kinetics
From: ap-gto@... [mailto:ap-gto@...] Sent: Tuesday, December 5, 2017 7:16 PM To: ap-gto@... Subject: Re: [ap-gto] Re: AP900 RA Slew noise
|
|
|
|
Re: AP900 RA Slew noise
calypte@...
I don't see this listed on the A-P website.
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Ray Gralak
PHD2 has a cool "Calibration Step Calculator" to calculate for the best Calibration step size in millisecondsCool "Calibration Step Calculator"? I think that PHD2 uses a calibration step size because it doesn't have the sophistication to detect the starting/ending star fields like commercial apps like Maxim, CCDSoft, TheSkyX, etc. Those apps don't need a "cool Calibration step calculator". (Just saying :-) -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro: http://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: http://www.gralak.com/apdriver Author of PulseGuide: http://www.pulseguide.com Author of Sigma: http://www.gralak.com/sigma -----Original Message-----
|
|
|
|
Re: AP900 RA Slew noise
Astrobob
Today I ordered Rolando's grease mix from AP for my AP1200 and according to George it'll work for the gear boxes as well as worm gears. The price is right and there's enough for more than just one application. I was a crew chief in the USAF and I learned the value of lubrication well. Bob
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Worsel
PHD2 calculates the appropriate calibration duration, given Guidescope focal length, guide camera pixel size in order to calculate guider pixel scale Guide speed as fraction of sidereal, default is 1.00 Number of calibration steps, default is 12 Calibration star declination (manual entry or retrieved automatically if an ASCOM mount) I assume that PHD2 has a movement criteria in arc-sec in order to calculate the length of each cal step. I do not know the criteria. My equipment: 80 mm f/6 OTA with 2.5x Barlow, and ST-i camera Calculates that, for the above, a cal duration of 250 ms for 12 steps = 3 s total. At sidereal rate (360 degrees/23.9344699 hours in a sidereal day)=(15.04 arc-sec/sec). In 10 seconds, the star would move ~150 a-s. This assumes the star is roughly at meridian and equator. In 3 s, the move will be ~45 a-s. You can enter a cal duration manually, if deemed necessary. Bryan
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Suresh Mohan
Yes : default values , don’t touch them except what is told by the guiding assistant
toggle quoted messageShow quoted text
Suresh
On 06-Dec-2017, at 1:05 AM, marfig1970@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: AP900 RA Slew noise
Ok. Thanks for the info. Don Anderson
From: "chris1011@... [ap-gto]" To: ap-gto@... Sent: Tuesday, December 5, 2017 9:07 AM Subject: Re: [ap-gto] Re: AP900 RA Slew noise While Lubriplate is a good lubricant, it is actually a bit on the thin side and was not originally intended for gears. It works if you do regular re-greasing, but doesn't really work long term because it tends to wipe away easily. Aeroshell 33 is a better grease for both the worms and spur gears.
Rolando
-----Original Message----- From: Don Anderson jockey_ca@... [ap-gto] To: ap-gto Sent: Mon, Dec 4, 2017 11:11 pm Subject: Re: [ap-gto] Re: AP900 RA Slew noise The first and last time I lubed my 2009 AP9000GOTO, I used Lubriplate 105. Is this still an ok grease to use? I did get a small amount of Aeroshell 33 from a friend. I was intending to regrease the worms on RA and Dec this winter. I was going to re do the gearboxes with the Aeroshell 33 as well. Is this not advised?
Don Anderson
From: "chris1011@... [ap-gto]" gto@...> To: ap-gto@... Sent: Monday, December 4, 2017 6:55 PM Subject: Re: [ap-gto] Re: AP900 RA Slew noise I have not yet seen Roland's secret sauce gear grease I brought you a small tub, did you already lose it?
Rolando
-----Original Message-----
From: 'Christopher Erickson' christopher.k.erickson@... [ap-gto] gto@...> To: ap-gto gto@...> Sent: Mon, Dec 4, 2017 6:59 pm Subject: RE: [ap-gto] Re: AP900 RA Slew noise Aeroshell 33 for the worm gears and
wheels.
"Roland's secret sauce gear grease" for the bores, brass
shoulder bolts and gear teeth of the spur gears under the axis
motor assembly covers.
I have not yet seen Roland's secret sauce gear grease
because he didn't bring any with him to Hawaii.
I have been using Z164 heavy duty gear grease in the AP spur
gears, which is designed for high-torque R/C model
gearboxes.
I don't know how Z164 compares to Roland's secret
sauce.
I hope this helps!
-Christopher Erickson
Observatory engineer Summit Kinetics From: ap-gto@... [mailto:ap-gto@...] Sent: Monday, December 4, 2017 1:56 PM To: ap-gto@... Subject: RE: [ap-gto] Re: AP900 RA Slew noise could you please clarify "gearbox grease (different than worm lube)"?
If AP "secret sauce" or Aeroshell 33 non-MS are to be used for gearbox
grease what should be used for worm lube?
Milan
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
topboxman
Hi Rolando,
toggle quoted messageShow quoted text
This is what PHD2 "Calibration Step Calculator"is for. No more guessing for calibration step size and it's pretty accurate. Never had an issue with this using my A-P1100GTO mount. The calculator takes into account of Declination of guide star as well as other parameters so that proper calibration step size will be calculated correctly. Peter ---In ap-gto@..., <chris1011@...> wrote : Yes I know it's different, but you still have to move the scope a certain distance in Dec in order to get proper values for the program. We have dealt with several customers now who did not understand what calibration does and ended up with bogus results. The guiding was totally off because the mount was being yanked back and forth with oversize error signals. Anyhow, the mount will do as you ask, no more no less. Rolando
-----Original Message-----
From: pnagy@... [ap-gto] <ap-gto@...> To: ap-gto <ap-gto@...> Sent: Tue, Dec 5, 2017 5:02 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? PHD2 is a totally different animal than other guiding software like Maxim DL and the names (i.e. calibration steps) and parameters are not likely going to agree or match. PHD2 has a cool "Calibration Step Calculator" to calculate for the best Calibration step size in milliseconds based on declination of guide star, focal length of guide scope, pixel size of guide camera and mount's guide speed. Use this instead of guessing and will NOT agree with Maxim auto guiding parameters. Click on the "Brain" icon, click on "Guiding" tab and finally click on "Calculate" button and it will pop up a window for you to fill in the blanks. Peter ---In ap-gto@..., <chris1011@...> wrote : The total distance traveled should be on the order of 150 arc sec. That is
equivalent to 10 seconds of move command at 1x in any other guide software and would move the star enough to accurately calculate the pixel/sec move parameter. A total of 10 seconds move command is normal in MaximDL and is done in one step in that program. In your example of 714mm, 3.8 micron pixel size, you are running at 1.1 arc sec per pixel. The resultant pixel/sec parameter would be 13.7 pixels per second at 1x sidereal. The reason for the 10 second cal run in MaximDL is to minimize the delay error in reversing Dec. If it takes 1 second to reverse Dec, then the parameter would be in error by 10%, which is not a big problem. If the cal run was only for 3 seconds, then the resultant error is 33%, which is quite large, and any setting of aggressiveness above 70% will begin to cause oscillations because the loop gain is now above 100%. It may be that PHD can compensate for this reversal delay in Dec by doing calibration only in one direction. I'm not familiar with the workings of the software, I only know how it was done in all the other programs. Rolando -----Original Message----- From: Zac Kruger z@... [ap-gto] <ap-gto@...> To: ap-gto <ap-gto@...> Sent: Tue, Dec 5, 2017 4:04 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Roland, Have you successfully used PHD to attempt calibration over the recommended 150 arc sec? Using an OAG at 714mm FL and 3.8u pixel size I have been entirely unsuccessful because of what I assume is due to the way PHD functions. It loses track of the star when using such large calibration steps. I have to be somewhere at 150-250ms pulses in order to calibrate at all. Doing that to cover 150'' would require an immensely long calibration time.
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Roland Christen
Yes I know it's different, but you still have to move the scope a certain distance in Dec in order to get proper values for the program. We have dealt with several customers now who did not understand what calibration does and ended up with bogus results. The guiding was totally off because the mount was being yanked back and forth with oversize error signals. Anyhow, the mount will do as you ask, no more no less.
toggle quoted messageShow quoted text
Rolando
-----Original Message-----
From: pnagy@... [ap-gto] To: ap-gto Sent: Tue, Dec 5, 2017 5:02 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? PHD2 is a totally different animal than other guiding software like Maxim DL and the names (i.e. calibration steps) and parameters are not likely going to agree or match. PHD2 has a cool "Calibration Step Calculator" to calculate for the best Calibration step size in milliseconds based on declination of guide star, focal length of guide scope, pixel size of guide camera and mount's guide speed. Use this instead of guessing and will NOT agree with Maxim auto guiding parameters. Click on the "Brain" icon, click on "Guiding" tab and finally click on "Calculate" button and it will pop up a window for you to fill in the blanks. Peter ---In ap-gto@..., wrote : The total distance traveled should be on the order of 150 arc sec. That is
equivalent to 10 seconds of move command at 1x in any other guide software and would move the star enough to accurately calculate the pixel/sec move parameter. A total of 10 seconds move command is normal in MaximDL and is done in one step in that program. In your example of 714mm, 3.8 micron pixel size, you are running at 1.1 arc sec per pixel. The resultant pixel/sec parameter would be 13.7 pixels per second at 1x sidereal.
The reason for the 10 second cal run in MaximDL is to minimize the delay error in reversing Dec. If it takes 1 second to reverse Dec, then the parameter would be in error by 10%, which is not a big problem. If the cal run was only for 3 seconds, then the resultant error is 33%, which is quite large, and any setting of aggressiveness above 70% will begin to cause oscillations because the loop gain is now above 100%. It may be that PHD can compensate for this reversal delay in Dec by doing calibration only in one direction. I'm not familiar with the workings of the software, I only know how it was done in all the other programs. Rolando -----Original Message-----
From: Zac Kruger z@... [ap-gto] gto@...> To: ap-gto gto@...> Sent: Tue, Dec 5, 2017 4:04 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Roland,
Have you successfully used PHD to attempt calibration over the recommended 150 arc sec? Using an OAG at 714mm FL and 3.8u pixel size I have been entirely unsuccessful because of what I assume is due to the way PHD functions. It loses track of the star when using such large calibration steps. I have to be somewhere at 150-250ms pulses in order to calibrate at all. Doing that to cover 150'' would require an immensely long calibration time.
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
topboxman
PHD2 is a totally different animal than other guiding software like Maxim DL and the names (i.e. calibration steps) and parameters are not likely going to agree or match.
toggle quoted messageShow quoted text
PHD2 has a cool "Calibration Step Calculator" to calculate for the best Calibration step size in milliseconds based on declination of guide star, focal length of guide scope, pixel size of guide camera and mount's guide speed. Use this instead of guessing and will NOT agree with Maxim auto guiding parameters. Click on the "Brain" icon, click on "Guiding" tab and finally click on "Calculate" button and it will pop up a window for you to fill in the blanks. Peter ---In ap-gto@..., <chris1011@...> wrote : The total distance traveled should be on the order of 150 arc sec. That is equivalent to 10 seconds of move command at 1x in any other guide software and would move the star enough to accurately calculate the pixel/sec move parameter. A total of 10 seconds move command is normal in MaximDL and is done in one step in that program. In your example of 714mm, 3.8 micron pixel size, you are running at 1.1 arc sec per pixel. The resultant pixel/sec parameter would be 13.7 pixels per second at 1x sidereal. The reason for the 10 second cal run in MaximDL is to minimize the delay error in reversing Dec. If it takes 1 second to reverse Dec, then the parameter would be in error by 10%, which is not a big problem. If the cal run was only for 3 seconds, then the resultant error is 33%, which is quite large, and any setting of aggressiveness above 70% will begin to cause oscillations because the loop gain is now above 100%. It may be that PHD can compensate for this reversal delay in Dec by doing calibration only in one direction. I'm not familiar with the workings of the software, I only know how it was done in all the other programs. Rolando
-----Original Message-----
From: Zac Kruger z@... [ap-gto] <ap-gto@...> To: ap-gto <ap-gto@...> Sent: Tue, Dec 5, 2017 4:04 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Roland,
Have you successfully used PHD to attempt calibration over the recommended 150 arc sec? Using an OAG at 714mm FL and 3.8u pixel size I have been entirely unsuccessful because of what I assume is due to the way PHD functions. It loses track of the star when using such large calibration steps. I have to be somewhere at 150-250ms pulses in order to calibrate at all. Doing that to cover 150'' would require an immensely long calibration time.
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Roland Christen
The total distance traveled should be on the order of 150 arc sec. That is equivalent to 10 seconds of move command at 1x in any other guide software and would move the star enough to accurately calculate the pixel/sec move parameter. A total of 10 seconds move command is normal in MaximDL and is done in one step in that program. In your example of 714mm, 3.8 micron pixel size, you are running at 1.1 arc sec per pixel. The resultant pixel/sec parameter would be 13.7 pixels per second at 1x sidereal.
toggle quoted messageShow quoted text
The reason for the 10 second cal run in MaximDL is to minimize the delay error in reversing Dec. If it takes 1 second to reverse Dec, then the parameter would be in error by 10%, which is not a big problem. If the cal run was only for 3 seconds, then the resultant error is 33%, which is quite large, and any setting of aggressiveness above 70% will begin to cause oscillations because the loop gain is now above 100%. It may be that PHD can compensate for this reversal delay in Dec by doing calibration only in one direction. I'm not familiar with the workings of the software, I only know how it was done in all the other programs. Rolando
-----Original Message-----
From: Zac Kruger z@... [ap-gto] To: ap-gto Sent: Tue, Dec 5, 2017 4:04 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Roland,
Have you successfully used PHD to attempt calibration over the recommended 150 arc sec? Using an OAG at 714mm FL and 3.8u pixel size I have been entirely unsuccessful because of what I assume is due to the way PHD functions. It loses track of the star when using such large calibration steps. I have to be somewhere at 150-250ms pulses in order to calibrate at all. Doing that to cover 150'' would require an immensely long calibration time.On Tue, Dec 5, 2017 at 9:01 AM, chris1011@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Worsel
Roland
Which algorithm(s) do you recommend, if not hysteresis? Bryan ---In ap-gto@..., <chris1011@...> wrote : Don't use any hysteresis. It can cause oscillations because it is a form of over-aggressiveness. The way to get good guiding is to do a proper accurate calibration. Then check the numbers to make sure they make sense for your focal length and pixel size. Aggressiveness is used to slow down the amount of correction that is sent to the mount. If the software detects a +2 arc sec error and aggressiveness is set to 100%, then the mount will receive a correction signal that moves the mount - 2 arc seconds. If aggressiveness is set to 50%, then the mount receives a -1 arc sec move command. Sometimes it is advantageous to use lower than 100% aggressiveness when the seeing is not good and the guide star is bouncing around. I like to use 3 to 5 second guide exposures at 80% aggressiveness and a Min Move of .15 arc sec (.01 sec min move at 1x sidereal) and a 7.5 arc sec max move (.5 sec max move at 1x sidereal). Rolando
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Worsel
Joe
The two do completely different actions. From documentation 'Use Declination Compensation' - if PHD2 can get pointing information from the mount via an ASCOM connection ('Mount' or 'Aux'), it will automatically adjust the RA guide rate based on the current declination. This box should normally be left checked except in unusual cases. For example, SiTech mount controllers evidently apply a compensation automatically, in which case the box should be left un-checked. Don't confuse this option with 'Declination backlash compensation', which is an entirely different feature.'Use Declination Compensation' - if PHD2 can get pointing information from the mount via an ASCOM connection ('Mount' or 'Aux'), it will automatically adjust the RA guide rate based on the current declination. This box should normally be left checked except in unusual cases. For example, SiTech mount controllers evidently apply a compensation automatically, in which case the box should be left un-checked. Don't confuse this option with 'Declination backlash compensation', which is an entirely different feature.
'Use backlash comp' - this controls whether PHD2 will apply a compensation factor when the direction of declination guiding needs to be reversed. Measurement of backlash and calculation of a good starting value for the compensation factor is done in the Guiding Assistant. The size of the additional guide correction (compensation value) is shown in the 'Amount' field adjacent to the checkbox. This amount may be adjusted upward or downward by PHD2 if necessary to tune the guiding results. In either case, the adjustments are made conservatively in order to avoid making guiding unstable. Since PHD2 has the ability to detect and adapt to over-corrections, the backlash compensation available here should work better than the fixed backlash compensation available in many mount controllers. If you use the PHD2 backlash compensation, you should disable any backlash compensation in the mount.
Bryan ---In ap-gto@..., <J.Zeglinski@...> wrote : Huh ??? Brian – if the “algorithm” has been set to “NOT
use backlash compensation”, then doesn’t that take precedence over the Guiding
tab option of “Use DEC comp” ? It may have been an unfortunate duplication of
terms – maybe the latter actually first, “re-enables” compensation again
in the algorithm . Would have to, right? Joe
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Joe Zeglinski
Huh ???
Brian – if the “algorithm” has been set to “NOT
use backlash compensation”, then doesn’t that take precedence over the Guiding
tab option of “Use DEC comp” ? It may have been an unfortunate duplication of
terms – maybe the latter actually first, “re-enables” compensation again
in the algorithm . Would have to, right?
Joe
From: bryancashion@... [ap-gto]
Sent: Tuesday, December 5, 2017 4:20 PM
To: ap-gto@...
Subject: Re: [ap-gto] What are the PHD2 settings used in a
Mach1? Michael Maybe its understood, but don't confuse "Use backlash comp" (checkbox on
Algorithm tab under Brain) with "Use Declination comp" (checkbox on Guiding tab
under Brain). The latter adjusts the guiding for the declination of the
imaged object and is useful enhancement on most mounts with ASCOM enabled.
Bryan
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Worsel
Michael
toggle quoted messageShow quoted text
Maybe its understood, but don't confuse "Use backlash comp" (checkbox on Algorithm tab under Brain) with "Use Declination comp" (checkbox on Guiding tab under Brain). The latter adjusts the guiding for the declination of the imaged object and is useful enhancement on most mounts with ASCOM enabled. Bryan ---In ap-gto@..., <chris1011@...> wrote : Don't play with guide speed. Leave it sit at 1x and play with the other variables. Min Move is important - don't set it too high or you get no corrections. And try not to use any backlash comp or hysteresis. These will just complicate things and may cause instability, overshoot, oscillations, etc. Rolando
-----Original Message-----
From: Michael Fulbright mike.fulbright@... [ap-gto] <ap-gto@...> To: ap-gto <ap-gto@...> Sent: Tue, Dec 5, 2017 2:40 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Thanks for the suggestion I can give it a try next clear night. I think I've played with both 0.5x and 1.0x over time and being predominately seeing limited (Mid-Atlantic can be cruel seeing-wise) I'd just settled on whatever I tried last! Michael Fulbright
|
|
|
|
Re: PEMpro V3 how to make a curve? step by step please.
Roland Christen
Again, best bet is to contact George directly with your concerns about the performance. He can help you with some simple tests, some of which can be done indoors. It is important to differentiate between software settings in your guider program and actual hardware problems.
toggle quoted messageShow quoted text
Rolando
-----Original Message-----
From: Ron Kramer ronkramer1957@... [ap-gto] To: ap-gto Sent: Tue, Dec 5, 2017 2:42 pm Subject: Re: [ap-gto] PEMpro V3 how to make a curve? step by step please. However I seem to have a lot of blacklash in this mount. Sorry to jump in so late, just got back from a trip last week and noticed this "plea for help". I have not read any of the responses to your post yet, but my very first question will always be - What setting of guide speed are you using?
And the answer should be 1x sidereal NOT .5x or .25x!! Using these slower guide speeds will double and quadruple the Dec reversal time, and will result in less than optimum guiding response.
I'm at 1X. I just read elsewhere that someone ses .5 ( did try that briefly and didn't seem to help. I went back to 1X.
Secondly, the internal gearbox backlash in Dec can be adjusted, and the very first action would be to call George here at AP to discuss how to adjust it if it really is excessive at 1x sidereal guide speed. He can guide you thru some very simple tests to determine if it really is backlash.
I found some play in both axis. I adjusted the mesh to totally remove any play. (seemed a little better, but not much). It's SO HARD for me to test and compare this time of year in Michigan. Stars are a rarity in December.
In mt quest to improve guiding. I sold my ASI290 camera and replaced it with a Lodestar X2. (seems to be best choice). While I did not see an improvement in guiding from this, I do have a much better star and I no longer get lost star errors. (So it will help).
Thirdly, please refrain from doing a PEMPro run on a new mount. This has already been done at the factory, and even if you don't turn it on, your mount will guide beautifully anyway because the inherent periodic error is going to be less than 7 arc seconds. There is no reason to record a new curve right off the bat - use the mount for a few months and get familiar with its operation before making these kind of changes.
I would have but due to my problems. I thought I'd record a new one. I had hit record which I believe wiped out my factory pec. so now I feel I should do PemPro to restore the bad curve.
Finally, PE has zero to do with backlash in Dec, so don't chase two red herrings down two blind alleys.
Right. I assumed RA guiding would be better with PEC and Dec may be improved with backlash adjustment. I get pretty radical graphs in both. I had what I feel is acceptable guiding once at .59 (total rms) Arc.S. But it didn't last long and if I point elsewhere away from calibration point - it gets even worse. Often over 1.0
ITS JUST VERY HARD TO MAKE PROGRESS this time of year here.
Your best bet is to always call AP first in order to set your parameters. While the group may be helpful for some things, it really cannot solve problems if there really is something out of whack with your equipment. George can be of major help in these cases, and I am always available also to advise and figure out what may be going wrong. We have seen all kinds of issues, some customer error and some actual mechanical problems and can quickly determine what to do and not leave people hanging. Problem solving is what we do and getting people up and running is our #1 goal.
I think my results have been fine (good tight stars) on my 80mm at >1.0. But I plan to move to my 127mm (At more than double the current focal length.) very soon and suspect I will need .7 .6 RMS. I see others with same mount at <.5 consistently. I'd so love that.
Ron
Roland Christen
On Mon, Dec 4, 2017 at 5:28 PM, chris1011@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Roland Christen
Don't play with guide speed. Leave it sit at 1x and play with the other variables. Min Move is important - don't set it too high or you get no corrections. And try not to use any backlash comp or hysteresis. These will just complicate things and may cause instability, overshoot, oscillations, etc.
toggle quoted messageShow quoted text
Rolando
-----Original Message-----
From: Michael Fulbright mike.fulbright@... [ap-gto] To: ap-gto Sent: Tue, Dec 5, 2017 2:40 pm Subject: Re: [ap-gto] What are the PHD2 settings used in a Mach1? Thanks for the suggestion I can give it a try next clear night. I think I've played with both 0.5x and 1.0x over time and being predominately seeing limited (Mid-Atlantic can be cruel seeing-wise) I'd just settled on whatever I tried last! Michael Fulbright On 12/5/2017 3:34 PM, chris1011@...
[ap-gto] wrote:
|
|
|
|
Re: What are the PHD2 settings used in a Mach1?
Zac Kruger <z@...>
Roland, Have you successfully used PHD to attempt calibration over the recommended 150 arc sec? Using an OAG at 714mm FL and 3.8u pixel size I have been entirely unsuccessful because of what I assume is due to the way PHD functions. It loses track of the star when using such large calibration steps. I have to be somewhere at 150-250ms pulses in order to calibrate at all. Doing that to cover 150'' would require an immensely long calibration time.
On Tue, Dec 5, 2017 at 9:01 AM, chris1011@... [ap-gto] <ap-gto@...> wrote:
|
|
|
|
Re: PEMpro V3 how to make a curve? step by step please.
However I seem to have a lot of blacklash in this mount. Sorry to jump in so late, just got back from a trip last week and noticed this "plea for help". I have not read any of the responses to your post yet, but my very first question will always be - What setting of guide speed are you using? And the answer should be 1x sidereal NOT .5x or .25x!! Using these slower guide speeds will double and quadruple the Dec reversal time, and will result in less than optimum guiding response. I'm at 1X. I just read elsewhere that someone ses .5 ( did try that briefly and didn't seem to help. I went back to 1X. Secondly, the internal gearbox backlash in Dec can be adjusted, and the very first action would be to call George here at AP to discuss how to adjust it if it really is excessive at 1x sidereal guide speed. He can guide you thru some very simple tests to determine if it really is backlash. I found some play in both axis. I adjusted the mesh to totally remove any play. (seemed a little better, but not much). It's SO HARD for me to test and compare this time of year in Michigan. Stars are a rarity in December. In mt quest to improve guiding. I sold my ASI290 camera and replaced it with a Lodestar X2. (seems to be best choice). While I did not see an improvement in guiding from this, I do have a much better star and I no longer get lost star errors. (So it will help). Thirdly, please refrain from doing a PEMPro run on a new mount. This has already been done at the factory, and even if you don't turn it on, your mount will guide beautifully anyway because the inherent periodic error is going to be less than 7 arc seconds. There is no reason to record a new curve right off the bat - use the mount for a few months and get familiar with its operation before making these kind of changes. I would have but due to my problems. I thought I'd record a new one. I had hit record which I believe wiped out my factory pec. so now I feel I should do PemPro to restore the bad curve. Finally, PE has zero to do with backlash in Dec, so don't chase two red herrings down two blind alleys. Right. I assumed RA guiding would be better with PEC and Dec may be improved with backlash adjustment. I get pretty radical graphs in both. I had what I feel is acceptable guiding once at .59 (total rms) Arc.S. But it didn't last long and if I point elsewhere away from calibration point - it gets even worse. Often over 1.0 ITS JUST VERY HARD TO MAKE PROGRESS this time of year here. Your best bet is to always call AP first in order to set your parameters. While the group may be helpful for some things, it really cannot solve problems if there really is something out of whack with your equipment. George can be of major help in these cases, and I am always available also to advise and figure out what may be going wrong. We have seen all kinds of issues, some customer error and some actual mechanical problems and can quickly determine what to do and not leave people hanging. Problem solving is what we do and getting people up and running is our #1 goal. I think my results have been fine (good tight stars) on my 80mm at >1.0. But I plan to move to my 127mm (At more than double the current focal length.) very soon and suspect I will need .7 .6 RMS. I see others with same mount at <.5 consistently. I'd so love that. Ron Roland Christen On Mon, Dec 4, 2017 at 5:28 PM, chris1011@... [ap-gto] <ap-gto@...> wrote:
|
|
|
