-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
buttons.c (demo branch) #169
Comments
@VonSzarvas - Yes, rc_time should be leaving the pins as input when it's done. @AndyLindsay can correct me if I'm wrong. If we later set the pins low, they'll be set back to outputs. Is that what you intend, so there's no floating button lines (is that the "interference" you mean)? Question: What's on I/O 2 (that was set low twice in the old code but not at all in the new)? |
I don't think I wrote that. The button code for the non-WX badge was this:
|
Io2 was reassigned to another sensor. Instead the other side of the passive buttons is permanently low.
That links to why I wondered if setting the 2 passive button lines low when not being scanned would remove potential floating problems from the high impedance. Its 470k on the line to gnd.
|
Andy, yes the code changed for BadgeWX. Maybe it could be improved, but I can confirm it works great as is. Matt might have crafted these edits on the original badge code?
Impact note: |
Should be fixed now. This can be closed. |
Buttons is broken because some pins are hard-defined.
Suggested update (with original code in comments after each changed line):
old:
new:
rc_time leaves the pin as an input when it's done, right?
Extra idea- After the above code block, set the pins low to mitigate interference?
The text was updated successfully, but these errors were encountered: