Keymoves with 15-1995

tbsmith · Post by **tbsmith** » Tue May 25, 2004 9:51 pm

Paul,

That's right, I can code it in IR, but it doesn't work. Same with doing in right on the remote as Rob suggested. In both cases, it seems like it should work because the lcd display shows the moved device mode when I press that particular button, then it goes back to the mode it was left in before pressing the button. Hope that makes sense.

Tom

e34m5 · Post by **e34m5** » Wed May 26, 2004 5:48 am

As I recall a keymove does not reset the device selection. Are you trying this within a macro or by itself from the remote.

I still thinh it has something to do with the codes in the keymove itself. How did you determine the codes to use in the keymove?

Did you try them directly from the remote. To do that select the device in question and then press Set + the EFC in question. That should tell you id if works. One exception is when it requires a two byte code. I can't remember how to test those.

tbsmith · Post by **tbsmith** » Wed May 26, 2004 12:36 pm

Paul,

No, I'm not t trying it from a macro, just from the remote. I was following the factory instructions where you can move (actually copy) a key from one device to another. It works with everything but the amp.

When I tried it using IR, I got the code from the function list in KM. Tried both hex and EFC versions.

I don't think my remote has a "set" button, but I'll check tonight.

Thanks,
Tom

e34m5 · Post by **e34m5** » Wed May 26, 2004 12:47 pm

Try and learn the commands then look at them in IR. This may tell you some thing. Does your amp use two byte commands? This may be an issue.

Mark Pierson · Post by **Mark Pierson** » Wed May 26, 2004 3:27 pm

tbsmith wrote:I don't think my remote has a "set" button

On the 15-1995 it's the green P button.

tbsmith · Post by **tbsmith** » Wed May 26, 2004 7:54 pm

Yes, I think my amp does use 2-byte commands. In IR, under the devices tab, there are entries under Hex Command like FF FB (for Volume) and under EFC it says 213* (Use Hex). Also, in KM, there are numbers in the Functions Tab, Byte2=Sub Dev Column.

If these are 2 byte commands, could that be why I can't do a keymove?

I am uploading the file HERE to see if that help.

When I tried pressing "P" (for set) and the EFC, the LED flashed but nothing happened on the amp. I then tried this on the on a few other devices (which I'm not having a problem with) and something did happen. However, entering the EFC did not result in the expected response (e.g. the TV volume EFC ended up muting the TV instead).

On more thing I noticed...there are 10 kemoves associated with the amp that I never entered in KM and they don't show up there either. But they do show up in IR. I don't need them, nor do they work.
How did that happen?
Why don't they work?
Can I delete them?

Thanks,
Tom

PS - I can't learn the commands as this is not a learning remote.

e34m5 · Post by **e34m5** » Thu May 27, 2004 6:45 am

tbsmith wrote: When I tried pressing "P" (for set) and the EFC, the LED flashed but nothing happened on the amp. I then tried this on the on a few other devices (which I'm not having a problem with) and something did happen. However, entering the EFC did not result in the expected response (e.g. the TV volume EFC ended up muting the TV instead).

When testing this make sure that you have selected the proper device first, in your case that would be AMP. Other wise the remote is not using the correct protocol. Now having said that I am not sure if a two byte code can be tested this way. One of the other guys here can tell you more about that than me (Mark..hint, hint)

On more thing I noticed...there are 10 kemoves associated with the amp that I never entered in KM and they don't show up there either. But they do show up in IR. I don't need them, nor do they work.
How did that happen?
Why don't they work?
Can I delete them?

These keymoves were defined in the upgrade you used. It's common for people to have done that. If they do not work for you there is no harm in deleting them.

As you have already determined your amp uses a two byte code. Also as you have noted KM helps you determine what these are. Notice that in KM when you enter an EFC or OBC and the proper byte2 has been selected then the corresponding HEX is calculated automatically. This is the value that must be entered in IR when creating a key move for that function. You can see examples of this in those keymoves that are already there.

Since you don't have a learning remote then you may have to look through the various upgrades and test out several combinations until you hit the correct one.

As far as your file is concerned I don't see anything out of the ordinary. It looks to me like you are at that stage where you just need to locate the proper codes for your AMP and you'll be golden.

I noticed that ther are several upgrade files for SA-HE100, it is worht while trying all of them and doing some comparisons. One of them probably has what you are needing.

Keep trying and keep asking...

tbsmith · Post by **tbsmith** » Thu May 27, 2004 1:42 pm

When testing this make sure that you have selected the proper device first, in your case that would be AMP. Other wise the remote is not using the correct protocol.

Yes, that's what I did, but it did not give the expected results.

These keymoves were defined in the upgrade you used. It's common for people to have done that. If they do not work for you there is no harm in deleting them.

Are they hidden somewhere in KM? Where do I look for them in in order to delete them? (there is nothing in the buttons tab that indicates a keymove).

I will do what you suggest and try some of the different codes. It just seems strange that the functions work fine but cannot be moved. I feel like I'm still doing something wrong.

Tom

e34m5 · Post by **e34m5** » Thu May 27, 2004 2:15 pm

Look in the buttons tab of KM. The buttons preceded by @ are keymoves. You don't need to delete them from KM just delete them in IR.

I will do what you suggest and try some of the different codes. It just seems strange that the functions work fine but cannot be moved. I feel like I'm still doing something wrong.

I thought you said that none of the functions worked. So I'm confused, do you already have functions on the remote that do it correctly. If so just go into KM and change the function of the button to the function that works. No need for a KeyMove then. Or you can associate that function to a KeyMove button.

Mark Pierson · Post by **Mark Pierson** » Thu May 27, 2004 3:12 pm

tbsmith wrote:
When testing this make sure that you have selected the proper device first, in your case that would be AMP. Other wise the remote is not using the correct protocol.
Yes, that's what I did, but it did not give the expected results.

If you're talking about the "Set-E-F-C" method, that won't work for 2-byte commands (which your AMP/1763 uses). The only way to enter key moves for that setup code is directly in IR, or using KM.

I see you have a key move bound to SAT: Vol+. I bet that doesn't work, huh? The reason it doesn't is because you need to enter the 2-byte hex command "FF FB", not the EFC of 213.

These keymoves were defined in the upgrade you used. It's common for people to have done that. If they do not work for you there is no harm in deleting them.
Are they hidden somewhere in KM? Where do I look for them in in order to delete them? (there is nothing in the buttons tab that indicates a keymove).

I'd suggest you re-read the keymap-master-readme.txt file. The process of KM creating key moves as part of the device upgrade IS explained in there. As Paul said, ANY button on the Buttons sheet that's preceded by "@" will create a key move if a function is assigned to it (as will any function assigned to a shifted button).

The bottom line here is that in order to add key moves for the AMP/1763 device, you MUST use the 2-byte hex commands (select the Hex Cmd radio button in the Key Move dialog), and NOT the EFC's. If you want to know what the hex commands are for the various function, look at the Functions sheet Hex column.

tbsmith · Post by **tbsmith** » Fri May 28, 2004 10:18 am

If you're talking about the "Set-E-F-C" method, that won't work for 2-byte commands (which your AMP/1763 uses). The only way to enter key moves for that setup code is directly in IR, or using KM.

Thanks, good to know that doesn't do anything for 2-byte commands.

I see you have a key move bound to SAT: Vol+. I bet that doesn't work, huh? The reason it doesn't is because you need to enter the 2-byte hex command "FF FB", not the EFC of 213.

Yes, that's what I'm trying to make work. I had already tried entering the hex command "FF FB" (in IR - by adding a keymove) and it didn't work. The file I uploaded is the one where I tried the keymove directly on the remote. Anyway, when I entered the hex command (in IR), I tried it as "FF FB" and also as "$FF $FB" but neither worked (I checked the "hex" radio button). Should I be including a space between FF and FB? Also, I see that for KM, you can enter it as FFh FBh...is that necessary in IR? I will try it again

I thought you said that none of the functions worked. So I'm confused, do you already have functions on the remote that do it correctly. If so just go into KM and change the function of the button to the function that works. No need for a KeyMove then. Or you can associate that function to a KeyMove button.

I could not get any of the moved AMP functions to work...all the AMP functions work fine in AMP mode. But I want to be able to control the amp volume while watching a DVD and leaving the remote in the DVD mode.

Thanks,
Tom

Mark Pierson · Post by **Mark Pierson** » Fri May 28, 2004 10:46 am

tbsmith wrote:
I see you have a key move bound to SAT: Vol+. I bet that doesn't work, huh? The reason it doesn't is because you need to enter the 2-byte hex command "FF FB", not the EFC of 213.
Yes, that's what I'm trying to make work. I had already tried entering the hex command "FF FB" (in IR - by adding a keymove) and it didn't work. The file I uploaded is the one where I tried the keymove directly on the remote. Anyway, when I entered the hex command (in IR), I tried it as "FF FB" and also as "$FF $FB" but neither worked (I checked the "hex" radio button). Should I be including a space between FF and FB? Also, I see that for KM, you can enter it as FFh FBh...is that necessary in IR? I will try it again

You need the space between bytes or IR will display an error. The 2 formats it will accept are "FF FB" or "$FF $FB"; it complains about "FFh FBh".

When you're in Amp mode, the Vol+ button works like it's supposed to, and when you setup the Sat: Vol+ key move using "FF FB", and are in Sat mode, Vol+ does NOT work, correct?

Is the TV volume being controlled when you press Sat: Vol+? If so, disable the VPT Status on the General tab in IR.

tbsmith · Post by **tbsmith** » Fri May 28, 2004 12:58 pm

When you're in Amp mode, the Vol+ button works like it's supposed to, and when you setup the Sat: Vol+ key move using "FF FB", and are in Sat mode, Vol+ does NOT work, correct?

That is correct.

Is the TV volume being controlled when you press Sat: Vol+? If so, disable the VPT Status on the General tab in IR.

No, the TV isn't being controlled when I press Sat: Vol+. I do have VPT on, but it doesn't control the TV in Sat mode, only in some other modes, like CBL. I will try turning it off, just to make sure. Thanks for the ideas, Mark. One more thing, when I push Sat: Vol+, the LCD display flashes AMP/TUNER briefly, which leads me to believe the keymove is in there, but the code for Vol+ is somehow wrong.

Tom

Mark Pierson · Post by **Mark Pierson** » Fri May 28, 2004 1:44 pm

tbsmith wrote:One more thing, when I push Sat: Vol+, the LCD display flashes AMP/TUNER briefly, which leads me to believe the keymove is in there, but the code for Vol+ is somehow wrong.

But it works when in Amp mode... now I'm confused!

tbsmith · Post by **tbsmith** » Fri May 28, 2004 1:56 pm

Yes, it works fine in Amp mode. I either stumped the expert, or I really screwed something up. You guys gave me a few more things to experiment with so I'll try them over the weekend and let you know.

Have a good one 8)

Tom