开云体育

Hi! I really cannot see much in this, there is far too little detail about what is sent or the state of the mount. Do you say the the problem here is that in the second slew it never reaches the

You can also see in this log this exact thing happening. In the bad slew case, we stop getting slew updates after a pulse, and we never get a "slew completed" event. The attached files have more

Good idea about the kstars log, my first thought was to be able to see what the low layer was doing so I went with Indi. I run the Indi stack from init.d so it's separate from kstars. This is my

Hi! OK, then I understand a bit more. How come you do not take the Kstars log? At least I feel that is more readable, and you can see what Ekos is doing. Few more things: Do you run PHD2 connected to

Hey Magnus, This log is from indi. I run the indi server with -vvv argument (giving a massive log file). I parsed it and found both a good slew and a failed one. As you mentioned the good slew does

Hi! I'm not sure if I'm helping or just confusing, but thought I'd chip in since I have a similar setup. I found your log for a good slew here: /g/Losmandy_users/message/66498

solve the problem. yeah it seems that way. what a hassle, sorry to hear that but glad there's a temp fix I'm surprised this hasn't come up sooner jamie.amendolagine@...> wrote: -- Brian Brian

I did enable "stop guiding when mount slews" in phd. That feature seems to be broken? on the PhD/Indi stack for some reason. I let the Indi people know as well. So my workaround is to stop guiding

Jamie I looked at that thread - again, it seems specific to the Indi driver. i have not experienced that problem with the ASCOM driver. if i can find the time i may try out the indi driver to see if I

Hi Jamie pulses while slewing, and it seems that it doesn't, so that's the second issue. Did you try enabling "stop guiding when mount slews"? PHD for my windows ASCOM setup will continue issuing

https://indilib.org/forum/mounts/7065-losmandy-slew-goes-haywire.html

If you can give me the cable lengths you need from the NGC box to the encoders I can make up a cable for you. A photo of your encoder hookups from the RJ1-2 jack (RJ-11s are the same size but have 4

Hi! I'm not sure I understand your problem, but you mention Ekos and PHD2 guiding while slewing. That's more of an indi issue. Do you have a log showing that, or what makes you think it guides while

OK, so I think that I'm on to something here. M101 went behind a tree so I had just a few possible targets, each was having it's own issues, so I decided to just play around and test the guess about

You're right, quite the drift. So I'm out tonight and just got one of those wild slews. This time it happened during a plate solve, so it really seems like the same issue that the beta firmware fixes.

i'm not sure how we got from TCP and Indi discussion to this, but absolutely give it a try and love to hear the results jamie.amendolagine@...> wrote: -- Brian Brian Valente portfolio

Seems like this may be the same issue as Magnus found in another post. I'm going to try the beta firmware as that seems to fix it.

Oh, is that a setting in the handset?

i was referring to something else - "stop guiding when slew detected" PHD can send guiding commands and they do not interfere with slewing. or i should say they don't interfere under normal

I'm guiding with PHD2, and do have the option set to not send guide commands, but from the log they are being sent.