LED is on for LOW, off for HIGH, opposite to expected
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
Research direction
Start with the shown Blink sketch and the D1 mini onboard LED behavior, then check the repository's related example or board documentation. Confirm whether the active-low result is expected and whether the example's comments or pin guidance need correction; done means the expected LED behavior is clearly established.
Written by the indexing model from the issue text.
Description
This sketch is the basic "blink" example from this repository with a longer time LOW so as to see the difference between LOW and HIGH. LED is on for 4 sec, off for 1 sec. Other tests confirm that LOW=On and HIGH=Off. Is this normal or have I done something wrong during the very complex setup process? Does this mean that my other pins are reversed?
/*
- WEMOS sample sketch modified with my long time off to check
- Blink
- Turns on the onboard LED on for one second, then off for FOUR seconds, repeatedly.
- This uses delay() to pause between LED toggles.
*/
void setup() {
pinMode(BUILTIN_LED, OUTPUT); // initialize onboard LED as output
}
void loop() {
digitalWrite(BUILTIN_LED, HIGH); // turn on LED with voltage HIGH
delay(1000); // wait one second
digitalWrite(BUILTIN_LED, LOW); // turn off LED with voltage LOW
delay(4000); // wait FOUR seconds
}
- Dominant language
- C++
- Stars
- 560
- Forks
- 226
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wemos/D1_mini_Examples
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
wemos/D1_mini_Examples#61 ·
-
w5100 y esp8266Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
wemos/D1_mini_Examples#60 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
wemos/D1_mini_Examples#59 · 2 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
wemos/D1_mini_Examples#58 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
wemos/D1_mini_Examples#57 · 2 comments ·
All issues in wemos/D1_mini_Examples
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
espressif/esp-matter#1867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
cuAmpcorParameter.cpp (CPU pycuampcor) does not compile with libc++: EXIT_FAILURE is undeclaredOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
isce-framework/isce3#387 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conan-io/conan-center-index#31055 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day