Assigning a second device to the shifted keys of an existing

[Teleport]

I couldn't find any info on this on the forum but it must have been mentioned before. I'd be grateful if someone could help.

I have created an separate upgrades for both my TV and projector. Both work fine. I only have 5 buttons on my Topline 5 and to save space would like to move the projector functions over from the AUX button to the shifted keys on the TV button.

So The TV button would operate the TV as usual, but pressing the shift key would operate the projector.

I did think of using the "keymover" function on the remote but when I reassign a new device to the "AUX" button would I still have the projector functions available? Or would they be wiped from the shifted TV keys or replaced by the new AUX device keys?

Or is there a way I could somehow merge my 2 upgrades in KM even though they both use different protocols and device codes?

Thanks to anyone who can help

[johnsfine]

I did think of using the "keymover" function on the remote but when I reassign a new device to the "AUX" button would I still have the projector functions available? Or would they be wiped from the shifted TV keys or replaced by the new AUX device keys?

A KeyMove does not depend on the source setup code being assigned to a device key.

Even without JP1, you can define a KeyMove and then reprogram the source device key to some other setup code. The KeyMove remembers the source setup code it was defined with. It does not remember the source device key.

With JP1, you don't need to assign the source setup code even temporarily to a device key. You can directly specify the source setup code when defining the KeyMove rather than specifying it indirectly through a device key.

So you can do what you want with KeyMoves, but it might take more KeyMove memory than you want to dedicate to that purpose.

I don't know enough about your model remote to say very much about alternatives. In some models of remote it is possible to use more device modes than you have device keys. That approach may make your device easier to operate as well as saving KeyMove memory. In some extenders it is possible to define a seperate upgrade for the shifted keys of a device mode. That could duplicate the behavior of doing it all in KeyMoves, but using less memory. I don't know if either of those methods is available to you.

[johnsfine]

I have created an separate upgrades for both my TV and projector.

A KeyMove also doesn't depend on any functions being assigned to keys within the source setup code. It gets only the protocol and fixed data from the source setup code.

If you use KeyMoves, you might not need the projector upgrade at all. If any built-in setup code has the same protocol and fixed data, it doesn't matter how wrong its key assignments are, you can use it without problems.

If you do need an upgrade for the source setup code of KeyMoves, you can save space by clearing out the buttons sheet of the upgrade so it doesn't assign any functions to buttons.

[The Robman]

Even though the URC-5550 only has 5 device buttons, it's really an 8 device URC-8550 inside, so to do what you want is alot easier than you think. You can either use spare buttons, or shifted buttons, and make them extra device buttons. You would do this by programming macros on them that select the missing device modes.

For example, you could program a macro to the VIDEO button where the only step is @AMP (which is one of the missing device buttons). Then, as long as you have your projector programmed to the @AMP button, you're all set.

[Teleport]

Thanks for the replies John & Rob.

I've tried using keymoves but unfortunatly there seems to be a bug in IR where it seems to select the wrong key. If I choose say the "20" key it will assign the keymove to ")" which isn't even a key but part of a description for another key "keyname"(T8).

I also tried using the remoted built in keymover. I can select the source device and key fine, but when I press the "shift" key to assign the destination I get an "invalid" message appear on the lcd. So I can move to normal keys, just not shifted keys as I want.

Finally I tried your method Rob. Didn't work either, the device name on the lcd didn't change. I think doing it as a macro makes the device just execute any efc attached to that button rather than executing the internal command associated with that button. Just a guess.

[The Robman]

You're definitely doing something wrong, as the macro method does work. Also, the Toplines work the same as the Producer remotes as far as SHIFTing is concerned. When you program a keymove to a shifted key, you need to use the SETUP/MAGIC button as the shifter, not the official shift key.

Read this...
http://www.hifi-remote.com/manuals/p8/o ... 9800#shift

[mr_d_p_gumby]

I've tried using keymoves but unfortunatly there seems to be a bug in IR where it seems to select the wrong key. If I choose say the "20" key it will assign the keymove to ")" which isn't even a key but part of a description for another key "keyname"(T8).

There are some errors in the RDF file for this remote that are causing the display of the button names in IR to be corrupt. If you edit the RDF file and put quotes around the offending items, you'll be able to see the proper key names. In the [Buttons] section, look for key names with parenthesis in them, and add the quotes.

For example:

Code: Select all

"pip on/off":(T8)-PIP{Freeze}=$32

should be changed to

Code: Select all

"pip on/off":"(T8)-PIP{Freeze}"=$32

Nils (official keeper of the RDF files 8) ) will hopefully see this post & fix this for the next release.

[Teleport]

Thanks Rob- I'll try pressing the "Magic" key instead of the "Shift" key.

Will this then move the key to say "shift""2" or "Magic""2"?

Thanks Mike - I'll have a go at editing my copy of the RDF.

I'm off to try again.

[johnsfine]

Will this then move the key to say "shift""2" or "Magic""2"?

Keys defined using Magic are used using Magic. But I think you need to press Magic twice to use the "shifted" meaning of a digit (at least it works that way in models I understand. I know little about your model). I don't think that double press of Magic is required when defining the "shifted" key. It's not required when using shifted non-digit keys.

[The Robman]

Tele,
Like John said, if you define a keymove onto a shifted numeric button, you will need to press SETUP (aka MAGIC) twice in order to use the shifted button. This is because if you just press it once, the remote will think that you are trying to test an EFC code using the SETUP+nnn method.

However, if you do what I suggest and utilize one of the 3 missing device buttons, this won't be an issue.

[Teleport]

I've tried using keymoves but unfortunatly there seems to be a bug in IR where it seems to select the wrong key. If I choose say the "20" key it will assign the keymove to ")" which isn't even a key but part of a description for another key "keyname"(T8).

There are some errors in the RDF file for this remote that are causing the display of the button names in IR to be corrupt. If you edit the RDF file and put quotes around the offending items, you'll be able to see the proper key names. In the [Buttons] section, look for key names with parenthesis in them, and add the quotes.

For example:

Code: Select all

"pip on/off":(T8)-PIP{Freeze}=$32

should be changed to

Code: Select all

"pip on/off":"(T8)-PIP{Freeze}"=$32

Nils (official keeper of the RDF files 8) ) will hopefully see this post & fix this for the next release.

Thanks Mike - Do you mean buy this that if there is a : in the button definition any text after it but before a = should be enclosed in quotation marks? Not sure what I should and shouldn't be changing.

Unfortunatly I can't reliably try your method (which I'm sure does work) as every time I try to define a macro in IR it changes the keyname to "T8"

The keymoves seem to be working if I program them on the remote using the "Magic" key. Only one press of the "magic" key seems to be required.

But unfortunatly I have to press the "magic" key before every command where as I was hoping to press the "shift" button (making the little S in the box appear on the lcd) and just operate the projector that way.

Thanks for all your advice on this one guys. I'll see if I can lick this rdf corruption problem and try robs method. I'll let you know how I get on.

[The Robman]

I just took a look at the URC-8550 RDF and there are several mistakes. I have corrected as many of them as I could see and have loaded revised RDFs into the RDF folder. I don't have the ability to verify if these RDFs still work with RM.

ET80ET80 (URC-8550_5550 Topline).rdf
ET80ET80 (URC-8550_5550 Extender).rdf

[Teleport]

Cheers Rob. (so basically every button describes with lower case letters requires "" while upper case doesn't. As I knoe little of programming I won't ask.

I'll give em a try.

I got your method to work now. Pressing the "Magic" key then "enter"now gives me access to @AUX2. Great. I think these corrupt rdfs might be why my DVD upgrade isn't working fully on my Topline (while it works perfectly on my URC-8910). Strange the other upgrades work fine though.

Just out of curiosity, is there some reason why Shifted functions programmed with IR have to use the "Magic" key and not the dedicated "Shift" on the Topline?

Thanks Again

[The Robman]

Just out of curiosity, is there some reason why Shifted functions programmed with IR have to use the "Magic" key and not the dedicated "Shift" on the Topline?

Short answer: that's just how the remote's are programmed.

Longer answer: the SHIFT button is used to access the labelled shifted buttons, which are included as part of the built in setup codes themselves (eg, SLEEP = shifted POWER, etc) The MAGIC button is used to access user-programmed keymoves that are on shifted buttons.