https://bugs.kde.org/show_bug.cgi?id=410094
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|UNMAINTAINED
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #23 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=410094
Jasem Mutlaq changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #21 from Jasem Mutlaq ---
The only place where this happens is in sendNewNumber(...) so it sets the EQNP
property to IPS_BUSY. However, processNumber(...) in Align class looks for
updates in EQUATORIAL_EOD_COORD (sent by the driver). So this
https://bugs.kde.org/show_bug.cgi?id=410094
James Lancaster changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=410094
Jasem Mutlaq changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kst |https://commits.kde.org/kst
|a
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #18 from James Lancaster ---
Well, there's at least one instance seen here that I looked at.
[2019-08-22T14:00:48.074 CDT INFO ][ org.kde.kstars.indi] - LX200
OnStep : "[INFO] OnStep: Synchronization successful. "
[2019-08-22T1
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #17 from James Lancaster ---
Created attachment 122295
--> https://bugs.kde.org/attachment.cgi?id=122295&action=edit
Kstars log after patch using CCD simulator
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #16 from James Lancaster ---
I have had some troubles and the one (real sky) test I did have (where I also
put a timer in) worked, but had other issues, so I'll attempt to sim it again,
shortly.
Did you want wireshark or just kstars logs?
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #15 from Jasem Mutlaq ---
Did you have a chance to test this? I included this patch in KStars by mistake
as well. So if you just compile from git, you can test it out right away.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #14 from Jasem Mutlaq ---
Created attachment 122087
--> https://bugs.kde.org/attachment.cgi?id=122087&action=edit
align debug patch
I don't think we should opt for the hack-workaround just yet. Can you please
apply this patch and share th
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #13 from James Lancaster ---
So different periods do affect how often it gets triggered.
However, when I tried set at down at 100ms (really more like 200-250ish) and
locally 17/25 instances encounter it. If it's at 1 second, maybe 1/10 do.
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #12 from Jasem Mutlaq ---
Ok I'm not sure...
Is the driver update period 250ms? I see 4 IPS_BUSYs in 1 second. If that is
the case, just try to make the period 1 second and see if that makes any
difference?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #11 from James Lancaster ---
That case the Idle > OK is because of me turning tracking on. Then the mount
model starts slewing it. Ok > Busy
(Seen in packet 16405) :Te# sent (Tracking Enable)
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #10 from Jasem Mutlaq ---
Thanks for the logs! Do you know why in #16483 the state was set to Ok?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #9 from James Lancaster ---
Created attachment 121980
--> https://bugs.kde.org/attachment.cgi?id=121980&action=edit
kstars log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #7 from James Lancaster ---
Realized something just before posting this, make sure you read to at least the
note
I apparently didn't save the wireshark log, but I was able to reproduce it.
Attaching it with large packets removed, and
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #8 from James Lancaster ---
Created attachment 121979
--> https://bugs.kde.org/attachment.cgi?id=121979&action=edit
Wireshark Log
Log with ignoring packets above 1 bytes (as it's using the CCD simulator
and it ballons the size, even g
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #6 from Jasem Mutlaq ---
Thanks for the detailed report! This should win the trophy for the most
_detailed_ bug report yet! However, the attachments are missing and I need to
put the two logs (wireshark + kstars) next to each other to get a
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #5 from James Lancaster ---
Adding a couple more, it seems much more rare, but it still seems to happen, I
added more print statements, and ended up with this, didn't get a wireshark
capture, but this seems just odd.
Chronoloical order is
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #4 from James Lancaster ---
The settle timer operates from when it thinks the end of a slew is and is up to
15 seconds long, whereas slews (especially meridian flips) might be minutes.
I went back to the version in git, rebuilt kstars. Als
https://bugs.kde.org/show_bug.cgi?id=410094
--- Comment #3 from Jasem Mutlaq ---
There is already a settle timer, so I don't think adding another timer is the
right approach. There is a problem with the state transition.. so what is
causing that? some race condition? driver issue perhaps?
--
Yo
https://bugs.kde.org/show_bug.cgi?id=410094
James Lancaster changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=410094
Jasem Mutlaq changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kst
|
24 matches
Mail list logo
