Yamaha rx-v863 power toggle issue
Moderator: Moderators
-
mitchharper42
- Posts: 9
- Joined: Thu Aug 26, 2004 5:44 pm
Yamaha rx-v863 power toggle issue
I just got the Amp and I haven't been able to get the power toggle to work. The remote only has discrete power on and power off. This unit also uses two device codes 122 and 126 for button functions.
What I'm trying to find is a power toggle, here is what I have found so far:
power on: NEC1, device 126, OBC 126, EFC 6 - works
power off: NEC1, device 126, OBC 127, EFC 10 - works
the power toggle I have found for other Amps in the rx-v family:
NEC1, device unknown, EFC 250 - tried both 122 and 126 device codes, nothing
I have also tried shooting in the dark with EFC codes around the power on/off but nothing so far.
Anyone found a fix for this?
What I'm trying to find is a power toggle, here is what I have found so far:
power on: NEC1, device 126, OBC 126, EFC 6 - works
power off: NEC1, device 126, OBC 127, EFC 10 - works
the power toggle I have found for other Amps in the rx-v family:
NEC1, device unknown, EFC 250 - tried both 122 and 126 device codes, nothing
I have also tried shooting in the dark with EFC codes around the power on/off but nothing so far.
Anyone found a fix for this?
-
mitchharper42
- Posts: 9
- Joined: Thu Aug 26, 2004 5:44 pm
I haven't seen anything specific to that model, but there are specs for the 361 and related models for both the standard and extended IR codes available in the thread over at AVS:mitchharper42 wrote:tried the EFC 087 for both device 122 and 126 and neither work.
http://www.avsforum.com/avs-vb/showthre ... 95&page=26
A.A.
-
The Robman
- Site Owner
- Posts: 22018
- Joined: Fri Aug 01, 2003 9:37 am
- Location: Chicago, IL
- Contact:
If it turns out that your Yamaha doesn't have a power toggle button, you could stack both the ON and OFF commands on the one button by using shifting.
For example, the regular POWER button could be ON and shift/POWER could be OFF (or vice versa, if you prefer).
Of course, if you're using macros for everything this may not matter, as discrete power codes is what you would want anyway.
For example, the regular POWER button could be ON and shift/POWER could be OFF (or vice versa, if you prefer).
Of course, if you're using macros for everything this may not matter, as discrete power codes is what you would want anyway.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
-
mitchharper42
- Posts: 9
- Joined: Thu Aug 26, 2004 5:44 pm
The avsforum was VERY close. Seems Yamaha doesn't have a power toggle though, the list for the 861 is the same as the ccf file I found but more complete. So far all of the power codes are discrete.
I only have one macro that is the 'power everything toggle' for all of my equipment so discrete codes confuse the roommates (there is only one power button on the remote) and since it is the 15-2104 remote shifting isn't easy
Well back to the goose chase....
I only have one macro that is the 'power everything toggle' for all of my equipment so discrete codes confuse the roommates (there is only one power button on the remote) and since it is the 15-2104 remote shifting isn't easy
Well back to the goose chase....
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Some/all extenders permit
1. relocating shift key to a better key
2. making a toggle out of discretes
Added later:
From the ToadTog.ext file in
https://www.hifi-remote.com/forums/dload ... le_id=1418
But if you select hex on the Special protocols, you can type in hex as well.
Exactly as in this very old example.
1. relocating shift key to a better key
2. making a toggle out of discretes
Added later:
From the ToadTog.ext file in
https://www.hifi-remote.com/forums/dload ... le_id=1418
It should be simple to do using the current IR interface, so you won't have to type in the hex numbers.For example, imagine shift-0 (9F) was an existing discrete OFF function
and shift-1 (95) was an existing discrete ON function and you wanted to use
toggle number 5 to contruct a toggle function. The hex command would be:
51 9F 95
The "5" means we want to use toggle 5. The "1" means the ON sequence is one
code long. The 9F will be sent (to turn the item off) if it was previously
on. The 95 will be sent if it was previously off.
But if you select hex on the Special protocols, you can type in hex as well.
Exactly as in this very old example.
Last edited by ElizabethD on Wed Jun 02, 2010 9:08 pm, edited 1 time in total.
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
-
vickyg2003
- Site Admin
- Posts: 7109
- Joined: Sat Mar 20, 2004 12:19 pm
- Location: Florida
- Contact:
The Toad/Tog protocol that comes with the extender would be helpful for this too. If there is a LKP that could be useful in this too. There are a lot of ways you can handle this in an extender.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
-
ElizabethD
- Advanced Member
- Posts: 2348
- Joined: Mon Feb 09, 2004 12:07 pm
Hi Vicky! we were typing at the same time 
I just checked in IR using 8910 extender - given the discretes on shift-0 and shift-1 I made a toggle on shift 2 and it reads in IR as
I just checked in IR using 8910 extender - given the discretes on shift-0 and shift-1 I made a toggle on shift 2 and it reads in IR as
That's toadTog#6, not 5 as in John's instructions.AUX SHIFT-2 ToadTog(6,Toggle) [On->Off]:SHIFT-0 [Off->On]:SHIFT-1 $61 $9F $95
Liz
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
Tweeking 8910, HTPro/9811, C7-7800, 6131o, 6131n, AtlasOCAP-1056B01, RCA-RCRP05B and enjoying the ride
HERE's the 15-2104 extender with ToadTog. However, I have to say this is a real Rube Goldberg solution to a very simple problem. A "power everything toggle" is a terrible idea. How do you keep everything in sync? Why don't you just use the macro keys for turning things on, and one macro key for master power off? That's completely bullet-proof, easy to program and easy to remember.
-
mitchharper42
- Posts: 9
- Joined: Thu Aug 26, 2004 5:44 pm
WOW! the help here is wonderful.
mdavej, I haven't had any issues with sync since it is only the Amp and TV and it was too easy
until now I haven't used discrete codes so now I get to learn ToadTog and attempt to get the power button to work with everything.
I was thinking that a seperate on/off would work and solve my issues, use the 'Theater' key for something now
The link to avsforums had the pdf files for the 861 and I now have all the IR codes for the 122 device which makes this a bit easier.
When I tried to create the 126 device with only the power IR codes the code generated didn't work in the IR program, the 'fixed bytes' was blank and the buttons were getting multiple hex codes. Seems like a limitation or bug somewhere.
mdavej, I haven't had any issues with sync since it is only the Amp and TV and it was too easy
until now I haven't used discrete codes so now I get to learn ToadTog and attempt to get the power button to work with everything.
I was thinking that a seperate on/off would work and solve my issues, use the 'Theater' key for something now
The link to avsforums had the pdf files for the 861 and I now have all the IR codes for the 122 device which makes this a bit easier.
When I tried to create the 126 device with only the power IR codes the code generated didn't work in the IR program, the 'fixed bytes' was blank and the buttons were getting multiple hex codes. Seems like a limitation or bug somewhere.