I will have a look at the pecprep when I'm home this evening .
I have a c11edge with focal reducer mounted at the moment without guide scope so I'm only at 1/3 of the weight capacity . I did balance the RA well but I didn't have it east heavy (I will try that out).
I cannot find the cge forum for some reason ? This is obviously my issue but any chance you could send me a link ?
I still don't understand why the Dec is moving considerably slower than the RA ? I mean this is the third cge pro I've tested this year all with the same issue , could it be something else ??
Cheers Ken
I will use PEC to start with . I was just concerned the guiding assistant said my backlash was to high to compensate and I should guide in one direction . Plus the RA and Dec are at different speeds like before ?? Should I be concerned ?
The connection to the mount kept dropping for some reason (loose connection ??)
Cheers Ken
-----Original Message-----
From: open-phd...@googlegroups.com
[mailto:open-phd...@googlegroups.com] On Behalf Of Kenneth Crichton
Sent: Tuesday, May 03, 2016 2:37 AM
To: Open PHD Guiding
Subject: RE: [open-phd-guiding] CGE POOR
Hi Bruce ,
I will use PEC to start with . I was just concerned the guiding assistant said my backlash was to high to compensate and I should guide in one direction . Plus the RA and Dec are at different speeds like before ?? Should I be concerned ?
Uncorrected PE in RA can affect the calibration, resulting in an RA guide rate that’s too high or too low. So if yours ended up being too high, that could trigger the calibration alert on rates. In the end, these alerts are just suggestions for things to consider, they’re not messages of doom. You should judge your guiding results based on your imaging results. We’ve seen lots of Celestron mounts that have these behaviors but people seem to do ok with them in the end. If the Guiding Assistant reports a lot of Dec backlash, you should go with the flow and try guiding in only one Dec direction. I don’t think you should be reluctant to try this, you can get very nice imaging results that way – many imagers do it.
Attached is an example from a uni-directional Dec guiding run. This was done with my crappy Meade fork mount and a Meade 10-inch SCT 8 years ago. I’m not claiming this is a world-class image by any means, but I can tell you I was very happy to get it at the time. Really, uni-directional Dec guiding shouldn’t be a big problem.
The connection to the mount kept dropping for some reason (loose connection ??)
What? What connection are you talking about? What error message are you seeing? This should never happen with the serial link to the mount, something’s not right. It could be the cable but we’d need to know what message you’re seeing and from which app it’s coming.
Good luck,
Bruce
During part of a guide log I posted PhD 2 came up with a warning something along the lines of "guide pulses not being received by mount " then the tracking became very good like 0.15 RMS . I disconnected PhD and re calibrated then it started to work on again .
I've been looking at the debug log I posted. Would the following be of relation to loosing control of the mount ?
02:25.267 00.000 768 UpdateImageDisplay: Size=(968,608) min=0, max=255, FiltMin=6, FiltMax=228
01:02:25.267 00.000 768 Resizing image to 562,353
01:02:25.267 00.000 4296 IsSlewing returns 0
01:02:25.267 00.000 4296 IsGuiding returns 0
01:02:25.282 00.015 4296 PulseGuide returned control before completion, sleep 408
01:02:25.282 00.000 768 UpdateGuideState exits: m=6988 SNR=49.6 Saturated
01:02:25.282 00.000 768 OnExposeCompete: CaptureActive=1 m_continueCapturing=1
01:02:25.282 00.000 768 ScheduleExposure(2000,3,1) exposurePending=0
01:02:25.282 00.000 768 Enqueuing Expose request
01:02:25.704 00.422 42
Im assuming the debug log holds all the data from the three guide logs i made during the evening?
I found the other debug log and I will post this evening as I'm using my iPhone at the moment.
I found the alert which is
Pulse guide command to mount has failed - guiding is likely to be ineffective.
I've had a look on pecprep and the periodic error is 10 arc sec is this what your referring to? I gather from your wording "period of the spikes" your meaning this is only happening during a particular period of the tracking ?
I'm assuming I would need to do a longer unguided sequence with PhD before I could correct periodic error ?
Near the end of the unguided sequence you highlighted for me, there is a period of a flat graph , should I delete this before attempting pec ? What is it actually ?
So the issue is mechanical :(
I will need to contact celestron! being that it's a new mount under a 2 year warranty I would void this if I opened the gear box etc . Unless anyone knows an alternative?