I noticed that you specify a "-j3" option when making, is that so that it can 'make' the software without failing on the ODroid N2? I had tried "-j4" on the C4 and make failed before completion so I reverted back to "-j2".
Hello again Jerry,
I just ran your script on my laptop, with "-DBUILD_TESTING=OFF" added to the KStars cmake, and everything went fine. Great job! I will try it on my ODroid next.
Thanks for your script Jerry, it will surely make building the KStars/Ekos/Indilib suite much simpler. Great idea!
If I may ask, would it be possible to add a "-DBUILD_TESTING=OFF" cmake option to the KStars build as building for smaller machines (Raspi, ODroid...) tends to fail when it gets to the KStars test suite, and they may not be necessary for those running Raspi or ODroid?
I will add it to my version of the script but others may benefit from this option as well.
Very nice setup, it looks so compact. It seems to me that it could almost fit in a 60cm on a side box!
I get away with only one profile for 3 cameras, main, guide, and PoleMaster (auxiliary device). The main and guide (through OAG) cameras use the main telescope info (f.l. and aperture), and I have set the guide telescope info with the PoleMaster lens specs. So, when I perform the PA, I specify the PoleMaster as the camera to use, and the 'guide' scope, as the optics to use.
When the PA is done, I revert back to main camera and guide camera, through 'main' scope.
In your situation, your ASI178 could be the auxiliary camera and the 50mm lens, your 'guider' optics.
Hope this helps.
Thanks for your reply. I would have hoped that the data was accessible without human intervention but, as PA is done once every "once in a while occasion" or whenever the mount is moved to a new location, transcribing it for the PAA screen to my application won't be a major issue.
Thanks also for the great work you do on PAA and SEP Multistar guiding, they are much appreciated.
Is it possible to get the altitude and azimuth polar alignment error data from Ekos so I can use it to control the motorized polar alignment of my Avalon M-Zero OBS mount? I have built the hardware and software to make it work with a simple NSEW keypad when close to the mount but I would like to control it by software, either python script or Indi driver, remotely and, ideally, automatically.
Thanks for any help and insight.
A bit more info that may or may not be helpful in finding and fixing the problem for the Esatto/Sesto Senso 2 focuser driver.
Just to make sure the problem was not residing in Ekos or between Ekos and Indi, I decided to test my Esatto focuser movements from the Indi panel only. I started from the 180000 'focused' position, set the absolute position input panel to 175000 and clicked on the set absolute position button. According to the absolute position panel, the focuser moved to an 'arbitrary' position between 180000 and 175000. Without changing anything, I re-clicked on the set absolute position button and the absolute position panel changed to 175000 without any movement or motor sound from the focuser. Did the same going back to absolute position 180000 and the behavior was the same: wrong position, click again, correct position displayed.
I wanted to do the same with relative position to see if the behavior would be the same but a zero relative position is, logically, not permitted. I would assume though that if the source of the problem and the solution are found for absolute position, the solution would be the same, or similar for the relative position.
Hope this helps.
I am having the same problem with my Esatto. On autofocus, it does a first move and sits there with a wrong position in the panel. It should have moved 5000 steps but reports a position much less than 5000 steps away from original.
Not knowing how the driver works, it seems as if the driver reads the focuser position only once and waits for the focuser to get to the prescribed position, which it never does softwarewise but does hardwarewise. This, I would assume, would make the autofocus procedure wait forever as it thinks the focuser is not there yet.