|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Numpad on Driver Station?
Quote:
|
|
#2
|
|||||
|
|||||
|
Re: Numpad on Driver Station?
Quote:
Note: This is a serious question, not sarcastic. Last edited by Vikesrock : 22-01-2011 at 18:54. |
|
#3
|
|||
|
|||
|
Re: Numpad on Driver Station?
This has nothing to do with code-writing. If I want some new input device, I have to buy something to use it, and probably some new hardware. If they'd remove rule 75, there'd be no problem (in relation to this post, he'd be able to use his numpad). Just have an inspector verify that nothing has a chance to move during the disabled stage (and no one would probably set it up this way, due to obvious reasons...)
|
|
#4
|
|||||
|
|||||
|
Re: Numpad on Driver Station?
A device driver is software that you write. You don't have to buy anything as far as I am aware.
|
|
#5
|
|||
|
|||
|
Re: Numpad on Driver Station?
If he wanted to use a numpad/keyboard, he'd have to buy a USB encoder and interface it to the encoder. And perhaps I wish to pre-interpret my USB device's data? There's no provisions for sending it to the robot after that.
|
|
#6
|
|||
|
|||
|
Re: Numpad on Driver Station?
Even if you could find an inspector with the time, you would need a field to show him/her that. Pretty much every regional I've ever been to, the practice and competition fields are booked quite solid.
|
|
#7
|
|||
|
|||
|
Re: Numpad on Driver Station?
It would be nice to test it in a field environment, but why wouldn't putting it on blocks and making sure the arm, etc, are cleared not be enough (and run it through a practice round)?
Sure, it could potentially be dangerous, but as long as no one's in the way and it can't move, it's just as good (they shouldn't have an insanely wide reach, anyway). |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|