Timeline for How to detect pinout at run-time
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:33 | history | edited | Community Bot |
replaced http://electronics.stackexchange.com/ with https://electronics.stackexchange.com/
|
|
Jan 15, 2017 at 2:22 | answer | added | per1234 | timeline score: 1 | |
Jan 15, 2017 at 1:56 | history | edited | Nick Gammon ♦ | CC BY-SA 3.0 |
Removed "Arduino" from question title.
|
Jan 15, 2017 at 0:55 | answer | added | Nick Gammon ♦ | timeline score: 0 | |
Jan 15, 2017 at 0:22 | answer | added | aaa | timeline score: 0 | |
Jan 14, 2017 at 23:59 | history | migrated | from electronics.stackexchange.com (revisions) | ||
Jan 14, 2017 at 22:36 | comment | added | Mr. Developerdude | I am actually going this route in my project. The idea is to abuse Arduino to the benefit of the ease of use for end user. | |
Jan 14, 2017 at 22:34 | comment | added | Jack Creasey | It's a nice thought, but I'd suggest this could most practically only be done at compile time (selecting an Arduino model based on cpu ID). The only situation where you'd actually need this would be if you deployed the same firmware image to multiple cpu ID's ...but that seems beyond the expectations of the Arduino dev environment. | |
Jan 14, 2017 at 22:22 | comment | added | Mr. Developerdude | I did not know about it! Moderators, please migrate this question! | |
Jan 14, 2017 at 21:23 | history | asked | Mr. Developerdude | CC BY-SA 3.0 |