Mount Control - Property read Tracking is not implemented in this driver

[andyofastro]

I have an Eq5 mount controlled by:
https://astro-gadget.net/gadgets/contro ... ledreameq5
The Simpledreameq5 is then controlled by a Guide Dream:
https://astro-gadget.net/gadgets/astrop ... dedreamst4
It is superb for lunar and planetary imaging.

I use the guidedream ascom driver to control the mount in Cannot move mount because: Property read Tracking is not implemented in this driver from Sharpcap.

I am getting the following message: Cannot move mount because: Property read Tracking is not implemented in this driver.

I click OK and it vanishes and then I can control the mount again for a few moments until it appears again. I have a work around, I use APT or Nina to do mount control, because the message does not appear in those programmes.

I then use Sharpcap for video capture. It would be nice to just use Sharpcap interface if this is possible.
I know the driver is a little old, however it does work in APT, Nina and PHD2. The supplier is/was Ukraine based and I wouldn't dream on messaging them at this time and I want to support the use of their products.

Is there any way of ignoring this message or telling Sharpcap to ignore this message from the driver - it is literally just RA and DEC control to centre planets or surface lunar details. Many thanks.

[admin]

Hi,

so the best solution here would be to see if the people who make that kit can update their ASCOM driver, since by not implementing the tracking property, they have missed out one of the *required* parts of the ASCOM telescope control system. If you were going to contact them, you could point them to this web page, which makes it clear that they need to implement the tracking property - https://ascom-standards.org/Help/Platfo ... acking.htm . They could even run the automatic conformance check that ASCOM make available on their driver which would have found this error and any other errors they have made - https://ascom-standards.org/COMDevelope ... rmance.htm

Anyway, I know it is sometimes hard to get people to update things, so I will also try to put in some code in SharpCap to ignore the missing implementation of Tracking so that you can control your mount. I think I will make it assume that the tracking rate is sidereal if the ASCOM driver gives an error.

cheers,

Robin

[andyofastro]

Thanks Robin. The Dream guide generates an ST4 output to the mount controller, therefore I'm not sure how the feed back for tracking rate would function. Thank you for looking at the code. Regards Andy