I want to point out that there is a longstanding issue in the Find object tool that is leaving out some objects that do exist in the database catalogues. In this example I show the incomplete list of Hickson galaxy groups in the Find tool. Then I pull up the database and open details of a couple examples that were not coming up (Hickson 90, 68). Upon doing so, the selected objects will appear in the Find tool. So it appears KStars is not loading all the database information itself. This issue likely also affects other catalogues, but I haven't looked at them as closely.
The way the driver itself is written is not setting any particular step state. It simply commands it to take an integer number of steps, but there is a variable to scale that integer relative to the microstep dip switch setting. Not changing one or the other will have consequences in terms of speed and step angle. Or the wrong scaling can cause you to run up to the step limit.
I have an earlier post in this thread that explains how the dip switches actually behave.
Hold coil power is an electronic break in a sense. I could see that being useful for some with heavy loads and poor focusers that can slip. But I do not have that issue. Motors in a hold state will also use power and can get hot. So it has drawbacks too. I also have a geared drive that can not be back driven.
I have a custom enclosure for the Pi with a mounted db9 socket with wires soldered to leads on the HAT.
You only need to change the dip switches to select the microstep mode. But for more customized tuning, a few modifications to the code and self compiling it is an option.
I've used a 6 foot DB9 cable to reach the motor and it seems fine.
In the driver you can not change the microstep mode, but you can adjust the delay.
Also you described the motor making a noise and warming up. That is the enabled mode. It's not desirable. There are two revisions of the board. Rev 1 enable pin pulled low, Rev 2 enable pin pulled high (if I recall chevron). If you bought it recently you probably have rev 2 and need to set that in the indi driver.
Very nice. Just like Al's collimation aid, but for Linux
Do you plan to have this tool incorporated into KStars someday? Or have you considered adding some INDI client functionality to connect to a camera for live view, focuser, and maybe even recentering mount all-in-one place?
None that I know of. I said you can set a custom tracking rate.
But if you're able to modify the driver source code, then you should just do that cabs give it a unique name.
You can probably calculate the new ratio and work out a custom tracking rate that can be set in the INDI driver.
You need to check the manual slew box in the PAA tool before you take your first alignment image. It will then wait for you to push the mount, by no specific degree. 15°-30° will do. Then you trigger it to take the next alignment image.
Just now, Norder6 and 7 torrents started downloading fine for me from the single seed currently alive.
Thank you kindly for the complete list.
I was working from the AstroPi script, which is evidently out of date, and adding what ever I was told was missing.
I ultimately got it to build. But I might've missed something. As some things weren't quite right.
I am working on compiling KStars on Ubuntu Mate. Yes, I am aware it is available pre-compiled from the repository. But I have some custom code for KStars to build myself.
I have been pretty successful at finding the needed dependencies sofar. But these two have been hard to satisfy.
Package 'kio-dev' has no installation candidate
Package 'kdoctools-dev' has no installation candidate
What packages do I need to install to satisfy these dependencies on Ubuntu Mate 22.04 Jammy?
Thanks. I believe you are correct. Going to work on it some more later.
Now, I just hope PHD2 is ok.