Team portal ↗

3171 / YOUR ROBOTICS UTILITY BELT

Every skill opens
a new possibility.

Choose a branch. Build something. Show what you learned. Earn coach-reviewed rank points and core mastery badges in the team portal.

0 / 28practice challenges completed

Practice progress stays in this browser on this device. It is self-reported, not a coach-approved badge or portal reward.

EXPAND YOUR UTILITY BELT

Choose your next mastery.

Follow an ordered pathway, build an original project, and submit evidence in the protected portal. Practice, submission, approval and rank points are separate steps.

Autodesk Fusion · CAD

Design editable parts and mechanisms for Team 3171. Fusion is the introductory Autodesk option; Onshape remains available.

Programming · Java and WPILib

Write understandable, testable robot code; begin in simulation before supervised hardware.

Animation · Krita

Build original visual assets with readable Team 3171 colors.

Animation · Blender

Explain robotic motion through original 3D models and animation.

3D Printing · Bambu Workshop

Design, print, inspect and improve useful team parts on the Bambu X1C. A1 Combo and A1 mini profiles are included for when they return to service; every robot-use part still needs coach review and current FRC rules verification.

FIRST 3D Parts · Design Challenges

Model original, useful FRC-adjacent parts in Onshape or Autodesk. These are learning references, not vendor files: a coach must approve every print and any robot use.

Scouting and Strategy

Turn observations into evidence-based team decisions; keep strategic data private.

Choose your path.

java

Java → FRC programming

CAD

Onshape & robot CAD

printing

3D print for the team

simulation

Robot code without a robot

electrical

Understand the control system

github

GitHub & code collaboration

missions

Put a skill to work for 3171

Your utility belt.

Each completed practice adds a tool here. Bring your work to a mentor for feedback.

Reset this device’s practice progress?

This only clears this browser’s skill tree. It does not change portal records.

Full tutorial library & meeting routine

LEARN / PRACTICE / BUILD

Build your next skill.

Official tutorials and suggested practice for FRC students. Choose a starting point with a mentor and leave each meeting with something you can show.

Every meeting1. Punch in2. Choose one goal3. Learn & build4. Show your result5. Punch out
Start Java →Start Onshape →Open team portal ↗

Learning links are public. Attendance requires an invited, approved portal account. Practice ideas below are suggestions to agree on with your mentor.

01 / BEGINNER

Java → FRC programming

Start with variables, conditions, loops, methods, and classes. Then use those ideas in a robot project.

Try it at a meeting

Write a method that limits a requested motor speed to a safe range. Explain the input, output, and boundary cases to a partner.

Use the team’s WPILib installation and matching Java version for robot projects. Ask a programming mentor before changing the toolchain.

02 / BEGINNER

Onshape & robot CAD

Learn navigation, constrained sketches, dimensions, extrusions, parts, and assemblies before designing a full mechanism.

Try it at a meeting

Model a simple mounting plate with dimensioned holes. Change a dimension, inspect the result, and show a teammate how the sketch controls the part.

An Onshape account may be required. Use your team-approved education account and sharing settings.

03 / BAMBU WORKSHOP

3D print for the team

Use the Bambu X1C to design, print, measure, and improve original team tools and prototypes. The A1 Combo and A1 mini are future printer profiles once repaired.

Try it at a meeting

Start with a FIRST 3D Parts design challenge: a spacer, tube end cap, cable clip, sensor mockup, roller insert, guard, or pit organizer. Measure it, test its fit, and revise it before submitting evidence.

Preseason training only: do not put a printed part on a robot until a coach reviews its fit, load, safety, service access, and the current official FRC rules. The 2027 game manual will control competition legality.

03 / AFTER JAVA BASICS

Robot code without a robot

Use WPILib simulation to practice controls and observe what the program does before working with hardware.

Try it at a meeting

Run a simulated example. Identify one subsystem and one command, then explain when the command starts, runs, and ends.

Build a small working example first. Progress to sensors, autonomous routines, and mechanism control with a mentor.

04 / CONTROLS & ELECTRICAL

Understand the control system

Learn how robot power, the controller, communications, sensors, and code connect.

Try it at a meeting

Draw a labeled diagram of a motor-control signal path and the power path. Have an electrical mentor check it against the actual robot.

Read the documentation for the hardware and software versions your team uses. Physical wiring and powered tests need mentor supervision.

05 / TEAMWORK

GitHub & code collaboration

Learn how to save changes, explain your work, and review code with teammates.

Try it at a meeting

In a mentor-approved practice repository, make a small change on a branch and open a pull request explaining what changed and how you tested it.

Ask for a review and respond to the feedback before merging.

06 / APPLY WHAT YOU LEARN

Put a skill to work for 3171

Connect a tutorial to your current mission, mechanism, presentation, or team responsibility.

Try it at a meeting

Show one concrete result: a CAD part, working program, test observation, wiring diagram, or improved team document.

Ask a mentor to review your evidence and help choose your next step.