Which tool to create hex

kdp99 · Post by **kdp99** » Fri Apr 27, 2012 3:17 am

Hi,

I have been floundering round in the tools section, can some one point me to the correct one.

I need to create pronto hex from data such as the example below (I have a few to do)

Many thanks

Protocol NEC2
Device 128
Sub device
OBC 2
Hex cmd BF
EFC 183

Post by **The Robman** » Fri Apr 27, 2012 6:41 am

The tool that you need is called MakeHex.

kdp99 · Post by **kdp99** » Fri Apr 27, 2012 7:04 am

The Robman wrote:The tool that you need is called MakeHex.

Firstly many thanks, As a test I have tried it with a the numbers above which I have the Hex data from in IR has I have learned it OK, and get different numbers, I am being thick or is this OK.

MakeHex gives

Protocol=nec2 Device=128.0 Function=183..183
Device Code: 128.0 (0x80.0x00) Function: 183 (0xB7)
0000 006D 0000 0022 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0689

IR Gives

0000 006E 0024 0002 00C4 013A 0014 0017 0014 0017 0014 0017 0014 0017 0014 0017 0014 0017 0014 0017 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 0017 0014 0017 0014 0041 0014 0017 0014 0017 0014 0017 0014 0017 0014 0017 0014 0017 0014 0041 0014 0017 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 0041 0014 05E6 0055 0155 0115 0D35 0055 0155 0115 0D35

Post by **The Robman** » Fri Apr 27, 2012 11:38 am

Your original post indicated that you wanted NEC2 device code 128, with *no* sub-device code whereas you created an NEC2 signal with device code 128 *and* sub-device code 0, which is different.

I'm not sure how you generated the "IR Gives" signal but that appears to be an NEC1 signal, not NEC2.

You didn't mention what device this is for, so I can't verify what the correct protocol is, but looking at our files, every device that uses NEC with device code 128 uses NEC1, so I'm guessing that's the correct protocol.

Here's what I got when I tried it.

Device Code: 128 Function: 183
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0689 0157 0056 0015 0E94

kdp99 · Post by **kdp99** » Fri Apr 27, 2012 12:56 pm

Rob,

Thanks for the help and pointers, I have looked again and still it does not look right, I have uploaded a file kdp99makehex.doc to the upload area, I am sure I am being stupid but can't see where !?

Many thanks again.

Post by **The Robman** » Fri Apr 27, 2012 3:11 pm

Here's a link to the file, in case anyone wants to look at it:
http://www.hifi-remote.com/forums/dload ... e_id=10900

Post by **The Robman** » Fri Apr 27, 2012 3:35 pm

kdp99 wrote:Rob,

Thanks for the help and pointers, I have looked again and still it does not look right, I have uploaded a file kdp99makehex.doc to the upload area, I am sure I am being stupid but can't see where !?

Many thanks again.

You entered 0 as the device code, when you said you wanted 128.

kdp99 · Post by **kdp99** » Sat Apr 28, 2012 1:18 am

The Robman wrote:You entered 0 as the device code, when you said you wanted 128.

Yes my error at the start, all the stuff in the word file I uploaded is consistent (I hope), I have also uploaded the IR file, HEADATA3.IR

3FG · Post by **3FG** » Sat Apr 28, 2012 1:38 am

In the uploaded Word file, the decode from IR is NEC1 device 0, OBC 10. You should enter 10 into the function boxes in MakHex GUI. Instead you've entered 55, which is the EFC value.

Besides the function number, there are some small differences in the two versions of Pronto Hex, e.g. 006C versus 006D in the frequency specifier (second quad of hex data). These are not important. Also, the learned signal has the main IR signal plus a "ditto" repeat, while the MakeHex version doesn't have the ditto. Usually, the device that accepts the Pronto Hex will manage the repeat behavior, so the MakeHex version is OK.

In other words, enter the OBC instead of the EFC and I think it should work.

kdp99 · Post by **kdp99** » Sat Apr 28, 2012 2:49 am

3FG wrote:In the uploaded Word file, the decode from IR is NEC1 device 0, OBC 10. You should enter 10 into the function boxes in MakHex GUI. Instead you've entered 55, which is the EFC value.

Besides the function number, there are some small differences in the two versions of Pronto Hex, e.g. 006C versus 006D in the frequency specifier (second quad of hex data). These are not important. Also, the learned signal has the main IR signal plus a "ditto" repeat, while the MakeHex version doesn't have the ditto. Usually, the device that accepts the Pronto Hex will manage the repeat behavior, so the MakeHex version is OK.

In other words, enter the OBC instead of the EFC and I think it should work.

MANY THANKS, that works. I had actually looked at the Hex for 10 and 55 but the small differences you mention threw me, all now working fine.

Thanks again