Go to Post Friends don't let friends prototype alone. - SenorZ [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 05-01-2014, 23:30
Woolly's Avatar
Woolly Woolly is offline
Programming Mentor
AKA: Dillon Woollums
FRC #1806 (S.W.A.T.)
Team Role: Mentor
 
Join Date: Feb 2012
Rookie Year: 2012
Location: Springfield, MO
Posts: 512
Woolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond reputeWoolly has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by DavisC View Post
Otherwise, the strongly robust robots might hold more weight in alliance selection...
Well, hypothetically, if you have 2 robots that can throw, none of the robots left available to pick can catch, and one of your robots has a multi-ball autonomous, the safest pick is a box (or ramp if you want to get fancy with loading) with a good drive-train under it.
__________________


Team 1806 Student: 2012-2013 | Mentor: 2013-Present
Reply With Quote
  #17   Spotlight this post!  
Unread 05-01-2014, 23:46
Bryan Herbst's Avatar
Bryan Herbst Bryan Herbst is offline
Registered User
AKA: Bryan
FRC #2052 (KnightKrawler)
Team Role: Mentor
 
Join Date: Sep 2007
Rookie Year: 2007
Location: Minneapolis, Minnesota
Posts: 545
Bryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond reputeBryan Herbst has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by redneckrobot View Post
that is the programmers job
This isn't possible.

The Driver's Station (and FMS) are responsible for telling the robot if it is in teleop, in autonomous, or if it has been disabled. If there is no communication with the DS/FMS, the robot cannot move. Allowing the robot to move at all (electronically) in this situation would be a huge safety issue.

I think the point of the question also goes beyond communication issues. What if the robot loses power (due to a loose wire, a battery that fell out, or something else)? What if a hit from another robot resets your cRIO?

There are a number of problems that could cause your robot to become inoperable with a ball in its grasp.
__________________
Team 2052- KnightKrawler
Mentor and volunteer
Reply With Quote
  #18   Spotlight this post!  
Unread 05-01-2014, 23:52
yash101 yash101 is offline
Curiosity | I have too much of it!
AKA: null
no team
 
Join Date: Oct 2012
Rookie Year: 2012
Location: devnull
Posts: 1,191
yash101 is an unknown quantity at this point
Re: Ball eject

This is what it should be like:
If the driver thinks the robot is jammed, either the robot is disabled by FMS, or that ball is invalidated if it ever exits the robot. That way, even if the robot is stuck, it can perform something else, like defense or if they add an endgame!
Reply With Quote
  #19   Spotlight this post!  
Unread 05-01-2014, 23:58
AllyMeeg's Avatar
AllyMeeg AllyMeeg is offline
Registered User
AKA: Ally Meegan
FRC #2410 (Metal Mustangs)
 
Join Date: Jan 2014
Rookie Year: 2013
Location: Overland Park, Kansas
Posts: 1
AllyMeeg will become famous soon enough
So you could try to build your robot so that it has the ability to retrieve balls from disabled robots with an arm of some kind.
Reply With Quote
  #20   Spotlight this post!  
Unread 06-01-2014, 00:25
atucker4072's Avatar
atucker4072 atucker4072 is offline
Andrew Tucker
AKA: Andrew Tucker
FTC #4968 (Rapid Robotics)
Team Role: Mentor
 
Join Date: Feb 2012
Rookie Year: 2011
Location: Glenwood Springs, Co
Posts: 152
atucker4072 has a spectacular aura aboutatucker4072 has a spectacular aura aboutatucker4072 has a spectacular aura about
Re: Ball eject

Quote:
Originally Posted by yash101 View Post
This is what it should be like:
If the driver thinks the robot is jammed, either the robot is disabled by FMS, or that ball is invalidated if it ever exits the robot. That way, even if the robot is stuck, it can perform something else, like defense or if they add an endgame!
There is no secret endgame. End of discussion.
Reply With Quote
  #21   Spotlight this post!  
Unread 06-01-2014, 00:37
Dalrik Dalrik is offline
Registered User
FRC #0639 (Code Red Robotics)
Team Role: Alumni
 
Join Date: Jan 2014
Rookie Year: 2010
Location: Ithaca, NY
Posts: 2
Dalrik is an unknown quantity at this point
Re: Ball eject

The solution is, unfortunately, completely mechanical. The electrical and software rules and libraries expressly prohibit a disabled robot from taking any action.

What teams will have to do, one way or another, is design their collection systems such that when disabled they either release the ball or weaken their grip such that a hit from an alliance partner will dislodge it. Congratulations, you've found the difficult design challenge in this year's game. No, don't design your launchers to immediately fire if they lose power, as that's a clear violation of safety.
Reply With Quote
  #22   Spotlight this post!  
Unread 06-01-2014, 00:43
Kevin Selavko's Avatar
Kevin Selavko Kevin Selavko is offline
Registered User
AKA: Voltonless
FRC #3260 (SHARP)
Team Role: Electrical
 
Join Date: Jan 2012
Rookie Year: 2008
Location: Beaver PA USA
Posts: 155
Kevin Selavko is on a distinguished road
Re: Ball eject

On our vex robot our pistons default to retracted so we start in a legal configuration, but can you have a solenoid that defaults to push a piston into where you store your ball when it has no signal, and possibly have it on its own pneumatic circuit in case the first one fails? This way if you have a ball and you become disabled/battery dies/act-of-god, the ball will be ejected, or is this not allowed?

EDIT: I does not need to be very forceful, just enough to make your ball holder a shape that the ball will roll out of.
__________________
Team SHARP
Pittsburgh Regional Champions 2014
Vex Pittsburgh Excellence Award 2014
Vex Pittsburgh Champions 2014
Vex Maryland Champions 2014
Pittsburgh Regional Finalists 2013
Buckeye Regional Finalists 2013

Last edited by Kevin Selavko : 06-01-2014 at 00:45.
Reply With Quote
  #23   Spotlight this post!  
Unread 06-01-2014, 01:05
RRLedford RRLedford is offline
FTC 3507 Robo Theosis -- FRC 3135
AKA: Dick Ledford
FRC #3135 (Robotic Colonels)
Team Role: Mentor
 
Join Date: Jan 2010
Rookie Year: 2009
Location: Chicago, IL USA
Posts: 286
RRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond reputeRRLedford has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by Dalrik View Post
The solution is, unfortunately, completely mechanical. The electrical and software rules and libraries expressly prohibit a disabled robot from taking any action.

What teams will have to do, one way or another, is design their collection systems such that when disabled they either release the ball or weaken their grip such that a hit from an alliance partner will dislodge it. Congratulations, you've found the difficult design challenge in this year's game. No, don't design your launchers to immediately fire if they lose power, as that's a clear violation of safety.
Are you saying that it is illegal to have a robot with a pneumatic cylinder that, when working properly with bot powered on, gets air via a normally closed solenoid valve and extends, stretching some surgical tubing to move an element which keeps the ball from falling out of the robot.

Then when emergency stopped, the normally closed air valve closes, and a 2nd normally open valve opens to bleed air from the cylinder, allowing the the piston to retract by the surgical tubing tension, releasing the hold ball element and dropping the ball.

If this kind of ball eject scheme would be illegal by the current rules, then there should be an exception rule written to allow such a scheme, or to just have another fresh ball cycle be started from the pedestal, when robots carrying calls are disabled

-Dick Ledford
__________________
FTC 3507 RoboTheosis
FRC 3135 Robotic Colonels
Reply With Quote
  #24   Spotlight this post!  
Unread 06-01-2014, 08:37
wireties's Avatar
wireties wireties is offline
Principal Engineer
AKA: Keith Buchanan
FRC #1296 (Full Metal Jackets)
Team Role: Mentor
 
Join Date: Jan 2006
Rookie Year: 2004
Location: Rockwall, TX
Posts: 1,171
wireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond reputewireties has a reputation beyond repute
Send a message via AIM to wireties
Re: Ball eject

Quote:
Originally Posted by Woolly View Post
I for one think that robots moving without connection to the driver station constitutes a safety issue, as does FIRST. This is why the base robot project shipped with your choice of programming language tends to make the robot refuse to do anything without connection to the driver station, and a signal that it is in teleop or autonomous mode.
In theory nothing (much) can move if the communications are down. The FIRST libraries on the robot fire a watchdog that disables all control outputs.

If a robot on my alliance went brain dead I would want them to hit the big red button - maybe the refs would put the ball back into play?
__________________
Fast, cheap or working - pick any two!
Reply With Quote
  #25   Spotlight this post!  
Unread 06-01-2014, 09:05
Mr. Lim Mr. Lim is offline
Registered User
AKA: Mr. Lim
no team
Team Role: Leadership
 
Join Date: Jan 2004
Rookie Year: 1998
Location: Toronto, Ontario
Posts: 1,125
Mr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by atucker4072 View Post
Thia will be a great test of gracious Professionalism! Although if teams meet before a match like they should lots of problems can be avoided. If I had to as a driver I wouldn't like a team to load a ball into their robot if they haven't tested it or been successful with it.
A very BIG test of gracious professionalism

I'm not sure where to go with this aspect of the game.

I'm asking myself very seriously, if a robot can't automatically eject a ball when disabled, should it be allowed to intake it?

Autonomous is also very tricky - if your robot requires the ball to be inside your robot at the start of the match, and can't be easily freed by another robot, your alliance partners might ask you not to run it.

How would you feel if your alliance partners ask you never to pick up a ball? Or to not run your autonomous?

Would you ask your alliance partners not to do those things?

Because right now, this seems like the prudent thing to do.
__________________
In life, what you give, you keep. What you fail to give, you lose forever...

Last edited by Mr. Lim : 06-01-2014 at 09:46.
Reply With Quote
  #26   Spotlight this post!  
Unread 06-01-2014, 09:57
FrankJ's Avatar
FrankJ FrankJ is offline
Robot Mentor
FRC #2974 (WALT)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2009
Location: Marietta GA
Posts: 1,946
FrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond repute
Re: Ball eject

The issue is the state "Estop" is really the same as disabled. So you load the ball in the disabled state (Robot is disabled until the match starts) Nothing will happen until the robot is enabled. The coders that can make the robot magically eject the ball on system failure aren't going to be the ones with these kinds of issues.

Scouting is going to be important this year (as if it was never unimportant) because a non functioning robot in the seeding matches can really skew the scores.

This might be the year that a good defense is a good offense.
Reply With Quote
  #27   Spotlight this post!  
Unread 06-01-2014, 10:30
JohnSchneider's Avatar
JohnSchneider JohnSchneider is offline
Registered User
FRC #3310 (Black Hawk Robotics)
Team Role: Mentor
 
Join Date: Mar 2010
Rookie Year: 2010
Location: Dallas
Posts: 779
JohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond reputeJohnSchneider has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by Mr. Lim View Post
A very BIG test of gracious professionalism

I'm not sure where to go with this aspect of the game.

I'm asking myself very seriously, if a robot can't automatically eject a ball when disabled, should it be allowed to intake it?

Autonomous is also very tricky - if your robot requires the ball to be inside your robot at the start of the match, and can't be easily freed by another robot, your alliance partners might ask you not to run it.

How would you feel if your alliance partners ask you never to pick up a ball? Or to not run your autonomous?

Would you ask your alliance partners not to do those things?

Because right now, this seems like the prudent thing to do.
It's a terrible enough feeling at a regional telling a team "Hey we need you to put this giant net on and sit there and not do what your robot was designed to do because of the nature of the game." I cannot imagine telling someone they cannot play the game in its proper form because "We don't trust your robot's design".

Heck, there are times when a team will just refuse and try it anyways and when the ball gets stuck then what do you do? The rules pertaining to this are not fair for any member of an alliance.

An E-Stopped robot with a ball most definitely should not have its ball counted. That way there's at least a way to keep playing the game for the other 2.
Reply With Quote
  #28   Spotlight this post!  
Unread 06-01-2014, 10:49
RSaunders RSaunders is offline
Registered User
FRC #2537
 
Join Date: Jan 2013
Location: Maryland
Posts: 4
RSaunders is an unknown quantity at this point
Re: Ball eject

Why wouldn't the referees consider a ball in an EStopped robot "out of play"? It's a good idea to raise this question in the Q&A, but software solutions aren't what you want when a simple human decision can solve your problem. That's what referees are for.

/Randy
Reply With Quote
  #29   Spotlight this post!  
Unread 06-01-2014, 11:40
DonRotolo's Avatar
DonRotolo DonRotolo is offline
Back to humble
FRC #0832
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Atlanta GA
Posts: 7,019
DonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond repute
Re: Ball eject

Quote:
Originally Posted by Mr. Lim View Post
I'm asking myself very seriously, if a robot can't automatically eject a ball when disabled, should it be allowed to intake it?
I would think a robot capable of taking action while disabled would be a safety hazard, violating R8.
__________________

I am N2IRZ - What's your callsign?
Reply With Quote
  #30   Spotlight this post!  
Unread 06-01-2014, 11:47
Whippet's Avatar
Whippet Whippet is offline
MIT Class of 2020
AKA: Luis Trueba
FRC #4301 (New Tech Narcissists)
Team Role: Alumni
 
Join Date: Feb 2011
Rookie Year: 2011
Location: Cambridge, MA
Posts: 1,187
Whippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond reputeWhippet has a reputation beyond repute
Send a message via Yahoo to Whippet
Re: Ball eject

Quote:
Originally Posted by DonRotolo View Post
I would think a robot capable of taking action while disabled would be a safety hazard, violating R8.
What about the robots in 2012 with the after-the-buzzer pneumatic bridge balancers?
__________________
2010: FRC 3043, Build Assistant
2011: FRC 3043, Head of Minibot subteam; FLL 12762, Team Captain
2012: FRC 3043, Electrical; FLL 12762, Team Captain; FTC 5670, Team Captain
2013: FRC 4301, Electrical, Team Co-Captain
2014: FRC 4301, Electrical/Programming, Team Co-Captain
2015: FRC 4301, Electrical/Programming, Team Captain
2016: FRC 4301, Chief Technical Officer; FTC 10860, 10861, and 11004: Mentor. Winner, Hub City Regional (3310 & 4063)
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 06:31.

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