Move new ledboard recipes to advanced page

This commit is contained in:
Ben Nuttall
2017-07-26 18:51:35 +01:00
parent 42de063ac3
commit bebae8116c
4 changed files with 53 additions and 48 deletions

View File

@@ -1,9 +1,8 @@
from gpiozero import LEDBoard
from time import sleep
from signal import pause
leds = LEDBoard(5, 6, 13, 19, 26)
leds = LEDBoard(5, 6, 13, 19, 26, pwm=True)
for led in leds:
led.on()
sleep(1)
led.off()
leds.value = (0.2, 0.4, 0.6, 0.8, 1.0)
pause()

View File

@@ -1,8 +1,9 @@
from gpiozero import LEDBoard
from signal import pause
from time import sleep
leds = LEDBoard(5, 6, 13, 19, 26, pwm=True)
leds = LEDBoard(5, 6, 13, 19, 26)
leds.value = (0.2, 0.4, 0.6, 0.8, 1.0)
pause()
for led in leds:
led.on()
sleep(1)
led.off()

View File

@@ -162,34 +162,12 @@ A collection of LEDs can be accessed using :class:`LEDBoard`:
.. literalinclude:: examples/led_board_1.py
You can also iterate over the LEDs one-by-one:
.. literalinclude:: examples/led_board_2.py
Using :class:`LEDBoard` with ``pwm=True`` allows each LED's brightness to be
controlled:
.. literalinclude:: examples/led_board_3.py
.. literalinclude:: examples/led_board_2.py
:class:`LEDBoard` also supports indexing. This means you can access the
individual :class:`LED` objects using ``leds[i]`` where ``i`` is an integer
from 0 up to (not including) the number of LEDs:
.. literalinclude:: examples/led_board_4.py
This also means you can use slicing to access a subset of the LEDs:
.. literalinclude:: examples/led_board_5.py
:class:`LEDBoard` objects can have their `LED` objects named upon construction.
This means the individual LEDs can be accessed by their name:
.. literalinclude:: examples/led_board_6.py
:class:`LEDBoard` objects can also be nested to contain other :class:`LEDBoard`
objects:
.. literalinclude:: examples/led_board_7.py
See more :class:`LEDBoard` examples in :doc:`recipes_advanced`.
LEDBarGraph
===========

View File

@@ -8,6 +8,46 @@ The following recipes demonstrate some of the capabilities of the GPIO Zero
library. Please note that all recipes are written assuming Python 3. Recipes
*may* work under Python 2, but no guarantees!
LEDBoard
========
You can iterate over the LEDs in a :class:`LEDBoard` object one-by-one:
.. literalinclude:: examples/led_board_3.py
:class:`LEDBoard` also supports indexing. This means you can access the
individual :class:`LED` objects using ``leds[i]`` where ``i`` is an integer
from 0 up to (not including) the number of LEDs:
.. literalinclude:: examples/led_board_4.py
This also means you can use slicing to access a subset of the LEDs:
.. literalinclude:: examples/led_board_5.py
:class:`LEDBoard` objects can have their `LED` objects named upon construction.
This means the individual LEDs can be accessed by their name:
.. literalinclude:: examples/led_board_6.py
:class:`LEDBoard` objects can also be nested within other :class:`LEDBoard`
objects:
.. literalinclude:: examples/led_board_7.py
Who's home indicator
====================
Using a number of green-red LED pairs, you can show the status of who's home,
according to which IP addresses you can ping successfully. Note that this
assumes each person's mobile phone has a reserved IP address on the home router.
.. literalinclude:: examples/whos_home_leds.py
Alternatively, using the `STATUS Zero`_ board:
.. literalinclude:: examples/whos_home_status.py
Travis build LED indicator
==========================
@@ -28,19 +68,6 @@ a Bee-Bot or Turtle robot.
.. literalinclude:: examples/robot_buttons_2.py
Who's home indicator
====================
Using a number of green-red LED pairs, you can show the status of who's home,
according to which IP addresses you can ping successfully. Note that this
assumes each person's mobile phone has a reserved IP address on the home router.
.. literalinclude:: examples/whos_home_leds.py
Alternatively, using the `STATUS Zero`_ board:
.. literalinclude:: examples/whos_home_status.py
Robot controlled by 2 potentiometers
====================================