Key Moves
|
Back to IR Help Index |
Previous Topic Macros |
Next Topic: Learned Signals |
Key moves are another useful feature in the UEI remotes.
This feature is typically used to:
- add functions that are not part of the basic setup.
- simulate punch through to another device.
- block access to functions that are in the device mode setup code.
- combining two pieces of equipment in one device mode when a remote doesn't have enough device buttons for each device to have its own and a multiplexer isn't feasible.
You can either copy keys from one device to another or setup new functions using EFCs.
For example: On my system I wanted to prevent anybody from accidentally turning off the satellite box, when they meant to turn off the TV. So I KeyMoved the TV power button to the satellite power button to prevent my family from accidentally turning off satellite box.
KeyMoves can also be created manually using the 994-command. You can read more about 994 commands in Chapter 5.
From this screen you have the ability the Edit, Add, Clone (partially copy), Delete or Import from RM or ExtenderCodeCalculator.xls.
|
|
You assign a bound key, it can be shifted, or with some extenders it can be x shifted.
You can select from one of the device mode and setup from any of the device modes that you have assigned to your device buttons, or you can select any other device type/setup code that actually exists in the UEI built in library, or any upgrade devices that you have added with Keymap-Master or RemoteMaster. If you hand type in a code that does not exist in your remote, your remote may hang up. |
There are three types of keymoves. EFC, HEX commands and Key(code). KeyCode type keymoves were introduced at the end of the EEPROM era, but are pretty standard on FLASH type remotes. A KeyCode type keymove, lets you send any key that is defined in a setup code.
An EFC style keymove allows you to add functions that may or may not be defined in a setup code. On remotes that take both types of keymoves, EFC style keymoves take 1 more byte of keymove/macro space, than keyCode type keymoves. If the setup code is an upgrade, assigning the functions to buttons so they can be used by keycode type keymoves will take up extra bytes in the upgrade area.
The Hex option, is set up for adding special protocols that are not supported by the special protocols tab.
See Chapter 5 for more information on finding EFC codes.
Note: Remotes designed around 2005, when UEI was transition from 3 digit EFCs to 5 digit EFCs have some problems with EFC style keymoves. The last few JP1 remotes and the first JP1.2 remotes have some issues with keymoves.
The JP1 SA_7SA_7 Atlas and PVR0PVR0 OneForAll URC-6131 remotes can't do EFC style keymoves at all, but they can do keycode style keymoves.
The JP1 KASAKAS0 OneForAll URC-9960B01 and the JP1.2 CS301009 Comcast can't do EFC style keymoves where the EFC is above 65535.
