Delphi SkyFi 2 and RadioShack 15-2117

[celeron876]

I have a RadioShack 15-2117 that I purchased and programmed using JP1 a few years ago. I recently purchased a Delphi SkyFi 2 satellite radio that I would like to add to my RadioShack remote.

I want to customize the buttons, so rather than download one of the pre-configured files, I would like the RadioShack to learn the buttons from the Delphi remote.

The first time through the process of having the RadioShack learn the Delphi remotes codes, I held the buttons on the Delphi remote down until the RadioShack displayed "success". I tested the RadioShack remote and the Delphi SkyFi 2 only accepts a command the first time I press a button. In other words, if I repeatedly press the up channel button on the remote, to flip through the channels, the Delphi SkyFi 2 only changes the channel one time. The Delphi remote works fine and does not exhibit this behavior.

Thinking maybe I pressed the buttons too long while in learning mode, I repeated learning mode and used a press and release technique, but it did not make a difference.

What am I doing wrong?

[myk7]

It sounds like it's toggling to me. Have you tried to build an upgrade with your learned codes? I had that problem once and an upgrade fixed the problem. Learned toggle codes don't seem to work, but the upgrade built from the learned signals worked great. Be sure to delete the learned keys though.

You could download the file and configure the buttons the way you like too.
Either way, you will have to configure things then upload to your remote.

[celeron876]

No, I haven't tried to build the upgrade. I'll try that and report back.

[Capn Trips]

It's definitely a toggle issue. The learned command will always send the signal exactly as learned, so the toggle will not switch, whilst a properly built upgrade (using decoded data and the proper protocol) will properly toggle your 2117's signal.

[celeron876]

I built an upgrade, but it doesn't work at all. I probably did something wrong, so I'll rebuild and try again. I did assign it to a button.

The original remote uses RC5. I've been reading on this forum about some RC5 toggling issues, but do not completely understand the circumstances.

[Capn Trips]

Have you deleted your learned signals? They will override your upgrade.

If you can't figure it out, upload and provide a link to
(a) your IR file with learned signals,
(b) your KM (or RM) file that you created and
(c) your IR file that you created and doesn't work right.

[celeron876]

Thanks for your help! Below are links to the requested files.

(a) your IR file with learned signals
http://bellsouthpwp.net/k/e/kesteele/learned.IR

(b) your KM (or RM) file that you created
http://bellsouthpwp.net/k/e/kesteele/km.txt

(c) your IR file that you created and doesn't work right
http://bellsouthpwp.net/k/e/kesteele/upgrade.IR

The problem I am experiencing is after performing the upgrade, the Delphi SkyFi 2 Satellite Radio does not respond to the RS 15-2117 remote at all. I'm using the "CD" button on the remote.

[Capn Trips]

If you look at your upgrade file in KM, you will see that the OBCs of the functions you define do NOT match the OBCs of the learned signals, meaning you chose the WRONG EFC from the three possible ones displayed in IR's learned tab. In those cases when IR gives you multiple possible EFCs, you should always use OBCs to build your upgrade.

Bottom Line: Use OBCs to build the upgrade in KM, not EFCs.

[celeron876]

I was unable to get OBC to work either, but I'll try again and upload the files.

[Capn Trips]

The protocol help worksheet in KM for the RC5 protocol pretty clearly states:

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.

So, if you used OBC's, AND FOLLOWED THE DIRECTIONS IN THE PROTOCOL HELP, it should work.

I would wager that you have NOT read those instructions, else you would realise that for your upgrade (all of which OBC's are greater than 63) the device number you should enter is 127 rather than 27.

Bottom line #2: Use device number 127 instead of 27.

[The Robman]

Try this...
http://www.hifi-remote.com/forums/dload ... le_id=3342

[celeron876]

I read the protocol help worksheet - although I may have misunderstood it.

Here's what I did:

On the Functions sheet, since my learned OBC values are over 63, I added 100 to the values.
For example, in the OBC column, if the learned value was 076, I entered 176.
If the learned value was 125, I entered 225.

In the byte2: column, I entered 1's all the way down.

I configured the Setup sheet this way:

Device 1: 27
Device 2: blank
Device 3: blank

This configuration did not work.

Next, I downloaded the upgrade kindly provided by Rob. It worked, PROBLEM SOLVED!

I see three differences.

On the Functions sheet, Rob used the real OBC codes and did not add 100 to them.
On the Functions sheet, Rob entered "0" to the byte2: column.
On the SetUp sheet, Rob entered 127 for Device 1:

Thanks, Robman and Capn Trips!

[celeron876]

I uploaded this file so others can benefit.

KeyMaster file for Delphi XM SkyFi2

http://www.hifi-remote.com/forums/dload ... le_id=3343

[The Robman]

On the Functions sheet, since my learned OBC values are over 63, I added 100 to the values.... I configured the Setup sheet this way: Device 1: 27

I'm guessing all the terminology that is unavoidable with this sort of thing is probably confusing to you. What the protocol help sheet actually said was "In order to access OBC's in the range 64 - 127, you will need to add
100 to the device code entered.", which means you add 100 to 27 to get 127.

Here's the background, if it helps. The variable data that is assigned to each button only contains the lowest 6 bits of the OBC, which gives it an effective range of 0 thru 63. The 7th bit of the OBC resides in the fixed data. So, if that 7th bit is set, you just get OBCs 64 thru 127 and if it's clear, you get OBCs 0 thru 63.

This isn't something we invented, it's the way UEI built the executor for the RC-5 protocol and we're stuck with it.

When I implemented the RC-5 protocol into the KM spreadsheet I had to come up with a way to signify whether you want the 0-63 range or the 64-127 range. So I came up with the +100 scheme as it was the best I could do working with the limitations of a spreadsheet.

UEI's executor for the RC-5 protocol lets you combine up to three device codes, so if you had needed the complete 0-127 range of OBCs for device code 27, you could have entered 27 as device1 and 127 as device2. Then in the Functions sheet, you would enter a 0 in the byte2 column for OBCs in the 0-63 range (or leave it blank) and you would enter a 1 in the byte2 column for OBCs 64-127.

[Capn Trips]

I read the protocol help worksheet - although I may have misunderstood it.

Here's what I did:

On the Functions sheet, since my learned OBC values are over 63, I added 100 to the values.
For example, in the OBC column, if the learned value was 076, I entered 176.
If the learned value was 125, I entered 225.

In the byte2: column, I entered 1's all the way down.

I configured the Setup sheet this way:

Device 1: 27
Device 2: blank
Device 3: blank

This configuration did not work.

Next, I downloaded the upgrade kindly provided by Rob. It worked, PROBLEM SOLVED!

I see three differences.

On the Functions sheet, Rob used the real OBC codes and did not add 100 to them.
On the Functions sheet, Rob entered "0" to the byte2: column.
On the SetUp sheet, Rob entered 127 for Device 1:

Thanks, Robman and Capn Trips!

As I wrote:

Bottom line #2: Use device number 127 instead of 27.

I'm glad it works. Congratulations.

You've just taken a step into a whole new world.