开云体育

OK, it happened again.? This time, that PHD2 checkbox was clicked. All I did was GOTO (under stellarium) a nearby star to center in the field of view for focusing. Then the mount started running away

Peter, If I am understanding what you are doing here you now have 3 bearings with less play replacing the looser original 2. Each of the new bearings has less freedom for the shaft to rock up and down

On Sat, Jul 17, 2021 at 04:36 PM, <pcboreland@...> wrote: > > I think I may have discovered something interesting regarding why it is so > difficult to both reduce and get a consistent backlash

Peter, Glad to read your last posting, not your "hit by lightning" obituary! What a story! You may need a lightning rod near your observatory. On to the question: why does your clutch force affect

Eastern position: 100 Western position:112 Western Goto Limit 2:18

Alan, This really sounds like the issue I has 3 years ago when the Beta ware was created. I had runaway slews when GoTo commands were sent from SGPro. At that time I recall sending my Gemini logs to

I think I may have discovered something interesting regarding why it is so difficult to both reduce and get a consistent backlash value for Dec. First, while out in the field disassembling my mount

I used one of those cheap $3 mini laser pointers at the hardware store, designed to make a spot for harassing / entertaining your pets.? It's about 3/8" diameter and 2 inches long. I used a binder

I doubt there is a hardware problem Both motors slew when this happens Stellarium keeps reporting the crosshair position as it goes flying off, so the mount is clearly "telling" it that it's doing so

Show a screen shot of PHD with these oscillations, and I can tell you. It could be "forwards-lash" from a too tight worm mesh. Or axis stiction.

The way to tell if you are getting good guiding or not is to see if the mount responds to corrections. Since you still left the corrections checkbox turned off, I don't know.

Change the y axis to +/-4” and it will look much smoother! Seriously though the RMS pixel values are only 1/3 or 1/5 of a pixel, so even if there are some variations in RA I don’t think it will

From the picture it appears that you're getting 0.28 rms. Is that right? The best I've seen is 0.38 and I have a gm811g with the lightweight tripod. I usually check my focal length setting when I see

The onstep sounds like a great and satisfying project!

I don't know what to tell you, but I had some spikes in Dec, and I tightened it up and they disappeared. I think that the clutches should be cleaned when they start slipping like this, or you can get

Sorry I'm struggling to download, upload and get a proper resolution.? Here's a link to a better version in an album, I hope this works.

BTW here's an image of M39 from 20 subs that I took while observing these oscillations, letting DSS select the best 50%.? I think this is a turning point for me.? It proves that Ekos on a Pi with a

No Stop Button? Haven't heard that one before. Perhaps a power issue. Is the supply yielding 15V and enough amps? Then you might be talking cables or electronics, as Paul mentioned. This might be a

Last night I was autoguiding and DEC started periodic oscillations every 100 seconds or so while RA was fine at 0.5" RMS.? After I loosened the RA and DEC clutches a bit (I like to have them real

This sounds more like an issue with cables or motors/encoders — when Gemini slews to a destination (even if it’s the wrong destination) a stop button becomes visible on HC and in ASCOM driver