STF-8300 freezing or even crashing Maxim

Discussion in 'STF Series CCD Cameras' started by lukepower, Nov 8, 2020.

Page 1 of 2
  1. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Hello,
    I am struggling to narrow down one issue that I have with an STF-8300. I have the latest drivers and also the latest firmware, and am using MaximDl 6.21 on Windows 10.

    Basically, I can connect to the camera and use it normally. The issues are sporadic and show in two different variations:
    • Mostly, the camera stops updating it's status in maxim. So during an exposure, the timer just stays stuck at the seconds it was showing (even for hours), or I am unable to start or stop an exposure. Disconnecting will then crash MaximDl
    • Sometimes, MaximDl simply crashes.
    I can imagine that this is an USB issue and will try to swap cables and USB host ports once more (already tried this). I wonder if ther is anything I could do to get some more debug information? The USB Settings have all power saving options disabled. I wonder if this could be an issue with the computer itself? I don't know...

    Thanks
    Lukas
     
    lukepower, Nov 8, 2020
    #1
  2. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    This sounds like a hardware / system problem. MaxIm shouldn't just "crash".

    Try a different USB 2.0 cable, less than 15 feet (preferrably shorter) direct between the camera and the USB ports on the rear of the PC.
    No hubs, extenders etc.
    Do you have any hubs or extenders in your setup?

    Although you mention USB settings have been taken care of, double check:
    selectivesuspend.png
    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:
    usbnoturnoff.png

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

    MaxIm DL Pro is now at version 6.24. Help... Check for Updates.

    As far as "crashes" go, check the Windows Event Viewer, Application Log, and look for Application Error with serious errors - a Red circle and (!).
    Like this, pointed to in GREEN:
    event_applicationerr.png
    The text in the box that says Faulting Application Name and Faulting Application Module is of interest, and may give a hint.
    You can copy/paste that text and reply with it here.

    Other suggestions:
    You may wish to test your system's RAM with Windows Memory Diagnostic or a version of Memtest86 or Memtest86+.

    You should also run Windows Update to make sure the machine is current. You might have to do this a couple of times.
    It's possible that you have some underlying O/S problems. You might want to google DISM and SFC /scannow for info on checking and repairing your Windows OS.
     
    Colin Haig, Nov 8, 2020
    #2
  3. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Hi Colin,

    thank you for your exhausive answer. What I did in the meantime was to ativate the debug log in SBIGDriverChecker, and got this (before it froze):
    Code:
    At t = 6628.766: data                    : 06, 00
At t = 6629.389: CC_END_READOUT          : end, err = 00 - No Error
At t = 6629.953: =========================
At t = 6630.603: CC_END_EXPOSURE         : begin
At t = 6631.237: EndExposure -> start...
At t = 6631.861: MicroCommand            : MC_END_EXPOSURE, ccd=0, flags=0x0: ABORT_DONT_END=0
At t = 6632.490: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6633.054: data                    : 06, 00
At t = 6633.689: EndExposure -> MicroCommand -> MC_END_EXPOSURE -> res : 0
At t = 6634.318: MicroCommand            : MC_MISC_CONTROL
At t = 6634.954: MC_MISC_CONTROL   Flags : 0x14: ExtShutter=Leave, Fan=Enabled, LED=On, Shutter=Leave
At t = 6635.583: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6636.139: data                    : 06, 00
At t = 6636.804: EndExposure -> end, res : 0
At t = 6637.433: CC_END_EXPOSURE         : end, ccd=0, err = 00 - No Error
At t = 6638.072: =========================
At t = 6638.711: CC_SET_IRQL             : begin
At t = 6639.263: CC_SET_IRQL             : end, err = 00 - No Error
At t = 6639.902: =========================
At t = 6640.537: CC_SET_IRQL             : begin
At t = 6641.164: CC_SET_IRQL             : end, err = 00 - No Error
At t = 6641.798: =========================
At t = 6642.353: CC_END_READOUT          : begin ----> GRAB END
At t = 6642.987: MicroCommand            : MC_READOUT -> RS subcommand: RS_END_READOUT
At t = 6643.618: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6644.254: data                    : 06, 00
At t = 6644.885: CC_END_READOUT          : end, err = 00 - No Error
At t = 6645.441: =========================
At t = 6646.044: CC_END_EXPOSURE         : begin
At t = 6646.678: EndExposure -> start...
At t = 6647.317: MicroCommand            : MC_END_EXPOSURE, ccd=0, flags=0x0: ABORT_DONT_END=0
At t = 6647.974: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6648.546: data                    : 06, 00
At t = 6649.176: EndExposure -> MicroCommand -> MC_END_EXPOSURE -> res : 0
At t = 6649.817: MicroCommand            : MC_MISC_CONTROL
At t = 6650.451: MC_MISC_CONTROL   Flags : 0x14: ExtShutter=Leave, Fan=Enabled, LED=On, Shutter=Leave
At t = 6651.108: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6651.690: data                    : 06, 00
At t = 6652.378: EndExposure -> end, res : 0
At t = 6653.037: CC_END_EXPOSURE         : end, ccd=0, err = 00 - No Error
At t = 6653.688: =========================
At t = 6654.252: CC_SET_IRQL             : begin
At t = 6654.887: CC_SET_IRQL             : end, err = 00 - No Error
At t = 6655.523: =========================
At t = 6656.147: CC_SET_IRQL             : begin
At t = 6656.803: CC_SET_IRQL             : end, err = 00 - No Error
At t = 6657.364: =========================
At t = 6657.985: CC_END_READOUT          : begin ----> GRAB END
At t = 6658.616: MicroCommand            : MC_READOUT -> RS subcommand: RS_END_READOUT
At t = 6659.247: ReadComPipe             : Ask/Got = 2/2  -> ACK
At t = 6659.894: data                    : 06, 00
At t = 6660.452: CC_END_READOUT          : end, err = 00 - No Error
    In Maxim it looks like this:

    upload_2020-11-8_15-5-1.png
    upload_2020-11-8_15-7-49.png

    (since 2 hours now).

    And indeed there are some erros in the Event Log:
    Code:
    Faulting application name: MaxIm_DL.exe, version: 6.7.0.0, time stamp: 0x54482fd5
Faulting module name: CCDPlugSBIG.dll, version: 6.7.0.0, time stamp: 0x5448187c
Exception code: 0xc000041d
Fault offset: 0x00004fdb
Faulting process id: 0x1c3c
Faulting application start time: 0x01d6b539d5407aaf
Faulting application path: C:\Program Files (x86)\Diffraction Limited\MaxIm DL V6\MaxIm_DL.exe
Faulting module path: C:\Program Files (x86)\Diffraction Limited\MaxIm DL V6\CCDPlugSBIG.dll
Report Id: 05fa964e-ff6a-4610-8ae3-38fd616f9795
Faulting package full name:
Faulting package-relative application ID:
    Code:
    Faulting application name: MaxIm_DL.exe, version: 6.7.0.0, time stamp: 0x54482fd5
Faulting module name: KERNELBASE.dll, version: 10.0.18362.1139, time stamp: 0x6a8e6b97
Exception code: 0xc000041d
Fault offset: 0x00114662
Faulting process id: 0x560
Faulting application start time: 0x01d6b532bdf33f17
Faulting application path: C:\Program Files (x86)\Diffraction Limited\MaxIm DL V6\MaxIm_DL.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: f07eccf4-270f-4bfa-a757-76f394849b68
Faulting package full name:
Faulting package-relative application ID:
    Code:
    Faulting application name: MaxIm_DL.exe, version: 6.7.0.0, time stamp: 0x54482fd5
Faulting module name: CCDPlugSBIG.dll, version: 6.7.0.0, time stamp: 0x5448187c
Exception code: 0xc0000005
Fault offset: 0x00004fdb
Faulting process id: 0x221c
Faulting application start time: 0x01d6b530f479cfeb
Faulting application path: C:\Program Files (x86)\Diffraction Limited\MaxIm DL V6\MaxIm_DL.exe
Faulting module path: C:\Program Files (x86)\Diffraction Limited\MaxIm DL V6\CCDPlugSBIG.dll
Report Id: 20af5b7e-9d53-49ea-a8cb-059fc236a449
Faulting package full name: 
Faulting package-relative application ID:
    I will try to check more by switching cables and even computer. If you want or need, the system is remote so you could connect there and test some more :)
     
    lukepower, Nov 8, 2020
    #3
  4. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    Nothing in the SBIG driver log looks obviously abnormal.

    What exact version of Windows are you running and what are the specs on the PC?

    The exception 0xc000041d in Kernelbase.dll (which is part of the OS) is not part of MaxIm, that's an unhandled exception in an operating system component.

    I really suspect something is corrupt in your Windows environment.

    The exception 0xc0000005 in CCDPlugSBIG.dll is an unhandled exception - something went wrong and our SBIG plugin didn't know what to do with it. I've never seen this before - the SBIG driver code is very stable, has been for a very very long time. Something low level in the OS probably went bad.
     
    Colin Haig, Nov 8, 2020
    #4
  5. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    If you have a second computer, try it on that machine.
     
    Colin Haig, Nov 8, 2020
    #5
  6. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Okay, one night went without issues. What I've done:
    - run a sfc /scannow scan, returned no big issues
    - updated to MaximDL 6.21 (for some reason, I still was running on 6.08)

    I feel that the updated MaximDL version fixed it, but I am going to test it further to be sure :)
     
    lukepower, Nov 9, 2020
    #6
  7. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    If SFC /scannow found and fixed *anything* then there was definitely a problem with your operating system.

    Updating MaxIm is often a good idea too.
     
    Colin Haig, Nov 9, 2020
    #7
  8. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Okay I can confirm that the camera works now as expected.
    The only quirk I can see is that at some point during the night the cooler reads an obviously wrong temperature:
    upload_2020-11-18_11-0-13.png
    Power cycling seems to help, or waiting... :) But I don't know, maybe the probe has an issue?
     
    lukepower, Nov 18, 2020
    #8
  9. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    Ok, agreed that -116.6 is not right.
    Can you upload a FITS image taken around the time of this error?
    It might help us track this down.
    There have been some bug fixes and changes made in MaxIm sicne 6.21. You might want to do a Help... Check for Updates to get current. 6.24 is the latest, and we're working on 6.25.
     
    Colin Haig, Nov 18, 2020
    #9
  10. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    I've changed the status on this thread from Resolved back to normal, so we don't miss this.
    It's ironic that the thread title is STF Freezing and you're getting -116C for a temperature.
    Ethanol freezes around -114... makes for a fine beverage...
     
    Colin Haig, Nov 18, 2020
    #10
  11. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Hi Colin,

    alright, so first of all some affected frames: https://drive.google.com/drive/folders/1EZdAaKZCQNiZFDYmLtDziMSAxoyFCVRL?usp=sharing

    upload_2020-11-18_14-27-46.png

    As for the MaximDl version, let me first renew the license as I can currently only get to 6.21; then I'll update it and see if that helps. It has to be said that the temperature control functions mostly correctly, just sometimes it goes nuts thinking it is a truly cold beverage :)
     
    lukepower, Nov 18, 2020
    #11
  12. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    That turned out to be 0.5GB zipped... and all the ones I checked look fine other than the bizarre temps.
    Let me see if colleagues have any idea.
     
    Colin Haig, Nov 18, 2020
    #12
  13. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    The images are perfect so far, only the temperature is an issue, as it is basically unknown...

    btw, I updated to MaximDl 6.24 and will test tonight... Let's see if this helps in some way.
     
    lukepower, Nov 18, 2020
    #13
  14. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    Ok, let us know what you experience.
     
    Colin Haig, Nov 18, 2020
    #14
  15. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    Lukas,
    I just connected with our development manager, and he's requested that we work on getting a Crash Dump - so next time MaxIm just quits un-gracefully, there will be a .DMP file that can be Zipped up and sent in to development, and they will see exactly what happened.

    To set up Crash Dumps on your machine:
    https://forum.diffractionlimited.com/threads/how-to-enable-crash-dumps-for-maxim.7464/

    If you've got any questions, let me know.
    We could also do a TeamViewer session if your computer is internet accessible so I could either see it happen or get the crash dumps setup and download them after they occur.
    Best regards
    Colin
     
    Colin Haig, Nov 18, 2020
    #15
  16. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Hi Colin,

    so last night the temperature was normal without any sudden spikes; the whole night was a breeze to be frank. Let's watch it for a few more nights, but maybe it truly was a software issue which had been fixed with one of the latest MaximDl versions?
    I will enable the dump feature nonetheless, who knows if not something else pops up :)

    And yes, the computer would be accessible via Teamviewer as it is in a remote observatory in Spain.
     
    lukepower, Nov 19, 2020
    #16
  17. Doug

    Doug Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    9,967
    That is not a software fault. No software fault is going to randomly change the reported cooler temperature. Also we have not worked on MaxIm DL's cooler control software in many years.

    Possibilities are:
    • Intermittent camera fault
    • Bad power to the camera
    • Possibly USB communications problem. Was the outdoor temperature below freezing when you were having the problem? Desktop USB hubs don't work properly in cold temperatures, and often cause all kinds of problems. (That sort of thing always pops up this time of year!)
     
    Doug, Nov 19, 2020
    #17
  18. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    So today I let the technicians on site check the camera, and they found the fan dangling:
    upload_2020-11-19_19-54-0.png
    It looks like the screws lost grip. Any advice on how to fix it?
     
    lukepower, Nov 19, 2020
    #18
  19. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    7,429
    Location:
    Earth
    That's not good! That's the first time I've seen that problem. Looks a little dusty too.
    Can you provide the serial number of the camera?
    Then I can ask our repair colleagues for some advice/instructions.
    BTW is it in Namibia? (Trying to figure out where in case parts are needed).
     
    Colin Haig, Nov 19, 2020
    #19
  20. lukepower

    lukepower Cyanogen Customer

    Joined:
    Jul 8, 2016
    Messages:
    46
    Colin, I will let you know the s/n tomorrow. It is located in spain, so if we can arrange for a local repair it might be pretty easy (opposed to what would happen in Namibia) :)
     
    lukepower, Nov 19, 2020
    #20
Page 1 of 2

Share This Page