Timeline for Comparing button presses to correct sequence
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 19, 2018 at 20:53 | answer | added | Katie | timeline score: 1 | |
| Apr 19, 2018 at 20:50 | history | edited | Katie | CC BY-SA 3.0 |
deleted 10270 characters in body; added 76 characters in body
|
| Apr 19, 2018 at 18:55 | comment | added | Katie | That was one of the things I was thinking could be wrong since I declare the pinModes with INPUT_PULLUP. Should I instead just use INPUT? Or would it be more efficient to not have the pull down resistors? | |
| Apr 19, 2018 at 18:49 | comment | added | Juraj♦ | the buttons in schema have pull-down resistors | |
| Apr 19, 2018 at 14:42 | history | edited | Katie | CC BY-SA 3.0 |
added picture
|
| Apr 19, 2018 at 14:25 | comment | added | Katie | I have outputted the button states as well as the button state right before it checks the sequence along with the seq. In the serial monitor it will say button3 = 1 when I have not pressed any buttons since the start of the program. | |
| Apr 19, 2018 at 14:23 | history | edited | Katie | CC BY-SA 3.0 |
added debouncing
|
| Apr 19, 2018 at 14:03 | comment | added | Mark Smith | What have you done to try to understand the problem? Put some debug prints in, see where it's going wrong. | |
| Apr 19, 2018 at 13:57 | history | edited | Katie | CC BY-SA 3.0 |
Improved formatting
|
| Apr 19, 2018 at 13:57 | answer | added | Michel Keijzers | timeline score: 0 | |
| Apr 19, 2018 at 13:51 | history | asked | Katie | CC BY-SA 3.0 |