ok, done the above.

I get the following message:

log file:

I see the following in the log file:

[2018-06-27T12:58:35.599 CEST INFO ][ org.kde.kstars.ekos] - "Unable to establish remote devices:\n\nPlease ensure remote device name corresponds to actual device name."
[2018-06-27T12:58:35.639 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Ekos failed to start."
[2018-06-27T12:58:35.666 CEST INFO ][ org.kde.kstars.ekos.scheduler] - Stopped.

I don't get it, all the devices I asked to start up are up.

indi-web:


ekos:

I solved the "Ekos failed to start.", I should have picked Guider Simulator instead of CCD Simulator in the Guider section.
Now the roof opens, mount slew, and start taking pictures...

However, I got the following new issue:




The job in the main window shows as complete, while in the scheduler it's still running and never finishes.

This I got very recently : the capture tab was using the same ccd as the guider tab for an unknown reason, even though the sequence file specified a different one. Check in the log which device is running which capture. The guider tab is able to detect timeouts, but not the capture tab. If that's the reason, the scheduler stalls and bad things ensue.

-Eric

Could you please elaborate on this?
thanks

I logged this at github.com/TallFurryMan/kstars/issues/2 in an attempt to list what I should work on.

-Eric

What I observed is that when the capture tab executes a capture, and the capturing device doesn't reply with a notification, the capture tab remains stuck.

-Eric

I got you, so do we think this is actually a bug somewhere?
Worth deeper investigation?

Obviously, the scheduler should run without this issue, unless this is only affecting the CCD Simulator. Maybe I should try with the real CCD?

This occurred once on my physical setup this week (but wasted the observation time). Worth investigating yes indeed, but I had no time to delve into it yet. There's a parking state issue when playing with indi connection/disconnection that is more annoying to me.

-Eric

I proposed phabricator.kde.org/D13769 for the qt slot connection warnings, and for proper job evaluation when editing.

-Eric