Thanks Jerry. To be clear, the mount does work. It has accuracy limitations that aren't out of line with its price, and as I say, if I'm shooting a single target an evening then as long as I look after centering every couple of hours I've managed a few nice shots. However I had hoped that with Stellarmate I could shoot 2 or 3 targets each evening which so far I just cannot do. Possibly Astroberry of some other computer solution would be better but I've never gotten the plate solver to work automatically with Stellarmate and the drift is way worse (FOR ME!!!) with Stellarmate than the SynScan phone app so I'm never up for much more than 4 hours a night - set it up, run 2 hours, recenter, run 2 hours, shut down.
I had hoped that, being a low cost mount, there'd be a few people anyway using it with the whole Ekos/Indi infrastructure but apparently not.
In the next month or so I'll start gearing up for next winter and clearer skies. Maybe I'll do better this year.
Hi Jasem
To be clear I’m using the Skywatcher Sky Discovery mount, using a different device drive (Skywatcher WiFi) not the GTi driver.
So the issue is in a common routine and the error message seems very straightforward .
I will produce a log today, but last time I tried to get a log I couldn’t find it.
Regards
Paul
Thanks for this but I’m an Astroberry user and only ever used the apt-get commands. If you can give me a set of commands I can run them.
I have worked in IT most of my life but very little exposure to Unix mainly IBM mainframe etc
Regards
Paul
Thanks I followed a previous link to this. I have built a new core using the cmake option. Just finishing breakfast will setup mount and send you the log
Paul
First I apologise for 'sticking my nose in' but the 0 value from microsteps per worm revolution is surely only required if there is some sort of PEC on the mount (highly unlikely for an Alt/Az)
So maybe not a major issue
Paul