Page 1 of 1
15-2117 remote question
Posted: Mon Sep 29, 2003 11:33 am
by Mr Z|P
I'm almost positive this isn't documented anywhere.
1. What are the db-08 through db-14 used for.
2. What are the following used for:
x_tv
t_tv = transport ( meaning what?)
v_tv = set volume punch through
c_tv = channel device
m_tv = menu device
o_tv
Posted: Mon Sep 29, 2003 12:03 pm
by johnsfine
x_tv etc. are used just for the extender. You didn't mention whether you were using an extender. If you're not using an extender make sure you're not using the extender's RDF file (without which you shouldn see x_tv etc.).
Each of T, V, C, M and O represent a group of keys. For example the T (transport) group is play, pause, FF, REW, stop, and record.
Without the extender, each device key is a direct command to put all other keys in the mode associated with that device. With the extender, V_TV is a command to put just the V keys (Vol+, Vol- and Mute) in the TV mode, leaving all other keys in whatever mode they were in before.
By using V_TV, T_VCR, etc. in macros you can customize a mixture of device modes more flexible than the "My System" (Home Theater) mode that is in some UEI remotes or the volume punch through and/or transport punch through of some models.
Posted: Mon Sep 29, 2003 2:32 pm
by The Robman
The answer to Q1 is, we don't know.
Posted: Wed Oct 29, 2003 10:35 pm
by Lenroc
Maybe I'm missing something, but aren't DB08-DB14 (question 1, above) used as "Virtual Devices", that don't have physical buttons?
This seems to be somewhat explained in the ReadMe that comes with the 15-2116/7 extender #2. Here is an exceprt:
The device selection mechanism supports the following:
8 phycial device indexes:
TV, VCR, CBL, SAT, CD, DVD, AUX, and AUD
7 logical device indexes:
db-08, db-09, db-10, db-11, db-12, db-13, and db-14
6 key sets:
Menu, Channel, Volume, Transport, Other and PIP
Or were you simply saying that you don't know how to
use them, as I certainly dont??
Posted: Thu Oct 30, 2003 1:51 am
by sfhub
Most of db-08 through db-14 are occupied by extender2. The ones that
aren't, I assign devices which don't have need keymoves. Keymoves are
not supported for those devices. In particular, many of my devices have
custom display names, which require a keymove. I assign these to the
actual devices.
Posted: Thu Oct 30, 2003 2:04 am
by Lenroc
Yes, I just learned some of that.
Well, actually, I was just getting frustrated by the fact that I would make a Keymove on dbxx, upload to the remote, download from the remote and... the keymove would be on a different device!
I just used some unoccupied buttons on a real device, and that worked
Posted: Thu Oct 30, 2003 10:23 am
by The Robman
Lenroc wrote:Yes, I just learned some of that.
Well, actually, I was just getting frustrated by the fact that I would make a Keymove on dbxx, upload to the remote, download from the remote and... the keymove would be on a different device!
I just used some unoccupied buttons on a real device, and that worked
From your description, it sounds like what you are looking for are "phantom keys". I'm guessing that you only want to use these keymoves in macros? If that's the case, rather than using up real buttons, program the keymoves to phantom buttons.
Posted: Thu Oct 30, 2003 10:33 am
by Lenroc
You're probably right. I skipped them last night because I thought there were only 5.... now I realize there are 15 in practice (shift, x_shift...).
Thanks for the suggestion.