About the Spiral Search Direction

A place to report problems and bugs in SharpCap
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]
takuya_t
Posts: 50
Joined: Fri Apr 19, 2024 12:58 pm
Location: Aichi,Japan

Re: About the Spiral Search Direction

#11

Post by takuya_t »

Hi Robin,

I completely agree with both 1) and 2) you mentioned. So, I only reluctantly remove the Barlow lens when I can't find anything after searching. Another reason is that when focusing directly on Jupiter or Saturn, it's hard to tell where the perfect focus is, so if possible, I would like to first achieve precise focus using a Bahtinov mask on another star and then keep Jupiter or Saturn in view.

Regards,
Takuya
jamesjacob
Posts: 1
Joined: Sat Feb 21, 2026 11:02 am

Re: About the Spiral Search Direction

#12

Post by jamesjacob »

Hello, just checking in to see if any updates are planned for spiral search based on the discussions in this thread? I tried out spiral search on Jupiter the other day and experienced the same issue mentioned in the first message - the spiral kept going in the top left direction when Jupiter was in the bottom right.
User avatar
admin
Site Admin
Posts: 17510
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: About the Spiral Search Direction

#13

Post by admin »

Hi,

I'd like to improve it, but I suspect that will end up being very sensitive to the exact details of the mount/ASCOM driver in use. If you try to base the movement for a leg on 'movement time * mount speed' then you are prone to errors due to the time the mount takes to respond, get moving, stop, etc. On the other hand, if you try to work based on the co-ordinates then the update rate of the co-ordinates can be an issue - if the values SharpCap sees are always 0.5 or 1.0 or 1.5s out of date then things go wrong because of that :(

Thanks for re-flagging this for attention though - it's definitely not as good as it could be.

cheers,

Robin
Post Reply