JP1 Remotes

silron1 wrote:Is there a way of setting when the remote low batt. warning message comes on.

I have it defined on a button and it comes on when pressed but it does not appear to come on by itself.

With all the use on the new extender my batts got really low but the warning did not appear.

I will have to look for it. How do you have it defined to a button?

silron1 wrote:Is there a way of setting when the remote low batt. warning message comes on.

I have it defined on a button and it comes on when pressed but it does not appear to come on by itself.

With all the use on the new extender my batts got really low but the warning did not appear.

I was not aware that there was a low battery warning, how do you access it and what does it do to indicate a low battery?

The low batt message was picked up from the Sky Remote

EFC 248 - OBC 71 - Hex 47

I assigned this to a button on the 8060 which produces the low batt warning on screen.

However now that I thought about it a little more I think the code only sends the message as opposed to something being activated within the remote as happens in the Sky remote.

silron1 wrote:The low batt message was picked up from the Sky Remote
EFC 248 - OBC 71 - Hex 47
I assigned this to a button on the 8060 which produces the low batt warning on screen.

However now that I thought about it a little more I think the code only sends the message as opposed to something being activated within the remote as happens in the Sky remote.

I will see what I can figure out. I know the 8060, 9960, 2133, and the 8040 have a built in routine that blinks the backlight when battery is low. I don't believe I stopped this in any fashion since I hit it when writing the 9960 extender and it was running in the remote. I will have to try to figure out if there is an early warning routine that I can test.

Following on from the 'low battery in remote' message.

Assigning EFC 080 - OBC 72 - Hex 48 to a button in the Sky Digibox device shows a message 'low batteries in keyboard' (there is an optional extra keyboard availiable from Sky to replace the remote).

I do not use the keyboard so this message comes up everytime I access Sky Digibox via the 8060. Perhaps suggesting the message appears because the Digibox cannot find a keyboard to assess and is reporting a low battery.

Can't quite grasp the relationship between the 8060 extender and the digibox with these low batt. warnings.

silron1 wrote:Following on from the 'low battery in remote' message.

Assigning EFC 080 - OBC 72 - Hex 48 to a button in the Sky Digibox device shows a message 'low batteries in keyboard' (there is an optional extra keyboard availiable from Sky to replace the remote).

I do not use the keyboard so this message comes up everytime I access Sky Digibox via the 8060. Perhaps suggesting the message appears because the Digibox cannot find a keyboard to assess and is reporting a low battery.

Can't quite grasp the relationship between the 8060 extender and the digibox with these low batt. warnings.

I am assuming that what you are saying is that you don't get this message with the unextended remote. Is that correct?

Second, when you do get the message is it on the box or the display?

I suspect that that EFC is designed for the keyboard to send to the box indicating that it has a low battery. If that is the case it has no value when assigned to a button on the remote unless there was a way for us to trigger sending it when low battery is sensed in the remote. So far I have not figured out how to do that so I see no reason to assign it to a button.

All messages appears on the TV.

It's obviously me but I don't understand why the keyboard message always comes on but the remote message never come on even when the remote battery is low.

silron1 wrote:All messages appears on the TV.

It's obviously me but I don't understand why the keyboard message always comes on but the remote message never come on even when the remote battery is low.

As far as I can tell the only thing the remote does is flash the backlight on and off when the battery is low. If you keep trying to do things when that starts it just blinks faster.

Putting the EFC you have on a button will not do anything since the remote does not know to send that code when the battery is low. If you put it on a button and execute it yourself all it is doing is making the box think the keyboard battery is low. I assume the keyboard has a routine in it that sends that code when it is low. So, effectively having the EFC assigned in the remote is of no value.

Hi Nils,

would it be possible to implement a kind of scan protocol which allows scanning a list of keys up and down?

Something like this would be very handy for me because I have 12 discrete codes for DSP modes which never can be put on discrete keys. But it would be easy to scan through this list with up/down commands.

I propose the following cmd format:
first byte: upper nibble: commands (0=set; 1=up; 2=down; 3=push)
lower nibble: index to identify different scan sets

second byte: cmd=0: set index to specified value

For all commands except 0=set the bytes after the first byte contain the scan set. This allows to keep the protocol generic and everything else is controlled with the keymove.

Example:
01 0A = set index of scanset 1 to 10
11 20 21 22 23 24 25 26 27 28 29 2A 2B = issue 2A and increment index to 0B
21 20 21 22 23 24 25 26 27 28 29 2A 2B = issue 2B and decrement index to 0A
31 20 21 22 23 24 25 26 27 28 29 2A 2B = issue 2A

On the end of the list there is an automatic wrap to the beginning end of the list. Up to 16 distinct scan sets can be managed.

This protocol can also be used to simulate channel+ and channel- like on the remote without extender.

Emil

Let me think about this one. There may be an easy way to accomplish it.

Hi,

what are the key codes for the X-shifted Phantom keys?

It is possible to define them, but it seems to be not possible to use them in one of the special protocols with a hex code.

Emil

egn wrote:Hi,

what are the key codes for the X-shifted Phantom keys?

It is possible to define them, but it seems to be not possible to use them in one of the special protocols with a hex code.

Emil

There are none. If you look in the KeyCodes.txt you will see the only available xshited buttons ie. the only one available are the ones that have a code in the xshifted column. Reason being is those without would have conflicts with other buttons hex codes.

By the way, xshifted is base plus $C0

I refreshed the URC-8060 Extender 1 at jp1 URC-8060 Extender 1

Added:

• The fix for the ToadTog problem
  Updated RDF's to correct the PAUSE and RECORD buttons.

Nils_Ekberg wrote:

egn wrote:Hi,

what are the key codes for the X-shifted Phantom keys?

It is possible to define them, but it seems to be not possible to use them in one of the special protocols with a hex code.

Emil

There are none. If you look in the KeyCodes.txt you will see the only available xshited buttons ie. the only one available are the ones that have a code in the xshifted column. Reason being is those without would have conflicts with other buttons hex codes.

By the way, xshifted is base plus $C0

I've found that the expected values of

XShift Phantom 1 FA
XShift Phantom 2 FB
XShift Phantom 3 FC
XShift Phantom 4 FD

Work fine and don't seem to conflict with anything and are not defined in KeyCodes.txt, is there somthing I'm missing? In the KeyCodes.htm from the 2133 these values are used also.

Richard

Richard

They are probably fine. When I created the xshift list I generated the ones I knew were safe. I probably would have dug deaper if I thought that anyone would actually need more than 100 or so shifted and xshifted buttons.

Anyones you can dig out that don't conflict with other buttons either base or base plus $80 or base plus $C0 would be safe. A good guide is if IR will let you shift or xshift it, it should be safe.