> Because this remote uses a special repeat code, the bouncing effect in
> fact can only be caused by the remote itself. Try cleaning the contacts on
> the remote.
> Unfortunately I can't thing of any parameter in lircd.conf that you could
> use as work-around.
So I'm showing my EE geek tendencies here, but I decided to hook an o-scope up to me receiver and see how the signal levels looked on the receiver. Everything looks fine, but I did see a different problem. It looks like normally the remote sends a long IR string when pressing down on the button, and a short IR string when holding or releasing the button. For some reason, my remote occasionally sends two long IR strings when pressing down on the button, hence the bouncing.
The patch to lircd.c below fixes my problem. Sorry to bastardize your code, as it is almost assuredly the wrong way to do this, but that's probably becuase I have a combined total of about 2 hours of experience with this source. Anyway, this hack works for me becuase my remote should never be broadcasting the exact same string twice in a row as far as I can tell.
Thanks for the help,
--- lircd.c.orig 2009-04-19 21:28:42.000000000 -0600
+++ lircd.c 2009-04-19 22:16:52.000000000 -0600
@@ -1743,7 +1743,8 @@
void broadcast_message(const char *message)
- int len,i;
+ int len,i,compare;
+ static char prev_message[PACKET_SIZE+1] = "";
const char *release_message;
release_message = check_release_event();
@@ -1753,7 +1754,11 @@
+ if(compare == 0) return;
for (i=0; i<clin; i++)
LOGPRINTF(1,"writing to client %d",i);