| E-Paper Driver HAT
|
Universal e-Paper Driver HAT, supports various Waveshare SPI e-Paper raw panels
|
|
|
|
|
|
|
Description
|
|
|
| Features
|
---
|
| Interfaces
|
SPI
|
|
|
|
|
|
Introduction
Universal e-Paper Driver HAT, supports various Waveshare SPI interface e-Paper raw panels
Interfaces
| VCC |
3.3V
|
| GND |
GND
|
| DIN |
SPI MOSI pin
|
| CLK |
SPI SCK pin
|
| CS |
SPI chip select (low active)
|
| DC |
Data/Command control pin (high for data, and low for command)
|
| RST |
External reset pin (low active)
|
| BUSY |
Busy state output pin (low active)
|
Switch settings
There are two switches on the front panel of Drive HAT: Display Config and Interface Config.
Display Config Switch
The Display Config switch on e-Paper Driver HAT is made for being compatible with various SPI interface e-Ink raw panels from Waveshare. This switch has A and B sides. For connecting to different e-Paper raw panels, you can set the Display Config switch refer to the table below:
Interface Config Switch
With Interface Config, you can change the SPI interface of e-Paper to 3-lin SPI or 4-line SPI
| Switch to 0 |
Switch to 1
|
| 4-line SPI |
3-line SPI
|
Note: Examples we provide use 4-line SPI by default
Example for 7.5inch e-Paper Switch Settings
Connecting the e-Paper Driver HAT to 7.5inch e-Paper, we must switch the Display Config to B according to the Display Config table above, and set the Interface Config to 0 to make the e-Paper work on 4-line SPI mode.
How to use
Working with Raspberry Pi
Installing libraries required
If you want to connect your E-paper screen to Raspberry Pi, you should install some necessary libraries, or else the Demo below may work improperly. For more information about how to install the Raspberry Pi libraries, please visit the website: Libraries Installation for RPi, where you can find the detailed presentation about the installations of libraries wiringPi, bcm2835 and python.
Hardware connection
Here is the connection between Raspberry Pi 3B and E-paper (BCM).
| e-Paper |
Raspberry Pi 3B
|
| 3.3V |
3.3V
|
| GND |
GND
|
| DIN |
MOSI
|
| CLK |
SCLK
|
| CS |
CE0
|
| DC |
25 (BCM)
|
| RST |
17 (BCM)
|
| BUSY |
24 (BCM)
|
Expected result
1) After the corresponding libraries installed, you can copy the relative programs into your Raspberry Pi, and then enter the corresponding file.
- BCM2835: Execute the command: make, to compile the code and generate a file epd. Execute the command: sudo ./epd, the program will run.
- WringPi: Execute the command: make, to compile the code and generate a file epd. Execute the command: sudo ./epd, the program will run.
- Python: Execute the command: sudo python main.py
2) Image will be displayed on the screen.
- Note：The refresh rate of this module is slow, and it will flicker for several times during refreshing. Please be patient.
Working with Arduino
Hardware connection
| e-Paper |
Arduino UNO
|
| 3.3V |
3V3
|
| GND |
GND
|
| DIN |
D11
|
| CLK |
D13
|
| CS |
D10
|
| DC |
D9
|
| RST |
D8
|
| BUSY |
D7
|
Expected result
- Copy the libraries file of Arduino demo code to the libraries folder which is under the installation directory of Arduino IDE, it usually is C:\users\username\documents\arduino\libraries. You can also designate the location on Arduino IDE--> File -->Preferences -->Sketchbook location
- Upload the project.
- E-paper will display the image.
Note:
- The refresh rate of this module is slow, and it will flicker for several times during refreshing. Please be patient.
Working with the STM32 development board
- Here we use STM32F103ZE development board or NUCLEO-F103RB. (The demo code of 1.54inch/2.13inch/2.9inch e-Paper are based on NUCLEO-F103RB,
Others are based on STM32F103ZE)
- The demo code is based on HAL, so you can port the demo code to other STM boards with STM32CubeMX.
- The demo code can be compiled successfully in Keil v5
Hardware connection
Connecting to the STM32F103ZE:
| e-Paper |
STM32F103ZE
|
| 3.3V |
3V3
|
| GND |
GND
|
| DIN |
PA7 (MOSI)
|
| CLK |
PA5 (SCK)
|
| CS |
PA4
|
| DC |
PA2
|
| RST |
PA1
|
| BUSY |
PA3
|
Connecting to the NUCLEO-F103RB:
| e-Paper |
NUCLEO-F103RB
|
| 3.3V |
3V3
|
| GND |
GND
|
| DIN |
PA7
|
| CLK |
PA5
|
| CS |
PB6
|
| DC |
PC7
|
| RST |
PA9
|
| BUSY |
PA8
|
Expected result
- Open the project (epd-demo.uvprojx), which is under the MDK-ARM directory.
- Click Build to compile the project.
- Click Download to load the code to your board.
- Reset, the screen will display image.
- Note: The refresh rate of this module is slow, and it will flicker for several times during refreshing. Please be patient.
Resources
Documentation
Related Resources
e-Paper
FAQ
FAQ
| Question:
|
| Working requirements of e-Paper?
|
|
| Answer:
|
- Two-color B/W e-paper
- 【Working】Temperature: 0~50°C; Humidity: 35%~65%RH
- 【Storage】Temperature: ≤30°C; Humidity: ≤55%RH; Max storage time: 6 months
- 【Transport】Temperature: -25~70°C; Max transport time: 10 days
- 【Unpack】Temperature: 20°C±5°C; Humidity: 50%RH±5%RH; Max storage time: Should be assembled in 72h
- Three-Color e-Paper
- 【Working】Temperature: 0~40°C; Humidity: 35%~65%RH
- 【Storage】Temperature: ≤30°C; Humidity: ≤55%RH; Max storage time: 3 months
- 【Transport】Temperature: -25~60°C; Max transport time: 10 days
- 【Unpack】Temperature: 20°C±5°C; Humidity: 50%RH±5%RH; Max storage time: Should be assembled in 72h
When store three-color e-Paper, please refresh it to white, and keep the screen upward. Note that you need to update it at least every three months.
|
|
| Question:
|
| What do you need to note about e-Paper refreshing?
|
|
| Answer:
|
- Refresh mode
- Full refresh: e-Paper flicker when full refreshing to remove ghost image for best display.
- Partial refresh: It don't flicker if you use partial refresh (only some of the two-color e-paper support partial refresh). Note that you cannot use Partial refresh all the time, you should full refresh e-paper regularly, otherwise, ghost problem will get worse even damage.
- Refresh rate
- When using, you should set the update interval at least 180s.(except Partial supportable types)
- Please set the e-Paper to sleep mode or power off it directly, otherwise, the e-Paper is damaged because of working in high voltage for long time.
- You need to update the content of three-color e-Paper at least one time every 24h to avoid from burn-in problem.
- Working place
- We recommend you to use the e-Paper indoor. If you need to set the e-paper outdoor, Please place the e-paper in shadow and protect it from UV. When you designed you e-paper product, you should take care about the working situation like temperature, humidity, etc.
|
|
| Question:
|
| How much could the flexible e-paper be bended
|
|
| Answer:
|
- The IC part of e-Paper cannot be bended, you can bend the display area in degree larger than 60°C
|
|
| Question:
|
| Why the e-Paper cant work with Arduino?
|
|
| Answer:
|
|
The I/O level of Arduino is 5V, and the e-Paper should be driven with 3V3. If your Arduino cant drive the e-Paper successfully, please try to convert the level to 3.3V
You can also try to connect the Vcc pin to the 5V of Arduino to see whether the e-Paper works, but we recommend you not to use 5V for a long time.
|
|
| Question:
|
| Why does the color of e-Paper look a little black or grey?
|
|
| Answer:
|
|
You can try to change the value of Vcom on demo codes.
|
|
| Question:
|
| Three-color e-paper looks more red/yellow than the picture on website?
|
|
| Answer:
|
|
Because of different batch, some of them have aberration. Store the e-Paper right side up will reduce it. And if the e-Paper didn't be refreshed for long time, it will become more and more red/yellow. Please use the demo code to refresh the e-paper for several times in this case.
|
|
| Question:
|
| Why my e-paper has ghosting problem after working for some days
|
|
| Answer:
|
|
Please set the e-paper to sleep mode or disconnect it if you needn't refresh the e-paper but need to power on your development board or Raspberry Pi for long time.Otherwise, the voltage of panel keeps high and it will damage the panel
|
|
| Question:
|
| Why the FPC of the e-Paper is broken after using for some times?
|
|
| Answer:
|
| Please make sure you have used it in correct way.
|
|
Support
|
Contact us
Working hours: 09:00-18:00 (UTC+8 Monday to Saturday)
|
|
