Notes and code from hack the house - #1
Open
kirahowe wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the firmware for the motion sensor/magnet sensor/led setup from hack the house Nov 11-13 and some notes about setting it up and where we found resources.
Next steps for this are:
delay(5000)call. We want to sound the buzzer after the magnet sensor has been apart for more than 5 seconds, but the problem withdelayis that it freezes all other execution while it finishes.. so if someone pulls the magnet sensor apart for 5 seconds, the buzzer goes off, then they put the sensor back together, the buzzer will still ring for at least 5 seconds. The language has amillis()function that returns the number of seconds since the device booted that I was trying to use to manage the timing instead ofdelay