Replies: 1 comment 1 reply
-
|
Hi @Zog47, This isn't something I've experienced although I have ST servos from mixed manufacturers in my Cody build so I doubt you've done any permanent damage. It sounds like your issue is better suited to the FeeTech support team or community as it isn't related to this build. I should also mention that the current release of this project doesn't use ST servos so you're deviating from the supported build there and we won't be able to support issues you experience. Not to discourage you at all, just managing expectations. Having said all that, There is a module for controlling both ST and SC servos now in develop, so feel free to try that out if it helps. https://github.com/makerforgetech/modular-biped/blob/develop/docs/BusServo.md It isn't released officially yet so expect some issues. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
So long story short i was originally using the FE-UART-1 to assign ID's then added ESP32 WROOM-DA it was going well until i was having trouble fitting all my components into the body then I seen people were using the waveshare boards and the size of the waveshare serial bus adapter(A) seemed like it would be an upgrade I also ordered a ESP32-s3-zero. when I switch to these to control my FeeTech STS3215 servos I had all kind of trouble never even got the servos to move then I attempted to switch back and know I have no response from servos and the IDs numbers are correct but the names are weird symbols Ive tried everything I could come up with there is very little information online i was able to find I even tried to update the firmware on one servo and that one does not even turn on now(no red light when powered)? Does any one have any idea what I did and Maybe possible way to fix it it or did i brick my servos? Please Help?!

Beta Was this translation helpful? Give feedback.
All reactions