REV DUO Application Examples
Last updated
Last updated
One of the most common requests from Control Hub users is how to use the Blinkin to signal to a driver different actions the robot is performing. The basic code below walks through how to use the SDK to code the Blinkin to different actions. When a certain gamepad button is pressed the LED turns a solid color, if no buttons are pressed the LED defaults to the Beats Per Minute pattern with a Forest Pallette.
For information on the different patterns visit the LED Pattern Tables.
The Blinkin can run in a stand-alone operation mode when there is no way to generate a PWM signal, or a single output pattern is all that is needed. In this mode the Blinkin will be operating in Normal Mode with no input signal (blue blinking LED) and will default to the programmed no input signal pattern (factory setting is pattern 29 – Color Waves, Party Palette).
The currently displayed pattern can be changed at any time by pressing the up and down buttons to scroll through the pattern list. Unless a new default no signal test pattern is saved in memory by completing the setup mode process, the Blinkin will default back to the last saved pattern after a power cycle.
Connect to a 12V power source which can supply up to 5amps.
Select either a 12V or 5V LED strip.
Follow through Setup and Configuration to program to a default pattern.
Adding LEDs to your robot (or other project) can do more than just make them look cool, you can use LEDs to provide critical visual feedback. Here are some examples:
Program a controller button to change the LED output pattern (e.g. 85 – Solid Yellow) and the drive can use the LEDs to communicate to the human player at a portal station across the field that the robot is ready to receive a game object.
If the driver has poor visibility to see if the robot has acquired a game object, add a sensor to the intake and the LED strip can be programmed to automatically display a new pattern when the object is acquired. The driver never has to take their eyes off the robot to check the dashboard because the robot will clearly display its status.
Using the match time value available in software, the LEDs can be changes to a time warning pattern (e.g. – Solid Red) with X seconds left in a match.
The robot can display a different pattern when enabled vs disabled which provides a more visible indicator of the state of the robot than the RSL.