Shockwave Shows Off Some Mad Skills!
A Brief Summary
WHAT: Shockwave launched t-shirts into a crowd of excited Stanford Basketball Fans
WHEN: Saturday, February 3rd, 2018
WHERE: Stanford University in Stanford, CA
Team 254 Members Griffin Soule, Shruthik Musukula, Mubashir Hussain, and Jack Gnibus work together to prepare Shockwave before the game
As part of an eventful weekend, we participated in a successful outreach event at Stanford, CA. Due to the efforts of students on our outreach subteam, Team 254 students were excited to have the opportunity to present Shockwave at the Stanford Basketball Game, where Stanford played against the Oregon Ducks from the University of Oregon. During a timeout in the first half of the game, Team 254 students Yusuf Halabi, Shruthik Musukula, Jack Gnibus, Griffin Soule, and Mubashir Hussain worked together to operate Shockwave and launch several Stanford t-shirts into a crowd of approximately 8,000 people. We are extremely grateful to have such an opportunity and would love to support Stanford University in the future!
Shockwave launches t-shirts towards excited audience members
On Thursday, December 7th, we hosted a Game Analysis, Scouting, and Strategy Workshop to help acquaint new team members with an important aspect of the robot game. The workshop by led by a member of Team 254’s drive team, Brandon Chuang. During the workshop, we taught new members about the importance of pit scouting and match scouting and how we use the data that we collect in order to form great alliances. In order to give our members a realistic experience, we helped them analyze a 2016 FRC Match Video and track the number of points scored by each team during the autonomous and teleoperated periods. Members were introduced to the team’s scouting database and how it is used at tournaments to organize collected data. Our drive coach, Kevin Sheridan, and FRC Technical Lead, Ashwin Adulla, also helped provide examples of some hardships that Team 254 went through when forming alliances at tournaments. We also emphasized the importance of working together with other teams and how that plays a role in an alliance’s performance. Overall, we strategically prepared our new members for kickoff!
On November 11th, Team 254 appeared at the Bay Area Science Festival Discovery Day to demonstrate our 2017 season robot Misfire. At the event, we used a few game elements like wiffle balls, gears, and a makeshift wooden hopper to show over 2000 people the capabilities of our robot. In addition, we spoke about our experiences during 2017 FRC season and the challenges we faced. We collaborated with other FRC teams including Team 1868: The Space Cookies and Team 5026: The Iron Panthers to convey the message of FIRST and STEM. This event allowed us to spread our knowledge and experience to our community in the Bay Area.
Team 254 Members showcase Misfire to the audience
Our experience at Discovery Day not only spread awareness for STEM within our community, but also made an impact on our team. Outreach leader, Yusuf Halabi stated, “My Discovery Day experience this year allowed me to take a new perspective into 254 and our role as an organization. When I first joined robotics as a freshman, I was under the impression that 254 was only good for creating robots. However, my experience at Discovery Day allowed me to realize that serving and supporting the community is just as important as building robots.” Similarly, Team 254 Operator, Themis Hadjiioannou said, “My favorite part of Discovery Day was seeing the joy on children’s’ faces when they saw Misfire shoot into the high boiler. Watching the light in their eyes flash as they observed what a robotics team was capable of struck a chord with me. I thought back to when I was a kid and was inspired by drones and robotics. Discovery Day made me proud to be a part of an organization that strives to bring this inspiration to kids around the world.” Overall, Discovery Day was an outstanding outreach event and we wish to continue making such a profound impact in our community!
Team 254 Driver, Justin Ramirez, helps load up fuel before Misfire demonstrates its shooter
A Brief Summary
As part of an eventful weekend, we hosted Chezy Champs, our annually hosted offseason FRC tournament at Bellarmine College Preparatory, in our hometown of San Jose, CA. We had a great time jumping back into action with our robot, Misfire, before the start of the 2018 FRC Season. Alongside, FRC Team 1011 Team CRUSH, FRC Team 696, Circuit Breakers, and FRC Team 5104 BreakerBots, we were able to win the tournament!
Team 254 Members pose for a picture with Misfire after winning at Chezy Champs 2017
Check out this great highlight reel made by RoboSports Network (RSN)!
At the tournament, we hosted an exhilarating exhibition match, which included the several teams with highly skilled shooting robots. The standard rule for this match was that the only way to score points was to shoot fuel into each alliance’s respective boiler. The teams which participated in the exhibition match:
The Blue Alliance
- Team 971 Spartan Robotics
- Team 973 Greybots
- Team 1678 Citrus Circuits
The Red Alliance
- Team 254 The Cheesy Poofs
- Team 1323 Madtown Robotics
- Team 3309 Friarbots
Team 1323, Team 3309, and Team 254 work together to gather fuel to shoot into the boiler
The Red Alliance started off with a significant lead by scoring 50 fuel balls into the boiler, making it an amazing show for the audience to see 3 robots scoring fuel into one boiler at once! Eventually, the Blue Alliance slowly started catching up with the Red Alliance by consistently scoring their collected fuel into their boiler. With a minute left in the match, the our friends from Team 973 displayed their true defensive skill by blocking Team 1323’s path across the field. Though the Blue Alliance’s efforts were equal to that of the Red Alliance, the Blue Alliance was unable to keep up with the pace of the Red Alliance. After the great efforts shown by both alliances, the Red Alliance came out to be the winner scoring 203 kPa compared to the 97 kPa scored by the Blue alliance. The Exhibition Match Video can be viewed here.
A Special Thanks
Chezy Champs was very special this year due to the efforts of so many people and organizations. Team 254 would like to thank our friends from RoboSports Network (RSN) for providing our audience with such a great analysis of each match and team at the tournament. We would also like to thank all the volunteers, who helped make Chezy Champs possible. It was truly an incredible experience to host an offseason tournament attended by so many talented teams, even those who chose to attend from out of state, and to make new friends and catch up with old ones too!
Throughout the qualification matches, we encountered a few mechanical problems with our gear grabber, hopper, and drivetrain and a few problems with Misfire’s autonomous performance. After some careful observation, we realized that our gear grabber’s knife-edge was worn out, so we replaced it with a new piece of polycarb. Our stationary hopper panel kept colliding with the field hoppers, which tore our hopper wall. We replaced the broken hopper panel to solve this problem. We also noticed a crimp lodged between our chain and sprocket on our drivetrain, so we removed it to make our drivetrain function normally. Overtime, our autonomous performance improved after our mechanical changes. Thus, we were able to seed first for alliance selection after having a qualification match record of 7 wins and 3 losses.
Misfire successfully hangs within the last few seconds of a Qualification Match
During elims, we faced some fierce competition during our Semifinal and Final Matches. We ended up having to compete in a third tiebreaker match in semifinals and finals. In Semifinals Match 2, the opposing alliance of Team 973 Greybots, Team 1538 The Holy Cows, Team 604 Quixilver, and Team 2135 Presentation Invasion, scored a large amount of kPa during auton and kept their lead up by activating all 4 rotors! In Finals Match 2, the opposing alliance of Team 1323 Madtown Robotics, Team 3309 Friarbots, Team 5026 Iron Panthers, and Team 2073 EagleForce, displayed their true skill, by keeping a consistent lead, from the start of the match. By the end of our elimination matches, we won all of our tie breaking matches, allowing us to win the event with our alliance. We wouldn’t have been able to accomplish such a victory if it weren’t for our amazing alliance partners – Team 1011 CRUSH, Team 696 Circuit Breakers, and Team 5104 BreakerBots.
Members of the Team 254 Pit Crew repair Misfire before an upcoming Finals Match
Team 254 is kicking off the school year with a Fall Project. This year students will be building a gear robot for the 2017 FIRST Steamworks challenge. The goal of this year’s Fall Project is to provide students with the opportunity to pursue whichever aspect of FRC they want to in a stress free environment, in order to prepare them for build season in January, and to have fun! Team 254’s Fall Project robot will be competing in Madtown Throwdown this coming November.
2017 FRC Class of FIRST Champions
Recently, we attended the first ever FIRST Festival of Champions in Manchester, NH. After winning the St. Louis Championship with our extraordinary alliance partners, we faced the Houston Championship winning alliance in an intense series of 5 matches. Alongside Team 2767 Stryke Force, Team 862 Lightning Robotics, and Team 1676 The Pascack PI-oneers, we were able to win the Festival of Champions Event. We enjoyed a tour of DEKA and a great potluck at Dean Kamen’s home. We would like to say thank you to FIRST for giving us the amazing opportunity to participate in this event!
“Thanks to the phenomenal performance by our alliance partners!”
In the most intense games we’ve played all season, the Houston alliance won the first two matches. Our alliance won the third and fourth to stay in the game. In Match 4, our alliance partners helped us win against the Houston alliance by a margin of only 16 points. In the final match, our alliance capped a great season with one last win. We won the match, and the festival championship, setting a record high score for this year’s game of 588. We’ll let the video speak for itself, as our last finals match was certainly one of Team 254’s best performance of the season.
We would like to honor our alliance partners because of how far we all came, from St. Louis to Festival of Champions. We would also like to thank Team 973 Greybots, Team 5499 The Bay Orangutans, Team 1011 CRUSH, and Team 2928 Viking Robotics from the Houston Alliance for setting the bar high and making all our matches an intense, and great experience. We’re excited to meet other FRC teams at our annual offseason event, Chezy Champs, and to kick off next year’s season!
This past week, we attended the FIRST Robotics Competition Championship in St. Louis. With two Championship events this year, it was hard to decide which to compete at, but we had a great time facing off against teams from the east coast, Canada, and more. Alongside, Team 2767 Stryke Force, Team 862 Lightning Robotics, and Team 1676 The Pascack PI-oneers, we were able to win the Daly Subdivision finals before continuing on to win the Championship at Einstein.
In our qualification matches, we went 7-3 overall and seeded second, with Team 2767 holding first seed. The improvements we made since the Silicon Valley Regional payed off as we hit over 100 kPa during our second qualification game and managed an average of about 381 points per match. Throughout qualifications, we were also regularly able to achieve 40 kPa and activate 4 rotors, giving us enough ranking points to propel us into a high seed.
Moving into alliance selection, we joined Team 2767 alongside Team 862 and Team 1676. With a balance of gear and fuel scoring ability, we planned to maximize our points by hopefully achieving 40+ kPa and activating 4 rotors every match. Throughout the Daly finals, we remained undefeated and won against incredibly fierce competition. In our first semifinals match, we managed to score a personal record of 550 points! We were also very grateful to have received the Innovation in Control Award, an award we had also received back at the San Francisco Regional. After winning Daly with some very close matches, we were anxious to see how we would perform at Einstein.
In a round robin style tournament, we competed against every other subdivision champion throughout 5 matches. We ended up going 3-2 here and seeded second, giving us the opportunity to compete in the grand finals as the blue alliance against the Darwin champions, who had beaten us in the round robin tournament.
In the most intense games we’ve played all season, our alliance pulled ahead in the finals, winning the second match by only 3 points. We’ll let the video speak for itself, as the second finals match was certainly many on 254’s favorite game of the season:
We are so grateful to our alliance partners for playing such a huge role in our success, and to every team that attended the Championship for competing with us and making it such an amazing experience. Special mention to the Einstein teams for going all the way and challenging us in ways we hadn’t previously been. We’re looking forward to facing off against the Houston alliance at the Festival of Champions!
“Thanks to our mentors for such a great season!”
Day 42: Preparing for World Championships
Everything that we need at competition, which includes the pit, was packed and prepared for being shipped to St. Louis.
We worked on some hood geometry and started to look at the placement of the hanger tube and different sizes. We also finished the design of the new hood and CNCed the new hood plates. We laser-cut a new center divider for the hood. Everything was assembled at on Monday’s build.
The old hopper broke on the practice bot, so we laser cut new plates and assembled them onto the robot. We also cut spare hopper plates and spare intake ramps in case we need them during champs.
We started practicing a new kind of gear cycle called the check mark cycle, which we plan will probably use from here on out.
Today, we worked on shooter tuning and semi-automated gear placement in teleop using an ultrasonic sensor. For shooter tuning, we worked on fixing a problem where our stream will begin to walk backwards over long periods of time. We believe this is a result of the system becoming more efficient over time as the bearings on our flywheel heat up. To solve this problem, we tried compensating for the increased flywheel speed over time by taking an average speed of the flywheel between shots and using it to adjust our voltage.. For teleop gear placement, we tried to use the ultrasonic sensor to limit the amount the robot can drive backwards when scoring gears to prevent it from driving too far back and bending the spring. However, we found that the ultrasonic sensor updates far too slowly for this to actually work right now, so we are investigating ways to speed up the ultrasonic sensor and use our drivebase encoders to compensate for this lag.
Day 41: Improving Gear Scoring
Today we worked on the Cow Catcher, or an assembly that prevents balls from getting stuck in the Gear Grabber and pushes balls out of the way. We began with prototyping with two delrin side plates and a 3/8" standoff, and while the results were promising, balls still got caught in the general vicinity, affecting its performance. To solve this issue, we prototyped the cow catcher with a longer standoff, which prevented balls from getting caught.
Having determined the relative effectiveness of the Gear Grabber, we began to design a deployment mechanism such that the cow catcher fits in the framer perimeter at the start of the match. We came up with the use of a torsion spring and hardstop to deploy the cow catcher at the start of the match. Due to the limited availability of springs at the lab, we used rubber bands instead, but the deployable cow catcher was ultimately too weak. Thus, we added standoffs and reinforcing plates to increase rigidity.
We worked on fixing up our practice bot, making a new intake ramp and straightening out our hopper flanges. We also did a lot of shooter testing and were able to significantly improve the accuracy of our shots.
This past weekend, we competed at the Silicon Valley Regional at San Jose State University.
Throughout the qualification matches, Misfire performed very well, despite bearing one loss, going 8-1 overall and scoring an average of about 300 points. We focused on a strategy of reaching 40kPa along with delivering a couple gears to maximize the amount of ranking points we would receive, which worked out as we were seeded first heading into eliminations
Eliminations & Awards
In our alliance, we picked Team 604 “Quixilver Robotics” and Team 4990 “Gryphon Robotics.” With this alliance, we aimed to focus both on fuel and gears, hoping to reach 40kPa+ in the boiler, 4 rotors spinning, and all robots hanging in an ideal game. During quarterfinals, we beat the prior record of 506 points with no penalties by scoring 507 points and later in semifinals we scored 509 points. During finals we finished off with scoring 522 points (517 without penalties)!
Through the eliminations, we ended up winning the tournament after an exciting final match! We won the Quality Award and were recognized for being captain of the winning alliance. It was a great experience playing against all these teams and we hope to see some of them again at World Championships in St. Louis.
Day 40: Improvements for SVR
We added additions to our robot in order to create an easier and more efficient driving environment. We have placed a blue LED strip on the back of the hood to let drivers know whether or not they are in a good shooting proximity. To do so, we wired up MOSFETS to control the LED strip, which will plug into the DIO port on the roborio.
At SFR, we found that installing “back-up cameras” would help with gear placement. Therefore, we worked on optimizing the camera placement, as well as finding a way to widen the narrow field of view (currently 70 degrees) to better capture the gear’s location.
After the post-mortem we worked to improve the robot's turning during autonomous. We prototyped small Delrin sliders that didn't quite work when sliding on carpet. We anticipate that the best solution will be to try to implement drop-down omni wheels that we can turn on. However, if that does not work either we will resort to changing the autonomous routine itself.
This past weekend, we competed at the San Francisco Regional at St. Ignatius College Preparatory.
Throughout the qualification matches, Misfire performed strongly, going 10-0 overall and scoring an average of about 277 points. We focused on a strategy of reaching 40kpa to maximize the amount of ranking points we would receive, which worked out as we were seeded first heading into eliminations.
Eliminations & Awards
In our alliance, we picked Team 971 “Spartan Robotics” and Team 4990 “Gryphon Robotics.” With this alliance, we aimed to focus heavily on the high goals, hoping to get 40kpa+ in the boiler, 2 rotors spinning, and all robots hanging in an ideal game. We also planned to use defense, having one of our robots block the chokepoint near the gear loading station, hopefully making it impossible to for other teams to score 4 gears.
Throughout several exciting rounds, we ended up winning winning the tournament after an intense final match. We also won the Innovation in Control Award and Griffin Soule, our team president, won a Dean’s List Finalist Award. It was a great experience playing against all these teams and we hope to see some of them again at SVR.
Days 37, 38, & 39: Preparing For Competition
Today, we worked on fixing the intake after it broke earlier this week. After analyzing the strength of our current weldment and modifying it slightly, we decided that simply strengthening it would not help the fundamental problems existing in the design. We took one of the broken intakes and attached it to new polycarb side plates hoping that this would decrease impact forces by increasing the time of impact (change in momentum = force * time). We drove around and crashed the intake several times with minimal damage occurring, and we are proceeding with the new design.
Today, we worked on the Hopper and testing the fully assembled redesign. After fixing some initial discrepancies in the real life assembly, we tested out deployment and stowing. As of a few tests, the intake deployed well (after modifying the intake ramp slightly to have slightly deeper notches to fit the constraint screws in) and we will be updating the CAD with these changes on Friday. We will also laser cut a new intake ramp to get definitive results. If all systems work well after that, we will begin assembling the new parts for comp as well as a back up.
Between, Friday and Saturday, we were able to finalize the hopper design. After some CAD work on the redesign and some troubleshooting after assembly, we were able to make a solid hopper. More testing will continue to confirm consistency, but we will be moving forward with the Comp set soon.
In the last week, we explored the use of a large flywheel to help increase the consistency of the shooter. A flywheel dramatically increases the kinetic energy of the shooter wheel system, hopefully reducing the amount that the wheel slows between shots. We designed a steel flywheel with about 4 lb*in2 of inertia. It is geared up 2.5:1 from the shooter wheel to increase the kinetic energy. Preliminary testing shows that adding the flywheel may not actually achieve the desired result. The elasticity of the timing belt caused some controllability challenges that the programming team worked on this weekend. Each time the direction of tension in the belt switched (from energy going into the flywheel to energy leaving the flywheel), there was a little bit of elastic movement which added oscillations to the shooter wheel system. The plots looked like the typical mass/spring/damper plots for a 2nd order system from a controls or dynamics class.
We are using inline elastic to add stretch to the rope. This will allow the robot to pull the rope down with a low amount of force at first, getting some wrap before beginning to lift the robot off the ground. This is important because the Velcro that engages the climber drum is strong in shear – and its strength is proportional to surface area. Once the rope has wrapped around the drum enough, the load transfer switches to Capstan forces. We are assembling several ropes, each with a number of pockets like the ones shown below.
A video is linked below of the climber being tested. Note that in this test case, we were pulsing the motors. Typically, the climb is much faster.
The latest iteration of the gear grabber has a dual pivot design – the whole mechanism pivots from a pickup configuration to a scoring configuration with one pivot, and a second lower pivot is sprung to allow the wedge to conform to the floor without digging in. We built this prototype last week out of delrin on the laser cutter and used it for driver practice over the weekend. We moved forward with making this out of metal and sent the parts to Anodize on Monday morning.
Check out the video below for pickup and scoring performance of the current prototype:
We practiced driving by cycling gears with and without defense, climbing, and intaking balls off the floor. We are much better now at quickly scoring gears, and in one practice match we scored 9 gears and climbed when no defense was played on us. The gear grabber is much more reliable, and consistently picks up gears off the ground the second we touch them. Scoring is still tricky, but we are getting better at finding the right depth at which we need to drive into the spring.
Today, we worked on finding and fixing a bug in our Adaptive Pure Pursuit controller. The bug was causing arc lengths in the controller to be calculated incorrectly in some cases, resulting in a value much higher than it should have been. This would in turn cause the robot to drive way too fast and shoot past the end point in the path.
Gear Grabber State Machine
Today, we worked on implementing a new Gear Grabber state machine. The new gear grabber code greatly simplifies the operator controls. Now, there are only 2 buttons used for intake and release. The state machine uses output current to determine when a gear has been picked up and will activate the piston automatically.
We also found two bugs resulting in the robot not turning left and twisting along an autonomous routine, and we were able to fix these edge cases.
The hardware team began crimping and attaching 15 battery leads and running battery tests to determine true battery capacity.
Day 36: Improving Subsystems
Today we ordered all the the parts for the upper extension of the hopper floor and got majority of the CAD done. We will be going with 50 degree edges made out of Delrin with the first two rollers of the upper extension not having any surgical tubing to allow for horizontal movement.
Today we worked on inventorying all the COTS parts for the Feeder subsystem. This would allow us to become more organized and make sure parts we need we have or are buying. I also helped lead students in inventorying other subsystems via the CAD,
We worked on the gear grabber. We removed the polyurethane added before with black, conforming WCP wheels. We found them to work significantly better than the polyurethane, but still not extremely well. We continued to work and changed the WCP wheels to red conforming wheels, which while ugly, worked better.
Days 33, 34, & 35: Preparing for Competition
Gear Grabber/Driver Practice
We worked with the drivers over the weekend, doing basic drills like gear cycling, in order to become accustomed to driving the robot prior to the SFR Competition. We started the day by iterating on the floor for the gear grabber. The floor pickup for gears still needs work as it is inconsistent at picking up the gears when we drive into them. The polycarbonate knife edge was not as smooth as the prototype. There was a small edge on the actual version which was causing problems, so we sharpened it. After iterating on it, we then mounted it, and set ourselves on solving the jackknifing. We realized the best solution for this would be to redesign it, so Andrew and Mani are working on a new CAD. Meanwhile, the group worked on iterating on the length of the polycarb. We still have work to do before we finalize the design.
The major problem we were trying to solve was that the bumpers were too low. This was because the mounting solution uses C-channel brackets that go around the bumper supports and are supposed to sit flush to the underside of the little 1/2 x 1/2 bumper rail. But, what we didn’t realize is that the rail actually has a weld bead under it so the brackets could not go up high enough. This made the bumpers too low to the ground. To fix this, we removed a couple staples and pulled back just a bit of fabric on one of the practice bumpers so we could remove the brackets without actually remaking the entire bumper. We used the mill to make the brackets shorter, so they can move up and avoid the weld. We also used the drill press to add a new hole so they can align to the holes already drilled in the robot. This works pretty well, but some concerns are that the bumper is now too high and lifting the intake up, preventing it from going down far enough to have good compression on the balls. As of now, the intake is working fine. We still need to mill down all the other brackets, and we talked about making new ones and getting them anodized for the competition bumpers. The red comp bumper still needs fabric, and the blue one should have the fabric removed.
Over this weekend, we worked on the hopper redesign. After some initial tests, we found that perhaps preventing the hopper from expanding sideways in the front expansion might add rigidity and strength to the hopper. To do this, we tested by bolting the front sliders to the hopper to prevent them from sliding. After testing, however, we found that intake by actuating the field hopper became difficult as the decreased width of the hopper prevented the balls from coming into the robot. To accommodate this, we redesigned the hopper in CAD so that the top will slide out vertically while the bottom pivots about a fixed point that torques the flexible polycarbonate. We also started the CAD of the new hopper floor for SFR which has the top rollers and wedges and a center to increase our ball throughput. We started the construction of the wedges on the hopper floor. After some brief testing, we CAD-ed this out. We will begin manufacturing on Monday.
This weekend, we received the 3/4” ratchet strap climbing ropes with the sewed on velcro. We tested it by pulling on it and rubbing it at corners in order to see distressing. The rope was then tested using the rope climber on the practice robot but the lack of stretch/slack made it hard to latch onto. In the near future, the rope team will attempt to plan out elastic placement on the rope.
We wired up a MOSFET to control the switching of the LED light, located on the front of the robot, by having a voltage signal sent out from the relay port of the Roborio. It allows the drivers to see better when having to place a gear without the light blinding them.
Today, we worked on creating a reliable 40 kPA autonomous mode. We decided that previous autonomous modes that used complicated S curves to swerve into the hopper were too inconsistent, so we settled for a new, much simpler mode. But, at the end of the night, we had a working auto mode that deployed the intake, rammed into the hopper head on, waited a few seconds for balls to pour in, then aimed and fired the balls into the goal. We continued to improve the efficiency of this autonomous mode until we had it begin shooting around 6.3 seconds or less. We needed the autonomous mode to begin shooting as early as possible because there is around a 5 second delay between scoring a ball and having the scoring system pick it up. Because of this, any balls shot past 10 seconds will probably not be scored during auto.
We continued revising our robot's autonomous routines, and we were able to drive to the hopper and trigger it, receive a payload of balls, and fire into the boiler.
We also worked on a live data plotter that could plot robot data much faster than SmartDashboard. Various subsystems, such as the drivetrain, simply push data to a server, which pushes data to a grapher website on the driver station. This utility will be useful for tuning drivebase and shooter PID, as well as other programming tasks.
Day 32: Continued Assembly and Programming
Today, we worked on designing and testing the roller gear grabber. We installed a prototype onto the programming robot, and it worked somewhat well. When we drove into a gear directly, it was always ours, but it was narrow and difficult to always aim correctly at the gear. We played around with passive funneling, but were unable to significantly improve the width from which we can intake because of the sidewalls of the rollers were too low. Griffin and Colin are currently designing a new gear grabber that will likely funnel more effectively, and we plan to have it on the robot and testing it on Friday.
We took the top roller prototype that we have been working on, and added a center wall. The one from Monday was not long enough, so we extended it and stiffened it. We found this to help immensely. We also added zip ties across rollers to help the balls move across faster. We have reached a point where we are comfortable and confident with the floor.
We made progress on the hopper improvements in CAD and the redesigned Gear Grabber. We determined the geometry for the gear intake, designed the gearbox, and made the basic assembly that will be developed upon later.
Today, we worked on improving the web interface for the autonomous pathing tool. We improved the overall aesthetic of the app, and added several new features. These include the ability to see robot start and end rotation, and having the path colored based on the current speed of the robot.