 |
 |
|
|
Discrete Code Hunter Forum - View Post
|
|
 |
|
|
|
 |
|
The following page was printed from RemoteCentral.com:
|
Adcom IR documentation issues?
| |
|
| Topic: | Adcom IR documentation issues? This thread has 2 replies. Displaying all posts. |
|
| Post 1 made on Tuesday July 31, 2007 at 18:58 |
tgrugett Select Member |
Joined:
Posts: | August 2004
1,847 |
|
|
I have been looking at the IR documentation for the Adcom GFR700.
The codes used decode as NEC device 26 and 26.232, however, the documentation indicates the following...
NEC Transmission Format using ADCOM Custom Code (A): 1AE5h
-I would assume this to be device 26.229 (1A=26, E5=229), however, using IRtool these decode as only device 26. Here is the code for the power toggle (function 128)
0000 006d 0022 0000 0155 00ab 0015 0015 0015 003f 0015 0015 0015 003f 0015 003f 0015 0015 0015 0015 0015 0015 0015 003f 0015 0015 0015 003f 0015 0015 0015 0015 0015 003f 0015 003f 0015 003f 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 003f 0015 003f 0015 003f 0015 003f 0015 003f 0015 003f 0015 003f 0015 003f 0015 0015 0015 05f5
NEC Transmission Format using ADCOM Custom Code (B): 1AE8h
-I would assume this to be device 26.232 (1A=26, E8=232). These decode as 26.232. here is the code for discrete off (function 85)
0000 006d 0022 0000 0155 00ab 0015 0015 0015 003f 0015 0015 0015 003f 0015 003f 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 003f 0015 0015 0015 003f 0015 003f 0015 003f 0015 003f 0015 0015 0015 003f 0015 0015 0015 003f 0015 0015 0015 003f 0015 0015 0015 0015 0015 003f 0015 0015 0015 003f 0015 0015 0015 003f 0015 0015 0015 003f 0015 05f5
This seems like it should be simple to understand but I can not figure out if the documentation is not accurate or if IRtool is not decoding properly for the 1AE5 codes
I can email the documentation if someone would like to take a look. It just lists the information I included above plus both hex and decimal versions of the function codes.
|
|
|
| Post 2 made on Tuesday July 31, 2007 at 19:43 |
johnsfine IR Expert |
Joined:
Posts: | September 2002
5,159 |
|
|
The rule for NEC device numbers is that when the two halves of the custom code add up to FF, the device number is based on just the first half, but when they don't add up to FF you need both halves.
1A+E5 = FF so custom code 1AE5 is device 26
1A+E8 is not FF, so custom code 1AE8 is device 26.232
The rule comes from an earlier form of the protocol in which the two halves of the custom code always added to FF and the second half normally wasn't mentioned.
|
|
| OP | Post 3 made on Tuesday July 31, 2007 at 21:38 |
tgrugett Select Member |
Joined:
Posts: | August 2004
1,847 |
|
|
Thank you John for the clarification.
|
|
|
 |
Before you can reply to a message... |
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now. |
Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.
|
|
|
|
|
