Go to Post The best way to deal with an opponent who is going to hang is to go and hang yourself. - dtengineering [more]
Home
Go Back   Chief Delphi > ChiefDelphi.com Website > Extra Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 11-11-2016, 12:11
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,555
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
pic: T1G3R^2 - 3946's 2013 Ultimate Ascent robot

Reply With Quote
  #2   Spotlight this post!  
Unread 11-11-2016, 15:31
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,555
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: pic: T1G3R^2 - 3946's 2013 Ultimate Ascent robot

Continuing the 3946 history ramble begun here...

2013 - Ultimate Ascent. Put frisbees through goals, and climb the monkey bars, one rung at a time. Double Bizarro.

The first two days of build season were basically spent figuring out how a robot could launch a frisbee in a 112" frame perimeter - the online frisbee launchers we found needed a whole lot more elbow room. Also, the robot should preferably be short enough to limbo under the pyramid for an inside climb (which was obviously easier than an outside climb, once we figured out that the conveyor belt plan broke the rule that you could not contact more than two levels of the pyramid at a time).

Fortunately, this was the inaugural year of Robot in Three Days. I don't recall the details of their shooter, but it featured a wheel on one side and a "wall" on the other, which was enough inspiration to get us into gear.

Remembering lessons learned from 2012, we decided not to do floor pickup, and to prioritize scoring goals (in the high goals) over the climb. Mindful of weight, we went with a welded aluminum chassis that year with the chassis work taking place in mentor Bruce's garage.

The three sub-teams that year were "team foundation", which was responsible for driving and frisbees; "team climb" which was responsible for climbing the pyramid, and which had to work around foundation, and "controls" which included programming, wiring, and plumbing, but was more focussed on programming.

Team Foundation was worried first and foremost about getting frisbees into the high goal. The photo is looking right down the over-under barrels of the shooter. Frisbees were loaded into the upper barrel, slid down to the back where the baffles had been removed, to form a stack. A pneumatic mechanism (more on this later) would then push a frisbee up into the AM 8" pneumatic* wheels, which were located on the right side of the robot (left in photo) and extended slightly into the lower barrel. The first wheel was run at about 70% speed, the second at 100%. This was our initial guess based on giving the frisbee the same amount of energy from each wheel; trial and error proved this to give good results, both in terms of consistency of launch and the amount of sound & vibration produced. After putting in some teflon plates along the upper channel (both to reduce friction and constrain the frisbee a bit), we were putting frisbees in an ellipse about 4" high and 9" wide - much tighter than needed to make high goals. A new addition to the programming team programed a rasperry pi to process camera output and return the size and location of the goal. Once we got the goal in the right spot on the camera, we were solid making high goals. We managed to get this dialed in prior to bagging.

The arming mechanism (that is, that which lifted a frisbee into the wheels) was a piece of slightly bent aluminum bar mounted to the end of the rod of a 3/4" pneumatic cylinder. It pushed on the inside of the leading edge of a frisbee, reaching up from underneath. It worked well in many test launches at the shop, but during competition it started getting buggy, and eventually jammed completely in our final qualifying match. We were not selected to an alliance, but we were on the short list for alternates, so we struggled in the pits to fix it, but after the semifinals started we threw in the towel. It was over a year before we mustered the gumption to get that working again.

The loading mechanism would jam whenever we had more than two frisbees in at a time (the rules allowed four). We resolved this by including a "check" mechanism low in the loading barrel. We would load two frisbees, drop them through, then load two more. The check mechanism consisted of some FLL wheels driven by a PG gearmotor, mounted low enough to catch the frisbees but high enough that we could run the motors and let them through.

Knowing what I know now, the drive train was simply an embarrassment. On the front, (under the high end of the shooter) we had two AM 6" plaction wheels with wedgetop tread (ok so far) direct mounted on CIMple boxes with a single CIM on each, yielding nearly 30fps free speed, 24 adjusted -- way too fast. On the rear (where we had very little space around the shooter) we had AM 6" omni wheels. Idle omni wheels. Not surprisingly once you draw a free body diagram, when making the long run from one end of the field to the other we made much better time and had better control in reverse than forward.

Team Climb (which I mentored) was obsessed with the 60 point (3 rung) climb, and having to work around the frequent unannounced foundation changes, had quite a job of it. The primary lifting was done with the four large (1.5"x20") pneumatic cylinders, two on either side. Each cylinder was mounted to its mate with two 2-hole mending plates, with the cylinders facing opposite directions. This enabled the length of the unit at full extension to be nearly triple the compressed length. The downward-extending rod was mounted to the lower chassis. The pair was located in a cage made of angle aluminum with a felt lining which kept it from rotating while allowing the cylinder bodies to slide up. The upward-extending rod was a hex non-rotating rod terminating in a hook machined by NASA. This unit was reclined at an angle similar to the slope of a pyramid face. The upper cylinders were powered through one solenoid valve, the lowers through another, making this a "three position" hook. There was also a "railcar" on top of the robot driven by a lead screw (OK, threaded rod) with two hooks which also engaged the pyramid horizontal bars. These came forward until they were directly over the robot CoG to get the front wheels off the ground.

There was also a window-motor-placed "deflector" which pushed the rungs clear of the bumpers; the green bar across the top is part of it. Like the finally successful bridge tipper in 2012, the window motor put the deflector in place, but mechanical stops did the job. Multi-rung climbing was a complex ballet that we never did get working. The climb was going to use a lot of air, so we had 7 white clippard tanks; scary in retrospect. We would have scored more points with a 10 point climber which worked than this 30 point climber which never worked.

The control system was an afterthought, stuffed into every available nook and cranny of the robot, starting low and working up (which mostly meant under the shooter barrel). Our wiring lead that year described controls layout management as "3-D Tetris". We had so many loose connections, leaks, half dead batteries, and left-open vent plugs that the jammed arming mechanism was misdiagnosed as a control problem until the very end.

In 2013, we used bumper covers (IIRC the base bumper was red, and blue was a cover). The one time the climbing mechanism got all of the robot wheels completely off the floor, a pulled-loose bumper cover was dragging.

Green paint on aluminum. Yuck. Looked so-so when fresh, and horrible after 10% of it had peeled off.

Lessons Learned:
  • Learn from your mistakes. In particular, KISS and Do the Math from 2012, which we partially did, but not consistently.
  • Pay attention to detail, especially on controls. Try to anticipate problems and fix them before they become problems. Aim not for functionality, but consistent functionality.
  • Skip the welding. Because we had to send the chassis out for welding, we had much less time with the robot in house than we would have liked. We probably gave the robot a test drive before it went in the bag, but it must have been brief. The discovery that we had problems driving forward were not discovered until practice rounds.
  • Spend some effort on the drive train and the controls wiring. You won't get far without them.
  • Figure out some way to get drive practice next year!
  • Have some one responsible for making sure that all the various pieces and parts come together, and that each one is doing what it is supposed to do. (That's become my job the past few years.)


*Yes, fast-spinning pneumatic wheels. Wouldn't do that today as I've heard of "marshmallow" wheels, but solid wheels would not have engaged the frisbee for very long.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.

Last edited by GeeTwo : 11-11-2016 at 15:35.
Reply With Quote
  #3   Spotlight this post!  
Unread 12-11-2016, 14:06
gixxy's Avatar
gixxy gixxy is offline
Programming and Arduino Mentor
AKA: Gustave Michel III
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Nov 2011
Rookie Year: 2012
Location: Ruston, LA
Posts: 207
gixxy is on a distinguished road
Re: pic: T1G3R^2 - 3946's 2013 Ultimate Ascent robot

Quote:
Originally Posted by GeeTwo View Post
Our wiring lead that year described controls layout management as "3-D Tetris". We had so many loose connections, leaks, half dead batteries, and left-open vent plugs that the jammed arming mechanism was misdiagnosed as a control problem until the very end.
That's "4-D Tetris". Not only were we trying to stuff the controls into extremely narrow spaces, leading to use of vertical boards as horizontal boards, but every 2 days or so changes where made as to where structural parts of the chassis would be, leading to required total redesign of the controls layout, and with each subsequent re-design, less effort and consideration given, and more "just fit it in" mentality.
__________________
Programmer - A creature known for converting Caffeine into Code.
Studying Computer Science @ Louisiana Tech University
Associate Consultant @ Fenway Group

2012-13: 3946 - Head of Programming, Electrical and Web
2014 - 3468 - Programming Mentor
2015 - Present - Lurker
Reply With Quote
  #4   Spotlight this post!  
Unread 12-11-2016, 18:10
MARS_James's Avatar
Happy Birthday! MARS_James MARS_James is offline
Always Scouting
AKA: James Comstock
FRC #0179 (The Children of The Swamp)
Team Role: Tactician
 
Join Date: Jan 2010
Rookie Year: 2006
Location: Jupiter, Florida
Posts: 1,952
MARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond reputeMARS_James has a reputation beyond repute
Send a message via AIM to MARS_James
Re: pic: T1G3R^2 - 3946's 2013 Ultimate Ascent robot

Quote:
Originally Posted by GeeTwo View Post

Team Climb (which I mentored) was obsessed with the 60 point (3 rung) climb,.
So the 3 rung climb was 30 points, then with the maximum colored disks allowed would net you an additional 20 for a 50 point climb. So unless your team was obsessed with climbing with an illegal amount of disks you were not getting a 60 point climb
__________________
Driving Record: 24-8
Coaching Record: 66-31
2014 South Florida Regional Woodie Flowers Finalist


Reply With Quote
  #5   Spotlight this post!  
Unread 12-11-2016, 19:27
GeeTwo's Avatar
GeeTwo GeeTwo is offline
Technical Director
AKA: Gus Michel II
FRC #3946 (Tiger Robotics)
Team Role: Mentor
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Slidell, LA
Posts: 3,555
GeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond reputeGeeTwo has a reputation beyond repute
Re: pic: T1G3R^2 - 3946's 2013 Ultimate Ascent robot

Quote:
Originally Posted by MARS_James View Post
So the 3 rung climb was 30 points, then with the maximum colored disks allowed would net you an additional 20 for a 50 point climb. So unless your team was obsessed with climbing with an illegal amount of disks you were not getting a 60 point climb
Right, 30 points. I probably crossed my memory up with the fact that it was 60 inches, plus the size of the rung.
__________________

If you can't find time to do it right, how are you going to find time to do it over?
If you don't pass it on, it never happened.
Robots are great, but inspiration is the reason we're here.
Friends don't let friends use master links.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 01:33.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi