Quote:
|
Originally Posted by CronosPrime1
Well, I think I'll just wire several binary switches and ask the computer to compute values using binary. Like if I want to select between 4 things, I'll convert input from 2 binary switches to a number from 0-3, and attach a printed label sheet to the operator interface so my team members can know what's going on. No problem, I guess. Binary math is easy.
|
Binary math may be easy, but I'd avoid it on the OI.
Last season, I was field coach for 1293 during their short (two-match, if I recall) reign as #1 seed at Palmetto. I wasn't even doing the driving, and my mind had a million things going (time remaining, which goals were ours, which goals needed to be ours, is anyone in the loading zones, et cetera). Trying to throw in much of any sort of math would've had dire consequences.
The general thing you'll see on most OI panels is that they're simple. A driver should be able to judge what's going on by touch or a brief glance. This, in turn, gives them more time to figure out how to do more important things, like moving around those two 120-pound hunks of machinery blocking your path to the goal. (Of course, if your two switches corresponded to something visual on the robot, such as a left and right ball sucker, then by all means go for it.)
That said, binary is perfectly fine on the robot side for things like setting an autonomous mode. Even the most tense field coach in the world can figure that sort of thing out.
Hope this helps!