JP1 Remotes

Thanks for explaining this.

The naming "device 3" is from the custom protocol Vicky created for NEC1-f16, see details here .

As a reference, the byte "grouping" used in the original spreadsheet for the onkyo ir commands:

NEC1: D26C D2 (HDMI SELECT)
NEC1-f16: D21E 50 94 (HDMI BOTH)

From this I ...

Decoding a NEC1-f16 style pronto hex code in IRTool using 2.42BETA the output is missing the OBC and returning device 3 instead.

Example:

0000 006c 0022 0002 0156 00ac 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 ...

Using the information I added the following new section to protocols.ini:

[NEC1-f16]
PID=00 0F
CmdTranslator=Translator(lsb,0)
CmdParms=OBC
DefaultCmd=00
CmdIndex=0
DevParms=Device 1=133,Device 2=227,Device 3=39
DeviceTranslator=Translator(lsb,0) Translator(lsb,1,8,8) \
Translator(lsb,2,8,16 ...

A complete list of discrete ir codes can be downloaded from

http://www.awe-europe.com/ir_232.html

The older commands are 3 byte giving device, sub device, and obc in NEC1 protocol. As multiple sub devices are used the NEC1 Combo protocol can be used to create a device upgrade. Example:

D26C D2 ...