Some times we get a double bounce signal... I'm not sure what is causing that though... the code looks like it should send the correct signal. (But obviously it does not)
Some times we get a double bounce signal... I'm not sure what is causing that though... the code looks like it should send the correct signal. (But obviously it does not)
Or I was wrong. Maybe the delay between repeating codes is too long?
My guess is, TV got the command, waited (ok, I didn't see the command again), then saw your "repeat" and thought -- Ok! Let's do it again!
Also, there are usually commands for "repeat" -- like key repeat.
Run the "learning" code, and use/hold down the volume up/down.
You'll see the comamnds .. then you'll see the "repeat" key FFFFFF. It might be worth learning that too, rather then trying to send the same command multiple times -- while fighting with the TV dup-check.
Or I was wrong. Maybe the delay between repeating codes is too __long__?
My guess is, TV got the command, waited (ok, I didn't see the command again), then saw your "repeat" and thought -- Ok! Let's do it again!
Also, there are usually commands for "repeat" -- like key repeat.
Run the "learning" code, and use/hold down the volume up/down.
You'll see the comamnds .. then you'll see the "repeat" key FFFFFF. It might be worth learning that too, rather then trying to send the same command multiple times -- while fighting with the TV dup-check.
In [991e33a208] I reduced the CODE_DELAY value, and so far I have yet to see the TV have anymore issues.
The movie box has the "repeat" key FFFFFF. The TV from what I gathered did not, it sends a command repeated but I think my command sending was to slow so the TV was getting the command then waited then saw it again.
I think this issue is fixed... but again if need be I can/will change the CODE_DELAY again.
In [991e33a208] I reduced the CODE_DELAY value, and so far I have yet to see the TV have anymore issues.
The movie box has the "repeat" key FFFFFF. The TV from what I gathered did not, it sends a command repeated but I think my command sending was to slow so the TV was getting the command then waited then saw it again.
I think this issue is fixed... but again if need be I can/will change the CODE_DELAY again.
Some times we get a double bounce signal... I'm not sure what is causing that though... the code looks like it should send the correct signal. (But obviously it does not)
In [
fbbc499375] I merged the CODE_DELAY into aconst intvariable. (This should make things easier to change if needed)Or I was wrong. Maybe the delay between repeating codes is too long?
My guess is, TV got the command, waited (ok, I didn't see the command again), then saw your "repeat" and thought -- Ok! Let's do it again!
Also, there are usually commands for "repeat" -- like key repeat.
Run the "learning" code, and use/hold down the volume up/down.
You'll see the comamnds .. then you'll see the "repeat" key FFFFFF. It might be worth learning that too, rather then trying to send the same command multiple times -- while fighting with the TV dup-check.
In [
991e33a208] I reduced the CODE_DELAY value, and so far I have yet to see the TV have anymore issues.The movie box has the "repeat" key FFFFFF. The TV from what I gathered did not, it sends a command repeated but I think my command sending was to slow so the TV was getting the command then waited then saw it again.
I think this issue is fixed... but again if need be I can/will change the CODE_DELAY again.