detach() Command Question

Hello to everyone.I have a standard servo(MG995) and i have a question.The detach() command hold the position of the servo?Thanks in advance i am newbie.

Basically i want the servo to hold the position when i want it.I want to work like this (- YouTube) with mit app inventor that i have created.Thanks in advance

I can't be bothered following up links and watching videos.

The detach() command hold the position of the servo?

In short the answer is no. If you call 'servo.detach()', the servo will no longer actively hold it's position. (It would have been easier to experiment than to post the question, you know. ;) )

Thanks in advance i am newbie.

After 99 posts over a period of 11 months, you shouldn't be too much of a newbie.

This 'scope trace shows how an attach()-ed servo receives its “reminder” every 20ms. (This is a 1.5ms pulse, ie 90 degrees, but whatever the angle is, it gets a repeat.) When you detach() the servo, the reminder pulse is no longer sent, so unless the servo has some kind of “memory” (which I suppose is not impossible) it will not hold its position since it doesn’t know where it should be.

As suggested, why not just test it?

servo attached.jpg

But if the servo isn't under much load it will just stay in it's position. For example, I detach servos that drive model railroad turnouts and signals. The friction of the gearbox is more then enough to keep it in it's position.

septillion: But if the servo isn't under much load it will just stay in it's position. For example, I detach servos that drive model railroad turnouts and signals. The friction of the gearbox is more then enough to keep it in it's position.

Yep. It takes a little effort to move them, but they can move. That's why I used the word "actively":-

If you call 'servo.detach()', the servo will no longer actively hold it's position.

But maybe I should have gone into more detail. Thanks for clarifying.

septillion: The friction of the gearbox is more then enough to keep it in it's [sic] position.

That's what I meant by memory.

(Not it's not :) but it could have been.... "mechanical memory")

Yeah I know. But just to make it clear to the TS :slight_smile: