I built everything on Debian 10 about a week ago using the latest stable tagged branches from each repo. Should you choose to do it manually rather than via the script above the main issue is installing all the dependencies you need Assuming you already know how to use git that is. If not, have a read about how to checkout a repo and switch to a named/tagged branch and you'll be all set.
If it's of any help, here's what I built and iirc the order I did it in:
I have a fork mount LX90 scope with a long enough optical train that I can't image any object within around ~25 degrees of polar home without a mount crash.
Is there anyway to add a circle around Polaris with a given degree radius so I can determine when an object is getting close to risk a slew? Also, any way for Ekos to refuse to slew to an object within X degrees/minutes of polar north?
The indi 3rdparty SX drivers for Starlight XPress cameras appears to be failing to build under v1.9.0 of indilibThere's a few deprecation warnings and then errors over setInterlaced on PrimaryCCD and GuideCCD. Looking at the current git source setInterlaced appears to have been commented out?
Has v1.9 being released before all the 3rd party drives have been updated?
Hi all, I've got the solver setup and index files installed in kstars 3.3.6 via the snap package, but when I try a load and solve it returns
2019-10-01T21:20:20 Solver failed. Try again. 2019-10-01T21:20:20 Starting solver... 2019-10-01T21:20:20 Solver iteration #1 2019-10-01T21:20:20 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 202.591 -4 47.1381 -5 15 2019-10-01T21:20:20 FITS header: cannot find FOCALLEN (keyword not found in header).
-O --no-plots --no-verify --resort --downsample 2 -L 14.402 -H 18.003 -u aw -3 202.642 -4 47.0878 -5 30
2019-10-01T21:59:56 Using solver options: -O --no-plots --no-verify --resort --downsample 2 -3 202.524 -4 47.1485 -5 15
I hadn't realised it was just a warning rather than a configuration error and the makefile was still able to be generated. I've set a build off now.
It looks like that package isn't in debian stretch and I it doesn't look like it'll be buildable without a newer version of QT than stretch ships with.
What is it that is making use of datavis?
I'll be doing a build of this and latest stable indilib tonight so no comments on the 2.9.3 itself, however, when I went to check the git repo out, the tags are a little confusing.
Latest stable is v2.9.3 yet there's v3.x.x and v4.x.x as well as v16/17 etc. I assume the latter are for ubuntu but what are the v3.x and v4.x tags? They're several years old so not the latest, which makes the version numbering odd?
Is there a way to have the guide graph continue to update when rapid guide mode is in use?
Also, what do the other options on the guide cam tab such as "auto loop" do?
Just in case there's an issue detecting the slew complete, try turning on the driver debug messages and doing a slew and see if there's a message logged for slew start and slew complete.
If you see those messages (I can't remember if they're in by default or if i added them when I was testing a similar issue with my lx90 and the autostar driver) then set the scope to slew over quite a large area that will take several seconds to complete. Then monitor the debug output and see if it reports back that the scope has completed the slew whilst the scope is still visibly moving.
Won't solve your issue but might help determine if there is some issue with reporting slew complete or not.
I recently completed a project to build a "hat" pcb for the Raspberry Pi 3 to drive a Moonlite focuser via the PIs GPIO pins and a DRV8805 controller. As I use Ekos/INDI for my imaging I also wrote a new focuser driver for it.
On the off change this is of any use to anyone else the hardware is available under the CERN OHL and the driver is available under the GPL3.
There's more information about the project on my website along with links at the bottom of the page to several blog posts that cover the issues I encountered during the project and mistakes made (quite a few ).
If you just want to see the driver it's on bitbucket in the indi_driver/indi-mupastrohat/ directory.
Sadly there's only been one night of clear skies since finishing the project, so whilst I managed to test the focuser out and know everything works, I've yet to get time to take any images with it Fingers crossed this month is better than December was.