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:
    5,351
    Location:
    Earth
    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:
    25
    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:
    5,351
    Location:
    Earth
    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 Lead Developer Staff Member

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

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Hi guys,
    I am having the same problem in PHD2 and I have upgraded to the latest firmware and driver versions. See below.

    This error happens even indoors at 20 degC. The SC-2 would work for a while and then throw this error.

    Also, I have a suspicion that the problem may also be traced to serial commands being issued to other devices, like the mount when I park and unpark. Unfortunately, this doesn't happen all the time and could be a red herring.


    cytan

    track.png

    config.jpg
     
    Last edited: Oct 31, 2020
  7. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
  8. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Hi Colin,
    Yes I have. I decided to do an uninstall/reinstall again, just to be sure:

    ascom.jpg

    I have also tried isolating the problem. I unplugged and unpowered all the USB devices except the SC-2. In PHD2 it ran for a few minutes and then gave the Catastrophic failure :(
    And this is done indoors, so it's not an ambient temperature problem.

    cytan
     
  9. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    OK, I did another test. I have a backup computer and it is running an earlier version of the driver:

    config.jpg

    And with this version of the driver, I don't see the catastrophic error.

    I think if I can downgrade my driver on the non-backup computer, I should be able to confirm that it is a driver problem. Where can I download the 1.7.1.0 driver?

    cytan
     
  10. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Hi Colin,
    Any updates? FYI, I imaged with my backup computer with the 1.7.1.0 driver last night and there were no catastrophic errors from SC-2.

    cytan
     
  11. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
    My colleague @Adam Robichaud has been assigned to investigate these errors. We have to wait for his investigation.
     
  12. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Hi Colin,
    In the meantime can you send me the link to 1.7.1.0? I can give you and Adam another data point if the problem disappears with this driver.

    cytan
     
  13. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
    Gentlemen, can you confirm the following:

    In MaxIm, check that you have the Camera 1 and Camera 2 (if used) [OPTIONS] button settings for enabling threading turned on:
    [​IMG]

    Windows Power Management sometimes can cause USB communication failures.
    There are a couple of things to check.

    Windows Power Management - USB Selective Suspend - this should be OFF (disabled) to prevent Windows from powering down USB hardware.
    [​IMG]

    For all devices, COM ports (USB/RS232 adapters), USB hubs, USB root hubs, PCIe devices, turn off [] Allow the computer to turn off the device to save power:
    [​IMG]

    You might want to save your Windows Power Plan with a new name after making these changes, sometimes that helps.
    We've learned that Windows Updates, Windows Feature Updates etc sometimes REVERT these settings, and that can cause trouble to show up later after a Windows update.

    CYTan - I will look into finding 1.7.1.0, however I'd prefer you check the settings above to make sure that Windows Power Management isn't causing the problem.
     
  14. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Hi Colin,
    I checked the devices that you suggested and the only device that I found that had "turn off[]" marked is my usb3 hub. I unchecked it.

    After I (un)checked all the devices, I ran the SC-2 in PHD2 and after about 10 minutes, the catastrophic failure popped up again :(

    cytan
     
    Last edited: Nov 9, 2020
  15. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
    Ok, thanks for letting us know.
     
  16. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
    It just occurred to me - Did you power cycle everything before the test?
    e.g. shut down the camera, hubs, PC, power it all off and then back on again?
     
  17. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Since these tests are done indoors, only the cameras were power cycled. I did not power cycle the laptop but I can try again tonight with the laptop power cycled before redoing the tests.
     
  18. cytan299

    cytan299 Standard User

    Joined:
    Jun 6, 2020
    Messages:
    15
    Rebooted and restarted laptop. Catastrophic failure after about 10 minutes.
     
  19. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    5,351
    Location:
    Earth
  20. Adam Robichaud

    Adam Robichaud Lead Developer Staff Member

    Joined:
    Sep 29, 2014
    Messages:
    899
    Location:
    Ottawa
    It looks like this is happening because of an error waiting for the camera to update its status, but I haven't reproduced the issue yet. We don't have DLAPI logging active for the ASCOM driver, which we should probably remedy, so this may take a while to fully rectify.
     

Share This Page