Hi guys. I'm looking for some ideas on what could have happened here. I know there are several servo experts around here and I'm hoping I can get a little welcomed feedback. Richard R. You always seem to have good solid knowledge with servos. I'd welcome your comments if willing.
I had a servo burn up a couple days ago. It's not an EZ Robot servo but a Hitec HS-85MG servo being controlled through EZ Builder. I'm not powering it through the EZB. It's being powered directly (past the EZB) from a 12vdc to 6vdc converter. I have one other servo sharing this power converter and it's also controlled through EZ Builder.
Here's what was going on when the HS-85MG overheated and smoked; I had not yet initialized or sent any signal to the soon to be smoked HS-85MG through EZ Builder however it was powered up from the converter. I had the other servo sharing this converter holding a position set from EZ Builder. I had a third servo moving up and down using a servo control slider in EZ Builder. This third servo is powered by a different step down converter (at 7vdc) and also bypassed around the EZB. Both the step down converters that powers these three servos share the same 12vdc feed.
As I moved the third servo powered by a different converter, the HS-85MG that was not yet initialized or had a movement command sent overheated, started smoking and was destroyed.
I can't figure out why if the HS-85MG had not yet been started (but powered up from a shared converter) would lock up and burn when a separate servo was moving.
I've noticed at other times with other servos, if I haven't initialized and then released them in the INT script, sometimes they tend to twitch when other servos move. However I've never had any of them lock up and burn like this.
Any ideas on what could have happened here and how to avoid this in the future are very welcomed. *confused*