Blog

Quick Summary: BIOBUZZ™ kickoff is almost here! With the 2026–2027 FIRST^® Tech Challenge season just days away, now is the time to make sure your team, workspace, skills, and equipment are ready. Use this FTC robotics season prep checklist to get organized, build team confidence, and hit the ground running when the new game is revealed.

Get Your FTC Team Ready for BIOBUZZ™

The countdown to the new FIRST^® Tech Challenge is on. On September 12, FTC teams will discover the new game challenge presented by RTX and begin turning ideas into their next competition robot.

You may not know what the game will require yet, but there is plenty your team can do before kickoff. Use these nine preseason tips to get organized, strengthen your team's skills, and prepare to move quickly once BIOBUZZ™ is revealed.

Tip 1: Take a Quick Look Back at Last Season

Before jumping into a new season, take a few minutes to reflect on your DECODE™ experience. A quick review can help your team carry forward what worked and avoid repeating past challenges.

📌 FTC Preseason Check-in:

☐ Celebrate: What did our team do particularly well?
☐ Identify challenges: What slowed us down or caused problems?
☐ Review decisions: Which design or programming choices would we change?
☐ Build skills: What skills should we strengthen this season?
☐ Set goals: What do we want to accomplish during BIOBUZZ™?

You don't need a lengthy meeting. Even a quick team conversation can help everyone start the new season with a clear focus.

Tip 2: Get Your Team on the Same Page

With kickoff approaching, make sure everyone knows how your team will work together once the game is revealed.

Welcome new members, review team expectations, and reinforce the FIRST Core Values, including Gracious Professionalism^® and Coopertition^®.

This is also a good time to clarify team roles and responsibilities. Who will focus on mechanical design? Who will program? Who will document the build? Who will handle outreach and communications? Your team may adjust those roles once you understand BIOBUZZ™ , but having a starting point will help everyone jump into action.

Tip 3: Identify Strengths & Skill Gaps

You don't need to learn every robotics skill before kickoff. Instead, take a quick look at what your team already knows and where you may need additional support.

📌FTC Team Skills Checklist

✓ Design and Engineering: CAD, mechanical design, fabrication, and prototyping ✓ Programming: Java, Blocks, sensors, control logic, and autonomous routines ✓ Electronics: Wiring, power distribution, and troubleshooting ✓ Creative Skills: Presentations, graphic design, photography, video, and social media ✓ Soft Skills: Communication, collaboration, organization, and problem-solving

Knowing your strengths and gaps now will make it easier to assign responsibilities once the BIOBUZZ™ challenge is revealed.

💡Bonus Tip:

If your team plans to submit an Engineering Portfolio, start documenting from day one. Keep track of design ideas, testing, decisions, successes, and failures throughout the season rather than trying to recreate everything later.

Tip 4: Start Practicing

You may not know what BIOBUZZ™ will ask your robot to do yet, but you can practice building and programming. Use this time to experiment with common robot systems such as drivetrains, arms, lifts, linear mechanisms, intakes, servos, sensors, and autonomous routines. The goal isn't to build your robot before kickoff. It's to get your team comfortable designing, building, testing, and troubleshooting so you're ready to prototype quickly when the game is revealed.

Tip 5: Organize Your Workspace and Inventory

Once kickoff arrives, you don't want to spend valuable build time looking for parts or discovering that something important is missing.

Give your workspace a quick preseason reset and make sure your team knows where everything belongs.

📌 Sample Inventory Checklist:

☐ Motors and servos ☐ Actuators ☐ Fasteners and hardware ☐ Structural components ☐ Slide rails ☐ Encoders and sensors ☐ Batteries ☐ Power components ☐ Tools and fabrication equipment Check batteries, chargers, cables, and other frequently used equipment while you're at it. A little organization now can save significant time later.

Tip 6: Know Your Hardware

Now isn't necessarily the time to completely rethink your robot hardware strategy. Instead, make sure your team understands the components you already have and knows which parts could be useful once the game is revealed.

📌 Review Your Available Hardware

• Drivetrain components for speed and maneuverability
• Smart servos for controlled movement
• Linear actuators for lifts and extensions
• Slide rails for linear mechanisms
• Power components for reliable energy distribution
• Encoders and odometry components for autonomous navigation

If there are components your team has never used before, now is a good time to familiarize yourselves with how they work.

That way, when a BIOBUZZ™ mechanism calls for a particular type of motion or control, your team can spend less time learning the hardware and more time solving the engineering challenge.

Tip 7: Learn from the FTC Community

You don't have to start from scratch. One of the best resources available to FTC teams is the larger robotics community. Review technical documentation  and check out the FTC Community Forum. You can also explore related videos on YouTube, the FTC subreddit, watch videos on the FUN Robotics Network, and browse Chief Delphi.

Use this final preseason stretch to watch robot reveals, review match footage, and see how other teams have approached engineering challenges.

📌 FTC Team Learning Activities

✓ Watch FTC robot reveal and match videos ✓  Review past game strategies ✓  Explore technical documentation ✓  Research mechanisms you're interested in ✓  Discuss ideas and approaches with other teams Use what you see as inspiration and a learning opportunity. The goal is to understand different engineering approaches and spark ideas your team can develop into its own solutions.

Tip 8: Make a Season Game Plan

The BIOBUZZ™ challenge may be unknown right now, but your team's schedule doesn't have to be. Before kickoff, make sure you have a plan for managing the weeks ahead.

📌 Add Key Dates to Your FTC Calendar

☐ Build and design milestones ☐ Testing and iteration time ☐ Autonomous development ☐ Driver practice ☐ Scrimmages and competitions ☐ Engineering Portfolio updates ☐ Judging preparation ☐ Outreach and team activities

Once the game is revealed, you can add game-specific goals and deadlines. Having a basic framework already in place will help your team stay focused when the build season gets busy.

Tip 9: Check Your Build-Ready Supplies

Having the right parts on hand helps your team prototype quickly and iterate once the BIOBUZZ™ challenge is revealed. Take one final look at your build inventory and identify any components you'll want available for early prototypes.

Need to fill any gaps? These Studica Robotics components can help teams prepare for the season, from power and motion control to linear mechanisms and autonomous performance.

Power Systems

• Servo Power Block and FTC Power Block
  These compact power solutions help provide reliable power distribution for FTC robot systems, including dedicated power for servos.

Servo Power Block with XT30 Male to JST-VH Cable Bundle - Part 75005

Studica Robotics FTC Power Block - Part 70407

• Battery and Power Switch
  A competition-ready power system starts with an FTC-approved 12V NiMH battery and an approved main power switch. Studica's 12V 3000mAh NiMH battery and On/Off Power Switch Kit are options for teams building or refreshing their power system.

Studica 12V 3000mAh NiMH Battery Pack PP45 ARES – Part 70025

Studica On/Off Power Switch - Part 70182

XT30 Female to PP45 Cable - Part 70195

Motion Control Components

• Multi-Mode Smart Servos
  Multi-mode smart servos provide flexible motion options for mechanisms such as arms, intakes, and other moving assemblies.
• Linear Servo Actuators
  Linear servo actuators provide controlled push-and-pull movement for lifts, arms, and other mechanisms.
• Slide Rails
  Aluminum slide rails provide a strong, lightweight solution for linear mechanisms, including lifts and extending arms.

Multi-Mode Smart Servo Motor - Part 75002

Studica Linear Servo RC Actuator - Part 75014

Slide Rails from Studica Robotics

Odometry and Autonomous Performance

• Cypher Max Encoder with 38mm Omni Wheel
  For teams working to improve autonomous navigation, odometry components can provide more precise robot tracking and positioning. The Cypher MAX Encoder paired with a 38mm Omni Wheel offers a compact option for teams exploring advanced autonomous performance.

Cypher MAX Through Bore Encoder - Part 75051

38mm Omni Wheel - Part 76259

Frequently Asked Questions

What should an FTC team do before kickoff?

Before FTC kickoff, focus on readiness rather than predicting the game. Organize your workspace, check your inventory, review team roles, test hardware, and confirm your schedule.

Should we build a robot before the BIOBUZZ™ game is revealed?

You don’t need a complete robot. Use preseason time to practice with drivetrains, mechanisms, sensors, servos, and programming. Small prototypes can help build skills you’ll use after the game is revealed.

What FTC hardware should we have ready for kickoff?

Make sure you have the basics for prototyping and building, including motors, servos, structural components, fasteners, power components, batteries, sensors, and tools. Know what you have and what you may need.

How can FTC teams prepare before the game is revealed?

Focus on transferable skills like mechanical design, programming, autonomous routines, prototyping, troubleshooting, and teamwork.

Where can FTC teams find inspiration?

Look to robot reveal videos, match footage, technical documentation, FIRST resources, robotics forums, and other FTC teams. See how others solve problems and use those ideas to inspire your own designs.

How should we prepare new FTC team members?

Get new members hands-on, introduce them to your tools and processes, and pair them with experienced students when possible. Clear responsibilities and mentorship can help them become confident contributors.

Should we start working on our Engineering Portfolio now?

Yes! Document your season from the start, including design ideas, prototypes, testing, challenges, improvements, outreach, and team accomplishments.

When should FTC teams start planning their season? Ideally, before kickoff. With BIOBUZZ™ just days away, now is the time to organize your workspace, review your team’s skills, confirm your schedule, and get your hardware ready.

Start BIOBUZZ™ Strong

Kickoff is almost here, and your team doesn't have to wait for the game reveal to start preparing. A few simple steps now, like organizing your workspace, checking your equipment, reviewing your team's strengths, and getting everyone on the same page, can give your team a stronger starting point when the BIOBUZZ™ challenge is revealed.

Studica Robotics offers FTC-legal robot components and building solutions to help teams prototype, build, test, and iterate throughout the season. Get ready for the 2026–2027 BIOBUZZ™ season and make the most of every build day ahead. Browse FTC robot parts and kits and get ready to build!

Quick Summary: The countdown to WorldSkills Shanghai 2026 is on! Taking place September 22–27, 2026, the 48th WorldSkills Competition will bring together approximately 1,400 Competitors from 73 countries and regions to compete across 64 skill competitions. Among them are Autonomous Mobile Robotics and Unmanned Aerial Systems, two rapidly evolving fields that bring together engineering, electronics, software, automation, and problem-solving. As a WorldSkills Global Partner and the exclusive supplier for the WorldSkills Autonomous Mobile Robotics Competition, Studica Robotics is proud to support the global skills community and follow these two exciting competitions as Competitors prepare to take the stage in Shanghai.

WorldSkills Shanghai 2026 Is Almost Here

Every two years, the WorldSkills Competition brings together the world's top young talent in technical and vocational skills for a global celebration of skills excellence. Competitors have earned their places at WorldSkills through national and regional selection competitions, representing years of dedication, preparation, and technical achievement.

WorldSkills Skill Sectors

The 64 skill competitions are organized across six skill sectors.

The competition gives Competitors an international stage to demonstrate their technical expertise while highlighting the importance of skilled careers and technical and vocational education and training around the world. For Studica, two competitions are particularly exciting: Autonomous Mobile Robotics and Unmanned Aerial Systems.

Two Skills to Watch in Shanghai

From robots navigating the ground to unmanned systems taking to the air, Autonomous Mobile Robotics and Unmanned Aerial Systems demonstrate how technical skills are being applied to increasingly automated and connected systems.

Both bring together engineering, electronics, software, and problem-solving, while applying those skills in very different environments.

Autonomous Mobile Robotics at WorldSkills Shanghai 2026

Autonomous Mobile Robotics brings together mechanical engineering, electronics, programming, sensors, and control systems as Competitors design, build, program, and test mobile robots to solve complex problems.

Part of the Manufacturing and Engineering Technology sector, the skill reflects the growing role of robotics across industries such as manufacturing, agriculture, aerospace, mining, and medicine. Competitors need to combine multiple areas of technical expertise to create robotic systems that are reliable, precise, and effective.

AMR Materials for Shanghai 2026

For the Autonomous Mobile Robotics competition, the Shanghai 2026 collections provide the components Competitors need to build and configure their robots. The BASE Collection provides the components needed to build four base robot configurations: Differential Drive, Differential Drive All-Terrain, Mecanum, and X-Drive.

The WorldSkills Autonomous Mobile Robotics Shanghai 2026 FULL Collection includes components for those four robots, plus additional parts for the robot OMS assemblies. The collection includes the VMX Robotics Controller, electronics, motors, servos, structural components, gears, sprockets, pulleys, belts, wheels, bearings, axles, brackets, fasteners, and other robotics hardware. In total, the collection offers more than 2,100 components.

Together, these materials give Competitors the flexibility to build, test, and adapt their robots as they tackle the challenges of the Shanghai 2026 competition. Competitors can also create 3D-printed parts when additional components are needed.

Unmanned Aerial Systems Makes Its WorldSkills Debut

For the first time, Unmanned Aerial Systems (UAS) will make its WorldSkills debut at Shanghai 2026. Commonly known as drones, UAS technology has moved far beyond hobby aircraft, with applications ranging from aerial surveying and infrastructure inspection to precision agriculture, firefighting, conservation, and public safety.

At WorldSkills Shanghai, Competitors will bring together skills in aerodynamics, electronics, flight control, software, navigation, sensors, and communications as they work with unmanned aircraft and the technologies that make them fly, sense, and respond to their surroundings.

The Technology Behind the UAS Skill

Studica Robotics supports UAS education and skills development with the Studica WS500 UAV Quadcopter Kit, an open platform designed for hands-on learning with modern unmanned aerial systems.

The WS500 combines a carbon-fiber frame and motors with a CubePilot flight controller and Raspberry Pi 4B companion computer. Its sensor package includes an optical flow and distance sensor with a 6-axis IMU, a ToF 3D depth camera, and T-Mini Plus LiDAR. Together, these components provide a hands-on platform for exploring flight control, navigation, obstacle avoidance, sensor fusion, and autonomous systems, while ROS 2 support with MAVROS adds opportunities to work with robotics software and autonomy.

The kit also includes the practical hardware needed to build and maintain the aircraft, including the power distribution system, propellers, landing gear, wiring, protective covers, and an installation and repair toolkit.

Frequently Asked Questions

When is WorldSkills Shanghai 2026?

The 48th WorldSkills Competition will take place from September 22–27, 2026, in Shanghai, China.

Where will WorldSkills Shanghai 2026 be held?

WorldSkills Shanghai 2026 will be held in Shanghai, China.

How many skills are represented at WorldSkills Shanghai 2026?

WorldSkills Shanghai 2026 will feature 64 skill competitions across six skill sectors.

What is Autonomous Mobile Robotics?

Autonomous Mobile Robotics is a WorldSkills competition focused on designing, building, programming, testing, and maintaining mobile robots that can solve problems in real-world environments.

What sector is Autonomous Mobile Robotics part of?

Autonomous Mobile Robotics is part of the Manufacturing and Engineering Technology sector at WorldSkills Shanghai 2026.

What is Unmanned Aerial Systems?

Unmanned Aerial Systems, or UAS, refers to unmanned aircraft and the technologies used to operate them, commonly known as drones. The field involves technologies including aerodynamics, flight control systems, communications, robotics, software, sensors, navigation, and regulatory compliance.

Is Unmanned Aerial Systems new to WorldSkills?

Yes. Unmanned Aerial Systems is making its WorldSkills debut at Shanghai 2026.

What is Studica Robotics' role in WorldSkills?

Studica Robotics is a Global Partner of WorldSkills and the exclusive supplier for the WorldSkills Autonomous Mobile Robotics Competition. Studica also supports skills development in emerging technology fields including robotics and unmanned aerial systems.

The Final Countdown to WorldSkills Shanghai 2026

The countdown to WorldSkills Shanghai 2026 is almost over. In just a few weeks, Competitors from around the world will put their skills, preparation, and determination to the test on the global stage. For Autonomous Mobile Robotics Competitors, Shanghai is the culmination of years of preparation. For Unmanned Aerial Systems Competitors, Shanghai marks the beginning of a new chapter as the skill makes its WorldSkills debut. Studica Robotics offers WorldSkills Competition Kits for AMR and UAS and proudly supports both competitions. We are excited to be part of the journey to Shanghai.

The countdown is on. We’ll see you in Shanghai!

Related Articles:

• WorldSkills Jamaica Robotics Training for AMR and UAS
• WorldSkills Shanghai 2026: Building Skills for a Changing World

Quick Summary: The Cypher MAX is an external encoder that can help FTC teams track robot movement for odometry and localization. Learn how external encoders and dead wheels work, why they can improve autonomous movement, and the basics of quadrature and absolute encoders.

FTC Odometry: Know Where Your Robot Is

In autonomous, knowing where your robot should be isn't enough. You need to know where it actually is. FTC odometry uses sensor data to estimate your robot's position and movement on the field, helping teams create autonomous routines that are more precise and repeatable.

Many FTC teams use the encoders built into their drive motors to estimate movement. But when wheels slip, traction changes, or a mecanum drivetrain strafes across the field, motor rotation doesn't always tell the whole story. An external encoder and tracking wheel can provide another way to measure how the robot is actually moving.

The Cypher MAX Through Bore Encoder is an external through-bore encoder that can be used with a dead wheel for odometry and robot localization, as well as applications such as mechanism position tracking and RPM measurement. Let's look at how it works and why external encoder data can be useful for FTC teams.

What Is an Encoder?

An encoder is a sensor that measures rotational movement. As a shaft or wheel rotates, the encoder converts that movement into signals that a robot controller can use to determine position, speed, distance, or direction. This information is especially valuable for autonomous routines that require precise and repeatable movement.

How Is the Cypher MAX Different from a Typical Motor Encoder?

A typical motor encoder measures the rotation of the motor shaft. The Cypher MAX is an external through-bore encoder, which means it can be mounted independently from the drive motor.

For example, an FTC team can mount the Cypher MAX to a dedicated tracking wheel, commonly called a dead wheel, to measure the actual movement of the robot rather than relying only on drivetrain motor rotation. This gives teams another source of encoder data for odometry and robot localization.

Why Use an External Encoder for FTC Odometry?

Using motor encoders to estimate drivetrain movement is a straightforward approach to localization, and it can work well. However, the rotation of a drivetrain wheel does not always perfectly represent the robot's actual movement.

This is particularly relevant for mecanum-drive robots. When a robot accelerates, decelerates, strafes, or rotates, changes in traction can cause drivetrain wheels to slip or lose contact with the field. The motor encoder continues to measure the rotation of the motor shaft, even when the robot's actual movement differs from the calculated movement.

That difference can become more noticeable when an autonomous routine needs to make precise strafing movements, navigate to multiple locations, align with field elements, or position the robot consistently for scoring. An external encoder mounted to a dedicated tracking wheel provides another way to collect movement data that is less dependent on drivetrain motor rotation.

What Is a Dead Wheel?

A dead wheel, also called a tracking wheel, is a small unpowered wheel dedicated to measuring robot movement. The wheel and encoder are often mounted together as part of an odometry pod.

Unlike a drivetrain wheel, a dead wheel does not drive the robot. Instead, it rolls along the field as the robot moves. An encoder attached to the wheel measures its rotation, providing data that can be used to estimate the robot's movement and position.

Many odometry systems use multiple tracking wheels positioned to measure movement in different directions. By combining these encoder measurements with the known positions of the tracking wheels on the robot, software can estimate forward movement, lateral movement, and changes in heading.

Dead wheels are not completely immune to error. They can still slip or lose contact with the field if the odometry pod is poorly designed.

Dead Wheel Reliability Checklist

A dead wheel can provide useful odometry data, but the mechanical setup matters. Before relying on a tracking wheel for autonomous movement, check that your odometry system is set up to provide consistent readings.

Use this checklist when designing or troubleshooting your dead wheel setup:

• Maintain consistent contact with the field. The tracking wheel should stay in contact with the field as the robot moves without excessive bouncing or losing contact.
• Minimize mechanical flex. Movement in the odometry pod or mounting structure can introduce inaccuracies into your encoder readings.
• Properly support the encoder. Make sure the encoder and shaft are securely mounted to prevent unnecessary movement or misalignment.
• Keep the tracking wheel aligned. Proper alignment helps ensure the wheel is measuring movement in the intended direction.
• Reduce unnecessary vibration. Excessive vibration or movement in the mechanism can affect the consistency of your measurements. 

Remember: Dead wheels are not completely immune to error. Wheel slip, inconsistent field contact, mechanical flex, and setup issues can still affect localization accuracy.

Benefits of External Encoders for FTC Teams

Using an external encoder with a dead wheel gives FTC teams another source of movement data that is less dependent on drivetrain motor rotation. This can help reduce the effects of drivetrain wheel slip on localization and support more precise and repeatable autonomous movements.

External encoders also give students an opportunity to explore how encoder data is used for odometry and robot localization, while creating a foundation for more advanced autonomous programming.

What Is the Difference Between a Quadrature Encoder and an Absolute Encoder?

Encoders can measure rotation in different ways. Two common types are quadrature encoders and absolute encoders, and the difference comes down to how they report position.

A quadrature encoder tracks changes in position as a shaft rotates. It outputs signals through its A and B channels, and the robot can interpret those signals to determine how far and in which direction the shaft has moved. The Cypher MAX also includes an index, or I, channel that provides a reference point once per revolution.

An absolute encoder works differently. It provides a position value that corresponds to the shaft's current position, rather than requiring the robot to track changes from a starting point. The position is represented by a unique output value, allowing the robot to determine the shaft's position without calculating movement from a starting point.

Why Does This Matter for FTC Teams?

For odometry, teams are primarily interested in measuring how much movement has occurred, which is where quadrature encoder data is useful. The robot can count encoder changes and combine that information with factors such as wheel circumference, gear ratios, and tracking wheel placement to estimate movement across the field.

Absolute position data can be useful in other situations, particularly when a robot needs to know the current position of a rotating mechanism or shaft.

The Cypher MAX provides A, B, and I quadrature outputs as well as an absolute PWM output, giving teams flexibility for odometry, mechanism position tracking, and other robotics applications.

Applications for the Cypher MAX Encoder

Odometry and robot localization are just some of the potential applications for an external encoder.

The Cypher MAX can also be used for:

• Mechanism position tracking
• Arms and lifts
• Rotating or pivoting mechanisms
• RPM measurement
• General shaft position tracking

This makes an external encoder a useful tool not only for autonomous navigation but also for teaching and experimenting with different robotics applications.

Getting Started with Hardware and Software Setup

Once you understand how the encoder works, the next step is installing it and configuring your robot to read its data.

Setup at a Glance

Hardware Installation

When mounting an encoder for odometry, focus on keeping the encoder properly supported, aligned, and protected from unnecessary movement or flex.

For an odometry pod, the tracking wheel should maintain consistent contact with the field while still rotating freely. A stable mechanical setup helps produce more consistent encoder readings and, ultimately, more reliable position tracking.

Example Odometry Pod

Above is an example of a simple odometry pod system. The encoder is angled so that the omni-wheel can maintain contact with the ground, while also simultaneously being housed safely. The hole pattern on the U-Channel allows for adjusting the angle of the encoder tracking wheel accordingly to ensure contact with the ground.

Odometry Example Build

This is one example of how an odometry pod can be integrated into a mecanum drivebase. The encoders are mounted on the inside of the robot's frame to protect the encoders as well as to accurate track the robot's movement about it's center of mass. Teams can modify the design to fit their own robot while keeping the same basic design principles in mind.

Software Setup

Once the hardware is installed, the general configuration process is:

1. Connect the encoder to compatible FTC control hardware.
2. Open the robot's hardware configuration.
3. Verify that the connected hardware is recognized.
4. Identify the ports being used for the external encoders.
5. Give the encoders appropriate names, such as encoderX and encoderY.
6. Read the encoder values in your robot code.
7. Convert encoder counts into useful movement or position data.

The exact setup will depend on the FTC hardware and software configuration being used.

Software Setup Instructions

In the configuration file, declare an unspecified motor in the port being used, and give it a name such as "cypherMax". External quadrature encoders are accessed through the corresponding motor object.

Declaring Encoder in Configuration File Cypher MAX being declared in the configuration file. Here is the example code to set up the encoder. 

Setting up Encoder: At the beginning of the OpMode, reset the encoder and establish the starting encoder position as 0. Create the variables.

Creating Variables Create the following variables:

• encoderCounts
• revolutions
• distanceMM
• distancesInches

Then establish constraints.

Establish Constants Establish constants for the encoder and wheel specifications and calculate the tracking wheel's circumference.

Read the encoder.

Reading the Encoder When the OpMode begins, it will continuously read the encoders current position, then calculate the amount of revolutions. Then calculate distance.

Calculating Distance Traveled After calculating how many revolutions the tracking wheel performs, the OpMode uses the that calculation to determine how far the robot has traveled from it's starting position in millimeters and inches. Then add telemetry.

Adding Telemetry Data All the data calculated then gets displayed on the driver hub.

Here is the complete code.

Frequently Asked Questions

What is FTC odometry?

FTC odometry is the process of using sensor data, such as encoder measurements, to estimate a robot's position and movement on the field.

What is a dead wheel in FTC robotics?

A dead wheel is an unpowered wheel dedicated to measuring robot movement. As the robot moves, the wheel rotates and an encoder measures that rotation.

Why use an external encoder instead of a motor encoder?

Motor encoders measure motor rotation, which may not always perfectly represent the robot's actual movement if the drivetrain wheels slip. An external encoder connected to a tracking wheel provides another source of movement data.

What is the difference between a quadrature and absolute encoder?

A quadrature encoder measures changes in position by generating pulses as the shaft rotates. An absolute encoder provides information about the shaft's current position.

How many counts per revolution does the Cypher MAX have?

The Cypher MAX provides 2048 counts per revolution in quadrature mode.

Can the Cypher MAX be used for applications besides odometry?

Yes. External encoders can also be used for mechanism position tracking, arms, lifts, rotating mechanisms, and RPM measurement.

Do dead wheels eliminate all localization errors?

No. Dead wheels can still experience errors from slip, inconsistent contact with the field, mechanical flex, or incorrect software configuration.

What is the difference between a dead wheel and a motor encoder?

A motor encoder measures the rotation of a motor, while a dead wheel uses an unpowered tracking wheel and encoder to measure the robot's movement independently of the drivetrain.

Take Your Odometry Further

Understanding how a robot moves is an important part of building reliable autonomous routines. External encoders and dead wheels give FTC teams another way to collect movement data and explore robot localization beyond the encoders built into their drive motors.

The Cypher MAX provides a versatile external encoder option for FTC odometry, mechanism tracking, and other robotics applications. Whether your team is just learning about robot localization or working toward more precise autonomous routines, understanding encoder data is a valuable step in developing better-performing robots. Related Articles:

• Essential Odometry Tips for Your FTC Robot
• How is Odometry Used in FTC Robotics Competitions?

Quick Summary: The FTC offseason gives teams valuable time to build skills, train new members, and improve their approach before the pressure of competition begins. Through programming, CAD, robot design, driver training, and team organization projects, teams can develop the experience and processes needed to design, build, program, and compete more effectively when the new season begins.

Success during the offseason isn't about building the perfect competition robot before kickoff. It's about creating a stronger foundation through learning, experimentation, and continuous improvement.

Why FTC Offseason Preparation Matters

While the competition season moves quickly, the offseason gives teams valuable time to learn, experiment, and improve without the deadlines of an upcoming tournament. Teams can use this time to strengthen technical skills, train new members, test new ideas, and create better processes for the upcoming season. Some of the biggest benefits of FTC offseason preparation include:

FTC Offseason Planning Roadmap

A structured approach helps teams stay focused and make the most of their offseason time.

The goal is not simply to stay busy during the offseason. Each project should help team members develop skills that will translate into stronger performance during competition.

Tip #1: Evaluate Your Previous Season

Before starting new projects, teams should take time to reflect on the previous competition season. Understanding what worked well and what needs improvement helps teams choose meaningful offseason goals. Here are some questions to consider:

📌 Evaluating Your Previous Season Checklist

Tip #2: Boost Programming Skills

Programming skills are one of the most valuable areas teams can develop before the season begins. Many programming concepts carry over from year to year, allowing students to build knowledge that can be applied to future robots.

🟠 Beginner Programming Projects

Beginner projects should focus on building a strong foundation with the FTC SDK.

🟡 Intermediate Programming Projects

Intermediate projects help teams improve driver control, automation, and overall robot performance.

🟢 Advanced Programming Projects

Advanced projects introduce concepts commonly used by highly competitive FTC teams.

Tip #3: Improve CAD Skills

CAD skills allow teams to design, test, and improve robot concepts before physically building them. Strong CAD practices can reduce mistakes, improve collaboration, and speed up robot development.

🟠 Beginner CAD Projects

These beginner CAD projects are designed to learn the software and FTC components.

🟡 Intermediate CAD Projects

These intermediate CAD projects give practice with designing and improving real mechanisms.

🟢 Advanced CAD Projects

These advanced CAD projects give your team practice engineering complete robot concepts and optimizing performance.

FTC Offseason Tip #4: Use an FTC Starter Bot to Build Skills

A Starter Bot gives teams a proven robot platform they can use to practice, experiment, and improve throughout the offseason. Instead of waiting for kickoff to begin learning, teams can build programming, CAD, mechanical, and driver skills using a robot that's ready to modify and test. 👉 Get ready with the FTC Starter Bot Build Guide from Studica Robotics.

📌 Starter Bot Challenge Ideas

Studica Robotics offers an FTC Starter Bot and FTC-compatible robot building solutions that help teams begin learning, experimenting, and building long before the next competition season starts.

Tip #5: Mechanical Design Challenges

The offseason is the perfect time to experiment with mechanical concepts, compare design options, and gain hands-on engineering experience without the pressure of competition deadlines.

📌 Mechanical Design Challenge Ideas

Tip #6: Strengthen Driver Performance

Consistent driver practice helps teams build confidence, improve match performance, and identify opportunities to refine both the robot and its controls before the competition season begins.

📌 Driver Practice Ideas

Tip #7: Improve Team Organization

The offseason is an ideal time to improve team organization and establish processes that help projects run more efficiently throughout the competition season.

📌 Team Organization Ideas

Build Better Robots with Studica Robotics

Having reliable building components allows teams to spend more time designing, testing, and improving their robots. Studica Robotics provides FTC teams with affordable, competition-ready robot parts, building systems, and resources to support offseason development. The Studica Robotics building platform includes FTC-compatible structural components, motion components, electronics, hardware, and robot kits designed for classroom learning, team training, and competition use. Teams can also explore different robot designs with durable aluminum structural components available in multiple colors, including blue, green, gold, red, silver, and black. The 6061-T6 aluminum structure system provides a strong, safe, and versatile foundation for building custom robots. FTC teams can  explore FTC robot parts and take advantage of resources including the FTC Starter Bot Resource Guide.

Frequently Asked Questions

What should FTC teams do during the offseason?

FTC teams should use the offseason to develop technical skills, train new members, test robot concepts, practice driving, improve documentation, and prepare team processes before the next competition season.

Should FTC teams build a competition robot during the offseason?

The goal of offseason preparation is not necessarily to build a competition-ready robot. Instead, teams should focus on learning, experimenting, and developing skills that will help them during the official season.

What programming skills should FTC teams learn?

Teams can practice programming fundamentals such as TeleOp control, sensors, encoders, autonomous routines, odometry, and PID control.

How can new FTC members prepare before the season?

New members can learn robot assembly, programming basics, CAD, driving skills, and team processes through offseason projects and Starter Bot activities.

Prepare Your FTC Team for Success Before Kickoff

The offseason provides FTC teams with a valuable opportunity to learn, experiment, and improve. Teams that invest time in skill development, testing, documentation, and organization can enter the next season with stronger technical abilities and a clearer strategy. Whether your team is training new members, exploring advanced programming concepts, improving CAD skills, or testing new robot designs, offseason preparation helps create a stronger foundation for competition success. With the right projects and resources, teams can spend less time learning the basics during the season and more time developing innovative solutions.

Quick Summary: International competitors gathered in Jamaica for a five-day robotics training camp designed to prepare them for WorldSkills Shanghai 2026. In partnership with Studica Robotics, the program focused on Autonomous Mobile Robotics (AMR) and Unmanned Aerial Systems (UAS), combining hands-on robot and drone training with real-world competition preparation. Participants progressed from system setup and assembly to programming, testing, and evaluation. The goal was to build both technical and teamwork skills needed for global competition success.

Robotics Training for WorldSkills Competition

As global demand for automation and intelligent systems continues to grow, WorldSkills Shanghai 2026 is placing a strong emphasis on advanced robotics training in Autonomous Mobile Robotics (AMR) and Unmanned Aerial Systems (UAS), where competitors must apply engineering principles in real time under international competition standards.

This type of robotics training goes beyond technical instruction; it mirrors the environments shaping modern industry, from smart manufacturing and autonomous logistics to precision agriculture, infrastructure inspection, and emergency response systems. Participants gain hands-on experience with technologies that are actively transforming how work is designed and delivered worldwide.

By working through real-world challenges in both AMR and UAS, competitors strengthen not only their technical capabilities but also their problem-solving, adaptability, and collaboration skills essential for success at WorldSkills Shanghai 2026 and beyond.

Inside the Robotics Training Experience

The five-day training camp followed a progressive learning model that moved competitors from foundational system setup to competition-level performance in both Autonomous Mobile Robotics (AMR) and Unmanned Aerial Systems (UAS). Each phase built upon the previous one, combining technical instruction, hands-on application, and performance evaluation.

By the end of the program, participants had progressed from assembling and configuring systems to executing autonomous navigation tasks, flying drones under performance constraints, and demonstrating the teamwork and technical proficiency required for WorldSkills competition.

Voices from the Camp

"Through international collaboration, knowledge sharing, and hands-on learning, participants are gaining valuable exposure to industry-leading practices in autonomous mobile robotics." -Walace Felipe de Almeida Oliveira, WorldSkills Brazil

“Robotics is not an activity that only men can partake in. Women can, as well, and we’re living proof of this…”
- St. Hilda’s Diocesan High School Team Captain, Toria-Lee Martin

“If you want to beat the best, you have to see how the best train.”
- Derek Murphy, General Manager, Studica Robotics

Why Train AMR?

Autonomous Mobile Robotics (AMR) is one of the fastest-growing areas in technical education and modern industry. It focuses on designing and building robots that can move and operate independently using sensors, control systems, and intelligent programming. Through AMR training, participants develop a wide range of integrated engineering skills, including mechanical and electronic system design, sensor integration, and automation. They also strengthen their ability to program autonomous systems, enabling robots to navigate, map environments, and respond to real-world conditions. AMR training also develops problem-solving and teamwork skills, reflecting the collaborative nature of real-world engineering environments.

Why is UAS Important?

Unmanned Aerial Systems (UAS) are rapidly expanding across industries and are becoming essential in areas such as infrastructure inspection, agriculture, logistics, disaster response, and environmental monitoring.

Training in UAS helps participants understand both the mechanical and digital systems behind drone technology. This includes building and configuring aerial systems, programming flight behavior, and developing the ability to troubleshoot and diagnose technical issues. As with AMR, this training strengthens critical thinking, engineering methodologies, and technical collaboration. These skills are increasingly in demand across aerospace, advanced manufacturing, infrastructure inspection, and emerging drone technology sectors.

Studica Robotics and Global Skills Development

With over 40 years of experience supporting technical education, Studica Robotics provides standardized training kits, curriculum resources, and technical support for WorldSkills member countries. For AMR competitions, teams use the official WorldSkills Autonomous Mobile Robotics Collection. For UAS training, participants utilize the WS500 Quadcopter Kit to build, program, and operate drone systems while also developing troubleshooting and diagnostic skills.

This structured ecosystem helps ensure consistent training quality while encouraging collaboration and peer learning across countries. Through its partnership with WorldSkills, Studica Robotics helps member countries develop robotics and UAS skills by providing standardized equipment, training resources, and competition support.

What This Robotics Training Experience Delivers

Beyond technical preparation, the training camp is designed to build long-term capabilities that extend well beyond the competition itself. It strengthens real-world engineering and robotics skills by providing competitors with hands-on experience with systems they will encounter in advanced technical environments. At the same time, it improves collaboration within international teams, where participants must communicate, adapt, and work effectively across different cultures and approaches.

The experience also helps develop the ability to solve complex problems under the pressures of a competition environment, where timing, accuracy, and decision-making all matter. Most importantly, it supports clear pathways into future technical careers by exposing participants to industry-relevant tools, processes, and expectations.

This training camp provided competitors with an opportunity to develop their skills in a collaborative international environment while preparing for the upcoming challenges of WorldSkills Shanghai 2026.

Frequently Asked Questions

What is Autonomous Mobile Robotics (AMR)?
AMR involves designing, building, and programming robots that operate independently using sensors, control systems, and automation logic.

What are Unmanned Aerial Systems (UAS)?
Unmanned Aerial Systems (UAS) focus on drone technology, including assembly, programming, flight control, maintenance, and system diagnostics.

Who is this WorldSkills Jamaica robotics training for?
It is designed for students and competitors preparing for international robotics competitions and technical skills development programs.

How does Studica Robotics support WorldSkills?
Studica Robotics provides standardized kits, training materials, and technical expertise to support global robotics education and competition readiness.

What is the goal of the WorldSkills Jamaica robotics training camp?
To prepare competitors for WorldSkills Shanghai 2026 through hands-on robotics and drone training under real competition conditions.

Conclusion

The WorldSkills Jamaica & Studica Robotics Invitational Training Camp demonstrated how immersive, hands-on learning can accelerate technical skill development and global competition readiness.

Over five days, competitors moved from foundational system understanding to full competition performance in Autonomous Mobile Robotics and Unmanned Aerial Systems. Beyond robotics, the camp strengthened collaboration, communication, and confidence. These skills are essential for success in both international competition and future technical careers.

As robotics, automation, and drone technologies continue reshaping global industries, programs like this are not just training events; they are launchpads for the next generation of skilled robotics professionals.

Quick Summary: Field-centric drive is a control system commonly used in FTC mecanum drivetrains that keeps robot movement aligned to the field instead of the robot’s orientation. Unlike robot-centric drive, drivers do not need to mentally adjust controls when the robot rotates. This article explains what field-centric drive is, how it works, the math behind it, and common considerations teams should understand before implementing it.

What Is Field-Centric Drive?

In traditional robot-centric teleop control, robot movement is based on the robot’s orientation. The robot has a designated “front” and “back,” and the controls rotate with the robot.

For example, if the robot turns 90 degrees to the right, pushing the joystick forward causes the robot to move toward the right side of the field because the front of the robot is now facing that direction.

Field-centric drive changes this behavior by making movement relative to the field rather than the robot’s orientation. No matter which direction the robot faces, controls stay aligned to the driver’s perspective from the driver station.

Robot Orientation Diagram for Robot-Centric 

Robot-Centric vs. Field-Centric Drive

Let's take a closer look at the robot-centric drive and the field-centric drive so you can understand how and when each could work best for your team.

Robot-Centric Drive

With robot-centric drive:

• Pushing the joystick forward moves the robot in the direction the robot is facing
• Controls rotate with the robot
• Drivers must constantly account for robot orientation during movement

Robot-Centric Drive Perspective

Field-Centric Drive

With a field-centric drive:

• Pushing the joystick forward always moves the robot forward relative to the field
• Controls remain consistent regardless of robot orientation
• Drivers can rotate the robot without mentally remapping controls

Field-Centric Drive Perspective

Why FTC Teams Use Field-Centric Drive

Field-centric drive is commonly used in FTC because it can create a more intuitive driving experience, especially with mecanum drivetrains.

However, preferred drive style still depends on driver comfort and experience.

How Field-Centric Drive Works

Field-centric drive works by using the robot's current heading from the IMU (Inertial Measurement Unit) to transform joystick inputs before they are applied to the drivetrain.

The driver still uses the same controls as a standard FTC mecanum drivetrain:

• Left Joystick X → Strafing
• Left Joystick Y → Forward/Backward movement
• Right Joystick X → Rotation

The difference is that the translational inputs (X and Y) are adjusted using the robot's heading, while the rotational input remains unchanged. This allows movement to remain aligned with the field instead of the robot's orientation.

The process follows these general steps:

Joystick Input
↓
Read IMU Heading
↓
Apply Mecanum Equations
↓
Motor Powers

For example, if the robot turns 90 degrees, the software compensates for that change in orientation. As a result, pushing the joystick forward still moves the robot forward relative to the field, regardless of which direction the robot is facing.

Field-Centric Drive: The Math Behind the Controls

Field-centric drive works by mathematically rotating the driver's joystick input based on the robot's heading from the IMU. This allows the robot to maintain field-relative movement regardless of its orientation.

The process can be summarized in three steps:

1. Read joystick input (x, y)
2. Rotate the input using the robot heading (θ)
3. Apply the corrected values to the mecanum drive equations

The coordinate transformation used for field-centric control is:

x′ = x cosθ + y sinθ

y′ = y cosθ − x sinθ

Where:

• x = strafe input
• y = forward/backward input
• θ = robot heading from the IMU
• x′, y′ = corrected field-relative movement commands

These equations rotate the joystick input to compensate for robot orientation while preserving the driver's intended direction of travel.

The corrected values are then used in the mecanum drive equations:

FrontLeft = y′ + x′ + rx

BackLeft = y′ − x′ + rx

FrontRight = y′ − x′ − rx

BackRight = y′ + x′ − rx

Where rx represents the driver's rotational input.

For example, if the robot is rotated 90° and the driver pushes the joystick forward, the software adjusts the input before calculating motor power. The result is that the robot continues moving forward relative to the field, even though it is facing a different direction.

Key Considerations Before Implementing a Field-Centric Drive

Field-centric drive can improve driver performance, but it also introduces additional system complexity. Before implementing it, teams should evaluate whether their robot, software, and drivers are ready for the added requirements. Here are the key questions teams should ask themselves.

Team Readiness Checklist

Before implementing field-centric drive, confirm the following:

☐  Fully working mecanum drivetrain
☐  Motor directions tested and verified (robot moves correctly in robot-centric mode)
☐  Understanding of robot axes: forward, strafe, rotation
☐  IMU properly configured in the control system
☐  IMU calibrated with stable heading output
☐  Joystick inputs correctly mapped (no X/Y inversion issues)
☐  Consistent robot-centric control before adding field-centric logic

Common Field-Centric Setup Issues

Field-centric drive may behave incorrectly if any of the following are not configured properly:

☑️ IMU mounted in a different orientation than defined in code
☑️ Missing or inconsistent IMU calibration
☑️ Heading drift during operation
☑️ Swapped forward/back or left/right axes
☑️ Incorrect motor direction inversion
☑️ Unpredictable robot behavior when rotated

Field-Centric Drive vs Robot-Centric Drive

Both control styles are valid in FTC. The right choice depends on the team's experience, driver preferences, and software maturity.

Field-Centric Drive Pros & Cons

Robot-Centric Drive Pros & Cons

Frequently Asked Questions

Do I need an IMU for field-centric drive?

Yes. Field-centric drive relies on an IMU (Inertial Measurement Unit) to determine the robot's current heading. Without heading information, the robot cannot compensate for its orientation relative to the field.

Does field-centric drive only work with mecanum wheels?

No. Field-centric control can be used with other omnidirectional drivetrains, but it is most commonly implemented in FTC mecanum drivetrains because they can move in any direction without turning first.

Is field-centric drive better than robot-centric drive?

Not necessarily. Many teams prefer field-centric controls because they are more intuitive, but robot-centric drive is simpler to implement and can be easier to troubleshoot. The best choice depends on driver preference, team experience, and robot design.

Why does my field-centric drive behave incorrectly?

Common causes include incorrect IMU orientation settings, heading drift, swapped joystick axes, incorrect motor directions, or errors in the coordinate transformation equations.

Should rookie FTC teams use field-centric drive?

Rookie teams can certainly use field-centric drive, but it is usually best to first ensure the robot drives reliably in robot-centric mode. Once the drivetrain, motor directions, and controls are working correctly, field-centric control can be added as an upgrade.

Final Thoughts

Field-centric drive is a popular control method in FTC because it allows robot movement to remain aligned with the field rather than the robot's orientation. By using an IMU to track heading and applying a simple coordinate transformation, teams can create a more intuitive driving experience that reduces the need for constant mental reorientation during matches.

While field-centric drive introduces additional software complexity and requires a properly configured IMU, many teams find the benefits worthwhile, especially when using mecanum drivetrains. Whether your team chooses field-centric or robot-centric control ultimately comes down to driver preference, experience, and what works best for your robot and game strategy.

Related Articles

• FTC Mecanum Drive Programming Tips
• Build a Mecanum FTC Chassis in Your Team Colors
• Create a Fast & Versatile Mecanum Chassis for Your FTC Robot
• How to Build a Mecanum Drivetrain – Instructions
• Choosing the Right Drivetrain for Your Robot

Quick Summary: This article walks FTC teams through everything needed to program a mecanum drivebase using the FTC Drive Base Kit from Studica Robotics. You’ll learn how mecanum wheels work, how to configure motors in the Driver Hub, build a working TeleOp program, create a basic autonomous routine, and improve performance through tuning techniques like dead zones and input scaling. Whether you're new to FTC or refining your drivetrain, this is a practical, team-ready resource for building smoother, more precise robot control.

Mecanum Drive Programming Fundamentals

Mecanum drivetrains are one of the most powerful and flexible systems used in FTC robotics. When programmed correctly, they allow your robot to move in any direction - forward, backward, sideways, and rotationally - all independently. This article is designed to help teams using the Studica Robotics FTC Drive Base Kit, though the concepts apply to any FTC mecanum drivetrain. For this tutorial, we’ll use a mecanum drivebase built with the mecanum wheel set from Studica Robotics, along with an FTC Control Hub, Driver Hub, and a standard FTC-legal gamepad. All programming will be done in Blocks through the Control Hub’s web-based interface.

How Do Mecanum Wheels Work?

[caption id="attachment_22015" align="alignright" width="300"] Force Diagram of Mecanum Wheel[/caption] Mecanum wheels use rollers positioned at a 45° angle. Instead of pushing straight forward like traditional wheels, each wheel produces a diagonal force vector. That force can be broken into:

• Fy → Forward and backward motion
• Fx → Sideways (strafing) motion

A single wheel alone isn’t very useful, but when all four wheels work together, those forces combine and cancel in specific ways to create controlled movement.

Correct Mecanum Wheel Configuration

A mecanum wheel has angled rollers that create force vectors at 45 degrees. When these forces combine across four wheels, the robot can move forward, backward, sideways, or rotate. The “X” wheel configuration:

• Forces cancel or combine depending on the direction of travel
• Forward motion cancels sideways forces
• Strafing cancels forward forces
• Rotation creates torque around the robot's center

This is what makes mecanum drivetrains holonomic, allowing full directional movement without turning first.

Force Diagram of Each Wheel in a Mecanum Drivebase

X Pattern of Wheels in a Mecanum Drivebase

Hardware Setup (Driver Hub Configuration)

Before coding, you must configure the robot hardware in the FTC Driver Station. This tells the Control Hub which ports each electrical device, such as motors, servos, and sensors, is connected to.

Accessing the Configuration Menu

1. Power on the Control Hub and Driver Hub.

2. Open the Driver Hub and connect to the Control Hub. To get to step 3, teams would need to open the Drive Station App built into the driver hub.

3. Tap the three dots (⋮) in the top-right corner.

4. Select Configure Robot.

Create a New Configuration

1. Tap “New”

2. Select your hardware type (Control Hub) and click on the “Control Hub Portal”

3. You will see a list of available ports.

How to Assign Motors to Ports

1. Tap on a Motor Port (example: Port 0)

2. Assign each motor port to the correct motor and name each motor

3. Name the motors based on the drivetrain’s perspective (front, back, left, right). For this configuration, our motors are labeled as:

  Tip: Use consistent directional names like frontLeft, frontRight, backLeft, and backRight. This prevents confusion later in programming.

TeleOp Programming (Driver Control)

The example TeleOp program shown below uses a simple block-based structure, making it easy to map driver inputs directly to robot movement controls. The information in this section introduces the key concepts you’ll need to understand before working through the drag-and-drop version of the program.

Control Mapping and Motion

Use the following control mapping as a reference for robot movement. The left joystick controls forward/backward and strafing, while the right joystick controls rotation.

Motor Behavior Setup

Before writing any movement logic, the drivetrain motors need to be configured so they respond correctly during operation.

Motor Direction

Because the motors on opposite sides of a mecanum drivetrain face opposite directions, one side must be reversed. This ensures that when the robot is commanded to drive forward, all four wheels spin together in the correct direction. Here is the code showing motor direction configuration, where one side of the drivetrain motors is reversed so all wheels rotate correctly for forward movement. This code determines how motors will behave when not powered.

Zero Power Behavior

Zero Power Behavior determines how the robot responds when no power is being applied. Setting this to BRAKE causes the motors to stop immediately and hold their position when the driver releases the joysticks. The drivetrain will stop immediately and try to hold its position. This provides more precise control during TeleOp. Here is the code setting drivetrain motors to BRAKE mode, causing the robot to stop immediately and resist rolling when joystick input returns to zero.

Declaring Variables

Next, create the variables that will control robot movement. These variables represent the three primary directions of the mecanum drive, along with a scaling value used to normalize motor power.

• Y → Forward and backward movement
• X → Side-to-side strafing movement
• Z → Rotation left and right
• Denominator → Scales motor powers proportionally so no value exceeds the allowed range, ensuring smooth and accurate movement

Here, the code is creating variables for mecanum drive control, including forward/backward, strafing, rotation, and motor power normalization.

Why Normalizing Motor Power Matters

When multiple joystick inputs are combined, motor power values can exceed the allowed range of -1.0 to 1.0. Normalization scales all motor values proportionally so the strongest motor runs at full power while preserving the intended direction of movement. Without normalization, motor values are clipped, which causes uneven power distribution and unpredictable motion.

Mecanum Motor Power Equations

Each wheel receives a combination of X, Y, and Z values. These equations determine how forces combine to produce omnidirectional movement.

• frontLeft = Y + X + Z
• backLeft = Y − X + Z
• frontRight = Y − X − Z
• backRight = Y + X − Z

Each value is then divided by a normalization factor when necessary.

Why This Works

• Y controls forward and backward movement.
• X controls sideways strafing.
• Z controls rotational torque.

Because each wheel contributes differently, combining these inputs creates full omnidirectional motion.

Autonomous Programming

Before diving into the full autonomous example, it’s important first to understand the foundation of Autonomous Programming in FTC. This section begins with Initialization and Calling Functions, which set up how the robot’s motors and systems will behave before any movement starts. Defining motor behavior early ensures your autonomous runs accurately and consistently, while clearly structuring functions helps you understand what each part of your code is responsible for before putting everything together into a complete autonomous sequence.

Initialization

As previously demonstrated in the TeleOp example, set the motor direction so that the all the wheels move in the same direction to drive forward. Then set the motors so that all the wheels brake when motor power = 0

Calling Functions

For this autonomous example, each movement of the robot is separated into its own function. A function is a reusable block of code to perform a specific task. So instead of repeatedly writing the same motor commands, you can group them into a single function and call those commands whenever needed. Create the following functions below. These functions define the motor outputs to perform each movement. The “STOP” function sets all motor power to zero, ensuring the robot halts before executing the next action

Basic Autonomous Example

Autonomous code runs sequentially from top to bottom. Each block is executed in order, one after another. A simple FTC autonomous routine often begins with timed movements. Here is an example flow:

• Move forward (1.5 seconds) - Here is a code example:
• Stop (1 second) - Here is a code example:
• Strafe right (0.5 seconds) - Here is a code example:
• Stop (1 second)
• Rotate left (1.5 seconds) - Here is a code example:
• Stop

Improving Control and Tuning

1. Deadzone (Fix Stick Drift)

Deadzones prevent unintended motion when the joystick is near zero.

• Helps eliminate drift
• Improves stability at rest

Tradeoff: Too large of a deadzone can reduce fine control.

2. Input Scaling

Input scaling reduces maximum speed for better precision.

• Example: 1.0 × 0.8 = 0.8
• Makes the robot easier to control

Tradeoff: Lower maximum speed.

3. Strafe Compensation

Mecanum wheels are typically less efficient when moving sideways than forward. Slightly increasing the X input can improve balance between strafe and forward speed.

Troubleshooting Common Programming Issues

Here are some common issues FTC teams face when programming their mecanum chassis, along with helpful tips to fix them.

Telemetry (Your Best Debugging Tool)

Telemetry helps teams debug by showing live data from the robot while the code is running. Instead of guessing what the robot is doing internally, telemetry lets you see exactly what the robot thinks is happening in real time.

In FTC programming, you typically use telemetry during testing to compare what you expect the robot to do with what it is actually doing. If something looks wrong, telemetry helps you narrow down whether the issue is coming from the controller inputs, your code logic, or the motors themselves.

Telemetry Debugging Overview

Here are some of the most common things teams use telemetry to check:

This is one of the most valuable debugging tools in FTC programming because it turns invisible code behavior into clear, readable information you can act on immediately.

Where Studica Robotics Fits In

The Studica Robotics FTC Drive Base Kit is designed to make mecanum programming easier by providing:

• Pre-engineered drivetrain geometry
• FTC-compatible motor configuration
• Consistent mechanical alignment for smoother strafing
• A reliable starting point for learning drivetrain programming

This allows teams to focus less on mechanical inconsistencies and more on learning core robotics concepts like kinematics, control systems, and autonomous design.

Frequently Asked Questions

What is mecanum drive in FTC? Mecanum drive is a holonomic drivetrain that allows a robot to move in any direction without turning first. Why do FTC teams use mecanum wheels? They provide full directional movement, making scoring, alignment, and positioning faster and more efficient. Why is my mecanum robot drifting? Common causes include incorrect motor direction, missing normalization, joystick drift, or mechanical misalignment. Do I need to normalize motor power? Yes. Without normalization, combined inputs can exceed motor limits and cause unpredictable movement. What is the best way to learn FTC mecanum programming? Start with TeleOp control, then add tuning features like deadzones and scaling. Once you're comfortable, move on to encoder-based autonomous routines.

Conclusion

Programming an FTC mecanum drivetrain is one of the most important skills for competitive robotics teams. Once teams understand how forces combine across all four wheels, they can unlock smooth omnidirectional movement, precise driver control, and reliable autonomous performance. With the Studica Robotics FTC Drive Base Kit, teams gain a strong mechanical foundation, allowing them to focus on what really matters: writing smarter code, improving control, and building better autonomous strategies.