People normally remap the buttons because each remote and the intended use are different. It was only an issue here because we want to completely understand the failure mode, and I think we do now.

Wait, I'm not sure I understand the problem. Does it have anything to do with Vicky's broken glasses? Because I think that deserves the highest priority and needs to be resolved, stat.

You'll be happy to know my JP1 my soldering iron was put to good use and I now have working glasses. Working with the Accessibility Magnifier was a pain. The only thing I could without the accessibility magnifier was browse the internet with the font enlarged as big as it would go. I was really bored as you can see by the Wiki.

Quote:

Quote:

In any case, for diagnostic purposes it would have been a big help if you had saved and uploaded the RMDU file that resulted when the remote type was changed. It really isn't the same file anymore once the remote has been changed or the buttons have been remapped.

Actually, I didn't save the file to disk, I just changed the remote type and copied the device code to IR. I assumed that I didn't need to save the file for the generated code to be correct. Am I wrong about that?

Its always easier to diagnose a problem if we have all the facts. There are numerous common user errors that can be easily seen when we load the files into the tools. Sometimes we even go as far as loading a file into the remote and shoot the code at a Widget in order to see why things don't work. The diagnosis process works best with the files._________________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.

You'll be happy to know my JP1 soldering iron was put to good use and I now have working glasses. Working with the Accessibility Magnifier was a pain. The only thing I could see without the accessibility magnifier was browse the internet with the font enlarged as big as it would go. I was really bored as you can see by the Wiki.

Wow, bravas are in order. Very handsome work you've done there. Maybe not having your glasses for this while wasn't such a big loss to the community. Thank you very much for completing it. Brava!_________________Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)

Has anyone uploaded a .RMDU for the RX-V671 utilizing the 4Dev Yamaha Combo protocol?

I am starting to piece together one. I've spent the last few hours adding the different IR codes, and am looking forward to trying it out once i actually get the RX-671 in the mail.

I want to thank the people in this thread. Thank you user [chico_woodhill]. Without you, this thread wouldn't exist. Thank you user [3FG] for your link to awe-europe. Without that, i would not have any codes to input. What a wonderful site. Too bad it doesn't have every electronic device listed such as my blu-ray players, etc.

Has anyone uploaded a .RMDU for the RX-V671 utilizing the 4Dev Yamaha Combo protocol?

I am starting to piece together one. I've spent the last few hours adding the different IR codes, and am looking forward to trying it out once i actually get the RX-671 in the mail.

I never uploaded my .RMDU (for shame) but I have been using my remote with the RX-V671 since this thread got me through the various Yamaha protocol issues. Yes, having the proper protocols set up in the .RMDU lets you pick and choose from the many commands available in the document you refer to.

Later this weekend when I get some time I'll upload my .RMDU, which you should be able to use directly for the RX-V671 (changing the remote type, of course...)

I think we built that into DecodeIR, so if you're working with learned signals, the decode should tell you which variant it is._________________Rob
www.hifi-remote.comPlease don't PM me with remote questions, post them in the forums so all the experts can help!

It would be nice to know specifically where. That page you referenced has a hundred (or so) links. And the one that's relevant to the Yamaha RX-V671 doesn't seem to have it._________________Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)

This comes from decodeIR.html
-y1: D:8,S:8,F:8,~F:7,F:1:7 (complement all of F except the MSB)
-y2: D:8,S:8,F:8,F:1,~F:7:1 (complement all of F except the LSB)
-y3: D:8,S:8,F:8,F:1,~F:6:1,F:1:7 (complement all of F except MSB and LSB)

85FA
85 1000 0101
FA 1111 1010

So I believe this is y1 because everything but because of all of the twisiting and turning with LSB and MSB I am never quite sure which is msb and which is lsb. If its not y1 then its y2._________________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.

This comes from decodeIR.html
-y1: D:8,S:8,F:8,~F:7,F:1:7 (complement all of F except the MSB)
-y2: D:8,S:8,F:8,F:1,~F:7:1 (complement all of F except the LSB)
-y3: D:8,S:8,F:8,F:1,~F:6:1,F:1:7 (complement all of F except MSB and LSB)

No wonder I felt like was going crazy. The last couple of days, I decided to sit down and read it from my iPad and I couldn't find reference to those NEC "-y[1-3]" variants. I still don't have a complete grasp in deciphering IRP notations, so it didn't help me too much after realizing it was the wrong document. Though DecodeIR.html the did help understand some protocols a little better._________________Remotes; JP1.2: Comcast URC-1067, JP1.3: Insignia NS-RC02U-10A, JP1.4 OARI06G, JP2.1: Cox URC-8820-MOTO (still trying to figure out how to make them self-aware.)

If you're working from the Yamaha documentation, and using NEC 4DEV Yamaha Combo, use the notes provided in RMIR:

YStyle selects among the following:
NEC: sends the ordinary NEC signals (specified by NStyle) in which the second byte of data is the complement of the first byte.
The two bytes of data always add to 255, which is standard for NEC signals. Normally only the first byte is specified.
Y1: sends NEC signals except the sum of the two bytes is 127 or 383 (256+127). Yamaha shows both bytes in their docs.
Y2: sum is 254 or 256.
Y3: sum is 126 or 128 or 384.

Since the Yamaha docs are in hexadecimal notation, first convert the function codes to decimal. 85h = 133d, and FAh = 250d.

133 + 250 = 383, which means this is a y1 style signal.

Most Yamaha signals that are associated with the Main zone are either NEC1 or NEC1-y1. Signals for other zones may also be y2 or y3.

Since the Yamaha docs are in hexadecimal notation, first convert the function codes to decimal. 85h = 133d, and FAh = 250d.

133 + 250 = 383, which means this is a y1 style signal.

Most Yamaha signals that are associated with the Main zone are either NEC1 or NEC1-y1. Signals for other zones may also be y2 or y3.

Since the Yamaha documentation is an Excel spreadsheet, I added several new columns with Excel formulas to the sheet to calculate and display the protocol styles for each command. I'm traveling at the moment so I can't share the formulas or modified sheets, but if anybody is interested I could upload the file when I get home.

This utilizes the extended NEC protocols discussed in this thread. You can add more codes as needed but just be careful to make sure that the NEC protocols are properly indicated in the rmdu file Functions page (i.e., Dev.Sub, N-Style, and Y-Style).