SGP 3.1.0.322 error writing captured images

Hi,

I have been running this version for some time now, but tonight I ran into a serious issue.
SGP was not able to write the captured images to disk anymore (and there is plenty of space on that disk). After a restart of SGP, it failed to start altogether, with the “incompatible sequence with this version” message. I had to delete the sequence file as it obviously got corrupt.

This happened after he had successfully saved 40 frames, but then it went wrong. File after file were not saved (note: I have sequence recovery and restart on safe conditions on).

Any ideas? Since it is clouded now, I can not test if a restart solved the issue, but for sure it is a nasty problem with an automated observatory, as I am not there to watch when it goes wrong.

This is the repeating error message in the log file (repeated for every file SGP failed to write).

[01/20/20 22:57:50.642][DEBUG] [Sequence Thread] Saving the CCD temp…
[01/20/20 22:57:50.642][DEBUG] [Sequence Thread] Entering super dangerous loop to await image completion…
[01/20/20 22:57:50.643][DEBUG] [Sequence Thread] EventMarker 16 - t:Boogieman2 (0); e:0; f:0; o:
[01/20/20 22:57:51.794][DEBUG] [Camera Thread] ASCOM Camera Error : CheckDotNetExceptions ASCOM.ASICamera2_2.Camera ImageArray Get System.OutOfMemoryException: Insufficient memory to continue the execution of the program. (See Inner Exception for details) (System.OutOfMemoryException: Insufficient memory to continue the execution of the program.)
at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
at ASCOM.DriverAccess.MemberFactory.GetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 664
at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 288
at ASCOM.DriverAccess.Camera.get_ImageArray() in C:\ASCOM Build\Export\ASCOM.DriverAccess\Camera.cs:line 359
at r1.hv(qb A_0, sb& A_1)
[01/20/20 22:57:51.794][DEBUG] [Camera Thread] Error while attempting to capture frame…
[01/20/20 22:57:51.795][DEBUG] [Main Thread] Adding sequence level notification: Error attempting to capture image (see logs for more information).
[01/20/20 22:57:51.833][DEBUG] [Camera Thread] Sending Notification: Error - Error attempting to capture image (see logs for more information).
[01/20/20 22:57:51.833][DEBUG] [Camera Thread] SGM_CAMERA_CAPTURE complete…
[01/20/20 22:57:52.156][DEBUG] [Sequence Thread] EventMarker 17 - t:Boogieman2 (0); e:0; f:0; o:
[01/20/20 22:57:52.156][DEBUG] [Sequence Thread] Image reported as complete. Continuing…
[01/20/20 22:57:52.159][DEBUG] [Sequence Thread] Collecting FITs headers…
[01/20/20 22:57:52.159][DEBUG] [Sequence Thread] ASCOM Camera: Could not get last exposure start time. Reported as (unknown)
[01/20/20 22:57:52.159][DEBUG] [Sequence Thread] DATE-LOC time provided by SGPro (failed to retrieve valid entry from camera)…
[01/20/20 22:57:52.167][DEBUG] [Sequence Thread] GatherFitsHeaders: Writing header info for last solve…
[01/20/20 22:57:52.167][DEBUG] [Sequence Thread] GatherFitsHeaders: Writing header info from UI…
[01/20/20 22:57:52.167][DEBUG] [Sequence Thread] Clearing timed monitoring events…
[01/20/20 22:57:52.191][DEBUG] [Sequence Thread] Error saving ASCOM image. : Object reference not set to an instance of an object.
at r1.f8(qi A_0, List`1 A_1)
[01/20/20 22:57:52.191][DEBUG] [Sequence Thread] Failed to save image to disk!

These errors are typically indicative of:

  • A disk with very little space left on it
  • For older spinning disks, a highly fragmented disk
  • A failing hard drive
  • Using older, unstable, ASI ASCOM or native drivers

Hmm, drivers were update a few months ago, and it always worked stable. The disk gave no errors on it, and there is lots of space free (2TB something).
Any other ideas?
Thanks.

D.

Other than to recommend that the camera always be connected directly to the computer (no USB hub), I don’t have any. The error is issued by ZWO. They might have some ideas.

Thanks Ken. I will see with ZWO what they think if it happens again.

D.