Full reverse is usually 1.0 ms, but I suspect that was just a typo.fleet130 wrote:When driving servos, the speed/time curve translates directly into pulse width input to the servos. e.g. A 1.5ms pulse commands 0 speed, a 2ms pulse commands full speed, and a .5ms pulse commands full speed in reverse. (check the pulse widths are correct, I'm going strictly from memory). Acceleration is the rate of change (slope) of the pulse width.
Note: in unmodified servos, the input pulse width represents a position error. The servos drive to a position (rotation angle from center position) relative to the pulse width. Servos modified for continuous rotation use a fixed position signal equivalent to the center position. This makes the input pulse width a speed command rather than a displacement command.
How a servo reacts to modification to continuous rotation really depends on the controller, but most of the time it's a close approximation to a simple P (for proportional—the velocity response is linear to the error) controller. Most of the time they will actually hit full speed forward/reverse even if the error isn't yet equivalent to 500µs of displacement, so servos will probably most responsive to control than you would expect.
BTW, the Basic Stamp 2 in the BOE bot uses the PULSOUT command for servo control, which takes a 16-bit number as the number of TWO µs, if you're wondering why the program would have PULSOUT 750 instead of the 1500µs we're using here. The Vex system abstracts it more, and you just set motor speeds in a signed 8-bit number (-128–127).
I posted my EV's progress to the Image Gallery: 26/EV_foil_2009.png