|
|
|
 If you're not trying to make the best possible product given your set of constraints and resources I'm not quite sure what you're doing. - Aren_Hill [more] |
 |
|
|||||||
|
||||||||
 |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| If you're not trying to make the best possible product given your set of constraints and resources I'm not quite sure what you're doing. - Aren_Hill [more] |
|
|
|||||||
|
||||||||
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#2
02-12-2014, 19:05
|
||||
|
||||
|
Re: [FTC]: Continous Servos
255 is full power in one direction, 0 is full power in the other direction. Somewhere around 127 is stopped. 127 is supposed to be stopped, but we recently found that some of our servos stopped with a setting around 133.
In other words: servo[myContinuousServo]=255; // full power one way servo[myContinuousServo]=0; // full power the other way servo[myContinuousServo]=127; // stopped. might be a different # close to 127 Also make sure that you've configured the servos as Continuous Servos in the Motors and Sensors Setup. BTW, a cheatsheet for RobotC teleop programming is available here. Last edited by wgardner : 02-12-2014 at 19:13. 
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Hybrid Mode
