Comments on: Software Debouncing Multiple Latching Switches With Arduino http://www.musicalgeometry.com/archives/248 sound, code, & DIY tech Tue, 31 Aug 2010 18:23:50 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Jason Job http://www.musicalgeometry.com/archives/248/comment-page-1#comment-334 Jason Job Fri, 20 Nov 2009 07:46:36 +0000 http://www.musicalgeometry.com/?p=248#comment-334 I am sorry that my blog post did not meet your expectations. It was not meant to be a treatise on de-bouncing, I merely wanted to share with the world the solution that I came up with for my Arduino project and that worked for me. I am sorry that my blog post did not meet your expectations. It was not meant to be a treatise on de-bouncing, I merely wanted to share with the world the solution that I came up with for my Arduino project and that worked for me.

]]> By: Ray Pasco http://www.musicalgeometry.com/archives/248/comment-page-1#comment-333 Ray Pasco Thu, 19 Nov 2009 19:08:05 +0000 http://www.musicalgeometry.com/?p=248#comment-333 All debouncing, whether done in hardware or software, is dependent on time. You have completely ignored this, which makes your software a "point solution" good for only this uC and its particular crystal frequency, not even to mention the compiler you used and whatever optimization level you chose. It's simply not portable. The algorithm does not account for time passing. All debouncing, whether done in hardware or software, is dependent on time. You have completely ignored this, which makes your software a “point solution” good for only this uC and its particular crystal frequency, not even to mention the compiler you used and whatever optimization level you chose.

It’s simply not portable. The algorithm does not account for time passing.

]]> By: brian http://www.musicalgeometry.com/archives/248/comment-page-1#comment-191 brian Wed, 13 May 2009 10:26:35 +0000 http://www.musicalgeometry.com/?p=248#comment-191 I had to do something similar recently. I had to watch several pins for changes in an electrically noisy environment, so I couldn't immediately believe what a pin was telling me. The solution I came up with was to make a struct containing pin number, pin value, number of votes, and number of votes required. To update the struct, I read the appropriate pin. If the reading agreed with the current value, I considered it a vote to keep the current value and decremented the number of votes, if it wasn't already 0. If the reading disagreed with the current value, I considered it a vote to toggle and incremented the number of votes. If the number of votes reached the number of votes required, I toggled the value. The electrical noise never reaches the required threshhold. Sounds pretty similar to what you did. I had to do something similar recently. I had to watch several pins for changes in an electrically noisy environment, so I couldn’t immediately believe what a pin was telling me. The solution I came up with was to make a struct containing pin number, pin value, number of votes, and number of votes required. To update the struct, I read the appropriate pin. If the reading agreed with the current value, I considered it a vote to keep the current value and decremented the number of votes, if it wasn’t already 0. If the reading disagreed with the current value, I considered it a vote to toggle and incremented the number of votes. If the number of votes reached the number of votes required, I toggled the value. The electrical noise never reaches the required threshhold. Sounds pretty similar to what you did.

]]>