I apologize if (1) this isn't the right place for this question, and (2) if the question has a completely obvious answer. I've been browsing the forums for several hours with no luck.
I have what I think is a strange situation. I'm using some obscure Chinese chip (a Habey HB1682A IR chip) to act as an environmental control unit in a software suite I'm involved in writing. The chip provides the capability to learn IR signals, as well as send learned signals, or send signals from a pre-programmed set in the chip's ROM.
The goal is to be able to store our own database of codes because the chip's set is outdated and limited. It seems like most databases provide codes in the Pronto hex format. My only issue is, when I observe the data stream received by learning a signal, it doesn't look like it translates directly to what many databases have as an entry for it in the Pronto format. Is there a way to go back and forth between Pronto and what the device would expect from it's own remote?
For a concrete example, I'm using a Toshiba SD-4100 DVD player with a SE-R0301 remote for testing. Learning the Power signal from the remote gives me the following byte stream:
16 86 d0 8f 36 6b 72 82 31 81 1a 21 69 21 23 22 68 22 22 21 22 23 22 21 69 21 22 23 22 21 69 21 22 22 68 23 68 23 68 22 22 21 69 21 22 23 68 23 23 21 23 23 68 22 22 21 22 22 23 21 69 21 22 23 68 23 68 23 23 21 69 21 69 21 69 21 89 c1 82 31 80 8e 21 97 7a 82 31 80 8d 21 97 7a 82 31 80 8d 21 97 79 82 31 80 8d 21 97 79 82 31 80 8d 22 97 7a 82 30 80 8d 22 97 79 82 30 80 8d 22 97 79 82 31 80 8e 21 97 7a 82 31 80 8d 21 97 7a 82 30 80 8e 20 97 79 82 31 80 8e 21 97 7a 82 30 80 8e 21 97 7a 82 30 80 8e 21 97 7a 82 31 80 8e 21 97 7b 82 30 80 8e 21 97 7a 82 31 80 8d 21 97 7b 82 31 80 8e 21 97 7a 82 31 80 8d 21 97 79 82 31 80 8d 22 00 29 be 08
which in integer form is:
22, 134, 208, 143, 54, 107, 114, 130, 49, 129, 26, 33, 105, 33, 35, 34, 104, 34, 34, 33, 34, 35, 34, 33, 105, 33, 34, 35, 34, 33, 105, 33, 34, 34, 104, 35, 104, 35, 104, 34, 34, 33, 105, 33, 34, 35, 104, 35, 35, 33, 35, 35, 104, 34, 34, 33, 34, 34, 35, 33, 105, 33, 34, 35, 104, 35, 104, 35, 35, 33, 105, 33, 105, 33, 105, 33, 137, 193, 130, 49, 128, 142, 33, 151, 122, 130, 49, 128, 141, 33, 151, 122, 130, 49, 128, 141, 33, 151, 121, 130, 49, 128, 141, 33, 151, 121, 130, 49, 128, 141, 34, 151, 122, 130, 48, 128, 141, 34, 151, 121, 130, 48, 128, 141, 34, 151, 121, 130, 49, 128, 142, 33, 151, 122, 130, 49, 128, 141, 33, 151, 122, 130, 48, 128, 142, 32, 151, 121, 130, 49, 128, 142, 33, 151, 122, 130, 48, 128, 142, 33, 151, 122, 130, 48, 128, 142, 33, 151, 122, 130, 49, 128, 142, 33, 151, 123, 130, 48, 128, 142, 33, 151, 122, 130, 49, 128, 141, 33, 151, 123, 130, 49, 128, 142, 33, 151, 122, 130, 49, 128, 141, 33, 151, 121, 130, 49, 128, 141, 34, 0, 41, 190, 8
and as a base64 encoded string:
jzZrcoIxgRohaSEiI2gjIiEjIiMhaSEiIiIhaSEiI2cjZyJoIyIhaSEjI2giIiEiImgiIyEjIiIhaSE iImgjZyIiIWkhaSFpIYnAgjGAjiGXe4IxgI4hl3uCMYCOIZd7gjGAjSGXe4IwgI4hl3uC MYCNIZd6gjGAjSGXe4IxgI0hl3uCMICNIZd7gjGAjiGXeoIxgI0il3uCMYCNIpd7gjGAj iCXe4IxgI0hl3uCMYCNIpd8gjGAjiGXfIIwgI0hl3uCMYCNIZd6gjGAjSEANw==
This doesn't seem to to map into the burst pairs of the Pronto hex for it, which is:
0000 006C 0022 0002 015B 00AD 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0016 0016 0041 0016 0041 0016 0041 0016 05F7 015B 0057 0016 0E6C
|