You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- That seems odd, and not expected. The inputs on a CMOS device like an Arduino should be capacitive, and draw almost no current once they settle on their state. (It takes a small amount of current to drive the capacitor on the input to the high state, but then once it's charged, current flow should drop to the leakage current of the capacitor.)Duncan C– Duncan C2019-12-10 18:22:08 +00:00Commented Dec 10, 2019 at 18:22
- Could you put the pin through a 10K resistor to ground when your switch is closed? That should be enough to pull the pin low, but greatly reduce the current flow.Duncan C– Duncan C2019-12-10 18:22:49 +00:00Commented Dec 10, 2019 at 18:22
- You write that the "attiny85 draws around 3mA", so did you measure the current that is sunk by the pin or is it the current consumption of the entire chip? Does it change when you don't configure anything? Also, measuring current to detect the state of a switch seems way too complicate, you could probably read the voltage level at the switch directly.Sim Son– Sim Son2019-12-10 18:57:03 +00:00Commented Dec 10, 2019 at 18:57
- 3 mA is a normal current draw for an ATtiny85 @ 3 V and 8 MHz. This has nothing to do with the input pin, it's just the current the AVR core needs to execute whatever instructions you ask it to execute.Edgar Bonet– Edgar Bonet2019-12-10 19:29:49 +00:00Commented Dec 10, 2019 at 19:29
- 1On your devboard PB3 is connected to +5V over two resistors (1.5 k + 66.5) Ohms. That's the reason for the high current. Not the PU Resistor. ;-) See the scematics s3.amazonaws.com/digistump-resources/files/… (5/1560 = 0.0032051)Peter Paul Kiefer– Peter Paul Kiefer2019-12-11 16:30:27 +00:00Commented Dec 11, 2019 at 16:30
| Show 5 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. arduino-uno), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you