Author: Abriti Chatterjee & Yuga Patel
Witness: Ms. Maria Osoria and Ms. Manisha Shah
Date: 11/9/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
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
✅
Today the hardware team has multiple tasks to complete and tackle.
These tasks included finishing our design for the shooting mechanism and making the robot CAD design look more presentable for the showcase.
The goal today for the programming team is to add the shooter and intake motor codes to our autonomous programs, as well as get a basic understanding of how to code for servos.
Shaurya has to start working with the servo code.
He also has to explain the code to Abrahim, Ria, and Abriti if time permits.
The main task that our team focused on completing today was our design for the shooting mechanism. We also attempted to attach this component of the robot to the main chassis design and the intake mechanism.
In prior to creating a final design for the shooting mechanism, we first worked on a blueprint. This blueprint was created in a separate assembly on OnShape, which allowed us to clearly visualize how the different parts of the shooter will work together.
For the actual shooting mechanism we decided to use a base plate, two sets of gecko wheels, motors and channels.
Our future plans include, attaching the shooting mechanism to the intake system. This will come as a big challenge since it will be very difficult to angle the structure at the perfect degree. Additionally we have to find a way to attach the structure of the shooter to the small wheel assembly.
We were all able to successfully add the shooter and intake motor code into our autonomous programs.
We divided the work amongst ourselves so that no one has too much or too less work, but all are challenged to apply the concepts learned in the last meeting into the programs.
We did have questions occassionally as some words were unfamiliar to us. We helped each other to resolve all the confusions and finish the code.
Shaurya was also able to add the servo code into one of the programs.
While Ria, Abrahim, and Abriti were adding the shooter motor and intake motor codes to the autononous programs, Shaurya researched about how to code for servos and started it.
He was also able to explain the function of servos while writing the code.
Today, the hardware team has multiple tasks to complete and tackle.
One of these tasks include finishing our design for the shooting mechanism.
It is necessary to complete this design by the end of today's meeting, because our robot will be showcased in the virtual session.
The next task for our team is to make the robot look more presentable in the CAD design for the showcase.
In order to do this we would delete the unnecessary components that are not fixed in place.
The main task that our team focused on completing today was our design for the shooting mechanism. We also attempted to attach this component of the robot to the main chassis design and the intake mechanism.
In prior to creating a final design for the shooting mechanism, we first worked on a blueprint. This blueprint was created in a separate assembly on OnShape, which allowed us to clearly visualize how the different parts of the shooter will work together.
For the actual shooting mechanism we decided to use a base plate, two sets of gecko wheels, motors and channels.
Benjamin and Leonard worked on attaching the two gecko wheels to to the aluminum base plate. These wheels were attached to the plate with the use of different pattern plates. One of the wheels was attached to the motor, while the second wheel was dead (not moving) to generate maximum power.
Astrid, Tvisha, and Yuga worked on attaching the shooting mechanism to the chassis design. On each side of the chassis a 1 hole U-channel was placed. These U-channels were later linked by a low-side U-channel. This channel served as a bridge in the middle connecting the two sides. When this assembly was completed, the shooting mechanism was centered on top of the low U-channel.
Vanisha, Tessa, and Eva checked to see if everything was correctly placed and organized in the robot. This included searching for collisions and making the robot look presentable. This is because we planned on showcasing our robot design in the virtual session so that our team could receive helpful feedback.
Our future plans include, attaching the shooting mechanism to the intake system. This will come as a big challenge since it will be very difficult to angle the structure at the perfect degree. Additionally we have to find a way to attach the structure of the shooter to the small wheel assembly.
OnShape was running slow, causing complications for the team trying to finish up the design in time for the presentation. Short on time, we had to delete most of the unfixed parts. Another issue was trying to come up with an idea to prevent the scrapping of the sides of our robot to gain the maximum points needed in a competition.
The foam rings which lay on top of the aluminum base plate, will be propelled by the two gecko wheels on the corners. The aluminum base plate is then connected to the low-sided U-channel with the use of grid plates.
Here you can see how the motor is fastened to the gecko wheel. This side of the wheel will spin with the power from the motor, while the other wheel remains dead. In the end you can virtually see the one hole u-channel that is connected to the blue u-channel. Overall, this is a very simple but solid shooting mechanism.
The main task for today is to add the shooter and intake motor codes which are in already in our TeleOp programs to our autonomous programs with some minor changes.
Ria, Abrahim, and Abriti are supposed to do this since Shaurya added the shooter and intake motor codes for the TeleOp program.
Shaurya has to research, as well as work with the servo code and add them to our autonomous, as well as our TeleOp programs.
Ria, Abrahim, and Abriti are then supposed to listen to Shaurya's explanation about how servos work and how to code for them.
Ria, Abrahim, and Abriti were all able to successfully add the shooter and intake motor codes into our autonomous programs.
They reviewed their notes and worked with one another in order to do so.
Whenever someone made a mistake, the others pointed them out and helped their team member to fix it.
Throughout the time, our understanding of the shooter and intake motors increased.
At first, Shaurya guided the others through what they are supposed to do. Once everyone was fine with their tasks, he started researching about how to code for the servos.
While the others worked through adding shooter and intake motor codes to the Autonomous programs, Shaurya added the servo code to both the Autonomous and the TeleOp programs.
After that, Shaurya explained the functions of the servo code to Ria, Abrahim, and Abriti.
They asked questions if they had any and Shaurya answered them.
At the end, the programming team explained what they accomplished today to Team Captain Ahmed, who commended us for our work, as well as gave us suggestions on what to do next in the future.
In the future we would like to update our gradle dependencies to be at the newest possible.
This would help us be more efficient with writing our programs since a huge part of it depends on the functionalities of the system.
We also have to add servo code to the rest of the autonomous programs.
Then, we would have to add the code for the linear slide to all of the programs.
At first, we have to research about it, and then we would have to do it.
This part of the program shows pieces of the code dealing with the shooterMotor and the intakeMotor. We get both the shooterMotor and the intakeMotor from the hardwareMap, and set both of them to RunMode. Then, for the shooterMotor, we set the coefficients for velocity and feedforward.
This part of the code has the shooterMotor and the intakeMotor set at 1.0 for power for a temporary time period. Then, when the program is over, it sets the intakeMotor and the shooterMotor to off (0.0 power).