Issue using RC5-5x combo protocol in KM

impius · Post by **impius** » Mon Apr 17, 2006 2:30 pm

I'm working on a device upgrade for a Marantz SR-7000 Receiver as the only ones out there are for SR-7200 (quite a bit newer). I've started with the SR-7200 upgrade as many of the functions work correctly.

See https://www.hifi-remote.com/forums/dload ... ile_id=454

I've also found that code 1189 works ok but is missing functions as well.

In attempting to add the cursor and select functions (up, down, select etc.) I've run into a situation where KM creates two identical commands.

Example:

Vol+: OBC 016
Up: OBC 080

Once I toss the upgrade into IR, I find that the Hex and EFC (under devices) for these two keys are identical. Likewise, during a test, both keys perform the same function (raising volume).

What's even more confusing is the result of learning the cursor keys from the orignal remote.

Up: Proto RC5, Device 16, OBC 80, Hex BC or BD or BE, EFC 175 or 167 or 191, Misc T=1 ??

I have no idea how to use this to create a working upgrade.

I'd also like to know how to copy functions out of 1189 and use them in my upgrade.

I'm stuck at the moment. I would much rather use a full device upgrade over using several learned keys.

Thank you,

Ian

Post by **The Robman** » Mon Apr 17, 2006 4:07 pm

It's good that you mentioned that you are using the RC-5 protocol as this totally lets an expert know what's going on.

In KM there is a tab called "Protocol Help" that explains how to enter data for the currently selected protocol, so re-open your upgrade using KM and take a look.

The bottom line is that, because of how UEI implemented the RC-5 protocol, it only accepts OBCs in the range 0-63. If you want to use OBCs in the upper range (ie, 64-127) you need to do some extra work.

You should have already entered 16 in the "device 1" cell on the setup sheet. This is enough for you to program OBCs in the 0-63 range. To program OBCs in the 64-127 range, you will need to enter a 2nd device code of 116 (ie, 16 plus 100), then in the Functions sheet, for any functions that have an OBC > 63 enter a "1" in the byte2 column.

impius · Post by **impius** » Mon Apr 17, 2006 5:14 pm

Rob,

Interesting.. The protocol help sheet mentions nothing of the < 64 limitation. The setup sheet hints at this but I assumed it had to do with RC-5x.

As there's already a 17 in the dev2 box. I tried adding 116 to dev3 and referencing that with a byte2: 2, but that didn't work (the hex now differs but the device does not respond to the functions).

If you look at the upgrade I referenced, the functions sheet is all over the place. Byte2 follows formats that seem to match the RC-5x device/unit format and others that are a single byte. I can't make any sense of it.

Still not working, but enlightened nonetheless.

Thank you,

Ian

Post by **The Robman** » Mon Apr 17, 2006 5:39 pm

impius wrote:Rob, Interesting.. The protocol help sheet mentions nothing of the < 64 limitation. The setup sheet hints at this but I assumed it had to do with RC-5x.

Just to make sure that we're looking at the same thing, here's a quote from the Protocol Helb tab in my version of KM when the RC-5 protocol is selected...

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:

Device1 = 4
Device2 = 104 (4 + 100)
Device3 = 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 Device3 cell, but you can only use one range of OBC's.

If you need to combine more than three RC5 codes, or if you
would also like to combine some RC5x codes, use the RC5/5x
Combo protocol.

impius wrote:If you look at the upgrade I referenced, the functions sheet is all over the place. Byte2 follows formats that seem to match the RC-5x device/unit format and others that are a single byte. I can't make any sense of it.

A-ha, I didn't look at the upgrade before so I didn't know that it is using the RC-5/5x Combo protocol, and I see that the protocol help section doesn't mention the OBC issue for this version of the protocol. Furthermore, KM isn't coded to handle OBCs over 63 for RC-5 signals using the combo, so somebody will need to take a look at fixing this in K (probably me). I just checked RM and it can handle OBCs > 63 so you could switch over to RM if you want.

I have just fixed KM (v8.40) so that it handles OBCs > 63 for RC-5 signals with the combo protocol.

impius · Post by **impius** » Mon Apr 17, 2006 7:10 pm

Thanks Rob. RM did the trick. ... and just when I was getting comfortable with KM

Post by **The Robman** » Mon Apr 17, 2006 7:53 pm

Now you have a choice of upgrade editors.