Season Goals with New Team Members

Today we discussed the team’s goals for the year, leadership positions and rules. This was the first meeting in which many of the team members were present. We started the meeting with introduction so that everyone could get to know each other. Then we began to deliberate our regulations and objectives for the season.

We re-affirmed that our goals for the year are:

  • Win the Bryson Cup in our league meets
  • Be the Final Boss at the LA Regional Championship
  • Play in the elimination matches at Worlds

We decided upon leadership roles after Mr. Porter described the responsibilities of each. The results are as follow

Captain (Engineering Notebook) – Emilio

The captain is the member of the team who makes very sure that the Engineering Notebook is current and high quality.

Business Lead – Kristoffer

Te business lead coordinates the rest of the team’s efforts to
secure funding. They have final say over whether or not we buy
more parts, over t-shirt purchases, etc.

Mechanical Lead – Chase

The Mechanical Lead makes sure that we remain a CAD-first team.
They own the Fusion 360 model and make sure that everybody, from
time to time, contributes to it.

Programming Lead – Jonah

The Suit Bots expectation is to have a full autonomous ready by meet
zero. The programming lead ensures that our teleop and autonomous
are ready for competition.

Video Lead – Emily

This lead is responsible for our Promote award submission, a video
reveal (or joke reveal video) if we choose to do one, and any other
vlogging the team may choose to do.

Electronics Lead – Andrew

The electronics lead makes sure that the robot is wired properly and
has all of the sensors it needs to run a successful autonomous.

Communications Lead – Jessica

Responsible for the Suit Bots’ web page and social media presence.
Works with the mechanical lead to make sure that any SBKOP components
are available for other teams to download.

Outreach Lead – Outstanding

The outreach lead ensures that we develop and maintain a suitable
schedule of outreach events, of both the learning (Connect) and
teaching (Motivate) variety.

Not only did we establish goals for the team, but also for individual members as well. These included every team member learning how to do a bit of every step in the design and creation of a fully running robot. Subjects like CAD, java programming, and 3-D printing are included. We also set expectations for each of the team members that we would follow either by the deadline or throughout the robotics season.

Goals and expectations for Suitbots and team members.

JPL Tour

Depicted in the picture below is Suit Bots Alumni Fletcher demonstrating how the project he is working on for JPL is doing. The project he is working on is designed to take off the gravitational pull of an object hanging on it. He allowed one of our team members to feel the effect by hanging off of a bar hooked up to the motor.

In addition to Fletcher’s gravity offload system, we learned about Alumni Brian Bugert’s work on the Deep Space Network. He is responsible for writing the software that ¬†manages the DSN.

Visiting JPL’s campus

 

Seeing one of our alumni’s work on a gravity offload system

Blinken LED Driver Exploration

Ryan works on learning levels for the Blinkin

Determining the proper step value for the Blinken

Today we worked on learning how to use the REV Robotics Blinken LED driver. Previously we learned how to set the user colors, but we did not know how to control the color modes.

The REV documentation listed PWM values for a RoboRIO controller that would activate different color levels. The RIO has a PWM output range that differs from the FTC control units. We created a Wolfram Cloud notebook to try to figure out what the values would be for FTC. Our first approach was to find the step value for each different color:

From there we wrote a small OpMode to start at what the REV documentation said was the beginning of the FTC output range (.2525) and step through colors one by one, taking note of what colors and patterns we saw for each value.

We learned that, though the REV documentation says the range only goes to
.7475, some values are above that published range. Black — or “off” — is at 0.7775, for example. We determined that the colors we are most likely to use are:

  • Re (.6725) for when we are the Red alliance
  • Blue (.7425) for when we are the Blue alliance
  • Green (.71715) for a “go” alert color
  • Yellow (.6975, actually gold) for a second alert color
  • Black (.7775) to turn the lights off.

On the next page is our observations of colors and patterns based on
PWM signals to the REV Expansion Hub.