team971

youtube

971’s Madera MadTown Throwdown reel!

featuring:

  • matches
  • Maxwell running around in a giant spartan costume
  • video proof of Austin putting up the logo backwards in the mentor competition
  • the announcers unbelievably slow score-announcing during the finals matches
  • Roy holding our finalists trophy!

971 Presents: Renegade

Watch us compete in our first regional today through saturday at Davis!

a couple of specs (as seen on chief delphi)

  • All new sheetmetal chassis with just 3 major parts, weighing only 12 lbs.
  • Belt driven 6wd, 16/7 fps 2-speed transmission
  • Over-bumper pickup and belt driven ball path. ~1 second from a ball touching the intake to the top of the shooter
  • Intake doubles as bridge manipulator, capable of producing 120lbf at the end
  • Hopper (not pictured) for collecting from the inbounder station and other robots
  • Low bumpers to assist in pushing matches and prevent inadvertently driving over balls
  • Pneumatically powered drop-down skids lift up the front of the robot for crossing the bump
  • Low CoG, just 8" above the floor
  • 2-position hood for fender shooting and long distance shots
  • Automatic ball indexing with banner sensors
  • Several custom circuits including a FitPC for faster vision processing and code updates, a custom gyro board for high-speed gyro feedback
  • Shooter wheel spinup from dead stop to shooting speed in ¼ second with no overshoot

Catch us this week at Sacramento/Davis, and week five at SVR!

Madstream Webcasts

It has been brought to my attention that the meeting time for Sunday was listed at 12 midnight, which would be an unusual meeting time this early in the season. We will meet at 12 noon instead, so everyone can get some sleep.
— 

an email typo fixed by our team captain.

sleep? during build season? puh-lease.

edit: also, can we just pause for a moment and notice that someone was confused about the time in the first place? someone on our team saw this email and went “ooh man, midnight, I don’t want to meet then. Oh, wait, typo!”