Advice On Using Release() Command


I have a general question regarding the Release() script command. What I would like to do is to add this to some of my scripts after a Sleep() duration command to release some of my servos to save on any unnecessary servo holding strain and also to save on battery power.

But I read in a post somewhere recently (can't find the thread I saw it in at the moment) that using a "release" would cause the EZ-B to brown out and would need to be power cycled, or dis and reconnect the EZ-B's network connection, as this should only be used in an emergency.

I have tried it on a simple servo script to have a servo release at its rest position and it seemed to work ok. But before I go ahead and add more Release() commands to a lot more scripts, can anyone tell me if this would be ok to do, or would it not be advisable? Obviously a don't want to keep restarting the EZ-B every time a servo is released in a script.

Thanks. Smile


Release will not brown our the ez-b.

There is also the Release Control, which will release a servo after X amount of time since last move.

More information:


Thanks for the reply DJ. I thought as much, as I mentioned, I used it in a script and worked just fine (wish I could remember the thread I saw this in now). Just wanted to be sure before I added Release() to a load more scripts.

Also thanks for pointing me in the direction of the Auto Release control. I missed that one. *eyeroll*



@Steve... If anything the release() command will do the opposite of a "brown out"... The power needed to hold the servos is as the command indicates "released" leaving the battery with less of a load to contend with..

One thing about release... once you use it you will have to reset your servo speeds again or the servo(s) may not respond to any new commands...


Thanks Richard. Good to know. Smile


I just found the thread I read it on in post #10. It was something @thetechguru wrote talking about a servo control. I thought release on the servo control or via script was the same thing, so I guess not.


Clicking Release will stop sending position information to the servo. In general, you need to restart the EZ-B after a release for that servo to take commands again. Release is used as an "emergency stop" when you have gotten into a position that is straining a servo and risking burn out.

After re-reading the other thread, I see I used the term "brown out" to try and describe what I was talking about, which I now see was the wrong term. Apologies for that.

Thanks again.


It is possible I was wrong about needing to reset after releasing. Richard R indixates that maybe just restting the servo speed will get them working again. I need to experiment to see if that resolves the issue, but I do set all the speeds in my initialization script and I am fairly certain reconnecting or re-running the script was not sufficient to bring all the servos back to life.



Hmmm, I don't think @Alan believes that entirely now... Reading it however, I can see how it could be taken out of context a little... You don't need to restart your ezb, just reset your servo speeds... Any chance was this in a thread about an ezb3? It's true though, release can be used to save a would be smoking servo....


@Alan, next to "Panic Release" in the menu bar is the Reset Servo Speed option... That will get you back in business... Just wish there was a script command to reset servo speeds (Similar to the release(all) command )


@DJ... Could that be by any chance be a future script command? ResetServoSpeed(all) or something like that?