cedric-r / ascom.homemade.sbigcamera Goto Github PK

The imaging camera driver loads and works in Prism 10 Advanced, but only produces a 640x480 image instead of the 4500x3600 image. Actually, both the imaging and external drivers load and all 3 of the drivers produce a 640x480 image. Is that built in to the driver?

Is ASCOM Alpaca porting foreseen?

Hi. I've tried your drivers and the image driver works fine but there is no way to get any image from the guiding camera. No error, just a pure black image. Am I doing something wrong?

May be it is related so FYI, I went through these steps

• Working SGP with SGP API Guider
• I installed NINA and the Sbig Tracker driver which I kew was going to break the SGP API guider plugin. This happened always to me and I've found no way to fix it.
• NINA Sbig camera showed some disconnections while in session so I tried your driver
• Homemade driver installed, imaging camera works fine but tracking camera always return a black image in PHD2. When I try the guiding camera in NINA I also get a black image. No errors.

How could I help you to fix this?
Thanks in advance
Alvaro Fornas

I am an ASCOM developer and I installed your SBIG ASCOM driver and attempted to connect to my ST-2000XCM in my imaging application. The connection failed. I can see in Device Manager that the camera's USB interface is flagged as Unknown.

Do I need to download any DLL files from SBIG? I only ran your Setup program.

SBIG_Common_xxxx.log:
10/9/2021 13:14:21.452: Connect: Connection request
10/9/2021 13:14:21.458: Connected Set: Enumerating USB cameras
10/9/2021 13:14:21.458: Connected Set: No camera found
10/9/2021 13:14:21.458: Disconnect: Disconnecting device
10/9/2021 13:14:21.475: SBIGService HandleMessage: Message is CCD_INFO
10/9/2021 13:14:21.481: SBIGService HandleMessage: Error: CE_DRIVER_NOT_OPEN
at SbigSharp.SBIG.UnivDrvCommand[TParams,TResults](PAR_COMMAND command, TParams Params, TResults& pResults)
at ASCOM.HomeMade.SBIGCommon.SBIGHandler.UnivDrvCommand[TParams,TResults](PAR_COMMAND command, TParams Params, TResults& pResults)
at ASCOM.HomeMade.SBIGCommon.SBIGHandler.HandleMessage(SBIGRequest request)

10/9/2021 13:14:21.490: Disconnect: Disconnection requested
10/9/2021 13:14:21.490: Disconnect: Disconnecting device

SBIG_Imaging_Camera_xxxx.log
10/9/2021 13:14:21.427: Camera: Starting initialisation
10/9/2021 13:14:21.427: DriverVersion Get: 1.1.0
ASCOM.HomeMade.SBIGImagingCamera v1.1.0
Process ID: 12744
10/9/2021 13:14:21.427: Camera: Completed initialisation
10/9/2021 13:14:21.443: InterfaceVersion Get: 3
10/9/2021 13:14:21.445: Connected: Set True
10/9/2021 13:14:21.447: IsConnected: connectionState=False
10/9/2021 13:14:21.458: Connected Set: Connected to camera
10/9/2021 13:14:21.458: Connected Set: Getting camera info
10/9/2021 13:14:21.458: IsConnected: connectionState=True
10/9/2021 13:14:21.484: Connected Set: Error: CE_DRIVER_NOT_OPEN
at ASCOM.HomeMade.SBIGClient.SBIGClient.CCD_INFO(GetCCDInfoParams tparams)
at ASCOM.HomeMade.SBIGClient.ISBIGCameraSpecs.GetCameraSpecs()

10/9/2021 13:14:21.486: Connected Set: Error: CE_DRIVER_NOT_OPEN
at ASCOM.HomeMade.SBIGClient.SBIGClient.CCD_INFO(GetCCDInfoParams tparams)
at ASCOM.HomeMade.SBIGClient.ISBIGCameraSpecs.GetCameraSpecs()

at ASCOM.HomeMade.SBIGClient.ISBIGCameraSpecs.GetCameraSpecs()
at ASCOM.HomeMade.SBIGCamera.SBIGCamera.set_Connected(Boolean value)

10/9/2021 13:14:21.490: IsConnected: connectionState=True

Charlie Miller
[email protected]

Hi.

First of all I would like to thank you for the great work you have done with the development of this ascom driver.

I have a SBIG STF8300 Mono Camera. While testing your drivers with the astrosoftware N.I.N.A I noticed that the pixel size is displayed incorrectly. After connecting the camera with N.I.N.A a pixel size of 54 micro meter is displayed instead of 5.4 micro meter. Can I change this myself or do you need to change this in your driver program.

BR
Manfred

I am interested in this driver to use an older SBIG STF-402M as a guider camera. The camera works fine in MaxIm DL through the native SBIG Universal driver plugin. I tried to connect to the camera via the ASCOM driver plugin in MaxIm DL which fails with the attached error message. I have not yet tried connecting from other software or from scripts, but this error already hints at a non-conformity. The CanFastReadout property seems undefined, at least for this camera model. - https://ascom-standards.org/Help/Developer/html/P_ASCOM_DriverAccess_Camera_CanFastReadout.htm

Best,
4ks1

Just wondering if I can get some assistance with an issue I'm having.
On my micro-pc, I get the following exception when I attempt to connect to my SBIG ST8300M through NINA.

ERROR|AscomDevice.cs|Connect|241
ASCOM.DriverException: Unable to load DLL 'HomeMade.SBIGUDrv.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at SbigSharp.SBIGDLL.SBIGUnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG.SBIGUnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG._UnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG.UnivDrvCommand(PAR_COMMAND command)
   at ASCOM.HomeMade.SBIGCommon.SBIGHandler.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGHub.SharedResources.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGClient.SBIGClient.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGCamera.SBIGCamera.set_Connected(Boolean value)
 ---> System.Exception: Unable to load DLL 'HomeMade.SBIGUDrv.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
   at SbigSharp.SBIGDLL.SBIGUnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG.SBIGUnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG._UnivDrvCommand(PAR_COMMAND command, IntPtr Params, IntPtr pResults)
   at SbigSharp.SBIG.UnivDrvCommand(PAR_COMMAND command)
   at ASCOM.HomeMade.SBIGCommon.SBIGHandler.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGHub.SharedResources.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGClient.SBIGClient.Connect(String ipAddress)
   at ASCOM.HomeMade.SBIGCamera.SBIGCamera.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 637
   at ASCOM.DriverAccess.MemberFactory.SetTargetInvocationExceptionHandler(String memberName, Exception e) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 654
   at ASCOM.DriverAccess.MemberFactory.CallMember(Int32 memberCode, String memberName, Type[] parameterTypes, Object[] parms) in C:\ASCOM Build\Export\ASCOM.DriverAccess\MemberFactory.cs:line 372
   at ASCOM.DriverAccess.AscomDriver.set_Connected(Boolean value) in C:\ASCOM Build\Export\ASCOM.DriverAccess\AscomDriver.cs:line 161
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at Castle.DynamicProxy.AbstractInvocation.Proceed()
   at NINA.Equipment.Equipment.AscomDevice`3.set_Connected(Boolean value) in C:\Projects\nina\NINA.Equipment\Equipment\AscomDevice.cs:line 143
   at NINA.Equipment.Equipment.AscomDevice`3.<<Connect>b__45_0>d.MoveNext() in C:\Projects\nina\NINA.Equipment\Equipment\AscomDevice.cs:line 235

The same version of the driver and NINA are running on my main laptop, but I'm trying to migrate to the new MicroPC and can't seem to get past this issue.

I have reinstalled the ASCOM, the SBIG native drivers, the HomeMade.SBIGCamera driver.

The MicroPC NINA instance is connecting to my mount via ASCOM without an issue, and to PHD2 via ASCOM, so I don't think that that the ASCOM platform or NINA are the issue here - I'd say something has gone sideways on the installation of the SBIG ASCOM driver.

Would love to hear your thoughts.

Also - Thank you so much for providing an ASCOM driver for the SBIG cameras... I'm a .NET dev, and was planning on having a crack at it until I found yours! On my main laptop - its flawless!

Hello,
I was wondering whether the ASCOM.Homemade.SBIGCamera is also usable for ST-4000 XCM?
Thanks in advance for your reaction.
Regards,
Dirk

Hi Cedric. I've been testing your driver and I've come with an unexpected problem. When main camera is reading an image and the guider tries also to read, guider image is just noise. What baffles me is that PHD2 Guiding goes wild without reason. This is a frame error that happened at 19:51:16

Here are the logs. a lot of files. I suppose it is because I had Trace enabled
https://www.dropbox.com/s/z9o1b11uduaiseo/Logs.rar?dl=0

Hi Cedric,

I receive a message on CN from a CCDciel user that get an access violation exception when reading the imagearray using a ASCOM.HomeMade.SBIGCamera driver. A quick search about this driver take me here and I see you are the author of this :) congratulation to take this well needed task!

Not sure if this is related to this error but looking at the code I remark the imagearray is defined as unsigned when the ascom specification is 32bit signed integer.
Definition found at row 26 of ASCOM.HomeMade.SBIGCommon/ISBIGCamera.cs :
public UInt32[,] cameraImageArray;
must be:
public int[,] cameraImageArray;

Patrick

Hy there I was using your drive on Nina was perfect, one day I was take picture and nina Can't change the filter Itried to connet the filter whell again and apear this message "Unable to connect to Ascom Sbig Filterwhell Driver...Reason No sutitable camera found on ascom.homemade.set_connected(Boolean value) camera still working!
I tried reinstall your driver ascom plataform and still showing this.
I used the CCDops and the filter wheell is working
Could you help me
tks

Hi Cedric, I've noticed something strange with these drivers. SBIG STXL-11002 has an external guider camera (it is on the filter wheel) that isn't cooled but PHD2 thinks it is cooled

If I deactivate the cooler on PHD2, it also gets deactivated in the NINA imaging camera. They share cooler controls.

Not really sure how PHD2 manages cooling but I've got several imaging session in which at some point cooler is set off and I think it is PHD2 swithing it off. SBIG STXL-11002 Guide Camera driver should report it has no cooling capabilities.

Also, I think guiding camera has no temperature sensor. Don't know where is driver getting it from. Guide temp doesn't match perfectly with the main imagin camera temp. May be both are read at different instants.

Hope it helps

Regards
Alvaro Fornas