Quote:
Originally Posted by Chris Hibner
And Dave: don't you guys have the STOP button?
|
Sure we do, and it is a perfectly valid way to stop the robot. My problem with it is if you press the STOP button you have to power cycle the robot to get it running again. If the STOP button mimicked the old disable switch I'd be perfectly happy.
Quote:
|
Also, the spacebar works as a fast disable, but you have to train yourself to do it so you don't forget when the important time comes.
|
I was unaware of that. That's good to know.
Quote:
|
Originally Posted by Greg McKaskle
BTW, I don't get the distinction between suggestion one and two.
|
Suggestion 1 was coming from a use case where I run autonomous, then disable, then reenable without changing to teleop. Our team protects against running accidental autonomous, but there are a lot of teams that don't.
Suggestion 2 was coming from the initialization standpoint. If the last operation from the DS was to run autonomous, it is very easy to forget to change the state back to teleop. My point here was to default to teleop-disabled on startup (or initial link connection)
We have taken preventative measures on our end to try to make our robot as safe as possible with the way things currently work. I'm more worried about the teams that don't. It's far too easy to enable without looking at the run mode.