Go to Post I saw 2274, a rookie team that had won the regional, gathered around their mentor. He was holding their trophy and saying, "This is what it is all about. Teamwork and cooperation. You guys did great." - Po-ser [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rating: Thread Rating: 7 votes, 5.00 average. Display Modes
  #16   Spotlight this post!  
Unread 14-11-2012, 17:22
Tom Line's Avatar
Tom Line Tom Line is offline
Raptors can't turn doorknobs.
FRC #1718 (The Fighting Pi)
Team Role: Mentor
 
Join Date: Jan 2007
Rookie Year: 1999
Location: Armada, Michigan
Posts: 2,554
Tom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond reputeTom Line has a reputation beyond repute
Re: Driver Station + Space Bar

Quote:
Originally Posted by Bot190 View Post
Something that doesn't seem to be understood by many so far is the differences between disabling and e-stopping the robot.

Disable - Stops the execution of code for now
E-Stop - Changes robot state to disabled and sets something in the cRIO that prevents it from being enabled again.

Under normal (non-competition usage) there is no reason for the functionality of the e-stop button. Unless it does something I'm unaware of, it disables the robot in the same way as the disable button. Disabling the robot until a power cycle serves little purpose other than to slow development down considerably.

I seem to remember a time where the space button disabled the robot and the enter button e-stopped the robot. This only changed last year, causing a fair amount of confusion among team members.
If both buttons are actually necessary, a way to either switch the mapping or select your own mapping would be extremely helpful.
See Mark's note below. That's a good question for the NI guys though: I'd like to know more about the differences too.

There is a fairly good argument why the mapping should not be changed. If everyone in FIRST knows the mapping, then anyone in FIRST can stop your robot by smacking the spacebar/enter key. Safety is one of those items where you have to take the attitude that, if it can happen, it will.

Last edited by Tom Line : 14-11-2012 at 23:23. Reason: Editted to remove incorrect information.
  #17   Spotlight this post!  
Unread 14-11-2012, 17:36
Brandon Holley's Avatar
Brandon Holley Brandon Holley is offline
Chase perfection. Catch excellence.
AKA: Let's bring CD back to the way it used to be
FRC #0125 (NU-TRONs, Team #11 Alumni (GO MORT))
Team Role: Engineer
 
Join Date: Jan 2004
Rookie Year: 2001
Location: Boston, MA
Posts: 2,593
Brandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond reputeBrandon Holley has a reputation beyond repute
Send a message via AIM to Brandon Holley
Re: Driver Station + Space Bar

I think a good solution to the problem may be a better way to un-e-stop the robot beside a reboot.

Would there be some way to hit a specific combination of keys (ctrl+shift+alt+U ?) that could then disengage the e-stop? I should note, I have very little knowledge of how the DS is built or what the e-stop is actually doing when it is engaged.

-Brando
__________________
MORT (Team 11) '01-'05 :
-2005 New Jersey Regional Chairman's Award Winners
-2013 MORT Hall of Fame Inductee

NUTRONs (Team 125) '05-???
2007 Boston Regional Winners
2008 & 2009 Boston Regional Driving Tomorrow's Technology Award
2010 Boston Regional Creativity Award
2011 Bayou Regional Finalists, Innovation in Control Award, Boston Regional Finalists, Industrial Design Award
2012 New York City Regional Winners, Boston Regional Finalists, IRI Mentor of the Year
2013 Orlando Regional Finalists, Industrial Design Award, Boston Regional Winners, Pine Tree Regional Finalists
2014 Rhode Island District Winners, Excellence in Engineering Award, Northeastern University District Winners, Industrial Design Award, Pine Tree District Chairman's Award, Pine Tree District Winners
2015 South Florida Regional Chairman's Award, NU District Winners, NEDCMP Industrial Design Award, Hopper Division Finalists, Hopper/Newton Gracious Professionalism Award
  #18   Spotlight this post!  
Unread 14-11-2012, 18:12
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,906
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Driver Station + Space Bar

Quote:
Originally Posted by Tom Line View Post
As far as I know, E-stop stops all code execution, while disable does not.
Neither one actually stops code execution on the cRIO.
The user code continues to hum along blissfully.
I just tested it to make sure.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 14-11-2012 at 18:18.
  #19   Spotlight this post!  
Unread 14-11-2012, 18:22
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,756
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Driver Station + Space Bar

Estop is simply a latched disable. Neither of them bother to abort user code, but instead they will both set outputs to safe values, ignoring user code settings. Sensors and other features continue to operate as normal. Ideally, estop would kill power, but that isn't something the system can easily achieve.

When FIRST stopped using the estop USB button, which wasn't a very robust button anyway, the decision was made to remap the buttons. Previously space disabled the robot, and I believe enter did as well. The estop button emitted ctl-shift-enter, so that combo would estop the robot no matter what keyboard it came from.

The new mapping is that enter disables and space estops. F1 will actually enable the robot, and while running will enumerate the joysticks again in case something came unplugged, etc.

As for another way to un-estop the robot, it has been discussed many times, and the folks who own the decision feel that it is very important to enforce good safety processes. Part of that process is to walk to the robot and give it a visual inspection after an estop. It is also good to give it some thought before you repeat the steps that led to an estop you are currently recovering from. If you are in such a hurry that an estop was necessary, perhaps that is too much of a hurry.

As for the value of estop when not in a competition? The argument is that this allows teams to learn about estop before an event. If, in a practice setting, you estop your robot, it is rather permanent -- ditto for the competition field. If a team became used to the inconsistent practice setup, perhaps even using this as a driving technique, that would be unfortunate. So, the controls are as consistent to the field conditions as budget will allow. If it were feasible to ship large red mushroom buttons or panic triggers or other equipment, that would also likely be a part of the practice and development setup as well.

Greg McKaskle
  #20   Spotlight this post!  
Unread 15-11-2012, 15:36
~Cory~'s Avatar
~Cory~ ~Cory~ is offline
Student
AKA: Cory Rypkema
FRC #0706
Team Role: Alumni
 
Join Date: Jan 2010
Rookie Year: 2010
Location: Worcester MA
Posts: 216
~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold~Cory~ is a splendid one to behold
Re: Driver Station + Space Bar

@Greg McKaskle

Interesting information on the F1 button and enumeration. Where did you find this info?

Also, I think the space bar estop is here to stay even if a budgeting allows for an external button like the ones on the field. From a safety perspective two buttons is better than one and the other this is the space bar can not easily be covered or accidentally be pressed by someone who is not at the controls. I know some teams in 2010 opted to cover their button so it would not be accidentally be pressed. This presents a huge safety hazard.
__________________
corin.rypkema.org
WPI Class of '17
'12 Dean's List Finalist, Mentor of 706 - Cyberhawks
  #21   Spotlight this post!  
Unread 15-11-2012, 16:03
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Driver Station + Space Bar

Quote:
Originally Posted by ~Cory~ View Post
Interesting information on the F1 button and enumeration. Where did you find this info?
Lore, word of mouth, oral tradition, and several years of intimate familiarity with the control system.

Oh, and it's described in both the "Getting Started with the 2012 FRC Control System" document and the FMS White Paper. I'm sure it was in one of the 2011 setup documents too. Someone on each team should have read those, right?
  #22   Spotlight this post!  
Unread 15-11-2012, 16:05
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,756
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Driver Station + Space Bar

"Where did you find this info?" From a reliable source of course.

If an external estop is detectable, it could be used as a key -- the robot wouldn't run without it. At that point I'm pretty sure you could have the space bar back.

Greg McKaskle
  #23   Spotlight this post!  
Unread 16-11-2012, 16:38
SuperS_5's Avatar
SuperS_5 SuperS_5 is offline
[Certified LabVIEW Developer]
FRC #1219
 
Join Date: Dec 2010
Rookie Year: 2010
Location: Canada
Posts: 140
SuperS_5 will become famous soon enoughSuperS_5 will become famous soon enough
Re: Driver Station + Space Bar

While I would like 1+ external e-stops, I wouldn't want to remove the spacebar as one. There would be no guarantee that an external e-stop is anywhere near the person that is enabling the robot. (As even USB buttons could be on long extensions, or under the table, etc.) I think the current use of the spacebar is the most appropriate as an e-stop even with the reintroduction of external e-stops.

Sent from my AT100 Using ForumTouch for Android
Closed Thread


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 02:24.

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