Activation of QHYCFW3 in V3.2.6054 and 6051

Post Reply
Zenzanon
Posts: 12
Joined: Fri Jun 07, 2019 6:30 pm

Activation of QHYCFW3 in V3.2.6054 and 6051

Post by Zenzanon » Thu Jun 27, 2019 2:25 am

I'v noticed in these two versions, it is no longer possible to use my QHYCFW3. In the past it would connect, but now it throws this. The wheel is connected via the 4 pin cable and works well with other apps.

Thanks!
Attachments
Capture1.JPG
Capture1.JPG (47.77 KiB) Viewed 102 times

User avatar
admin
Site Admin
Posts: 2735
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Activation of QHYCFW3 in V3.2.6054 and 6051

Post by admin » Thu Jun 27, 2019 9:17 pm

Hi,

It looks like you're using the sort of filter wheel that connects via the qhy camera. If that's the case then the best option is not to use the Ascom driver (set the option for filter wheel to none in the hardware settings). SharpCap should autodetect that the filter wheel is connected via the camera when you connect to the camera and everything should work that way.

Another option may be to uncheck the tick box that says connect devices at start-up in the hardware settings and then trying to connect to the Ascom filter wheel after the cameras running. As far as I understand the Ascom driver can only talk to the filter wheel if the cameras already connected.

Hope this helps, Robin

Zenzanon
Posts: 12
Joined: Fri Jun 07, 2019 6:30 pm

Re: Activation of QHYCFW3 in V3.2.6054 and 6051

Post by Zenzanon » Sun Jul 07, 2019 11:30 pm

Sorry Robin, but nothing works! I tried using your suggestion of letting the wheel be autodetected, which it is, but a change of position throws an index out of range error. I can't use ASCOM, because I have to use the 183m ASCOM driver too (it's mutually exclusive both the camera AND the wheel have to use ASCOM, not only one). Like I said it used to work, but now it's very rare that it works at all, most of the time it just throws. I know the ASCOM drivers is bad, I mean it works, but enumerates 38 filter positions instead of 7. QHY knows about it but has not issued a fix. But, ASCOM works none the less. The index out of range issue makes me wonder if it's also affecting the native drivers too now.

Thanks!

-John

User avatar
admin
Site Admin
Posts: 2735
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Activation of QHYCFW3 in V3.2.6054 and 6051

Post by admin » Mon Jul 08, 2019 7:24 pm

Okay, thanks for the update. I will take a look at my qhy wheel and see if I see a similar problem.

Cheers, Robin

User avatar
admin
Site Admin
Posts: 2735
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Activation of QHYCFW3 in V3.2.6054 and 6051

Post by admin » Thu Jul 11, 2019 8:10 pm

Hi,

I tested this and sometimes the QHY wheel seems to report it is in position 31. I have changed the code to re-request the position after a short delay if this value is encountered and that seems to fix the problem for me. This change is in the very latest version available from the download page.

Thanks

Robin

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests