search

TallFurryMan / kstars

Desktop Planetarium
GNU General Public License v2.0
0 stars 0 forks source link

Capture tab doesn't always select proper CCD #2

Open TallFurryMan opened 6 years ago

TallFurryMan commented 6 years ago

It happens that the capture tab, when loading a sequence, will not select the CCD which is referred to in the sequence file.

For instance, as stated in http://indilib.org/forum/ekos/3501-capture-tab-using-wrong-ccd.html, problem appeared when capturing frames using CCD #2, and starting a schedule job with a sequence on CCD #1. The capture tab used the CCD #2 when loading the sequence job, and was preempted by the guider tab which used CCD #2 too with shorter exposures.

  1. This is fatal for the observation as the capture tab is not able to detect exposure timeouts. On the opposite, guider tab is able to detect such timeouts and restart exposures. Thus a first fix is required in the capture tab to support timeouts, and a second fix is required to properly select the CCD, or at least warn the user if the sequence job is conflicting with the guider tab.

  2. This causes damage to the mount, as the Scheduler is unable to detect the timeout in the sequence neither. The Scheduler leaves the mount to track, and if no counter-measure exists on the INDI server, the mount doesn't stop tracking.

TallFurryMan commented 6 years ago

https://github.com/indilib/indi/pull/612 for the damage mitigation when the client is stuck.