869 replies to this topic

[tjay]

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

Alex,

 

We've started with a driver that was in progress already that took this approach, and the focus so far has been trying to get the basics working.  It is something I've considered, but we haven't really talked about it very much.  I think looking at one driver per manufacturer (i.e. one driver for Canons, one for Nikons, etc.)...

[deathtical]

Hello everyone,

 

I came across this while trying to find some way to get something that would allow me to use APT with my Pentax K3 II. It looks like you guys have done a great job but I appear to be having a similar issue outlined by others. I get the same error when try to test my camera.

 

Here is what I am getting as far as logs and messages.

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

************** Exception Text **************
ASCOM.NotConnectedException: Camera not connected ---> ASCOM.NotConnectedException: Camera not connected
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanForCameras()
   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 560
   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.

The ASCOM logs are in the attached zip file.

 

Please let me know if there is anything else I can provide to help you, help me.

 

Oh, as a side note, when I run the test, I can see it talking to the camera and it does "take a picture", but seems to timeout when trying to acquire it.

 

Thank you in advance.

Attached Files

•  Logs 2020-05-20.zip   7.46KB   38 downloads

[FearL0rd]

Hello everyone,

I came across this while trying to find some way to get something that would allow me to use APT with my Pentax K3 II. It looks like you guys have done a great job but I appear to be having a similar issue outlined by others. I get the same error when try to test my camera.

Here is what I am getting as far as logs and messages.

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

************** Exception Text **************
ASCOM.NotConnectedException: Camera not connected ---> ASCOM.NotConnectedException: Camera not connected
   at ASCOM.DSLR.Classes.CanonSdkCamera.ScanForCameras()
   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 560
   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.

The ASCOM logs are in the attached zip file.

Please let me know if there is anything else I can provide to help you, help me.

Oh, as a side note, when I run the test, I can see it talking to the camera and it does "take a picture", but seems to timeout when trying to acquire it.

Thank you in advance.

can tou try to open the test app and select Pentax in the camera? looks like canon is selected. can you try to use the ASCOM driver testing also

Sent from my SM-G975U using Tapatalk

[deathtical]

can tou try to open the test app and select Pentax in the camera? looks like canon is selected. can you try to use the ASCOM driver testing also

Sent from my SM-G975U using Tapatalk

What version is that? It doesn't look like the version I downloaded yesterday. Is there a newer version since yesterday?

 

Thanks

[FearL0rd]

ASCOM Diagnostics is instaled your machine by default when ascom framework is installed. try to search for ascom in the star menu. if itnis nit there you need to install ascom before use the driver

Sent from my SM-G975U using Tapatalk

[deathtical]

Just to clarify, this is what I see...

 

Album: screen shots

45 images

0 comments

 

Thank you

[FearL0rd]

Just to clarify, this is what I see...



Thank you

pentax doesn't have api. the application calss a external pentax software to execute commands. try this options

Sent from my SM-G975U using Tapatalk

[deathtical]

pentax doesn't have api. the application calss a external pentax software to execute commands. try this options

Sent from my SM-G975U using Tapatalk

Those settings are what I used each time. I tried using the Diagnostic tool rather than the test tool (both 32 and 64 bit) and I still get the same timeout error. It still tries to take the test photo, but nothing happens after that but the error.

Edited by deathtical, 20 May 2020 - 03:18 PM.

[lmclouth]

I just tried the Device Connection Tester and here is the result.

 

Attached Thumbnails

• 

[FearL0rd]

I just tried the Device Connection Tester and here is the result.

in the properties coould you please check? Store in the Location

Sent from my SM-G975U using Tapatalk

[lmclouth]

in the properties coould you please check? Store in the Location

Sent from my SM-G975U using Tapatalk

I did that and now this is the output:

Attached Thumbnails

• 

[FearL0rd]

I did that and now this is the output:

@tjay is writing troubleshoot logging. he will countact you

Sent from my SM-G975U using Tapatalk

[FearL0rd]

I did that and now this is the output:

Can you try the tester in 32bits mode?

[lmclouth]

ASCOM Device Connection Tester 32bit mode result:

 

Attached Thumbnails

• 

[tjay]

@tjay is writing troubleshoot logging. he will countact you

Sent from my SM-G975U using Tapatalk

Still working on it but not as fast as I would like! Sorry (Yeah I am Canadian )

Sent from my SM-T713 using Tapatalk

Edited by tjay, 22 May 2020 - 06:56 PM.

[FearL0rd]

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)

Im getting the same error with my non DSLR astrocamera. It stops during the gain

[NightBear]

Im getting the same error with my non DSLR astrocamera. It stops during the gain

Hmm that's weird. Maybe try the 32-bit version of sharpcap?

[boelaars]

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

 

error.png

Just installed the latest ASCOM Platform 6.4 and the ASCOM.DSLR drivers from the first post in this thread. Testing with a Nikon d7500, I get this exact same error when trying the ASCOM.DSLR.Test application.

 

However after a few attempts that error now suddenly disappeared and I only get a popup that says 'Driver setup method failed: "ASCOM.DSLR.Camera" Object reference not set to an instance of an object.'

 

That just appears to save none of the settings, because if I simply proceed and click "Connect" the error messages show me it's trying to connect to a Canon camera, despite having tried to set it to Nikon.

 

Happy to help with debugging in some way or other. Have a Nikon d850 and d7500 at hand. (And have Visual Studio Professional, but not exactly experienced using it.  )

[rwgrwg]

Im getting the same error with my non DSLR astrocamera. It stops during the gain

Hi,

 

If you have implemented the GainMin/GainMax/Gain integer properties then SharpCap will expect to be able to set any value between the minimum and the maximum and will choose what it thinks are appropriate values in the allowed range. So for instance if the minimum is 100 and the maximum is 1600, SharpCap might pick 177, 334, 405, or whatever other random seeming values in that range as the gain is that it will test.

 

Another option with the Ascom driver is to implement a discrete list of gains via the ICamera.Gains property - SharpCap will read this list and offer you those gains to choose between is a drop-down, but the sensor analysis functionality currently does not support this type of gain control. There's no really good reason that it shouldn't support it except for the fact that I'd not come across very many cases of it being used, so it didn't seem worth implementing at the time.

 

Hope this helps, Robin

[deathtical]

in the properties coould you please check? Store in the Location

Sent from my SM-G975U using Tapatalk

Sorry for the delayed response. I have tried both the 32 and 64 bit versions of the test with my Pentax K3 II. I have ticked the box you indicated above. I still get the timeout error.

 

Thanks

[FearL0rd]

Hi,

 

If you have implemented the GainMin/GainMax/Gain integer properties then SharpCap will expect to be able to set any value between the minimum and the maximum and will choose what it thinks are appropriate values in the allowed range. So for instance if the minimum is 100 and the maximum is 1600, SharpCap might pick 177, 334, 405, or whatever other random seeming values in that range as the gain is that it will test.

 

Another option with the Ascom driver is to implement a discrete list of gains via the ICamera.Gains property - SharpCap will read this list and offer you those gains to choose between is a drop-down, but the sensor analysis functionality currently does not support this type of gain control. There's no really good reason that it shouldn't support it except for the fact that I'd not come across very many cases of it being used, so it didn't seem worth implementing at the time.

 

Hope this helps, Robin

I did this in my dev environment but SharpcAP still failing. 

[FearL0rd]

Just installed the latest ASCOM Platform 6.4 and the ASCOM.DSLR drivers from the first post in this thread. Testing with a Nikon d7500, I get this exact same error when trying the ASCOM.DSLR.Test application.

 

However after a few attempts that error now suddenly disappeared and I only get a popup that says 'Driver setup method failed: "ASCOM.DSLR.Camera" Object reference not set to an instance of an object.'

 

That just appears to save none of the settings, because if I simply proceed and click "Connect" the error messages show me it's trying to connect to a Canon camera, despite having tried to set it to Nikon.

 

Happy to help with debugging in some way or other. Have a Nikon d850 and d7500 at hand. (And have Visual Studio Professional, but not exactly experienced using it.  )

Do you mind have a teamviewer session and I can debug the code in your machine like I done with @NightBear fixing his problems?

[FearL0rd]

I have made a change in the driver for Nikon cameras 

 

Could you please test? 

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

Edited by FearL0rd, 28 May 2020 - 05:26 PM.

[Elephant42]

I have made a change in the driver for Nikon cameras 

 

Could you please test? 

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

Nikon D7200

 

Can select the driver and open the Properties dialog but Get a System.NullReferenceException after closing the DSLR Setup window.

Have got as far as looking at

ASCOM.DSLR.Classes.DigiCamControlCamera.LogCameraInfo(ICameraDevice camera)

Most (but not all) of the properties on the camera parameter are null.  The exception occurs as soon as one of these null properties is referenced.

 

Am now digging into the gizzards of CameraControl.Devices.CameraDeviceManager.ConnectToCamera(bool retry) in an attempt to determine where the missing properties have gone.

Will report anything I can discover...

[FearL0rd]

anybody with a Nikon, Canon or Pentax that want to have a TeamViewer where I can debug the code using your computer?