Author: Abriti Chatterjee & Yuga Patel
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 10/12/20
Duration: 5:00 - 6:30
Ahmed Mahmud
Manyata Arora
Amanpreet Dhah
Hooryah Raja
Murtaza Raja
Martin Soliman
Martina Soliman
Syed Shah
Benjamin Fitzgerald
Caitlyn Mei Roxas
Arleen Dhah
Atharva Khandelwal
Abrahim Mahmud
Abriti Chatterjee
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Anirudh Chaturvedula
Astrid Salazar
Ehtesham Suhail
Lutfiyah Mohammed
Prajwal Khanal
Ria Gray
Shaurya Singh
Sivaditya Padmanabhan
Tvisha Doshi
Vanisha Rajlakshmi
Ved Borade
Venya Goyal
Yuga Patel
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
For the hardware team, the agenda for today is to review the new Strafer Chassis released by GoBilda.
After reviewing the design as a whole, we plan to recreate our chassis on OnShape.
For the programming team, the goal for today isto understand the TeleOp Code that Shaurya made with RoadRunner.
We are supposed to pay close attention to the code and ask any questions that come to mind regarding the code.
We find a few parts that could be helpful in building the new robot easily and quickly without a set manual/instructions. For the previous robot we have a long list of parts and instructions, so most of what we have to do was copy and paste the ID’s onto OnShape and search for the parts.
As for assembling the parts together and fastening them, we just had to follow the instructions from GoBilda.
Since the Strafer Chassis with the 96mm GoBilda wheels is new and still on pre-order in their website, we couldn’t find a set of instructions like last time. We still have the part ID’s but not a guide on how to assemble them.
Luckily, we find a model of the new chassis on OnShape; this is similar to what we would have gotten from importing the STEP file from the GoBilda website onto OnShape. The model has all the parts fastened together in the correct places, however, we just can't see the actual fastenings that were used. This should aid us in our process to build the new chassis.
We take some time going over Shaurya's code. It is very long and detailed. So, we look at it minutely and listened carefully as Shaurya explained different parts of it.
Learning the code helps us understand the differences between the TeleOp and Autonomous parts of the competition even better.
We realize how we would have to have basic knowledge of how gaming consoles work in order to fully understand the code.
When we have questions, we ask Shaurya, and he resolves our confusions.
We have a lot of questions because, like I mentioned before, the sample TeleOp code is very different from the autonomous programs we have been writing.
We especially have confusions about the difference between Driver Control and Automated Control in a TeleOp program. Shaurya uses a toy car from his house to explain the difference.
Other questions are mainly based on the functions of the gaming console, whose functions Shaurya demonstrates using a X-Box controller.
The agenda for today is to review the new Strafer Chassis released by GoBilda.
After reviewing the design as a whole, we plan to recreate our chassis on OnShape.
We find a few parts that could be helpful in building the new robot easily and quickly without a set manual/instructions. For the previous robot, we had a long list of parts and instructions so most of what we had to do was copy and paste the ID’s onto OnShape and search for the parts.
As for assembling the parts together and fastening them, we just have to follow the instructions from GoBilda.
Since the new Strafer Chassis with the 96mm GoBilda wheels is new and still on pre-order in their website, we could not find a set of instructions like last time. We still have the part ID’s, but not a guide on how to assemble them.
Luckily, we found a model of the new chassis on OnShape that is similar to what we would have gotten from importing the STEP file from the GoBilda website onto OnShape. The model has all the parts fastened together in the correct places, however, we just can't see the actual fastening that were used. This should aid us in our process to build the new chassis.
Next meeting, we will cross reference the model and its parts/assembly to the pictures on the GoBilda website to make sure we have the correct parts and can copy the model. We will adjust any parts that don’t match, and if they all do, we hope to be far ahead by next meeting.
The biggest change this meeting is scrapping our old robot and starting to build a new one. Although it is a setback, we choose not to view it as a waste of time because we learned each other's strengths, how to effectively divide our workload between ourselves, and new techniques on OnShape.
These are the new 96mm Mecanum Wheels that are added to the new design. These are the main features that changed from the old chassis we built to the new one we started today.
This is the model of the chassis we have to build that we found on OnShape. Our hope is that we can use it as reference on how to assemble the parts listed together.
The agenda for today is to listen to Shaurya as he goes over the sample TeleOp program that he has created.
We would have to try to understand its components in the span of today's meeting.
The programming team was supposed to ask any questions that came into our minds about any part of the program.
We are supposed to pay close attention and ask questions as soon as we thought of them.
Shaurya's main task is to make sure we understand the program because we would have to write them collectively very soon.
Today is a learning day. We go over Shaurya’s TeleOp code.
We start the day with Shaurya showing us exactly what his TeleOp code is supposed to do.
Then we go over some basic components of the TeleOp code that would eventually help us understand the more complex parts of the program.
After that, Shaurya gives us a demonstration of what every single part of a gaming console does so that we have no trouble understanding the next parts of the TeleOp code.
Then, we go over some of the more technical parts of the code. Our understanding of the console and the function of the program paid off significantly.
We ask several questions to Shaurya regarding the program. He tries his best to resolve our confusions.
Naturally, we have many questions about the program because it is completely different from the autonomous programs we have been writing. Thus, we made sure to ask the questions so that we don't get puzzled later on.
We ask most of our questions in the beginning of Shaurya's explanation because we want to have a strong foundation about the topic before going into detail with it.
Shaurya uses things readily available at home, such as remote controls, to resolve our confusions.
His explanations are nice and we are able to understand the program.
In the future, we would like to first finish making all of our autonomous programs, and then focus on writing the TeleOp programs to make it easier and more organized for oursleves.
We want to make multiple autonomous programs that bring the robot from each of the four starting positions to each of the three points.
The TeleOp programs would be based on the autonomous programs. Only, they would inlcude technical components.
Our plan is to first learn the concepts and then apply them.
This is the first part of Shaurya’s code. It introduces the basic elements of the program. To demonstrate what everything here is, Shaurya used objects from his home such as a toy car. We initially had some trouble understanding this part of the code since it introduces some new words like "Driver Control" and "Automated Control." We used the demonstrations to understand the meanings of those words.
This is the part of the code that is actually going to make the robot do what we want it to do in the field. Since this is a TeleOp program, the gamepads on the remote control control the actions of the robot. Over here, we have assigned different parts of the code to different parts of the remote control. We had less trouble understanding this part because it was based on the code that was presented above.