Asi camera driver

hansheiser

Hi,

using any Zwo camera with ascom driver the model of the camera is not shown, the host program (i.e. APT) shows 'connected to Asi camera (2)'.

This behaviour is frustrating, as I am guiding and imaging with two different Zwo cameras and it is not clear two which camera I'm currently connected.

I am using latest drivers. Am I missing something?

Regrads, hansheiser

james_screech

I have another related issue if using two cameras via ASCOM. I have a 1600MM-C and 120MM but both ASCOM drivers keep defaulting to the 1600MM-C every time the computer starts. If the two drivers would connect to a different camera and give its type that would be great.

James

hansheiser

Hi James,

if you are using the 120mm for guiding via PHD you can store your profile. Doing this the connection will be made to the 120mm at any new start of PHD.

Using PHD you must not use the Asi ascom driver as PHD has native support for the camera and also you can use Windows WDM (web camera) driver. This belongs to the 120mc which I use, I don't know for sure about the mono version.

Excuse my bad English !

Hannes

james_screech

I found that using the native support in PHD was less stable than the ASCOM driver. Also the USB band width cannot be controlled, which I need to drop down to 40% as I'm using it through the USB hub on my ASI1600MM-C. All in all I've found using the two ASCOM drivers the most stable way to run two cameras. The only problem is you can never be sure which camera is on which driver until you connect them and I usually get the ASI1600MM-C on both drivers for some reason.

James

hansheiser

I have not recognized any performance issue on my system yet (old pentium machine). When the Asi 120mc is connected via WDM driver then inside PHD I have three controllers in the camera panel for usb traffic, gain and offset. As gain and offset work flawlessly I guessed that usb traffic control (which is at 80 percent default) would also do that. I have not tested if it really does because no problems so far.

I think there is no problem for Zwo to change the driver to display the camera model name when using ascom driver so I hope a developer can confim that.

Regards, hansheiser

Sam@ZWO

you need press "shift" key to select ASCOM camera under APT

otherwise it connect by default

james_screech

I have APT set to ASI (1) ASCOM driver and that always selects the 1600MM-C (as I want). I have PHD2 set to ASI (2) ASCOM driver and this also by default connects to the 1600MM-C camera. Shouldn't one ASCOM driver default to the 120MM camera as there is no point in using the same camera on both drivers.

I always connect APT to the camera first (to start cooling) and then start PHD2 and connect some time later.

James

Sam@ZWO

james_screech wrote:
I have APT set to ASI (1) ASCOM driver and that always selects the 1600MM-C (as I want). I have PHD2 set to ASI (2) ASCOM driver and this also by default connects to the 1600MM-C camera. Shouldn't one ASCOM driver default to the 120MM camera as there is no point in using the same camera on both drivers.

I always connect APT to the camera first (to start cooling) and then start PHD2 and connect some time later.

James

Hi James

the 2 ASCOM driver is the same and it always pick up the first camera

it doesnot matter it select which camera by default because you can change it

james_screech

Sam wrote:
james_screech wrote:I have APT set to ASI (1) ASCOM driver and that always selects the 1600MM-C (as I want). I have PHD2 set to ASI (2) ASCOM driver and this also by default connects to the 1600MM-C camera. Shouldn't one ASCOM driver default to the 120MM camera as there is no point in using the same camera on both drivers.

I always connect APT to the camera first (to start cooling) and then start PHD2 and connect some time later.

James

Hi James

the 2 ASCOM driver is the same and it always pick up the first camera

it doesnot matter it select which camera by default because you can change it

Wouldn't it be better if driver 1 defaulted to the first camera and driver 2 to the second? No one would ever want to use the same camera from both drivers (I wonder what would happen if two applications tried taking images with the same camera at the same time).

Or better still the two drivers should remember the camera they were connected to from the last session and default to that.

Yes you can change the camera connected to each driver but its an extra step that is easily forgotten, especially when imaging / guiding software comes back and tells you that it has connected to a camera.

James

hansheiser

Isn't it possible to change the driver to read out and echo something like "Zwo Asi 1600mmc" ? Other manufacturers also do it that way.

hansheiser

Sam@ZWO

Hi James

actually our ASCOM driver can remember which camera you selected

you can disconnect and connect again and don't need to choose again

but there is a display problem if you call out the setup dialog and it only show the first one

we will change it in our next version software

hxpi

I have the same issue using ASI Driver 1 for ASI1600MM-C in SGP and ASI Driver 2 for ASI174MM in PHD2. I always have to go into the settings and select the correct camera or PHD2 will connect to the wrong camera! The other settings appear to be correct.

It would be really nice if the driver could be changed to support displaying and retaining the correct camera it is assigned to. It is frustrating and confusing when the two ASI ASCOM drivers do not retain assignment to separate cameras, which is the whole point of having two drivers in the first place!

Thanks Sam for addressing this.

Ciao,

Mel

Sam@ZWO

please try this new driver

ASICamera ASCOM Setup V1.0.2.27.zip