Skip to content
Binnur Al-Kazily edited this page Jan 24, 2020 · 4 revisions

IMPORTANT: In-progress stream of thoughts and comments I have gathered from communications... Feel free to add to this raw stream.

Document objective: compile requirements and prioritized work objective for robot bling.

WPILib and Addressable LEDs

Refer to WPILib documentation for configuring addressable LEDs and recommended practice for setting LED data. WPILib Addressable LEDs Documentation

Why Robot Bling?

Robot bling is not only entertaining but can be a useful tool during matches as a visual indicator to the driver for critical information.

Robot States and Bling Support

Note: this is a brainstorm list, we need to review & prioritize.

  • Robot is ready for operation -- ex. robotinit indicating all subsystems are functioning
  • Autonomous period
  • Shield Generation stage -- reported by the FMS. Bling to reflect on the different states (both stage readiness and its rotation completeness), such as the color required for activation of the Control Panel
  • Endgame
  • Vision target acquired
  • Intake/indexer fully loaded
  • Automatic control to turn off bling -- to minimize potential interference, such as Control Panel color reading
  • Climb victory bling

Draft: Robot+Bling States and Events

This is a rough start to outlining different states and transitions for bling integration with robot code. robot+bling states

Once finalized, write up a short requirements for each bling state. Example:

PoweredOn

  • Triggered by disabledInit() event
  • Animation pattern matches the robot signal light at disabledInit() == solid ORANGE
  • At start of robot code, it will move to the default animation