• At power up the LED will fade in green over a period of 2s
• During normal operation it will be blue, fading in and out every second
• When a communication packet addressed to this board is received the LED will be green
  • Packets addressed to a slave will not make the LED turn green (ex.: Plan is connected to Manage over USB, and Manage is connected to Execute over RS-485. Addressing Execute from the Plan GUI will turn Execute's LED green, but not Manage's)
  • The green color is latched for around 1s. Getting packets at >= 1Hz will keep it green.

• Three colors are used to indicate what power source is present:
  • Green: battery voltage is in the programmed range.
  • Aqua: USB powered.
  • Orange: unknown power-supply. Typically seen with bad USB hubs and/or cables.
  • The Low Voltage Protection (UVLO) page has a graphical representation of the states & colors.
• With the pushbutton pressed, the LED will fade in green or aqua over a period of 2s
• If all the safety checks pass, it will start blinking at that same color until the pushbutton is released
• If errors are detected, it will blink red. As soon as the pushbutton is released the circuit will power off.
• During normal operation it will be green or aqua, fading in and out every second
• A brief press will turn the LED magenta as a confirmation that the software has registered the user input. This can be used to start experiment or to switch mode or control policies.
• If the pushbutton is pressed, the led will start fading red.
  • If released before it starts blinking, the board will revert to the previous operating mode.
  • If held until it starts blinking, the board will power off as soon as released.

• A yellow LED indicates a warning.
• A red LED indicates a major error, such as a hardfault or a temperature out of range. In most cases, the board will not be functional at this point.

Some circuits (Execute, Rigid, Pocket, etc.) have a bank of green LEDs indicating the status of each power supply. In some occasions the silkscreen will indicate which is which, but in other cases the user will have to refer to the schematic and PCB layout files. These LEDs are only used to diagnose power issues, or broken circuitry. In normal operation, with a battery or a power supply connected, all LEDs should be on, with a similar intensity. Seeing one or two of them off is a sign that the circuit is powered by USB, that it's not turned ON, or that something is broken (fuse, or voltage regulator).

Each RN-42 Bluetooth module has two LEDs (one green, one red). The list below covers the typical patterns seen on our products. Please refer to the module's documentation for all the details.

• No LEDs: no power, or held in reset by a microcontroller
• Slow-blinking green LED: module not connected to a computer or to another Bluetooth module.
• Steady green: module is paired.
• Fast-blinking green: module is in Configuration mode.
• Red:
  • It will blink in bursts during a module's configuration
  • It will pulse when new data is received and the module hasn't been configured yet.

• Some circuits, or sections of circuits, have green or red LEDs. Please refer to their page for more information.
• The RGB LED we typically expose (via a light pipe, or a hole in an enclosure) is Regulate's.