Embedded Files
Author: Ria G. and Caitlyn Mei R.
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 10/2/2020
Duration: 5:00 - 6:30
TABLE OF CONTENTS
Attendance
Ahmed Mahmud
Hooryah Raja
Murtaza Raja
Manyata Arora
Amanpreet Dhah
Caitlyn Mei Roxas
Abrahim Mahmud
Shaurya Singh
Benjamin Fitzgerald
Martina Soliman
Anirudh Chaturvedula
Ria Gray
Asmi Shirsat
Abriti Chatterjee
Tessa Weaver
Leonard Malott
Mary Dawod
Arleen Dhah
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Atharva Khandelwal
Ved Borade
Tvisha Doshi
Venya Goyal
Eva Ji
Prajwal Khanal
Lutfiyah Mohammed
Sivaditya Padmanabhan
Yuga Patel
Vanisha Rajlakshmi
Astrid Salazar
Ehtesham Suhail
Alisha Varma
Ashita Birla
Syed Shah
Mark Rajah
Luniva Joshi
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Team Planning
Agenda
The programming team implements the RoadRunner GUI into their Android Studios.
They also create the foundation for a program that will hopefully allow the robot to move from anywhere on the mat to the stack of rings and position itself facing the power shot target.
The specialty parts team's goal for today is to upload the bumper guards onto Onshape.
The robot design team's agenda for today is to test different chains out for the robot, and also to gather some necessary parts that are needed for the intake mechanism.
Reflection
The programming team installs and navigats the RoadRunner GUI.
The programming team also creates the basis of a code we hope to further develop in the future to use in most, if not all, of our programs.
The specialty parts team is able to upload the bumper guards onto Onshape after running into some issues.
Next meeting, we plan on putting the odometry piece into the part studio folder for the robot design team to use. We have to also make sure that the type of file that the part is in is correct.
The robot design team is able to test different chains.
We plan on finishing the first set of wheels for the intake mechanism. We also plan on working out a way to drive all of the components of the complete design. We have some ideas for this whole process.
Hardware
Agenda
Specialty Design Team:
Today, we continue what we have been doing during the last meeting, which is to continue to download the bumper guards.
Robot Design Team:
Today, we focus on gathering parts that are essential to the construction of the intake mechanism. We also focus on testing out different chains for the robot.
Reflection
Specialty Design Team:
We run into issues that are from the last meeting, where Arleen and Caitlyn are not able to edit anything. To solve this issue, Arleen and Caitlyn have to create new accounts for Onshape. Today, they are added back to the team on Onshape. After this, we proceed to import the bumper guards. This task is successful.
As for our future plans, we plan on putting the odometry piece into the part studio folder. Importing is not difficult, but making the file the right type is very crucial. We want the files to be .stl, so that we can edit them in Onshape, and converting them from their old file type may or may not be possible.
Robot Design Team:
Today, we focus on two different topics. The first one is gathering parts for the construction of the intake mechanism, and the second topic that we focus on is testing out different chains for the robot.
For our next meeting and other meetings in the future, we plan to finish the first set of wheels for the intake mechanism. We need to work out a way to drive all the components of the complete design. We are leaning towards using chains and sprockets for this task. We will also be gathering more parts and exploring the options we have.
We have some ideas for this. Our current idea is to build the rest of the project in two phases: The intake and the shooter. The intake will draw the rings into the robot and the shooter will launch them at the targets.
These are two of the D-shafts we pulled out. We were trying to estimate the size of them in reference to the distance between the two channels that hold the mecanum wheels of our robot. The D-shafts should be shorter than the width but not excessively.
This is a picture of the bumper guard that we uploaded onto Onshape, prior to it being a .stl file. Our goal for the next meeting will be to convert the part to the right type of file so that it can be used on the robot as a part.
Programming
Agenda
Our goal for today is to implement the RoadRunner GUI into our Android Studio
We also want to make a sample program that allowed the robot move from any position on the mat, go to the stack of rings, and change its orientation to face the power shot target.
Reflection
After we all sucessfully install the RoadRunner GUI into our respectful Android Studios, we are able to understand how to use it to our advantage and come up with a basic idea about how to approach the programming challenge of next week.
We initially have some trouble understanding exactly how to do the first part of the task; but we are able to test our tries out and eventually get to a good stage with the program.
Creating a new program almost every session means that a single program didn't really change over the course of the week, but rather our approaches towards certain tasks change.
For example, the tasks of Wednesday and Friday are pretty different from one another; so, our approaches to solving the task also change.
One thing that was common in our approach is trying to learn the concepts first and applying them afterwards.
In the future, we would like to implement all our learnings of today into a usable program.
That would include a program that can make the robot go from any position on the field to the place where the rings are and a program that can make the robot turn towards a certain direction so that it can shoot at its targets.
Here is a picture of the Road Runner plugin we installed today. This particular path is where we tried to get the robot to where we want it to shoot the rings and at the correct angle. We got the x and y position about where we want it for this run, but we were unsuccessful in getting the orientation correct in this meeting.
This is what we have of our code so far. It’s not substantial or specific to what we want the robot to do yet, but it’s part of an outline. It tries to get the position of the robot. We have the “wait for start” line and a line to follow the trajectory we don’t have coded yet. We also have the code written to turn the robot and an arbitrary degree in the code for the robot to turn.
Google Sites
Report abuse