Entry 23

Everyone on the Hardware team is working on completing the second course on Onshape.

The agenda for the Programming team is to organize and review all the code we have till now. After that, we are having a discussion with the rest of the team about how to use and incorporate Kotlin in our code.

• We also will be devising a way to make our code more simple and accessible for the team.

Today, the hardware team is continuing their training week and working on their second course on Onshape, “Onshape Assemblies.” Each person works separately on this task as before, and our hope is that these lessons will improve our efficiency on the actual robot CAD.

In the programming team, we are successfully starting using Kotlin in our programs as it is a simpler to understand and an easier way to test our code.

• We are gaining a stable understanding on the program we are creating through researching and asking questions.

In the future, before we start the other rings in the software, we want to include the code to fire the preloaded rings.

• The programs should also be replicated in Java as our project is based on Java.

Everyone on the Hardware team is working on completing the second course on Onshape.

This course continues to build upon the mating features mentioned in the previous course.

• Specifically it goes into depth on creating mates for when they are non existent.

The most important lesson in the course was on assemblies and creating subassemblies/part studios.

• Previously, our team has not explored the different workspaces that could be created on OnShape.

The course includes the following assemblies: Workspaces where different mechanisms can be built, and Orta can be attached. When it comes to our robot, we would much benefit from separating all our different mechanisms into different assemblies. Since assemblies can be brought into other assemblies, already built, we are able to build our shooter and intake in separate assemblies and bring them to a main assembly where our chassis would be.

• • This is also helpful because it would organize the fastenings for each mechanism. Instead of having over 100 fastenings to search in one assembly when something goes wrong we will be able to isolate the fastening from each mechanism if editing was needed in a separate part of the robot.

• Workspaces where custom parts are built and parts can neither be pulled out nor attached. This is the place where custom parts, holes, or edits would be made. There is the possibility of us needing custom 3D printed parts; thus it is useful for the whole team to know about the features in part studios, especially if we need to make custom parts and collaborate with the Specialty parts team.

Our goal for today is to review our code and to understand our code that uses Kotlin.

• Formulate our code in a way which makes it easier for the team to look back at it.

Over the course of the week, we are continuously refining our code and changing the code to be more structured.

During the arranging process, we are all able to understand what the our program does on a greater degree. It is an autonomous program which deals with turning accordingly based on the lines on the field.

• The team has questions about the autonomous program which Shaurya and Ahmed answer with thorough explanations.

When testing the program, the testing process of the code was easier because the code was written in Kotlin.

• After, we are developing another code using Kotlin.

In the future, we want to include the code for shooting the preloaded rings before we pick up the other rings in the program.

• The programs would also have to have copies in Java since our project is a Java-based project.