Design and prototype
We break into groups to explore mechanisms, evaluate ideas, and build things we can learn from.
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.
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.
Start with a problem worth solving. Every member can bring an idea or challenge an assumption.
Sketch, program, fabricate and try alternatives before committing to a design.
Run controlled tests. Record what happened, including results that challenge our expectations.
Share the evidence, discuss what it means, and make the next decision together.
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.
We break into groups to explore mechanisms, evaluate ideas, and build things we can learn from.
Students help shape how the robot moves, senses, responds and recovers, then study the results of each change.
Practice creates feedback. Drivers and engineers work together to turn observations into more reliable behavior.
When we're not driving, we're observing other teams, comparing notes, and building relationships at events.
Students explain what they tried, what the evidence showed, and what they would improve next.
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.
THE LEGACY ROBOT
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.
How accurately does the arm settle? When is it truly HOME? Can the full scoring-and-parking sequence repeat under match conditions?
THE SHOOTER PROJECT
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.
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.
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.
READ THE EVIDENCE
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?
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 APPROACHCode, 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.
One place to investigate, visualize, compare and share evidence within authorized team workspaces.
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.
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.
Different sources stay distinguishable. Missing observations don't turn into a guessed “no.”
Review observations together, identify complementary strengths and open questions, and make a team decision.
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.