Page 6 of 8

Posted: Tue Aug 03, 2004 10:15 am
by RichardP
OK Nils,

It's on its way ....

Nothing sent from info key?

Posted: Fri Aug 27, 2004 3:00 pm
by Mog
I have recently bought a Humax 8000T PVR :)

So, I have programmed it onto a SAT device, as it has the PVR screen
One of the keys I really want to use on the PVR is the 'info' key - but
I don't get anything sent from this key when using the 8060 extender

The -/--,back,>10 key does send data (it sends the code associated with the
-/-- function, regardless of screen scrolled to),
but the select,info,AV doesn't send anything on any screen :?

Is this to be expected?

Also, should I expect to be able to send a different code with these keys,
depending on which screen I scroll to?

Re: Nothing sent from info key?

Posted: Fri Aug 27, 2004 4:46 pm
by Mark Pierson
Mog wrote:So, I have programmed it onto a SAT device, as it has the PVR screen One of the keys I really want to use on the PVR is the 'info' key - but I don't get anything sent from this key when using the 8060 extender
Are you using a built-in setup code or an upgrade? If it's built-in, then it's possible that the Info button has nothing mapped to it.
Also, should I expect to be able to send a different code with these keys, depending on which screen I scroll to?
If the same button appears on multiple screens in a given device mode, it sends the same signal.

Re: Nothing sent from info key?

Posted: Sat Aug 28, 2004 2:24 am
by RichardP
Mog wrote:I have recently bought a Humax 8000T PVR :)

So, I have programmed it onto a SAT device, as it has the PVR screen
One of the keys I really want to use on the PVR is the 'info' key - but
I don't get anything sent from this key when using the 8060 extender

The -/--,back,>10 key does send data (it sends the code associated with the
-/-- function, regardless of screen scrolled to),
but the select,info,AV doesn't send anything on any screen :?

Is this to be expected?
I use the 'Info' button on the extended 8060 using Sky and Sky+ and it works fine for me when mapped to the AV{input-select} key, so I don't see why it shouldn't work for the Humax. Have you tried programing some other cammand that you know works on another key?
Mog wrote: Also, should I expect to be able to send a different code with these keys,
depending on which screen I scroll to?
Thats the way it works I'm afraid, there are actually very few keys that change within a device (on the UK version anyway), the back, -/-- and Play,Text and Record,Text Off keys for the Sat device is all I can think of. I guess you could code this manually using a ToadTog, but I don't use Teletext anyway and the Back key would only duplicate the Exit function so I didn't see the point for mine.

Now I see what's happening...

Posted: Sat Aug 28, 2004 10:37 am
by Mog
Ah! Now I get it :)

The reason there is a problem is because there are two codes
allocated for one key :?

In my RDF there are two codes for the select / info / AV key,
AV{input-select}=$12
display:Info=$52
Key $52 is the one referenced in the ButtonMap

When using KM, I allocated the info operation to the info button
(the AV button is not in the available button list)
So, when imported into IR, I see the same thing - there is an info button,
and the correct code is associated with it.

However, when I press the key on the remote, the AV key is processed,
not the info key, and as this has no associated code, nothing is transmitted

So, adding a suitable keymove on the AV key solves my problem :)

The -/-- / back / >10 button, by contrast, only has the one code,
and works as expected

Nils - I guess this is a (small) bug ?

RichardP - thanks for your reply, which gave me the clues I needed! :)

Posted: Thu Jan 12, 2006 3:21 pm
by frejac
Hi. I've just installed the extender and a breif test shows that most things seems to work fine.

But I have a problem with keymoves with my SAT device...

In my pre-extender config I have pvr, teletext-off and subtitle mapped to some hex-values I've done trial-and-error (in IR) on before to find, as they arent defined by default (on any button I could find).

With the extender setup they have been renamed to Key102, Key114 and Key 85. They dont work. I cant seem to find the old labels in IR. What can I do to make them work as before?

Also there are some things in IR that I dont understand, but I'll try to read up on those somewhere. But I'll post some examples here:
1.
Other setting - T Device (set to TV).
From the readme I guess that the T comes from the word Transport? (Pip, Menu, Channel, Volume, Transport, Other and Temporary(X)) But what does it do? I dont get it..Transport means nothing to me..same for V device, C device and the others. All currently to TV.
2.
TPT. I've seen the term in the readme - but what is it? (I know what VPT is)

3. Phantom and Descrete keys?

Thanks for helping. :)

Posted: Thu Jan 12, 2006 4:02 pm
by Nils_Ekberg
Within the remote the teletext and a few other buttons look like they are actually the transport buttons so assign you functions to them and even when the teletext buttons are showing they should work.

Within the readme it outlines what buttons are in which groups. For example the play, FF, rewind etc are in the T (transport) group. Volume up/down and mute are in the V (Volume) group etc. When you set up a macro to select the device you can mix and match them for example you may want all the TV functions like menu, pip and so on when you are in TV mode but you may still want the volume to be for the home theater systems which is in the DVD device. So, you would put all the _TV options in the macro but the V_DVD in there also.

X_device is just a temporary way to get to a device and execute something but stay in the device you are in. Say for instance you are in TV device but you want to execute a DVD command would would make a macro like X_DVD;Play. It temporarily switches to DVD executes the play then comes back to TV.

TPT is the same as VPT just for the transport buttons.

Phantom and discrete buttons are just buttons that are within the remote but not associated to a physical button. The are good to put a function on and call it from a macro without wasting a real button.

I hope that helps.

Posted: Thu Jan 12, 2006 4:21 pm
by frejac
Thanks for the swift answer. Appreciated.

Ok, so now the phantom/discrete/tpt/X_device are crystal clear to me. Great. Many thanks.

Now it's mostly the settings from IR's first page/tab that I cant understand:
Other setting - T Device (set to TV). I understand the macros as you described. But not these settings... the device settings in the upper right part of the picture:
http://www.jacobsson.nu/temp/extender/extender.JPG

I also put up pictures of my keymoves before the extender installation:
http://www.jacobsson.nu/temp/extender/pre_extender.JPG

as well as after:
http://www.jacobsson.nu/temp/extender/post_extender.JPG

I still quite dont get it what I need to activate those again. :)

Again. Thanks.

Posted: Thu Jan 12, 2006 5:09 pm
by Nils_Ekberg
The settings on the main panel are just what you want the defaults to be. If you add any T_, V_, P_ etc. commands in a macro they override what you set on the main panel. In other words they are the defaults for each function group. If you set DVD to Volume on the main panel and never include a V_device in a macro then the V_DVD is always in effect. In other words volume punch through. With the extender you can do punch through for any function group. For instance if you always wanted to pip function to work on the TV no mater what device you are in you set TV to be the PIP device and never include P_ in a macro.

As far as your keymoves go the reason they don't work is because in the base remote they are required to be 2 bytes hence the reason for $00 $26. In the extended remote I eliminated that problem so only one byte is required. If I remember correctly for example you just remove the 00 and enter only the 26 (2nd byte) it should work.

Posted: Thu Jan 12, 2006 5:19 pm
by frejac
Thanks. I'll try it tomorrow.

Does that mean that I can could keep the "Bound key" for my keymove? (showing Key85 for example)

Posted: Thu Jan 12, 2006 5:45 pm
by Nils_Ekberg
frejac wrote:Thanks. I'll try it tomorrow.

Does that mean that I can could keep the "Bound key" for my keymove? (showing Key85 for example)
No, those were the ones I suggested moving to the transport buttons because not all of the teletext buttons are available in the extender. If the transport buttons show in the device you are using they will act just like the teletext buttons then.

Just a compromise I had to make in the extender.

Posted: Thu Jan 12, 2006 6:08 pm
by frejac
Okies, thanks for the clarification.

Posted: Sat Jan 14, 2006 2:00 pm
by frejac
Is there a KM version that can handle extenders? Mening having the button-definitions of the extender. As well as support for the extra shifts.

Just curious. Thanks.

By the way...the backlight hack is great. Hightly appreciated!

Posted: Sat Jan 14, 2006 2:42 pm
by greenough1
I don't think so. If there was I'm not sure how'd it work within the KM framework.

I do all the macro programming (key assignments, etc.) within IR after I've gotten all my upgrades loaded and buttons/function mapped. If there's a KM based way, can someone let us know about it.

You have to refer to the extender doc's for the functionality. IR's pulldowns show you what keys you can select.

Hope this helps,
jeff

Posted: Sat Jan 14, 2006 3:01 pm
by frejac
Okies. Thanks. Was just a little whishful thinking. :)

I'll check what buttons that are excluded and take them out from my mappings in KM to make the basic stuff be the same. I like to have KM as a register of where I have functions. Now some functions are on disabled buttons, so that'll fix it.

Then I'll play in IR.