Hi Robin
Seems I have another issue when connected to my RST-135 mount.
SC pro v 4.1.11351 64 bit
Trying to jog at the Slow speed RATE .27 , SC is throwing an exception.(Did not do this in the past, but not sure how many updates ago)
The 0.6 and 6.2 Rates do work OK.
attached is the zipped bug report file.
Thanks
Steve
Error with RST-135 Slow Rate
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
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
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Error with RST-135 Slow Rate
- Attachments
- admin
- Site Admin
- Posts: 13344
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Error with RST-135 Slow Rate
Hi Steve,
I think we looked at this one before and didn't resolve it. I do seem to recall adding logging to check things more carefully if it happens again, and the current log contains that info.
From the log it looks like the ASCOM driver is wrongly rejecting a movement rate that it has advertised as being available...
You can see that the 0.26666666666666 value being rejected is identical to the one reported as available.
I really hope that the ASCOM driver is still being maintained for your telescope, since it seems that it needs some work in more than one place
cheers,
Robin
I think we looked at this one before and didn't resolve it. I do seem to recall adding logging to check things more carefully if it happens again, and the current log contains that info.
From the log it looks like the ASCOM driver is wrongly rejecting a movement rate that it has advertised as being available...
Code: Select all
Info 15:06:16.425558 #1 Axis 0 has 3 slew rates. in Tuple<double, double>[] SharpCap.MountProxy.ASCOM.MountWrapper.GetSlewRatesViaIndexing(int axis)
Info 15:06:16.428158 #1 Slew rates are : 0.6-0.6, 0.26666666666666666-0.26666666666666666, 6.25-6.25 in Tuple<double, double>[] SharpCap.MountProxy.ASCOM.MountWrapper.GetSlewRatesViaIndexing(int axis)
Info 15:06:16.448360 #1 Axis 1 has 3 slew rates. in Tuple<double, double>[] SharpCap.MountProxy.ASCOM.MountWrapper.GetSlewRatesViaIndexing(int axis)
Info 15:06:16.448519 #1 Slew rates are : 0.6-0.6, 0.26666666666666666-0.26666666666666666, 6.25-6.25
...
Warning 15:06:56.133616 #1 Error from MoveAxis attempt with parameters Secondary, 0.26666666666666666 : Exception of type 'InvalidValueException' : unspecified
I really hope that the ASCOM driver is still being maintained for your telescope, since it seems that it needs some work in more than one place
cheers,
Robin