Winged Monkey Mech Motor Problem - can anyone offer advice? First, I apologize if I'm asking about an issue that this thread or another one on Pinside has covered before. Before posting, I searched for posts and topics that talk about my specific kind of monkey glitch, but I didn't find any. So here it is: my winged monkey motor seems to have become limited to only one direction of movement; it twists only in the direction needed to bring the monkey back up to the castle.
If the monkey is nested at the castle as default position, then when I turn on the machine, the monkey doesn't move at all. (Whereas usually at power-up the monkey should go halfway down and then back up again as a test, just like the house spins at power-up, as I imagine all of you see on your machines too.) And, if the monkey is nested at the castle, then it doesn't move at all during gameplay. (But interestingly if Dorothy is ready for capture and I hit the magnet, the game somehow thinks I actually captured the ball and brought it up to the castle, even though the monkey never moved.) Also, if, again, the monkey is nested at the castle, and I go into Device Test Mode, the monkey won't move at all. But the game can't tell - thinks the test is going fine - and there's no Error Log entry about it.
By contrast, if I manually wind the monkey downward to any degree first by hand, then (1) on power-up, the motor spins and the monkey returns to the castle; and (2) in Device Test Mode, the motor spins and the monkey will move toward the castle. But not in the other direction (toward the magnet) in either case.
As far as I can tell, both wires (black and red) are firmly connected to the motor.
And the rod is lubed. ("That's what she said.")
I'm on OS 6.06. Standard Model/Edition Game # 790/1000 built August 2015. Everything else seems to work fine, other than castle right-door problems (not asking about that here; know it's been discussed pretty thoroughly).
Maybe I just have to replace the motor? Any help would be much appreciated. Thanks in advance!
@ltg - I've opened a ticket with Support.