-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TI Launchpad / Operator Console core #89
base: master
Are you sure you want to change the base?
Conversation
@agausmann @Zabot, let me know if we should merge this now or wait until after competition. |
Just to add my two cents, I am a little (LOT) worried that the Adafruit push buttons may not hold up in competition. So we can use the buttons, but need to be prepared to use joystick as a backup. Considering the late turn around on the button panel, I'd prefer we label joystick buttons and go that route. Nick seems to have that well in hand, so why change a good thing... RJ On Wednesday, March 18, 2015 9:03 AM, Randall Hauch [email protected] wrote: @agausmann @Zabot, let me know if we should merge this now or wait until after competition. |
I do not know if we will have time to merge this and get it fully working. If we intend to use the new migrated framework during competition, we may want to wait to merge this because GitHub says there are a few conflicts between the two branches. |
Additions:
OperatorConsole
input device with digital/analog I/O corresponding to the button panel on the console.SwitchWithIndicator
which abstracts a switch with an indicator LED or similar feedback device.oc
) toOperatorInterface
@Zabot - you'll need to integrate the new controls in the
OperatorInterface
. Each newSwitchWithIndicator
corresponds to the button and LED pair with the same label.