Research & Learning

Data, Code, and Iteration

We document decisions, test new ideas, and learn fast to improve the robot.

Learning & Programming

Highlights from Java onboarding and early software tests.

Create a new OpMode and choose a sample template (BlankLinearOpMode).
Use “Setup Code for Configured Hardware” to auto-generate hardwareMap entries.
Build Everything compiles all files; disable incomplete OpModes to avoid errors.
Ensure the intended configuration is active before using Setup Code.

arm = hardwareMap.get(DcMotor.class, "arm");
waitForStart();
while (opModeIsActive()) {
  arm.setPower(gamepad1.left_stick_y);
}

Initial motor control tested on December 2–3, 2025.

Multithreading experiment: Runnable-based test completed on December 5, 2025.

Early season notes and milestones.

[15:30] Ainsley from Hearts Innovation Centre speaks to us and informs us of what the tech challenge is about and that we are invited to it.
[16:10] All depart.
[18:45] A Discord chat was created for our team where we share information and discuss tasks.

[12:06] We unpacked the starter kit, created an Excel inventory, and checked all parts against the kit list.
[12:15] Mechanics team started building the robot frame following the booklet.

[15:35] Team meets.
[15:40] Java program for the first motor is written while mechanics builds the robot infrastructure. First motor works.
[17:00] All depart.

[15:40] Controllers working with both motors. Frame complete; external parts fixed. Discussed ideas for shooting mechanism.
[17:30] Team departs.

[10:30] Team goes to Hearts stadium for scrimmage.
[10:40] Worked on software and robot; feeder on the back while software team develops movement program.
[13:55] All depart.
[15:30] Team meets; program works with feeder system. Sponsors team reaches out to potential sponsors.
[17:00] Team departs.

[9:45] Sponsors team reaches out to more sponsors; emailed 16–17 new sponsors, plus snack sponsors.
[12:30] Continued sponsor outreach and sent additional emails.