home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
HTPC Projects
Hardware
Input/Output Interfaces
Is there any use for a multi protocol IR receiver/ transmitter?
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CyberSimian" data-source="post: 1182109" data-attributes="member: 141969"><p>There are two shortcomings common to existing MCE RC6 IR receivers:</p><p></p><p>(1) On wake from sleep or wake from hibernation, a USB-connected MCE RC6 IR receiver sometimes malfunctions, and Windows displays a message to the effect that "a USB device has stopped working". The malfunction evidently occurs at some point <em>during</em> the wake-up process, as the receiver is able to <em>initiate</em> the wake-up process without problem.</p><p></p><p>This problem seems to affect quite a few users, but not necessarily all users (so it may be dependent on the exact sequence of wake-up processing resulting from the specific hardware and software present in the HTPC). Certainly, I experienced this problem during the five years that I used WMC, and I have continued to experience it now that I use MP. In my case, it occurs on average perhaps once per week, but it is erratic. The solution that I use is simply to unplug the IR receiver, wait 10 seconds, and then replug it.</p><p></p><p>(2) The MCE RC6 signalling protocol uses "toggle codes", whereby there is an extra bit flag that toggles between 0 and 1 on successive button-presses (this may not be an exact description, but it is something like this). So two consecutive presses of the <em>same</em> button actually give two <em>different</em> button codes. This technique helps to eliminate the effects of contact bounce occurring in the remote control. The problem is that the Microsoft driver implements debounce processing incorrectly, with the result that some button-presses are ignored in certain sequences of button-presses. This is described in excruciating detail in this post:</p><p></p><p><a href="http://www.thegreenbutton.tv/forums/viewtopic.php?p=55303#p55303" target="_blank">http://www.thegreenbutton.tv/forums/viewtopic.php?p=55303#p55303</a></p><p></p><p>There is a registry setting that can disable Windows debounce processing. That eliminates the problem that causes some button-presses to be ignored, but introduces the problem of some single button-presses being interpreted as two or three button-presses (caused by contact bounce in the remote).</p><p></p><p>Recently I have been using the Ortek/Hama remote control (with its own dedicated IR receiver). This remote is <em>not</em> an RC6 remote, and does not suffer from either of the shortcomings described above, so I am probably going to use it long term (albeit with the Ortek/Hama definitions programmed into a universal remote control). I also have a Logitech 650, and that <em>does</em> implement toggle codes correctly, so <em>does not</em> suffer from shortcoming (2). However, it still requires a conventional MCE RC6 IR receiver, and so <em>does</em> suffer from shortcoming (1).</p><p></p><p>-- from CyberSimian in the UK</p><p></p><p>See further discussion on that in the <a href="https://forum.team-mediaportal.com/threads/mce-rc6-ir-receivers-shortcomings.134210/" target="_blank">following thread</a>.</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1182109, member: 141969"] There are two shortcomings common to existing MCE RC6 IR receivers: (1) On wake from sleep or wake from hibernation, a USB-connected MCE RC6 IR receiver sometimes malfunctions, and Windows displays a message to the effect that "a USB device has stopped working". The malfunction evidently occurs at some point [I]during[/I] the wake-up process, as the receiver is able to [I]initiate[/I] the wake-up process without problem. This problem seems to affect quite a few users, but not necessarily all users (so it may be dependent on the exact sequence of wake-up processing resulting from the specific hardware and software present in the HTPC). Certainly, I experienced this problem during the five years that I used WMC, and I have continued to experience it now that I use MP. In my case, it occurs on average perhaps once per week, but it is erratic. The solution that I use is simply to unplug the IR receiver, wait 10 seconds, and then replug it. (2) The MCE RC6 signalling protocol uses "toggle codes", whereby there is an extra bit flag that toggles between 0 and 1 on successive button-presses (this may not be an exact description, but it is something like this). So two consecutive presses of the [I]same[/I] button actually give two [I]different[/I] button codes. This technique helps to eliminate the effects of contact bounce occurring in the remote control. The problem is that the Microsoft driver implements debounce processing incorrectly, with the result that some button-presses are ignored in certain sequences of button-presses. This is described in excruciating detail in this post: [URL]http://www.thegreenbutton.tv/forums/viewtopic.php?p=55303#p55303[/URL] There is a registry setting that can disable Windows debounce processing. That eliminates the problem that causes some button-presses to be ignored, but introduces the problem of some single button-presses being interpreted as two or three button-presses (caused by contact bounce in the remote). Recently I have been using the Ortek/Hama remote control (with its own dedicated IR receiver). This remote is [I]not[/I] an RC6 remote, and does not suffer from either of the shortcomings described above, so I am probably going to use it long term (albeit with the Ortek/Hama definitions programmed into a universal remote control). I also have a Logitech 650, and that [I]does[/I] implement toggle codes correctly, so [I]does not[/I] suffer from shortcoming (2). However, it still requires a conventional MCE RC6 IR receiver, and so [I]does[/I] suffer from shortcoming (1). -- from CyberSimian in the UK See further discussion on that in the [URL='https://forum.team-mediaportal.com/threads/mce-rc6-ir-receivers-shortcomings.134210/']following thread[/URL]. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
HTPC Projects
Hardware
Input/Output Interfaces
Is there any use for a multi protocol IR receiver/ transmitter?
Contact us
RSS
Top
Bottom
