Hours

As a part of the process of earning academic credit for robotics, I am required to log hours spent doing robotics activities. While this log will not include every hour, it will include the majority of the time I spent working on robotics during the season.

Apart from the 193 hours during actual Build Period (broken down into days in the table above), I have added the minimum number of hours I spent at each competition (36) times 3 competitions. This total comes to 301 hours.

Unfortunately I am not able to log a significant amount of my time, because I did not log it at that time, and can no longer remember the exact hours of each session (for example, I spent multiple weekends at Mr. Reif's house fabricating parts for the team, beginning in December, none of which I am able to officially count now). Hopefully this will be a lesson learned and I will log all my hours properly next season and get a more realistic idea of the amount of time I dedicate to FIRST robotics in a season.

Update: 20.4.12

Unfortunately I have not had an incredible amount to log, and have not logged the little I have had to log. Over the past few weeks we have competed at the Central Valley Regional in Madera in order to practice with our robot Andromeda, and so that we were able to spend a last few hours working on her. We have upgraded/modified several systems, and I even designed and fabricated brakes at the request of our drivers after seeing several robots with brakes at the Central Valley competition. I designed the brakes as simply as I could, nothing more than a bracket to mount an air cylinder, onto which a rubber foot is to be threaded. This brake is screwed onto the inside of each drive-plate, and when pressurized, the rubber feet descend and apply force to the floor. According to my calculations, the cylinders will have just short of the amount of force needed to lift the robot, which means maximum braking power without the risk of the robot becoming unstable.

Wednesday we leave for Championships in St. Louis. As a part of the competition events, I have decided to design and fabricate a duct tape dress for a friend, who I will be accompanying to Roboprom. Pictures of the fabrication process to come.

More good news, I have received notice of receipt of my Provisional Application for Patent from the United States Patent and Trademark office. This means that I can now post all material regarding Project ÜberTank, as I have patent protection. I am hoping to win the FIRST Future Innovators Award presented by the Abbott Fund for that invention, which comes with free nonprovisional patent service with a patent lawyer, and the opportunity to meet with investors to help me with the project.

WE WON!

We did! It was incredible... Things have been so crazy I've hardly had a chance to even think about logging our success. I guess I should though...

It truly was a thing of luck/beauty. Our robot, Andromeda performed in a mediocre range throughout the competition. The team, however, did an excellent job of screaming our strengths from the rooftops instead of worrying all day about our weaknesses. We, a 3 year old (very new and inexperienced for FRC) team with limited resources (I suppose all teams have limited resources but sometimes it sure feels like ours are very limited) were the FIRST team to use the Kinect driver station during hybrid mode to control our robot. Even by the end of the competition, out of 50 teams many of which have been around for years and years, we were 1 of 3 teams to get the Kinect working. This is one example of a strength we screamed from the rooftops. Whenever our Kinect driver used the Kinect, the ENTIRE team stood up in the stands and mimicked his every move (arms and legs flailing). Whenever the team posed for a picture, everyone crossed their arms across their chest (the "default" position in our Kinect driver program). Another strength we focused on was our continued structure in game strategy, and ability to follow the plan we made at the beginning of the season. We were never planning on making a shooting robot. That was not the idea, so we were never expecting/ed to score. We are a defensive and assisting robot that gets to the opposite side of the field, blocks the opponent, and gets balls to the home side of the field. These two things appealed greatly to the number one alliance during the alliance picking, and we were chosen by the number one and number three seeded teams as an alliance partner.

After that, we went through every elimination round undefeated and proceeded to celebrate.

Apologies

I would like to apologize for having to take down a significant portion of my prior work on this log; a lot of what I have written about is quickly becoming rather confidential because I am applying for a patent and the FIRST Future Innovator Award for the material in question. Once I have moved past the legal humps I plan on re-publishing all the material that has been taken down.

What next?

For the next week and a half the team will be preparing for competition. The year, as far as robotics is concerned, will climax with 3 crazy 18-hour days of hurried preparations, even more hurried repairs, and a few choice minutes of adrenaline-quenched Rebound Rumble. A handful of teams will go on to Championships and experience the whole thing over again on a 10x scale.

But what about the rest of us? What is the next move? There are a million answers, for each of a millions ways of answering that question...

My answer is that I would like the team to become a company in all but the literal, legal sense of the word. Being a member of the team, like being an employee of a company, should be a privilege, not a right. Those who do not show up for work, or are not productive during the workday will be reprimanded, and if necessary, removed from the company. True accountability is yet to be achieved in this team; while what I saw this year was exponentially better than the first year I was with this team in 2010, it still needs to be improved to be a competitive team. Deadlines must be exactly that: DEAD lines. If you cross a deadline, you are, in one way or another, dead. There is no leeway, no play, no tolerance. If the robot is to be finished by 2 weeks into the build period, then that is to happen at all costs.

Another thing I would like to bring to the team is goal-based operation. One set of goals that mandates every decision, action, and lack of action on the team. Every single decision the team makes throughout the entire year is based on one set of parameters, the team goal(s), and absolutely nothing else. It is my belief that this will increase the effectiveness of nearly all decisions made on this team.

While researching on Chief Delphi, I came across a truly incredible custom gearbox build by team 192. Here is a picture...

Season's over, finishing things up...

Well... It's been a long time since I logged anything. Too long. We bagged the robot Tuesday night at 12. Most of the team was in the lab past midnight, and I got a ride home with Mr Reif at about 2am.

Based on a 30 lb repairs and upgrades rule, we withheld the Flinger (one of our various names for the shooting mechanism) in order to continue working on it. We encountered torque problems with the drive-train using only 2 CIM motors, so we changed to 4 on the drive-train. This means that we are no longer able to use a CIM motor on the Flinger (rules mandate no more than 4 CIMs on any one robot). Since bag n' tag we have been working on putting together a custom gearbox with inputs for up to 4 BaneBots 550 motors in lieu of a CIM. The likelihood that we will require all 4 to achieve the power we want in the Flinger is low. More likely we will end up using 2 or 3, however due to the incredible torque of the BB550, and our gearing down it may be possible to achieve the results we require with only 1 motor. Isaac Lozano was in charge of that project, and I helped out some when he wasn't around. Since then most of the parts have been fabricated, and we met for a small group session on Sunday with half a dozen of the mechanical team to get a good idea of what will be happening on the project, and prepare for it.

Since I last logged anything I worked on pneumatics for a short period (I was in charge of that subsystem), many mechanical people worked on the disaster that ending up not being tank treads. We had too many last-minute problems to deal with and ended up switching to wheels. A couple of impressive notes on that however, are that 1) we were able to switch drive modules from one side to another reversing the entire drive-train in about an hour. 2) we were able to change from treads to wheels in about an hour as well. These are both rather in-depth processes, and the fact that we were able to do them so painlessly speaks to the advantageous nature of the modular construction of our drive-train this year. I am currently working on the polycarbonate shield that wraps around the back of the robot, several things less robot-build-oriented such as planning of the pit for competition and putting together lists and forms for scouting other teams at competition. Scouting is a crucial, often over-looked among rookie teams, aspect of competition due to the complexity and spontaneity of FRC. As I discussed in the beginning of the season, matches consist of 2 alliances, each of which are made up of 3 teams (each with one robot). This means that from match to match, your alliance, and therefore the robots you are paired with and the strengths thereof change. A completely new match strategy must be designed based on robot and team strengths and weaknesses, as often as every 45 minutes during the tournament.

This is a picture of the robot on February 12th, things slowly coming together. In this picture one can see alligator clips attached to the motor powering the arm/scoop/appendage; we had been testing the functionality of the arm for the first time just that evening.

 Here is a picture of the robot in action, the night of bagging. The programming and drive teams were getting one feverish night of practice in before the bot was sealed away.

Another shot of the bot in action, with the arm up in this one. The electronics boards are also visible from this viewpoint.

10.2.12 Friday

Today was, for the most part, rather usual. Aron and I are working out some kinks in the drive-train, and I am transitioning over to full time integration. The best thing that happened (in my opinion) is that my new work station arrived! I now have a bleeding edge (albeit a couple generations old), extremely CAD-capable mobile HP workstation so that I can devote my life at home, at school, in the car, on the toilet... Every minute of my life I am now able to work on CAD. As soon as I get SWX installed (waiting for a code from a teammate), then I will be ready to rock.

I had a quick intellectual pow-wow with Mr. Reif on Project ÜberTank and, while I do not think it will be a part of this year's robot, I still plan on pursuing the project personally with the possibility of selling out, or developing the system specifically for FRC teams.

We also had a great end of meeting discussion about team commitment and power-build-mode which the team has yet to enable this year. In the morning we are going to have a PRE-BUILD pep-talk/rally instead of the usual POST finger-wagging in the hopes that we are able to get the adrenaline flowing properly and get everyone filing something all day like it is the last 2 days of build.

9.2.12 Thursday

Today was a relatively uneventful, however productive meeting. Drive-train, in it's roughest, least elegant form, is finished. However many "bandaids" (as Mr. Reif calls post-design fixes) are holding it all together, it is finished and works. There are improvements/issues to be addressed, such as increasing the inside friction of the tread, improving/spring-loading tread tensioners, re-machining an updated design of the drive plates... However in its current configuration the drive-train is drivable.

I worked on bumper design, and came up with an overall layout for the bumpers. The plan is one wrap-around end-piece in the back extending all the way across the back, and 8" on either side towards the front. Then each of the front two corners will have individual 8"x8" angle bumpers. The one wrap-around piece in the back will make it an easy one-piece solution, as well as increase structural integrity in the back (where this is minimal frame support for the bumper), while the minimalist approach along the sides and front will keep the bumpers easy to build, leave plenty of frame space for the robot build, and show off the sexy sides of the robot.

Provided I can finish updating the CAD files and acquire material, a team alum and mentor may be able to machine new drive plates on an NC mill at his old school and possibly powder coat them making aforementioned sides eversomuch sexier.

From now on I guess I am all integration (until we start a second bot; IF we start a second bot). With luck my new CAD workstation purchased on ebay will arrive tomorrow, and I will be up to my ears in SWX all day long.

I would also like to revisit the Project ÜberTank BoM, however modify it for a single roller design instead of double. After considering it, I think good stability and traction will still be easily attainable for possibly a significant amount less. Mr. Reif also laser-etched a key fob for me that says ÜberTread 2012 on one side, and bevel your junk on the other. Very awesome.

6.2.12 Monday

We drove the robot! Or rather, twitched the robot. Because programming has also been twitching due to the fact that they have no robot to test/break/make mechanical fix, I decided to give them SOMETHING on Monday. When Aron Linker was done with putting chain on the drive-train, I asked Geir Lindborg (original creator and captain of team, current electronics guru among other things) to throw the electronics development board on the chassis "quick 'n dirty like" so we could let programming drive it. Dev (yes, we have a programmer who's actual name is Dev) uploaded code and (the second time) it worked. We only had one tank tread, due to the fact that we originally did not order enough (when it was ordered it was for wheels not treads) and are waiting for the rest. Nevertheless, the robot did move.

It's alIIIIIIIve!!!!!!

Update: Picture

Here's a picture of the robot Saturday night after our full day of build. It is, of course, a ways from completion. This is simply a mock-up of each subsystem placed on the robot.

2-4.2.12

Well things are finally coming together. Thursday and Friday were relatively typical meetings, in neither of which was I particularly useful. Saturday I was able to put (some) real time in and get a few things done. Mostly thinking, but the fact is that must happen just as much as the making. After an integration disaster in which subsystems were not planned to be compatible (the elevator was designed and built to go exactly where the inner frame assembly is) was worked through with grinding gears and high-revs, the team got into let's-build-a-robot mode and got some good work done. In one day we went from a pile of aluminum scraps to several sub-assemblies fitted together. There is still a good amount of work that has to happen, but this season's baby is beginning to take shape.

Over the past couple of days I have developed a plan I will execute to the best of my ability and discover where it takes me. Oak Ridge High School has a manufacturing lab with (literally) millions of dollars worth of machinery. I am going to visit on Tuesday and talk to Mr. Wilson (manufacturing teacher there) about 2 things. I would like to ask permission to machine some parts for the robot, and discuss the possibility of my becoming on intern. If I am an intern, I will be able to spend All Tuesday and Thursday working on fabrication et cetera, as well as get academic credit for my work. If all this works out, then I would like to machine new, lighter, stiffer, prettier drive plates (the original design had some major flaws that have since been dealt with, however none of the solutions are elegant) and possibly even anodize them. It is my understanding that the lab has an anodizing tank, however I am not sure what size a part it is able to accommodate or if there is a cost for replenishing supplies. In addition to robotics parts, I have a variety of projects that I would love to continue with the use of a CNC mill and/or 3d printer.

30-31.1.12

Monday and Tuesday have been relatively uneventful. I now have the correction plates for the design screwup in the drive plates fully fabbed and have started installing them.

I had fun today (Tuesday) teaching myself to power tap. I saw Mr. Van Dyke power tapping PVC over the weekend and was captivated. After asking him about it, and doing some reading at home, I decided to try it with a larger tap (1/4-20) and soft (6061) material. While I was relatively shy at first and wasn't making it all the way through the .125" plate, I did eventually get the hang of the basic idea. The process of power tapping consists of using a drill press or mill as a framework for tapping instead of attempting to line things up by hand, as well as doing so under the power of the drill or milling machine motor. The way this is done is by placing the tap in the drill chuck and hand-tightening it; the reason for hand-tightening only is that it causes the chuck to act as an artificial torque-clutch slipping before breaking the tap. Then (with copious amounts of cutting fluid) one spins the tap up to speed by turning the drill press on, brings the tip down to just above the surface, quickly shuts off the drill press (or mill) and plunges the tap into the hole, letting it coast through (the whole process is done with very little pressure). Overall, I'm excited to keep improving my tapping skills.

Last night and today I did some work on my own time on the materials of Project ÜberTank, and discovered that this program will require a good bit of funding to manufacture at the level required for an FRC robot. The shear amount of tread required for a robot that is 37"x27" is quite large and rather expensive. A preliminary run-through of the parts and materials on McMaster-Carr ended with a total price for just the tread being close to a thousand dollars. While I was slightly deterred at first, Ms. Lindborg told me to go forward and not let money stop me. Whether this is a true commitment from the power that controls team money to go through with it, or simply her curious as to what I am capable of, is something I do not know. Time will tell, I suppose...

The current BoM (Bill of Materials) for a single linkage:

• 3.25" 6061 aluminum round-stock of a 0.25" diameter (McMaster #8974k31)
• 1.5" W1 water-hardened tool steel of a 0.125" diameter (McMaster #8890k18)
• (2) 1" long nylon spacers of a 0.5" o.d. (Outside Diameter) and a 0.25" i.d. (Inside Diameter) (McMaster #94639A506)
• (1) 0.75" long nylon spacer of a 0.25" o.d. and a 0.14" i.d. (McMaster #94639A305)
• 2" latex tubing of a 0.75" o.d. and a 0.5" i.d. (McMaster #5234K85)
• (2) self-locking retainer clips for a 0.125" shaft (McMaster #98430A116)

With these parts/materials the cost for one 1.25" link is $5.71, and with a rough estimate based on the size of our robot the number of links needed will be approximately 165 links. Do the math and you get well over $900. This number of links does not account for the lot size of parts on McMaster-Carr (it will not be possible to buy the exact number of parts/amount of material needed), nor does it consider spare parts or extra material for manufacture error.

On top of all this comes nearly every significant problem that we had with the first "standard" tank drive (machining the Drive Plates, et cetera...), as well as the necessity to fabricate some sort of sprocket system for holding/powering the tread.

While I have not given up (yet), this is proving to be an incredibly costly and in-depth project. We will see what more is to come.

21.1.12 Sunday CAD

I believe I have spent a cumulative hour or two away from the computer starting the minute I woke up at 8 this morning. I have been glued to SWX, organizing team CAD files, designing a solution to the misplaced gearbox conundrum, and reworking old, outdated, and unfinished CAD work. The result is, among other things, one sexy looking chassis....

26-28.1.12

Things are finally starting to come together! Thursday meeting I saw some people beginning to really work on their own on the robot and Friday it took off. Groups were autonomous, fabricating and designing like I've never seen this team work. Friday night I brought home the drive plates I spent so much time designing, and Mr. Reif machined during the week. It was not easy to design, and not easy to machine. The hardest part is probably that after the dozens of hours that went in to designing and fabricating these plates, they have some serious design flaws/issues. First of all, even though I spent a lot of time on them, I was still rushing through and did not CAD all the parts of the drive modules. Because I couldn't see how all the parts would go together in 3D, I placed the mounting points for the gearbox/motor assemblies higher than is feasible. The current placement interferes with the frame and tread.

I worked last night after our meeting, and will continue to work today on a solution. I need to design a sub-plate that essentially moves the mounting holes for the gearbox down. I have the material here to fabricate these plates assuming I am able to finish. Also on the list of things to do today is spending 2 hours or so putting up flyers for our upcoming ewaste fundraiser on February 11th.

Here are a few pictures of the Drive Plate in CAD and the fabrication process...

21-24.1.12

I am home getting some school work done (and writing an entry for my engineer's log) after a long 4 days of robotics work alternating locations between the Robolab and the home/shop of our main technical mentor Adam Reif. While I thought I was finalizing designs Sunday, little did I know. I spent all Saturday night, all Sunday, all Monday night, and all Tuesday working on that same set of CAD files (among a little bit of other big-picture CAD work). I ended with a set of files and drawings that I am very happy with. Mr. Reif pushed me to fix every single bug, design flaw, SWX (Solidworks) getaround, screen-blip, and assumption in my design until I had something I can both be proud of having created, and present to potential employers as prior design work. After revision upon revision, and printing half a dozen differently new/updated drawings, I am not only not sick of working with SWX, my passion is newly stoked. I have spent the evening reading, watching videos, learning more about using SWX to its fullest.

Unfortunately, due to the shear amount of time it took to complete the drive-train "Drive Plate" design, I will not be able to machine the actual part. When I left Mr. Reif's house, we had discussed every nuance of the design, and had cut and laid out the material to be machined. Even though two plates are needed (a right and a left), only one needs to be machined because they are identical so the machinist is able to stack the two and machine them at the same time. While this seems completely straightforward, and even obvious, I had not considered the idea until Mr. Reif mentioned that that would be the most efficient way of going about it.

While perusing the interwebs I came across an incredible reference for all things FRC. From how to weld and where to buy tools, all the way to a hyperlinked list of other robotics competitions; it's all on the Hauppauge Robotics Eagles website under files.

The next robotics meeting is Thursday 26.1.12 from the end of school (the team draws students from 6 different schools so the times are not the same for each person) until 8. I will try to remember to export a jpg or two of the weekend's design work.

21.1.12 Saturday Meeting

Written Sunday 22.1.12 morning:

Saturday morning my mother snuck out of work for 30 minutes in order to get me to the Robolab. The meeting started later then I thought, however I had a jacket and little was lost. Saturday was quite productive for the chassis and drive-train teams. Aron Linker worked on finishing the designs in detail for the drive-train modules, while I finished designing and then fabricated the inner frame. We now have a complete frame, and I am writing this post off and on throughout the same day (Sunday) that I am finalizing CAD drawings of the drive-train for fabrication. I hope to finish machining the parts needed for drive-train today, and have a complete robot chassis Monday 23.1.12.

Here are some pictures I never managed to post of the newest version (1.2) of ÜberTank...

A single link separated from the chain.

A full, 36 link assembly with a sprocket at one end (~8" diameter sprocket).

16-20.1.12 Monday-Friday Meeting(s)

**I wrote this Saturday (21.1.12) morning waiting for the Robolab to be opened and Saturday meeting to begin.

Well I have really been slacking off with regards to logging my robotics work. Almost a full week has gone by. I'm not going to pretend I remember everything that has happened, but I'll do my best to sum up where we've gotten. The Chassis and Drive-Train team (Aron Linker and me) have designed a highly modular drive-train which will enable us to switch between a standard treads and our own proprietary omni-direction treads (Project ÜberTank). The basic frame is complete, with some inner structure for mounting robot componentry the only thing that remains.

14.1.12 Weekend

Wow! It has been a long, roboticcy weekend. After the meeting Friday night ending at 10, my dad and I got up early Saturday morning and hit home depot for emergency prototyping materials. We spent the morning fabricating a proof of concept for Project ÜberTank. The results were rough, but worked. We ended up with a three-link chain, each link with two rollers perpendicular to the axis of tread rotation. The chain/tread has incredible traction, however rolls sideways with very low friction exactly as intended.


At the Saturday robotics meeting, I presented the prototype to the team and spent the day working out design issues with the robot chassis and drive-train layout. All of our major issues were resolved, and we ended with a modular design that will allow for the possibility of both traditional treads, and ÜberTreads.






Here are some CAD screen captures of both version 1.0 and 1.1 of ÜberTank.

 "Linkage Plate" from version 1.0: A plate of aluminum with slots machined for attachment of the roller axles, as well as depressions to prevent slippage on contact with a drive (or floating) sprocket.

Single version 1.0 link.

 Alternate view of version 1.0 link.

 Full assembly of six version 1.0 links.

 Single version 1.1 link.

Alternate view of version 1.1 link.

Assembly of six 1.1 links. In 1.1 the drive or floating sprockets have concave teeth on which the crossbar between each linkage bar can rest. This design should reduce weight and wear due to the fact that the round crossbar will wear significantly less than the filleted depressions in version 1.0. Also, due to the decrease in the amount of material, it is possible to use a lower-wear material for the crossbar such as stainless steel (as opposed to aluminum).

While I don't have any pictures of the fully assembled prototype yet, I plan on taking some tomorrow (Monday the 16th) in the robotics lab. Here are a few photos of the prototyping process Saturday morning.

Dad working on rollers for prototype Saturday morning.

Me drilling assembly and axle holes for prototype Saturday morning.

Stacks of two different aluminum parts for prototype.

Mr. Reif enjoying a cupcake to its fullest at Saturday meeting in the lab.

Up we go

Early start to a long day: its 5:45. During Build, if I want "spare time," this is how it happens. I'm going to go make stuff.

Until tonight...

13.1.12 Friday Meeting

Long day. We had a ~2-10 meeting in which we made some good progress. I was working on chassis and drive-train with Aron Linker, and had some very serious design issues. We had problems due to maximum dimensions and creating the ability to go over the 4"x6" bump in the middle of the field. We are still quite unsure as to what to do, however we settled (pending...) on a very short, wide chassis design with a high-strength, dual purpose "arm" for both tipping the bridge, and for assisting in balance when crossing the bump.

Not much more tonight. I want to get to bed early as I have early-prototyping plans for the morning. More on that tomorrow.

Also hoping to load some screenshots of the CAD files from Project ÜberTank, as well as some truly inspiring footage of our main technical mentor Adam Reif.

12.1.12 Thursday Meeting

I do not have a lot to report on from today's meeting. I started out doing some  CAD work for Project ÜberTank, mostly cleaning up/reworking existing design drafts from Tuesday. I have most of the designs cleaned up so they are not only modeled, but well modeled. I have never had much problem making things in Solidworks, but thinking ahead towards more complicated assemblies etc... has always been a challenge for me. This project is forcing/enabling me to take my CAD skills to the next level by creating a well done, complete set of designs for the project.

After spending some time on ÜberTank I went on to work with Aron Linker on some fundamental design decisions regarding the chassis and drive-train.

I left 2 hears early for a quasi-emergency doctors appointment so I look forward to being brought up to speed tomorrow.

10.1.12 Tuesday Meeting

Today we met from 3 to 6. As a whole, the team spent a good deal of time discussing design (even more), however I was not as involved in that as previously. I focused on Project ÜberTank with Sam Sedgwick. ÜberTank will be the operating name for the development of OmniTreads. We spent most of our time (apart from design discussions) CADing the preliminary design, under special orders of the team coordinator Mrs. Lindborg. We were able to complete a model of both a single tread link, and a working flexible chain of several links. This is a preliminary design and will be refined greatly, however a first pass in under 48 hours from concept to full CAD model is better time than I could have asked for. Due to my involvement in such a covert (sideline) mission, I am hoping to be issued a Solidworks capable computer to enable me to work on such things, as well as other (more central) team related CAD assignments from home. Unfortunately I was unable to prepare screenshots/renderings of the model. I hope to do that during our meeting Thursday (no meeting Wednesday), however I will be leaving early so I don't know whether I will have time. When I have them, I will show them here.

The design (as seen in a basic, incomplete sketch in yesterday's post) is as simple as could be managed while maintaining ease of fabrication and relatively low cost.

No meeting tomorrow, I will post Thursday night after my appointment (for which I am leaving early).

9.1.12 Monday Meeting

Today was my first day at Shenandoah High School. School went by quickly enough, and I was able to get on with robotics. We spent another entire meeting researching and discussing design, we are several days behind schedule now. While this does not sound "good," at the some time it is to be, to a point, expected. If we are able to get through and finish the big picture design tomorrow so that we may come back Thursday and hit the ground building, I believe we will be in good shape. We talked about different types of ball collection devices, ball launching devices, and we dabbled for moments here and there in different possibilities for the drive train. My opinion with the 4"x6" rectangular-profile obstacle running across the middle of the field, treads may be our best option. In the 3 regional competitions I've been to, I don't remember seeing any group of 5 or 6 winning teams in which there were not at least a pair of treaded 'bots. It provides incredibly effective traction, mobility, and in the case of the obstacle in this years game protects any components mounted to the underside of the robot. For my homework tonight I did a couple of sketches. I sketched the parts needed in a semi-fantastical idea I had to create OmniTreads: tank treads with the holonomic aspect of omniwheels (not mecanum wheels). I also diagrammed a few key points regarding a collector consisting of a 2" spinning "roller' with sticky, compliant foam wrapped around to suck in any basketballs that are unfortunate enough to come it contact with said device.

The closest things to decisions we made today were eliminating about 95% of the possibilities for different types of collectors, elevators (a mechanism to bring the ball from ground level where the collector is up high to the launcher), and launchers. Tomorrow we still have to finalize decisions regarding those, as well as discuss our drive train.

8.1.12 Sunday Meeting

This morning I woke up to my mother saying, "Avery, maybe you should get up..." When I asked what time it was and she answered 10 (the time robotics was starting this morning) I amazed both of us with my speed. In the lab we decided upon a final game strategy. Personally I am very happy with where the team ended up. While our decision is far from the strategy that I initially envisioned, that is far from what is important. What I believe is important is the fact that the team has, with some time and effort, unanimously agreed on a game strategy that is (once again, subjective here) simple enough for the team to successfully build a robot that could potentially dominate. We decided on a robot that will have the ability to rapidly gather (foam) basketballs from the ground and fire them to the other side of the field, as well as have some significant thought put into balancing on the appropriate alliance bridge in the middle of the field.

Tonight's "homework" was to consider and sketch some different ideas/designs for a gathering mechanism and a firing mechanism. I skimmed through a book on the 2006 FRC game which in some aspects was similar to this year's and settled on a firing mechanism that was discussed today in the meeting as well. I sketched that up very quickly, but spent most of my time brainstorming the strengths, weaknesses, and possibilities with a system like that. I also put a few ideas on paper all together in a detail-free semi-comprehensive sketch of a robot chassis with a gathering mechanism roughed out.

Monday school starts and after school we have a meeting from around 1 until 6.

Kickoff

Well, today was the big day. We got up at 5am and trucked all the way down to St. Francis to discover the nature of this year's FRC. I am VERY excited about the game this year(Rebound Rumble). A derivative of basketball, I believe the 2012 competition will be an incredibly intense and difficult season for even the most seasoned veteran teams. It seems after 2 decades of hard work, FIRST wants to push us even harder!

Actual Kickoff went quite well, and the brainstorming session held in the 3189 RoboLab also went well for the most part. Tho good about today's meeting was that a LOT was said and the structure that was put in place by last year's Task Force did a great job of forcing the team to learn the rules and understand the game before we even started discussing possibilities for the season and robot. Unfortunately I feel some of the other work done by the Task Force is being partially ignored by the majority of the team. The conclusion made by the Task Force over last summer was that the greatest source to date of 3189's failure is our tendency to try to create a robot that is capable of doing everything on the "checklist" of tasks FRC gives us each year. The Task Force also concluded that the "solution" is to choose a select few functions for the robot to perform, and perform well. At the end of today's meeting the team was split with the majority leaning towards a multi-purpose robot: exactly what the Task Force recommended against. The final discussion will happen tomorrow morning when people are rested and less irritable. Time will tell what game strategy the team chooses.



Without watching the Game Animation (above) or reading the Manual, it is difficult to really understand how the game works. It is played on a 27ft by 54ft field, with 4 basketball hoops on each end of the field at 3 different heights. The MS Kinect sensor seems to be legal in virtually any use or configuration. From usage on the 'bot to as a controller, FIRST really wants to let team creativity rule all with this particular donation. Apart from the Kinect, the Kit seems to be pretty standard. It appears the included wheels have changed this year, and the First Choice program (used by teams to purchase additional parts with points allotted by FIRST) is back for a second year in what appears to be a much more streamlined version 2.0.

Tomorrow (Sunday) all-day meeting will be used to
     1) Finalize game strategy (was supposed to happen today).
     2) Inventory KoP (Kit of Parts) in order to ascertain whether a missing parts request must be sent in.
     3) Develop (Discuss, evolve and finalize) overall robot design