Is there a way to see exactly why BYE stopped taking subs?

[TheRealEleven]

I had BYE set up to take 10 darks unattended. I came back a couple minutes early and it appeared finished. It was very late (6:45am, been up all night) and I still had to do Flats and Bias so I wasn't paying attention.

 

I get the rig put away and get on the PC to look at what I gathered all night and notice that BYE just stopped halfway through the 8th Dark frame. I have the logs, but I can't really see what happened. Can anyone help?

logfile-[20180322-02h46m15s445]-[7212]-2018-03-22.txt

[astroman133]

I do not remember any other BYE users reporting this type of issue before. I understand that you would rather not have issues like this, but I would suggest trying it again to see if it was a one-time glitch or is evidence of a repeatable problem.

Also, I can see where the 300 second image was terminated early, but according to the log, you clicked the Abort button to end the capture plan. Here are the relevant lines from the log.

2018-03-22 06:32:18,321 [CameraTakePictureOnMessageRecieved] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(Not supported) Duration(300.0) Iso(800) Quality(IMAGE_RLF+) Mirror(0) SaveTo(CARD)
2018-03-22 06:32:19,587 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(CameraRef, 2, 0)
2018-03-22 06:32:19,727 [CameraTakePictureOnMessageRecieved] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 2, 0)
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=1) (inContext=0)
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - Items waiting to be transfered...
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - StateEvent_BulbExposureTime Fired! (inParameter=0)
2018-03-22 06:32:34,575 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:33:35,409 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:34:36,260 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:35:16,312 [Main] DEBUG - ButtonPlus_MouseClick(btnAbort = 'Abort')
2018-03-22 06:35:16,344 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(CameraRef, 3, 0)
2018-03-22 06:35:16,359 [CameraTakePictureOnMessageRecieved] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 3, 0)
2018-03-22 06:35:16,359 [CameraTakePictureOnMessageRecieved] DEBUG - Abort seconds = 176
2018-03-22 06:35:16,453 [CameraTakePictureOnMessageRecieved] INFO  - Timespan 178.257
2018-03-22 06:35:16,469 [CameraTakePictureOnMessageRecieved] DEBUG - Camera BUSY flushing ObjectsWaitingToBeTransfered...
 

 

[astroman133]

From looking at the log file I see that you are set up to save the RAW and JPG images to the camera's memory card. Is the card full? Why save JPG images at all, especially for dark frames?

[admin]

Are you sure sent the correct log file.  This log file is nice, you even manually disconnected the camera.

[TheRealEleven]

53 minutes ago, astroman133 said:

From looking at the log file I see that you are set up to save the RAW and JPG images to the camera's memory card. Is the card full? Why save JPG images at all, especially for dark frames?

I like being able to do a quick look at the data, it's just easier for me to do that in jpg. Can't just turn jpgs off for darks, so I leave the settings like that. I continued and did Flats and Bias on the card after this,  and I just checked, I'm only at 5gb out of the 32gb.

31 minutes ago, admin said:

Are you sure sent the correct log file.  This log file is nice, you even manually disconnected the camera.

Yea that's the right one. Here is where I can see that a 300 second sub was only 178ish:

 2018-03-22 06:35:16,453 [CameraTakePictureOnMessageRecieved] INFO  - Timespan 178.257

But I can't figure out what happened there. 

[TheRealEleven]

22 minutes ago, astroman133 said:

I do not remember any other BYE users reporting this type of issue before. I understand that you would rather not have issues like this, but I would suggest trying it again to see if it was a one-time glitch or is evidence of a repeatable problem.

Also, I can see where the 300 second image was terminated early, but according to the log, you clicked the Abort button to end the capture plan. Here are the relevant lines from the log.

2018-03-22 06:32:18,321 [CameraTakePictureOnMessageRecieved] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(Not supported) Duration(300.0) Iso(800) Quality(IMAGE_RLF+) Mirror(0) SaveTo(CARD)
2018-03-22 06:32:19,587 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(CameraRef, 2, 0)
2018-03-22 06:32:19,727 [CameraTakePictureOnMessageRecieved] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 2, 0)
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - StateEvent_JobStatusChanged Fired! (inParameter=1) (inContext=0)
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - Items waiting to be transfered...
2018-03-22 06:32:19,868 [OnStateEventHandler] DEBUG - StateEvent_BulbExposureTime Fired! (inParameter=0)
2018-03-22 06:32:34,575 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:33:35,409 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:34:36,260 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-22 06:35:16,312 [Main] DEBUG - ButtonPlus_MouseClick(btnAbort = 'Abort')
2018-03-22 06:35:16,344 [CameraTakePictureOnMessageRecieved] INFO  - Running (throw): EDSDK.EdsSendCommand(CameraRef, 3, 0)
2018-03-22 06:35:16,359 [CameraTakePictureOnMessageRecieved] INFO  - Success: EDSDK.EdsSendCommand(CameraRef, 3, 0)
2018-03-22 06:35:16,359 [CameraTakePictureOnMessageRecieved] DEBUG - Abort seconds = 176
2018-03-22 06:35:16,453 [CameraTakePictureOnMessageRecieved] INFO  - Timespan 178.257
2018-03-22 06:35:16,469 [CameraTakePictureOnMessageRecieved] DEBUG - Camera BUSY flushing ObjectsWaitingToBeTransfered...
 

 

It's never happened before, and actually it's not a huge deal this time, I still had 7 darks to work with and everything seemed to stack nicely so no biggie. I was just wondering exactly what happened. 

 

So get this...now that I see it's an abort, I wonder if a touch on the touch screen in the abort circle could trigger that? Does a touchscreen register as a mouse click? I'm in Florida and even though it's chilly now, nights still get damp, so I've been putting a light jacket over the laptop when I leave it out unattended. I wonder if I actually aborted the session when removing the jacket? That actually makes sense now that I put it all together. 

 

Thanks for helping investigate!

[admin]

That is exactly what happened.  This ButtonPlus_MouseClick(btnAbort = 'Abort') log message requires a physical/manual user intervention to be logged.  The abort button was pressed, that I'm 1000% sure about this given the log file provided.  Thank you Rick for pointing it out.

Regards,