Hi Neil. We don’t seem to be making much progress, so I’ll ask you to carefully review the instructions here:
https://openphdguiding.org/getting-help/
In particular:
Good luck,
Bruce
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fc608c0c-c19b-48a8-ab62-ab2a4e38a6fd%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd...@googlegroups.com.
Thanks Neil, now we can get into the problems. Two of the problems are expected for this class of mount, a fairly large uncorrected periodic error in RA and a lot of Dec backlash. You can see the RA periodic error in the GA results:

This is a peak-to-peak periodic error of about 30 arc-sec and looks like it’s occurring at the native worm period of the mount, about 480 seconds. If you can find a way to apply a usable periodic error correction to the mount, that would be the best approach. If not, you can try using the PPEC guide algorithm for RA, giving it an initial period value of 480 sec.
The backlash test showed that it’s taking nearly 7 seconds for the Dec axis to reverse direction at your current guide speed of 0.5x sidereal. If you increase the guide speed setting in the mount up to, say, 0.9x sidereal, that backlash recovery time will decrease proportionately. Beyond the basic backlash, we can see the “lumpy” movement in Dec you were talking about. Here’s an example during a calibration:

This is probably a mechanical problem of some kind that you’ll want to eliminate. It may be something as simple as grit or dried grease in the Dec drive train. Sometimes slewing the axis at high speed in both directions a few times can clear this stuff. Otherwise, you’ll probably have to open up the drive assembly to see what’s going on. I assume, of course, that you didn’t have some external that was interfering with the movement like a tugging guide cable.
Most of your calibration alerts were coming from the large Dec backlash. With your mount, you’ll need to precede *every* calibration with a forced north movement of the mount. You can do this with a short slew or by using the hand-controller. That will clear the backlash and get you better calibration results. You may see advisory messages that the mount didn’t move south very much at the end of the calibration but you can disregard those.
With all of that said, you actually got some good guiding during the 6-hour session on 8/4. The total guiding RMS was only 0.8 arc-sec and your should have been getting nice round stars. So if this is the period when you saw the bad imaging results, it doesn’t look like guiding. What is the main scope you’re using? If it’s a long focal length SCT or something like that, you probably won’t be able to guide effectively with a separate guide scope.
Hope this helps,
Bruce
From:
open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Neil Martin
Sent: Thursday, August 08, 2019
9:28 AM
To: Open PHD Guiding
Subject: Re: [open-phd-guiding] Re:
RA and Declination guiding rates differ by an unexpected amount
https://openphdguiding.org/logs/dl/PHD2_logs_5RXj.zip
On Thursday, August 8, 2019 at 9:21:45 AM UTC-5, bw_msgboard wrote:
Hi Neil. We don’t seem to be making much progress, so I’ll ask you to carefully review the instructions here:
https://openphdguiding.org/getting-help/
In particular:
1. Don’t trim or modify the log files in any way. What may seem extraneous to you is often important to us, and edits can break custom tools we use for support. And yes, the log files can be large, that’s why we provide the upload service
2. When you’re having trouble with guiding, we need to see the *guide* log. If you’re having equipment connection problems or you think there’s a bug in PHD2, we need the *debug* log. If you can’t decide, it’s ok to upload both.
3. If you can’t get the upload tool to work for you, it’s ok to post the files to a shared service like DropBox, but you have to be sure the files are public or accessible to anyone who has the link. We can’t handle being “invited” to share all these log files.
Good luck,
Bruce
From: open-phd...@googlegroups.com
[mailto:open-phd...@googlegroups.com]
On Behalf Of Neil Martin
Sent: Thursday, August 08, 2019
4:40 AM
To: Open PHD Guiding
Subject: [open-phd-guiding] Re: RA
and Declination guiding rates differ by an unexpected amount
Hi Bruce,
Sorry about that, I trimmed the log file (which was huge, but also wanted it to only contain the one night's data) and saved it to another file. I must have uploaded the wrong one..
Neil
On Wednesday, August 7, 2019 at 10:54:04 PM UTC-5, Bruce Waddington wrote:
Hi Neil. These logs are virtually empty. When you use the Uploader tool, you need to look at the timestamp and duration columns to be sure you're covering the time period when you had problems. PHD2 creates log files whenever it is run, whether you actually do anything or not. If you can't figure it out any other way, you can do a text search on 'Calibration Begins' in the PHD2_GuideLog*.txt files to see when you attempted calibrations.
Bruce
On Wednesday, August 7, 2019 at 12:54:06 PM UTC-7, Neil Martin wrote:
I need some help interpreting the calibration results and the output of the Guide Assistant. I've used PHD2 in the past (for shorter exposures) with mixed results. I put that down to user error, but now I'm starting to think that my AVX mount maybe a big factor. On Sunday I tried taking some 5 minute subs with a Ha filter. I started with a fresh PHD profile and got a lot of warnings when it calibrated. I went ahead anyway and no surprise, the resulting images were appalling - larger stars were crescent shaped. The warnings had me take a look at my mount and it made me realize how sticky the declination axis is. Additionally, with the clutch released, and turning through a large angle, there were definite "lumpy" spots. These seemed to clear with repeated exercise, but not a good sign.
Last night I went through the same process, but with only my guide scope mounted and the counterbalance weight and spindle removed. I've captured the PHD output with a few snapshots using my phone, which I have attached along with my log.
--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fc608c0c-c19b-48a8-ab62-ab2a4e38a6fd%40googlegroups.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/a3167cb7-356d-4a5c-8984-379b4adb75d2%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/a3167cb7-356d-4a5c-8984-379b4adb75d2%40googlegroups.com.
Can I generate that period error graph myself? I didn't see that in the GA, or am I missing something? Or is this produced by another tool that you use to analyze log files?
>>> Interesting to know that I actually got good guiding.
Keep in mind although the graphs look pretty grumpy, the pixel movement was only 0.37 average for the entire 6 hour session, so we’re talking minimal guide- or mount-related issues on the final imaging.
If you aren’t happy with your images, you could also share some raw files via dropbox or other file sharing? It could be just about anything: seeing, focus, etc. but happy to take a look
Thanks
Brian
portfolio https://www.brianvalentephotography.com/
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fa443d22-225e-4ef2-a925-40876c5f064a%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fa443d22-225e-4ef2-a925-40876c5f064a%40googlegroups.com.


To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/b7716cbe-29f2-407a-9744-69ad542f6790%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i6ztcr55A-VchxYwry2wh47X%2BXeq-%3DA-5uEKXgQznxcOQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABKPALrQ02dpdg3y6%3Dazj2c8%2BacdZSapO0suSkS3_YSoMnLFkQ%40mail.gmail.com.
the Canon 70-200
Hi Neil, everyone
If stopping to 5.6 doesn't fix it -I gave up on my Canon zoom for the same reason-, you may want to have a look at an old Takumar 200mm. Over APS-C, this gives you sharp stars corner to corner and costs around $50. Complete your wide field armory with a 135mm from the same source.
HTH and clear skies,
Steve
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/fe4fc73a-3c36-48e0-b2f8-a5b1b8f8623d%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i6uMs1m6vRzcpmrAg16qXb6ANoSGK6jH2YVfp1BVL6aWQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CABKPALo15Vn6GBitRanpOuVuLbFuur7RYUhkUYQ%3DVnmWjE4ADQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/CAJa45i5MVE8gsp6Ht5vDKAEzeqQVM5Xj4Ou%3DyS8qxvKjnOUprg%40mail.gmail.com.