FIRST TECH CHALLENGE BIOBUZZ 2026–27

We don't just build robots.
We learn why they work.

We're TECHNADOS, Team #7693. Every student has a voice in what we design, what we test, and what we do next. We turn ideas into experiments, experiments into evidence, and evidence into better decisions. Our Legacy catapult and developing flywheel Shooter give us two very different engineering challenges.

7693 / ROBOTICS + REASONINGSCROLL TO EXPLORE
TECHNADOS / ENGINEERING STUDY2026—27
Conceptual drawing of our Legacy competition robot Illustrative overhead schematic showing a mecanum drivetrain, front intake, rear three-position release mechanism and internal engineering systems. Not a measured CAD drawing. RELEASETHREE LATCHES ENCODERFEEDBACK FRONTINTAKE SCHEMATIC / NOT TO SCALE X / Y REFERENCE

The robot is the project.
The process is the point.

Ideas don't become decisions because someone speaks the loudest. We talk them through, build them, test them, and use what we learn to decide what comes next.

01

Ask

Start with a problem worth solving. Every member can bring an idea or challenge an assumption.

02

Prototype

Sketch, program, fabricate and try alternatives before committing to a design.

03

Measure

Run controlled tests. Record what happened, including results that challenge our expectations.

04

Explain

Share the evidence, discuss what it means, and make the next decision together.

No spectators.
One team.

Our members are middle-school students, but the work is real engineering. We don't separate people into permanent boxes. Students learn from each other and contribute across design, programming, testing, strategy and presentation.

Every idea gets heard. Every member has a part in the answer.

Design and prototype

We break into groups to explore mechanisms, evaluate ideas, and build things we can learn from.

Program and debug

Students help shape how the robot moves, senses, responds and recovers, then study the results of each change.

Drive and test

Practice creates feedback. Drivers and engineers work together to turn observations into more reliable behavior.

Scout and strategize

When we're not driving, we're observing other teams, comparing notes, and building relationships at events.

Present and reflect

Students explain what they tried, what the evidence showed, and what they would improve next.

Two robot systems.
One engineering mindset.

Our Legacy competition robot and our developing Shooter configuration solve different mechanical problems. Studying both helps us connect what we design, what the robot reports, and what we still need to prove.

01 / COMPETITION PLATFORM BUILT & TESTED
Functional schematic of the TECHNADOS Legacy competition robot Not-to-scale view of four mecanum wheels, front intake, rear three-latch catapult, a shared tension arm with home feedback, and localization sensors. Placement and geometry are illustrative, not verified CAD. 3 LATCHESSHAREDTENSIONFRONT INTAKE FUNCTIONAL SCHEMATIC / NOT TO SCALE

THE LEGACY ROBOT

Mechanical control you can measure.

BIOBUZZ
2026–27

A front intake feeds a rear catapult with three independently released scoring positions. One motor tensions the shared arm, while encoder feedback and a HOME switch help the team investigate repeatability and recovery.

DRIVETRAIN
Four-wheel mecanum, with field-relative driving
POSITION REFERENCE
Pinpoint localization with two odometry pods
SCORING MECHANISM
Shared tension arm, three independent latches
AUTONOMOUS
Blue and red leave/park and scoring routines
WHAT WE INVESTIGATE

How accurately does the arm settle? When is it truly HOME? Can the full scoring-and-parking sequence repeat under match conditions?

02 / NEXT DEVELOPMENT DIRECTION PHYSICAL VALIDATION PENDING
Conceptual functional flow of the planned dual-flywheel Shooter robot A conceptual left-to-right intake, two independently driven opposing flywheels, a firing linkage, and an outgoing game element. This is not a verified physical layout or launch direction. INTAKEDUAL FLYWHEELSRELEASE ELEMENT FLOWINDEPENDENT SPEED FEEDBACKDIRECTION TBDFUNCTIONAL CONCEPT / LAYOUT NOT VERIFIED

THE SHOOTER PROJECT

A different way to launch.

IN
DEVELOPMENT

Our planned Shooter explores two independently regulated flywheels and a staged firing sequence. The development software can manage wheel-speed feedback and shot timing, while the physical launcher, aiming, and scoring performance still need testing.

MOTION FOUNDATION
Mecanum drive with provisional Pinpoint setup
LAUNCH CONCEPT
Two opposing, independently driven flywheels
SHOT SEQUENCE
Spin up, engage, recover, repeat
STILL TO VALIDATE
Mounting, firing direction, feeder, angle and scoring
WHAT WE WANT TO LEARN

How consistently will both wheels reach speed? What timing delivers a repeatable shot? Which mechanical design performs best once tested?

These diagrams explain documented system concepts, not exact assembly drawings. Legacy competition tests have bounded, dated acceptance evidence; the Shooter software foundation is separate from physical mechanism acceptance. We do not display private recordings, student information, or robot source code.

What happened is the beginning.
Why it happened is engineering.

On our BIOBUZZ competition robot, a successful action is only part of the story. We also investigate how the mechanism reached that point, whether it behaved consistently, and what the controller actually reported. Our real mechanism provides the questions; the illustration below shows the reasoning, not a recorded run.

ANATOMY OF A TEST / ARM POSITION STUDY
ILLUSTRATIVE EXAMPLE · NOT A RECORDED RUN

READ THE EVIDENCE

See more than a final number.

A controller can report that the arm approached its target. Our questions go further: Did it settle cleanly? Was the sensor reference valid? Was the behavior repeatable?

A commanded position and controller-reported position are different kinds of information. Comparing them is where an investigation begins.
POSITION THROUGH A TESTCONCEPTUAL / NO NUMERIC SCALE
Illustrative arm command and response chartBlue stepped command line and green position response line; control buttons reveal how to interpret motion, settling and a decision from the comparison. No values are real measurements. STARTSAMPLES OVER TIMEENDARMPOS. MOVESETTLE?RETURN REVIEW THESETTLING BEHAVIOR
Commanded position Controller-reported position
WHAT THE DATA SUPPORTSTwo signals, two different meanings.

Our goal isn't to turn a chart into a claim. It's to make the source, assumptions, uncertainty and reasoning visible so anyone on the team can challenge or improve the conclusion.

THE TECHNADOS APPROACH

Good engineering knowledge
shouldn't live in one person's head.

Code, controller logs, prototypes, design changes, practice observations and scouting notes tell parts of the same story. TECHNADOS is our browser-based engineering workspace, built to connect those pieces for the students and mentors who need them.

SOURCESORIGINAL CONTEXT PRESERVED
{ }
Robot configuration & sourceWHAT WE INTENDED TO RUN
01
⌁
Controller recordingsWHAT THE ROBOT REPORTED
02
◇
Prototypes & test notesWHAT WE TRIED AND CHANGED
03
▦
Student scoutingWHAT TEAM MEMBERS OBSERVED
04
TECHNADOS
ENGINEERING STUDIO

One place to investigate, visualize, compare and share evidence within authorized team workspaces.

↗Make behavior understandable
↔Compare ideas and iterations
◎Keep every contribution connected
✓Separate evidence from assumptions
A GROWING PLATFORM → Team access

The platform is developed in stages. Illustrations on this page describe our engineering approach, not a claim that every planned analysis feature is already available. Private robot evidence and student records are not published here.

The match isn't the only place we work.

While the drive team is preparing or competing, other students have a job too: meet teams, observe robots, collect pit and match information, and help our team make thoughtful decisions.

Scouting is more than recording a score. It means asking what another robot can do, how reliably it does it, and how our teams could work together.

Everyone contributes. The drive team uses what the whole team learns.

SCOUTING / HOW EVIDENCE CONNECTSILLUSTRATIVE WORKFLOW
01 / COLLECT

Student observations

POLLEN / NECTARSeparate capabilities
AUTONOMOUSBehavior & reliability
DRIVER PERIODPatterns & notes
02 / COMPARE

Source-aware review

Student reported Official records Unknown / not observed

Different sources stay distinguishable. Missing observations don't turn into a guessed “no.”

03 / DISCUSS

Next-match preparation

Review observations together, identify complementary strengths and open questions, and make a team decision.

Build something.
Understand it.
Share what you learned.

The best part of building a competition robot is what the whole team learns along the way. Our goal is to make that learning visible, useful and accessible to every member.