Hi Roberto,
just to be very short i answer you for point:
- ASI and QHY have only one SDK and not more SDK for every cameras
- Voyager use ASCOM or SDK
- SDK call is equal for all camera and no distinction is possible
- Voyager do not have in his installation any beta driver and will never have
- the camera you talk (and the sensor) seems to be in beta and need for sure BETA drivers
- If you want to use beta camera driver you must update it on Voyager installation folder
- in the latest daily build I separate the SDK dll from root directory of Voyager installation folder to help who want use beta driver
- QHY on more that ASI have problem on drivers having called the SDK dll with the same name of DLL used for ASCOM, this mean the first DLL (and for sure his version) you load will remain in memory until you close all reference (others application also opening it). This cause strange behavior to who change ASCOM to Native more times or use QHY from more than one application vendor. QHY engineers reached me directly and I suggest them solution for this.
- for each information about driver and DLL you must refer to ASI and QHY directly, they release driver to fix problems with this cameras so frequently
- this is link to ASI driver page (look for driver and also for SDK tab update) https://astronomy-imaging-camera.com/software-drivers
- this is link to QHY driver page (look for driver and SDK also for this) https://www.qhyccd.com/download.html
- ASI version of your camera have problem with bin>1 and ROI, they have fixed in ASCOM but not in SDK at today
- I purchased few days ago at my cost a new ASI294MMPro for testing and help
- Voyager for any of problems reported here or in public forum is at now not responsible, we use only SDK and their methods, but if you think there is some problem with Voyager and to Voyager inputable please use support channels and not this forum
- finally thanks to QHY and ASI Engineers for their support to me and Voyager development
All the best and happy new year
Leonardo