Ron it looks like your DEC in calibration wasn’t responding well.
Did you try running the guide assistant and seeing what it said/following its advice?
Thanks
Brian
Brian Valente
Brianvalentephotography.com
--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
What did the GA report as your DEC backlash?
The calibration results are not saved in the guidelogs, but they may be in the debug logs
It’s pretty clear DEC is at least a main culprit, you saw it yourself in those calibration graphs.
This does not look like a repetitive pattern to me. it looks like some normal guiding with
I’m sure there are some periodic errors going on in there, but no, not what you point out
Thanks
Brian
Brian Valente
Brianvalentephotography.com
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Friday, September 15, 2017 8:58 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
--
Hi Steve, thanks! - but I don't know what language you're speaking. open my new mount? idler? any youtube step by steps on this?
On Friday, September 15, 2017 at 11:57:36 AM UTC-4, Steve Sheriff wrote:
El 15/09/2017 a las 17:31, Ron Kramer escribió:
> > > My Dec (red graph) jumps ALL OVER - I constantly tweak numbers trying > to up hysteries and reduce aggressiveness.
Hi. Fellow eq6 user here. RE: DEC.
Just before the software gurus step in, may I offer some observations which got me going?
The mesh between the worm and crown gear needs to be loose -enough to enable you to detect it when pushing the telescope by hand. Remove the DEC motor and have a look at the mesh between the idler and the driven gear on the motor. Make sure there is play between them. Make sure those also mesh loosely enough to be able to see movement. When you replace the DEC motor, don't push it hard against the gear on the worm shaft. One last trick is to try with the telescope perfectly balanced rather than camera-end heavy.
Next, drift align and run the ga. Now your tweaks will do something, I'm sure.
HTH and clear skies,
Steve
--
Is that backlash the result of a guiding assistant recommendation?
If you aren’t sure, I’d recommend running the GA again (maybe after some of the suggestions Steve had) and seeing what it says
It seems there is an issue with your DEC that PHD is not able to handle.
I’d say
Thanks
Brian
Brian Valente
Brianvalentephotography.com
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Friday, September 15, 2017 9:15 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
Subject: [open-phd-guiding] Re: I'm back to share my problems again. Please review my logs - I get EXCELLENT and lousy guiding.
Here is the debug. It shows backlash = 1600? I had also tried checking the box to use BL comp and not use it - neither seemed to change anything.
--
Guide assistant set my min moves to 15 (ok) then said I might try guiding dec from one side. I wasn't real sure how to do this. I "TRIED" NORTH only and SOUTH only and both lost dec off the graph. I have to keep it on auto?Not much else is said... I thnk it reported my polar alighnment at 9 arc min?
to do N or S only Dec guiding, you need to tweak your mount so its not quite polar aligned, so all Dec adjustments will be the same way, either N or S.
-- john r pierce, recycling bits in santa cruz
Hi Ron. Well, you’ve certainly stirred up the forum today. <g> I see a couple of problems, focusing only on your OAG setup. As others have noted, your mount has some significant problems in Dec. You’ve inadvertently made this a lot worse by using a 0.1x guide speed, which is a very bad idea for any mount that has backlash. Take a look at this link and adjust the mount guide speed up close to 1x sidereal. For a given amount of physical backlash (slop) in the gears, the amount of time it will take to clear the backlash is a linear function of the guide speed. At super-slow speeds, it will take a very long time indeed.
https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings
You also need to make sure all the EQASCOM tuning and adjustment settings for guiding are disabled – PHD2 doesn’t want any “help” from the ASCOM driver. And you’ll need to be sure any backlash correction settings in the mount are also disabled.
That should be the easy part. The second problem is that something other than guiding is causing your mount to move a lot in Dec. Here’s one of several examples:

Look at the 5 arc-sec move north at the center of the snippet. At the point it happened, the Dec motor wasn’t even running, and no guide pulses were sent to move north. This was an external event, something you’ll need to track down.
I suggest getting a new baseline with the proper guide speed settings in the mount:
1. Reset all the guiding parameters to their default values
2. Turn off the star-mass checking option in the guiding tab of the Advanced Dialog
3. Try to get a clean calibration – no lost stars for example. If necessary, manually move the mount north at guide speed immediately before starting the calibration. You probably have a lot of Dec backlash and that will help to clear it.
4. Re-run the Guiding Assistant – let it run for at least 10 minutes then apply any recommendations for min-move settings. But don’t turn on backlash compensation even if it’s offered.
5. Let PHD2 guide for another 10 minutes with no dithering and no futzing around with guide parameters. While you’re trying to track down Dec problems in the mount, dithering in Dec just makes it harder to see what’s going on.
If you collect the guide and debug log files from all this, we’ll try to help you figure out your next moves. I also think you should pay close attention to the earlier input from Steve Sheriff – these sorts of problems are often mechanical and usually require a mechanical solution.
Good luck,
Bruce
From:
open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Friday, September 15, 2017
9:15 AM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re:
I'm back to share my problems again. Please review my logs - I get EXCELLENT
and lousy guiding.
Here is the debug. It shows backlash = 1600? I had also tried checking the box to use BL comp and not use it - neither seemed to change anything.
--
Hi Ron. Well, you’ve certainly stirred up the forum
Hi Ron. Well, you’ve certainly stirred up the forum today. <g> I see a couple of problems, focusing only on your OAG setup. As others have noted, your mount has some significant problems in Dec. You’ve inadvertently made this a lot worse by using a 0.1x guide speed, (I don't recall setting this as I have no idea what this does, maybe inadvertantly?) what should it be 1.0?) which is a very bad idea for any mount that has backlash. Take a look at this link and adjust the mount guide speed up close to 1x sidereal. OK! For a given amount of physical backlash (slop) in the gears, the amount of time it will take to clear the backlash is a linear function of the guide speed. At super-slow speeds, it will take a very long time indeed. I'm so hoping to find some easy fix - hope this is it.
https://github.com/OpenPHDGuiding/phd2/wiki/EQASCOM-Settings
You also need to make sure all the EQASCOM tuning and adjustment settings for guiding are disabled – PHD2 doesn’t want any “help” from the ASCOM driver. And you’ll need to be sure any backlash correction settings in the mount are also disabled. These settings are where? In Eqmod I see some guiding setting (I think I left alone). But I thought I left guiding speed alone. I tried again last night concentrating only on guiding and setup. It was better but my GA said my DEC wasn't good. I'll post screen shots later.
That should be the easy part. The second problem is that something other than guiding is causing your mount to move a lot in Dec. Here’s one of several examples:
I had considered uninstalling PHD2 and deleting all data, ini and log files and reinstalling. I've not been at this very long and when I started - I BELIEVE my guiding was very good. I figured my mount went bad or I did something.
I had considered uninstalling PHD2 and deleting all data, ini and log files and reinstalling. I've not been at this very long and when I started - I BELIEVE my guiding was very good. I figured my mount went bad or I did something.
QUESTION: should my skywatcher NEQ6 sound like a blender of grinding parts when it spins up to move any direction? I asked the dealer and they said yes that's normal. (when I just recieved it). I wonder now if it's grinding away at the gears and this is the result? IT SOUNDS like it needs more lubrication. ? (is there warranty?) I got it last March.
QUESTION 2 - when I went to OAG and 384FL scope does the graph and RMS number change? On the external guider the night before I was getting total RMS of 0.22 and It was inside 2 arc seconds on the graph. Last night with the OAG I was almost always inside 2 arc seconds and yet the total RMS was around 0.40 - 0.60 ?? Am I looking for too much? All my stars are round in my shots and I never get trails.
Hi Steve. Hey, wait a sec! <g> You have nothing to apologize for! On the contrary, I thought your message was very helpful. When people have personal experience with a particular mount and especially if they know some of the hardware details, they can really provide some specific help to others. Andy and I aren’t mechanical engineers and we only have personal experience with a few mounts, so we usually have to talk in generalities when it comes to mechanical problems. My comment about “stirring up the forum” was a joke, just a reaction to the number of messages in the thread when I finally got around to looking at my e-mail. Please continue to contribute to the forum, we’ll all benefit.
Thanks,
Bruce
My apologies for any WEIRD posting, I'm a forum person and new to GROUPS and I don't quite understand the order/reply order presented.
Hi Ron. All I can tell is you what we have in the Wiki doc, I don’t use EQMOD. Make sure both RA and Dec pulse guide options are set and move the sliders to 0.9. I don’t know what the ‘reverse’ options are for, I would leave them disabled. That said, they aren’t likely to have any effect on your guiding so long as they don’t change after the PHD2 calibration is done. I don’t see any reason to think they have any bearing on the problems we talked about before.
Going forward, we always need to see your guide logs to analyze and discuss results. Screenshots are basically useless for what we’re trying to do.
When it gets dark, you should repeat the earlier process using the 0.9x mount guide speed, then we can start to look harder at what’s going on with your Dec axis. Before you do the next calibration, you’ll need to adjust the calibration step-size. Go to the guiding tab in the Advanced Dialog, and click on the ‘Calculate’ button:

That will bring up a dialog that should show your new guide speed setting of 0.9x:

That value is being read from the mount, so if you don’t see the 0.9x value, something is still wrong in the EQMOD settings. But if it looks right, click on ‘Ok’ and that will re-calculate the calibration step-size used in calibration. Then you can get on with calibration and testing.
Good luck,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Saturday, September 16, 2017
10:50 AM
To: Open PHD Guiding
--
I started astrophotography last spring. PHD2 was new to me and it's been 3 months or so and it's been a love-hate (more so confusing) experience.I asked for help before - we assumed I was overweighing the mount. I REALLY lightened the load and not much change. I fiddled and things went good againthen poor again and with frustration I purchased and installed a OAG to eliminate the possible problems and weight of the guide scope.The guide scope was around 150mm FL and with OAG I'm using the imagine tube which is (with focal reducer) 384mm FL. (I enter that in PHD/SGP as my guide scope FL right?)With the external scope I could sometimes get RMS total of 0.22 WOW! but sometimes 0.60. (up and down) while seeing seemed to stay very good. (I often use my HFR focus results to judge my seeing conditions).___Last night first time with OAG. It was a logical and fairly painless transition. Again at times I had "decent"? guiding and other times horrible. What I want to ask is...With the guide scope - is the RMS total of 0.22 - the same reading as with the OAG and much higher FL imaging scope? What I'm saying is... while the graph Looked similar, the good RMS reading for the OAG setup was more like 0.50. Bad was .80 +vs 0.22 and 0.45 good and bad for the guide scope external setup. (do these reading change with FL?) or are they consistent numbers for all configurations?I also recorded and played my PEC for my NEQ6pro mount and played it back "on and off" and found no help from it. If anything it seemed to make things worse?____Enough jabber - The beef is in the logs I'm told. I'm viewing them in the log viewer program (cool) but not sure what I'm seeing.THANK YOU so much for the support.The two log files I've attached are...xxxx952.txt - AOG guider last night. (first time) I kept playing with and adjusting settings.xxxxx052,txt - My last guide scope night, with very and good guiding as well as issues (UP N DOWN) all the time. Despite I feel seeing is quite consistent.Despite sitting there and nursing it all night - I have had some decent success's for a noobie. But I'd like to try my 8" RC and figure I should work out the kinks in guiding first.
Hi again Ron. It looks like you got the guide rates set right, so that’s good. But it looks like you missed a few other things from my earlier post:
I suggest getting a new baseline with the proper guide speed settings in the mount:
1. Reset all the guiding parameters to their default values - this didn’t happen, there are a number of parameter changes that made your situation worse
2. Turn off the star-mass checking option in the guiding tab of the Advanced Dialog - still seeing sporadic lost stars due to mass change.
3. Try to get a clean calibration – no lost stars for example. If necessary, manually move the mount north at guide speed immediately before starting the calibration. You probably have a lot of Dec backlash and that will help to clear it. Good job on this, your calibrations look good, but only when you cleared the backlash manually. You got good calibration data, no need to keep re-doing these – but you should have kept the one you did at Dec=-0.3. Calibration near the celestial equator produces the best overall results.
4. Re-run the Guiding Assistant – let it run for at least 10 minutes then apply any recommendations for min-move settings. But don’t turn on backlash compensation even if it’s offered. – backlash compensation was active for most of these sessions.
5. Let PHD2 guide for another 10 minutes with no dithering and no futzing around with guide parameters. While you’re trying to track down Dec problems in the mount, dithering in Dec just makes it harder to see what’s going on.
In any case, it’s clear your mount has a very large amount of Dec backlash, it takes somewhere between 7 and 15 seconds for the mount to reverse direction. Unless you can improve this by making some of the adjustments suggested by Steve, you’ll probably need to guide in only one Dec direction. The Help doc gives more information on how to do that. This sort of thing can’t be corrected by any sort of backlash compensation, it’s simply too large. It also looks like you have another app doing pause/resume operations with PHD2, and the delays are often quite long – several minutes typically. This also makes it much harder to interpret what your mount is doing because the long intervals with no guiding mean the guide star can wander far afield. It would be better to avoid these things while trying to diagnose your mount’s behavior.
On the other hand, if you like the results you’re getting with your images, maybe you don’t want to fool around with this stuff. With this mount, I think you could be facing a long slog to eliminate all the problems. I think, best case, it might be reasonable to hope for an overall guiding RMS of about 1 arc-sec – anything better than that is likely to require a lot of work.
Hope this helps,
Bruce
From:
open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Sunday, September 17, 2017
11:38 AM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re:
I'm back to share my problems again. Please review my logs - I get EXCELLENT
and lousy guiding.
BRUCE! thanks - did the .90 and removed the reverse dec. I re-calibrated and it gave me a warning that said "really? this is WAY different from the last calibration). I said - yes really.
--
Thanks
Brian
Brian Valente
Brianvalentephotography.com
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Tuesday, September 19, 2017 10:35 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
Subject: [open-phd-guiding] Re: I'm back to share my problems again. Please review my logs - I get EXCELLENT and lousy guiding.
Appears the pics didn't paste in - lets try this again.
--
Clouds have a tendency to adversely impact guiding, so yes, I am not surprised by that
Especially why PHD reports star was lost
Thanks
Brian
Brian Valente
Brianvalentephotography.com
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Tuesday, September 19, 2017 11:14 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
--
So one last question remains before I get a chance to really test it. Why do I leave Backlash compensation unused? and ignore what GA says to do?
don't I want to compensate for what it determines is BL error?
So one last question remains before I get a chance to really test it. Why do I leave Backlash compensation unused? and ignore what GA says to do?don't I want to compensate for what it determines is BL error?
Because you want PHD to handle the backlash
You don’t want two drivers for that backlash truck, so to speak. They would fight each other
Thanks
Brian
Brian Valente
Brianvalentephotography.com
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Tuesday, September 19, 2017 1:38 PM
To: Open PHD Guiding <open-phd...@googlegroups.com>
--
Hi Ron. As others have said, this does look a lot better – nice job! Now you’ll probably want to get some more time with it to be sure your adjustments are stable and don’t get out of whack. Once you think you can close the book on the bad Dec behavior, you’ll probably want to apply a periodic error correction to the mount. It looks like you probably have uncorrected periodic error north of 20 arc-sec peak-to-peak (the red RA curve). It’s a low-frequency error, apparently tied to the worm period of the mount:

Good luck,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Tuesday, September 19, 2017
10:42 AM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re: I'm back to share my problems again. Please review my logs - I get EXCELLENT and lousy guiding.
Logs which started well and went south I THINK due to high thin clouds.
--
So one last question remains before I get a chance to really test it. Why do I leave Backlash compensation unused? and ignore what GA says to do?
don't I want to compensate for what it determines is BL error?
--
You received this message because you are subscribed to a topic in the Google Groups "Open PHD Guiding" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-phd-guiding/WrdwvHET1GY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-phd-guidi...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to open-phd-guiding+unsubscribe@googlegroups.com.
Nicely done! <g>
Have fun with it – I don’t imagine we’ll be hearing much from you though…
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Ron Kramer
Sent: Saturday, October 07, 2017
12:28 PM
To: Open PHD Guiding
--
You received this message because you are subscribed to the Google Groups
"Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.