Hi,

I've followed the process described in the forum to discover discrete codes:

Learn a code using Pronto
Pass the Hex to IrTool
Pass the protocol and device to MakeHex
Use IRPanel to build a new CCF
Ready to test the codes.

My question is:

What does OBC and EFC mean? I haven't used these anywhere in the process. Can I use these numbers to find the original learned code in the list generated by MakeHex?

I'm particularly concerned because I couldn't find the original learned code in the list originated by MakeHex, but I guess this may be related to garbage in the learning process.

If that helps somehow, I'm coying the information generated by IrTool:

>>ScreenToogle
Protocol:NEC1
Device:80
OBC:75
EFC:43

>>InputToogle
Protocol:NEC1
Device:80
OBC:9
EFC:57

The OBC number from the decoder is another name for the function number in the MakeHex output.

So you would select the NEC1.IRP file and edit it to be device 80. Then drop it on MakeHex.exe producing a new NEC1.HEX. Then (for Screen Toggle) look into NEC1.HEX with a text editor (such as Notepad) and find the Pronto Hex that comes right below a label line reading:
Device Code: 80 Function: 75

If you passed the MakeHex output through IrPanels, then the OBC number will be the number displayed on the button produced by IrPanels, so in the above example, you would find button 75 in that CCF file. (OBC means Original Button Code).

The EFC number is a stupid encription of the OBC number that is used by OneForAll brand remotes. The EFC number is completely irrelevent if you are not using a OneForAll (or a few rebrandings of it) remote.

Great,
Thanks for the reply. But what about the difference between the original code learned by Pronto and the code generated by MakeHex?

>>Original code:

0000 006d 0024 0000 0155 00ab 0016 0015 0015 0015 0016 0015 0015 0015 0016 003f 0016 0015 0015 0040 0015 0015 0016 003f 0016 003f 0016 003f 0016 003f 0016 0015 0015 0040 0015 0015 0016 003f 0016 003f 0016 003f 0016 0015 0015 0040 0015 0015 0016 0015 0015 0040 0015 0015 0016 0015 0015 0015 0016 003f 0016 0015 0015 0040 0015 0040 0015 0015 0016 003f 0016 05f7 0155 0055 0016 00ab

->Information provided by IrTool:

Protocol:NEC1
Device:80
OBC:75
EFC:43

Carrier:006d
0:0016 0016
1:0016 003f
Raw:0155 00ab 0 0 0 0 1 0 1 0 1 1 1 1 0 1 0 1 1 1 0 1 0 0 1 0 0 0 1 0 1 1 0 1 0016 05f7 0155 0055 0016 00ab

>>Code generated by MakeHex (Protocol Nec1, Device 80,function 75)

Device Code: 80 Function: 75
0000 006D 0022 0002 0157 00AC 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0689 0157 0056 0015 0E94

Are they equivalent? This look like greek to me...

If you knew the basics of reading Pronto Hex you could see that almost all the differences between the learned version and the constructed clean version are insignificant (don't have any detectable impact on the actual IR signal generated).

(I'm not saying you need to or even should learn to read Pronto Hex, just that you can't judge whether two examples of Pronto Hex are the same by just looking at them textually).

There is one significant difference between the two.

The first has captured the specific length of the keypress used during learning, so that when you use the command from your Pronto the length of any Pronto keypress won't matter. It will always reproduce the length of the original learned keypress.

The reconstructed Pronto Hex string has generalized length so that when you use it the length it sends will depend on the length of time you press the button.

In most cases you want generalized length. The Pronto always attempts to learn the generalized length when it learns from the original remote. But sometimes, like this time, it fails and learns the specific length instead.

For this particular signal (Screen Toggle) I expect that the TV doesn't care about the length of the button press. So this difference will have no real impact.

The clean code worked perfectly. Thanks for the help.