|
Re: What's wrong with this mount? Help please .
¿ªÔÆÌåÓýThat depends on the rings. ?These rings are rock solid and a huge improvement in stability: ??On May 20, 2020, at 3:28 PM, Brian Valente <bvalente@...> wrote:
|
|
Re: TCP connection
OH, well whatdayaknow I have the logs. I believe that this is where it happened:
So I believe that this time log is GMT so that would equate to?12:50 AM pacific time and looking up?16:42:24 - DEC: 36:25:22 I believe is Hercules 2020-05-19T07:53:07: Losmandy Gemini: [INFO] Slewing to RA: 16:42:24 - DEC: 36:25:22 2020-05-19T07:53:40: Losmandy Gemini: [ERROR] Error reading from device Timeout error (-4) Not a lot of log data, but if I remember correctly this is where it started slewing to lala land. I can't remember if it was the ground or if it was going to hit something. This is still not a lot of info I know. I'll have to look into gemini.net to see if I can get some detail there.? |
|
Re: OPW Adjustment Steps with Belleville Washer
Seb, My thinking is: The Oldham coupler is best left in place, but not tightened down until the end of the assembly process. So...as you said: 1. Get the worm in its final position ? ? a. Tight within the left and right worm blocks. ? ? b. The worm blocks are lined up straight ? ? c. The worm is gently in full contact with the ring gear teeth. ? ?d. Both work blocks are tightened down. ? ?e. The worm can spin pretty easily? by your hand and not feel pinched 2. Put on the Oldham coupler metal part on the worm, and gently put on the white plastic center, but only lightly set the setscrews.? You will move the coupler later. 3. On a straight old type drive: ? ?a. Put on the other metal Oldham coupler part on gearbox drive shaft.? Again, don't tighten it much as you may have to move it in a later step. ? ?b.? Put the Oldham coupler firmly into each other, as you also line up the gearbox shaft with worm shaft.? I had to use a thin round file (aka "rat-tail" file) to slightly enlarge my gearbox mounting holes, to get the gearbox exactly in the best position. ? ? c. Rotate the worm if possible to see that the Oldham parts only rotate...you prefer the white plastic center to not slide, and you prefer no angle between the gearbox shaft and the worm shaft. ? ? d. Then bolt down the gearbox position. ? ? e. Then, you may want to loosen the Oldham parts:? slide them so that the white middle is exactly centered in the gap between the Gearbox shaft and the Worm shaft.? And make sure the white center is tight between the metal parts. Here is a photo of a DEC axis with original 2 piece worm blocks and precision brass worm. If you look carefully, you can see the far (right) bearing block has its bearing sticking a bit out (toward the worm), because the R4 Belleville washer under the bearing is pushing it that way from under the bearing. The bearing there was polished down in OD and lubed to slide in it's mounting cylinder sleeve. 4. On a newer tucked motor system: There is also an Oldham coupler hidden in this system too.? It is very hard to get to this.? The coupler in this system attached between the worm shaft and the inner transfer drive gear shaft.? Again, try to line the Oldham parts up.?? Best of luck, Michael On Wed, May 20, 2020, 12:14 PM Sebastian Kotulski <sebkotulski@...> wrote: I don't have a OPWB. Not yet. My plan is to remove the scope, ?counterweiht, counterweight bar and a worm cover. Than I will remove the motor and a gearbox. Then I will slightly rotate the ra axis and lightly press the worm against the worm gear while holding the worm blocks between fingers. I will lock the worm block srews and try to rotate the worm with my fingers and also check if it moves between the worm blocks. If there is any movement between worm block or excesive backlash between wom gear and worm I will repeat the proces. I dont exactly know what I should do next. Should I mount the coupler to the worm shaft or gearbox shaft? |
|
Re: TCP connection
On Wed, May 20, 2020 at 03:27 PM, Brian Valente wrote:
Yes, Brian, any communication issues will be in the log, including any attempts to retransmit. Regards, ? ? -Paul |
|
Re: TCP connection
I just tried setting the debug enabled for the indi driver, and I do get some limited info that looks like this:?
2020-05-20T20:38:53: [INFO] Slew is complete. Tracking... 2020-05-20T20:38:42: [INFO] Slewing to RA: 7:28:13 - DEC: 49:10:12?
2020-05-20T20:38:15: [INFO] Slewing to RA: 7:56:27 - DEC: 47:36:46?
2020-05-20T20:37:42: [INFO] Slew is complete. Tracking...
2020-05-20T20:37:22: [INFO] Slewing to RA: 7:56:27 - DEC: 47:36:46? I'll leave that on and next time it happens, I'll look through it. I'm not sure what gemini.net is, I'll look it up.? |
|
Re: TCP connection
On Wed, May 20, 2020 at 03:21 PM, Jamie Amendolagine wrote:
That makes sense. So it sounds like the gemini protocol implements reliability on top of udp. So that should not be the issue. Is that right?? ?Right. Unless the connection is really unstable and packets are constantly lost, this should not be an issue. |
|
Re: TCP connection
Thinking about your response a bit more, it seems what you're saying is that since the protocol doesn't use a "stop" command, a flaky udp connection should not leave the mount slewing forever or really badly. So maybe somehow between skysafari and the mount a wrong slew command was issued and that's why the mount goes off to lala land. If that's the case then removing skysafari from the equation might fix it. Updating the software stacks to stable might also do it. Next time I'll enable logging to see if I can capture the commands that are sent to the mount. -- OH, but what if udp doesn't deliver a complete command and some data is left out giving a malformed command? So many things to consider...
Jamie.? |
|
Re: TCP connection
Hi Jamie,
Gemini? UDP is protocol is designed to allow for retransmission of failed commands. Gemini.NET will try a few times to get Gemini to respond, but will give up after a few unsuccessful attempts. At this point it will display an error message about the lost connection. Regards, ? ? ?-Paul? |
|
Re: TCP connection
You're right "it just kind of looses it", is vague.?
Just as some background, it may just be my setup because I've been compiling the components from source and usually using the "master" branch so it's going to be hard to track down issues.? The issue is a little hard to explain, but I'll try. This never has happened during the initial slews or plate solving. It usually happens after doing some imaging on a target for a while, then slewing to a different target. I can usually tell that something is going wrong because I can hear the motors running at a high rate and not slowing down. So I step out of my little house next to the scope and see the mount slewing somewhere completely wrong like pointing into the ground, or going way too far so that the wires start to wrap around the mount. I usually intervene by either stopping the mount with a command, or by turning it off before something get's damaged.? I don't want to even ask anyone to diagnose my setup as building from master could introduce all kinds of issues that would be hard to trace down. This is why I'm trying to just switch individual aspects one-at-a-time to see what might be causing it. UDP/TCP seems like a good candidate so I'm trying that.. I used to build from stable tags, but at some point those became unusable because my zwo guide camera would disconnect before getting a single shot. I switched to master and I don't have this issue. I try every once in a while to switch back to a newer stable tag, but so far I have to stay on master.? Here's my setup:
These are the things that I'm going to try, ordering by least painful of a change:
|
Timothy Campbell
Jamie Amendolagine
Michael Herman
Paul Kanevsky