2018 World Champions!

A Brief Summary

As part of an eventful week, we attended the 2018 FIRST World Championship in Houston, Texas from April 18th to April 21st. Assigned to the Hopper Division, we won the Division Championship Award and the the Autonomous Award sponsored by Ford, for our 4 cube scale autonomous program and scale detection software. After becoming the Hopper Division Champions, we executed a well-planned strategy alongside FRC Team 148 Robowranglers, FRC Team 2976 Spartabots, and FRC Team 3075 Ha-Dream Team, allowing us to win our 4th world championship and finish with an undefeated season!

Team 254 poses for a picture after winning at the 2018 FIRST Championship in Minute Maid Park

Robot Performance

Qualification Matches (Hopper Division)

Throughout our qualification matches, we wanted to make sure that we secured 4 ranking points during every match, while still gaining control of our scale for as long as possible. In order to do this, we ran our scale autonomous program, which placed 3-4 cubes on our alliance’s scale or, when we were not confident with our alliance partners’ ability to place cubes on the switch, we executed our autonomous program which placed cubes on the switch and scale.

Alliance Selection

Going into the elimination period in the Hopper Division, we chose to form an alliance with FRC Team 148 Robowranglers, FRC Team 2976 Spartabots, and FRC Team 3075 Ha-Dream Team.

Team 254 representative, Weston White, poses with our chosen alliance partners

Elimination Matches (Hopper Division)

During the elimination matches in the Hopper Division, we maintained our undefeated record for the entire tournament. From a strategic perspective, we aimed to always have possession of the scale and our own switch while also placing cubes on our opponent’s switch. This strategy allowed us to gain a significant lead during each match and stopped the opposing alliance from being able to score from their own switch. We would also like to thank Team 3075 Ha-Dream Team for helping our alliance during Finals Match 2 in the Hopper Division, while Team 2976’s robot was undergoing some repairs. Through the efforts of our alliance partners, we were able to win the Hopper Division. We also won the Autonomous Award sponsored by Ford, for our unique 4 cube scale autonomous program and scale detection software!

Lockdown hangs with alliance partner, Team 2976, at the end of a match

On the Einstein Field

We generally maintained a similar strategy during the Einstein matches as in the Hopper Division elimination round, by placing cubes on both switches and keeping possession of the scale. Team 2976 Spartabots played awesome defense on the portals to slow down the opposing alliance’s cube flow after they used all the cubes from their switch fence. Team 148 Robowranglers attacked the opposing alliance’s switch to force them to cover their switch before attacking our switch or the scale. Our drive team chose not to prioritize powerups, by placing only 3-4 cubes in our exchange for the levitate or boost powerup. With this strategy, we placed first during the round robin matches, allowing us to move on to Finals, with the Carver Division winners. We would like to shout out FRC Team 2910 Jack In The Bot, FRC Team 4911 Cyberknights, FRC Team 4499 The Highlanders, and FRC Team 5006 Apophis, the Carver Division winners, for executing a great strategy while playing against us on the Einstein Field.

Lockdown works to place a cube on the opposing alliance’s switch

A Special Thanks

At the 2018 FIRST World Championship in Houston, we would not have been able to be so successful without the amazing teams that we were able to work with during our matches. Also a special shout out to our pit crew and drive team for properly maintaining our robot during the tournament. We would also like to highlight the efforts of our alliance readiness crew to keep our alliance partners ready throughout the tournament. Team 254 would also like to thank all the volunteers and judges that made this tournament an exciting experience, and all of our mentors, teachers, and parents who supported us and helped us succeed in this tournament.

Members of the Team 254 Pit Crew repair Lockdown before an upcoming match

Members of the Team 254, 148, 2976, and 3075 drive team strategize before an upcoming match

Our drive team poses for a picture on the Einstein Field

Members of the Team 254 Alliance Readiness Crew assist Team 6014

2018 Silicon Valley Regional Champions!

A Brief Summary

As part of an eventful weekend, we attended the the 20th Silicon Valley Regional, in San Jose, CA. We had a great time at our second tournament of the FIRST Power Up Season with our robot, Lockdown. We won the Innovation In Control Award sponsored by Rockwell Automation for our autonomous code. Congratulations to one of our mentors, Nick Hammes, for winning the Volunteer of the Year award, for his hard work emceeing and in planning this wonderful event! Alongside FRC Team 973 The Greybots and FRC Team 2367 Lancer Robotics, we were able to win the tournament, earning our 50th Blue Banner!

Team 254 poses for a picture with Lockdown after winning at the 2018 Silicon Valley Regional

Robot Performance

Qualification Matches

Throughout our qualification matches, we executed a variety of autonomous programs to ensure we were prepared for various situations. This allowed us to either place 3 cubes in the switch or place 3 cubes on the scale. When on an alliance with robots that were good at placing cubes on the scale, we had to make sure we maintained ownership of the scale before placing cubes on ours’ or our opponent’s switch. We always tried to position ourselves on the scale platform to have enough time for hanging. During the qualification match period, we gained 4 ranking points in each match.

Team 254 places a cube on the scale during the autonomous period

Alliance Selection

Going into the elimination period, we chose to form an alliance with FRC Team 973 The Greybots, FRC Team 2367 Lancer Robotics.

Team 254 representative, Weston White, stands with Team 973 and Team 2367 as they agree to join our alliance

Elimination Matches

By choosing Team 973, a great scale robot, and Team 2367, a great switch and exchange robot, we were able to follow a more flexible strategy. During the elimination matches, Team 973 worked with us to lock down the scale, while Team 2367 focused on keeping ownership of our switch and delivering cubes to our exchange station. To create a head start on scoring cubes onto the scale, we used our 3 cube scale autonomous program. If our opponents were good scoring on the scale, we joined 973 in maintaining ownership of the scale. When our autonomous program was successful, we worked on maintaining ownership of our opponent’s switch, using cubes from our portal. Team 2367 executed flawless and well-timed defense against the opposing alliance. With an organized strategy and great alliance partners, we remained undefeated for the season, allowing us to become the first-place alliance at the tournament and win our 50th blue banner!

Team 254 and alliance partners Team 973 and Team 2367 stand together during Semifinals Match 1

Helping Other Teams

The Alliance Readiness Crew worked hard throughout the tournament to assist Team 6688 West Valley Middle College Robotics and Team 7317 Crusader Crew. Our crew helped improve the design of Team 6688’s exhaust system, used for delivering cubes to the switch, safely wire their control system, fix their pneumatics so that there were no leaks, and write an auto that could put cubes into the correct side switch. When Team 7317 needed help, our crew worked to create a new and improved intake system to collect and deliver cubes to the exchange. Through this experience, students were able to make friends and get more hands on with designing an actual robot.

Our alliance readiness crew assists Team 7317 in mounting hardstops for a newly designed intake

A Special Thanks

At the Silicon Valley Regional, we would not have been able to be so successful without the amazing teams that we were able to work with during our qualification and elimination matches. Also a special thanks for our pit crew and drive team for properly maintaining our robot during the tournament. A big thank you to the chairman’s presentation team for handling our team’s Chairman’s Presentation in front of a panel of FIRST Judges. Team 254 would also like to thank all the volunteers and judges that made this tournament an exciting experience, and all of our mentors, teachers, and parents who helped us succeed in this regional.

Members of the Team 254 Drive Team repair Lockdown with a mentor before an upcoming match

Our drive team discusses a possible strategy before a tense eliminations match

Excited Team 254 members receive the team’s 50th blue banner

2018 Arizona North Regional Champions!

A Brief Summary

As part of an eventful weekend, we attended the Arizona North Regional, for the very first time, in Flagstaff, AZ. We had a great time starting off the FIRST Power Up Season with our robot, Lockdown. Alongside FRC Team 842 Falcon Robotics and FRC Team 2403 Plasma Robotics, we were able to win the tournament!

Team 254 poses for a picture with Lockdown after winning at the 2018 Arizona North Regional

Robot Performance

Qualification Matches

Throughout our qualification matches, we used an experimental strategy by testing out which of our autonomous programs worked best during a match. From this experimentation, we concluded that it would be best to use our autonomous program, which scored 2-3 cubes on the scale, to establish an early lead in a match. This autonomous program helped us gain ownership of the scale, but we had to focus more on maintaining ownership of the switches rather than the scale. Whenever we had alliance partners who could not secure the switch consistently, we ran our autonomous program for the switch to help our alliance partners before the tele-op period. During every match, we hung with our partners and used the levitate power up for an extra ranking point. By the end of the qualification match period, we were seeded first and had a undefeated record.

Team 254 and alliance partner Team 1011 work together to hang during Qualification Match 86

Alliance Selection

Going into the elimination period, we chose to form an alliance with FRC Team 842 Falcon Robotics, FRC Team 2403 Plasma Robotics.

Team 254 representative, Brandon Chuang, greets Team 842 as they agree to join our alliance

Elimination Matches

During the elimination matches, we maintained our undefeated record for the entire tournament. Our autonomous program and Team 842’s robot, worked to score on the scale during each match. This allowed us to score on switches, while Team 842 covered the scale during the tele-op period. We also focused on stopping our opponents from gaining ownership of their own switch. If we had spare time during a match, we passed cubes through the exchange. Team 2403’s robot worked to gain ownership of our own switch and we also helped with scoring cubes in our switch. During finals, Team 2403 focused on switch, exchange, and defense against opponents who tried to take ownership of our switch. With an organized strategy and great alliance partners, we scored an all-time high of 594 points in Finals Match 2, allowing us to become the first-place alliance at the tournament!

Helping Other Teams

The Alliance Readiness Crew worked hard throughout the tournament to assist Team 6585 Hózhóogo Naasháa Doo and Team 6656 Ryu Botics. When Team 6656 needed an intake, our crew searched for the necessary parts and mounted a simple 2-wheel intake onto their robot. In addition, we helped them write an autonomous mode that crossed the auto line consistently. When Team 6585 needed a robot, our crew worked for 3 days to build and wire a drivebase, 2-wheel intake, and a polycarbonate box for collecting cubes from the portal. Through this experience, students were able to make friends and get more hands on with designing an actual robot.

Our alliance readiness crew assists Team 6585 in mounting a newly designed intake

A Special Thanks

At the Arizona North Regional, we would not have been able to be so successful without the amazing teams that we were able to work with during our qualification and elimination matches. Also a special thanks for our pit crew and drive team for properly maintaining our robot during the tournament. A big thank you to the chairman’s presentation team for handling our team’s Chairman’s Presentation in front of a panel of FIRST Judges. Team 254 would also like to thank all the volunteers and judges that made this tournament an exciting experience, and all of our mentors, teachers, and parents who helped us succeed in this regional.

Members of the Team 254 Pit Crew repair Lockdown before an upcoming match

Our drive team works together during a tense eliminations match

Spirited Team 254 members cheer excitedly for their alliance

Lockdown Reveal

Team 254 presents our 2018 entry into the FIRST Robotics Competition: Lockdown. Lockdown will be competing at the Arizona North Regional, followed by the Silicon Valley Regional and the FIRST Championship in Houston. More information on the robot.

Build Blog Days 28 and 29 (2/23/18 & 2/24/18)


  • On Friday, 2/23, we handed off practice bot to the programmers to begin working on autonomous code. The programmers rewrote a large portion of our code to greatly simplify all our state machines and change the way operator controls work. They separated operator controls into wrist angle presets and height presets and experimented using an xbox controller rather than the button board. They also began working on some autonomous actions for intaking, setting superstructure position, and shooting/placing cubes.

Driver Tryouts

  • We had our first round of driver tryouts, where all 254 members interested in joining drive team participated in a written test. The purpose of the written test was to test one’s knowledge of the Game Rules and Drive Team Positions during a match. A few lucky students were chosen to move on to the second level of drive tryouts where they were able to drive Misfire, our robot from last year. Students were asked to pick up gears from the field and place them on a makeshift peg, using the controls on our driver station. After these two rounds of tryouts, we narrowed our choices for students on the drive team, and will finalize our choices over the course of this week.

Driver Practice

  • To facilitate driver practice this weekend, we rigged up the wooden lever arm of the scale we got from the SJSU kickoff onto the aluminum scale we are currently constructing. Our driveteam also practiced with Team 973 and Team 5499 throughout the day.

Working on Programming Bot

  • On Saturday, 2/24, we worked on getting programming bot to the same state as competition bot. This year, driving is an especially critical component of the game. Because our robot accelerates extremely quickly with the 6 MiniCIM drivetrain and has a high CG with the elevator, the driver needs to have confident control over the robot's motion to ensure it doesn't tip over and the operator needs to have confident control over the robot's operations to ensure our mechanisms are stowed unless needed and do not accidentally hit parts of the field.

Build Blog Days 18-27 (2/9/18 to 2/20/18)

It's assembly time!

Part 1

  • On Friday, 2/9, we assembled together the elevator on comp bot and tested out how wheel the intermediate stage and carriage slid with the bearing blocks. As we were sliding the stages, we noticed that the carriage was ripping off the powder-coating on the intermediate stage, so we decided to manufacture new inner stage uprights to be anodized for comp bot. We also assembled all 3 carriages and sanded down the welds. On Saturday, 2/10, we started putting everything together on all 3 robots. We installed all the bearing blocks and forklift brackets, and began wiring up the comp bot with the IGUS chain. We also decided to hook up a magnetic limit switch to the top of the horseshoe to detect the distance between it and the carriage. That switch will be connected to the encoder on the elevator gearbox. We also assembled an intake without the pivot arms and mounted it to programming bot to test out how well it works. On Sunday, 2/11, we worked on manufacturing more parts to send out for anodizing on Monday, 2/12, and we cabled up the elevator on practice bot and tested it out. We noticed that the elevator moves slower than we thought which may require a change in gearing, and we also noticed that the cable runs are too close together which may prove problematic for spitting the cube out the back.

  • On Wednesday, 2/14, we began assembling the programming bot and competition elevator gearboxes. After testing the elevator on Sunday night, we realized that it moved much slower than expected. To fix this, we swapped out the last stage gear reduction from an 18:50 to a 24:44 which theoretically allows us to climb 78.5" within 0.76 sec. We got back the intake pivot weldments from powder-coating and assembled them on practice bot.

  • On Thursday, 2/15, we continued work on assembling the intake. We wired up the CAN coming up from the PDP into the talon, then had the CAN daisy chain from the talon to the canifier, and then had the CAN terminate after the canifier with a 120 ohm resistor. The canifier will be used to breakout various DIO sensors we plan on placing on the intake such as magnetic limit switch sensors for soft stops for the intake pivot and beam break sensors for cube detection. We wired up the motors and pneumatics on the intake, and tested it out.

    • Part 2

      • After 4 intense days of early mornings and late nights, we bagged and tagged our completion robot last night! Thank you to all the students, mentors, and parents who made this build season possible!

      • Saturday, 2/17: We handed off the the practice bot to the programmers to begin tuning the wrist pivot and the elevator.

      • We wired up the carriage on competition bot by drilling in holes in the box tubing to channel the wires. We mounted the intake on the carriage and placed the magnetic limit switch sensor on the carriage pivot gearbox

      • Sunday, 2/18: The programming team continued tuning practice bot. We continued assembling and wiring competition bot.

      • Monday, 2/19: The programming team took competition bot to tune the mechanisms while the assembly team took practice bot to mount the forklift and hanger. We tested out both the forklift and hanger and saw that the sneaky hang with a partner was able to support two robots. While doing a solo sneaky hang, the robot did swing in which we expected to happen. We mounted a rollercoaster arm on practice bot hoping to counteract that swinging, but rather it only caused the robot to now pivot around where the rollercoaster arm contacted the scale. After all this testing, we decided to remove the partner hang and only mount the sneaky hang on competition bot.

      • Tuesday, 2/20: Stop build day! We finished up all the wiring and assembly on competition bot and took pictures of it. In the last hour, the programmers took the robot to test it, and we noticed a few issues arising with the intake, Omni followers, and sensors which will need to be corrected at competition. We bagged the robot at 115.9 lbs as well as a tote full of spare parts.

      • Our Final Robot

Build Blog Days 16 and 17 (2/2/18 & 2/3/18)

Task: Design Elevator Cartoon CAD

  • We decided to offset the A-Frame from the frame rail to allow more space for the intake to open and close in between. To do so, this also required moving the frame rail closer to the elevator such that it would not interfere with the omni followers. We finalized the outer stage and A-Frame of the elevator, manufactured all the parts, and sent them out to be welded. We decided to have the igus chain ride on a polycarb guide on the same plane as the outer face of the upright. The igus chain will attach to the top of the polycarb guide, will curl around the side tube of the carriage weldment, and will bolt to the inside of the carriage. We also moved the pulleys in a little on the bottom side of the horseshoe to make space for our pit crew members to easily put in the thumbscrew bolting the bumpers to the back of the frame rail.

Task: Design Forklift CAD

  • We adjusted the forklift pivot and piston to work around the A-Frame by using a larger bore piston with a smaller stroke. We had initially planned on using a 3/4″ bore piston with a long lever arm, but because we decided to move it within a protected area and closer to the elevator, the lever arm decreased and thus required a larger bore piston to hold the forklift upright. We also finalized the tensile member which will be a steel wire bolting from the elevator to a-frame gusset to a standoff on the forklift and added a crossmember between the two forks.

Rollercoaster Wheels
Task: Complete Rollercoaster Wheels CAD Design

  • We completed the design of the rollercoaster wheels. We decided to use metal lanyards as the deploying hardstop. In addition, we chose to use a ball bearing with a 3D printed cover to increase the size of the wheel without increasing the thickness.

Task: Wire the Practice, Programming, and Competition Robots

  • Over the past two builds, we completed wiring the practice, programming, and comp bots. We also installed all necessary gearboxes and chains on each drivebase. So far, the practice and programming robots are set with pneumatics. At our next build, we plan to finish plumbing the pneumatics on the comp bot.

Stanford Outreach Event

Shockwave Shows Off Some Mad Skills!

A Brief Summary

WHAT: Shockwave launched t-shirts into a crowd of excited Stanford Basketball Fans
WHEN: Saturday, February 3rd, 2018
WHERE: Stanford University in Stanford, CA

Team 254 Members Griffin Soule, Shruthik Musukula, Mubashir Hussain, and Jack Gnibus work together to prepare Shockwave before the game

As part of an eventful weekend, we participated in a successful outreach event at Stanford, CA. Due to the efforts of students on our outreach subteam, Team 254 students were excited to have the opportunity to present Shockwave at the Stanford Basketball Game, where Stanford played against the Oregon Ducks from the University of Oregon. During a timeout in the first half of the game, Team 254 students Yusuf Halabi, Shruthik Musukula, Jack Gnibus, Griffin Soule, and Mubashir Hussain worked together to operate Shockwave and launch several Stanford t-shirts into a crowd of approximately 8,000 people. We are extremely grateful to have such an opportunity and would love to support Stanford University in the future!

Shockwave launches t-shirts towards excited audience members

Build Blog Days 14 and 15 (1/29/18 & 1/31/18)

Task: Design Elevator CAD

  • We changed the placement of the A-Frame by pushing it further towards the front of the robot and higher up the outer stage elevator upright such that the bumper latch could freely swing without contacting it, and we made the corresponding changes to the gusset joining the A-Frame to the outer stage elevator upright. We also modified the horseshoe plate to accommodate the omni follower wheels on the back of the robot by having the cutout fit around a space of the follower wheels. To ensure that our forklift would not contact our pulleys and cables when stowed within the frame perimeter, we looked into pushing the pulleys closer to the sides of the elevator, but realized that they would then interfere with the carriage as it traveled up. Instead, we decided to adjust the forklift pivot such that it could stow vertically and not have the carbon fiber rods leaning into the elevator assembly. Moving forward, we will also need to design in a part to protect the pulleys in case the forklift sways while we accelerate across the field during a match. We also modelled in a new piston pivot off the lower part of the A-Frame to actuate the stowing/deploying of the forklifts. We decided to move this piston to be above the frame rail and below the top of the bumpers such that it is in a protected area. If it was kept in its previous configuration, a robot could have easily come in and hit it, which would have rendered us incapable of actuating the forklifts for that match.

Task: Wire the Practice, Programming, and Competition Robots

  • We finished wiring the PCM on the Practice and Programming Robots. We also finished wiring all the Talons for each robot. Lastly, we worked on gathering and assembling the pneumatic systems for each robot.

Task: RPLIDAR Driver

  • Today, we finished the odometry calculations necessary to track the robot’s position using the follower wheels. The main difference from last year’s code is the inclusion of the back follower wheel, which can be used to detect sideways slip when making turns. We are pretty much ready to test the follower wheels once they are ready, but we still need to figure out where the encoders will plug in so we can finish up the code.

Build Blog Days 12 and 13 (1/26/18 & 1/27/18)


Task: Design Elevator Cartoon CAD

  • We finalized the elevator gearbox and pulley placement. To ensure the gearbox does not get in the way of the carriage, we decided to stow it below the elevator and belt out to reductions and the spool. We will have two spools, one on each side. Each spool will be divided into two sections by a flange: one section for the pull up cable and one section for the pull down cable. To avoid the carriage sweeping through in front of the elevator, we decided to have our cable runs go on the back of the elevator then come below the horseshoe and back onto the spool. We extended the horseshoe onto the frame perimeter to give us space to bolt the pulley assemblies and also to bolt into the frame rail to provide overall structure to the elevator assembly.

Rollercoaster Wheels

Task: Finish Rollercoaster Wheels Design in CAD

  • We finalized the geometry of the rollercoaster wheels design. We determined that we should have the piston mount to a plate mounted off the upright. This eliminates the original need for two degrees of freedom with two rod ends. Our plan is to start detailing the parts, finalizing that everything packages, and doing stress analysis.



Task: Wire the Practice, Programming, and Competition Robots

  • For wiring, we worked on wiring the talons and distributed power to the VRM, PCMs, and RoboRio. We completed wiring the programming bot and are close to finishing wiring the practice bot.



Task: RPLIDAR Driver

  • We worked some more on the lidar driver.  We discovered a few problems with the UDP method where some data would be lost when the information was sent to the roborio resulting in a few of the packets missing timestamps.  To solve this problem we ended up writing to an input stream and using a buffered reader to transfer the data instead.  The new method also reduces CPU usage and decreases latency, so it is pretty much better all around.

Build Blog Day 11 (1/24/18)


Task: Design Elevator Cartoon CAD

  • The previous issue with Option B was the issue of the spool not being low enough if we directly mounted it on the shifter shaft. To address this issue, we decided to add a 1:1 reduction to lower the spool down. We also talked about the horseshoe. The horseshoe allows us to drop the intermediate stage as low as possible such that we can score our cube safely into the exchange.

Option A:

Option B:

We also designed new bearing blocks to allow us to save an inch of space between the vertical and horizontal tube of the intermediate stage.



Task: Finish Forklift CAD

  • At Wednesday's build, we worked on further detailing the forklift arm. More specifically, we added a point to the back of the arm where surgical tubing could hook onto it and in-effect spring load it downward when we are ready to climb. We also beefed up the main arm and added a pivot point just above the downward 90 degree angle of the arm, which will later serve as an attachment point for a tensile member that will help support the whole arm when we are lifting another robot. Finally, we added a small notch in the triangle brace to allow room for the elevator superstructure. Moving forward, the plan is figure out how we will release the arm from a stowed position, and run a simulation to make sure the arm can support another whole robot.





Task: Decide on a final intake prototype

  • Yesterday, we decided to switch up the intake design and started designing an intake that uses several 2" compliant Andymark wheels as opposed to the 4" we had been using so far. We began designing it in cad but have not laser cut it yet.



Task: RPLIDAR Driver

  • We got the RPLIDAR to output data to Network Tables, and can now access it from the node.js server. However, there are still some bugs to be fixed – for example, the data stops sending after a certain amount, and we will need to look into the problem more to find out why. Also, we will need to parse and send the data from the node.js server to the visualizer to complete the transfer of data from RPLIDAR to visualizer. Meanwhile, we also researched more line detection methods and are working on finding the best one for our purposes.

Build Blog Day 10 (1/22/18)


Task: Finalize Drivebase CAD and Prepare For Manufacturing

  • Over the weekend, we finished CADing and reviewing the drivebase. We sent the baseplate out to be laser cut. At our next build, we need to manufacture and assemble the drivebases so they can be welded on Thursday. On Thursday, we will need to deburr the drivebases so that on Friday they can be anodized. For a image of the electronics layout, you can look below.


Task: Finish Designing Forklift CAD

  • On Monday, we started the build by designing the forklift arm that we would be using to carry other robots at the end of the match. This design certainly needs some refinement, but the image below can give you a rough idea of what it looks like.

  • Some of the other challenges tackled during build were stowing and packaging in a space that is already really crowded with other subsystems. The roller coaster wheels that are still being designed need to fit into the same general space, so we spent a decent amount of time working with him to make sure that our designs didn't collide with one another. On Wednesday's build, we will look into this a bit more and get it reviewed before we start detailing each sub assembly.



Task: Design Elevator Cartoon CAD

  • Today, we investigated different gearbox options to power the elevator. Both options contain 2 speed gearboxes (high gear for fast cube cycling and low gear for hanging). One option is to mount the gearbox is to have it attach off the side of the upright such that the motors do not interfere with the intake carriage. Another option is to mount it between the elevator crossbar and the baseplate so that we can bring the spool as low as possible. For the cable runs between stages, we are working on deciding whether we want a single pullup cable that is connected to the center of the carriage and is then redirected to the side or having two pull up cables, one on each side of the carriage, and does not require any redirect pulleys.

Option 1 Pulley Path (Redirects and mount off the side of tube)

Pulley Path Option B (No redirects, just pulls on each side of carriage)

Rollercoaster Wheels

Task: Complete designing rollercoaster wheels and find methods for mounting/deployment

  • Since the drivebase CAD has been frozen, we decided to mount the roller coaster wheels to the gusset at the junction of the angled A-Frame support and Elevator Uprights. We plan to finalize this idea at the beginning of our next build.


Task: Update All Talons and Roborios for Driver Stations

  • We worked on updating our roborios and talons to the latest 2018 firmware. We also updated all of our driver station laptops with the FRC Update Suite. Now that all our electronics are running on 2018 software, it should be a lot easier to program prototypes and test new code as we no longer have to keep switching between 2017 and 2018 code.

Task: RPLidar Visualizer

  • We worked on a field mapping program using the lidar sensor and Google Cartographer. The goal of this program is to push the lidar around the field on a cart and use the scans we get as we move around in order to build a map of the field. We want to use this data to scan a field before every tournament and adjust our autonomous paths accordingly so they are best optimized for small differences. This would be easier and more accurate then the method we used last year, which was to measure the field manually using a tape measure.

We also worked on an algorithm to determine our starting position in autonomous using the lidar and our field mapping data. We detected clusters of points in the lidar data based on their distance from each other then drew best fit lines through the clusters.

Build Blog Days 8-9 (1/19/2018 – 1/20/2018)


Task: Design Elevator Cartoon CAD

  • We worked on finalizing the placement of the elevator. The front face of the elevator will be 9" from the outside of the back bumper. We wanted to move the elevator back because we wanted to ensure as confident a handoff between our intake which will end before the elevator and the exchange, but we also needed to leave space for the roller coaster wheels and the forklift. We decided to place a 2×2 crossbar across with 90 degree angle plugs welded in the ends to dodge the chain and mount to the elevator plugs such that the elevator and the crossbar as a whole can come off as one unit. We finalized the gear reductions for the two speeds of the elevator and packaged the gearbox between the crossbar and the drive gearboxes. The gearbox will mount to the 90 degree plugs.

Top Level Assembly:

Preliminary Elevator Gearbox:

High Gear For The Elevator:

Low Gear For The Elevator:


Task: Finalize Drivebase CAD

  • At the last build, we worked on adding mounts for other parts of the robot to the drivebase and also placing electronics. There were a few requirements we kept in mind when placing the electronics including a horizontal battery (instead of vertical placement) to allow for a tunnel, a possible kicker roller in the front, and the gearboxes in the middle of the robot. Keeping these limitations in mind, we placed the battery in the front of the robot (to balance the center of gravity) and the PDP in the middle of the robot with stacked staggered Talons to each side. See the image for placement of everything else.


Task: Complete Forklift CAD

  • Yesterday, we worked on the Forklift design for the 2018 FRC Robot. On Friday night, we started by doing some physics calculations to determine how much the forklift would bend once a robot was on it, and determined that a 100lb force at the end of a single 36in rod we plan on using would yield a 6in deflection. This number seemed like a lot, however when we moved the 100lb force to the center of a rod (18in), the deflection was only about 3/4in, which is very reasonable. The next step was to do some sketching in CAD to figure out where the mounting place for the forklift pivot point would be. After trying to make the forklift arms fit in between the bumper cutout (which ultimately didn't leave enough space for a cube to pass through), and trying to make the arms to go over the bumper (which collided with the elevator superstructure when stowed), we finally settled on having the pivot point for the forklift mount on the elevator superstructure itself. With this design, the forklift could stow vertically, and then come down neatly at the end of the match and react against the robot's frame rail when lifting a robot. Now that we have decided to go forward with this design, the forklift design team will need to work closely with the roller-coaster wheel team to make sure that the two subsystems don't collide with one another, as they are both located in very similar parts of the robot.

Rollercoaster Wheels

Task: Complete designing rollercoaster wheels and find methods for mounting/deployment

  • The intention of the rollercoaster wheels is to allow the robot to climb up straight in the sneaky hang, while preventing our partner from falling off the forklift in the partner hang. Our original plan was to have a single plate mounted to the elevator uprights, as well as a actuation deploying the wheels for both the partner hang and the sneaky hang. However, we were unable to package the plate in such a way to stow inside the frame perimeter. Thus, we decided on two separate plates and actuations for each of the rollercoaster wheels. In addition, since mounting the rollercoaster wheels on the elevator uprights would interfere with the forklift deployment, we are pursuing the deployment of the rollercoaster wheels from the bumper frame rail.


Task: RPLidar Driver with JNI

  • We made some real progress on the RPLidar Driver using JNI. We finished most of the C++ code for the JNI, which again allows us to call functions written in other languages, in Java. To do this, we adapted some of the code from example RPLidar programs for JNI. Once we were done with the C++ code, we built the code into a Shared Object. Our next steps are to finish the Java code, which will load the Shared Object, parse the data returned, and send the data over NetworkTables to the RPLidar Visualizer. Finally, once all of the code is written, we will do some testing and debugging.

Task: RPLidar Visualizer

  • We fixed an error where the RPLidar Visualizer Node.js server was unable to connect to the robot using NetworkTables, which is an implementation of a distributed "dictionary," meaning that named values are created either on the robot, driver station, or potentially an attached coprocessor, and the values are automatically distributed to all the other participants. Also, we updated some formatting on the visualizer to make the timestamp easier to read.

Task: Transforming RPLidar Vectors to XY Coordinates

  • Since the RPLidar scanner only returns an angle (in degrees) and a distance (in mm), we need to be able to transform that to XY coordinates for plotting on the RPLidar Visualizer. To do this, we had to account for the robot's own position and angle, and use some basic trigonometry to transform the vectors into coordinates.

Build Blog Day 7 (1/17/2018)


Task: Cartoon CAD

  • Prior to today, we had the idea of having an intake feed into a tunnel. The tunnel would serve as a conveyor system to transport the cube back and forth across the robot. However, the issues with the tunnel are that a) it will be very bulky and would serve as a huge cantilevered load on the elevator and b) the vertical translation of a cube from the ground to the tunnel (~4.75") would be hard. To solve these issues, we had a new idea where we could have an intake that would pivot 180 degrees to pick up a cube in the front of the robot and then fold back to spit it out on the back side. Since the intake is now taking in and spitting out the cube, there is no need for a vertical translation of the cube and no need for a series of rollers to convey the cube back and forth across the tunnel we need to continue investigating the geometry of this new intake design and make a decision if we want to pursue this design or not by this weekend.


Task: Design a way of attaching the bumper to the drive frame rails

  • We have been working on using latch pieces to latch the bumpers onto the bumper rails. During our next build, we will decide if this is the best way to go and finalize the bumper mounts on the drive frame rails.


Task: Complete designing the new intake prototype

  • With our new intake prototype design, the intake is mounted on an arm and grips the cube. The arm that the intake is attached to has the ability to rotate back 180 degrees. We plan to have the arm and the intake system itself mounted onto the elevator. When the elevator moves up, the intake arm rotate back and ejects the cube onto the scale or switch. A few issues we are facing and trying to solve, are that we don’t want the intake to be too heavy and we want the intake to have a better grip on the cube.

Build Blog Day 6 (1/15/18)

Task: Design drivebase gearbox

  • We found out today that the gearbox will have to be redesigned. Our original plan consisted of a triangle of mini-CIMs but this design was too tall and would not allow the tunnel to lay flat and exhaust cubes to the exchange. Our new design still uses 3 mini-CIMs but they are arranged flat so that they can be lower than the bumper rails.

Task: Design tunnel with timing belts to friction drive the cube across on all four sides

  • For the tunnel, we worked on prototyping a mechanism that used timing belts to move the cube.. We made a four bar that allowed us to test the cube in both orientations (11 and 13 in width). Initially, we had trouble with the prototype as there was too much friction between the wood the cube rested on and not enough tension in the belt. We redesigned the prototype and made changes including making the four bar structure more secure, tensioning the timing belt, and installing plastic rails for the cube to slide on. These changes greatly increased the effectiveness of the prototype, and pushed the cube quickly through the tunnel. We now are designing a variation of this but using rollers instead of timing belts, to see which one works better.

Task: RPLIDAR Driver

  • After ensuring that the RPLIDAR works, we discussed several options, and have started to implement two of them. For our first method, we were able to use existing examples of code, from the RPLIDAR’s Software Development Kit (SDK), and write our own program that gets data and a timestamp for that data from the RPLIDAR, and send that data to the robot. Because the SDK is for C++, we would probably have to run this program on a co-processor on the roboRIO that communicates with the rest of the robot code over User Datagram Protocol (UDP). Our other option, which is more preferable, is to use the Java Native Interface (JNI). JNI allows the Java Virtual Machine, which runs Java code, to call functions written in other languages, which will allow us to use the SDK, even though it is written in C++. We will continue work on both of these methods, and choose whichever will work better for the robot.

Task: RPLIDAR Visualizer

  • We scaled down points to the size of the field, but this messed with the zooming and panning functions so we’ll have to fix this. Here is a sample image of the current functionality of this interface:

Build Blog Day 5 (1/13/18)


Task: Model drivebase moving up platform ramp with 1/8" center drop and minimal space from outside bumper supports

  • To ensure we have a stable robot when our CG raises with our elevator, we decided to extend our wheelbase as far out as possible. By doing so though, we are more susceptible to high centering on the platform ramp. To ensure we do not do so, we revisited the sketch we used to model the drivebase motion and adjusted the parameters to space the wheels as far out as possible and with a center drop. We also decided to constrain the lowest height of the bearing holes by having the center 16 tooth sprocket with chain OD be tangent to the baseplate. We will account for the chain run by having a cutout in our base plate.

Task: Finalize drive gearbox

  • We finalized the design of the drive gearbox and placed an order for the necessary hardware required (gears, pneumatics, screws, etc.) We hope to begin assembly of the drive gearbox this week.

Task: Sketch electronic placement

  • Task: Sketch electronic placement
    We sketched the electronics placement on the baseplate. We plan on having the battery lay flat as in 2017 rather than standing up as in our 2016 robot. This way, we can lower the carriage/tunnel as far down as possible which means the cube does not need to move vertically as much from the ground to the handling mechanism.


Task: Prototype Intake

  • We assembled an intake with adjustable wheel placement and pivotable arms/outer wheels, and mounted it to the 2017 drivebase. We controlled each wheel with its own independent 775pro geared with a 5:1 reduction —- by doing so, we were able to test asymmetry and easily adjust certain speeds of certain wheels. This intake prototype worked well in quickly drawing in the cube and orienting it from a diamond to a square shape. We also saw that by increasing the pressure in the pistons controlling the outer arm pivot, the intake itself became a lot stiffer and was able to better control the cube. We quickly implemented a bottom kicker roller and saw that it worked well because the intake itself was able to provide enough force to push the cube up and above the kicker roller. Moving forward, we will design a prototype that combines this intake with a kicker roller and mount it on a test drivebase.

Task: Prototype ramp intake

  • We design and tested if a kicker roller + a ramp with wheels on either side guiding the cube up would work in transitioning the cube from the ground to the tunnel. While testing, we realized that the wheels on either side did not grip well to the cube (we used colsons) and the transition from the kicker roller to the ramp and wheels was not as straightforward as expected. When the cube goes over the kicker roller, its motion is not very controllable especially when that is the only roller it is contacting. We added a vertical constraint (a piece of 2×4) to stop the cube from being kicked too high, however it deflected the cube from the center of the intake and away from the ramp. Watch this video to see the prototype in action.

Miscellaneous CAD

Task: Cartoon CAD and system integration of robot

  • Today was mostly filled with discussion regarding how best to integrate the various systems of the robot and how to constraint the placement of those systems. In terms of the elevator, we will be moving the outer bars (2×1 box tubing) to sit on top of the frame rails. The outside face of the intermediate stage will come in 0.138" (same clearance used in 2011) from the inside face of the outer bars, and then the carriage tunnel will be another 0.138" in from the inside face of the intermediate stage. This leaves us with around 17" for the width of the tunnel which we think will be enough to handle any orientation of the cube. We also investigated the elevator placement with regards to climbing. To make climbing especially easy on the drivers, we plan on driving straight up onto the ramp and having our bumpers flush against the scale wall and our elevator bar flush against the 2×2 box hanger box tubing. With those constraints, this means our elevator sits 8" from the outside face of our bumper which also means that given we want to spit cubes out on the back side of the tunnel (the side opposite the intake), we need to spit them 8"+. 8"+ is not ideal especially if we want to strategically place a cube, so we need to further investigate how best to optimize elevator placement. We also did line contact calculations on the bearings contacting the intermediate stage from the outside bar, and given that we are hanging 3 robots, then the bearings as well as the aluminum tubing will endure more load than their static load capacity and yield strength, respectively, can handle, To solve this, we tossed around ideas of alleviating a portion of the load from the bearings with a tensile member extending from the top of the intermediate stage to the CG of our robot (the tension of the cable acts opposite to the torque of the robots). Lastly, we decided that to ensure we have a smooth transition from the intake to the tunnel, we will have the intake fixed to the tunnel and not pivot, but will have the entire tunnel + intake system pivot such that it can stow within the frame perimeter, intake horizontally, and place cubes on stacks on the scale.


Task: RPLIDAR Driver

  • We tested the driver that was already written, but nothing happened. After rewriting some of the code, we were able to send a request to the RPLidar and received some sort of "ok" response, but still, the RPLidar did not start scanning.

Task: RPLIDAR Data Visualizer

  • We worked on some more modifications to the visualizer. We were able to cache all the data sent to the visualizer in an array, so that we could view data with specific timestamps. We also worked on being able to zoom in and pan around the image of the field, so that it is easier to see, but there are still some bugs with this.

Task: Intake Prototype

  • For testing purposes, we remapped the control board so we could toggle each of the four motors on the intake prototype with four separate buttons on the driver station. We also added some buttons to change the speed of the motors on the intake. In addition, we read the drive code, but since last year's programming bot did not have a working compressor for the dog shifters on the drivebase, the robot could not drive.

Build Blog Day 4 (1/12/18)


Task: Test different wheel arrangements between colsons and omnis

  • We decided to switch our initial idea of using 6 colsons to 2 colsons and 4 omnis on the drivebase. We also decreased the drivebase width by 0.6 inches to accommodate for the entire width of the colsons. In addition, we added custom wheel shafts into the Drivebase CAD. We also added the gearboxes into the drivebase CAD. This will require us to change the placement of the electronic components.


Task: Design drivebase gearbox

  • We started by resolving a few minor issues with packaging Cims around the shifter cylinder. We also realized that we needed more space for components in our gearbox, so we decided to increase the size of the gears between the Cims to fit all necessary components. After fixing these issues, we now have a working gearbox design. At our next build, we plan to finalize the assembly and detail the Gearbox CAD.


Task: Design intake prototype with two horizontal rollers to pull in and kick up cube

  • We began build by testing the 1st simbotics style intake prototype with 2 sets of wheels. After our testing, our results confirmed that asymmetry is the best way to go forward. Next, we assembled a new intake prototype with a horizontal roller and a kicker roller placed slightly behind the horizontal roller. When testing this prototype, we noticed that the cube would be lifted off the ground and get stuck between the rollers. We plan to keep testing this prototype since the kicker roller showed some promise in getting the cube over the frame rail. Look at Video 1 and Video 2 to see this new intake prototype in action.

  • Lastly, we laser cut version 2 of the simbotics intake, which will be assembled during our next build.


Task: Design tunnel with timing belts to drive the cube across on all four sides

  • The original plan for the tunnel was to have a square tunnel 13”x13” that would have power belts on each side. This way, no matter the orientation of the cube, it would always be in contact with at least 3 sides.


Task: Test the lidar driver with the roboRIO

  • We worked on the driver, which helps us get data from the RP LIDAR sensor. The sensor gives the distance in mm and the angle in degrees of a detected object.

Task: Hook up the visualizer to the robot

  • We also worked on the visualizer by plotting dummy points on a picture of the field. We encountered a few bugs, but fixed them all. Look below for a picture of the visualizer.

Task: Setup and testing

  • Limelight is a camera specifically made for FRC, which makes it easier to use, so we have been experimenting with it. We tuned the vision pipeline specifically for the power cube. In this process, we realized that we had to re-tune the vision pipeline in different lightings, so at each competition we would have to re-tune the pipeline if we were to use the Limelight. The Vision Pipeline is a set of consecutive image processing functions that work to isolate and find specific objects.

Build Blog Days 2 and 3 (1/8/18 – 1/10/18)


Task: Test drivebase with modelled dimensions (28"x33") 1.15” center drop; from top of frame rail and placed 2.5” from the front and back of the drivebase frame high centering on the ramp at various angles.

  • When approaching the ramp perpendicularly, the robot clears the ramp and does not high center. However, when it approaches at angle towards the corner of the platform where the front and side ramps meet, it high centers. Also, when the robot is travelling up the ramp with the cable protector below it, The back of the drivebase frame contacts the cable protector and high centers on it. The drivebase modelled with these dimensions in CAD accounts for a 16 tooth sprocket with chain OD and a 0.1" clearance between the sprocket-chain OD and the baseplate. In addition, the 4" colson wheels used are actually 3.9" wheels. If we were to bring the sprocket lower to the baseplate and use fully 4" wheels, there is a possibility it would not high center. We need to investigate the lowest we can go with the sprocket-chain OD and test with new 4" wheels. Additionally, these results may change our driving strategy where we will only attempt to go up the ramp perpendicularly. See these videos to see the drivebase in action.

Task: CAD drivebase weldment and begin work on drivebase assembly

  • We designed the drivebase frame rails such that the wheel placement and center drop can be easily modified as they are yet to be finalized. We went with our traditional West Coast Drive using 4” colson wheels. Assuming we will want to carry our partners while climbing, we need to beef up our drivebase, whether it be using thicker box tubing or by adding cross members. We will perform a bending calculation on different sizes of box tubing to determine what is the best size to use. Regarding bumper mounts, we currently see to ways to approach the task. The first way is a 2014 style bumper mount with latches on the drivebase frame that latch onto mounts on the bumper. The second way is a 2017 style bumper mount that uses guiding rods that go into the drivebase frame and some other latching system. The 2017 is definitely a harder bumper mount to work with, however, the straight face with mounting provisions may prove useful if we decide to deploy ramps for our partners to climb up on. We will investigate this in a cartoon CAD.

Task: Drivetrain gearbox design

  • We decided on a triangular configuration of mini-CIMS, with ratios that yield about 10ft/s and 18.6 ft/s. We are now trying to figure out how to package the shifter cylinder into the gearbox below the CIMs. We are exploring either a smaller bore cylinder or a nose-mount piston instead of pancake. Changing from 3/4 to 9/16 bore reduces the shifting force from 22lb to 11lb; Further testing is needed to see if this is enough force to shift. Regular air cylinders can be used if it is ok that they stick out longer than the CIMs. The next steps are to finalize which shifter cylinder we want to use, model the rest of the gearbox plate, and then detail in the entire gearbox assembly with Cheesy Parts.



Task: Test intake prototype with pivotable arm

  • We assembled the intake prototype and mounted it to the 2015 drivebase to test. We were able to run a few tests with a single set of wheels, but unfortunately, as the intake was made out of 0.25" plywood, a part of the arm broke off and we were unable to gather any further data.

Task: Test 2015 Simbotics style intake prototype with pivot wheel sets

  • We initially based the intake prototype off of 2015 Simbotics’; with the first set of wheels pivotable but not the second set–we spaced out the second set to be tangent to the cube when it is 13" width. When intaking a cube in a square position, the intake easily worked, however, when intaking a cube in a diamond position, the cube got trapped between the first set of wheels which were able to pivot to comply to the cube's shape and second set of wheels which were stationary. To fix this, we made the second set also pivotable and were able to intake a cube at different angles. We hooked up the motors on the intake to the drive talons on the development board and were able to simulate different speeds for different sides by turning with the control board joysticks. With different speeds, we were able to force the cube to rotate into a square position in a certain direction which shows that some amount of asymmetry may be necessary to intake cubes. We will continue testing this intake on the field carpet to account for the friction between the cube and field and will further design this in CAD into a stronger prototype.


Task: RPILIDAR Driver

  • We finished up writing the driver and implementing all necessary methods. The driver is ready to be tested once the LIDAR sensor arrives.  

Task: LIDAR Visualizer

  • We continued work on the LIDAR visualizer. We set up a Node JS server that recieves LIDAR point data encoded in JSON from the roboRIO using Network Tables. The server then uses websockets to send this information over to the viewing page. We also continued work on the visualizer interface. It can now plot fake JSON data, but needs to be hooked up the the websocket so it can display a continuous stream of data from the LIDAR sensor.

FRC Build Blog Day 1 (1/6/2018)

Here is the 2018 game animation.

Game Analysis
This year’s game involved many variables, requiring a strategy that succeeded in performing all tasks presented in the challenge. With the power ups, scoring based on points/sec, randomized sides, and the difficulty of climbing, no straightforward strategy which ensures a win presents itself. After trying various combinations of scores, we concluded the best way to maximize our points would be during autonomous when the scoring is scaled by a factor of 2 and during the endgame when each climb is worth 30 points. Since autonomous scoring is worth more than tele-op scoring, we decided that autonomous scoring was a major priority to stay ahead during a match. We planned for short paths to score cubes (<30 ft), so drivetrain acceleration and our ability to score from either side of the robot was critical for rapid cycles. We debated between starting off on the middle or side of the field. If we were to start off on the middle, we would have an equally distant route to reach the switch and scale. However, we could not guarantee the successful completion of our autonomous route as our alliance partners may get in our way. If we were to start on the side, we may either have a very long or a very short route to reach the switch and scale. However, we could guarantee the successful completion of our autonomous route as our alliance partners would not get in our way. During the endgame, we aimed for having all 3 robots climb or by having 2 robots climb and 1 levitate.

Task: Fix 2015 drivebase and prototype if it can go over the platform ramp

  • We fixed the 2015 drivebase which was missing a control system. We mounted our development board on the drivebase and programmed it to drive, but immediately saw issues as it went up the ramp. Because of the long wheel base and short distance between the wheels and the ground, the drivebase high centered on the ramp when the bellypan came into contact with it. This result shows that for our 2018 drivebase, we will need a shorter wheelbase and a greater centerdrop.

Task: Model drivebase motion up the platform ramp

  • We modelled in CAD the motion of a possible 2018 drivebase going over the platform ramp without high centering. We tweaked two factors (distance of outer wheels from side edge of frame rail, center drop) until we arrived with the dimensions of a drivebase that would safely clear the ramp with 4 wheels (2 on each side) always contacting it and without the bumpers or bellypan ever contacting it.

Task: Fix 2015 intake and prototype if it can intake Power Cubes

  • We fixed the 2015 intake which was initially missing the intake wheels, shafts, and timing belts. We used this intake to prototype the intaking of the Power Cubes. We did see some promise with this intake, however since it was designed for the tote and not the Power Cube dimensions, we were not able to efficiently intake the Power Cube. Moving forward, we plan on testing out different wheel materials to contact the Power Cube as it is being intaked and will design/prototype an intake with the correct geometry to fit the width of the Power Cube.

Field Prototyping
Task: Test coefficient of friction of Power Cube on scale plate

  • We wanted to calculate the coefficient of kinetic friction between the Textured HDPE and the fabric of the Power Cubes. To do this we looked at how high we had to lift the straight piece of HDPE before the Power Cube started to slide down. From this we calculated the angle formed and the coefficient of kinetic friction which ended up averaging to about 10.32 degrees and 0.18, respectively.

Task: Test geometry of 3 robots on the platform

  • We laid out the spacing of three robots on the scale platform to see if it was physically feasible of having 3 robots side by side with enough space for the robots to maneuver to those locations. It seems that it is possible for 3 robots to fit on the platform.

Task: Find what angle does the scale tilt to at its highest state

  • At its highest state, the scale tilts to around an angle of 7.662 degrees. Based on our data gathered from the task: “Test coefficient of friction of Power Cube on scale plate”, the Power Cubes will not slide down the scale plate when it is tilted to its highest state.

Field Construction
Task: Assemble wooden scale

  • We assembled a wooden version of the scale, however we are planning on assembling an aluminum version similar to the scale we will see in competition. This is because we don’t want any differences from the tournament scale from different materials that will arise in different materials (center of mass, weight, friction) which may impact our robot performance and drive our robot design.

Task: Space claim of 3 robots on the scale platform

  • In CAD, we made a space claim of 3 robots, placed them in various arrangements on the scale platform, and looked at the feasibility of having all 3 side by side. It seems that it is possible for 3 robots to fit on the platform.

Task: Program 2015 drivebase to steer in correct direction with controller joysticks

  • When we initially placed the development board control system on the 2015 robot and attempted to drive it, the wheels were turning in the opposite direction to the controller joysticks. We corrected this by reprogramming the drivebase to match with the direction of the controller joysticks.

Game Analysis, Scouting, and Strategy Workshop

On Thursday, December 7th, we hosted a Game Analysis, Scouting, and Strategy Workshop to help acquaint new team members with an important aspect of the robot game. The workshop by led by a member of Team 254’s drive team, Brandon Chuang. During the workshop, we taught new members about the importance of pit scouting and match scouting and how we use the data that we collect in order to form great alliances. In order to give our members a realistic experience, we helped them analyze a 2016 FRC Match Video and track the number of points scored by each team during the autonomous and teleoperated periods. Members were introduced to the team’s scouting database and how it is used at tournaments to organize collected data. Our drive coach, Kevin Sheridan, and FRC Technical Lead, Ashwin Adulla, also helped provide examples of some hardships that Team 254 went through when forming alliances at tournaments. We also emphasized the importance of working together with other teams and how that plays a role in an alliance’s performance. Overall, we strategically prepared our new members for kickoff!