JP1 Remotes

I recently acquired a Rosewill RRC-126 MCE RC6 Remote + USB Receiver. This is attached to a Windows 7 machine.

The original Rosewill remote only has a Power toggle button.

The RCA RCRP05B has the v1.05 Extender installed.

Thanks to the the MCE + XBox 360 upgrade available on the site, I was very happy to find that everything worked, including the Discrete On / Off commands during my testing.

However, once I had everything setup, I noticed an issue with the discrete codes. The discrete ON command seems to "miss" sometimes, and not wake the computer. Sending the command again does work, and manages to wake the computer as expected. When a "miss" happens, it causes HDMI handshake issues with the Onkyo amp connected to it.

I would like some help in figuring out why this is happening, and if there's a solution to this issue.

I have uploaded an RMIR with just the device + 3 buttons setup here, which exhibits this issue: https://www.hifi-remote.com/forums/dload ... e_id=12424

Thanks In Advance!

Your answer was in the title. Its an MCE RC6 remote. One thing I've learned about automation, is that RC5, RC6 and MCE can make automation tricky. The protocol has a toggle bit, so each time you press the button, it changes the toggle bit.

Apparently on some equipment, it ignores the toggle bit, if it is a receives a different function, but on all my RC5 equipment it stubbornly refused to do anything until it received the a button in the correct toggle state. Hence learns would only work once, and functions that use a setup codes from a UEI remote would often "miss", since the toggle bit isn't kept for a single mode, it varies with every keypress no matter what mode you are in.

The oood news for you, is that you have a discrete, so you can put it in the macro two times in a row, and it will be on. Toggle buttons on the other hand are a mess. I gave all my toggling equipment to the Goodwill, and then went around front and bought the equivalent equipment in a non-toggling brand.

Thanks, vicky.

Don't know why I didn't think of sending the discrete ON twice. Duh, seems obvious now.

I did come across that issue during my research in trying to fix it. However, from what I gathered, it meant that all keys had the "miss" issue, and that wasn't the case for me so I assumed that wasn't the problem.

What threw me off was the note in the device upgrade:

The MCE toggle bit actively toggles when this protocol is used, so you do not need the Windows registry change that disables debounce (to work with learned signals in which the toggle bit isn't active). The RC6 toggle bit is a different bit than the MCE toggle bit. The RC6 toggle bit is always zero in MCE signals.

I thought that meant that it was emulating the original remote for all keys, but apparently the discrete ON is a special case.

Thanks again.

well upon reading more, it does appear that MCE is supposed to have the T=0 and nonstandard has a toggling bit.

The "miss" thing can happen on some keys and not others. My last, most irritating rc5 device, had a different toggle bit for the arrow keys, than on the rest of the remote. Trying to automate CC was a nightmare. That was the last straw.


I refuse to buy any more equipment that has an RC5 or RC6 protocol. I now look for discrete codes in the upgrades here, before I buy. I like JP1 for the automation aspect and some equipment just makes that impossible. So I vote with my $$$.