Starting at timestamp [2022-09-30T22:45:02.978] in your log, there are more than a few move absolute commnads sent in just 6 milliseconds.
Sending this many move commands, not sure what it does to timer_hit with all the remove/set's done at the end of MoveAbsFocuser.
The above does not help with your autofocus issue, is your power to the unit known good?
Something that may get you closer on the INDI side is work by WOTALOTA.
Check out thread:
The GIT seems to have moved for the source.
If you are in the 'Downloads' directory, to specify the destination you need an absolute file path
sudo mv indiwebmanager.service /usr/bin
-but- 'service' files usually live in
So it would be
sudo mv indiwebmanager.service /etc/systemd/system
A real back of the envelope calculation
Plugging in 72mm, 420mmFL, 0.85FR, 2.4umPIX and 687 pixels donut size I get approx 8mm.
Best guess is the sealing glass cover on the front of the CCD camera itself
Be advised, if you (or anyone) decides to get a printer, the number of things I found to print/fix keep growing.
Len's caps for finders, knob for RedDot, side bracket (broke and glue was no use for original) for RedDot, ESP32 cases for DSC control, DSC gears/adapters, 2inch to T-2 adapter, plus a multitude of adapters/gadgets for around the house and car.
The printer 'justification' came about when I picked up an 8inch Dob for a great price that adding a printer would come up to about what the scope's value.
Then adding the DSC's to it.
I have found the 3D printing world opened a world of things to help astro gadgets.
Here is a printable case, designed with RTC and fan in mind and used by author for astronomy.
You do not need a printer if only doing a few one off's, I have used various services to print models. Not an endorsement, upload file to print and then see various vendors willing to print along with cost.
Using PLA material is good enough if scope not going to be out in the sun for extended periods of time, going PETG if it is.
Check out the focus.h, it identifies d_bus interfaces
I have not used it but another data point
The changelog shows:
Version: 1.3 (2021 September)
For the SBDB
The 400 response code is for a direct query, does kStars use asteroids.dat from asteroidscomponent.cpp or ?
Have you seen this tutorial?
I believe it has some of what you are looking for.
The Kstars/Ekos API reference for controlling
Something does not sound correct in your startup.
Indi, via EKOS, should be running with the indi_dsi_ccd loaded and running prior to starting PHD2 Connect.
You can try just launching indiserver with indi_dsi_ccd, no Kstars or Ekos, to get there
Open a terminal window
/usr/bin/indiserver /usr/bin/indi_dsi_ccd (given the paths you provided above).
Does this error out for you?
Then launch PHD2 and do the Connect.
Unfortunately I am about 1k miles from my astro equipment for the next few days, and I have 3 various flavors of DSI (1 mono, 1 color, 2 mono) to walk it all through.