Entry 6

On the agenda for today is advancing the programming teams knowledge, and starting to build the design for the robot.

• • • Hardware team begins building the GoBilda Stafer Chassis.

Programming team works on learning more about Odometry.

• The programming team uses their previous knowledge and newly acquired knowledge by watching a playlist on Odometry to tackle a program in a different way.

The GoBilda Strafer Chassis will serve as the basis on which we build the rest of our robot for this year's FTC Challenge.

• • • While half the team works on assembling the parts they found, the other half of the team works on finding the rest of the parts needed.

      • • They reference the assembling instructions for the GoBilda Strafer Chassis (https://www.gobilda.com/content/user_manuals/3209-0001-0002%20Assembly%20Instructions.min.pdf) as well as the official part number ID's on the GoBilda website (https://www.gobilda.com/strafer-chassis-kit/).

          • Despite having the part ID's, we face problems while finding the parts on OnShape.

            • • Certain ID's didn't match up to those on OnShape, or the exact parts weren't on OnShape. We improvise and find parts that will fit the criteria necessary for the assembly, even though they aren't the exact ID's listed GoBilda Strafer Chassis assembly instructions. If the ID numbers are off by a couple digits, we inspect the part. If it seems to look exactly like the one listed, we pull them onto the document for use.

The programming team lead by Ahmed works on making the program on floobit.

• Though we face a few problems while using floobit, we are able to correct them after some trial and error.

• We attempt to fix the problem by carefully going through each problem, even if it took a long time.

Today, we find most of the parts that we need to assemble the GoBilda Strafer Chassis. We fasten a few parts together.

• • Yuga finda and fastens the mecanum wheel assemblies together.

    • • Astrid start the axel assemblies, but is unable to finish due to lack of time and mating issues she ran into.

        • Benjamin and Vanisha continue to gather the parts that are needed to assemble the whole design.

Our team finds that some parts are hard to fasten due to the malfunctioning of certain features on OnShape. We are unable to fasten them in the correct positions.

• • • Astrid has trouble attaching the Hub Mount Bevel Gear to the Hyper Hub for the axel assembly. Due to her unfamiliarity with the mating feature on OnShape, she has to go through documentation to learn how to fasten the part.

    • Yuga works on fastening the Mecanum Wheel assemblies, and is able to attach them without much trouble.

      • • The rest of our team spends the meeting looking for some of the parts for the Strafer chassis.

By Friday we plan on assembling all the pieces for one side of the chassis.

• • • When our team finishes one side, we can copy and rotate it because both sides are symmetrical.

      • • Both sides will need to be connected with two channels to finish the design.

The agenda for the today is to learn about odometry. Odometry is a very accurate way of measuring your robots position on the field independent of the motors.

• • Together, we watch a playlist about odometry. Then, we work on a program that we have previously done. However, we have to implement the techniques we learn and already knew to complete the program in a different way.

While we want to work on our program, we encounter glitches on Floobits. We spend our time trying to fix the Floobits errors.

We solve the problem by taking it one error at a time, and analyzing how each person’s Android Studio is affected.

We change our program to implement odometry instead of using encoders and IMU because it was more efficient.

• • Our goal is the same: to make the robot go in a square.