Week 4 UpdateRead Now
The team has grown a lot since the start of the school year. Covid has not stopped the interest in STEM. We have received 21 new members, doubling our team in size. The new members along with the veterans have been hard at work over the past few weeks. After kick-off, we identified new ways to improve communications with each other, had a change in our meeting schedule, and divided into different subsections. With our new meeting schedule, the team meets four times a week; two days that are fully remote, and two days that are in person. For these in person meetings, members have the option to be remote and are still able to participate in the meetings. These in-person meetings invite all team members to come in and work with everyone else on the team. With this, we have introduced new safety measures and protocols to ensure that every team member will be safe. This allows us to safely roll into a strong start to the build season. Each member has the option of what area they would like to go. There are six different subsections of the robot. From there, each member has been assigned into a specific subsystem, a model that the team has used in past seasons.
Team operations talked about rebranding the team, and some of the members have created sketches that may replace the current logo. Although we will not be changing our team logo this year, these designs may be implemented next year for future seasons. The team has worked on setting up the Mooyah fundraiser and making it official. Check out our previous blog post for more information. Along with rebranding, team ops has been writing handwritten letters to send out to our sponsors. These handwritten letters are more personal, and will let our sponsors know that the team is still active and that we appreciate their support. We have also been updating the layout and information on our team website so it is more up to date and fresh. We have also been working on coming up with ideas for the innovation challenge which we mentioned in the 2021 Kickoff Blog Post, as well as working on making the team t-shirts for this season.
Since the start of the new FIRST Robotics season, the software team has been especially hard at work. We’ve focused on onboarding the new members by involving them in peer programming and planning. Additionally, our highest-priority goals are completing the team’s main build project (the swerve drive) and excelling in the at-home challenges offered by FIRST this year. This means learning the basics of swerve and the mathematics required to implement it, as well as the programming logic behind it. We’ve also been working to integrate computer vision into our robot in order to complete the Galactic Search challenge, where we seek out Power Cells randomly placed on the field.
The shooter group has been reading and discussing the game manual for this year’s competition. We went over rules, regulations, dimensions, and penalties. Then, broke off and discussed possible strategies for gameplay, like field maneuvering, cycles, possible shooting positions, and different ways to score lots of points. Then, we started to make needs, wants, and nice to have lists so we can prioritize what needs to be worked on. Now that the team is able to meet in person, the group started some concept sketches after looking at last year's robot, considering the pros and cons. Then, discussed values of these concepts, and looked into materials for certain parts of the robot. We began training the new members on Onshape (CAD Software) for practice before designing the shooter. With the guidance of our mentors, students created a simple drivetrain. Then we started a CAD sketch of the shooter, while referencing the one from last year’s robot. To do this, the group used a graphical simulation to test different shooting angles with different heights, and velocities.
Since members are participating both virtually and in person, the intake/indexer group used zoom to include the virtual members so everyone was able to collaborate. Together, we came up with designs on a white board for moving a power cell from the floor to the shooter. With new members, the group did some training on CAD. Using that training, designs from a whiteboard were transferred to the CAD software.
The control panel group has started planning how they would like to build the manipulator while staying under the trench run height. The plan we ended up choosing was a pneumatic piston that will push a motor that has a stack of wheels attached to the top of it. The motor would be attached by a pivot point, so it can stay in a rested state until it is ready to be used. The group has started discussing locations it could be mounted on, such as the intake or the shooter’s hood. The location may change the design and their idea on how they would like to do this. After discussing possible mounting options, the group is waiting to begin the design process of mounts and locations. Since we don’t have a solid mounting spot yet, the group built the chassis in the CAD software and attached the new swerve drive modules, then designed new bumpers to attach to the chassis. The dimensions of the wheel pattern, height, and speeds to run the manipulator were tested and after inserting a motor with additional wheels to it, the group applied it to our 2019 robot for testing. Sadly it didn’t work out so we moved to the next option, which was to attach it to our most recent robot and retest the patterns to optimize the situation. The group has determined the ideal wheel pattern and height with a combination of 2-3 wheels and a height of approximately 31 inches from the ground. Motor speeds will be recorded soon.
Since the build season began, the swerve group has been focusing on getting each student caught up on the progress of the swerve module, and focused on design skills to begin modifying the CAD model. In the process, the current design has been tweaked, and some of the components have been tested to see if they work or if they need to be changed. A full scale 3D printed prototype of the main component stack of a module has been assembled to use as a test-bed. Unfortunately, testing has shown that significant design improvements are necessary in order to ensure the module and overall drivetrain will work. Now that the group is comfortable with the internals of the system and how it works, we are able to continue to push forward and make improvements that will ensure the longevity and efficiency of the drivetrain.
Leave a Reply.
SUBSCRIBE TO OUR BLOG
Email firstname.lastname@example.org to receive an email notification every time a new blog is posted!