[Daniel_LaFleur]

Each of these solutions has things that you need to consider.

Originally Posted by meatmanek

There are a few solutions.

My preferred solution is to use a positional feedback sensor of some sort (potentiometer, encoder, etc) mounted to the arm, so the controller knows where the arm is, and then use a PID loop. This is the most complex in terms of programming, but if there's an easy way to mount your sensor it can be the easiest mechanically.

Some motors do not like to be run this way (specifically the banebots) as their cooling is attached to their drive shaft. Choose your motors wisely when doing this.

Originally Posted by meatmanek

The next solution would be to use a worm drive, or a motor that has worm drive built in. The Denso and Keyang window motors are all worm drive, and cannot be back-driven.

This is probably the best solution, however these motors tend to be less efficient and less powerful, so you may need to 'assist' them (depending on your application)

Originally Posted by meatmanek

The third solution, if you don't want to mess with tricky PID tuning or replacing a motor entirely in an arm, is a brake system.
Here is a picture of another team's brake mechanism:
http://www.chiefdelphi.com/forums/at...9&d=1172112278

This is a great way of doing things, but you must make sure that the brake can be released with weight on it and that the brake is released when you want to move the motor again (or else it will quickly stall)

Originally Posted by meatmanek

You may want to read this thread:
http://www.chiefdelphi.com/forums/sh...ighlight=brake
EDIT: Never mind, you've already posted on that thread.

Each of the above will work as long as you take the proper considerations into the design.