Staff Assigned: Adam Robichaud (ASCOM.DLImaging.Camera) Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))

Discussion in 'Guiding and Adaptive Optics - StarChaser and AO' started by PeteFleurant, Oct 18, 2020.

Tags:
  1. PeteFleurant

    PeteFleurant Standard User

    Joined:
    Oct 1, 2018
    Messages:
    18
    Location:
    Massachusetts
    Hi,

    I have just started using the SC-2 with STF-8300 and FW8-8300. All in all it has been performing very well and am very happy with it.

    Recently after hours of operation the following exception was thrown and caused PHD2 to stop guiding.

    I'm not asking for you to debug PHD logs, but I was wondering if you had any idea about the HRESULT statement ? (This only occurred once in a 4+ hour session.)

    My exposures were 4 sec.

    Below is the log beginning with the successful exposure followed by the one that failed.

    Thanks!


    01:26:36.755 00.004 15404 Worker thread wakes up
    01:26:36.755 00.000 15404 worker thread servicing REQUEST_EXPOSE 2500
    01:26:36.755 00.000 15404 Handling exposure in thread, d=2500 o=3 r=(335,35,31,31)
    01:26:39.456 02.701 15404 Exposure complete
    01:26:39.482 00.026 15404 worker thread done servicing request
    01:26:39.482 00.000 8448 OnExposeComplete: enter
    01:26:39.487 00.005 8448 UpdateGuideState(): m_state=6
    01:26:39.492 00.005 8448 Star::Find(15, 350, 49, 0, (0,0,0,0), 1.5, 0) frame 2015
    01:26:39.497 00.005 8448 Star::Find returns 1 (0), X=350.30, Y=49.54, Mass=773, SNR=19.4, Peak=71 HFD=4.7
    01:26:39.502 00.005 8448 CameraToMount -- cameraTheta (-3.11) - m_xAngle (-1.68) = xAngle (-1.43 = -1.43)
    01:26:39.506 00.004 8448 CameraToMount -- cameraTheta (-3.11) - (m_xAngle (-1.68) + m_yAngleError (-3.00)) = yAngle (1.57 = 1.57)
    01:26:39.510 00.004 8448 CameraToMount -- cameraX=-0.03 cameraY=-0.00 hyp=0.03 cameraTheta=-3.11 mountX=0.00 mountY=0.03, mountTheta=1.43
    01:26:39.514 00.004 8448 SchedulePrimaryMove(07CEDE70, x=-0.03, y=-0.00, opts=13)
    01:26:39.517 00.003 8448 Enqueuing Move request for scope (-0.03, -0.00)
    01:26:39.521 00.004 15404 Worker thread wakes up
    01:26:39.521 00.000 15404 worker thread servicing REQUEST_MOVE scope ofs (-0.03, -0.00) opts 0xd
    01:26:39.521 00.000 15404 Handling offset move in thread for scope, endpoint = (-0.03, -0.00)
    01:26:39.521 00.000 15404 Moving (-0.03, -0.00) raw xDistance=0.00 yDistance=0.03
    01:26:39.521 00.000 15404 GuideAlgorithmHysteresis::Result() returns 0.00 from input 0.00
    01:26:39.521 00.000 15404 Throw from C:\cygwin\home\agalasso\projects\phd2\guide_algorithm_resistswitch.cpp:107->input < m_minMove
    01:26:39.521 00.000 15404 GuideAlgorithmResistSwitch::result() returns 0.00 from input 0.03
    01:26:39.521 00.000 15404 MoveAxis(E, 0, ABG)
    01:26:39.521 00.000 15404 Move returns status 0, amount 0
    01:26:39.521 00.000 15404 MoveAxis(N, 0, ABG)
    01:26:39.521 00.000 15404 Move returns status 0, amount 0
    01:26:39.521 00.000 15404 move complete, result=0
    01:26:39.521 00.000 15404 worker thread done servicing request
    01:26:39.528 00.007 8448 UpdateImageDisplay: Size=(640,512) min=29, max=71, FiltMin=29, FiltMax=58, Gamma=1.870
    01:26:39.588 00.060 8448 UpdateGuideState exits: m=773 SNR=19.4
    01:26:39.593 00.005 8448 OnExposeComplete: CaptureActive=1 m_continueCapturing=1
    01:26:39.598 00.005 8448 ScheduleExposure(2500,3,1) exposurePending=0
    01:26:39.603 00.005 8448 Enqueuing Expose request
    01:26:39.607 00.004 8448 GuideStep: 0.0 px 0 ms EAST, 0.0 px 0 ms NORTH
    01:26:39.612 00.005 15404 Worker thread wakes up
    01:26:39.612 00.000 15404 worker thread servicing REQUEST_EXPOSE 2500
    01:26:39.612 00.000 15404 Handling exposure in thread, d=2500 o=3 r=(335,35,31,31)
    01:26:42.196 02.584 15404 invoke imageready: [80020009] Exception occurred.
    01:26:42.196 00.000 15404 invoke imageready:
    (ASCOM.DLImaging.Camera) Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
    01:26:42.196 00.000 15404 ASCOM_ImageReady failed:
    (ASCOM.DLImaging.Camera) Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
    01:26:42.196 00.000 15404 Error thrown from C:\cygwin\home\agalasso\projects\phd2\worker_thread.cpp:157->Capture failed
    01:26:42.196 00.000 8448 Alert: Exception thrown polling camera:
    (ASCOM.DLImaging.Camera) Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
    01:26:42.202 00.006 15404 worker thread done servicing request
    01:26:42.407 00.205 8448 OnExposeComplete: enter
    01:26:42.413 00.006 8448 OnExposeComplete: Capture Error reported
    01:26:42.417 00.004 8448 StopCapturing CaptureActive=1 continueCapturing=1 exposurePending=0
    01:26:42.422 00.005 8448 Status Line: Waiting for devices...
    01:26:42.429 00.007 8448 Mount: notify guiding stopped
    01:26:42.433 00.004 8448 BLC: window closed
    01:26:42.438 00.005 8448 BLC: Last direction was reset
    01:26:42.446 00.008 8448 Changing from state GUIDING to STOP
     
  2. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,886
    Hi Pierre,
    One of our developers will have to look at this when we are back at work starting tomorrow.
     
  3. Anthony King

    Anthony King Cyanogen Customer

    Joined:
    May 10, 2016
    Messages:
    5
    I also attempted to connect the SC-2 to PHD guiding and failed drawing the HRESULT error. Using DL Imaging.
     
  4. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    3,886
    Please try the newly updated DL Imaging drivers, and newly updated ASCOM drivers.

    We released this software on 2020-10-22.
    You can get it from the StarChaser page, under the Downloads section.
    https://diffractionlimited.com/product/sbig-starchaser/
    Also, please note that there have been some firmware updates for the StarChaser cameras. You may wish to check that as well, by reviewing the firmware page linked from the Downloads section.

    Direct link to DL Imaging:
    https://diffractionlimited.com/down/SetupDLAPI.exe
    Direct link to ASCOM drivers:
    https://diffractionlimited.com/down/DLImagingASCOMDriverInstaller.exe
    Direct link to firmware - make sure to specify your device in the dropdown on this page:
    https://diffractionlimited.com/aluma-fpga-firmware/

    Also, MaxIm was updated to 6.24.
    Help... Check for Updates in MaxIm.
     
  5. Adam Robichaud

    Adam Robichaud Staff Member

    Joined:
    Sep 29, 2014
    Messages:
    798
    Location:
    Ottawa
    Do you happen to know what the ambient temperature was at the time of the failure?
     

Share This Page