JP1 Remotes

Ok here is the update, I managed map over the sound effect in the menu but it still looks like I will need to try all 255 codes to see what they do. There were some ecf I couldn't get to work. When I find some time I will need to go down the list and make a list of what works.

I will report back with an update.

I just purchased a Yamaha RX-V661 and have an 8910 remote. I did not find an existing upgrade file and tried a couple of the existing Yamaha upgrades. Nothing seemed to work too well.

Last night, I resorted to learning from the original remote. I am in the process of creating an upgrade for the unit. I don't have the information with me as i post here but almost all codes were NEC1 protocol, device 122.

However, there were a few that used a subdevice number.

Also, this receiver uses "Scenes" in order to quickly select a combination of parameters for a typical use scenario. The remote learned these commands as some totally different protocol. I'll list the specifics when i take the next step. I'm sure i'll be asking here how to incorporate the subdevice and this new protocol into the upgrade.

Stay tuned.

mdwags wrote:The remote learned these commands as some totally different protocol. I'll list the specifics when i take the next step.

Don't "list the specifics" of a different protocol. A different protocol is unexpected enough in this context that we probably wouldn't trust the decodes. (Unless it's just "NEC" instead of "NEC1", in which case the "NEC" just represents imperfect learns of "NEC1").

Instead, save a .ir file containing those learned signals. Before saving, please add some notes to the signals in IR.exe to say what functions they represent. Then put the .ir file in the diagnosis area and post its URL. We can tell a lot more from the .ir file than from your quotes from the decodes.

mdwags wrote:I'm sure I'll be asking here how to incorporate the subdevice and this new protocol into the upgrade.

With a summary of those subdevice decodes, someone can tell you the best way to proceed. But no guess of how to proceed with the other protocol decodes is likely before we see that .ir file.

I'll try to create and upload the .IR file as you suggest.

When posting to the diagnose area, i see some filenames begin with the remote type (in my case the 8910) and some begin with the mfr name. Do you have a preference?

When posting in the Diagnosis area, you need to provide a link. Naming matters when you put your final upgrade up. Then you want to look at the spacing and capitalization and such to make your upgrade group with similar upgrades.

vickyg2003 wrote:When posting in the Diagnosis area, you need to provide a link. Naming matters when you put your final upgrade up. Then you want to look at the spacing and capitalization and such to make your upgrade group with similar upgrades.

What do you mean by a "link"? Are you talking about a URL to some website on which i've uploaded the file? If so, I have Comcast as my ISP. Can i upload the file into some "webspace" that Comcast gives me with my account?

OR

In looking at the Diagnosis Upload screen and it appears as though i can just browse to the file on my PC and hit Upload. Is that not true?

mdwags wrote:In looking at the Diagnosis Upload screen and it appears as though i can just browse to the file on my PC and hit Upload. Is that not true?

That's correct. After uploading a file to the Diagnosis area, we ask that you post a link (URL) to it back here in this thread so that anyone willing to look at it can find it.

OK, i have uploaded an .IR file into the diagnostics area. The name of the entry is "Yamaha_RX-V661" (although the actual filename is System-IR-w-RX-V661.IR). The Learned Signals tab is where my concern is.

https://www.hifi-remote.com/forums/dload ... le_id=5038

All entries except the last three are standard NEC1 protocol. Some of the codes line up with other Yamaha receivers - some do not. Anyway, i learned these from the Yamaha remote (model RAV326) and should be able to plug into KM or RM to create an upgrade.

However ...

The last three are for 3 of the 4 "Scene" buttons. The protocol shows up as "Gap-550-1687-32?" with a device code of 122 and a subdevice of 133. I haven't seen a protocol with that name in KM or RM. How can i create an upgrade file that would include this data?

Note: There is a RCVR found in the device tab. It is from a previously used upgrade file.

Thanks for the assistance.

I half remember something about these Yamaha signals from a thread at RC. I thought it was a "zone" thing, but maybe I'm misremembering and it was the same "scene" functions you have.

The signals are almost NEC1.
The device is 122 (that subdevice of 133 in the decode doesn't mean anything).
The OBC is not the reported value. For each of those three, the correct OBC is 127 minus the reported value (so 0, 3 and 6).

The difference between these signals and NEC1 is that the top (second) nibble of the check byte is used for some other purpose, not (as NEC1 would use it) the inverse of the top nibble of the OBC. In those three samples that nibble is 7. I don't know what that means.

Tivo and Apple protocols also are almost NEC1 but use the check byte differently. I don't know how the executors for those work, so I don't know whether one of them is close enough or whether a new executor similar to the Tivo one would be required.

Mixing these in one upgrade with ordinary NEC1 signals is probably more difficult than it is worth. I suggest making a helper upgrade for these special signals and using external functions to define those three keys, so it would act like it is all one upgrade but actually the special signals would be keymoves.

Hopefully someone else can tell you which/whether existing executor can be used for those three signals. If not, I'll try to dig up the Tivo or Apple info and check that myself for you when I can find some time.

mdwags wrote:The last three are for 3 of the 4 "Scene" buttons.

Which is the other scene button? I assume it decoded as normal NEC1. These almost-NEC1 signals have a one in sixteen chance (depending on OBC number) of decoding as perfect NEC1. If the other scene button is the same type signal but happened to decode as NEC1, its OBC value could tell us more about the rules for these signals than we can deduce from the three we have.

Wow. Johnsfine, you certainly know your stuff!

I only learned three of the four scene buttons because that's all i anticipated using with my remote. I was running out of buttons and something had to give.

I'll try to learn it tonight and report my findings. If not tonight, i'll be gone for the next 5 days.

Does the NEC1 protocol not have enough command codes that Yamaha chose to use this tweeked protocol? Don't they realize that some of us want to do more??

In order to replicate the scene buttons, someone would need to write a custom executor (protocol upgrade), therefore I recommend that you create an upgrade that includes all of the regular NEC-dev122 buttons and then just learn the 4 scene buttons.

Thanks for looking at this issue.

I think I understand what you are recommending and why.

I was thinking of moving to an extender in the near future to increase flexibility for me and simplicity for my family. Am i correct to believe that learning functionality goes away if i use an extender? Can i incorporate these existing learned functions into an extender somehow?

Do i need to make a choice of either extender or Scene buttons?

You are correct, the extender does not support learned signals.
The current extender is a little buggy. I was just working on this early this morning. Something is wrong with the x_dev, x_cancel command. I thought I'd have it packaged up by now, but its back to whe bench to see where the bug is. Hopefully it won't be long.

mdwags wrote:Thanks for looking at this issue.

I think I understand what you are recommending and why.

I was thinking of moving to an extender in the near future to increase flexibility for me and simplicity for my family. Am i correct to believe that learning functionality goes away if i use an extender? Can i incorporate these existing learned functions into an extender somehow?

Do i need to make a choice of either extender or Scene buttons?

Might I suggest going to the Extenders Forum and reading the Extenders FAQ?

mdwags wrote:Do i need to make a choice of either extender or Scene buttons?

If you're ready for the extender, I'm sure someone will figure out how to use or modify the Tivo executor for your similar signals.