https://bugs.kde.org/show_bug.cgi?id=418159
--- Comment #14 from mountainai...@outlook.com --- Jasem, I take that back. I got the scope out again last night, and the first thing I did was open the mount control pad and slew in RA. The values didn't change. But when I slewed in DEC, suddenly the values changed in RA, too. I couldn't trigger it again. I don't know what this means. I will check the handset values the next time I'm out, but I've never noticed that not changing. I can also try another hand controller, on the off chance there's something going on with StarSense. One other thing (sorry for piling on the observations): In the PA tool, when it works perfectly it does seem to slew 30 degrees (twice). Then there are times where it still works, but it slews *almost* to the limits (even with RA changing). It's strange. 110-120° instead of the expected 60. PLEASE READ: This is probably a separate issue, but it might be related. All of a sudden last night Ekos started acting very laggy (spinning MacOS beachball almost anytime I click on anything). In the PA tool, when I clicked start it would wait almost a minute before taking the first photo. The same thing would happen with subsequent images. The focus module was unusable. I gracefully quit the application and re-launched; same. I rebooted the Mac (connected to RPi); same. Rebooted the RPi; same. It did not happen when I VNC'd into the Pi. The reason I mention this is because if it hung right after I clicked the slew button, it might explain why RA didn't update and then it suddenly update later. Maybe the DEC trigger was just a timing coincidence. I wonder about this regarding the PA issue above, too. If it occasionally hangs after it sends the slew command, it might power past its 30 degrees. This is a 16GB MacBook Pro with 2.3 gHz quad-core i7, and nothing else running. I don't think the machine was resource-constrained. -- You are receiving this mail because: You are watching all bug changes.
