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 Ekos or fully independent?
I run PHD2 as well with Ekos, I do not have the "Stop guiding
when mount slews" checked, but I have no experience of that
causing any problems.
Is your issue the wild runaway slews (what I understand as what
you mean by "bad slew"), or that slews are aborted by guiding? I'm
not sure I understand which. And what in the log makes you
conclude that the guide pulse leads to aborted slew? I don't
follow you there.
Again, maybe you know more about this than I do, I'm not a
programmer but have been using this setup for a rather
considerable time now.
Magnus
Den 2020-05-28 kl. 20:52, skrev Jamie
Amendolagine:
toggle quoted message
Show quoted text
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 not
have any guide pulses in it. The bad slew does though. The log for
the bad slew is attached a few messages before the good one. I
broke down the log in this post in this thread:?/g/Losmandy_users/message/66491
The bad one has this just after issuing the slew:
2020-05-27T06:42:20: Driver indi_lx200gemini: queuing
responsible for <newNumberVector device='Losmandy Gemini'
name='TELESCOPE_TIMED_GUIDE_WE'>
It's not clear to me what the gemini is supposed to do if it
get's a pulse during a slew. What it appears to do is abort the
slew, but the indi driver never seems to realize that the slew
is aborted.?
I looked it up in the indi code lx200telescope.cpp, and
lx200gemini.cpp and don't see any logic for aborting pulses
during slews. There is logic for that in phd2, but it does not
seem to be working. I didn't look up that code...?
Jamie
