Thanks for your suggestions Hy and Wolfgang, I will look into doing it the way you suggested.
I wonder if there could be an interest (and feasability) in adding iteration capabilities to the Ekos scheduler where you specify how many times you want to repeat the list. If not, at least there is a workaround.
Just wondering if it is possible to insert a delay between short OSC or luminance exposures in the Ekos scheduler, to capture the motion of asteroids over a few hours.
I am thinking of the Ceres opposition where I could take 30~60 seconds OSC exposures with a 10~20 minutes delay before the next exposure and so on for a few hours. That would make for a nice animation for a high school physics teacher neighbor.
Anything in place in the scheduler to accomplish that? Did not see anything obvious and it's not quite clear if the 'Delay' setting (below Filter) could be used for that purpose.
Since the latest git from a few days ago, (KStars 3.5.6 Beta running on ODroid C4) I have had strange behavior from the Polar Alignment Assistant (EKOS Align).
After I performed and successfully completed an eastward PA, I pointed the scope to my target (IC 1805) and performed a plate solve/ slew to target. I think the mount made the necessary corrections but it also unsollicitedly went in PAA mode, capturing an image and solving, moving the mount to the East for a second capture/solve, and again for a third and last time. I unfortunately do not have logs that could help explain this (which one should be enabled?) but I can try to reproduce the issue with logs enabled when the sky is favorable, likely tomorrow.
Any idea what may be happening here?
Latest 'indi_asi_wheel' from git does not crash anymore, thanks Jasem!
As the title says, latest indi_asi_wheel crashes when my Indi profile or indiserver -vvv indi_asi_wheel is executed.
2021-10-31T01:26:41: startup: indiserver -vvv indi_asi_wheel
2021-10-31T01:26:41: Driver indi_asi_wheel: pid=32843 rfd=3 wfd=6 efd=7
2021-10-31T01:26:41: listening to port 7624 on fd 4
2021-10-31T01:26:41: Driver indi_asi_wheel: sending msg copy 1 nq 1:
2021-10-31T01:26:41: Driver indi_asi_wheel: Searching for HID Device VID: 0x3c3 PID: 0x1f01
2021-10-31T01:26:41: Driver indi_asi_wheel: Searching for HID Device VID: 0x3c3 PID: 0x1f02
2021-10-31T01:26:42: Driver indi_asi_wheel: stderr EOF
2021-10-31T01:26:42: Driver indi_asi_wheel: restart #1
Child process 32843 died
... and so on for 10 times.
Going back to the stable-1.9.1 version works fine.
Thanks for a solution
Thanks very much for your findings, that's great!
I will hopefully be able to give it a try with your recommended settings whenever the clouds roll out, i.e. by the end of the week.
Being away from my system I can't give specifics but I found similar issues with the gpsd rules file conflicting with other USB serial devices. I had to comment out the specific gps device rules that were conflicting.
Furthermore there also is a conflict with the Davis Vantage device which grabs a port, even though I do not have a Davis Vantage, and makes connecting my Esatto focuser (IIRC) fail. I thus has to remove the 99-vantage.rules file to fix the issue.
I can provide specifics when I get back home, if needed.
I can confirm that NoMachine works very nicely for two independant instances of KStars/Ekos, controlling two mounts and telescopes, using ODroid C4. That will likely come in handy this winter as I can control everything from inside the house.
Not specifically the answer you're looking for but from what I read you are setting up an All-Sky camera, using Ekos and Indilib. You may be interested in a self contained All-Sky camera that does not use Ekos and Indi, such as the one presented by Thomas Jacquin on github.com/thomasjacquin/allsky .
His All-Sky can make use of diverse cameras such as: Raspberry Pi HQ camera, ASI120MC*, ASI120MM*, ASI120MC-S, ASI120MM-S, ASI224MC, ASI178MC, ASI185MC, ASI290MC, ASI1600MC, and are controlled by a Raspberry Pi. It may or may not satisfy your specific requirements but it may be worthwhile to take a look as it allows setting many operation parameters.
Hope this helps.
I had the same problem, with 'indiserver' disappearing after I wanted to reinstall indi-full, on Ubuntu Mate 20.04. Re-installing, for unknown reasons, did not install indiserver. That's when I decided to rebuild from sources, as noone, then, made any mention of that issue.
I don't recall that happening on other platforms than my Odroid.
I got the same problem when building indi-3rdparty from source on an ODroid C4 (Ubuntu Mate 20.04).
Looking at the CMakeLists.txt, I found out that I could disable the build for 'playerone' by setting the "option(WITH_PLAYERONE "Install Player One Astronomy's Camera Driver" On)" line to 'Off', thus getting rid of the error.
Not useful for those updating through standard update procedure but at least there is a workaround.
What scope do you have on the mount? I suspect an RC scope (10 inch?) but not sure as it also looks a bit like an SCT but the focuser and what looks like collimations screws raise doubts on my part.
I did not know that the StarGo2 could be used with the M-Uno! I thought it was meant for the new M-Due.
Differences between the two controllers could explain the problem but, as other things seem to work correctly, that would be surprising.
Good luck and keep us posted.
Check that the slew "Speed:" button, in the PAA window, next to the "Direction:" button, is set to "Max" and not a slower speed. My M-Uno PAA speed was set to "Guide" and I thought that the mount was not slewing but it was, at a painfully slow speed. Changing it to "Max" solved the problem.
That may, or maybe not, be your problem though.