开云体育

On Wed, May 20, 2020 at 03:27 PM, Brian Valente wrote:

Paul would the "log everything" option also log lost/retry packets?

?Right. Unless the connection is really unstable and packets are constantly lost, this should not be an issue.

--

Brian?

Yes, Brian, any communication issues will be in the log, including any attempts to retransmit.

Regards,

? ? -Paul

OH, that with debug disabled. It does not seem to want to enable it. I'll try and get debug working.?

I just tried setting the debug enabled for the indi driver, and I do get some limited info that looks like this:?

--

--

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.

I would like to mount a guider on top of the main scope, but still have not found the proper rings.

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??

Thanks for a hint.

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.?

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?

PS. I have just lost this tiny cover screw. Damn it.

Sebastian

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?

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:

• I do all my slewing from skysafari running on a mobile device.
• I run the phd/indi/ekos software stack on a raspberry4 on the scope. I VNC in to access the rpi.?

I've noticed that when this happens, skysafari never seems to settle down. The "goto" button remains greyed out the entire time even after I reboot all the components, disconnect and reconnect skysafari. I need to shutdown and restart skysafari to be able to access the mount again. This makes me think that there is either something wrong between skysafari and the mount, or there is something wrong with skysafari. I know that udp is not a reliable connection so I though of switching that to tcp first, but it seems that tcp is maybe not an option for losmandy<->gemini<->indi<->skysafari. I may just try and switch to usb to see if that helps.?

These are the things that I'm going to try, ordering by least painful of a change:

• Switch to TCP (maybe not possible)
• Switch to USB for the mount connection instead of ethernet
• Switch to using kstars instead of skysafari for slews
• Switch back to stable builds for each of the components
• Profit!

--

I have a GM811G with spring loaded worm. I've found that increasing RA aggression is key to keeping the RA in check. I'd experiment with that value and see if it improves things. I've found that I can go above 100% for best results. My last try it was something like %135. I'd also recommend not making the RA clutch too tight. Make it just tight enough to prevent it from slipping in any position the mount may be in. The clutch screw puts pressure on a bearing, and I imagine that it could cause stiction if too tight.?

Jamie

Hi Sebastian,

I had a very light side by side setup as you have, even with 3 steps balancing I have always encountered balancing issues, very difficult IMO.

You still could check this guide for balancing in 3 steps if you are not already doing it:?

Cheers,
Carl

Taylor:

Here is my process for the newer OPW which is basically your's, but a bit more involved because of the Oldham coupler alignment .? This is mostly because with its design, the coupler is hidden so obviously Losmandy thinks it's alignment is not that important (which I don't think anyone has shown good data one way or the other).

1. Remove OPW from mount.
2. Loosen the cover screws, compress the blocks, snug the screws.? At this point the bearing blocks should be co-linear in the cover.
3. Attach OPW to mount, snug screws attaching to mount with an approximate mesh of the worm to the gear (so the angle of the worm assembly relative to the gearbox is close for next step).
4. Remove the OPW cover so you can see the Oldham coupler, then adjust the gearbox and coupler as per Michael.? (This is the unfortunate part of the OPW design if you care about coupler alignment.? I've contemplated drilling out an Oldham viewing/adjusting port in the OPW but I don't like modifying stock parts).
5. Re-attach OPW cover, then tweak mesh using the standard method.

Keith

OH, and I just tried setting the indi losmand connection to tcp with port 4030, and I get an error:?

2020-05-20T05:34:24: [ERROR] Error reading from device Read Error: Resource temporarily unavailable (-1)

I often have issues with the mount just kind of "loosing it!". It's usually with a slew, and I either have to send the stop command or turn it off.? My setup is ekos/indi/skysafari and I'm using the ethernet connection. I use udp for the connection and I'm wondering if the udp connection is loosing some command causing this. I realize that it's just a crossover cable, so not a lot of chances for messages to get lost, but that does not stop me from wondering if switching to tcp will help. I can't find a lot of info on using tcp other than?

HC plugged into HC port as it should be.