GM Canada Team 772Sabre Paw


Home
Current Season
The Team
Media - Photos, Videos, & Articles
About FIRST
Sponsors
Members
Links
Previous Years
News Archive

Sabre Bytes RoboticsLogo

AIM HIGH: 2005-2006

2006 for Sabres Robotics

  • Results for all teams in the 2005-2006 competition
  • Competitions:

  • 2006 Kickoff: Toronto, ON = January 7th, 2006
  • Finger Lakes Regional: Rochester, NY = March 9th - 11th, 2006
  • Waterloo Regional: Waterloo, ON = March 23rd - 25th, 2006
  • Greater Toronto Regional: Mississauga, ON = March 30th - April 1st, 2006
  • FIRST Championship Event: Atlanta, GA = April 27th - 29th, 2006
  • The Bytes had a good season, placing well at most of the competitions, but unfortunately, not well enough to snag a top place at Atlanta. Still, everyone had a fun time trying and had some great experiences. They did however, manage to capture the spirit award and the safety award.


    Week 6 (February 13th - February 17th) Goals:

    Manufacturing:
    - Test the shooting mechanism.
    - Make sure the drive train is operational.
    - Drill holes to decrease the weight of the robot.
    - Continue practicing with the robot.
    - Make the crate for the robot.

    Communications:
    - Continue fundraising efforts.
    - Finish the promo and kickoff video.
    - Finish the promo and kickoff video.
    - Start to make buttons for promotional use.
    - Organize the Zehrs Malden media event.
    - Work with A Channel for a promotional T.V. special.
    - Plan the parents meeting.
    - Put together the form packages for the trips.

    Week 5 (February 6th - February 10th) Goals:

    Manufacturing:
    - Mount the shooting mechanism to the drive train.
    - Make the drive train operational.
    - Drill holes to decrease the weight of the robot.
    - Conduct light tests with the onboard vision system.

    Communications:
    - Continue fundraising efforts.
    - Plan going away party for the Public Relations Leader.
    - Finish the promo and kickoff video.
    - Start to make buttons for promotional use.
    - Revamping the Media Section of the website.
    - Go to promotional event at Centerline.
    - Organize the Zehrs Malden media event.

    Week 4 (January 30th - February 3rd) Goals:

    Manufacturing:
    - Finish the manufacturing of our drive train.
    - Make the drive train operational.
    - Drill holes to decrease the weight of the robot.

    Communications:
    - Continue fundraising efforts.
    - Finalize and execute the Friday Night Fallout (Valentines Day Edition).
    - Finish the promo and kickoff video.

    Week 3 (January 23rd - 27th) Goals:

    Manufacturing:
    - Finish the construction of the playing field.
    - Continue to manufacture the drive train.
    - Begin tests of the vision camera.

    Communications:
    - Continue fundraising efforts.
    - Continue to plan for the Friday Night Fallout (Valentines Day Edition).
    - Continue to work on our promo and kickoff video.

    Week 2 (January 16th - 20th) Goals:

    Manufacturing:
    - Finish the design of the robot.
    - Members continue to present their ideas to the whole team.
    - Start the construction of the playing field.
    - Start the manufacturing of our drive train.

    Communications:
    - Continue fundraising efforts.
    - Continue to plan for the Friday Night Fallout (Valentines Day Edition).
    - Send thank-you letters out the sponsors.
    - Start to work on our promo and kickoff video.

    Week 1 (January 9th - 13th) Goals:

    Manufacturing:
    - Start to design the robot.
    - Hand out copies of this year’s manual.
    - A timeline will be determined for the construction of the robot.
    - The animation will be shown to the whole team.
    - Members present their ideas to the whole team.

    Communications:
    - Continue fundraising efforts.
    - Finish planning for the Devonshire Mall season kickoff.
    - Start to plan for the Friday Night Fallout (Valentines Day Edition).




    The 2006 Game - "Aim High"

    The FIRST assignment for the year 2006 is called AIM HIGH. Two alliances, red and blue, compete in each match - In each alliance in the game there are 3 teams and accordingly 3 robots. The game target is to gain a higher score than your opponent alliance by scoring balls in the center or corner goals, by winning the autonomous period, and by having robots on your platform at the end of each match.
    A ball scored in the center goal is worth 3 points, and a ball scored in the either of the corner goals is worth 1 point for the alliance whose driver’s station is opposite the goal, when that alliance is designated as playing offense. The alliance that has the highest score at the end of autonomous period will receive a 10 point bonus. One robot on a platform or ramp is worth 5 points, two robots are worth 10 points and 3 robots are worth 25 points.
    A match length is 2 minutes plus 10 seconds for an autonomous period. The autonomous period, starts the match. After the autonomous period there are 2 minutes of tele-operated game play, which are separated into three periods and each one lasts 40 seconds.
    The alliance with the highest score at the end of the autonomous period will play on defense during the second period. The alliance that was on offense for the second period will play on defense during the third period. Both alliances may play offense or defense during the final period (balls scored in all goals will be counted). It is a good idea to co-operate with other teams and remember that the points of the other alliance give a ranking bonus at the tournament. Each team gets a kit of parts and the possibility to purchase extra parts (not from the kit) to the robot, and six weeks to build their very own FIRST robot.

    - Back to top

       -previous years
    Old news...

    TRIPLE PLAY: 2004-2005

    Team 772 ends its season among the Champions of FIRST

    Please see the daily updates from Atlanta here

    Check out 
my sweet army

    -Back to top

    Club Sandwich Shines in FIRST's largest regional

    See the live updates from Mississauga

    The Sad Walrus 
owning

    Although our performance at this regional came to an abrupt end, the Sad Walrus was one of the dominant forces at the Hershey Center.

    We could tell we had one of the better robots in the practice rounds, even though not all the robots even showed up for them. This was proven when the qualifying rounds started and we won our first match. However, it was a very low-scoring (4-0) match due to penalties so we weren't as high in the rankings as we wanted with one win.

    Karthik with Incentive As the matches progressed we were up to a bumpy start (we lost our second match) but we came back in style and won every match after that except one, which we lost by two points because of a 10 point penalty. This put us in an extremely good position after the qualifying rounds, and we were 7th out of 66 teams, certain to enter the elimination rounds.

    However, before the elimination round started some exciting things happened. First of all, we received the Team 1547 "Where's Waldo" Team Spirit award, which, considering how energetic the Waldo girls are, was a great honour. Additionally, we registered for The Championship, but at the time we weren't sure if we would go or not; only time would tell.

    For the elimination rounds, we were very excited to be the second pick out of every team in the competition. The second alliance, lead by team 1241 (the third place team), and with the assistance of team 1006, became the GM Alliance of this regional event. We went into our first match against the fourth alliance (1482, 773, 1330) feeling extremely confident, and our team dominated the field. Before the penalties had been called the score for the match was 69-30 for us, but as it turned out, 40 points in penalties were called on our partner, 1006, and we lost the match by a single point.

    We knew we were the better alliance and were confident we could come back with two straight wins. As the second match started things were looking good, but after the Sad Walrus went to the auto-loading zone to get another tetra, it stopped moving. This problem hadn't happened to us since the practice rounds in Rochester, and this was the worst time it could come back to haunt us. The problem was that our battery connection had not been zip-tied together before the match, and it came loose. This disadvantage was too much for our other two team members to handle and we ended up losing, and our time in the competition was over.

    We are proud that we were able to compete so well against so many teams, and we left Mississauga satisfied with the knowledge that this is the best we had ever done. But we were hungry for a little more...

    Club Sandwich and 
Where's Waldo

    -Back to top



    Club Sandwich Leads #3 Alliance and wins Autodesk Visualization Award

    See the live updates from Waterloo

    Well if we were the sleeper robot of Finger Lakes, we certainly woke up in Waterloo. The Sad Walrus performed beautifully, and was definitely one of the stars of this regional competition.

    At the end of Friday we were ranked 3rd out of the 24 teams with 5 wins and 2 losses. On Saturday we had a few tough opponents and lost another two matches but won three more to end up in 5th place with 8 wins 4 losses. Additionally we gave the #1 seeded team (team 68) its only loss of the entire competition and held the highest scoring match of the elimination rounds (74-9).

    Although we did not make it to the finals our amazing alliance was certainly capable. For the first time ever, Club Sandwich lead the #3 alliance in this competition with teams 188 (Blizzard) and 1503 (Spartonics). Team 188 had won the Xerox Creativity award on Friday for their unique tetra grabber which is able to hold two tetras and drop them one at a time. Team 1503 was a rookie team who had proven themself on the field throughout the entire competition with their extremely versatile and reliable robot.

    In the quarter finals we eliminated the #6 alliance (758/1114/843) in two straight matches with scores of 79-4 and 66-0. In the semi-finals we faced the #2 alliance (1084/40/1605) and lost the first match 66-28. Before the second match we tried to call a time-out since our chain had broken on one side, but we couldn't because we had to call it within 3 minutes of the last match. We ended up running with just one of three wheels spinning on one side, but we had made three rows and would have had a score of 48-30 for us, but after penalties the score came to 20-18 for alliance #2 and we were eliminated. The 30 point penalty our alliance received was a loading zone infraction that was caused by the other alliance forcing 1503 into one of their own robots while it was still in the loading zone. Unfortunately we were not able to see a tape to confirm whether this was the case, but regardless the competition proceeded without a hiccup.

    See a video of our second quarter final match here (41 MB).

    In addition to our robot's performance, Aruj Chawla, Deniz Alpas, and James Herdman received the Autodesk Visualization Award for their hard work. As rookie animators, this is a great accomplishment for the three of them. They are now eligible to be judged at The Championship in Atlanta both for the National award and for a Rookie Animation award.

    -Back to top



    Team 772 Takes Home Silver for the First Time Ever!

    See the live updates from Rochester

    Hey Everyone,

    Our team getting announced during the finals There is mention we are a sleeper robot this year. Well thats not hard to understand after we finished 32nd out of 33 teams for the qualifying matches at the Finger Lakes Regional this past weekend. Once our robot got working there was no stopping it. After the first two days of competition Club Sandwich came out stronger then ever. The Sad Walrus was a force to be reckoned with. We were choosen to be in an alliance with teams 229 and 1507 to make up the 4th seed alliance. Our alliance then went on to win the quarter finals 2 matches straight taking out the 5th seed alliance (1567/1126/145) and then we faced the 1st seeded alliance (237/217/340) and made a huge upset taking them out with 2 straight wins once more.

    For the first time Club Sandwich went to the finals with their alliance. The 4th seeded alliance had to take on the 2nd seeded alliance (191/494/639). Again we were the underdogs looking to make another upset. We took the first match in a close battle to the buzzer. Then however the 2nd seed alliance took the next match with some agressive play to just sneak past our alliance to tie up the best of three 1-1. In the deciding match it was again very close. Either team could have won. Team 1507 just at the end of the match accidently knocked the centre goal which in turn resulted in tipping the tetras over negating the diagonal row of blue tetras and after a long thought out decision the refs decided that the 2nd seed alliance was to win the Finger Lakes Regional. You may see the video at the link below. This was by far the best Club Sandwich has ever done at any regional event despite the poor qualifying standings we recieved. The 
Website Award! GO WALRUS!!!

    Final Match Of FLR Finals Video (14 MB, *.wmv format)
    Courtesy of Team 639 (Code Red Robotics)

    Club Sandwich also took home the Finger Lakes Regional Website Design Award for the first time ever. Great job Phil and Andrew.

    A special thanks goes out to 1507 and 229 for allowing us to be in the 4th seed alliance it was a great honor. Next Club Sandwich looks to head to the Waterloo Regional. Will you be ready for The Sad Walrus? The Sad Walrus will be looking to make its presence known once again come Easter weekend.

    -Christopher Kelly


    -Back to top



    Week of February 14th-18th

    To all members of the robotics team,

    The final week is here...so we don't have any time to waste.

    Here are the final goals:

    1. get the plywood for the crate
    2. build the crate
    3. build the operator's interface
    4. place the sponsor's logos on the robot
    5. figure out a way to program the camera
    6. Inspect all of the mechanical parts
    7. Inspect all of the electrical parts
    8. Create a 'cost list' for the robot
    9. File any sharp edges
    10. Check the robot to ensure that it will pass the 'robot inspection' at the competition
    11. Check the final weight of the robot
    12. Choose drivers for the robot
    13. Record dimensions of the robot parts (if not done already) so that spare parts can be made
    14. Run a 'stress test' on the robot

    Also, I will be taking a FINAL team picture later this week. It will occur at 4pm, but the day will be decided during Monday's meeting (so that we can choose a day when everyone is available).

    The finish line is getting closer,

    PS: If anyone has 80A (blue) camera filter that I can borrow for the team picture (preferably 58mm or larger) please let me know.

    -Back to top


    Week of February 7th - February 11th

    To all members of the Robotics Team,

    Here are the goals for this week:

    1. Choose the drivers (Graeme will be building an obstacle course and testing everyone's speed and accuracy using last year's robot)
    2. Get plywood to build the shipping crate (we will be trying to get it donated)
    3. Mount optical encoders
    4. Mount camera
    5. Build/repair robot's operator's interface
    6. Finish building the robot's cart
    7. Wire 'quick disconnect' cables to the winch
    8. Plan for the placement of the 'team lights' (to be mounted at the first competition)
    9. Find a way to speed up the lift

    All of these things should be finished on Friday in order to allow the programming section to write the autonomous code.

    Please note that the LaSalle post will be coming in on Monday to interview a few people.

    -Back to top


    Week of January 31st - February 4th

    To all members of the Robotics Team,

    We just passed the half way point of the 6 weeks. As a result, we now have to work a lot quicker.

    Here are the goals for this week:

    1. mount the pneumatics (solenoids, gauges, etc)
    2. complete the electrical wiring
    3. mount the camera
    4. make & mount winch for "arm"
    5. get supplies to create the 'shipping crate'
    6. choose 2 drivers for the robot (for the competitions)

    Because the exams are done on Tuesday, and there are no classes on Wednesday, we will be working late on those dates.

    As well, we may be coming on Saturday (please check your e-mail late this week for the decision).

    Here is the schedule for this week

    Monday: After Exams (~9:30a) to 2:25p
    Tuesday [last day of exams]: After Exams (~9:30a) to (Late....8:00p ???)
    Wednesday [no classes]: 10:00a to (Late...8:00p ???)
    Thursday: 2:30p to (Late...8:00p ???)
    Friday: 2:30p to (Late 10:00p ???)
    Saturday: {To Be Determined}

    Good Luck on your final exams.

    -Back to top


    Week of January 24th-28th

    To the members of the robotics team,

    Here are the goals for week 3,

    1. Install the new drive system
    2. Investigate the use of Accelerometers and Gyros
    3. Begin electrical work

    However, because of the upcoming exams, we do NOT expect everyone to come. Your education is more important. However, if you do have time, this is the schedule for working this week (estimate):

    Monday - Tuesday: 2:30p to 6:00p
    Wednesday: Nothing (STUDY FOR EXAMS)
    Thursday: After Exams (~9:30a) to 2:25p
    Friday: After Exams (~9:30a) to ??? (to be determined)

    Good Luck on exams.

    -Back to top


    Week of January 17th-21st

    To the members of the robotics team,

    Here are the goals for Week 2:

    1. The drive system should be setup and ready to go.
    2. The electrical area of the robot should be designated (so that the electrical components can be mounted)
    3. The e-mail list should be finalized.
    4. A list of additional parts should be made and ordered (Electrical: PWMs, cables, Relays, Radios...etc. Programming: Optical encoders...etc)

    Please note that Graeme and myself will be taking a team picture (1 of 2 during the 6 weeks period) on Monday at around 4pm. This is for all students, teachers and mentors.

    -Back to top


    Week of January 10th-14th

    1. Monday January 10th, mandatory meeting for all members of the team.
      • A video of the dynamics of the competition will be shown.
      • The PDF manual of the competition will be downloaded and handouts made for Leaders.
      • Handouts of various aspects of the competition will be handed out to Leaders and timelines will be determined.
    2. Tuesday, January 11th,
      • Brainstorming begins. All students of the team must participate. You will be required to sketch your ideas of a robot that can complete all the requirements of the game. Check the parts list and look at the number of motors we are given and take into consideration the motors that must be used on the drive train. Give me your sketches on Tuesday morning to make overheads for your presentations.
      • Software manipulation should begin with practice on last year’s robot. Download the new C package.
      • All sections continue to work on their own requirements for the competition under the direction of their leader.
    3. Wednesday, January 12th
      • Continue Brainstorming. Refine ideas.
      • All sections continue to work on their own requirements for the competition, under the direction of their leader.
    4. Thursday, January 13th
      • Continue Brainstorming. Refine ideas.
      • All sections continue to work on their own requirements for the competition, under the direction of their leader.
    5. Friday, January 14th,
      • Continue Brainstorming. Refine ideas.
      • All sections continue to work on their own requirements for the competition, under the direction of their leader. Plan work to be done the next week.

    -Back to top


    2005 FIRST Robotics Competition Kickoff: Robovation - Ontario Science Centre

    About the 2005 Robovation Game

    Congratulations Team 772 on a job well done on the EDU robot you guys performed excellent in the ROBOVATION CHALLENGE 2005. I must say I did once again lose my voice at the competition. The team finished with a total of 4-0 in the qualifying matches and because of the scoring method Team 772 placed 3rd after the qualifying matches. The team went on to the playoffs and lost its first match, tied in its second match and then lost its third match and was eliminated by governer simcoe (Simbotics, 6th seed). All teams did very well I must say and had great robots. Once all the information is gathered (stats, pictures, maybe video) look forward to some documentation of the Team 772's performance.

    All and all the kickoff event was a great experience and the team is off to a great start. By the next event make sure EVERYONE KNOWS SANDWICH IS PRESENT. Would you like fries with that... was a great way to make the crowd pick us out... Lets supersize our Team energy this year, I will, can you? Can you smell what the Sabres are cookin?

    -Christopher Kelly

    - Back to top


    The 2005 Game - "Triple Play"
    Source: 2005 FIRST Robotics Competition Documentation: Section 0 - Introduction

    Triple Play Flash Simulator - Courtesy of Team 599

    "Triple Play" will present the teams with several new challenges:

    • A 3 vs 3 competition
    • A fresh, new shape for both the game object and the [scoring] goals, namely the tetrahedron, which is basically a 3-dimensional triangle.
    • A vision system. (camera and associated electronics)
    • A larger playing field (3' wider and 6' longer than the 24' wide x 48' long 2004 field)

    Playing 
Field
    An aerial view of the 2005 playing field would show the observer:

    • Nine goals configured in a 3x3 matrix.
      • 3 goals at each end of the field along the driver station wall(in marked zones called the end zones
      • 3 goals at midfield
    • Game tetrahedrons (aka, "tetras") hanging in the four corner goals.
    • Two "vision" tetras for each alliance randomly located in the space between the end zone and the midfield goals
    • Alliance robots in front of their driver stations
    • One tetra may be held by one robot on each alliance at the start of the game
    • 3 red human players and 3 blue human players [each with extra tetras] standing on pads arranged in diagonal lines off 2 corners of the field
    • Four tetra loading platforms along one side of the field

    Robots will attempt to place red and blue game tetras (coloured to match the two alliance colours) in or on one or more of the nine goals to both score points and claim "ownership" of goals with their coloured tetras.
    Ownership is claimed:

    • By the physically higher tetra colour on a goal or, if no tetras are on top
    • By the physically higher tetra colour in the base of the goal or, if no stacks are in the base
    • By the alliance with more tetras in the base

    Tetras in goals score 1 point and tetras on goals score 3 points. A row or diagonal of the same colour scores 10 points. Getting all of an alliance's robots back in their end zone at the conclusion of the match scores 10 points.

    Each 2-1/4 minute match will feature two (2) three-team alliances playing from opposite ends of the field. The robots from each alliance will be placed on starting positions in front of the driver stations (one at the tip of the center foal in an alliance's end zone and one to each side of the center goal and touching the driver station wall).

    The robots will have a 15-second autonomous period (no driver control) at the start of a match to knock down and score hanging tetras and/or to use their starting tetras and/or gather tetras from the loading platforms and/or to locate "vision" tetras(specially marked for identification by the vision system) to score points and claim goals. Vision tetras scored on any of the 3-midfield goals will yield 1 or 2 bonus tetras added to the corner goals in their end zone.

    After the Autonomous Period, the robots will be under driver control for the remaining 2 minutes of the match. Drivers from each alliance will be able to acquire additional tetra game pieces from four (4) locations, two (2) of which are attended by their human player (tetras will be placed on their robots) and two (2) of which are unattended (robots pick up tetras from loading platforms), and continue to score and claim goals. Before the end of the match, alliance robots will speed back to their end zones to top off their scores.

    This year's game will certainly challenge teams with the vision system, the "new" tetra shape, working as a three-team alliance, and strategizing on claiming goals.

    - Back to top

       -the sad walrus crew
    Old news...

    RAISING THE BAR: 2003-2004

    2004 for Sabres Robotics

    Great design guys!

    Visit the 2004 Website!

    The team at the regional

       -previous years
    More...

    STACK ATTACK: 2002-2003

    2003 was the year of the Sabres Srockbot!

    Chris controls the robot with his force powers. "This year we competed at the FIRST (For Inspiration and Recognition Of Science and Technology) Canadian Regional. It was held at the Hershey Centre on March 27-29, 2003.

    We had 8 matches, in which we won 6 of the 8 and we placed 26th out of the 51 teams. Then we were selected to play in the playoffs as a member of the 8th seed, all 8 seeds are 3 way alliances. We were knocked out of the playoffs in the quarter finals. Our alliance played two matches in the quarter finals both against the 1st seed. The First match we lost 154 to 31 and the second match we won 121 to 0. But when they totaled the scores up we fell two points short which in turn knocked us out of the playoffs and the 1st seeded alliance happened to go on to win the event."

    Working Great!

    Specs and Info on the Srockbot

    • The robot uses the Innovation First operator and robot interface
    • The robot was programmed using Basic Stamp Software, written by Larry Chen and it has an autonomous mode.
    • The robot runs on a 12 volt Exide lead battery
    • The operator and robot interface communicate by a 900 MHz radio
    • The operator interface uses three joysticks
    • The robot has four wheel drive powered by two 12 volt bosch drill motors
    • Our drive chains are tensioned using UHMW Idlers
    • The left joystick will control the left wheels and the right joystick controls the right wheels and the plunger device
    • The plunger device is deployed at the end of the match to have our suction cup on the device attach to the top of the ramp, the HDPE surface (plastic)
    • The plunger is run on a Globe motor with a worm gear
    • The purpose of the plunger is to create as much friction as possible between our robot and the top of the ramp to stop other robots from pushing us off the ramp at the end of the match. If we are successful, we will gain 25 points for this at the end of the match.
    • Our third joystick controls our forklift and the stack stabilizer which runs on the Fisher Price motors (the same motor that's used on the children's Power Wheels vehicles)
    • Both the plunger and the forklift have limit switches to stop the motors from moving these devices any further than needed, once the switch is activated the motor stops.
    • The forklift uses a ¼" aluminum plate Bosch sliders to slide in the tracks of the extruded aluminum. Shelf hangers and brackets are used as the forks for the lift. These forks simply lift the boxes to a maximum height of one box so we can build stacks if needed. Our plan is to steal the opponent's whole stack of four boxes and take it over to our side of the field.
    • The stack stabilizer also has a ¼ aluminum plate with Bosch sliders to slide in the tracks of the extruded aluminum. Our rotating light is attached to the top of this along with another suction cup which acts as a hand to stabilize the stack.
    • Friction reduction tape was used in order to reduce the amount of friction between our robot and the carpet on the field.

    2003 EDU Competition Overview

    The FIRST Robotics Kickoff event was held at the Ontario Science Centre in Toronto, Ontario, January 4th 2003. The Sabres Robotics team attended and competed in the EDU Robot challenge, finishing 20th out of 32 teams. A great time was had by all who participated in the kickoff event and we'd like to extend our thanks to Ian Mackenzie and Mark Breadner.

    When we first arrived, we took our robot and tested it. It worked fine so we had no worries going into our first match. It was match 5, Team 1232 (Stratford Central Secondary School ) versus Team 772 (Sandwich Secondary School). But we had a minor problem. Our robot would not move. The guys were baffled and the whole team was devastated. We expected it to work extremely well but it would not move. It turned out that the guys forgot to turn on the robot. So they ran and turned it on but we had another problem somehow when we were on our way to the playing field, our calibration controls on the joystick got hit and it made our robots calibration all wrong and we could not move. Ultimately, we were immobilized for the all of match 5, our first match of the day was over. Our calibration was off and we did not know it. We lost by a score of 40 to 0.

    After the match we took the robot back to our pit and tested it. It still would not work. That was when we noticed what had happened. So we fixed it knowing that we could make up for our mistake in the next three rounds. Unfortunately, things changed. Instead of getting 4 matches each team was to get 2 matches due to a lack of time. We had to catch up really fast, if we wanted to make the playoffs. View larger image

    Our next match was team 772 (Sandwich Secondary School) versus team 1112 (Timothy Eaton Business Technical Institute). This time we were ready. Both teams made a mad dash for the red balls. Sandwich made it to the balls first. In fear of breaking their gears, Sandwich backed off and Timothy Eaton was following Sandwich to its own goal. Then once Sandwich had a chance, they squeezed along side Timothy Eaton and the boards, quickly making a dash to the scoring bin and depositing many balls. Timothy Eaton ended up getting stuck it their scoring bin. Driver Chris Kelly, knowing that Sandwich had the advantage, turned around and deposited some white balls in Timothy Eaton's Goal figuring that in the end the winning team would get their score plus two times the losers score; this was not so. The officials counted out straight scores. So the final score of this match was Sandwich Secondary School with 350 points and Timothy Eaton with 240 points. Watch the video below to see all of the match between team 772 (Sandwich Secondary School) and team 1112 (Timothy Eaton Business Technical Institute).

    In the end the top 8 teams went to the playoffs in a battle for the title. Teams were seeded based on an average of their two match scores. Sandwich finished 20th with an average score of 175 points, based on two matches.


    Sandwich Sabres' Srockbot Website

    The Srockbot Team

    -Back to top

       -previous years
    Go to Srockbot's website...

    ZONE ZEAL: 2001-2002

    Team 772's first step into FIRST: The Sabrebot

    "As indicated by the name, the 2002 game was based entirely on particular ‘zones’ on the field and in which zones the robots, goals, and balls ended up. The field was 24’ x 48’ and divided widthwise into five approximately equal portions (10’). The field had three goals on it which started in the middle of the field, and twenty soccer balls lined up along each edge.

    The game was played with an alliance of two teams competing against another alliance of two teams. The pairing was random so that most teams played with different partners and opponents each match. Teams scored points by placing balls in the goals, moving the goals to the second-furthest zone from them, and having robots in the zone closest to them."

    Packed up and good to go!

    Specs and Info on the Sabrebot

    • The robot uses the Innovation First operator and robot interface
    • The robot was programmed using Basic Stamp software, written by Kyle Kryway and Sang-woo Chung
    • The robot runs on a 12 volt Exide motorcycle battery
    • The operator and robot interface communicate by a 900 Mhz radio signal
    Everything looks good!
  • The operator interface has 4 Joysticks
  • 2 joysticks for the drive train left and right wheels (drives like a bobcat)
  • 1 joystick for the ball grabber
  • 1 joystick for the ball thrower and Arm/claw
  • The Ball Grabber runs on 2 small globe motors and can go forward and reverse to push balls in and out of the ball thrower tower
  • The Ball Thrower runs on a chiaphua van door motor (Atwood Mobile), it works like elevator, it is also made of iron which was welded together
  • The drive train is 2 wheel drive and is capable of forward and reverse, it runs on two bosch drill motors that drive the two pneumatic wheels
  • The Arm uses a window motor to extend the arm in and out
  • The Claw uses a car seat motor to open and close
  • The robot is built on an extruded aluminum frame
  • The Sabrebot Team

    -Back to top

       -previous years
    Questions? Comments? Suggestions?
    E-mail The Webmaster
    FIRST
    GM CanadaCapaldiCenterlineSandwich Sabres
    (C)Copyright 2004-2007 Club Sandwich Robotics