Sharpcaphalted due error and will now close

Questions, tips, information and discussions about using the SharpCap Sequencer and Sequence Planner tools
Post Reply
SternwarteOrion
Posts: 17
Joined: Wed Aug 28, 2024 8:17 am

Sharpcaphalted due error and will now close

#1

Post by SternwarteOrion »

Hi,
I have some trouble using SharpCap. Until about 3 am, everything went increadibly well. But since 3 am, my Camera didn't capture any photos anymore. And at 0:54 am, this appeared on my screen:
A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (Der angegebene Host ist unbekannt. (msdl.microsoft.com:443))
This also happened yesterday at the exact same time (0:54 am and the camera did stop at 3 am). What am I doing wrong?`Here's my Sequence:
SEQUENCE
#Coordinates: 5 34 33.12 +22 00 53.7 - Camera rotation = 0°
SAVE COORDINATES "5 34 33.12 +22 00 53.7"
LIVE STACKING START
LOOP UNTIL LOCALTIME 01:20:00
MOUNT TRACKING Sidereal
DELAY 900
LIVE STACKING STOP
GOTO SAVED COORDINATES
DELAY 30
RETRY ERRORS UP TO 1000 TIMES
MOUNT TRACKING Sidereal
MOUNT SOLVESYNCONLY
END RETRY ERRORS
LIVE STACKING START
END LOOP
LIVE STACKING STOP
#New Target: NGC 3344
SAVE COORDINATES "10 43 31.77 +24 55 11.3"
GOTO SAVED COORDINATES
DELAY 30
SET EXPOSURE TO 30
RETRY ERRORS UP TO 1000 TIMES
MOUNT TRACKING Sidereal
MOUNT SOLVESYNCONLY
END RETRY ERRORS
SET EXPOSURE TO 15
LIVE STACKING START
LOOP UNTIL LOCALTIME 03:18:00
MOUNT TRACKING Sidereal
DELAY 900
LIVE STACKING STOP
GOTO SAVED COORDINATES
DELAY 30
SET EXPOSURE TO 30
RETRY ERRORS UP TO 1000 TIMES
MOUNT TRACKING Sidereal
MOUNT SOLVESYNCONLY
END RETRY ERRORS
SET EXPOSURE TO 15
LIVE STACKING START
END LOOP
LIVE STACKING STOP
GOTO SAVED COORDINATES
DELAY 30
SET EXPOSURE TO 30
RETRY ERRORS UP TO 1000 TIMES
MOUNT TRACKING Sidereal
MOUNT SOLVESYNCONLY
END RETRY ERRORS
SET EXPOSURE TO 15
LIVE STACKING START
LOOP UNTIL LOCALTIME 07:00:00
MOUNT TRACKING Sidereal
DELAY 900
LIVE STACKING STOP
GOTO SAVED COORDINATES
DELAY 30
SET EXPOSURE TO 30
RETRY ERRORS UP TO 1000 TIMES
MOUNT TRACKING Sidereal
MOUNT SOLVESYNCONLY
END RETRY ERRORS
SET EXPOSURE TO 15
LIVE STACKING START
END LOOP
MOUNT PARK
CAMERA CLOSE
END SEQUENCE
And if you need the log data, I can't send it because it's too large.

Cheers!
User avatar
admin
Site Admin
Posts: 17552
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sharpcaphalted due error and will now close

#2

Post by admin »

Hi,

I really will need the log to identify where in the code that problem came from - please either zip up the log file to make it smaller and post it here, or send it to me via email (use the 'contact us' link at the bottom of the page).

cheers,

Robin
SternwarteOrion
Posts: 17
Joined: Wed Aug 28, 2024 8:17 am

Re: Sharpcaphalted due error and will now close

#3

Post by SternwarteOrion »

Here it is :D
Attachments
Log_2026-01-19T18_11_30-16792.zip
The log data.
(365.82 KiB) Downloaded 390 times
SternwarteOrion
Posts: 17
Joined: Wed Aug 28, 2024 8:17 am

Re: Sharpcaphalted due error and will now close

#4

Post by SternwarteOrion »

Sorry, the message didn't appear at 0:54 am, but around 1:50 am.
User avatar
admin
Site Admin
Posts: 17552
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Sharpcaphalted due error and will now close

#5

Post by admin »

Hi,

thanks for sharing the log - I think the underlying cause is a bug in one of the components that I use to help with diagnosing issues with the software (ironically...).

The initial problem is that SharpCap becomes unresponsive while saving the live stack at about 01:53:40 or so. At that point the diagnostics kick in to try to record what the application is doing at that point into the log. That information lets me work out why the application became unresponsive and do something about it. In this case however, the diagnostic library tried to access a microsoft download server to access a file that helps with the diagnostics, and that failed probably because you were offline. Now, a) it shouldn't try if you are offline and b) it should cope with that failure anyway, but that is 'should', not 'did'.

I can see a few things that I can do to help here

1) try to repro the problem myself with the network cable pulled out to see if I can get it to break in the same way and find out more about why it happens when it shouldn't

2) See if there is an update for the library I use for diagnostics that maybe fixes this issue

3) Try to stop that particular error if it happens from bringing SharpCap down (maybe I can spot it and ignore it?)

4) See what I can do about the thing that made SharpCap unresponsive - oddly in spite of the failed download attempts it produced the required information and I can see that the thing taking a long time was saving the previous stack...

I will see what I can do about this for the next update.

cheers,

Robin
Post Reply