From 131b07cc0aa931170030d4bb82d341973abd056e Mon Sep 17 00:00:00 2001 From: philippe44 Date: Thu, 6 Feb 2020 17:08:00 -0800 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2085a113..50e12390 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ Use parameter rotary_config with the following syntax: A=,B=[,SW=gpio>[,volume][,longpress]] ``` -HW note: all gpio used for rotary have internal pull-up so normally there is no need to provide Vcc to the encoder. Nevertheless if the encoder board you're using also has its own pull-up that are stronger than ESP32's ones (which is likely the case), then there will be crosstalk between gpio, so you must bring Vcc then. Look at your board schedmatic and you'll understand that these board pull-up create a "winning" pull-down when any other pin is grounded. +HW note: all gpio used for rotary have internal pull-up so normally there is no need to provide Vcc to the encoder. Nevertheless if the encoder board you're using also has its own pull-up that are stronger than ESP32's ones (which is likely the case), then there will be crosstalk between gpio, so you must bring Vcc. Look at your board schematic and you'll understand that these board pull-up create a "winning" pull-down when any other pin is grounded. ### Buttons Buttons are described using a JSON string with the following syntax