← Back to Resources

Robot Controller Setup

Step-by-step guide to setting up your FTC robot controller hardware and configuration.

Required Hardware

  • Control Hub - REV Robotics Control Hub or equivalent
  • Expansion Hub (optional) - For additional motor/servo ports
  • Motors & Servos - Connected via ports on the Control Hub
  • Sensors - Color sensors, distance sensors, touch sensors, etc.
  • Power Distribution - Battery, XT30 connectors, power switch
  • Wireless Connectivity - WiFi for driver station communication

Physical Connections

Motor Ports

The Control Hub has 4 motor ports (0-3). Connect your drivetrain and mechanism motors here.

Servo Ports

The Control Hub has 6 servo ports (0-5). Servos control mechanisms like claws, arms, and rotators.

Sensor Ports (I2C/Analog)

Connect digital and analog sensors using these ports for color detection, distance measurement, and more.

Power Connections

Connect your battery using the XT30 connector. Include a power switch between the battery and the hub.

Software Setup

  1. Install Android Studio on your computer
  2. Clone the FTC SDK repository from GitHub
  3. Connect to Control Hub via USB or WiFi
  4. Build and Deploy your OpMode code to the robot
  5. Configure Hardware in the FTC app

Hardware Configuration

The hardware configuration file maps your physical hardware to software variables:

Example Configuration:

In the FTC app, create a new configuration and add:

  • Motor 0: "left_motor"
  • Motor 1: "right_motor"
  • Servo 0: "arm_servo"
  • Sensor (Color): "color_sensor"

Testing & Troubleshooting

  • Power On - Check all LEDs on Control Hub turn on
  • Connect to WiFi - Verify driver station connection
  • Test Motors - Manually control each motor in the driver station
  • Test Sensors - Verify sensor data appears in telemetry
  • Check Logs - Review any error messages in the system logs

Best Practices

  • Label all ports and connections clearly
  • Use protective cases for motors and servos
  • Secure cables to prevent disconnection during matches
  • Test hardware before each competition
  • Keep spare cables and connectors