Quote:
Originally Posted by wasyoungonce
Cheers Bren.
|
The issue was a fair bit more obscure than expected.
Replaced the battery (CMOS was resetting on every startup)
Geolocation was correct (In NINA, Stellarium and the Gemini computer)
Cables from RA/DEC were correct
Still - the issue remained...
I did some further digging, and it turns out that my mount has the McLennan gearboxes fitted, which reverse the motor rotation. This, combined with the fact that the Gemini.NET ASCOM driver didn't know that, was the cause of the issue.
Under the Gemini Options in the ASCOM driver, I changed the mount type to custom, modified the RA and DEC Worm to axis wheel ratio from 360:1 to -360 to 1 and boom. We slew and track in the correct direction.
The other thing I discovered, is that my mount has axis encoders, which I was using, however, they do not seem to do their job fantastically, so if I do a push to a target, the alignment goes off by a mile... I unchecked the 'Use Encoders' box in the ASCOM drivers, and that sorted out a lot of my pointing accuracy issues.
So, as a result, after a number of hurdles jumped through and a lot of testing, I got out under the sky last night for the first time in a decade, collected 3.3hrs of reasonable data and produced an image!
Couldn't be happier.
Thanks for all your suggestions, I did try them all!
The solution came from a member on the Gemini group on Groups.io, he basically read my post and said
Here's my assumption... Your mount is OLD, was originaly a 492 and later upgraded to gemini, and your motors have a gearbox on them that says McLennen. If those things are correct, put a - in front of the 360 in your drive ratios and the problem will be fixed.
He proceeded to email me about 30 documents about maintenance, gemini tweaking, mount upgrades/installation processes, guiding tweaking/fine tuning etc...
Amazing guy...
He did however mention you Bren, he gave me your email and said you're a top bloke and and would no doubt be able to resolve the issue!