Thank you for your reply.
Mapleleaf Have you tried disconnecting the ASI2600MC and seeing if PHD2 will connect to the ASI220m
Yes. I connected (by cable) only the ASI220 when I generated the new PHD2 profile.
Several times I tried to generate the new PHD2 profile with the direct camera driver ("ZWO ASI Camera") selecting "ASI220 mini", and finally found out the following behavior:
I am asked whether the new camera is already connected,
- when I click on 'yes', the pixel size (4 microns) is detected correctly, but the bit resolution is set to 8-bit, the 16-bit option is grayed out and no more selectable,
- when I click on 'no' and manually input the pixel size, I can select a bit resolution of 16.
ad 1.:
When I capture dark frames, the resulting dark library is a 8-bit file. This is evident from the Debug Logfile, and I verified it as well by loading the dark library in PixInsight. When looping, the camera generates images with a sampling of 8 bits. This is not appropriate for guiding.
ad 2.:
When I capture dark frames, the resulting dark library again is a 8-bit file! When looping, the camera now captures images in 16-bit (12-bit scaled to 16-bit). The camera generated images and star profiles that could be used for guiding. However, I don't understand how this combination could work, dark frames in 8-bit are not compatible with 16-bit images. Actually a dark frame subtraction executed in this way will achieve nothing.
So I conclude that this is a PHD2 issue: one cannot generate a dark library as 16-bit file.
Bernd