Guiding failure resets capture count? - by: RogueSquadron

Hello,

I have the following issue: When guiding error is out of tolerance and capturing is stopped and resumed, the image counter starts to count from 1 again.

See the following log:

2018-08-29T22:53:21 Capturing 300-second image...
2018-08-29T22:53:20 Received image 1 out of 20.
2018-08-29T22:47:37 Capturing 300-second image...
2018-08-29T22:47:37 Job requires 300-second images, has 0/20 frames captured and will be processed.
2018-08-29T22:47:37 Guiding deviation 2.14 is now lower than limit value of 3 arcsecs, resuming exposure.
2018-08-29T22:47:31 Guiding deviation 12.6 is still higher than limit value of 3 arcsecs.
2018-08-29T22:47:23 CCD capture aborted
2018-08-29T22:47:23 Guiding deviation 3.92 exceeded limit value of 3 arcsecs, aborting exposure and waiting for guider up to 60 seconds.
2018-08-29T22:47:12 Capturing 300-second image...
2018-08-29T22:47:12 Received image 1 out of 20.
2018-08-29T22:41:31 Capturing 300-second image...
2018-08-29T22:41:31 Job requires 300-second images, has 0/20 frames captured and will be processed.
2018-08-29T22:41:31 Guiding deviation 2.31 is now lower than limit value of 3 arcsecs, resuming exposure.
2018-08-29T22:41:15 CCD capture aborted
2018-08-29T22:41:15 Guiding deviation 9.42 exceeded limit value of 3 arcsecs, aborting exposure and waiting for guider up to 60 seconds.
2018-08-29T22:38:23 Capturing 300-second image...
2018-08-29T22:38:23 Job requires 300-second images, has 0/20 frames captured and will be processed.
2018-08-29T22:38:23 Guiding deviation 1.89 is now lower than limit value of 3 arcsecs, resuming exposure.
2018-08-29T22:38:16 CCD capture aborted
2018-08-29T22:38:16 Guiding deviation 9.68 exceeded limit value of 3 arcsecs, aborting exposure and waiting for guider up to 60 seconds.
2018-08-29T22:34:05 Capturing 300-second image...
2018-08-29T22:32:11 Setting temperature to -20 C...
2018-08-29T22:32:11 Job requires 300-second images, has 0/20 frames captured and will be processed.