New Feature : Support for ASCOM Cover/Calibrator devices

All the latest news about new features and improvements to SharpCap
sonata31
Posts: 72
Joined: Wed May 05, 2021 3:51 pm

Re: New Feature : Support for ASCOM Cover/Calibrator devices

#11

Post by sonata31 »

Hello Robin
I couldn't find a log file or a way to create one.
Louis
Monture : Rainbow Astro RST135E
Lunette : Takahashi FSQ106EDX4 + PegasusAstro FocusCube
Alnitak Flip-Flat
Caméra : ZWO ASI533MC + EFW
PC : PrimaLuceLab EAGLE4 PRO
Logiciels : SharpCap, ASTAP, PHD2, NINA, Stellarium, Skychart, Astroplanner
User avatar
admin
Site Admin
Posts: 13529
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Support for ASCOM Cover/Calibrator devices

#12

Post by admin »

Hi,

OK, no worries. What happens if you just tell it to ignore the error? Does it do what you want? That would indicate that I can make SharpCap treat the error as less serious and perhaps get it working.

cheers,

Robin
sonata31
Posts: 72
Joined: Wed May 05, 2021 3:51 pm

Re: New Feature : Support for ASCOM Cover/Calibrator devices

#13

Post by sonata31 »

Hello Robin
I still have the problem
However with NINA it works perfectly
Louis
Monture : Rainbow Astro RST135E
Lunette : Takahashi FSQ106EDX4 + PegasusAstro FocusCube
Alnitak Flip-Flat
Caméra : ZWO ASI533MC + EFW
PC : PrimaLuceLab EAGLE4 PRO
Logiciels : SharpCap, ASTAP, PHD2, NINA, Stellarium, Skychart, Astroplanner
User avatar
admin
Site Admin
Posts: 13529
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Support for ASCOM Cover/Calibrator devices

#14

Post by admin »

Hi Louis,

I have seen a couple of uploaded bug reports that might have been you - they match your description that the cover has reported an error state. Those reports were from SharpCap 4.1.12128.

The newer version - 4.1.12174 will still report the error state to the user, but no longer makes it a 'report the error and close SharpCap' issue. I have also put extra logging in to record changes of state, so if you can make it happen with the newer version and send me a log, I can track the history of how the cover and calibrator states have changed. It would be interesting to see what happens if you ignore the error state and let it carry on - does the state go back to a normal 'open' or 'closed' state, or does it stay stuck in error.

I can't hide the fact that the device has reported an error state from the user - even if the error state is perhaps an incorrect report - if I do that then people would not get notified if their device really reported an error.

cheers,

Robin
Post Reply