Onkyo amp codes, merging two sets for XSight Touch remote?

andrewilley · Post by **andrewilley** » Thu Sep 21, 2017 2:37 am

This is my first time trying Remote Master (after the EZ-RC website for the One-for-All Xsight Touch was sadly closed down earlier this year) so please be gentle with me!

So far I've been used to the official (and really simple) select-from-list hand-holding wizard method, so this is all a leap in the dark for me and I don't want to screw up my remote which is working perfectly at the moment apart from needing a new TV added [the LG TV discussion has been split here: http://www.hifi-remote.com/forums/viewt ... p?t=101051 ] and I'd like to condense my two existing Onkyo amp code sets into one neater one.

1. Device: Onkyo TX-NR555 (old one was TX-SR606)
2. Type of device: Amplifier
3. Year: 2016
4. JP1/UEI Remote model: URC8603 One-for-All Xsight Touch
5. Do you have a JP1 cable? No, just a plain USB connection
6. Still have original remote? Yes
7. Checked the file section? Yes
8. Checked Pronto file section (at R/C)? No (this is not a Pronto device)
9. Partially working setup code? Two sets downloaded from EZ-RC while the site was still working, need some functions from each.
10. Learning remote question? Yes
11. Have you tried the JP1 Lookup Tool? Yes

How I can copy a few codes from my old Onkyo Amplifier device into the set for my newer one. I currently have both full sets saved in the remote, just for the old Discrete On/Off codes which work with both amps, but it'd be much neater to move those couple of codes over into the new list. I tried just copying the OBC number from the old set (Onkyo TX-SR606) to the new device (Onkyo TX-NR555), but that didn't work so there must be some other differences I need to take into account. I also tried copying the three-byte hex sequence from the Onkyo master spreadsheet downloaded from the files section, but again no luck.

Andre

Post by **vickyg2003** » Fri Sep 29, 2017 7:12 pm

andrewilley wrote: I tried just copying the OBC number from the old set (Onkyo TX-SR606) to the new device (Onkyo TX-NR555), but that didn't work so there must be some other differences I need to take into account. I also tried copying the three-byte hex sequence from the Onkyo master spreadsheet downloaded from the files section, but again no luck.

Typically it copying the OBC from one upgrade to another. Many newbies make the mistake of copying Hex or EFC which doesn't work if the version of the executor is different. Typically if the OBC doesn't work the Device or Subdevice are different. If you want to post your file in the diagnosis area and post a link here I'm sure someone will take a look.

Also remember to post your upgrade in the file section.

andrewilley · Post by **andrewilley** » Sat Sep 30, 2017 2:14 am

vickyg2003 wrote: Typically it copying the OBC from one upgrade to another. Many newbies make the mistake of copying Hex or EFC which doesn't work if the version of the executor is different. Typically if the OBC doesn't work the Device or Subdevice are different. If you want to post your file in the diagnosis area and post a link here I'm sure someone will take a look.

Also remember to post your upgrade in the file section.

Thanks, I'll do that. And once I've entered all the extra codes and checked they work on this device, I'll definitely upload the file.

Andre

andrewilley · Post by **andrewilley** » Sat Sep 30, 2017 2:39 am

OK, RMDU files saved and uploaded as follows:

Old Onkyo TX-SR606 amp - http://www.hifi-remote.com/forums/dload ... e_id=14707
New Onkyo TX-NR555 amp - http://www.hifi-remote.com/forums/dload ... e_id=14706

The older TX-SR606 codes are all supported by the TX-NR555's IR receiver too, and I can use (for example) the 606 discrete IR power codes to turn my 555 amp on and off.

For neatness's sake though, I'd prefer to copy the few missing codes from the old 606 group into the 555 group, and then remove the otherwise-obsolete 606 set from my remote, but I don't quite know how to insert them into the new 555 list. Specifically, I'd like the discrete 'Power On' and discrete 'Standby' (OBC 4 and 71) codes, and also Dimmer (OBC 149) moved from the 606 set into the 555 one, but there are others (such as the numeric keys) which would be nice too, so if there is a method I can use to do the task myself that would be great.

Andre

Post by **vickyg2003** » Sat Sep 30, 2017 6:40 am

Okay, the problem is Onkyo uses a hodge podge of signals Nec1, Nec2 and Nec1-F1 signals. One of your uprgades uses a Nec1 Combo. The other upgrade uses a custom verison of "PID:0247". The experts here haven't analyzed this protocol, or we would have known that this protocol should have been read LSB instead of MSB. Then in addition there are 3 OBC fields, that have special meaning in the executor and at this point we don't know how to decode these either.

This is going to take some expert analysis to decode. If this is indeed an f16 combo code, that is worth our time to investigate for the Onkyo receivers.

Make sure you have notifications turned on, or check back on this thread in a few days. If this falls off our radar, make sure to bump the thread in 4 or 5 days.

andrewilley · Post by **andrewilley** » Sat Sep 30, 2017 11:36 am

Thanks, I've got this topic set for notifications anyway.

I might see if I can find another Onkyo code set that works with the NR555 and includes all of the recent keys plus discrete power functions too, which might be easier than trying to mangle two incompatible sets together.

I'm glad it wasn't just me being stupid anyway. Both of the files I uploaded earlier were originally installed on my XSight Touch via the old EZ-RC website, which uses the same device database as One-For-All I believe, and they both control the NR555 amp correctly - but neither individual one contains all of the available codes.

Andre

Post by **vickyg2003** » Sun Oct 01, 2017 6:58 pm

Could an expert look at this? 3FG? Anyone else

I've been looking at Protocols Ini trying to figure out what entry I need to make for PID 02 47 so that we can make additions to the ez-rc upgrade.

PID 02 47 is a Nec F16 Combo Code that has one Device, and a choice of 6 Sub Device Codes. PID 02 46 is Nec1or2 6 Subdevice protocol and I was trying to interpet that but....

I got to this point

DevParms=Device Code=210, Sub Device 1=108, Sub Device 2=109, Sub Device 3=2, Sub Device 4=172, Sub Device 5=30, Sub Device 6=25
DeviceTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8) \
Translator(lsb,comp,2,8,16) Translator(lsb,comp,3,8,24) \
Translator(lsb,comp,4,8,32) Translator(lsb,comp,5,8,40) \
Translator(lsb,comp,6,8,48)
FixedData=B4 C9 49 BF CA 87 67

But when I got Commands I couldn't make heads nor tails of the syntax.
There are 3 bytes in the command.

The 1st Command is the OBC
the 2nd Command would be the inverse of the OBC except where it is an F16 style code.
The 3rd Command pics the Nec repeat style and Sub Device

3rd Byte
Bit 6 is the Nec Style, 1 is Nec1 or Nec2
The lower 3 bits select the Sub Device

3FG · Post by **3FG** » Sun Oct 01, 2017 10:49 pm

Hi Vicky,
Try this

Code: Select all

[NEC-f16 SixSubs]
PID=02 47
DevParms=Device Code=210, Sub Device 1=108, Sub Device 2=109, Sub Device 3=2, Sub Device 4=172, Sub Device 5=30, Sub Device 6=25
DeviceTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8) Translator(lsb,comp,2,8,16)  Translator(lsb,comp,3,8,24) \
Translator(lsb,comp,4,8,32) Translator(lsb,comp,5,8,40) Translator(lsb,comp,6,8,48) 
FixedData=B4 C9 49 BF CA 87 67 
CmdParms=Sub:0|1|2|3|4|5, OBC1:8=0, OBC2:8=255, Style :NEC1|NEC2=0
CmdParmInit=PickInitializer(0,1,2,3,4,5,6)
CmdTranslator=Translator(lsb,comp,1,8,0) Translator(lsb,comp,2,8,8) Translator(3,1,17) Translator(0,3,21)
DefaultCmd=00 00 FF
Notes=Combines 6 subdevices for one device with independent command bytes.  Allows each function to be specified as NEC1 or NEC2.  It is necessary to enter both OBC1 \
 and OBC2 even if it is for a standard NEC signal, i.e. where the second command byte is the binary complement of the first command byte.  
Code.S3C80=43 8b 73 8b 12 cf 4d 08 08 01 21 00 fd 01 21 03 30 d2 dc 11 94 08 b6 e6 10 02 00 11 68 0c 08 c6 56 c0 07 87 20 04 29 04 e4 0a 05 e4 0b 06 37 6d 03 8d 01 46 e6 29 45 8d 01 49 
Code.TI2541=01 07 01 21 73 0E 16 00 15 00 16 00 40 00 0A 10 56 01 AB 00 02 91 40 81 12 08 16 30 0B 07 53 0C 03 30 62 D4 04 70 7A 77 78 80 08 16 30 0B 07 53 0C 03 30 62 54 04 70 7A 77 78

I tried to set this up so that if the OBC2 field is left blank, then RMIR would automatically compute the complement, using OBC2:8=[-1]. It almost sort-of works, but it actually always computes the complement of the most recently entered OBC1, rather than the one on the same line as the blank OBC2 field. I suspect that RMIR could be modified to do what I expect, but there is no other example of this usage for Command Params.

I had to edit andrewilley's RMDU file to set the correct Protocol Name ([NEC-f16 SixSubs]) and the 7 device and subdevice numbers. It appears that the only signal which needs the 0247 executor is Bluetooth with OBC1 = 80 and OBC2 = 14.

andrewilley · Post by **andrewilley** » Mon Oct 02, 2017 1:13 am

Thanks for the hard work there, a bit beyond my understanding as a week-old user at this point of course.

I've emailed Onkyo to ask for a full IR codes list for their TX-NR555 amp, which from comments in their forums seems to be something that they will do for users, so it might be worth waiting to see what I get from them before putting too much work into this? Unless you want to do it anyway for anyone else buying the same brand of course (and even then, the master data would presumably help too, as this issue could be related to however OneForAll created their own version of the codes list?).

Andre

Post by **The Robman** » Mon Oct 02, 2017 12:12 pm

vickyg2003 wrote:Okay, the problem is Onkyo uses a hodge podge of signals Nec1, Nec2 and Nec1-F1 signals. One of your uprgades uses a Nec1 Combo. The other upgrade uses a custom verison of "PID:0247". The experts here haven't analyzed this protocol, or we would have known that this protocol should have been read LSB instead of MSB. Then in addition there are 3 OBC fields, that have special meaning in the executor and at this point we don't know how to decode these either.

Hey Vicky,
Here's my attempt at decoding that new executor:
http://www.hifi-remote.com/forums/dload ... e_id=14722

And here's a spreadsheet that decodes all the codes used in the executor:
http://www.hifi-remote.com/forums/dload ... e_id=14723

Post by **vickyg2003** » Mon Oct 02, 2017 1:00 pm

Rob, are you suggesting we don't use the UEI protocol?

Andre

andrewilley wrote:Thanks for the hard work there, a bit beyond my understanding as a week-old user at this point of course.

Its beyond my understanding and I've been here forever.

Thanks 3FG.

In order to use this you will need to do some editing with NOTEPAD.

Open the protocols.ini with notepad
find this section

Code: Select all

[pid: 02 47]
PID=02 47
Code.S3C80=43 8b 73 8b 12 cf 4d 08 08 01 21 00 fd 01 21 03 30 d2 dc 11 94 08 b6 e6 10 02 00 11 68 0c 08 c6 56 c0 07 87 20 04 29 04 e4 0a 05 e4 0b 06 37 6d 03 8d 01 46 e6 29 45 8d 01 49 
Code.TI2541=01 07 01 21 73 0E 16 00 15 00 16 00 40 00 0A 10 56 01 AB 00 02 91 40 81 12 08 16 30 0B 07 53 0C 03 30 62 D4 04 70 7A 77 78 80 08 16 30 0B 07 53 0C 03 30 62 54 04 70 7A 77 78

Replace it with

Code: Select all

[NEC-f16 SixSubs]
PID=02 47
DevParms=Device Code=210, Sub Device 1=108, Sub Device 2=109, Sub Device 3=2, Sub Device 4=172, Sub Device 5=30, Sub Device 6=25
DeviceTranslator=Translator(lsb,comp,0,8,0) Translator(lsb,comp,1,8,8) Translator(lsb,comp,2,8,16)  Translator(lsb,comp,3,8,24) \
Translator(lsb,comp,4,8,32) Translator(lsb,comp,5,8,40) Translator(lsb,comp,6,8,48)
FixedData=B4 C9 49 BF CA 87 67
CmdParms=Sub:0|1|2|3|4|5, OBC1:8=0, OBC2:8=255, Style :NEC1|NEC2=0
CmdParmInit=PickInitializer(0,1,2,3,4,5,6)
CmdTranslator=Translator(lsb,comp,1,8,0) Translator(lsb,comp,2,8,8) Translator(3,1,17) Translator(0,3,21)
DefaultCmd=00 00 FF
Notes=Combines 6 subdevices for one device with independent command bytes.  Allows each function to be specified as NEC1 or NEC2.  It is necessary to enter both OBC1 \
 and OBC2 even if it is for a standard NEC signal, i.e. where the second command byte is the binary complement of the first command byte. 
Code.S3C80=43 8b 73 8b 12 cf 4d 08 08 01 21 00 fd 01 21 03 30 d2 dc 11 94 08 b6 e6 10 02 00 11 68 0c 08 c6 56 c0 07 87 20 04 29 04 e4 0a 05 e4 0b 06 37 6d 03 8d 01 46 e6 29 45 8d 01 49
Code.TI2541=01 07 01 21 73 0E 16 00 15 00 16 00 40 00 0A 10 56 01 AB 00 02 91 40 81 12 08 16 30 0B 07 53 0C 03 30 62 D4 04 70 7A 77 78 80 08 16 30 0B 07 53 0C 03 30 62 54 04 70 7A 77 78

Then use this upgrade as a starting point;
http://www.hifi-remote.com/forums/dload ... e_id=14724

I've emailed Onkyo to ask for a full IR codes list for their TX-NR555 amp, which from comments in their forums seems to be something that they will do for users, so it might be worth waiting to see what I get from them before putting too much work into this? Unless you want to do it anyway for anyone else buying the same brand of course (and even then, the master data would presumably help too, as this issue could be related to however OneForAll created their own version of the codes list?).

Andre

Andre, for our older remotes having 2 upgrades is no big deal, but for the xsights and Nevos this eats up a device, so its a good thing for all Onkyo users.

Nec 1 protocols have an 8 bit function, and then the next 8 bits are the complement (all 1s changed to 0s all 0s changed to 1s) of that function code. The Onkyo also uses F16 where the first and second bytes of the function are not related in the usual way.

Your responsibility in all this is to post your LG and your Onkyo upgrades in our file section so that we don't have to start over with the next user.

Good Luck

Post by **The Robman** » Mon Oct 02, 2017 1:31 pm

vickyg2003 wrote:Rob, are you suggesting we don't use the UEI protocol?

My file *is* the UIE protocol, it's just a commented PB version so you can see exactly what it's doing. You said that the experts hadn't decoded it yet, so I decoded it.

andrewilley · Post by **andrewilley** » Mon Oct 02, 2017 6:01 pm

If I replace that complete code block within the protocosl.ini file, I can no longer open my saved .rmir files as it says no protocol found with name "pid:02 47" (which of course is true).

Should I just add the new part rather than replacing the old section?

Andre

Post by **vickyg2003** » Mon Oct 02, 2017 6:11 pm

Save a backup before you do this.

Open your RMIR file with Notepad

Find the line that says

Protocol.name=pid\: 02 47

and change it to say

Protocol.name=NEC-f16 SixSubs

Then delete the Onkyo and add my Onkyo.

andrewilley · Post by **andrewilley** » Mon Oct 02, 2017 6:22 pm

Making that change and then importing the new Onkyo upgrade file that you posted, it initially objected to the Setup Code being a duplicate (of the existing 4581) so I changed it to 4582 and that seems to have allowed me to re-save a test .rmir file.

I'll upload it to the XSight in the morning and see how I get on (1:30am here in the UK now).

Andre