-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Blogs
Posts posted by AdrianVarga
-
-
On 18/08/2009 at 11:09, Macavity said:
Sadly, I suspect any plaudits may have been premature...
I left the mount - with my MAK127 attached, overnight, and, this morning, it was "back to it's old tricks". From a cold start the motor again struggled. But, having traversed a region of track, it then moved fairly freely!
I sense I might be barking (meowing) up the right tree but, as yet, have not "cracked it". Perhaps the lottery of (distributor) substitution will get you a "better" example of this mount? For braver souls, removal of the Silver plastic cover reveals:
The above show the NUT you have to remove. Observe and maintain the correct ordering of metal, plastic and compression/split washers! The gear housing has to be "jiggled" to remove (and replace) it. This (presumably) to mesh-unmesh the large gear with the final drive pinion... You then have TWO parts to the assembly:
The Main Mount arm, with the gear housing removed. Here we see the THREE circular "plastic" Pads which form the bearing surface, against the LARGE gear (below)...
The large Gear Housing. This shows the internal face of the Gear, after a few passes over full Altitude range. You can see how the "Plastic" Pads have swept a track clear of excess(?) grease - Or maybe sufficient lubrication?
At THIS point, I'm not really sure how to proceed. I sense(!) I may be "right" re. the nature of the problems in this example of the mount. Clearly, by running the mount for a while "things improve", but this hardly inspires confidence! I must admit I'm a bit disappointed with the whole thing - despite initial promise and GOOD tracking etc.
Maybe a "better" grease would remain(!) between the Pads and the metal surface? Any Experts in lubrication (Tribologists?) out there? Thoughts / Speculation / Inspiration welcome!
Is there a spare part for someone?
Help - SynScan AZ GOTO Problem
in Discussions - Mounts
Posted
Hi
I had such a problem too. I solved the problem by updating the motor motherboard firmware. (Only now is the error different for me at the moment, unfortunately i have not found a solution)