A robot is only as good as its ability to sense what's happening around it — and that depends directly on how motors, servos and sensors are configured and read.
Motors, servos and encodersLink to this section
Motors spin continuously, servos move to a specific position — understanding this difference avoids picking the wrong part for the wrong mechanism. Encoders, in turn, let the code know exactly how much a motor has already rotated, which is essential for precise movements.
- Configure motors and servos.
- Understand the difference between a motor and a servo.
- Learn about encoders and how they help control movement.
SensorsLink to this section
Each sensor exists to answer a specific question: a color sensor identifies objects, a distance sensor measures proximity, a gyroscope reports orientation. Choosing the right sensor depends directly on what that mechanism of the robot needs to know in order to work.
- Learn about the most common sensors in FTC.
- Understand what each sensor can report to the code.
- Choose the sensor based on what the robot needs to do.
Gamepad and telemetryLink to this section
Reading the controller's inputs is what translates the driver's touch into robot action. Telemetry, in turn, sends information back to the Driver Station — it's the main tool for understanding what the robot is “thinking” during testing.
- Read the controller's inputs.
- Send important information back to the Driver Station.
- Use telemetry to track what the robot is doing.