SharpCap Forums

I just recently set up my new WarpAstron WD-17 mount. All seems to work fine except in certain situations when I want to park the mount.

If at the end of my nightly session, I use the park button in the mount control panel, the mount will go Home (I configured this in the HC) and turn off tracking. If I leave this button checked and then close SC and shut down the computer, then next time I get back into SC, the mount is locked in the park mode. Neither SC or the HC can unpark it. NINA seems to work fine with it, and I can use NINA to unpark the mount and all is well again. I've also noticed a similar issue when first opening SC and attempting to park the mount again (this is the easiest way that I've found to get the mount to go Home).

I've attached the log from when this last situation occurred.

Hi,

from the included log, I can see that the underlying error that SharpCap is getting when trying to park is this one
I would hazard a guess that internally the ASCOM driver implements 'Park' as a GOTO movement, and for some reason the GOTO is being rejected by the relevant code inside the driver.

ASCOM parking is pretty basic - applications like SharpCap can send two messages

1) Park to default parking position
2) Unpark

and also also one status - is the mount currently parked or not.

So it's odd that you get different results in NINA (presuming NINA is using the ASCOM driver rather than some direct support for the Onstep). It would be interesting to see the log of attempts to get the moutn to Unpark in SharpCap - maybe that records an interesting error or warning. Also I would suggest making sure that your ASCOM Platform installation (and SharpCap) are up to date.

cheers,

Robin

I did make sure to update ASCOM Platform, OnStep, Sharpcap and NINA.

I'm just learning this thing, and maybe its something I have done with the park configuration. I'll see if I can get the log when the mount is stuck in park.

Thanks.