I have an HTPC and a 6131. I'm using Girder.
I want to simply program the DVD Mode to send a unique IR code for each and every button. I dont care what the IR code is, as I am going to learn it with Girder. What is the easiest way to do this?
Following the post by ToonGal, I was able to create a new file in KM using the RC-5 protocol, but I didnt necessarily know what device1, device2, device3 values to set.
Then I just went down the function list and entered "000", "001", "002" and so on for the OBC's. Then I clicked "Swap OBC/EFC". Assigned the functions to the buttons on the remote and applied the upgrade.
It works, except each button produces TWO IR codes....is this OK? I am assuming you learn BOTH codes if you want repeat and only ONE code if you don't want repeat? Is that what that's all about.
I'm sorry if these are basic questions, they're just difficult to search on as I'm not sure what to call them....
Thanks!
How do I setup a simple map for HTPC use?
Moderator: Moderators
RC-5 protocol is designed to have two different codes for each button. Unless Girder understands than and has specific support and use for that feature, RC-5 would be a poor choice for your purpose.
The purpose of the two codes is so that the receiver can tell the difference between one long press of a key and two shorter presses. A long press sends the same IR signal over and over again. Each time you release and repress the button, RC-5 switches between the two versions.
I think Girder is most compatible with the NEC2 protocol.
You don't need to swap OBC/EFC after entering the OBC values. Aside from that detail it sounds like you did all the steps just right. The device and subdevice numbers wouldn't matter for your purpose (unless you have other remotes or devices involved that you need to be unique from).
If the TWO codes problem is inconvenient enough that you want to start over, I suggest using NEC2 (most protocols, including NEC2 do not have the two-code behavior that RC-5 has).
The purpose of the two codes is so that the receiver can tell the difference between one long press of a key and two shorter presses. A long press sends the same IR signal over and over again. Each time you release and repress the button, RC-5 switches between the two versions.
I think Girder is most compatible with the NEC2 protocol.
You don't need to swap OBC/EFC after entering the OBC values. Aside from that detail it sounds like you did all the steps just right. The device and subdevice numbers wouldn't matter for your purpose (unless you have other remotes or devices involved that you need to be unique from).
If the TWO codes problem is inconvenient enough that you want to start over, I suggest using NEC2 (most protocols, including NEC2 do not have the two-code behavior that RC-5 has).
-
sixdoubleo
- Posts: 4
- Joined: Mon Apr 05, 2004 9:07 pm
The dual code isn't a problem per se. Like I said, I just learn both codes in Girder. The effect is that when you hold down a button, it does a VERY FAST repeat. Sometimes it's good...sometimes it's bad. FWIW, the Hauppauge Silver remote (which is what I USED to use for my HTPC uses the dual IR code method also.johnsfine wrote:The purpose of the two codes is so that the receiver can tell the difference between one long press of a key and two shorter presses. A long press sends the same IR signal over and over again. Each time you release and repress the button, RC-5 switches between the two versions.
I think Girder is most compatible with the NEC2 protocol.
Not inconvenient at all. Like most of the members here I enjoy playing with this stuff and am after the cleanest, most straightforward setup...so I'll definitely redo it with NEC2.johnsfine wrote: If the TWO codes problem is inconvenient enough that you want to start over, I suggest using NEC2 (most protocols, including NEC2 do not have the two-code behavior that RC-5 has).
Two more questions....
1. Do I just leave the device1, device2, and device3 empty? Or do I just set device1=1 or what?
2. What is the significance of selecting the code "1111" for the device code? Is that just some unused code? Can I select any code under 2047?
-
mr_d_p_gumby
- Expert
- Posts: 1370
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Newbury Park, CA
NEC2 is a commonly used protocol, so it's possible you might have other remotes that use this protocol that could interfere. You can leave the Device settings blank or put in some arbitrary numbers for Device1 & Device2. If it turns out some other remote interferes, change the Device numbers to something else.sixdoubleo wrote:1. Do I just leave the device1, device2, and device3 empty? Or do I just set device1=1 or what?
Any setup code number from 0 to 2047 is valid. Just don't pick a number that might conflict with another setup code you plan to use in the remote, because it will override a built-in setup code of the same type & number.sixdoubleo wrote:2. What is the significance of selecting the code "1111" for the device code? Is that just some unused code? Can I select any code under 2047?
Mike England