We’re back! This website has been down a long time, so we’ve got a lot to to catch up on!
The biggest change this year is that we are under new management, with Dr. Jim Kreyling as our coach. This has definitely brought some changes to the club, especially with the organization of the club. We elected a president (Thomas Gleiforst) and a vice president (Sheldon Salins) as we always do, but this year they are not the team captains. We also elected 3 other executives to help the club run more smoothly. The positions are as follows:
President: Thomas Gleiforst
Vice President: Sheldon Salins
Secretary: Nicole Neher
Treasurer: Hannah Jokuti
Communications Officer: Caleb Roth
Team 9612 Captain: Lukas Shelp
Team 9612 Co-captain: Nick DeLucia
Team 9328 Captain: Alisa Lazareva
Team 9328 Co-captain: Max Buckel
There should be a post up about each team later today, and hopefully the website will be continuously updated from this point forward. We’re happy to be back on the web to share our progress with the world again, so we are trying to keep this updated for the rest of the year.
Although there hasn’t been much coverage of Team 9612, the other robotics team has made plenty of progress!
When the FTC 2015-2016 game had come out, Team 9612 went straight to work, generating ideas for a robot that could climb all three levels of the mountain while hitting the triggers along the way, as well as pull up on the top bar. Some suggestions of picking up trash (wiffle balls and cubes) were quickly dismissed, as our team wanting to focus on the more challenging part of the game instead of the seemingly simple tasks.
One of Team 9612’s members gathering up all the different designs into one to get an initial idea of their robot.
Our first idea for an arm using drawer channels
After drawing up the designs, all 8 members at the time began creating our base. The base was crafted using the directions in the PushBot Design Guide that was provided to us through the FTC website. Making sure we remained within the 16x16x16 constraints, we also began generating ideas for an arm that would grab the pullup bar and lift the robot up. Using Youtube, certain members researched arm ideas to give us inspiration for how our bot arm would work.
Our first prototype used surgical string to extend out fully, but our team could not come up with an idea to the arm to pull the robot up. Running out of time and ideas, our mentor Brian Pohl gave a suggestion. Why not focus on the trash and after the first qualifier, develop the extending arm idea further. We set to work on designing a new arm that would grasp the trash and bring it up to the first basket. Unfortunately we did not have time to program an autonomous mode for the bot.
Final arm idea
With the whole robot working properly, we went to our first FTC qualifier on December 5th, 2015, getting 16th place overall. While at the competition, our program “hiccuped” a bit, making our wheels spin without us touching the controllers. We eventually had to switch out our power distribution module with a backup one from FTC due to a defect. The gears also slipped while we were competing. To improve our bot for the next competition, we plan on taking the gears off our bot and changing to treads. Also, we will update our code for the bot and create an autonomous mode.
We’re proud to say that we placed 4th in the first Missouri FTC qualifier!
Our goal for this specific competition was just to check measurements and see if our bot has the potential of climbing the mountain. Our first round and first attempt to climb the mountain resulted in one of the gears in the robot to come loose and fall off which caused one of the gear trains to not function anymore. This was due to the fact that we combined Vex and Tetrix parts, but this problem was solved by switching out the axles. Even though the gear train did not fall apart anymore from then on, we still needed to tighten all the wheels after every match, as some of them continued to come loose.
We found that our robot, like many, was having trouble getting up the first incline, especially without tipping over. Occasionally, we would be able to cross over the first bar by driving the robot straight into it, but it was too unreliable to depend on. However, the team improvised and attached a piece of sheet metal to the front of the bot to push balls and cubes around on the field. This allowed the team to score some points but raised the problem of not being able to make it up the mountain. This was easily solved by having the robot go backward up the ramp instead of forward, so the sheet metal didn’t hit the ground. When combined with good preliminary alliance partners, these improvised design ideas allowed us to qualify for the finals round. Because the third team in line was picked to be a finals alliance partner, we were made an alliance captain. We chose the other Oakville team (9612) as well as team 8782.
As time went on we began to notice that many teams were using treads, with varying degrees of success. From what we observed, other teams also used wheels, but to a lesser extent. The specific choice of wheels also tended to be larger than our own. On the field, one of the other teams skipped the bars and parking zones altogether by using an extending arm. With everything we observed at the qualifier, we decided that treads were useful for our plan of climbing the mountain, and plan to implement them in our robot’s design.
Hello, robotics fans! Over the past month, both FTC teams have been working on their robot bases. Today, we’ll be taking a look at Team 9328’s progress.
After unpacking the parts so we could measure and reference them, we needed to start designing. Because we have so many members this year, it was difficult for everyone to contribute to the design. To solve this, we let everyone draw their own designs for the base and subsystems of the robot, and we then collected everyone’s drawings and picked out the drawings that were most detailed and most promising. Several members of our team (including, but not limited to, Emily, Katelyn, and Hannah) then drew out final designs that combined our favorite aspects of each design.
For our base, we made a rectangle out of Tetrix c-channel. We used the longest available pieces for the sides, and for the front and back, Michael bolted together several smaller pieces. Jack and Max put together a wheel and axle assembly, and I calculated how wide the front and back could be in order to fit within the 18″ size constraint. Currently, some of us are in the process of attaching the motors to the gears for the wheels, and others are attaching the arm mount.
Speaking of the arm, we’ve settled on a folding design. We will attempt to use Tetrix servos to connect each link to the next. It’s worth noting that we’re not completely confident in the servos’ ability to lift the robot off the ground, so we’re looking into alternative options in case we need them. For now, the plan is to have two identical arms working at the same time, connected at the far end with a stick. On that stick, we will attach a carabiner, which will clip onto the cliff bar on the playing field. When the arms fold back up, the robot should be pulled off of the mountain.
In the coming weeks, we will finish the base and the arm mechanism. We will post another update once we’ve moved on to programming and autonomous functions.
During our 9/30 meeting, our FTC teams split up and discussed the 15-16 game, Res-Q.
Team 9328 talked about the various methods of scoring points, and decided that it wants to attempt pushing the colored buttons in autonomous mode and climbing the cliff during the driver-controlled period. Here are some of the early notes:
Next meeting, we’ll unpack the parts (assuming we get them) and continue to design based on the parts we have.
At our 9/23 meeting, we split the club up into two teams for the FTC. As of this post, the teams are as follows:
Jacob Kauffmann * (Captain)
Max Buckel *
Drake Follmer * (Captain)
Shane Murphy *
(This list was updated 13 December 2015.)
Members marked with the * symbol were in the club last year.
To create the teams, we assigned everyone a sequential number, then used a random number generator to pick numbers for each team. We then marked each name as a builder or programmer (based on each member’s reported interests) and made swaps until the teams were roughly equal in size and type.
Note that we are no longer using the “Team A/Team B” naming structure. To avoid negative connotations (and bad luck), we’re referring to the teams by their official FTC numbers this year.
Greetings, and welcome to the 2015-2016 school year! Following some uncertainty about our club’s future, I’m happy to report that Oakville Robotics is alive and well, at least for the next year.
We have two returning members this year, Club President Jacob Kauffmann (me) and Vice President Drake Follmer. We’ve got around 15 members total. A full list will be posted once we’re separated into teams.
Speaking of teams, we’ve received funding from Ranken Technical College to cover two team registrations for the 15-16 FIRST Tech Challenge. Four of our members attended the Missouri FTC Kickoff event at UMSL, and we’re excited to get started on our Res-Q robots. We’re in the process of ordering our part kits. We’ve received a grant that will cover the new Android-based control system, and we’ve got a few outside sponsors who will hopefully cover our TETRIX kits.
We’ll try to keep the public updated on our progress once we start designing our bots. For now, feel free to contact us via the email addresses on our “About” page.
Hello! As you might have noticed, we were WAY too busy during the FRC season to post regular updates, but we were able to capture a few moments along the way.
The FRC game this year, called “Recycle Rush”, involved picking up plastic bins and stacking them on top of scoring platforms. Our team decided early on to use a forklift-like design, but we knew that it would be too difficult to slide an arm underneath the boxes. We eventually decided to use side-gripping hooks that would pull the box up using string, which would wind around a motor. Here are some pictures of the bot about four weeks in.
The only major change that we made after taking those pictures was replacing the black motors (which were extremely fast, but were too weak for three or more boxes and didn’t hold their position when shut off) with silver motors (which were much slower, but held the boxes in the air even when they weren’t receiving power.) The switch also allowed us to attempt adding a third top motor, since the rules place a limit on black motors but the silver motors were unlimited. However, we ended up sticking with just two motors due to time constraints.
Before we figured all of that out, me and my programming team had to wire up the electronics of the bot and attach everything to the baseboard. Again, we were moving too fast to take a lot of pictures, but here are a few shots of the almost-finished product:
Toward the end of the built period, we put some finishing touches on the cable management, tidying up the baseboard and creating a tight bundle of cables running up to the top of the bot (but still not attached to the back pole, as that would block the sliding mechanism.) Finally, we decided to go with a tank drive control system this year, as it seemed easier to use during the FTC and we knew we would need precision steering to guide boxes into our bot. We also used a third controller (a left-over hand controller from the FTC season) for a second driver to control the lift mechanism with. With triple the controllers from our last two FRC bots, we needed a bigger driver station. I took the liberty of designing the new station myself!
At first, I used adhesive velcro to attach the controllers and laptop to the board, but the rubber mesh worked surprisingly well at keeping things from falling off. It was lucky that we made the switch to the mesh, because when we got to the competition, the field technician deemed our laptop inadequate and made us switch to our more powerful (and larger) laptop, which we had planned on keeping in the pits to use for quick programming changes. As such, the end layout looked a bit different (less polished) than the one pictured above, but hey, that’s pretty typical for our team. The important thing is that it worked!
Here’s a video from early in the testing stage, before the switch to more powerful motors. You’ll see the box shoot up off of the table, then slow to a halt about halfway up the slide.
We also changed the black nylon(ish) cord to a thinner white string to accommodate the shorter axles on the more powerful motors.
Finally, here’s my Nerd on the Street video covering the weekend of the competition:
Overall, it was a great season for the FRC team, and a good year in general for our club. Unfortunately, our school district has decided that it might not fund our club again next year (which is sad, because they weren’t giving us any money in the first place. “Funding” means letting us in the building and keeping the lights on. We’ve always been entirely supported by fundraising and donations.) I’ll make sure to keep you all updated as to how that plays out in the fall. For now, that’s everything.
We’ve been hard at work for the FRC, but before I catch you up, I wanted to post a little more about the FTC.
Here are a few pictures of Team A’s robot, which I haven’t talked as much about. (That’s because it was never finished.)
Team A had several design problems, ranging from LEGO motors that weren’t strong enough to power the street sweeper to a conveyor belt that wasn’t solid enough to pick up balls. At the competition, Team A removed the pickup and loading mechanism, and simply drove during the matches. Due to the lightweight wood and acrylic base, the bot was able to knock over the center goal ball stands easier than many of the more advanced bots!
Here’s one final clip of Team B’s bot during the design stages. We ended up using fishing line and drawer slides for the linear bearing lift, demonstrated below. We used the autonomous period of the game to lift the slides in order to start driving as soon as Tele-Op started.
Finally, here two videos from the competition itself. The first is from the Mehlville School District’s publicity department, and the second is from my website Nerd on the Street.