All-Sky Software Issue

Discussion in 'Specialty Cameras (ST-I, SG-4, AllSky)' started by Richard Bell, Feb 10, 2020.

  1. Richard Bell

    Richard Bell Cyanogen Customer

    Joined:
    May 2, 2019
    Messages:
    5
    We've developed an issue with our SBIG AllSky-340C Camera this past Sunday. I think it's a software issue. The program stopped recording images and it's been difficult to get it started up again. I've restarted the computer twice and it'll record images for a short time before encountering an error. COM port test is good. I've attached a snippet of the pop-up window. Clicking on "Details" shows the info pasted below.

    Would appreciate some advice and guidance on how to fix this problem.

    - Richard

    - - -

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.TimeoutException: The write timed out.
    at System.IO.Ports.SerialStream.Write(Byte[] array, Int32 offset, Int32 count, Int32 timeout)
    at System.IO.Ports.SerialPort.Write(String text)
    at SBIG_All_Sky_Camera.SerialCommunication.TransferImage(BackgroundWorker bw)
    at SBIG_All_Sky_Camera.formSettings.GetDarkImage(BackgroundWorker bw, BWParams myBWParams)
    at SBIG_All_Sky_Camera.formSettings.backgroundWorkerTakeImage_DoWork(Object sender, DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9148 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    ----------------------------------------
    SBIG All Sky Camera
    Assembly Version: 1.0.37.0
    Win32 Version: 1.0.37.0
    CodeBase: file:///C:/Program%20Files%20(x86)/SBIG/SBIG%20AllSky-340/SBIG%20All%20Sky%20Camera.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9147 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.9136 (WinRelRS6.050727-9100)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
     

    Attached Files:

  2. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    2,754
    Check that Windows Power Management - USB Selective Suspend is disabled.
    Check that the power management settings for the COM port/USB RS232 adapter, USB hubs, USB root hubs, and PCIe devices are set so that Windows doesn't turn off the device. There is usually a setting like [ ] Allow the computer to turn off the device to save power. Make sure this is disabled.
    Check also that you have the latest hardware drivers for yours serial port device. e.g. If it's made by FTDIchip, check that manufacturers web site.
    Windows updates/ugprades sometimes reset power management settings, and rollback or update hardware drivers.
    Windows sometimes puts USB devices / serial ports to sleep to save power, not realizing that the device was in active use. This results in a timeout.
     
  3. Richard Bell

    Richard Bell Cyanogen Customer

    Joined:
    May 2, 2019
    Messages:
    5
    Checked the Windows Power Management. The USN Selective Suspend is disabled. As far as I can tell, all other settings are that Windows doesn't turn anything off. Even made sure all drivers were up-to-date. The pop-up I posted before hasn't come back. What happens is the camera runs for a while (at one point for many hours) and then images don't download. The progress bar will stop or start over. Not sure what else to do.
     
  4. Colin Haig

    Colin Haig Staff Member

    Joined:
    Oct 27, 2014
    Messages:
    2,754
    What operating system are you running on?
    Have you tried connecting it to a different PC?
    Perhaps my colleague @Tim will have some ideas...
     
  5. Richard Bell

    Richard Bell Cyanogen Customer

    Joined:
    May 2, 2019
    Messages:
    5
    We are running Windows 10. It is located in an observatory at Arizona Sky Village, while I'm in Michigan. We have not tried to run the camera on a different PC. We could ask the gentleman that owns the observatory to try that.

    If anyone would like to TeamViewer in we certainly could arrange that.
     
  6. Tim

    Tim Staff Member

    Joined:
    Sep 25, 2014
    Messages:
    1,668
    The only other thing I can suggest is ensure your Windows PC is completely up to date, and you can also try a different serial cable and/or USB to serial adapter. Or as Colin already suggested, try a different PC to eliminate that as a possible cause.
     

Share This Page