[Bomberofdoom]

Originally Posted by Greg McKaskle

I'm most familiar with the LV code, so that is what I'll describe. The same stuff is often happening in the C++ example code too.

The servo control VI has proportional constants on its panel. I believe the LV ones are a dividing proportion, so smaller number will lead to bigger delta per pixel away from center. I'd keep the robot still, on blocks or unplugged in order to isolate the servos. Then decide on a repeatable movement, perhaps automated, perhaps approximated by a distance and tempo.

Lower the proportion number and you should see the servo speed up with small changes, and then become unstable as the servo overshoots and starts a feedback. The other thing you can do to speed it up is to turn off the smoothing, and perhaps the deadband. The smoothing will introduce a small lag, and the deadband will allow a small uncorrected error, but I wouldn't expect either the slow the servo. On the other hand, doesn't take long to test.

Beyond that, it is a function of the servo HW.

Greg McKaskle

Could you explain more specificly how to do those changes in the VI (searched for "Servo Control.vi", but realized it was "Set Position.VI")? Some images of the explanation would really help.
Plus, how diffrent is Set Position.vi compared to the servo control loop in the Two Color Servo Camera Example?

Thanks.