I have written a script FitsCap.txt to collect ASCOM images using the old FITS.dll. These images open directly in imageJ, which has powerful image correction methods. https://neutronoptics.com/fitsCap.pdf
Temperature control works well with the TOUPTEK ASCOM driver but not with the ZWO ASCOM driver.
1) Temperature is set immediately for TOUPTEK, but not for ZWO if the step is large, when it fails silently.
2) Temperature is maintained for TOUPTEK when the ASCOM routine exits, but the ZWO camera immediately warms up.
My questions to ZWO support are routed through a US astronomer, so I'm not even sure ZWO understands these (longstanding) "features" of their ASCOM driver. Amusingly I sell these cameras back to China as part of a scientific instrument, and have no problem communicating with them, even in Chinese (thanks to AI).
ASCOM temperature control with ZWO and TOUPTEK cameras
-
admin
- Site Admin
- Posts: 17558
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ASCOM temperature control with ZWO and TOUPTEK cameras
Hi,
I must admit that I really don't use ASCOM drivers for cameras if I can avoid it, but it would be weird that the temperature control is not the same as using the SDK in SharpCap - the ZWO SDK has a method to set the target cooler temperature. That is presumably sent to the camera and then the camera takes care of the cooling control (at least I assume it works that way - maybe the SDK controls the power level). Anyway, you would expect the ASCOM driver just to do the same thing - if an application sets the cooler target temperature then pass that on via the SDK to the camera...
The only things I can think of that would be expected to have an impact is that ASCOM also has a 'CoolerOn' setting - if that is not set then in theory the cooler should not activate on the camera, but it wouldn't be impossible for some drivers to see the target temperature being set and treat that as an implied 'CoolerOn'. Therefore if somehow the cooleron is not being toggled, that might be the issue.
Finally, worth checking the version of the ZWO SDK (ASICamera2.dll) that comes with their ASCOM driver. If you are using SharpCap then the best thing is to have a version of the ASCOM driver with the same ZWO SDK version as SharpCap uses. That's because SharpCap's version of ASICamera2.dll gets loaded during the initial camera detection at startup, and then the ASCOM driver ends up using SharpCap's version (whether it has a different version or not - Windows doesn't allow two DLLs with the same name to be loaded into the same process).
cheers,
Robin
I must admit that I really don't use ASCOM drivers for cameras if I can avoid it, but it would be weird that the temperature control is not the same as using the SDK in SharpCap - the ZWO SDK has a method to set the target cooler temperature. That is presumably sent to the camera and then the camera takes care of the cooling control (at least I assume it works that way - maybe the SDK controls the power level). Anyway, you would expect the ASCOM driver just to do the same thing - if an application sets the cooler target temperature then pass that on via the SDK to the camera...
The only things I can think of that would be expected to have an impact is that ASCOM also has a 'CoolerOn' setting - if that is not set then in theory the cooler should not activate on the camera, but it wouldn't be impossible for some drivers to see the target temperature being set and treat that as an implied 'CoolerOn'. Therefore if somehow the cooleron is not being toggled, that might be the issue.
Finally, worth checking the version of the ZWO SDK (ASICamera2.dll) that comes with their ASCOM driver. If you are using SharpCap then the best thing is to have a version of the ASCOM driver with the same ZWO SDK version as SharpCap uses. That's because SharpCap's version of ASICamera2.dll gets loaded during the initial camera detection at startup, and then the ASCOM driver ends up using SharpCap's version (whether it has a different version or not - Windows doesn't allow two DLLs with the same name to be loaded into the same process).
cheers,
Robin
Re: ASCOM temperature control with ZWO and TOUPTEK cameras
Thanks Robin. I should have said that ASCOM control works in SharpCap - the camera is cooled (slowly) and stays cold while collecting multiple frames, probably because the ASCOM driver is continually engaged. My problem is probably because I exit the driver before the temperature is finally set. I call the ASCOM FITS.dll to set the temperature and acquisition time, but don't wait for it to finish, only checking cyclically for the image file and temperature. That works fine for the exposure, but doesn't work for setting the temperature. Yes, the ASCOM camera dialogue has a "cooler on" switch that I set on. It's just that the ZWO driver forgets about the temperature request as soon as it exits, but does remember to collect the image.
With TOUPTEK cameras, I can set both the exposure and temperature, then exit, and both the exposure and temperature are executed. Perhaps it's because of the fussy way ZWO sets the temperature in steps. TOUPTEK just goes ahead and sets whatever temperature is requested (much faster) and then maintains it.
And I quite like the ASCOM idea of defining a standard set of commands for different cameras. I understand that all of the special features of a particular camera can't then be accessed, but ZWO's special feature of stepping temperature control should be handled by the camera firmware, not the end user.
I tried contacting ZWO support but never got past an amateur astronomer in the US - while I communicate with my own clients in China in real time. I think ZWO are focussed on amateur users, while TOUPTEK support a range of professional cameras apart from astronomy.
With TOUPTEK cameras, I can set both the exposure and temperature, then exit, and both the exposure and temperature are executed. Perhaps it's because of the fussy way ZWO sets the temperature in steps. TOUPTEK just goes ahead and sets whatever temperature is requested (much faster) and then maintains it.
And I quite like the ASCOM idea of defining a standard set of commands for different cameras. I understand that all of the special features of a particular camera can't then be accessed, but ZWO's special feature of stepping temperature control should be handled by the camera firmware, not the end user.
I tried contacting ZWO support but never got past an amateur astronomer in the US - while I communicate with my own clients in China in real time. I think ZWO are focussed on amateur users, while TOUPTEK support a range of professional cameras apart from astronomy.
-
admin
- Site Admin
- Posts: 17558
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ASCOM temperature control with ZWO and TOUPTEK cameras
Hi,
I think that your analysis of the market position of the companies is probably correct - ZWO have always largely targeted amateur astronomers, and now a lot of their focus is on the smart telescope market (shifting more towards 'casual' astronomy consumers). ToupTek actually have a background in cameras for industry and science, so they definitely bring some of that background into their astronomy product line.
cheers,
Robin
I think that your analysis of the market position of the companies is probably correct - ZWO have always largely targeted amateur astronomers, and now a lot of their focus is on the smart telescope market (shifting more towards 'casual' astronomy consumers). ToupTek actually have a background in cameras for industry and science, so they definitely bring some of that background into their astronomy product line.
cheers,
Robin