ftc centerstage game manual 1
Welcome to the FTC CenterStage Game Manual 1. This guide equips teams with knowledge, from game mechanics to play. It outlines objectives, rules, and best practices, ensuring a solid foundation for design, programming, and competition success.
All teams find this manual vital.
1.1 Purpose of the Manual
The FTC CenterStage Game Manual 1 serves as the definitive reference for teams preparing to compete in the 2024–2025 season. It consolidates all official rules, scoring guidelines, and design constraints into a single, easily navigable document. By presenting the information in a clear, structured format, the manual empowers teams to quickly understand the game’s core objectives, evaluate their strategic options, and align their engineering efforts with competition requirements.
Designed for students, mentors, and judges alike, the manual offers practical insights into effective preparation. It explains how to interpret the game’s narrative, how to translate that narrative into measurable goals, and how to document design decisions for review. The guide also emphasizes the importance of teamwork, safety, and compliance with the FTC Code of Conduct; By following the manual’s recommendations, teams can streamline their design process, reduce costly iterations, and focus on innovation.
In addition, the manual provides a framework for continuous improvement. It encourages teams to track progress, conduct systematic testing, and iterate based on data. The goal is to foster a culture of learning and resilience, ensuring that every team can compete confidently and safely. This manual is the cornerstone of a successful FTC season, offering clarity, consistency, and a shared vision for all participants.
Diagrams, sample code, and tips throughout the manual help teams apply best practices to hardware and testing and software.
Game Overview
CenterStage pits teams against a dynamic field where robots score by placing game pieces into designated zones. Each match lasts 2 minutes, with autonomous and driver-controlled periods. Success hinges on precise navigation, strategic placement, and power management!
2;1 Objectives and Rules
CenterStage challenges teams to maneuver a robot across a 12‑by‑12 foot field, placing game pieces—small cubes and larger blocks—into scoring zones. Each match lasts two minutes, split into a 15‑second autonomous period and a 105‑second driver‑controlled period. The autonomous phase rewards precise pre‑programmed actions, while the driver phase emphasizes real‑time control and strategy.
Objectives are twofold: maximize points by accurately delivering pieces to the center, left, and right zones, and maintain robot integrity by avoiding collisions with field elements and other robots. Points are awarded based on the type of piece, the zone of placement, and the timing of the action. For example, a cube placed in the center zone during the autonomous period earns 5 points, while a block placed in the same zone during the driver phase earns 10 points.
Rules govern robot design, operation, and safety. Robots must be fully autonomous during the first 15 seconds, with no driver input. After that, drivers may control the robot using a gamepad, but must adhere to speed limits, avoid illegal maneuvers, and respect the field boundaries. The robot must not exceed 12 inches in height, and all mechanical components must be secure and free of loose parts. Any violation results in point deductions or disqualification.
Teams must also follow the competition’s code of conduct, ensuring fair play, respectful behavior, and adherence to all safety protocols. The manual provides detailed guidance on scoring, penalties, and best practices for a successful competition experience.
Strategic planning involves selecting the optimal path to the center zone, timing the release of game pieces, and coordinating with teammates during the driver phase. Teams often practice autonomous routines that prioritize high‑value placements, while driver strategies focus on flexibility and rapid repositioning. Effective communication and role assignment are critical for maximizing scoring opportunities.
Play Field Layout
The field is a 12‑by‑12 foot square, divided into center, left, and right zones. Each zone contains a scoring platform. A 6‑inch high wall separates zones, and a central line marks the autonomous start. Robots must navigate without crossing boundaries. All zones are marked.
3.1 Field Zones and Elements
The CenterStage field is a 12‑by‑12 foot square divided into three zones: Center, Left, and Right. Each zone contains a scoring platform, a set of game pieces, and specific field elements that influence robot strategy. The Center zone is the most dynamic area, featuring a 6‑inch high wall that separates it from the Left and Right zones. This wall creates a natural barrier that robots must navigate around while attempting to place game pieces onto the center platform. The Left and Right zones each have a 3‑foot high wall that extends from the field’s perimeter to the center wall, forming a triangular play area. These walls define the boundaries for autonomous and teleoperated periods, ensuring that robots remain within their designated zones. The scoring platforms are positioned at the far ends of each zone, with the Center platform slightly elevated to reward precise placement. Each platform has a unique shape: the Center platform is a flat square, the Left platform is a trapezoid, and the Right platform is a circle. These shapes test robot manipulation and positioning skills. In addition to walls and platforms, the field includes a series of color‑coded lines that indicate zone boundaries and robot starting positions. The lines are 2‑inch wide and painted in bright yellow for visibility. The field’s floor is a smooth, non‑slippery surface that allows for consistent robot movement. All field elements are designed to be durable, with high‑impact plastic walls and reinforced platforms that can withstand repeated collision.!
Scoring System
Points are awarded for placing game pieces on platforms: 10 points for each piece in the center zone, 7 in left, 5 in right. Bonus 20 points for a full set of three pieces in any zone. Missed placements yield no points. Strategy focuses on maximizing high‑value zones. zones. End! !!
4.1 Points Allocation & Strategy
CenterStage scoring relies on placing game pieces in three zones: center, left, and right. Points per zone are 10, 7, and 5 respectively, reflecting reach difficulty. A 20‑point bonus is awarded for completing a full set of three pieces in any zone. Teams must balance speed and accuracy; rushed attempts often miss, yielding zero points. Prioritizing the center zone maximizes reward, while left and right zones provide secondary gains. Autonomous mode offers pre‑programmed placements, but driver‑controlled play allows dynamic adaptation to opponent actions. Clear communication between robot and driver is essential for targeting zones and bonus opportunities. Mechanical strengths—reach, lift height, precision—determine viable zones. Aligning robot capabilities with zone values helps maximize points. Continuous practice and data analysis refine strategies, ensuring each match builds toward a higher cumulative score.
In the endgame, a “zone sweep” lets teams move from one zone to another, securing multiple placements before the match ends. This demands careful path planning and real‑time decisions. The robot’s vision detects opponent placements, enabling dynamic zone targeting. By reviewing footage, teams spot opponent patterns and exploit defense gaps. Consistency is rewarded; a team placing at least one piece in each zone each match gains steady points, while a center‑only focus risks blockage. A balanced strategy that mixes high‑value placements with bonus chances yields the best season results. Mastering these tactics turns a solid robot into a championship contender. Mastering CenterStage demands focus, precision, and relentless improvement for success. and!!
Robot Design Guidelines
Design a lightweight chassis with high torque motors for quick acceleration. Use a 3‑axis lift to handle game pieces, and integrate a vision system for accurate placement. Ensure compliance with size limits and secure wiring for durability. Optimize weight for bale
5.1 Mechanical and Electrical Requirements
Mechanical design must prioritize structural integrity while staying within the 12‑inch square footprint. Use aluminum extrusions or 3D‑printed composite panels for a lightweight yet rigid chassis. All moving parts should be clearly articulated, with bearings rated for at least 10,000 cycles. The chassis should also incorporate modular attachment points for future upgrades, allowing quick integration of new subsystems without extensive redesign.
Drive train selection should favor high‑torque, low‑speed motors such as the REV 520 or 775 series, paired with gearboxes that achieve a 10:1 reduction for optimal acceleration. Motor controllers must support closed‑loop control with PID tuning. All gear ratios should be calculated to ensure the robot can lift and transport game pieces within the allotted time
Electrical architecture requires a master controller (e.g., REV Expansion Hub) with at least 8 PWM outputs and 4 CAN ports. Power cables should be 18 AWG or thicker, routed along the chassis to avoid abrasion.
Battery selection should be a 6‑cell Li‑Po pack, providing 22.2 V nominal voltage and a minimum 10 Ah capacity. Include a voltage regulator to maintain 12 V for auxiliary electronics. All wiring should be color‑coded: red for power, black for ground, blue for data.
Safety features: integrate a mechanical limit switch on the lift to prevent over‑extension, and a software watchdog that shuts down motors if communication is lost.
Programming and Control
Use the FTC SDK with Java or Kotlin. Structure code into subsystems, commands, and robot container. Leverage built‑in libraries for drivetrain, vision, and sensor fusion. Implement PID loops for precise motion, and use telemetry for real‑time debugging. Use async callbacks for sensor data now.
6.1 Software Architecture & Libraries
Robot main loop runs at 50 Hz. Vision runs asynchronously. Use ExecutorService for thread safetynow shared resources to avoid race conditions. Ensure thread safetynow and synchronization.
Testing & Deployment
Begin with unit tests for each subsystem. Use the FTC SDK test harness to validate motor encoders and sensor readings. Perform recording telemetry quickly. Adjust PID constants, then finalize the release build. Deploy via the driver station, ensuring firmware is signed.
7.1 Calibration, Practice, and Competition Prep
Before the first match, teams should perform a systematic calibration routine. Start by verifying the robot’s gyroscope, ensuring the heading is zeroed to the field reference; Next, calibrate the vision system: adjust the camera lens, set exposure, and run the target detection algorithm to confirm accurate distance measurements. Motor encoders must be reset and checked for consistency; run a full cycle of each drive motor and record the tick counts. Test the arm and wrist joints by moving them through the full range of motion while logging sensor data. Once calibration is complete, move into practice mode. Use the FTC Driver Station to simulate autonomous periods, verifying that the programmed routines execute within the allotted 15‑second window. During practice, focus on repeatability: run each autonomous routine at least ten times, noting any drift or unexpected behavior. Adjust PID constants on the fly, and record the results in a spreadsheet for later analysis. After autonomous practice, transition to teleoperated drills. Set up a mock field with all game pieces placed in their starting positions. Practice picking up, moving, and placing the pieces while maintaining speed and precision. Use a timer to track cycle times, aiming to reduce the average time per cycle by 10% each session. Incorporate obstacle courses to simulate real match conditions, ensuring the robot can navigate tight spaces and avoid collisions. During competition prep, perform a final system check: verify battery voltage, confirm that all sensors are functioning, and run a short test match against a teammate’s robot to validate communication protocols. Log any anomalies and resolve them before the match. Finally, review the strategy with the team, ensuring everyone understands the playbook, roles, and contingency plans. A well‑prepared team will execute flawlessly, turning practice into victory. Practice sessions should last at least two hours. Use data logs to refine PID tuning. All checks logged daily!. All members sign the checklist. Ensure all team members review the checklist before the match and double‑check all connections. All data archived daily.