JP1 Remotes

Hi, by my version of RM you know it's been a bit since i've been here. it's also been a long while since i used my irwidget. i need the 'streambox' input for a new onkyo 696. i used irScrutinizer to capture the key (NEC1: {D=210,S=109,F=12}, thanks barf.
The number keys for the existing upgrade (NEC1 combo) changed the receiver through most of the inputs. by changing just the sub device and the OBC for key "1" to 109 and 12, respectively, a press of "1" changed to the streambox input. I did capture the key for "CBL" input which had sub device 109 and OBC 14.
I feel like i got really lucky, but from the capture above for 'streambox', what's the right way to add it to an existing upgrade that contains the correct protocol?

best,
jeff

Hey Jeff, it's a bit hard to follow along as you don't provide any links or info on the upgrades that you're currently using. You've evidently been able to capture the 2 new buttons that you want to add to your setup, and I see that Onkyo receivers do seem to use NEC1 with device code 210 and various sub-device codes, but mainly 108 and 109, which is consistent with what you've found.

I am guessing that you're using an upgrade to control your Onkyo TX-NR696 but I don't know what that upgrade looks like. I did check the file section and we don't have an upgrade for that specific model of Onkyo, so I'm guessing that you made it yourself but never loaded it here.

So, the right way to add those codes depends on which NEC1 combo executor that you're using, but you need to identify the sub-device (ie, 109) and the OBC (ie, 12 or 14).

apologies robman and thanks for the reply!
this upgrade started a long time ago from a similar onkyo in the file section. maybe. it kept on working so i just kept using it, until now. it was probably this one: Onkyo TX-NR609 Receiver (remote RC-803M), https://www.hifi-remote.com/forums/dload ... le_id=9655. i took a quick look and i'm pretty sure it's that one. it doesn't have the streambox input that is on the new remote. I have the irwidget and figured I could do what I needed with minimal work (I'm lazy, lol).

i think you did answer my real question was what's the minimal info from a decode/learn i need to patch the upgrade assuming the protocol didn't change. i needed the sub-device and OBC. I hadn't bothered to explore much beyond using device upgrades in the past. but am using the latest extender for the atlas remotes and LKP.

I think the last time i used the irwidget was with the old IRDecode app. i couldn't get the IR widget to work with RMIR, but Irscrutinizer worked. I'm on a mac and I think the port wasn't right for RMIR and i couldn't figure it out.

i'm glad you're still here. i come by a few times a year. I notice chrome sees the site as not secure. I don't know if that's a concern or not.

best and thanks again to you, barf, greg, graham and the rest of the jp1 experts!
jeff

I would suggest that you consider the alternative approach: Using IrScrutinizer+IrWidget, capture all the commands of the remote. Export as Girr. Then import that file in RM, and see what executor it selects. If the original update containes commands not in the new one, add them manually in RMIR.

I notice chrome sees the site as not secure. I don't know if that's a concern or not.

It wants to see "https:" instead of "http:". Long story short (Google if you want more details), as long as you do not deal with security critical stuff (payments etc) it is not an issue. Except that some people get scared .

Ok, that upgrade uses the NEC1 Combo where you specify the main device code (210) in the Setup tab, then in the Functions tab you specify the sub-device and OBC (you can ignore the EFC and hex columns, those will populate automatically).

So, i think you've already figured out what to do, just capture any buttons which are new, like Streambox and CBL, to get their subdev and OBC codes, then add new lines for them in the Functions tab, then assign those new functions to buttons in the Buttons tab.

I just added those 2 functions to the file that you posted.

Once you've added any buttons that are on your new remote that aren't in that file, and you've removed any functions that don't work on the 696, could you please load the resulting RMDU file up under the 696 name?

Hi rob,
here's the link to the remote dump https://www.hifi-remote.com/forums/dload ... e_id=27021 as an excel spreadsheet. i'm not sure how to make an upgrade from all the 'learns'. Is this still useful?

the arrow keys and the tone and volume showed 'beg' and 'end' in the irscrutinizer. also zone2 shift and zone3 shift produced no signal. not sure what's up with that. the rest seemed like good learns.

let me know if you need anything else.
best,
jeff

Rather than just me doing it for you, I'd like to see you able to do this for yourself, so let's look at what you've done so far. You've managed to caputure all of the buttons from the 696 remote, and no surprise, they use the same signals as all the other Onkyo receivers, which is NEC1 with a main device code of 210, various sub-device codes (but mainly 108 and 109) and various OBCs.

You can already see how to build an upgrade like this because you are using one already.

So, what is it that you don't know how to do to complete the process of turning these learns into an upgrade?

Also, I have updated your spreadsheet. I've added a 2nd tab to show how the codes that you've found compare to the master file that I've compiled. Most of the buttons that you learned correspond exactly with the master, but you did find a few new ones which I've added to the master (in red). The only difference is the Bluetooth button, which is Display on other Onkyo units.

ok. i'm out of time today, but i think i figured out what i need to do.
rmir isn't the tool i need. i need to run rmdu.
then edit the functions, updating the names and the sub device and OBC with columns D and E respectively from my sheet (called S and F in IrScrutinizer). Also update the notes column.
I can then test the upgrade on an unextended atlas remote. i'll come back if i run into problems with some keys. (I was hung up trying to figure out why i couldn't open the 609 upgrade with RMIR. once i realized i needed rmdu, i was good...)

does this sound about right?
best,
jeff

You don't need to make your remote un-extended, if it's currently extended, that makes no difference.

You are correct that RM is the program to edit upgrades, whereas RMIR is the program that edits your remote's profile. But, RM is also in RMIR. When you go to the Devices tab in RMIR and click edit on an existing upgrade, or click new to add one, you get RM as a pop-up.

So, if you already have an upgrade in your remote that works the Onkyo, you can edit it and add the new sub-devs and OBCs.

hi rob,
i've run into an issue with one button, bluetooth input selection. irscrutinizer decodes it as: NEC1-f16: {D=210,S=30,F=80,E=14}
IRP:{37.9k,284,msb}<2,-2|2,-7|2,-16|2,-43m>(9022u,-16,A:63,B:3,(9022u,-7,2,-95m)18){A=0x8228aa000220a80,B=0x3}

i've uploaded the upgrade on working on to the diagnosis area: https://www.hifi-remote.com/forums/dload ... e_id=27023

What I do in cases like this is to re-learn the button several times to ensure that I'm getting a good learn. IrScrutinizer does the best that it can with the data that it's provided. NEC1-f16 just means that the 2nd byte of the OBC isn't the complement of the 1st byte, which it is for normal NEC1 signals.

If the Bluetooth button really does use NEC1-f16, we have options. We can rebuild the entire upgrade using NEC1-f16 or we can build a 2nd upgrade just to supply that one button.

or another option is make someone walk over to the receiver and push the bluetooth input button lol.
i've done a number of captures and the decode is the same. this is the only button that is different. i'll leave it to you to decide what to do.

i'm actually surprised the old upgrade pretty much just worked. i thought i'd read that onkyo had changed their remotes so that all the older upgrades didn't work for newer gear. i must have been wrong.
best,
jeff

Here's the one that I did based on your previous learns:
https://www.hifi-remote.com/forums/dload ... e_id=27022

Here's a zip file for you:
https://www.hifi-remote.com/forums/dload ... e_id=27025

This has your spreadsheet, with a new "f16" tab to show you how to format an f16 entry for a normal NEC1 signal (basically, the OBC2 value is 255 minus the OBC value). I've included my original rmdu file for this, then a new rmdu file where I've converted the whole upgrade to f16, and then another copy of that same rmdu with only the Bluetooth input function assigned to a button.

Your options are:
1. Use the NEC1 upgrade and do the Bluetooth thing manually
2. Use the f16 upgrade
3. Use the NEC1 upgrade plus the small f16 upgrade, and program the Bluetooth button as a keymove.

While the f16 upgrade option might sound the simplest, it creates a HUGE upgrade, because every button uses 4 bytes of data, compared to 1 byte for the NEC1 upgrade, plus you get a protocol upgrade too. If you have enough memory to spare, that's probably your best option, but if things are tight, chose one of the other options.

thank you so much rob. i can confirm the bluetooth input function works in both upgrades. so i guess it really was the nec1-f16.

i'm about out of time today for this and haven't check out the memory usage. that will determine which way to go. in the test remote, the difference seems small on the atlas remotes i have.

thanks again,
jeff
p.s. this exercise reminded me of how much i've forgotten about the remotes, lol. I'm still happy you guys are still around! happy holidays!