JP1 Remotes

I installed the upgrade for ReplayTV (hacked) to my URC8910 and mapped out the buttons using RM. I wanted to place the commercial advance function on the comm/skip button and that's where I placed it. When I loaded the upgrade and protocols into IR, it showed the keymove for the comm/skip button. Everything else worked well, but that button did not work.

I went back and downloaded to IR and there was no record of the keymove and the comm/skip button is not even listed. I have since changed the commercial advance to another button. But looking at the literature from the 8910, I found that the comm/skip button actually causes the remote to change channels for a specified period of time (like prev button), and when I press it, there is no LED and no signal on the LCD showing an IR signal is being sent. That leads me to believe that the comm/skip button may not actually send out an IR signal, but may be some kind of "timer" button. Does that make sense, and does anyone know if it can be programmed for an IR function?

Thanks

The only way to program the comm. skip button like any other button is to install the extender for the 8910.

Thank you very much!

I was reading about extenders the other night, and I d/led the 8910 extender and was reading the files that came with it. However, I'm still very new at this and I'm not quite sure if I want to use the extender yet. I'm not afraid to admit it seems a bit scary to install the thing!

Just remember that if you save your current remote image (a .IR file), you can always get back to that configuration by uploading that image to the remote. You can not damage the remote by incorrectly installing the extender. Worst case the extender won't work and the remote will seem dead. But restore the old image and everything will be back to normal.

Then I think I have everything I'll need. I might as well give it a go! That's what JP1 is all about anyhow, right, making our remotes do what we want them to do?

Well, I tried the extender, but I didn't have much luck. It made the remote do all kinds of crazy things. I'll experiment some more, but you were right...I just went right back to a working configuration with no problem.