Imager cam is ASI6200mm, guider cam is ASI1600mm, both running the native driver. I started trying to use an ONAG with Skyguard for guiding and focusing. Skyguard uses ASCOM drivers. The imager cam can be included in the instrument list in Skyguard, mostly for documentation, as the info about it isn't used in any Skyguard process. When I first started imaging with this setup, it would acquire 2-3 normal images in Sharpcap, then all following images would have the top of the image cut off. I played around with an Optec server arrangement, and got some better results with the Skyguard software, but the main images were still cut off. I finally gave up, and removed the imager cam from the Skyguard instrument list, and everything
now works just fine. Is there a way around the drivers fighting with each other? Or is it just another given?
ZWO driver conflict
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
-
Ray Hansen
- Posts: 39
- Joined: Sun Jun 11, 2017 5:54 am
- Location: Scottsdale Arizona
-
admin
- Site Admin
- Posts: 17496
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: ZWO driver conflict
Hi Ray,
having the same camera open in two pieces of software at once isn't supported - as you have noticed the two pieces of software tend to fight with each other over control of the device with unpredictable results.
In my view, the way this should work is that the camera should fail to open with an error if something else is already using it, but unfortunately that's a thing that would need to be implemented in the camera SDKs rather than in SharpCap, so I just have to live with how it works at the moment.
cheers,
Robin
having the same camera open in two pieces of software at once isn't supported - as you have noticed the two pieces of software tend to fight with each other over control of the device with unpredictable results.
In my view, the way this should work is that the camera should fail to open with an error if something else is already using it, but unfortunately that's a thing that would need to be implemented in the camera SDKs rather than in SharpCap, so I just have to live with how it works at the moment.
cheers,
Robin