Hey all, I've never built a hex code before.  I need it to use with an AMX system.  AMX has an IR Edit program that will allow IR files to be generated from hex code.

When I asked Infocus for the discreet hex codes, I was directed to their website to download.  However, the "download" is not an actual IR file.  It was a PDF with the following information:

Power ON: 2A
HDMI 1: 81
HDMI 2: 82
PC: 83
VGA: 98
Power OFF: 25

Obviously, just the number "2A" is useless to me in just that form.  How do I create a hex code from this?

 

Post the link to the PDF.

Ahh...that makes sense...

Sorry, here you are:

[Link: infocus.de]

The codes on the first page are just the codes for the IR remote control. I could just capture them from the remote, if necessary.

The discrete codes on the second page are the ones I need.


BTW, the pdf indicates that the monitor (called a "panel" in the pdf) requires a certain version of firmware to work with the discrete IR codes. The monitor does have the correct firmware.

Get IrScrutinizer, under Options change Output Text Format to CCF (Pronto,Hex), go to the Generate tab.  In the PDF, the Customer code is listed as 0x0080.  Put 0 in the D field, 0x80 in the S fiield, and the function number in the F field. Click Generate.  Try a non-discrete code first.  For example, Power toggle is 0x03
Power toggle NEC 0.128 function 0x03
0000 006C 0022 0002 015B 00AD 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0041 0016 0726 015B 0057 0016 0E6C

We need to try this first, because there is no standard for the byte order on NEC signal descriptions It could be that 0x80 should go in the D, and 0 in the S.

Probable Discrete On function 0x2A
0000 006C 0022 0002 015B 00AD 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0016 0016 0041 0016 0041 0016 0726 015B 0057 0016 0E6C

3FG,

Thanks, much for your help. I'll check out IRScrutinizer.

Well, I downloaded and installed IRScrutinizer. Using the hex codes it generates, I was able to make an IR file with IR Edit from AMX. I made two files. One IR file was created putting the 0 in the D field and the 0x80 in the S field. I made the other file reversing the order of 0 and 0x80.

I'll find out next week how it works as I'll be back on site then and can test.

Thanks, again, for the help. Hopefully, this will work!

hello tpsmith, did you ever get the discrete codes you created to work? any info will help, thanks in advance

I have some codes I have been trying to work through for about a year. It's only been in the last few weeks that I understood how to convert with codes listed like the ones above (non hex).

The customer code is listed as "00FF"

I put 0x00 in the D field and 0xFF in S field. Is that correct? The codes I generated didn't work, but then I had my output set on raw instead of pronto hex.

[Link: dropbox.com]

Here's a link to the document.

Yes, 0 in D and 0xFF in S is probably correct.  Of course, you do need to have selected CCF as the output type.

I guess I just realized I don't know the difference in raw and pronto hex. I thought pronto was showing raw.

That's just a question of terminology.  In IrScrutinizer, raw presents data as decimal number of microseconds.  A preceding + sign means On, and a - sign means Off.  IRScope calls this a timing list.

Pronto remotes also have a format called raw, which is much longer than Pronto Hex.  I don't think anyone has published an explanation of this format.

I am clearly using you for you knowledge here. I understand that different manufactures use the same terms to mean different things (like NAD ARC (receiver microphone). So that certainly generates confusion. :-(

I guess I am trying to understand the value of a timing list when it seems that pronto hex encapsulates that information in its hex.

There are a lot of formats for describing IR signals.  I'm not sure why Pronto Hex became the most used format.  The timing list format offers better time resolution, and most of us interpret decimal numbers more easily than hexadecimal.  Both of these formats are quite redundant for most signals.  Formats which identify the burst pairs, assign an index to these, and then list the sequence of indices are much more compact.  Even shorter is Denon device 2 function 193.  Compare this to the equivalent Pronto HEx
0000 006D 0000 0020 000A 001E 000A 0046 000A 001E 000A 001E 000A 001E 000A 0046 000A 001E 000A 001E 000A 001E 000A 001E 000A 001E 000A 0046 000A 0046 000A 001E 000A 001E 000A 0679 000A 001E 000A 0046 000A 001E 000A 001E 000A 001E 000A 001E 000A 0046 000A 0046 000A 0046 000A 0046 000A 0046 000A 001E 000A 001E 000A 0046 000A 0046 000A 0679.

Another issue with Pronto Hex or a timing list is that it tends to obscure the relationships between a whole set of signals.  IRP notation allows us to see the entire system employed by an IR protocol:
Denon (Sharp) is
 {38k,264}<1,-3|1,-7>(D:5,F:8,0:2,1,-165,D:5,~F:8,3:2,1,-165)+