Team 2337: 2013 Robot

http://d3j5vwomefv46c.cloudfront.net/photos/large/770644740.jpg

Here is Team 2337’s robot for Ultimate Ascent, Crossfire.

Extensive robot photos taken by Daniel Ernst, and a couple of team members can be found on the team Google+ page. All of our match videos from inside Michigan are available via the First in Michigan YouTube channel.

Robot CAD will be uploaded to FRC-Designs (post will be edited to reflect link when it is uploaded).

Robot features:

  • Four-CIM, SuperShifter-driven
    drivetrain in an octagonal shape using the 48/50/60 gearset (slimmed down), direct driven to the center four 4” VexPro VersaWheels, and chained out to the same, inline 4” VexPro VersaWheels. Speed should be around 7.5 and 14.5 fps. This is underpinned by our first sheetmetal chassis at ⅛” inch, with a bottom waterjetted piece and the rest milled. - From the ground disc intake
    , with two top rollers driven by a BAG motor through a 4:1 VexPlanetary through O-rings. The disc would be lifted off the ground slightly by a lexan lip, and then once the roller made contact, the lip would actuate upward with the disc to keep it moving. - A large arm driven by a linkage similar to FRC67 from 2007 and FRC148 from 2011
    . Powered by a MiniCIM, through a custom transmission at 335:1 inside the gearbox and through a wire EDM’d central gear (which had a ratio of 12:100 for a final ratio of 2790). - On the arm, a rubber-band disc management system
    with an upper tray to transfer discs to the two lower trays. The top part and bottom parts are driven separately, each by a AM 550 through a VexPlanetary at a 5:1 and then through timing belts. - A double-shooter
    that can shoot two discs out at once, or one at a time. Each shooter is a single AM 8” pneumatic wheel with about 90 degrees worth of wrap on the disc. The two wheels are direct-driven together by four BaneBot 550s paired together in CIMulators. - Two lexan hooks for hanging from level 1
    , each powered by a pneumatic cylinder and extra rubber banding. - Large lexan hood attached to arm for feeder station loading
    and blocking shots while the robot stays below 60". - Attachable blocker
    that folds down with the arm, and rises up to ~80" (first used at Worlds).

We have open-sourced all of our LabVIEW robot code for Crossfire on our team GitHub page.

Some software highlights:

  • LabVIEW robot project
    managed with git and hosted by GitHub. During build season, different projects had different branches, and then we completely manually merged code by hand. - ”Cheesy Drive”
    , an RC-style drive system where throttle and steering are on separate joysticks on the same gamepad - For intake belt system control, a simple state machine
    with different states commanded by operator - Bang-bang
    shooter speed-control with a unique bottom gain, tuned for specific speeds - Straight autonomous driving tracking the gyro and gyro turns
    for the 7 and 5 disc autonomous modes - Data logging to text file
    that can be retrieved via the cRIO FTP server. Tracks shooter speed and arm position for checking shots. - Last year’s autonomous scripting
    system with a trapezoidal motion profile algorithm implemented inside (not used in competition) - Dashboard-based vision processing
    (not used in competition) - Small usability improvements (from our perspective) NERDViewer.html
    (from FRC254’s 2012 code release’s PoofViewer.html) for driver/operator/coach viewing (not used in competition)

We didn’t look too hard at automated LabVIEW tools for diff and merges - any recommendations would be appreciated. Manual merges were inefficient, not fun, and resulted in refnum naming problems later on. We gave up branching after build season, when a lot of development and tuning happened at competitions, where only one or two programmers were involved, and they would simply work off of the master branch.

2013 Competition Season Performance:

  • Kettering District
    Quarterfinalists, seventh alliance - second pick, ranked 26th, Engineering Excellence Award - Troy District
    Quarterfinalists, sixth alliance - first pick, ranked 12th, District Chairman’s Award - Bedford District
    Semifinalists, third alliance - second pick, ranked 35th, Gracious Professionalism Award - Michigan State Championship
    Finalists, first alliance - second pick, ranked 52nd, State Chairman’s Award - Championship - Galileo Division
    Semifinalists, third alliance - second pick, ranked 46th

One of my favorite robots this year. Good job guys!

Your robot is a circle with a dash in it?

Thanks! Playing your alliance in the Galileo quarterfinals was intense. Two full court shooters between you and 1806… the thing that will stay with me the longest was 1806 falling off of the pyramid. I still feel really sorry about that.

It should be fixed, thanks. Note to self: do not use Google+ to host embedded photos. I’m not sure why the picture didn’t show up, the picture was shared publicly.

Loved your bot. It was just fun to watch, though I didn’t get to see many matches. I was jealous of your pit, by the way.

When discussing my favorite robots at champs, first I would talk about 1503, then about you guys. A double barreled shooter who’s also an excellent defender.
Almost makes me wish you were in Archimedes!
Good job to the Enginerds!

An autonomous readme has been posted to the GitHub page as above. Also, as previously announced by FRC-Designs, robot CAD can be found on the 2013 robot design page.

Thank you so much! With all of the full court shooters in Galileo… it was likely the right place for us to play that fullback role, unfortunately - because Archimedes looked like a blast this year!

It’s good that we get to see 2338 quite a bit when our pits are next to each other, at out-of-state events like MARC and Championship. I personally enjoyed playing with your community display, that had the handle to turn the gears displaying the team’s partnerships - that was cool! Out of curiosity, what did you like about our pits?

Yeah, it’s just too bad the chairman’s judges didn’t like our display :confused:
Your pit looks pretty good (I’m an AMD guy so I’m partial to the whole red and black thing), looks like it has plenty of storage space and you still have a lot of open floor for the robot. Also like that light over the workbench.