IR Toggle Bit Codes

[Roti]

Hi.

Is there an elegant solution for devices that use alternating toggle
bits in their IR codes (for debouncing, etc).

For instance, the UP button for a Windows Media Center remote will
alternate between:

code A:
sendir,
1:1,1,36127,1,1,96,32,16,16,16,16,16,32,16,32,48,32,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,32,16,16,16,16,16,16,16,16,32,16,16,16,16,16,16,32,32,16,16,16,16,16,16,16,16,32,16,16,16,16,16,16,32,16,3612

code B:
sendir,
1:1,1,36127,1,1,96,32,16,16,16,16,16,32,16,32,48,32,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,16,32,16,16,16,16,16,16,32,16,16,16,16,16,16,16,16,32,32,16,16,16,16,16,16,16,16,32,16,16,16,16,16,16,32,16,3612

Codes need to be alternated fort the device to repond normally to
sequential presses. Simply repeating one of the codes leads to further
presses being ignored until another button is pressed.
I've seen some posts saying change repeat count to 2, but this has not
worked for me.
Other have said to send both close together, or as a combined code,
but this usually results in a double press being detected by the
device.
RC5/6 Toggle bit codes were supported in the Pronto Pro (RIP)
database.

Now I could build a javascript solution for the devices and toggle a
variable/join/token to keep track of which code to send, but as it's
not an overly uncommon problem, I was wondering of anyone had a simple
fix ? Alternatively, would it be possible to add a checkbox in CF GUI
Designer in the "Command Properties" box that allows you to add a
second Command Value that can be alternated\toggled with the first
(hence you could use it for any type of network IR emitter if you have
noth codes).

In the case of Media Center PCs there are a few workaround options
(incl control via IP, disable deboucing in registry). I think XBox360s
might do this do (have not checked), and some Maramtz and Thomson
devices do it as well.

Thanks.

[xAPPO]

Sometimes devices will work without the toggle bit if you leave a
sufficient time gap between the transmissions.

Another way around is to find an IR code in the same format ( in your
case RC6 -6-32) that does nothing and append this to all the codes
that need toggles - so effectively the code always changes.

If you break apart the code into its various fields you can try a
different device or sub device code for example - might work. If
that doesn't work then you can try and find a control code that isn't
supported in your particular model eg a PIP button on a non PIP TV or
selecting an input you don't have. I dont use MCE so I can't suggest
what might be unused there. You need to ensure this code is ignored
in the place where you are needing the sequential identical codes

K

[sarneel]

Or try another receiver.. Maybe another usb interface works better..

When I need to simulate a toggle bit I just send a dummy on press and
the ir code i want to send on release..

gr.

[barrygordon]

For WMC i believe there is a registry option to inhibit the denounce
logic at which time the toggle bit is ignored. Do a search of remote
central for the phrase enabledebounce.

[Nahshon Williams]

On a different note, if using a computer I find a better option for WMC control from commandfusion is eventghost.
Now if only I can find a free mac version . . . .
Nahshon

--
You received this message because you are subscribed to the Google Groups "CommandFusion" group.
To post to this group, send email to comman...@googlegroups.com.
To unsubscribe from this group, send email to commandfusio...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commandfusion?hl=en.