after I added the third servo in the al5d the base servo went to center position at 1000 instead of 1500. I made
no mechanical changes other than adding the forearm. The shoulder servo did not lose its calibration. The elbow servo
seems to work fine. Is there a s/w fix to re-center the base servo? I am using the SSC-32U usb interface software.
If the servo seems to have moved without any changes, the easiest thing to do is send a 1500us command to center the servo, unscrew the horn and flex the bracket (with the horn still attached) outward, re-position it to the correct 90 degree angle, then re-attache and offset a few degrees in the software (SSC-32U sequencer for example) as needed.
when I click 1500 on servo 0 the servo centers about 70 degrees off the front to back line that the assembly instructions explain to line the base servo on. Is there anything I can do other than unattach the base and rotate the base housing the servo 0 70 degrees?
If this is the case, you need to unscrew the horn, remove it and re-position it.
I am also having trouble with the base top tipping off of contact with the bearings. Does this mean the horn screw is not tight enough holding the base top, or is the base top not setting deep enough on the servo horn splines?
When assembling the base, you need to re-attach the screw which was removed when you removed the white horn. It’s what keeps the top of the base rotate connected to the servo.
I took the 805BB servo off completely and removed the base top. Where the base top attaches to the 485HB servo looks really chewed up. Can I purchase a new base top as a separate item?
Normally the 485’s output spline meshes with the internal spine of the base rotate top and the two should not wear against each other.
The top can be purchased as a special order - please contact us at [email protected] and request a quote for RB-Tib-03.
You can also provide a link to this topic.
thank you for your info. I took the 805bb servo off and tightened the screw holding the base onto the 485 servo and that seems to have been the problem.
Resolved?
