Your Universal Remote Control Center
RemoteCentral.com
One For All & Radio Shack Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
6131nw vs. Sony DE885
This thread has 3 replies. Displaying all posts.
Post 1 made on Tuesday June 28, 2005 at 18:56
HELLFISH
Lurking Member
Joined:
Posts:
June 2005
1
Hello. I am trying to get my 6131nw to work with my Sony DE885. I've changed the command mode to AV1 and am using code 0158 to get very basic functionality with the receiver, but I need more. I've tried reading several websites about the sony codes, and [Link: hifi-remote.com] seems to be the information that I want, but I have no idea-- even after reading it three times-- what to do.

I would like to get the sound field mode + and - buttons working, as well as the auto dec button, main menu, and up, down, left, right, select. These appear to be in code 1059, but if I change the device to 1059, won't I loose the basic functionality that I have with 1058?

Please help, signed... confused.
Post 2 made on Wednesday June 29, 2005 at 07:56
ofafan
Founding Member
Joined:
Posts:
May 2002
249
With keymoves, you can assign a command from code 1059 to a button, and still use it in code 1058.
What I mean is that if you assign the UP command from setup code 1059 to the UP button, even if you use setup code 1058, when you press the UP button the UP command from setup code 1059 will go out.

To do this:
1. Decide which buttons you want to assign the functions to.
2. Push AUD.
3. Press and hold SET until the LED (red light)
blinks twice, then release SET.
4. Press 1059. The LED will blink twice.
5. Press and hold SET until the LED (red light)
blinks twice, then release SET.
6. Enter 9 - 9 - 4.The LED will blink twice.
7. Press AUD once.
8. Press SET, A, B, C (where ABC is the advanced code for the function you want to program).
9. Press AUD once.
10. Press X once (where X is the key you want to put the function on).
11. The LED will blink twice indicating the
keymoved sequence is correct.
12. Repeat steps 5 through 11 to
map remaining keys.
13. Push AUD.
14. Press and hold SET until the LED (red light)
blinks twice, then release SET.
15. Press 1058. The LED will blink twice.

What you have just done is:
1. Put the remote in the setup code that you want to use keys of.
2. Mapped those keys to buttons on the keyboard.
3. Placed the remote back into the setup code that gives you basic functionality.

Jim

This message was edited by ofafan on 06/29/05 11:54 ET.
Post 3 made on Wednesday June 29, 2005 at 08:32
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
Those are good detailed instructions (though I don't see what 16,17 are for), so maybe further explanation isn't needed. But there are a couple simple facts (missing from the OFA documentation) that you should understand in order be able to get to instructions like these on your own from the basics of programing an OFA remote:

1) When you change setup codes for a device button (steps 2-4 and steps 13-15), it doesn't affect the rest of any previous programming for that device key (keymoves in this case, and learned signals on models that support those). So in Step 13-15 you aren't disturbing the keymoves created in steps 5-11.

2) When you create a keymove (steps 5-11), it does not store the device button of the source (step 7). Instead it stores the setup code previously programmed to that device button. If you later change which setup code is programmed to that device button, that has no effect on the setup code already stored in the keymove.
Post 4 made on Wednesday June 29, 2005 at 12:00
ofafan
Founding Member
Joined:
Posts:
May 2002
249
On 06/29/05 08:32 ET, johnsfine said...
Those are good detailed instructions (though I
don't see what 16,17 are for), so maybe further
explanation isn't needed.

John, good catch. I had copied and pasted the instructions from the .pdf manual, and forgot to remove the excess. Thanks. Gone now.


1) When you change setup codes for a device button
(steps 2-4 and steps 13-15), it doesn't affect
the rest of any previous programming for that
device key (keymoves in this case, and learned
signals on models that support those). So in
Step 13-15 you aren't disturbing the keymoves
created in steps 5-11.

That is a much more concise way of stating what I had rambled on about, attempting to say! :)

2) When you create a keymove (steps 5-11), it
does not store the device button of the source
(step 7). Instead it stores the setup code previously
programmed to that device button. If you later
change which setup code is programmed to that
device button, that has no effect on the setup
code already stored in the keymove.

Again, John is right, and step 7 is perhaps redundant; these steps were copied from the OFA manual.

Thanks, John!


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse