good morning,

just got a bunch of pdf's from yamaha with ir codes for various devices i've been requesting.

ID1 CODE, ID2 CODE...
eg: 7E-BA, 7D-64

according to the document the ir format is 16-bit typed custom code NEC format

is there some useful software lying around somewhere to get this into a useable hex code for RTI, Pronto, etc...
As they all take the pure HEX string quite happily

On a side note, will manufacturers have documentation with the full HEX strings & do they willingly provide them?

I'm the type of person that just expects manufacturers to be co-operative & encourage the use of their products, but it seems i'm living in a fantasy world...

Ha Ha



...not laughing at you... just laughing.

You may want to adjust your expectations on this one.

"Pronto" hex as it can be refered to is one way of interpreting/formatting IR.

Some manufacturers (especially installation minded ones) provide basic hexadecimal or binary information about the IR codes, however, that information can look a bit different with different systems. Many control system are now setup to use the Pronto hex format but, unfortunately, few manufacturers have caught on to this and frankly many do not give a damn. There are applications available for download from this site in the Pronto utilities file section (IRTool and make hex are two) that will allow you to analyze and/or generate clean Pronto hex code strings. I would recommend doing some searches on this site for discussions on the use of the software and familiarize yourself with the basics. I regularly analyze and generate my own codes from manufacturer's documentation. I find that if done correctly, it saves me time and headaches over using learned codes, which, I have learned to hate.

thanks for the info above
i'll have a bit more of a look in to it

I'm not sure what you mean by "ID1 Code" etc.

I think I understand 7E-BA and 7D-64. Those are two seperate functions. Each of which has an 8 bit custom code (7E and 7D) plus an 8 bit command code (BA and 64).


It sounds like you're saying "16 bit custom code" (I don't know what "typed" means in this context, so I'm ignoring it). Most manufacturers using NEC format use 16 bit custom codes, but so far as I know Yamaha uses 8 bit custom codes. 7E and 7D are 8 bit custom codes that Yamaha frequently uses.


As already explained in this thread, what you want is called "Pronto Hex". There is no "pure" HEX format. There are many different hex formats, but many non Pronto systems can import Pronto Hex, so some companies (obviously not including Yamaha) treat Pronto Hex as the standard format for IR strings.

Anyway, MakeHex is the tool you want to convert from the form Yamaha gave to Pronto Hex.

Be sure to reade the readme file in makehex.zip.

MakeHex takes input only in decimal. So if I'm right that 7E and 7D are 8 bit custom codes, for MakeHex you would use device number 126 and 125 (7E hex is 126 decimal and MakeHex uses the name "device" for what NEC calls "custom"). Also, use the NEC1.irp file. There is an option in the way NEC protocol is used that is serious enough to make all my software treat NEC as two different protocols, NEC1 and NEC2. The one Yamaha uses is NEC1.

As described in its readme file, MakeHex can be run in a way that labels the output in hex, so if you run it that way and if I'm right that BA and 64 in what you quoted are command codes, then you can find those in the MakeHex output as "function" numbers.

By default MakeHex labels the hex strings with decimal device and function numbers. If you want to create a CCF file with Hex2CCF or IrPanels, you need to leave that default labeling. If you do leave the labeling in decimal you would need to convert the hex command codes you got from Yamaha to decimal in order to look them up in the MakeHex output.


At least one manufacturer has read threads like this in this forum and decided to start using MakeHex themselves and post the output on their web site (after manually replacing the numeric labels by meaninful labels), to save their customers the trouble of figuring out the conversion from the form they originally used to document their codes to Pronto Hex.


Given how small a fraction of their customers use PC programmable remotes that understand Pronto Hex, it isn't surprising that they are so slow about deciding that they ought to provide Pronto Hex.