Central Maryland District Event 2017

After 14 years, team 1389 has finally won an event!!!

The team was prepared for this event. The robot was tweaked. The awards team was on top of their game and the drivers had tasted the finals and were ready to try and get that blue banner.  But, the weekend started off a bit rocky.  The robot was not performing up to snuff for the first 3 matches.  But, the team rebounded and started to get the some wins.  And these wins were sweeter than those two weeks earlier because we were doing the caring.  The team went from 3 gears per match to 5 gears per match.  But then we started to trip on Sunday morning. What should have been 3 big wins turned out to be 2 wins and a loss, putting us in 13th place at the end of qualifications.

We knew we were going to be in eliminations since we were the only robot with a consistent gear pickup at the event.  And sure enough, we were picked up by the 5th seed alliance as their 1st pick.  First we knocked out the 4th seed, then the 8th seed and wow….we were in the finals again before we knew it.  On top of that, we had figured out how to score fuel for the first time, so now we were doing 4 gears, 1 KPA and a climb.  And that is exactly what we did for two big wins in the finals.  The team had finally won an event for the first time in its history.

Thanks to 1111 and all of the volunteers for making this weekend happen.  And congrats to all of the award winners;

Award Winner
District Chairman’s Award 2537
District Engineering Inspiration Award 5243
Rookie All Star Award 6326
District Event Winner 5115
District Event Winner 1389
District Event Winner 2534
District Event Finalist 449
District Event Finalist 2421
District Event Finalist 6239
Creativity Award sponsored by Xerox 4541
Entrepreneurship Award sponsored by Kleiner Perkins Caufield and Byers 1389
Excellence in Engineering Award sponsored by Delphi 3650
Gracious Professionalism Award sponsored by Johnson & Johnson 686
Highest Rookie Seed 6326
Imagery Award in honor of Jack Kamen 2377
Industrial Design Award sponsored by General Motors 4505
Innovation in Control Award sponsored by Rockwell Automation 1123
Judges’ Award 1915
Quality Award sponsored by Motorola Solutions Foundation 619
Rookie Inspiration Award sponsored by National Instruments 6504
Safety Award sponsored by Underwriters Laboratories 6239
Team Spirit Award sponsored by FCA Foundation 6239

Here are some match videos from the weekend

Greater DC district Event 2017

3 weeks ago the team hosted the 2nd greater DC district event at Walt Whitman high school.  We set up the field in record time thanks to the folks at ilite who left so much of the field assembled after their week 1 assembly debacle. The weekend started of with some setbacks on the field as the team worked to repair the robot after nearly every match.  However, much to our good fortune our schedule kept providing wins because our alliance partners were able to carry us. This all changed as the weekend went on, our robot’s technical challenges were quickly fading and we started to figure out how to drive around the field and manipulate the game pieces.

Because of the good fortune, we ended up in 13 and were picked by the 8th seeded alliance captain.  As we started eliminations it became evident that we had a winning team, we knocked off the 1st seeded alliance, then the 4th seed and before we knew it we were one win away from winning. And that is when the bottom dropped out, literally, the entire bottom of our robot fell out during the 2nd finals match. We were replaced by a back up robot for the 3rd match of the finals.  And for 3 seconds it looked liked our alliance won, then our new alliance partner’s locking mechanism failed and they fell back to the floor.

All weekend was amazing.  nearly 3,000 people stopped by to check out FRC and we hosted a Jr FLL event as well.  Thanks to everyone who helped make the weekend possible!!!!

Congrats to the following teams;

Award Winner
District Chairman’s Award 1885
District Engineering Inspiration Award 1111
Rookie All Star Award 6543
District Event Winner 4242
District Event Winner 1885
District Event Winner 102
District Event Finalist 2849
District Event Finalist 5338
District Event Finalist 3650
District Event Finalist 1389
Creativity Award sponsored by Xerox 1719
Entrepreneurship Award sponsored by Kleiner Perkins Caufield and Byers 422
Excellence in Engineering Award sponsored by Delphi 2912
Gracious Professionalism Award sponsored by Johnson & Johnson 888
Highest Rookie Seed 6543
Imagery Award in honor of Jack Kamen 5338
Industrial Design Award sponsored by General Motors 2537
Innovation in Control Award sponsored by Rockwell Automation 449
Judges’ Award 4242
Quality Award sponsored by Motorola Solutions Foundation 4514
Rookie Inspiration Award sponsored by National Instruments 6504
Safety Award sponsored by Underwriters Laboratories 4638
Team Spirit Award sponsored by FCA Foundation 5243


Here are some of the matches from the weekend

Build Week 4 2017 is in the History Books

What a week. awards, robots, planning for districts, designing t-shirts, testing final designs, finishing cad, assembling the drive train and more all happened this week.  On top of that we picked up nearly 8 new team members which brings us up to 54 students, making this the largest team we have ever had.

Let go by sub team

Awards – the awards team is putting the finishing touches on all of our awards.  we have awards due on Feb 9th and Feb 16th.  We also have a chairman’s video and a tech journal du by our first competition.

Planning for districts – we have a the pit map nearly worked out and are almost finished planning food. we are going to need a lot of help at our event being held at Walt Whitman High School on March 10-12.

Designing t-shirts – we are nearly done with our t-shirt design for the year.  Last chance for sponsors to get on the t-shirt is Feb 12.

Testing final designs – the team spent the first part of the week nailing down the geometry for the major robot components.  We are going into his season with a much better understanding of how different designs interact with the game pieces.

Finished CAD – now that our final testing is done we were able to complete our CAD. We should have something to release in the next few days.

Driver practice – drive practice continues for the 3rd strait week.  But tis was by far the coldest driver practice yet.  Since we set up outside things can get a little chillie.  Driver practice this week could have gone better though, we were plagues by breakages of all 3 working drive trains.

Drive train – the drive train is fully assembled and functioning.  We even used it for driver practice this week.  We were able to identify a few problems with the design and spent some time on Saturday getting the issues fixed.

Pneumatics – As part of this year’s drive train we have had to re learn pneumatic since we have not used them in the last few years.  We found a few leaks and learned how the pneumatics system as a whole worked.  Our system is now leak free and functioning correctly with 4 actuators.  This week we add 4 more.

Electrical – we now have our electrical board designed and mocked up.  We are putting the finishing touches on the CAD and will be getting that cut this week.  This will be the first time we have had a CNC electrical board and accounted for all of the wire runs and tubing runs.

Fabrication – We are up an running on one CNC machine this week and will soon have a second CNC running to do larger pieces. By this time next year the team will be able to make nearly all of our own parts as custom as we can design them.  This is a big step forward for us and should result in lighter more efficient robots going forward.  Also, our bumpers are nearly done.

The Robot – We are only a few days behind our schedule, but tis year’s schedule is aggressive.  We want to be completely done with the primary and secondary goals by the end of week 5 so we can work on our tertiary goals during week 6 while the code and drive team work out all of the kinks.

Scouting – our lead scout has joined the drive team this year, but that has not stopped him from putting together the stats on who we will be seeing at our week 2 event.

Coding – the team has been working on the driver station UI, octocanum code, manipulator code, vision code and Ohm (our initial build).  We have instituted code reviews and organized code merges.  This is has been helping ensure our code team that is 8 members strong aren’t wasting each others time.

Safety – we had some serious safety issue this week so we had a complete stand down and made everyone go back through tool safety training.  This was the closest we have ever been to a serious injury and definitely help put safety into perspective.  We may have lost a few hours of build season, but the time spent making sure we have a safety culture is worth it.



Lots to Review From Week 3

We started off last weekend making some parts on the CNC machine for our drive train. We learned a lot more abut zeroing than we bargained for as we found out the CNC machine was not fully calibrated in the Y. we will have that fixed on future parts.

Next up, we did some high speed driver testing to start to get our drivers used to 16-18 FPS.  Wow is that fast.  We have been getting our cycles down and have started looking at sight lines.

Our vision team was also hard at work.  We were able to get our hands on some reto reflective rope and found out we could create an auto centering teleop assist command to help us hit the rope with more accuracy.  But, we also learned that retro reflectve ropes are illegal so that is out.

Our chief strategists has been running field simulations to better understand how many balls we will be able to pick up and how quickly we can load up after all o the hoppers are empty.  It looks like the corners are the place to be fore picking up balls in a hurry.

And of course we have been building and prototyping.  We should have our drive train driving around today because of all of the great effort that has been put in this week.  On top of that we have a much better idea of how our gear intake and ball intakes will work.  As an added bonus. if we get the main robot fully functional by next Saturday, the tea already has plans for adding a high goal shooter.  If that is the case, shooter prototyping would be on the schedule in two weeks.  much earlier than we planned.

More videos can be found on our 2017 build season play list


Still Working on the Details

Last night the team was hard at work on some of the details of the final robot.  Roller intake for gear, roller intake for balls, octocannum sensor and software testing and climbing refinement.  We also did a quick review of the CAD that needs to be finished today so that we can order the remaining parts today.  Tomorrow the team will do a final design review and then start assembling the drive train. So that next week we can start driver practice and mechanical assembly.

It also looks like we picked our human players, now they can start practicing next week as well.

Have you called your sate officials about robotics yet?


Lots of Big Learning Today

The team came back from its three day weekend with a vengeance by making 3 gear picker uppers, a revised climber and got pneumatics working.  As a bonus, the team has found ourselves a new programming mentor and he has jumped right in by helping the kids organize their code.  Things are looking up.

As an added bonus, we have a finished airship to practice on and updated liftzilla drive train to start high speed driving with.

We have also starting trying to figure out the robot’s name for this season.

Additionally, the awards team is in full swing and we are working hard to get our awards videos done.

As if all that weren’t enough, the team is starting to plan our district event that we are hosting in march.

Detailed CAD is In Work

Our CAD team has been busy since Saturday afternoon when we finalized the design requirements.

We also made our first big purchase last night and should be able to start assembly of the drive train later his week. We are also going t be doing a lot of detailed prototyping to figure out exactly how our systems need to be designed to hit the cycle time numbers we are looking for.  On the down side, this is only a 3 day week for us since we have MLK day on Monday and inauguration day on Friday.  Next year we need to lobby school admins for no holidays during build season.

We Have Our Design Requirements Defined

We met yesterday to go through everything we learned this week and to come to a consensus around our design requirements.  It took a while, but we think we have settled upon a design and are readt to start detailed CAD. On top of that we started to prototype a new feature that was added today.  The ability to pick gears up off the ground.

Here is where we ended up.

  • Primary – Climb rope to the top in 10 seconds from touching the rope and stay at top past buzzer
    • Capture – Drum based
    • Capture – Use fingers
    • Capture – Use rotation
    • Capture – Catch fast 1-2 seconds)
    • Capture – Need driver camera for davits 1 and 3 to work with driver station 1 an 3
    • Climb – 5-8 seconds to top
    • Lock – Use ratchet wrench
    • Rope – Narrow rope
    • Rope – Big knot on end (monkeys fist)
    • Rope – Retro-reflective for auto assist
    • Rope – Be stiff and heavy
  • Primary – Pick up gears from the ground and drop them off at the peg with a max of 20 seconds per cycle
    • Intake – Drive by control
    • Intake – Scoop from ground while driving
    • Intake – Combine with passive design so it can pick up from feeder station as well
    • Intake – No drop design
    • Intake – will use 8″ arm to pick up gear
    • Stowage – No bump drop design
    • Deploy – Passive design
    • Deploy – Make space for peg
    • Deploy – Use drive assist camera
    • Deploy – Use auto assist code
    • Deploy – Use air ship pilot to pull gear out of robot
  • Primary – Be able to drive nearly 20ft per second and be highly maneuverable
    • Drive – 18-20 fps
    • Drive – Sideways or alignment for gears
    • Drive – Sideways for alignment with low goal
    • Drive – Octocannum
    • Drive – 4″ wheels
    • Drive – Un-actuated position is solid wheels
    • Chassis – 24″ x 24″ x 24″ or 30″ x 30″ x 24″
    • Bumpers – .5″ off ground
    • Robot – Be as light as possible
    • Root – Be as small as possible
  • Secondary – Pick up balls from the floor
    • Intake – Through bumper
    • Intake – Roller intake
    • Intake – Poly chord / belt elevator
    • Intake – Use 1 motor for intake and elevator
    • Intake – Have flap so that balls can be loaded in via the hopper or feeder station without spillage
  • Secondary – Store 20 balls or more on the robot
    • Stowage – Fixed hopper
    • Stowage – Ramp to low goal
    • Stowage – No agitator
  • Secondary – Deposit 20 balls in the low goal in less that 3 seconds
    • Deploy – Low goal
    • Deploy – Movable rake
  • Tertiary – Shoot 20 balls in the high goal in 5 seconds with 50% accuracy
    • Deploy – Use intake elevator
    • Deploy – Have two high goal positions, airship gear 1 and airship elevator gear 2
    • Deploy – Have a wheeled shooter

Over the next two days our CAD team will work on creating the robot design.  And over the next week the team will refine that design with detail prototypes. So that buy the time the parts arrive in week 3 we have the final dimensions figured out.

A big decision we made today was to use Octocannum.  This is going to be a big challenge for our team since we have not used this drive before.  We know it adds a lot of risk, but we feel the possible advantages combined with the learning we will do make it worth it.

Robot systems we need to build will have 9 motors and 8 cylinders / solenoids.

  • The Octocannum drive will require 4 cims, 4 encoders, pressure switches, 4 pneumatic cylinders, 4 solenoids.
  • The ball intake and elevator will require 1 motor for ground, 2 pneumatic cylinder and 2 solenoid for the hopper
  • The low goal scorer will require 1 motor with an encoder
  • The gear intake will require 2 pneumatic cylinders and 2 solenoids for moving the arm with 1 or 2 motors with encoders and IR range finders on the arm.
  • The climber will require 1 motor and 2 IR range finders


Here are some images from today.

Design Review Day is Here

Today we are going to review everything we learned this past week and make some big decisions.  Today is critical because it will lock in the robot design requirements and give our cad teams the green light to start detail design.  This is also the last time that all of the students will have the ability to impact the robot over all.  Next week, each student will be assigned to a detailed prototyping team whose goals are validate CAD.   Last yea we were snowed out of week 2 and part of week 3 and did not have a chance to do these detailed prototypes.  The lack of validation data definitely hurt us, as out first robot design had some major issues that were only discovered on the final robot.  These week 2 detailed prototypes will be key, if we want to be successful this season.

Some of the questions we have to answer,

  • Do we have any priority changes, will we add, remove or shift any of the below items
    • Primary – Climb rope to the top in 10 seconds from touching the rope and stay at top past buzzer
    • Primary – Pick up gears from feeder station and drop them off at the peg with a max of 20 seconds per cycle
    • Primary – Be able to drive nearly 20ft per second and highly maneuverable
    • Secondary – Pick up balls from the floor
    • Secondary – Store 20 balls or more on the robot
    • Secondary – Deposit 20 balls in the low goal in less that 3 seconds
    • Tertiary – Pick up gears from the ground
    • Tertiary – Shoot 20 balls in the high goal in 5 seconds with 50% accuracy
  • How will we climb
  • How will we receive gears from driver station
  • How will we store gears
  • How will we deploy gears
  • What drive train will we use
  • What configuration will we use A or B
    • A. 36 in. by 40 in. by 24 in. tall (~91 cm by 101 cm by 60 cm tall).
    • B. 30 in. by 32 in. by 36 in. tall (~76 cm by 81 cm by 91 cm tall).
  • How will we pick up balls
  • How will we move balls
  • How will we store balls
  • How will we deploy balls

Once all of questions are answers its on to the decisions.

Getting Ready for our Design Review this Saturday

We have at least 2 working prototypes of every primary and secondary system.  We have one last day to do crazy prototypes and then its decision time.  We will be meeting Saturday to go through all of the prototypes and research people have been doing.  The outcome of Saturday’s meeting will be the lockdown of our priorities, lock down of mechanical solutions and the agreement on a preliminary configurations.  From there the team will split into three parts.  Folks that will go heavy into CAD, folks that will continue to prototype and folks that will stat building.

We have our first two order days coming up next week and should be nearly 90% ordered by Friday.

As a bonus this year, because we had some extra help from the stage crew and we plan on being a gear team, we are building an airship.  Our airship will be complete with ropes and working gear pegs.  This will give our human play a lot more practice time than we were hoping to get.  This will also give our drive team more realistic practice.

And as a bonus, we had some alumni stop buy last night during the team dinner.  Sounds like they are having a lot of fun and miss robotics.

Here are some of photos from the night.