Hello,
I stumbled upon a weird issue this night. I have an Atik for imaging and a DMK/V4L2 for guiding.
Before the observation session, I took some darks for the DMK camera in the capture tab.
When proceeding to observation using a simple 480-second on M13 with the Atik, the capture tab kept the DMK camera to capture. This conflicted with the guiding tab, which got priority given the lower periodicity of captures.
This is an excerpt of the log at the moment the issue shows up (that is, very first capture):
[2018-06-25T00:50:26.397 CEST INFO ][ org.kde.kstars.ekos.guide] - "Calibration completed."
[2018-06-25T00:50:26.424 CEST INFO ][ org.kde.kstars.ekos.guide] - "Autoguiding started."
[2018-06-25T00:50:26.497 CEST DEBG ][ org.kde.kstars.ekos.guide] - Capturing frame...
[2018-06-25T00:50:26.509 CEST WARN ][ org.kde.knotifications] - Audio notification requested, but sound file from notifyrc file was not found, aborting audio notification
[2018-06-25T00:50:26.684 CEST INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Started 5.000-second manual exposure. "
[2018-06-25T00:50:26.972 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Checking job stage for "M 13-1" startup 2 "25/06/18 00:40" state 3
[2018-06-25T00:50:26.972 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Calibration & Guide stage...
[2018-06-25T00:50:26.973 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'M 13-1' guiding is in progress."
[2018-06-25T00:50:27.004 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Get next action...
[2018-06-25T00:50:27.115 CEST DEBG ][ org.kde.kstars.ekos.capture] - Initial hour angle: 0.268805
[2018-06-25T00:50:27.116 CEST DEBG ][ org.kde.kstars.ekos.capture] - Initial mount coordinates RA: "16h 42m 20s" DE: " 36° 25' 42\""
[2018-06-25T00:50:27.116 CEST INFO ][ org.kde.kstars.ekos.capture] - "Ekos will refocus in 1200 seconds."
[2018-06-25T00:50:27.151 CEST DEBG ][ org.kde.kstars.ekos.capture] - Preparing capture job "Light_LPR_480_secs_ISO8601" for execution.
[2018-06-25T00:50:27.328 CEST INFO ][ org.kde.kstars.ekos.capture] - "Capturing image..."
[2018-06-25T00:50:27.359 CEST INFO ][ org.kde.kstars.ekos.scheduler] - "Job 'M 13-1' capture is in progress..."
[2018-06-25T00:50:27.423 CEST INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[WARNING] Stopping running exposure 4.207 seconds before completion "
[2018-06-25T00:50:27.427 CEST INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Started 480.000-second manual exposure. "
[2018-06-25T00:50:27.972 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Checking job stage for "M 13-1" startup 2 "25/06/18 00:40" state 3
[2018-06-25T00:50:28.972 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Checking job stage for "M 13-1" startup 2 "25/06/18 00:40" state 3
[2018-06-25T00:50:29.972 CEST DEBG ][ org.kde.kstars.ekos.scheduler] - Checking job stage for "M 13-1" startup 2 "25/06/18 00:40" state 3
Right now I have no idea why the DMK was selected. This is the header of the .esq:
<?xml version="1.0" encoding="UTF-8"?>
<SequenceQueue version='2'>
<CCD>Atik 314E CCD</CCD>
<FilterWheel>Filter Simulator</FilterWheel>
<GuideDeviation enabled='false'>2</GuideDeviation>
<Autofocus enabled='false'>0</Autofocus>
<RefocusEveryN enabled='true'>20</RefocusEveryN>
<MeridianFlip enabled='true'>0</MeridianFlip>
<Job>
<Exposure>480</Exposure>
The conflict caused the target capture to wait indefinitely. While the guiding process detected the timeout, the capture tab just stood there doing nothing for a few hours. Scheduler did not react neither, which is a good opportunity for me to add some robustness code.
