View previous topic :: View next topic |
Author |
Message |
3FG Expert
Joined: 19 May 2009 Posts: 3371
|
Posted: Wed Dec 08, 2010 1:18 am Post subject: Should we consider these Onkyo signals to be NEC? |
|
|
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. |
|
Back to top |
|
|
mr_d_p_gumby Expert
Joined: 03 Aug 2003 Posts: 1370 Location: Newbury Park, CA |
Posted: Wed Dec 08, 2010 10:36 pm Post subject: Re: Should we consider these Onkyo signals to be NEC? |
|
|
3FG wrote: | 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. |
I think most devices decoding these signals would consider them as comfoming to the timing requirements of NEC, though it is unusual that the final burst in each frame is longer than the others. I wonder if it could just be a learning peculiarity of the particular Pronto they used, or if maybe Onkyo pieced the Pronto codes together by hand from different sources. I have an official Onkyo receiver remote, and it does not display this behavior. _________________ Mike England |
|
Back to top |
|
|
Loto_Bak
Joined: 09 Dec 2010 Posts: 3
|
Posted: Thu Dec 09, 2010 3:27 pm Post subject: |
|
|
Hey guys, I happen to be tackling this exact type of code with my Atlas 30003000 remote.
based on http://www.hifi-remote.com/forums/dload.php?action=file&file_id=7528
this device upgrade has some of these style of codes on the following buttons
game/random
music/repeat
movie/tv/search
Unfortunately none of these buttons work on my remote. All other codes function fine.
Am I able to help you guys with my onkyo hardware?
Any thoughts on how I can get these buttons working?
Thanks!
I'm happy to test and troubleshoot to help get these codes working in IR/decodeir.dll but do not have a learning remote (though I do have a serial Ir reciever used with lirc if it helps) |
|
Back to top |
|
|
3FG Expert
Joined: 19 May 2009 Posts: 3371
|
Posted: Thu Dec 09, 2010 4:43 pm Post subject: |
|
|
You can help by getting the functions to work. The upgrade is seemingly wrong. Functions listed as having device 210.176 should be 210.172.
You can see that on, for example, line 204 of IR Input=Main, where the function code is D2AC D0. That's hexadecimal notation for 210 (D2), 172 (AC) and 208 (D0).
So change device 4 from 176 to 172, and let's hope that works. If it does, then that implies that our executors will work even though the document says it hould be a "20" signal. |
|
Back to top |
|
|
Loto_Bak
Joined: 09 Dec 2010 Posts: 3
|
Posted: Thu Dec 09, 2010 9:29 pm Post subject: |
|
|
Thats got it working 3FG, Thanks!
and thanks for the hex->jp1 primer... simplifies things alot |
|
Back to top |
|
|
Loto_Bak
Joined: 09 Dec 2010 Posts: 3
|
Posted: Thu Dec 09, 2010 11:12 pm Post subject: |
|
|
This onkyo receiver supports 5 different device codes, is the best way to implement a 2nd device upgrade and keymove them? |
|
Back to top |
|
|
The Robman Site Owner
Joined: 01 Aug 2003 Posts: 21279 Location: Chicago, IL |
Posted: Fri Dec 10, 2010 2:33 am Post subject: |
|
|
Loto_Bak wrote: | Thats got it working 3FG, Thanks!
and thanks for the hex->jp1 primer... simplifies things alot |
Cool, I think that confirms that the pronto hex was a misprint rather than a new protocol, thanks for testing. _________________ Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help! |
|
Back to top |
|
|
jetstar52
Joined: 16 Oct 2003 Posts: 177 Location: Sacramento, CA |
|
Back to top |
|
|
|