|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Using a different button to e-stop the robot instead of the space key
I was wondering if there was anyway of changing the emergency stop key of the driver station to some thing other than the space key. The point of this is to allow driving and programming to be done on the same laptop so we can easily tweak values without having to disable, deploy, and then re-enable. Are there any easy ways of doing this, or would it be better to create our own driver station? Disabling the robot to deploy code is not an option in our case. Thank you.
|
|
#2
|
|||||
|
|||||
|
Re: Using a different button to e-stop the robot instead of the space key
Quote:
|
|
#3
|
|||||
|
|||||
|
Re: Using a different button to e-stop the robot instead of the space key
If you are just tweaking values, you might find it faster and more convenient to use Smart Dashboard variables instead of changing the program each time. Once you have found the value you want, then you can put it in the code.
The robot is going to disable itself anyway when you load new code. Why isn't it possible for you to disable it a few moments earlier? |
|
#4
|
||||
|
||||
|
Re: Using a different button to e-stop the robot instead of the space key
I am not sure if the space bar estop's the bot when it is disabled, but the point (I assume) is Estop requires a power cycle to reset. At least it did on the Crios. Which means you can't edit code while the DS is connected to the robot without causing a Estop?
Not quite as annoying, but you have to remember not so use the enter (Disable) key while changing smart dashboard values. Last edited by FrankJ : 09-10-2015 at 14:30. |
|
#5
|
|||
|
|||
|
Re: Using a different button to e-stop the robot instead of the space key
Quote:
|
|
#6
|
|||
|
|||
|
Re: Using a different button to e-stop the robot instead of the space key
The driver station intentionally does not allow for a different key to be used for estop.
If each team or each computer used a different key, it would be unclear how to stop a runaway FRC robot. Similarly, other keys are not allowed to be remapped either. The DS will not estop a disabled robot, only an enabled one. If you are changing code while the robot runs, it is even more important that you have a reliable estop. And it is important that others around the robot know how to stop it -- in case the robot has you pinned against a wall or something. So it is somewhat inconvenient to have an estop button that is easy to press. Safety mechanisms are almost always at odds with convenience and efficiency, but fingers don't grow back, FIRST doesn't give awards for best robot scars, etc. If you do use an alternate DS, be sure you can trust its estop and make sure it is well known to those operating the robot. My suggestion is to use a dedicated laptop for the DS and a second, programming laptop, both networked to the robot. Greg McKaskle |
|
#7
|
||||
|
||||
|
Re: Using a different button to e-stop the robot instead of the space key
It may not be the best solution, but you can copy and paste a space every time you need it.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|