JP1 Remotes

Posted: **Sat Dec 13, 2003 8:42 am**

OK, I read Hal's readme. Here's the interesting parts:

Key Illumination and Device Key Animation
-----------------------------------------

  2133 illuminates set of the keys that are available in the current device
mode and animates the device key corresponds to the current device index.

  In this extender, the O_ device selection commands decide what keys to
illuminate and to animate.  You can put a macro that includes an O_ command on
any button, however, the remote animates the device key which corresponds to
the O device index instead of the key that has the macro.

Also from the original thread:

There are a couple of things that I considered but didn't put in. I
might
include them in the next version or variant based on your feedback.

- Enabling non-illuminated keys. I prototyped it, and I find it
not so
bad as I previously thought, but it is confusing in general.

This leads me to believe that only the buttons in the ButtonMap are ever available.

Posted: **Sun Dec 14, 2003 8:36 pm**

Ron, can you confirm that with the URC-8060, only the buttons highlighted with an orange border in RM are available for use with keymoves and/or macros for a given device type? And that these correspond to the keys that are illuminated for that device type?

I suppose the possible exception to that would be the device keys.

Posted: **Mon Dec 15, 2003 1:15 am**

absolutely correct - you can only do 'key moves' on the selected screen(s) i.e those keys circled in orange and the dummy keys added by Nils. If you try a move on the non-illuminated screens - it doesn't happen.

It may help you to know (as if you didn't know already!!) that each device has up to 3 screens availiable to it, accessed by using a scroll button situated between the magic and power buttons - This is not a shift but gives more working buttons for each device. eg TV has 3 screens, VCR has 2 screens, DVD has 1 screen, SAT has 3 screens, AUD has 1 screen, CD has 1 screen.

Ron

Posted: **Mon Dec 15, 2003 8:54 am**

Let me summarize what I think I've learned, and ask some additional questions:

Using the remote, keymoves can only be programmed onto illuminated keys. What about using IR? I'm sure it allows key moves onto non-illuminated keys, but I'm guessing they can't actually be used?
The illuminated keys for a given device type correspond to the ButtonMap (as shown by the orange border in RM).
The remote uses multiple screens with only some keys illuminated on each screen. Is there overlap between iluminated keys on different screens? RM draws a border around all these keys at once, which in effect merges all the screens together?

Maybe the best thing to do would be for you to document which keys are illuminated on each to the TV mode's 3 screens. Maybe that will give me a better understanding of how things work.

Posted: **Mon Dec 15, 2003 10:53 am**

answer to 1- yes IR accepts key moves but they only work on illuminated buttons

answer to 2 - yes

answer to 3 - yes illustrated as follows.

TV Screen 1 (illuminated)
*... 1-2-3-4-5-6-7-8-9-0
*... >10
*... mute
*... vol+ - vol-
*... ch+ - ch-
*... menu
exit
up - down - right - left
ok
*... red - green - yellow - blue
*... M1 - M2 - M3 - M4

TV Screen 2 (illuminated)
*...1-2-3-4-5-6-7-8-9-0
*... >10
av
pp
*... menu
*... ch+ - ch-
*... vol+ - vol-
*... mute
*... teletext
*... red - green - yellow - blue
16:9
*... M1 - M2 - M3 - M4

TV Screen 3 (illuminated)
*... 1-2-3-4-5-6-7-8-9-0
* ...vol+ - vol-
*...mute
*... ch+ - ch-
text index
text expand
text mix
text hold
text off
*... red - green - yellow - blue
*... M1 - M2 - M3 - M4

lines of buttons above prefixed thus * .... do the same action in each screen on which they appear.

Ron

Posted: **Tue Dec 16, 2003 10:48 am**

OK, I have an idea about how to handle this multi-screen thing.

I'm thinking a new [Screens] section, similar to the [ButtonMaps] section, and which also has an entry for each DeviceType, using the same device type index.

Each entry would be a sequence of screen definitions, separated by commas. Each screen definition would be enclosed in braces, also like the ButtonMaps. The first item in the definition would be an optional image file to use instead of the one in the .map file, followed by a colon, followed by a comma separated list of the keycodes for keys that are available on that screen. Each keycode could have an optional text value assigned, which would be a unique display name for that key on that screen for that device type.

For example, given the above information from Ron, we would have:

Code: Select all

...
[Screens]
0={URC8060-TV-1.jpg: $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E, $1F, $61, $04, $05, $06, $07, $08, $14, $26, $29, $2A, $2B, $2C, $27, $0B, $0C, $0D, $0E, $2D, $2E, $2F, $30},
  {URC8060-TV-2.jpg: $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E, $1F, $61, $12=AV, $34, $04, $05, $06, $07, $08, $71, $14, $0B, $0C, $0D, $0E, $13="16:9", $2D, $2E, $2F, $30},
  {URC8060-TV-3.jpg: $15, $16, $17, $19, $1A, $1B, $1C, $1D, $1E, $1F, $04, $05, $06, $07, $08, $72, $73, $4f, $50, $0B, $0C, $0D, $0E, $2D, $2E, $2F, $30 }
...

We use 0= because that is the ButtonMap index associated with the TV device type. The rest I've explained above.

This would be used primarily for the Layout panel, but could also be used by the Button panel, to further restrict the buttons that can be assigned a function in a given device type, although a better way to do that might be some sort of flag in the [General] section, such as

OnlyEnableKeysInButtonMap=1

which would be something IR could use as well.

JP1 Remotes

Button maps, RM and the URC-8060