Author: Astrid Salazar & Lutfiyah Nawaz Mohammed
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 9/30/20
Duration: 5:00 - 6:30
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
Lutifiyah Mohammed
Sivaditya Padmanabhan
Yuga Patel
Vanisha Rajlakshmi
Astrid Salazar
Ehtesham Suhail
Alisha Varma
Ashita Birla
Syed Shah
Mark Rajah
Luniva Joshi
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Our goal for today is to build upon the finished robot chassis and determine our code to effectively and accurately shoot down the Power Shot targets.
The Hardware team establishes a foundation on which the intake system of the GoBilda robot design is based on and gathered parts needed for the system.
The programming team focuses on developing an autonomous program that makes the robot perform a specific degree turn to face the Power Shot targets.
The Hardware team defines the intake system by analyzing specific seconds in twitch videos of the GoBilda Robot Built in 3 days.
Unfortunately, GoBilda takes down the long version of their video where they explaine their robot in depth but the team relies on these clips to get the job done.
We manage to gather the parts necessary for both the intake and shooting mechanisms.
We also prepare for the arrival of the bumpers from the specialty robot design team that are necessary to protect the Mecanum wheels.
The programming team uses the Road Runner to help the robot execute complex movements autonomously and we also plan to incorporate the IMU into the code to determine the angles needed.
Our goal is to make the code easier to understand on Android Studio and correct all errors. In addition, we plan on conducting some more research on old and new techniques that would be beneficial to our current code. Furthermore, we plan on altering the code to perform other tasks based on the situation called for to score points on the playing field.
Today, we finish the adjustments on the gears. They are now properly attached on the axle.
Vanisha adds two channels to the chassis so the specialty parts design team can later upload bumpers to protect the wheels.
We are currently working on a design inspired by the GoBilda Robot in 3 days idea. Benjamin, Yuga, and Astrid work on finding parts resembling those from the GoBilda video.
Yuga manages to find wheels that resembled those in the front line of the intake system. Through further research, we find out that they were called Rhino Wheels.
The GoBilda intake system uses Gecko Wheels which are thicker and have less of an indent. OnShape doesn't have Gecko Wheels in their GoBilda folder. Instead, we are using Rhino Wheels.
Today’s session runs smoothly; we come across very few issues.
We spend more time than expected finding what parts we needed to build the intake and shooter mechanisms.
Since the pictures on the twitch streams are small when we tried to zoom in to see the parts, it is difficult to determine what we are looking at, especially for the inexperienced members who aren't aware of all the parts that GoBilda offers.
Searching for parts on OnShape also eat away at our time because certain parts aren't there. For example, we have to use Rhino Wheels instead of Gecko Wheels. Another issue is the abundance of parts in the GoBilda folder. Having a wide selection is helpful but becomes a burden when trying to narrow down sizes from a blurry photo. "Some were too small, some were too big and sometimes none were just right."
Next meeting, we plan on adding the remaining screws to the channels on the sides of the chassis. We will also further inspect the twitch videos to get a better understanding of how certain parts interact, and what the parts that are essential to the design are. One of the hardest parts is approximating size, but now that we have a Rhino Wheel of a size we are confident will work, we can compare all the other parts of the system to the wheel to get an approximate size.
These are our plans for the intake system. After watching the GoBilda videos on twitch we isolated the basic function of the intake system and how the different parts interact. The diagram above is a side view of the robot, and the yellow rectangles would be the rings traveling through the intake system. We don't plan on following the GoBilda model exactly, but instead captivating the basic function while utilizing parts we actually have access to and/or think work better.
https://docs.google.com/document/d/1OemBqXH8sWQSgFnEYMnklgwSp1mG015GdQ5JjkpE5VQ/edit
This is a diagram Benjamin created to explain how the intake system works to the rest of the team. It depicts how the motors would shoot the ring. One motor would be stationary, guiding the ring, while the other would spin, propelling the ring outward. With the code being developed by the programming team we can ensure some accuracy in the launching of the ring. The stationary wheel acts as a guiding mechanism of sorts and together with the code, we hope to score maximum amount of points shooting down all three Power Shot targets. This diagram can also be found in the google document.
This is a picture of the 3601 Series Rhino Wheel (14mm Bore, 120mm Diameter) Yuga found. They have a strong resemblance to the Gecko Wheels. The Gecko Wheels are made of better material and they are equally indented on each side. Rhino Wheels are unequally indented on each side. One side has a lower inner surface than the other. The surface shown above is of the side with the higher inner surface. The opposite side has an inner surface that has a greater indent into the wheel. These are the main wheels at the front of the intake system, thus finding a wheel this early in the building process was a useful.
On the right is the chassis so far. Vanisha added channels to the sides of the chassis and some screws in order to fit the bumpers that the specialty parts design team is working on. With OnShape, the channels are fastened without screws, making them technically unnecessary. Our group members add screws to keep the whole process more realistic; screws would be necessary when building in real life. It helps make the experience realistic, and makes our whole design look neater overall. Adding screws is also great practice for fastening on OnShape especially for new members.
Our goal for today is to make a sample code using RoadRunner and the IMU
Using the IMU, we can find the angle the robot needs to turn in order to face the direction of a Power Shot target.
We would then tell the RoadRunner the angle at which the Power Shot is located and the RoadRunner would turn to face the Power Shot to perform the task.
While working on the program, we develop the fundamental idea for making the robot turn the correct angle. However, we determine that this method wouldn't be able to operate effectively from anywhere on the playing field.
The program is supposed to gather data based on what direction the robot is facing at the start and where it needs to be facing. Based on that information it should turn the robot from anywhere on the playing field. As opposed to just telling the robot where it should go and how much it should turn based on every single different Power Shot target.
We are able to understand the part of the equation needed to turn the robot , but we are still working on implementing it into our code and mastering its use.
The robot wouldn't turn with only the RoadRunner because the IMU is essential for making the calculations necessary to adjust the robots direction and angle relative to the Power Shot target.
In the future, we would like to make additions that would help accomplish the task without the issues we ran into using Android Studio. We would have to make some adjustments for the code to be easier to comprehend and work with.
Furthermore, researching about new and old techniques and implementing them into the program would improve its accuracy and overall function. Our plans today work smoothly. We plan to improve and build upon the code in the future.
Currently, our program is only meant to determine specific crucial angles. We would like to add modifications in the future in order for it to accomplish more tasks.
This is another part of the equation. It takes the arbitrary positions of the Power Shot Target and the robot to find the displacement, or the amount we need to turn. It’s a work in progress is being modified progressively.
This is the isolated part of the equation we came up with. It calculates how much the robot needs to turn to reach its target. It includes the arbitrary position of the Power Shot targets, the arctangent of the triangle made to calculate the angle we need to turn and the specifications for turning right or left.