I have the following code:



The problem: the servo(contain) is set to 250 before I run this part of the code. However, when this starts, it begins rotating toward the 0 position and then it rotates back to the 250 position. This is very bad for us as we drop what we are holding. Any and all help is loved.

Thanks,

I think we need some of the other code... that function is not what is changing the servo as best as we can tell...

Yep, RobotC does that. No matter what position you initialize the servo, RobotC will reset it to 0 first. I don't know how to stop RobotC from doing that. You can do one of two things:
1. Remount your servo such that your default position is 0.
2. Load the batons after your code initializes it to 250.

Actually, RobotC seems to put the servos to 128 the first time any of them are positioned.

If you (in the initializerobot() function) set all the servos at the same time to the place you want them to be, it basically doesn't move them. Although the system sets them to 128 when it first runs, if you instantly set it to the desired location, it doesn't move them to 128 first.

We have a routine that sets the servo and at the same time stores that setpoint to a file (in the autonomous program). In the teleop program, during initialize(), we read that file and then set the servos to the same setpoint they were when the autonomous program stopped. They, thus, don't move.

Alan

That's interesting. Our code initialized all servos to their proper positions in initrobot but some of them still decided to move to different positions before coming back to the positions we set them. That's why we concluded RobotC firmware was doing it. You are probably right about it being 128 instead of 0. I don't remember which extreme it was that the firmware init them, but it was different from our intented position.