Entering RC5 Codes

GeorgeIoak · Post by **GeorgeIoak** » Thu Dec 11, 2003 10:14 am

This seems like a simple task and I've looked through the documents but I guess I must have missed the explanation somewhere.

I have a piece of equipment that operates with RC5 codes. I have been given the "system address" ID (RC5 address = 4 (0x04)) and a list of the commands:

STOP 0
FF 1
REW 2
SKIP+ 3
SKIP- 4
PLAY 5
PAUSE 6

When I open the KeyMap spreadsheet and change the protocol I am given 3 Device Boxes (Device1, Device2, ...) but I don't see where you would just enter the system address.

Could someone give me a little help or even better send me an example KM so I can look how another RC5 product is entered in the spreadsheet.

Thanks!!

George

johnsfine · Post by **johnsfine** » Thu Dec 11, 2003 10:54 am

For RC5 one setup codes supports half the possible OBC (command) numbers for three system addresses.

In any device box you put a system address to support OBC numbers 0 to 63 or put 100 plus the system address for OBC numbers 64 to 127.

So you would put 4 in the first device box and you might also need 104 in the second device box.

Then on the functions sheet put in the OBC number, and if that OBC should be used with a device box other than the first, you put a '1' in the byte2 column to use the second device box or a '2' in byte2 for the third.

Remember to switch KM to OBC mode rather than EFC mode.

Summary if you need all sytem address 4:

Device1 = 4
Device2 = 104

OBC column = command
BYTE2 column = blank when command < 64
BYTE2 column = 1 when command >= 64

GeorgeIoak · Post by **GeorgeIoak** » Thu Dec 11, 2003 12:30 pm

thanks, this is just the "kick start" information i was looking for

Post by **The Robman** » Thu Dec 11, 2003 1:11 pm

For future reference, this was explained in the protocols file that is included in the KM zip. Here's the section in question...

RC-5 (1-byte):
--------------
RC-5 is a quickie combo protocol, allowing you to combine up to
three RC-5 device codes. You select which device code you wish a
function to use by entering the OBC in the OBC column of the
Functions sheet, and then entering a "0", "1", or "2" in the byte2
column. However, you will only have access to OBC's 0 - 63. In
order to access OBC's in the range 64 - 127, you will need to add
100 to the device code entered.

For example, if you wish to program functions using RC-5, device
code 4, and you wish to use OBC's 0 - 63, you would set it up as
follows:

Device Code 1 = 4
Device Code 2 = 104 (4 + 100)
Parm/Dev3 = doesn't matter (see note)

Then, to program a function with an OBC in the range 0 - 63, you
would leave the byte2 column blank, and to program a function in
the range 64 - 127, you would enter "1" in the byte2 column.

NOTE: You can also combine a third set of codes by supplying a
value in the Parm/Dev3 cell, but you can only use one range of
OBC's.

GeorgeIoak · Post by **GeorgeIoak** » Thu Dec 11, 2003 5:49 pm

I'm having a bit of some trouble. When you are entering your commands should everything be in HEX or in decimal? Entering a number in decimal does not produce the correct hex value (entering 50 does not produce 0x32).

Thanks in advance for your help

johnsfine · Post by **johnsfine** » Thu Dec 11, 2003 5:55 pm

The OBC column must have decimal values. If the published data you started with is in hex you need to translate to decimal.

The hex column is NOT the hex value of the OBC. It is the hex value of the internal command used to generate the OBC, which varies by protocol. For RC-5 it happens to be the hex value of (255 - 4*OBC + byte2).

Mark Pierson · Post by **Mark Pierson** » Thu Dec 11, 2003 6:58 pm

The Robman wrote:For future reference, this was explained in the protocols file that is included in the KM zip.

And it will be on the Protocol Help sheet (where it should have been) in the next release of KM.