Mirror/betaflight
1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-25 01:05:27 +03:00
Code Issues Wiki Activity

Update LED strip code to allow configurable LED strips.

Browse source 
See documentation for details.
This commit is contained in:
Dominic Clifton 2014-09-14 21:40:20 +01:00
parent 3ef769bf7b
commit 6ce5736990
17 changed files with 983 additions and 236 deletions
Download patch file Download diff file Expand all files Collapse all files

226
docs/LedStrip.md
View file

@ -7,6 +7,7 @@ require that all the LEDs in the strip show the same color.
Addressable LED strips can be used to show information from the flight controller system, the current implementation
supports the following:
* Up to 32 LEDs.
* Indicators showing pitch/roll stick positions.
* Heading/Orientation lights.
* Flight mode specific color schemes.
@ -17,12 +18,12 @@ The function and orientation configuration is fixed for now but later it should
In the future, if someone codes it, they could be used to show GPS navigation status, thrust levels, RSSI, etc.
Lots of scope for ideas and improvements.
Likewise, support for more than 28 LEDs is possible, it just requires additional development.
Likewise, support for more than 32 LEDs is possible, it just requires additional development.
## Supported hardware
Only strips of 28 WS2812 LEDs are supported currently. If the strip is longer than 28 leds it does not matter,
but only the first 28 are used.
Only strips of 32 WS2812 LEDs are supported currently. If the strip is longer than 32 leds it does not matter,
but only the first 32 are used.
WS2812 LEDs require an 800khz signal and precise timings and thus requires the use of a dedicated hardware timer.
@ -42,24 +43,220 @@ uses. e.g. ESC1/BEC1 -> FC, ESC2/BEC2 -> LED strip. It's also possible to pow
from another BEC. Just ensure that the GROUND is the same for all BEC outputs and LEDs.
| Target | Pin | Led Strip |
| --------------------- | --- | --------- |
| Naze/Olimexino | RC5 | Data In |
| ChebuzzF3/F3Discovery | PB8 | Data In |
| Target | Pin | Led Strip | Signal |
| --------------------- | --- | --------- | -------|
| Naze/Olimexino | RC5 | Data In | PA6 |
| CC3D | ??? | Data In | PB4 |
| ChebuzzF3/F3Discovery | PB8 | Data In | PB8 |
Since RC5 is also used for SoftSerial on the Naze/Olimexino it means that you cannot use softserial and led strips at the same time.
Additionally, since RC5 is also used for Parallel PWM RC input on both the Naze, Chebuzz and STM32F3Discovery targets, led strips
can not be used at the same time at Parallel PWM.
## Configuration
Enable the `LED_STRIP` feature via the cli:
```
feature LED_STRIP
```
If you enable LED_STRIP feature and the feature is turned off again after a reboot then check your config does not conflict with other features, as above.
Configure the LEDs using the `led` command.
The `led` command takes either zero or two arguments - an zero-based led number and a pair of coordinates, direction flags and mode flags.
If used with zero arguments it prints out the led configuration which can be copied for future reference.
Each led is configured using the following template: `x,y:ddd:mmm`
`x` and `y` are grid coordinates of a 0 based 16x16 grid, north west is 0,0, south east is 15,15
`ddd` specifies the directions, since an led can face in any direction it can have multiple directions. Directions are:
`N` - North
`E` - East
`S` - South
`W` - West
`U` - Up
`D` - Down
For instance, an LED that faces South-east at a 45 degree downwards angle could be configured as `SED`.
Note: It is perfectly possible to configure an LED to have all directions `NESWUD` but probably doesn't make sense.
`mmm` specifies the modes that should be applied an LED. Modes are:
* `B` - `B`attery warning.
* `F` - `F`light mode & Orientation
* `I` - `I`ndicator.
* `A` - `A`rmed state.
Example:
```
led 0 0,15:SD:IAB
led 1 15,0:ND:IA
led 2 0,0:ND:IAB
led 3 0,15:SD:IAB
```
to erase an led, and to mark the end of the chain, use `0,0::` as the second argument, like this:
```
led 4 0,0::
```
### Modes
#### Battery Warning
This mode simply flashes the LED RED when the battery is low if battery monitoring is enabled.
#### Flight Mode & Orientation
This mode shows the flight mode and orientation.
When flight modes are active then the leds are updated to show different colors depending on the mode, placement on the grid and direction.
Leds are set in a specific order:
* Leds that marked as facing up or down.
* Leds that marked as facing west or east AND are on the west or east side of the grid.
* Leds that marked as facing north or south AND are on the north or south side of the grid.
That is, south facing leds have priority.
#### Indicator
This mode flashes LEDs that correspond to roll and pitch stick positions. i.e. they indicate the direction the craft is going to turn.
#### Armed state
This mode toggles LEDs between green and blue when disarmed and armed, respectively.
Note: Armed State cannot be used with Flight Mode.
## Positioning
Cut the strip into 5 sections as per diagram below. When the strips are cut ensure you reconnect each output to each input with cable where the break is made.
Cut the strip into sections as per diagrams below. When the strips are cut ensure you reconnect each output to each input with cable where the break is made.
e.g. connect 5V out to 5V in, GND to GND and Data Out to Data In.
Orientation is when viewed with the front of the aircraft facing away from you and viewed from above.
LED numbers and positions for a quad.
### Example 12 LED config
The default configuration is as follows
```
led 0 2,2:ES:IA
led 1 2,1:E:BF
led 2 2,0:NE:IA
led 3 1,0:N:BF
led 4 0,0:NW:IA
led 5 0,1:W:BF
led 6 0,2:SW:IA
led 7 1,2:S:BF
led 8 1,1:U:BF
led 9 1,1:U:BF
led 10 1,1:D:BF
led 11 1,1:D:BF
```
Which translates into the following positions:
```
5 3
\ /
\ 4 /
\ FRONT /
6 | 9-12 | 2
/ BACK \
/ 8 \
/ \
7 1
```
LEDs 1,3,5 and 7 should be placed underneath the quad, facing downwards.
LEDs 2, 4, 6 and 8 should be positioned so the face east/north/west/south, respectively.
LEDs 9-10 should be placed facing down, in the middle
LEDs 11-12 should be placed facing up, in the middle
This is the default so that if you don't want to place LEDs top and bottom in the middle just connect the first 8 leds.
### Example 16 LED config
```
15,15:SD:IA
8,8:E:FB
8,7:E:FB
15,0:ND:IA
7,7:N:FB
8,7:N:FB
0,0:ND:IA
7,7:W:FB
7,8:W:FB
0,15:SD:IA
7,8:S:FB
8,8:S:FB
7,7:D:FB
8,7:D:FB
7,7:U:FB
8,7:U:FB
```
Which translates into the following positions:
```
7 4
\ /
\ 6-5 /
8 \ FRONT / 3
| 13-16 |
9 / BACK \ 2
/ 11-12 \
/ \
10 1
```
LEDs 1,4,7 and 10 should be placed underneath the quad, facing downwards.
LEDs 2-3, 6-5, 8-9 and 11-12 should be positioned so the face east/north/west/south, respectively.
LEDs 13-14 should be placed facing down, in the middle
LEDs 15-16 should be placed facing up, in the middle
### Exmple 28 LED config
```
9,9:S:FB
10,10:S:FB
11,11:S:IA
11,11:E:IA
10,10:E:F
9,9:E:F
10,5:S:F
11,4:S:F
12,3:S:IA
12,2:N:IA
11,1:N:F
10,0:N:F
7,0:N:FB
6,0:N:FB
5,0:N:FB
4,0:N:FB
2,0:N:F
1,1:N:F
0,2:N:IA
0,3:W:IA
1,4:W:F
2,5:W:F
2,9:W:F
1,10:W:F
0,11:W:IA
0,11:S:IA
1,10:S:FB
2,9:S:FB
```
```
17-19 10-12
@ -72,15 +269,12 @@ LED numbers and positions for a quad.
26-28 1-3
```
## Configuration
All LEDs should face outwards from the chassis in this configuration.
Enable the `LED_STRIP` feature via the cli:
Note:
This configuration is specifically designed for the Alien Spider AQ50D PRO 250mm frame.
```
feature LED_STRIP
```
If you enable LED_STRIP feature and the feature is turned off again after a reboot then check your config does not conflict with other features, as above.
http://www.goodluckbuy.com/alien-spider-aq50d-pro-250mm-mini-quadcopter-carbon-fiber-micro-multicopter-frame.html
## Troubleshooting