SharpCap Forums

HI Robin
Annoying but not fatal issue with connecting to Seestar S50.
I do not see this issue with the 3 other startup configurations/settings for my other scope setups.
running with SharpCapInstall-4.1.14064.0-64bit
Connecting to Seestar S50 with latest update
I have a startup file for SC to setup hardware for a S50.
"C:\Program Files\SharpCap 4.1 (64 bit)\SharpCap.exe" /instance 2
When I run SC, and look at the Sharpcap Settings , Hardware
All of the Hardware settings are NONE. (pretty sure this was also happening with previous SC version)
I do wait 10-20 secs after S50 Says READY before running SC.
I have set all the Hardware settings for the S50 properly and APPLIED them.
(I also Exported the settings, after this started happening)
Everything connects OK for that session.
When I exit SC and restart , the Hardware settings are again NONE.
I have to use the IMPORT Settings each time .
Am I missing a step to have SC remember the Hardware settings?
Are you seeing this.?

Update
I was just retrying SC connection to S50 and now it is remembering the Hardware .......
Not sure what is going on .
I will update if I see this issue any more.

Thanks
Steve

Hi Steve,

The hardware settings show up as 'None' when the thing they are set to doesn't get discovered when SharpCap asks for a list of Alpaca/ASCOM devices. Behind the scenes they are still set to whatever you left them at, but the hardware settings UI defaults to 'None'. If you don't try to change them and instead get SharpCap to detect the missing devices then all should be fine.

The trick I have found with the seestar is to choose the 'rescan remote hardware' option from the file menu after opening SharpCap. This tends to detect the Seestar even when the first scan at startup misses it. That's on my list of minor annoyances to look into, but I suspect it may be all down to how long the initial scan takes to find the Seestar. SharpCap sets a fairly tight time limit on that scanning to avoid slowing down the whole startup process for everyone (even those who have never used any Alpaca devices), and maybe it's just not getting the scanning/identification done in time.

cheers,

Robin