Is there a way to map a button to NULL ?

[chas6000]

URC8910
IR5.10
Extender 1_1

Would like to map the short press of LKP on POWER to null. What's the best way to do this?

thanks!

[The Robman]

Hopefully someone familiar with the LKP special protocol will give you a cleaner answer, but if they don't you could always make it send a signal that doesn't actually do anything.

[chas6000]

Hopefully someone familiar with the LKP special protocol will give you a cleaner answer, but if they don't you could always make it send a signal that doesn't actually do anything.

i see -- like something from a different protocol entirely -right?

thanks!

[The Robman]

Not necessarily. If EFC 123 doesn't do anything, use that, or find another EFC that doesn't do anything, which shouldn't be too hard.

[ElizabethD]

URC8910
IR5.10
Extender 1_1

Would like to map the short press of LKP on POWER to null. What's the best way to do this?

thanks!

Hey, I am doing the same thing and just posted a query in Software.
Wish I read your post easlier . As I read Rob's answer to your question, it just might be legal what I did. BTW so long as you put something on the Long OR short side, it's legal, so LKP should never be a problem, yes? no? I was struggling with ToadTog where I must have NOTHING, but the issue seems similar.

[chas6000]

Thanks Rob and Eliz

I found that by erasing the entry in IR in the short side of LKP, I get what I wanted. The led still blinks but the receiver isnt responding if anything is sent.

This has allowed me to protect the power key on the 8910/9910 since its position is unfortunately too close to the arrow keys. it keeps getting pressed accidently as people are trying to navigate DVD menus. This solves the problem because they press it and it does nothing.

This is a great forum, and resource and group of people. Happy New Year to all!

[The Robman]

If the UI doesn't support what you want to do (meaning you need to do a kludge), post something in the Software forum describing how IR could have handled it better and it might make it into a future release of IR.

Be sure to label the thread in such a way that Mark pauker might spot it.

[ElizabethD]

... (meaning you need to do a kludge), post something in the Software forum ...

Rob, YOU have already made the key issue (can’t enter zero key codes into special protocols) visible. My kludge is a reaction to that very link. I didn’t link it. He won’t need it anyway I think

[The Robman]

Did I? I guess I can't keep track of everything, eh?

[mtakahar]

The LDKP protocol itself allows you to have "nothing" on the short/single side by setting the length nibble to 0, same as ToadTog.

Hal

[The Robman]

Rob, YOU have already made the key issue (can’t enter zero key codes into special protocols) visible.

I guess I did...
https://www.hifi-remote.com/forums/viewtopic.php?t=3644

[ElizabethD]

The LDKP protocol itself allows you to have "nothing" on the short/single side by setting the length nibble to 0, same as ToadTog.

Hal

Hal, we can't set low nibble to zero as in EC In IR special protocol keymoves hex-speak not allowed at this time so we kludge or don't get it done.
It will change, though, see https://www.hifi-remote.com/forums/viewtopic.php?t=3438

I don't believe L/DKP is at issue really. ToadTog is.
This is getting too multithreaded

[mtakahar]

Hal, we can't set low nibble to zero as in EC In IR special protocol keymoves hex-speak not allowed at this time so we kludge or don't get it done.

Yeah, I couldn't remember the cases HEX mode was so useful when I saw your posts, but now I do.

This is getting too multithreaded

I know, even Rob can't keep track of them...