Timeline for How to program thresholds?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2016 at 9:05 | comment | added | Avamander | It's always a good idea to add a Serial.print() and else/default to be notified via serial if any values go over/under your radar, especially as a beginner. | |
| May 14, 2015 at 4:51 | comment | added | bpinhosilva | Good point, @jwpat. Well, inside the function doSomething, there could be a verification and then decide which state to go in sequence. This code is just a start point where someone could develop their own code. The user has to make sure it checks every single situation to make sure it'll work properly. | |
| May 14, 2015 at 4:45 | comment | added | James Waldby - jwpat7 | That code is faulty – as it stands, once the state changes to 3, it stays at 3 no matter what value occurs. Also, when state is 1, a value of 30 or more doesn't get processed. So for example the sequence 15, 35, 15 results in no actions occurring. | |
| May 14, 2015 at 3:09 | history | answered | bpinhosilva | CC BY-SA 3.0 |