changeset 36:2a8e173f255d

More details about the shields
author Radomir Dopieralski <sheep-devel@sheep.art.pl>
date Tue, 02 Aug 2016 18:35:07 +0200
parents 1331b186add8
children f190fd4d471c
files shields.rst
diffstat 1 files changed, 21 insertions(+), 11 deletions(-) [+]
line wrap: on
line diff
--- a/shields.rst	Tue Aug 02 18:12:09 2016 +0200
+++ b/shields.rst	Tue Aug 02 18:35:07 2016 +0200
@@ -43,7 +43,11 @@
     print(sensor.temperature())
     print(sensor.humidity())
 
-(Use DHT22 class for the DHT Pro shield.)
+(Use ``DHT22`` class for the DHT Pro shield.)
+
+It is recommended to use this shield with the "dual base", so that the
+temperature sensor is not right above or below the ESP8266 module, which tends
+to become warm during work and can affect temperature measurements.
 
 
 Neopixel
@@ -51,7 +55,7 @@
 
 That shield has a single addressable RGB LED on it, connected to pin ``gpio4``.
 Unfortunately, that means that this shield conflicts with any other shield that
-uses the I2C protocol, such as the OLED shield or the motor shield. You can use
+uses the I²C protocol, such as the OLED shield or the motor shield. You can use
 it with code lik this::
 
     form machine import Pin
@@ -67,7 +71,7 @@
 This shield contains a relay switch, together with a transistor and a couple of
 other components required to reliably connect it to the board. It uses pin
 ``gpio5``, which unfortunately makes it incompatible with any other shields
-using the I2C protocol, such as the OLED shield or the motor shield. You can
+using the I²C protocol, such as the OLED shield or the motor shield. You can
 control the relay with the following code::
 
     from machine import Pin
@@ -80,11 +84,14 @@
 ====
 
 A small, 64×48 monochrome display. It uses pins ``gpio4`` and ``gpio5`` to talk
-with the board with the I2C protocol. It will conflict with any other shield
-that uses those pins, but doesn't use I2C, like the neopixel shield or the
-relay shield. It can coexist with other shields that use I2C, like the motor
+with the board with the I²C protocol. It will conflict with any other shield
+that uses those pins, but doesn't use I²C, like the neopixel shield or the
+relay shield. It can coexist with other shields that use I²C, like the motor
 shield.
 
+Up to two such displays can be connected at the same time, provided they have
+different addresses set using the jumper on the back.
+
 You can control the display using the ``ssd1306`` library::
 
     import ssd1306
@@ -100,10 +107,11 @@
 Motor
 =====
 
-The motor shield contains a DC motor driver (an H-bridge), and a PWM chip. You
-can control it using I2C on pins ``gpio4`` and ``gpio5``. It will conflict with
-any shields that use those pins but don't use I2C, such as the relay shield and
-the neopixel shield. It will work well together with other shields using I2C.
+The motor shield contains a H-bridge) and a PWM chip, and it's able to drive up
+to two small DC motors. You can control it using I²C on pins ``gpio4`` and
+``gpio5``. It will conflict with any shields that use those pins but don't use
+I²C, such as the relay shield and the neopixel shield. It will work well
+together with other shields using I²C.
 
 At the moment there is no ready-to-use library to control this shield.
 
@@ -112,7 +120,9 @@
 ========
 
 This shield lets you connect a micro SD card to your board. It connects to pins
-``gpio12``, ``gpio13``, ``gpio14`` and ``gpio15`` and uses SPI protocol.
+``gpio12``, ``gpio13``, ``gpio14`` and ``gpio15`` and uses SPI protocol. It can
+be used together with other devices using the SPI protocol, as long as they
+don't use pin ``gpio15`` as CS.
 
 At the moment there is no ready-to-use library that would let you use this
 shield.