Should we consider these Onkyo signals to be NEC?
Posted: Wed Dec 08, 2010 12:18 am
This spreadsheet lists the device and function numbers as well as Pronto Hex for all of the Onkyo receivers. Functions which have already been defined for a few years appear to be in the usual NEC format. Newer IR signals are similar to the following example Pronto represention:
D2AC 9F (device 210.172 OBC 159)
(Values in bold are unusual)
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 0016 0015 0041 0015 0041 0015 0016
0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041
0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016
0015 0041 0015 0041 0015 0016 0020 05EE 0156 0056 0020 0E54
Ordinary NEC expects these two bolded words to be 0015. DecodeIR.dll does not recoginize these "20" signals, although it does handle values between 00 and 1F. IR.exe v8.03 can import these Pronto Hex representations, and does decode the straight NEC versions correctly, but apparently with logic separate to DecodeIR.dll.
However, some defined signals have 16 independent bits of function data. For example:
D21E50 00 Volume Level Up 1dB Step (almost NEC2)
D21E 50 94 HDMI Out: Both
IR recognizes these as NEC2, but misses the second byte of function data. With the first 0020 changed to 001F, the 2.41b test version of DecodeIR describes these as NEC2-f16 and NEC1-f16.
Do we consider these 20 signals to be valid NEC? Should our tools describe them that way? Do Onkyo receivers care whether it sees a 20 or a 15? I assume that we have no executor which uses 15 for nearly all On durations, but sends a duration of 20 in the lead outs.
D2AC 9F (device 210.172 OBC 159)
(Values in bold are unusual)
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 0016 0015 0041 0015 0041 0015 0016
0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041
0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016
0015 0041 0015 0041 0015 0016 0020 05EE 0156 0056 0020 0E54
Ordinary NEC expects these two bolded words to be 0015. DecodeIR.dll does not recoginize these "20" signals, although it does handle values between 00 and 1F. IR.exe v8.03 can import these Pronto Hex representations, and does decode the straight NEC versions correctly, but apparently with logic separate to DecodeIR.dll.
However, some defined signals have 16 independent bits of function data. For example:
D21E50 00 Volume Level Up 1dB Step (almost NEC2)
D21E 50 94 HDMI Out: Both
IR recognizes these as NEC2, but misses the second byte of function data. With the first 0020 changed to 001F, the 2.41b test version of DecodeIR describes these as NEC2-f16 and NEC1-f16.
Do we consider these 20 signals to be valid NEC? Should our tools describe them that way? Do Onkyo receivers care whether it sees a 20 or a 15? I assume that we have no executor which uses 15 for nearly all On durations, but sends a duration of 20 in the lead outs.