ZWO ASI Native driver or ASCOM

I recently switched over to Voyager and love it. It’s super stable and I’ve already got things automated only after a few runs with multiple targets in one night.

  1. Any preferences to using the Native driver over ASCOM? In particular I’m using a 294MC.

I am using ASCOM for the 294MC imaging camera and the native driver for the ASI120mm mini for my guide cam in PHD2. I found this to be the most stable combo in APT and INDI. I was getting time out errors with the guide cam in PHD at one point, so I switched to that combo.

  1. Does anyone know if the offset value in ASCOM is the same for the native ZWO driver for this camera?


I always used the native driver with my ASI294MC (Recently sold) and do the same with my ASI2600MC and use the same gain and offset values as I did with the ASCOM driver and other software.

Hoi general question on the subject. Wat is normal the gain and offset you use for ASI1600MM Pro with EFW. My new baby have :wink:

and what adu do you define with that above’s settings in de flat sequences?


For the 294mc pro I use gain 120 and offset 30. 120 is unity gain and some type of noise algorithm kicks in there in the camera. For the 294 you shouldn’t use offset 0. Don’t know if that helps. . . .

1 Like

Regarding the ASI294MC is there a way to adjust white balance in Voyager with the Native driver?

I just want to make sure I have all the settings consistent before I make another dark library.

No white balance in Voyager, this is something reserved in processing for us.

All the best