vtorkalo / ascom.dslr Goto Github PK

Hi,
I install the ASCOM.DSLR .exe provided here and choose it in CCD Ciel. But when I connect to the camera (Canon 6D) it automatically just starts taking consecutive photos until the camera runs out of memory. Also CCD Ciel can no longer be operated.
I did not choose to take a photo.
Does the .exe from here work or must I compile my own .exe?
Thank you.
Markus

Hello, i'm the developer of the SW in subject. Some users report to me this project (congrats!) because they have problems to use the camera control in Voyager setting up with your ASCOM driver.

I check inside Voyager (and i tested also other brand software suite) that after StartExposure method (that doesn't fail) camera driver assume a CameraError status and when Voyager try to call ImageReady method to understand if all is finished the method give an exception "Camera not connected". After this if i retry an exposure the "camera not connected exception" continue to be thrown and a closing of driver with disconnect can reset the conditions.

If you have time i'm happy if you can investigate on it , you can download Voyager here:
https://software.starkeeper.it/index.php/download/

All the best and thanks for you effort an time
Leonardo Orazi

ASCOM.DSLR is giving the wrong pixel size for the Canon 5D MIII. The correct size is 6.25 um. This is what ASCOM.DSLR gives NINA when I use it:

2024-03-17T22:16:16.4192|TRACE|AscomDevice.cs|GetProperty|339|GET Camera.PixelSizeX: 3.8819875776397517

When i want to install Ascom.DSLR under WIndows 11 Pro, i get below warning.

Ive installed the latest Ascom Platform with all Dot.net frameworks.

W11 not compatible?

I'm using NINA and have FreeImage as the processor. In the ASCOM config I don't have Save Photos In checked. I see that I have both FITS and CR3 files but in different locations. The FITS go where I specify in NINA, and the CR3 files end up in Pictures\BackyardEOS and their names start with preview. Is it possible to have the driver remove the CR3 file as soon as NINA has converted them into FITS?

I'm not sure about other brands, as never used them before, but at least Canon cameras allow "manual" focusing via programmatic controls from EOS Utility. Stock photo just to show the controls:

These are particularly useful for astrophotography with long lenses, because they allow to perform manual focusing without touching the camera and the lens altogether, and so avoiding any shaking in the live view.

At the same time, ASCOM-compatible software usually supports focuser API for focuser rings... Given that ASCOM DSLR already bridges that gap for camera part, I wonder if it could simulate the focuser ring API too for even more control and compatibility with astrophotography software? cc @FearL0rd

First, thanks for this fantastic package! It is exactly what I was hoping to find to connect my Nikon cameras.

I'm just getting started, but discovered one small glitch in the initialization code.

Within NikonSKDCamera.cs .... The call to GetCapabilites in the Init routine needs to happen before it calls SetCameraToManual. Otherwise all the logic to test capabilities is invalid.

Works fine if the InitiCapabilites call is placed immediately after hooking up CaptureComplete.

Hi,

the ASCOM standard specifies that the list of gains should be an arraylist containing strings, but the code returns an arraylist of shorts.
The ASCOM.DriverAccess class forgave this error, but newer ASCOM library code currently does not.

See https://ascom-standards.org/Help/Developer/html/P_ASCOM_DeviceInterface_ICameraV3_Gains.htm

which proxies to

The code in the Camera class could simply become

return new ArrayList(ApiContainer.DslrCamera.IsoValues.Select(x => x.ToString());

I have raised an issue with the new ASCOMLibrary code to request that it forgive this error to allow existing binary versions of the ASCOM.DSLR to work.

ASCOMInitiative/ASCOMLibrary#28

cheers,

Robin

I was using this for a while, with my Canon DSLRs. Thanks! Now, moving to mirrorless (R5, R6, R7, R10, etc.). Is there support for these cameras? From this discussion (https://forums.sharpcap.co.uk/viewtopic.php?t=5268&sid=a312b746bb03ac6710cf90f92f48c6e2) it appears as though this may not be the case.

Is there a plan to update the driver? Otherwise, I cannot use the camera for live stacking via SharpCap Pro, for instance. Tx!

Hello,
I'm not a specialist and it is not a real issue.
Could you generate a Windows 64 bits version of ASCOM.DSLR ?
Most of the Astronomy software are moving to be only 64.
Thanks again for this very useful driver.
Didier SC

Hi,
First of all, this is an awesome project! Aside from cooling, not having ASCOM support on our DSLRs is the biggest drawback. To make this project even more accessible, we need to be able to use more selections of Nikons.

DigiCamControl has the ability to simulate bulb mode on almost all nikon dslrs. I use it myself with a Nikon D3300. Since this project already uses DCC as a library, why cant it use the bulb functionality that DCC provides?

Thanks for your amazing work,
Shlomi

Driver Setup Dialog Error

The SetupDialog method of driver "ASCOM.DSLR.Camera" threw an exception when called.

This means that the setup dialogue would not start properly.

Please screen print or use CTRL+C to copy all of this message and report it to the driver author with a request for assistance.

FileNotFoundException - Could not load file or assembly 'EDSDKLib, Version=1.1.1.0, Culture=neutral, PublicKeyToken=8d020bddf72dc52b' or one of its dependencies. The system cannot find the file specified.

OK

I tried to connect my Nikon Z8 to NINA using the ascom drivers and it just cannot connect to it. However, it works like a charm with my older Nikon Z7. The problem is that my Z7 is reserved for selling and will continue to use the Nikon Z8. Is there anyway i could make this work?

I want to use DSLR under Linux for live stacking. (develop)

Obviously the project is for Windows only. I try to understand how does the driver communicate with the camera.

What are the protocols are being used - how it works. Are there any design documents?

As the serial shutter cable hack (set RTS to high and switch a transistor) is not stable and harms all serial communication protocol standards I built a version using a ESP8266 and relays triggered by a amplified pin of it. I added a FTDI serial to usb adaptor (not wanted to use the serial of the NodeMCU) to support this ugly hack in the first step. Next step would be to avoid using this serial communication stuff anymore due to the esp is able to provide a web api controlling the whole thing. I wonder how to get started adding the ability to configure it. Can anyone provide me some help here? https://github.com/superdachs/NikonShutterController

Hello,

Whatever I re-install completely the driver or I just copy the Nikon SDK, I receive a "System.AggregateException" : Nikon.NikonException: failed to load MD3 file C:... The file might be corrupted or in use in another process.

Hello, first great initiative to have launched DSLR ascom driver project.
I am experiencing problem with 6D after downloading your last version. I try it with shartpcap and CCD ciel, both are not running but not at the same level. I follow your git tutorial and I am also able to compile and the exec file. Unfortunately I am not a C# developer and I am afraid to be able to help on the coding aspect. I better know Python. I post my problem to sharcap forum and CCDciel forum too. To summarize on sharcap I get immediately an exception and the picture is not displayed on screen whatever is the selected mode live view or not. With ccdciel it's a little bit better, it works in live view mode and the image is correctly displayed but in non live view mode, the image is not displayed and
the acquisition doesn't work well, it works once and save 1 fits and after camera is put in idle mode. I have to disconnect and reconnect again to make an acquisition again but only one. Well let me know if I can help in testing giving you some more info..

Philippe

Canon EOS Ra minimum is 1/8000s or 0.000125s, but the driver only goes down to 1/4000s or 0.00025s.

The new CameraValue for exposure of 1/250 was 1 / 150d should be 1 / 250d for that PropertyID.Tv.

Noticed this in NINA. NINA shows pixel size of 3.33728863838624 but the Canon EOS Ra's pixel size is 5.36. The only thing that I see this affecting is the framing assistant. I use BackyardEOS and the subs come in fine.

When I am trying to connect the camera it tries to shoot a picture (I hear the shutter) and it does that continuously without stop. Like a never ending loop. At the end the program crashes and I have to turn-off the DSLR.

Here's is a screenshot (if it helps):
https://drive.google.com/file/d/1B5tk2cvVNqRuIBxHkj2DzXYKv8CLCJF9/view?usp=sharing

https://www.virustotal.com/gui/file/da44bb9c5c1af487f85ca45dd16a8aeea8d469d0274d4343c896f22b8ffe996c/detection