Support for IR "Repeat Codes"?

[MartinR]

Greetings,

I'm a proud new owner of one of these terrific devices. I must say, the product looks very professionally assembled. Worked great, right out of the box! Superb!

I've done some searching, but I'm still a bit unclear on the following issue. Yamaha receiver volume controls use something I've seen referred to as "repeat codes". Here is the pronto code for the volume up:

0000 006c 0000 0022 0156 00ad 0015 0015 0015 0041 0015 0015 0015 0041 0015 0041 0015 0041 0015 0041 0015 0015 0015 0041 0015 0015 0015 0041 0015 0015 0015 0015 0015 0015 0015 0015 0015 0041 0015 0015 0015 0041 0015 0015 0015 0041 0015 0041 0015 0015 0015 0015 0015 0015 0015 0041 0015 0015 0015 0041 0015 0015 0015 0015 0015 0041 0015 0041 0015 0041 0015 0200

If I recall correctly, the whole code is sent once, and then part of the code is repeatedly sent as long as the remote button is held down. The repeat code is much shorter, and the receiver has a built in delay while it ignores such repeat codes. The result is that if you press and hold the volume up button on the remote, the receiver raises the volume one notch, waits about a second or so, and then raises the volume very quickly.

Can the USB-UIRT accomplish this button down behavior? If so, how does one get it to work in girder?

I've tried using netremote, as well as the AIT X10 remote plugin to test.

Netremote seems to send discrete button down events, even if I hold the button, so that's not encouraging.

The ATI driver is a bit better. It receives a button "down event", and then receives continued button "hold" events, until you stop pressing the button, and then it gets a button "up" event. However, the uirt girder plugin seems to only send one volume up code during this whole process.

I hope this question is straight forward. Fortunately, I don't have to worry about ir collisions in this scenario. I'd be pleased to clarify anything I've written!


Thanks,
Martin.

[jrhees]

Martin,

The pronto code you included in your post contains *only* a repeat section. That means that if you paste (in the USB-UIRT Pronto import screen) this code into Girder and then set the 'Repeat' setting to something high (like 20) you should see the equivalent of when you hold down the button on your remote a while (you can get an idea of how long a particular repeat value really is by looking at how long the RED LED stays ON).

Give this a try and let me know what happens.

-Jon

[MartinR]

Doh!

You are totally correct. I scooped the code from another forum, mis-remembering what I was cutting. I wanted to provide the code as an example of what I'm trying to get working, and just ended up complicating matters.

I'll post the correct full code tonight, once I get home. Hopefully that will put my question in it's proper context.

Thanks!
Martin.

[MartinR]

Here is the volume up pronto code:

Code: Select all

0000 006d 0022 0002 0155 00aa 0016 0016 0016 003f 0016 0016 0016
003f 0016 003f 0016 003f 0016 003f 0016 0016 0016 003f 0016 0016
0016 003f 0016 0016 0016 0016 0016 0016 0016 0016 0016 003f 0016
0016 0016 003f 0016 0016 0016 003f 0016 003f 0016 0016 0016 0016 0016 0016 0016 003f 0016 0016 0016 003f 0016 0016 0016 0016 0016
003f 0016 003f 0016 003f 0016 05e6 0155 0055 0016 0e3d


Here is the UIRT code:

Code 1:

Code: Select all

R0000815580AA1616163F1616163F163F163F163F1616163F1616163F1616
161616161616163F1616163F1616163F163F161616161616163F1616163F16
161616163F163F163F1685E6


Code 2:

Code: Select all

0000815555168E3D


BTW: what are the "Code 1" and "Code 2" for?

So, can UIRT handle the repeat codes properly?

Thanks,
Martin.

[jrhees]

In a word, YES.

Code 1 is the 'send once' code, and code 2 is the 'repeat' code.

So, for example, if you set repeat to 4, the send once part will be sent once and the repeat part will be sent immediately after 4 times.

If you set repeat high enough, you should see a mimick of holding the button down on your remote.

-Jon

[MartinR]

Jon,

Thanks for the reply! I see what you're saying. I was actually hoping that the exact same behaviour as the original remote was attainable. That is, the repeat would occur for as long as the button was held down. The repeat count is great for setting something like commands like, +3dB, -3dB, +6dB, -6dB, in my example with volume controls, which is very usable. But it doesn't handle the case of the remote control user having full control of the repeat duration. To be honest, this isn't a huge issue for me; I was just trying to get the as close to the same "feel" as the original remote.

Thanks also for the clarification on what code 1 and code 2 meant. Makes sense, but I didn't want to assume.

BTW: I wanted to mention that I'm very impressed with the power and angle of dispersion of the transmitter.

Finally, you might want to know that I found a crash in the Girder plugin. I was trying to get a difficult Pioneer remote code (doesn't repeat, and the learn function would keep waiting for more signal) by running the IR debug function, copied some of the hex to the clipboard, and when I closed the debug window, I got a crash. Seems reproducible.

Cheers!
Martin.

[jrhees]

MartinR,

Thanks for the infor about the Girder crash. As far as emulation of hold-down repeats, the closest thing to that currently is the NetRemote USB-UIRT plugin. This plugin is beta and must be requested at uirtsupport@earthlink.net. However, it *does* do what you describe (although it is still being improved).

-Jon