I have always wanted to make something for fun, and I happened to be inspired by the ink screen weather forecast made by duck, so I also planned to make a low-power personal display device. Considering low-power personal display devices, there is only Ink Screen, so we set the following goals:
vscode + esp-idf is used to write display-side programs keil + stm32 is used to write programs for power management chips python3 is used to write server-side calendar interfaces
[x] Schematic design [x] PCB diagram design [x] PCB proofing [x] Welding test [x] Functional test [x] Program test
The calendar is currently in use and uses a small 400mAh battery. Since updates are not very frequent, it can basically be charged once every six months. If you use a large battery, you basically don’t need to charge it, which meets the design requirements.
1. Ink screen driver The ink screen driver copies the v2 version of the circuit in the epdiy project on github. This circuit is relatively simple and relatively low-cost, but the low power consumption is higher (this will be discussed later). Otherwise, there are no shortcomings. The most important things in the circuit are the five voltages, which are +22V/+15V/-20V/-15V and vCal. The voltages of +22V and -20V are mainly generated by LT1945, and +15V/-15V are generated by two LDOs, 7815 and 7915. VoltageCalibarate is generated by LM358 and adjustable resistor, because it needs to be adjusted according to the actual screen parameters. For details, please see the following document: epdiy document 2. esp32 circuit In esp32, because the ink screen has more IO, 74HC4094D is used for IO expansion, and As a result, the quiescent current of the device remains high, so another low-power microcontroller is used for power management . 3. The power management circuit uses STM32L010 as the power management chip. This was bought before the price of the chip increased. At that time it was 2 yuan/piece, but now it’s hard to tell. The power management is relatively simple. The STM32L010 is always charged. It wakes up every 4 hours from sleep state to supply power to the downstream stage. When the ink screen wakes up, it requests the latest calendar data from the server. According to actual measurements, the current during sleep can reach 1uA. Since it only wakes up once every 4 hours, the overall power consumption is very low.
The software aspect is relatively simple. Directly use the webimage routine in the epdiy routine. Pay attention to modifying the following definitions.
#define ESP_WIFI_SSID "" //你的wifi信息
#define ESP_WIFI_PASSWORD ""
#define STR_HELPER(x) #x
#define STR(x) STR_HELPER(x)
#define IMG_URL ("https://loremflickr.com/"STR(EPD_WIDTH)"/"STR(EPD_HEIGHT))//你的日历服务器的地址
After modification, just compile it. Note that the model of the ink screen should be EPD060SC4 and the PCB version should be V2/V3.
For details, please refer to: Quick Start - ESP32 epdiy
FPC terminals are difficult to weld. If possible, go to Taobao and open a small steel mesh for only 15 yuan, which can ensure the success rate of welding.
As for the screen, I bought it from Xiaohuangyao, with a resolution of 600x600, a 3.8-inch screen with backlight and touch (no touch driver) and 16 levels of grayscale. It was only 20 yuan when I bought it, but now the price has increased.
All reference designs on this site are sourced from major semiconductor manufacturers or collected online for learning and research. The copyright belongs to the semiconductor manufacturer or the original author. If you believe that the reference design of this site infringes upon your relevant rights and interests, please send us a rights notice. As a neutral platform service provider, we will take measures to delete the relevant content in accordance with relevant laws after receiving the relevant notice from the rights holder. Please send relevant notifications to email: bbs_service@eeworld.com.cn.
It is your responsibility to test the circuit yourself and determine its suitability for you. EEWorld will not be liable for direct, indirect, special, incidental, consequential or punitive damages arising from any cause or anything connected to any reference design used.
Supported by EEWorld Datasheet