Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

ASCOM.DSLR - ASCOM driver for dslr cameras (Canon, Nikon, Pentax, Sony)

astrophotography CMOS ccd dslr
  • Please log in to reply
869 replies to this topic

#26 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 18 May 2020 - 07:22 PM

A very close together click click.

I have identified that newer cameras and old cameras have a different way to take pictures for exposures <1s. I have implemented a function to try to identify the camera and take the picture properly.

 

Could you please test?

 

https://github.com/F...amera Setup.exe



#27 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 196
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 18 May 2020 - 08:16 PM

I have identified that newer cameras and old cameras have a different way to take pictures for exposures <1s. I have implemented a function to try to identify the camera and take the picture properly.

 

Could you please test?

 

https://github.com/F...amera Setup.exe

Nope, I get the exact same results and the exact same error in SharpCap.


  • akagai1960 likes this

#28 NightBear

NightBear

    Mariner 2

  • *****
  • Posts: 215
  • Joined: 12 Nov 2019

Posted 18 May 2020 - 11:04 PM

Hi, I'm also around trying to get this to work. I have a Canon 700D/T5i. If there's anything specific you want me to test, let me know.



#29 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 18 May 2020 - 11:21 PM

Hi, I'm also around trying to get this to work. I have a Canon 700D/T5i. If there's anything specific you want me to test, let me know.

have you tried the lasted update? https://github.com/F...amera Setup.exe

 

can you try in both of your cameras?


Edited by FearL0rd, 18 May 2020 - 11:23 PM.


#30 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 18 May 2020 - 11:21 PM

Nope, I get the exact same results and the exact same error in SharpCap.

I will wait the logs from tom 



#31 scottmm2012

scottmm2012

    Ranger 4

  • *****
  • Posts: 317
  • Joined: 17 Jun 2017

Posted 19 May 2020 - 04:18 AM

Attempted new package this morning, using the Canon SDK in the ASCOM camera chooser, DSLR Setup (Canon T3i/600D): 

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

************** Exception Text **************
ASCOM.DriverException: Timeout waiting for setup exposure ---> ASCOM.DriverException: Timeout waiting for setup exposure
   at ASCOM.DSLR.Classes.CameraModelDetector.GetCameraModel(IDslrCamera camera, String storePath)
   at ASCOM.DSLR.Classes.BaseCamera.GetCameraModel(String cameraDescription)
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanCameras()
   at ASCOM.DSLR.Classes.CanonSdkCamera.get_MainCamera()
   at ASCOM.DSLR.Classes.CanonSdkCamera.OpenSession()
   at ASCOM.DSLR.Classes.CanonSdkCamera.ConnectCamera()
   at ASCOM.DSLR.Camera.set_Connected(Boolean value)
   --- End of inner exception stack trace ---
   at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 614
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 648
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 315
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 146
   at ASCOM.DSLR.Form1.buttonConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ASCOM.DSLR.Test
    Assembly Version: 6.2.0.0
    Win32 Version: 6.2.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Test.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ASCOM.DriverAccess
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DriverAccess/6.0.0.0__565de7938946fba7/ASCOM.DriverAccess.dll
----------------------------------------
ASCOM.DeviceInterfaces
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll
----------------------------------------
ASCOM.Utilities
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ASCOM.Exceptions
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll
----------------------------------------
ASCOM.DSLR.Camera
    Assembly Version: 0.5.73.0
    Win32 Version: 0.5.73
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Camera.DLL
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
EDSDKLib
    Assembly Version: 1.1.1.0
    Win32 Version: 1.1.1.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/EDSDKLib.DLL
----------------------------------------
OTelescope.API
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/OTelescope.API.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.

 

 

When using the BYEOS, in the Camera Chooser, DSLR Setup, I get this with no logging.

 

BYEOS DSLR Setup.JPG

 


Edited by scottmm2012, 19 May 2020 - 04:25 AM.


#32 NightBear

NightBear

    Mariner 2

  • *****
  • Posts: 215
  • Joined: 12 Nov 2019

Posted 19 May 2020 - 07:34 AM

Here is the error I got when trying to apply the DSLR settings:

 

error.png



#33 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 19 May 2020 - 08:50 AM

With my Canon EOS 7D Mark II, I get the attached error window in SharpCap after I select "ASCOM Camera Driver for DSLR".

The shutter will click twice, then the DSLR Setup window will appear.  I click on the OK button and the shutter clicks again and the "error in SharpCap.jpg" window appears.

 

Then with SharpCap closed and the power cycled on the camera, I run the ASCOM.DSLR.Test.exe and click the "Choose" button to make the "ASCOM Camera Chooser" window appear.  "ASCOM Camera Driver for DSLR" is already selected so I click the OK button.  Then I click the "Connect" button in the Test program and the shutter clicks and an unhandled exception window appears.  The detailed text is in the attached file.

 

A very close together click click.

Any of you cloud offer your computer to have visual studio loaded and I could open the code and Debug live using TeamViewer?



#34 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 19 May 2020 - 08:54 AM

Here is the error I got when trying to apply the DSLR settings:

 

attachicon.giferror.png

 

Attempted new package this morning, using the Canon SDK in the ASCOM camera chooser, DSLR Setup (Canon T3i/600D): 

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

************** Exception Text **************

 

What's the version of your ascom platform drivers? Could you please download the latest from their website?

 

https://github.com/A...MPlatform64.exe


  • scottmm2012 likes this

#35 NightBear

NightBear

    Mariner 2

  • *****
  • Posts: 215
  • Joined: 12 Nov 2019

Posted 19 May 2020 - 01:27 PM

Any of you cloud offer your computer to have visual studio loaded and I could open the code and Debug live using TeamViewer?

Sure, I sent you a PM.



#36 scottmm2012

scottmm2012

    Ranger 4

  • *****
  • Posts: 317
  • Joined: 17 Jun 2017

Posted 19 May 2020 - 06:02 PM

What's the version of your ascom platform drivers? Could you please download the latest from their website?

 

https://github.com/A...MPlatform64.exe

Ascom Ver.JPG

Downloading SP1, will take a while.  I'm on satellite.



#37 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 19 May 2020 - 06:44 PM

attachicon.gifAscom Ver.JPG

Downloading SP1, will take a while. I'm on satellite.

I remote and troubleshoot njghtbear and Im abke to make it work with exposures >=1 second. could you please test.

now Im going to work for the bellow 1s

Sent from my SM-G975U using Tapatalk

#38 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 19 May 2020 - 07:25 PM

I'll send you a private message.  I've built version of the driver with some low level logging that may help us debug this, but it definitely won't fix the issue, so I don't want to distributed too far.

 

Thanks for the error report!  Hopefully we can get it fixed soon!

 

Tom

 

With my Canon EOS 7D Mark II, I get the attached error window in SharpCap after I select "ASCOM Camera Driver for DSLR".

The shutter will click twice, then the DSLR Setup window will appear.  I click on the OK button and the shutter clicks again and the "error in SharpCap.jpg" window appears.

 

Then with SharpCap closed and the power cycled on the camera, I run the ASCOM.DSLR.Test.exe and click the "Choose" button to make the "ASCOM Camera Chooser" window appear.  "ASCOM Camera Driver for DSLR" is already selected so I click the OK button.  Then I click the "Connect" button in the Test program and the shutter clicks and an unhandled exception window appears.  The detailed text is in the attached file.

 

Thanks for the effort. 

 

Unfortunately, after downloading the new stuff, I still could not connect with either my 6D or 450.....Both had the same message:

 

The details of the error are:

Camera exposure failed, msg. 'Camera Error.'

 

Sharpcap itself did not crash, or freeze.

 

Alex

 

 

 

Good News,

 

Im able to troubleshooting using NightBear computer and visual studio. Please redownload the driver from here and reinstall. It should fix the problems. 

We did a test with sharpcap using the sensor analyses command and it is working.

 

https://github.com/F...amera Setup.exe


Edited by FearL0rd, 19 May 2020 - 07:27 PM.

  • tjay likes this

#39 NightBear

NightBear

    Mariner 2

  • *****
  • Posts: 215
  • Joined: 12 Nov 2019

Posted 19 May 2020 - 07:37 PM

SharpCap Sensor analysis on a DSLR seems to be possibly working!

 

 

 

 

Attached Thumbnails

  • dslr_sa.jpg

  • tjay likes this

#40 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 196
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 19 May 2020 - 08:17 PM

Good News,

 

Im able to troubleshooting using NightBear computer and visual studio. Please redownload the driver from here and reinstall. It should fix the problems. 

We did a test with sharpcap using the sensor analyses command and it is working.

 

https://github.com/F...amera Setup.exe

I just tried it with my Canon EOS 7D Mark II and SharpCap and hear two quick clicks and then this error window appears.

Attached Thumbnails

  • SharpCap error tab 1.jpg
  • SharpCap error tab 2.jpg


#41 tjay

tjay

    Gemini

  • *****
  • Posts: 3,349
  • Joined: 03 Feb 2007
  • Loc: just outside of Toronto

Posted 19 May 2020 - 10:30 PM

I just tried it with my Canon EOS 7D Mark II and SharpCap and hear two quick clicks and then this error window appears.

 

Is there more text to right in "Stack Trace" property?  That might help us narrow down the problem some more, since neither of us have a EOS 7D Mark II.

 

Thanks in advance!



#42 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 19 May 2020 - 10:32 PM

I just tried it with my Canon EOS 7D Mark II and SharpCap and hear two quick clicks and then this error window appears.

can you run the test app also and send the logs over?

Sent from my SM-G975U using Tapatalk

#43 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 196
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 19 May 2020 - 11:00 PM

Is there more text to right in "Stack Trace" property?  That might help us narrow down the problem some more, since neither of us have a EOS 7D Mark II.

 

Thanks in advance!

 

I wanted to get that same error again so I could tell you what the rest of the text in the "Stack Trace" said but now I'm getting something different.

I believe I still have everything setup the same (i.e. camera still in 'M' mode, connected to same USB port, etc.) but now when I select "ASCOM Camera Driver for DSLR" in SharpCap the quick clicks happen and then the DSLR Setup window appears.  If I just click OK, then this window now appears.

 

I've tried switching the camera to 'B' mode but now I still get that same error in SharpCap.

Attached Thumbnails

  • SharpCap new error.jpg


#44 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 196
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 19 May 2020 - 11:03 PM

can you run the test app also and send the logs over?

Sent from my SM-G975U using Tapatalk

Here is the error I get with the ASCOM_DSLR_Test and its text.

Attached Thumbnails

  • Test error.jpg

Attached Files



#45 scottmm2012

scottmm2012

    Ranger 4

  • *****
  • Posts: 317
  • Joined: 17 Jun 2017

Posted 20 May 2020 - 05:28 AM

Using the BYEOS option in the camera chooser:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
ASCOM.DriverException: Timeout waiting for setup exposure ---> ASCOM.DriverException: Timeout waiting for setup exposure
   at ASCOM.DSLR.Classes.CameraModelDetector.GetCameraModel(IDslrCamera camera, String storePath)
   at ASCOM.DSLR.Classes.BaseCamera.GetCameraModel(String cameraDescription)
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanCameras()
   at ASCOM.DSLR.Classes.CanonSdkCamera.get_MainCamera()
   at ASCOM.DSLR.Classes.CanonSdkCamera.OpenSession()
   at ASCOM.DSLR.Classes.CanonSdkCamera.ConnectCamera()
   at ASCOM.DSLR.Camera.set_Connected(Boolean value)
   --- End of inner exception stack trace ---
   at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 614
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 648
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 315
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 146
   at ASCOM.DSLR.Form1.buttonConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ASCOM.DSLR.Test
    Assembly Version: 6.2.0.0
    Win32 Version: 6.2.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Test.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ASCOM.DriverAccess
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DriverAccess/6.0.0.0__565de7938946fba7/ASCOM.DriverAccess.dll
----------------------------------------
ASCOM.DeviceInterfaces
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll
----------------------------------------
ASCOM.Exceptions
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll
----------------------------------------
ASCOM.Utilities
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ASCOM.DSLR.Camera
    Assembly Version: 0.5.77.0
    Win32 Version: 0.5.77
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Camera.DLL
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
EDSDKLib
    Assembly Version: 1.1.1.0
    Win32 Version: 1.1.1.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/EDSDKLib.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.


__________________________________________________________

 

When using the Canon SDK option in the camera chooser.  I initially get the timeout error:

CanonSDK Error 1.JPG

 

than this error.

CanonSDK.JPG

Details:

 See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
ASCOM.DriverException: CheckDotNetExceptions ASCOM.DSLR.Camera ConnectedSet System.InvalidOperationException: Sequence contains no elements
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   at ASCOM.DSLR.Classes.CanonSdkCamera.GetSelectedIsoValue()
   at ASCOM.DSLR.Classes.CanonSdkCamera.InitSettings()
   at ASCOM.DSLR.Classes.CanonSdkCamera.StartExposure(Double Duration, Boolean Light)
   at ASCOM.DSLR.Classes.CameraModelDetector.GetCameraModel(IDslrCamera camera, String storePath)
   at ASCOM.DSLR.Classes.BaseCamera.GetCameraModel(String cameraDescription)
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanCameras()
   at ASCOM.DSLR.Classes.CanonSdkCamera.get_MainCamera()
   at ASCOM.DSLR.Classes.CanonSdkCamera.OpenSession()
   at ASCOM.DSLR.Classes.CanonSdkCamera.ConnectCamera()
   at ASCOM.DSLR.Camera.set_Connected(Boolean value) (See Inner Exception for details) ---> System.InvalidOperationException: Sequence contains no elements
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   at ASCOM.DSLR.Classes.CanonSdkCamera.GetSelectedIsoValue()
   at ASCOM.DSLR.Classes.CanonSdkCamera.InitSettings()
   at ASCOM.DSLR.Classes.CanonSdkCamera.StartExposure(Double Duration, Boolean Light)
   at ASCOM.DSLR.Classes.CameraModelDetector.GetCameraModel(IDslrCamera camera, String storePath)
   at ASCOM.DSLR.Classes.BaseCamera.GetCameraModel(String cameraDescription)
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanCameras()
   at ASCOM.DSLR.Classes.CanonSdkCamera.get_MainCamera()
   at ASCOM.DSLR.Classes.CanonSdkCamera.OpenSession()
   at ASCOM.DSLR.Classes.CanonSdkCamera.ConnectCamera()
   at ASCOM.DSLR.Camera.set_Connected(Boolean value)
   --- End of inner exception stack trace ---
   at ASCOM.DriverAccess.MemberFactory.CheckDotNetExceptions(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 630
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 648
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 315
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 146
   at ASCOM.DSLR.Form1.buttonConnect_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
ASCOM.DSLR.Test
    Assembly Version: 6.2.0.0
    Win32 Version: 6.2.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Test.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
ASCOM.DriverAccess
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DriverAccess/6.0.0.0__565de7938946fba7/ASCOM.DriverAccess.dll
----------------------------------------
ASCOM.DeviceInterfaces
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.DeviceInterfaces/6.0.0.0__565de7938946fba7/ASCOM.DeviceInterfaces.dll
----------------------------------------
ASCOM.Utilities
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 14.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ASCOM.Exceptions
    Assembly Version: 6.0.0.0
    Win32 Version: 6.4.1.2695
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/ASCOM.Exceptions/6.0.0.0__565de7938946fba7/ASCOM.Exceptions.dll
----------------------------------------
ASCOM.DSLR.Camera
    Assembly Version: 0.5.77.0
    Win32 Version: 0.5.77
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/ASCOM.DSLR.Camera.DLL
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
EDSDKLib
    Assembly Version: 1.1.1.0
    Win32 Version: 1.1.1.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/Camera/ASCOM.DSLR.Camera/EDSDKLib.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.


I guess the question for me is to streamline the testing.  Which option should we choose.  The BYEOS option or the Canon SDK option?

 


 



#46 NightBear

NightBear

    Mariner 2

  • *****
  • Posts: 215
  • Joined: 12 Nov 2019

Posted 20 May 2020 - 10:42 AM

Ah, as I feared, the sensor analysis doesn't quite work right. When it gets to the part where it tries to adjust the gain, sharpcap crashes. My guess is that it doesn't know how to handle DSLR ISO settings as actual gain values. Is there some way to possibly change the ASCOM driver to translate the ISO settings into a linear gain range? E.g. ISO 100,200,400,800... = Gain 0,1,2,3... Gain=Log2(ISO/100)

Attached Thumbnails

  • 2.jpg

Edited by NightBear, 20 May 2020 - 11:03 AM.


#47 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 20 May 2020 - 11:08 AM

Ah, as I feared, the sensor analysis doesn't quite work right. When it gets to the part where it tries to adjust the gain, sharpcap crashes. My guess is that it doesn't know how to handle DSLR ISO settings as actual gain values. Is there some way to possibly change the ASCOM driver to translate the ISO settings into a linear gain range? E.g. ISO 100,200,400,800... = Gain 0,1,2,3... Gain=Log2(ISO/100)

i know there is a way to have a ISO vector. I haven't figure out how to use it yet

Sent from my SM-G975U using Tapatalk

#48 charotarguy

charotarguy

    Apollo

  • *****
  • Posts: 1,356
  • Joined: 10 Sep 2014

Posted 20 May 2020 - 12:37 PM

I see you have Sony in the title of the thread, will it work with Sony cameras? 



#49 Alex McConahay

Alex McConahay

    Hubble

  • *****
  • Posts: 14,181
  • Joined: 11 Aug 2008
  • Loc: Moreno Valley, CA

Posted 20 May 2020 - 12:47 PM

I have not written a program in quite a while......but, it seems to me that instead of trying to write one driver that works for all DSLR cameras, it might be easier to get one camera (Canon, I might suggest) that works.

 

And, learning what you learned from that, write a different driver to work with another camera. (Nikon would probably be second most used).

 

Of course you re-use what you had that was Sharp Cap specific in each driver. But you only have to adapt the output to comply with the different input demands of the camera system.

 

They would be separate drivers. Why, after all, does my camera need to know about the other cameras? Just give each person a driver that works with their particular camera. It seems that is the way it works with most drivers--they are device specific. 

 

I know it is easy for me to say, since all I do is every now and then report my progress. But, would not this ease the burden of getting at least one line of dslr's going? Then, the others can be worked out one by one. Trying to work on all of them at once must add to the complexity. 

 

Alex

 



#50 FearL0rd

FearL0rd

    Messenger

  • *****
  • topic starter
  • Posts: 453
  • Joined: 11 Oct 2019
  • Loc: Houston, TX Area

Posted 20 May 2020 - 01:01 PM

I have not written a program in quite a while......but, it seems to me that instead of trying to write one driver that works for all DSLR cameras, it might be easier to get one camera (Canon, I might suggest) that works.

And, learning what you learned from that, write a different driver to work with another camera. (Nikon would probably be second most used).

Of course you re-use what you had that was Sharp Cap specific in each driver. But you only have to adapt the output to comply with the different input demands of the camera system.

They would be separate drivers. Why, after all, does my camera need to know about the other cameras? Just give each person a driver that works with their particular camera. It seems that is the way it works with most drivers--they are device specific.

I know it is easy for me to say, since all I do is every now and then report my progress. But, would not this ease the burden of getting at least one line of dslr's going? Then, the others can be worked out one by one. Trying to work on all of them at once must add to the complexity.

Alex

yes we are working on Canon first. the other options are there but without a lot of work.

Sent from my SM-G975U using Tapatalk


CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics





Also tagged with one or more of these keywords: astrophotography, CMOS, ccd, dslr



Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics