Linking physicals key to phantom keys
Moderator: Moderators
Linking physicals key to phantom keys
I would like to press key x while in cable mode and have it activate a macro on the phantom1 key. This would then make key x available for other uses in other modes. If this is the right way to keep a macro from being globle, how do I link key x with key phontom1?
If you are simply trying to keep a macro from being global, you can generally use Device Specific Macros (DSMs). I'm not sure about the availability of such a feature on your remote though, they may only be available with an extender...JohnParks wrote:If this is the right way to keep a macro from being globle
Besides, I'm not sure if what you described would work otherwise. One of the "experts" here would know better, but I'm not sure if a keymove on one key will execute a macro on another (which is what I think you were saying).
e.g. (using arbitrary keys)
Code: Select all
Phantom1 (macro) = TV; Ch+; Mute
CBL:Info (keymove) = TV:Phantom1
Matt
You can get the Device Specific Macros protocol from the special protocols spreadsheet.
The KeyMove mentioned in the previous message must use the setup code of the device upgrade installed for DSM and must use a hex command equal to the keycode of phantom1 (which the special protocols spreadsheet will display for you).
There is a different (simpler) DSM method used with extenders. Consult your extender documentation if you are using an extender.
The KeyMove mentioned in the previous message must use the setup code of the device upgrade installed for DSM and must use a hex command equal to the keycode of phantom1 (which the special protocols spreadsheet will display for you).
There is a different (simpler) DSM method used with extenders. Consult your extender documentation if you are using an extender.
Should I just bite the bullet and get an extender? My intention was to do everything I could without using exteders, before putting them on an already steep learning curve. Besides this situation I have some others in which toadtags might be appropriate, though from posts their effectiveness seems questionable.johnsfine wrote:There is a different (simpler) DSM method used with extenders. Consult your extender documentation if you are using an extender.
I am using a urc-6131 with updated device codes.
Get an extender.
Earlier I missed the fact that this was a 6131. Even for a remote with normal KeyMove behavior, there is no reason to waste time learning and constructing the non extender version of DSM's, if you later intend to use the extender.
I hope the 6131 extender supports the typical extender DSMs (I haven't looked). I believe the 6131 does NOT support the typical non extender DSMs. I think non extender DSMs on a 6131 would be somewhere between harder and "forget it".
Earlier I missed the fact that this was a 6131. Even for a remote with normal KeyMove behavior, there is no reason to waste time learning and constructing the non extender version of DSM's, if you later intend to use the extender.
I hope the 6131 extender supports the typical extender DSMs (I haven't looked). I believe the 6131 does NOT support the typical non extender DSMs. I think non extender DSMs on a 6131 would be somewhere between harder and "forget it".
Will at least the choices aren't overwhelming, this was the only one I found at the Yahoo site. It seems to have even the kitchen sink.johnsfine wrote:Get an extender.
6131ex1.zip Fast/nested macros, flexible device selection, optional second shift key, multibyte key moves. ToadTog, Device Specific Macros, Pause, Device Multiplexer, Long/Double Key Press special protocols included. ***Does NOT support unextended remote's new key move format. Create key moves in the same way as other remotes instead.
Hope you're around when my remote starts smoking. Thanks much for your help thus far!!!