Your Universal Remote Control Center
RemoteCentral.com
Discrete Code Hunter Forum - View Post
Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Original thread:
Post 13 made on Monday March 31, 2014 at 18:31
SysIntegration
Advanced Member
Joined:
Posts:
December 2013
895
On March 31, 2014 at 09:41, deathvag said...
Hey Alesis!
Do you have a way (preferably a tool ) of doing the opposite. That is having a pronto code and extracting something like this "Power ON = 0x0A 0x58 0x55 0xAA"??
That will be vey helpful!

Ugh. I am sure there is a simpler way. The easiest way is to get a protocol sheet from the manufacturer.

However, it is has been my experience that if a manufacture gives you a protocol sheet, they usually haven't bothered to generate the pronto hex for you.

Here's what you could do. Download IRScrutinizer.


Take your pronto hex and copy and paste it into the scrutinze signal box. (This would be better with screen shots). Scrutinize it.

If we take the code from above, using the steps I just listed, we see that this hex string is

protocol = nec1 device=10 subdevice = 88 obj = 85. We expected this to be an nec1 signal, so we are on the right path. Now we do a little decimal to hexadecimal conversion. If you don't want to do the math mentally: [Link: mathsisfun.com]

10(d) = 0A(h)
88(d) = 58(h)
85(d) = 55 (h)

knowing that hex is usually formatted starting with "0x" we have our pieces and have worked backwards.

Using IRScrutinizer again, we use the Generate tab. It spits out a pronto hex code which we dump back into the scrutinizer tab to verify that it is the same protocol and device as listed above. I am not sure what the 0xAA stands for or does. I don't quite have it all figured out yet. I am also not staring at the protocol sheet. At least this is push in the right direction.
0101001101111001011100110100100101101110011101000110010101100111011100100110000101110100011010010110111101101110


Hosting Services by ipHouse