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

Login:
Pass:
 
 

Topic:
Trying to generate HEX code using MakeHEX, need help please!
This thread has 7 replies. Displaying all posts.
Post 1 made on Saturday May 27, 2006 at 09:38
Brian Garner
Long Time Member
Joined:
Posts:
November 2004
35
Good day,

I have read lots on this forum and other forums, yet I can't seem to get my Monoprice HDMI 5x1 switcher to work. I contacted the company and they sent me the following:

IR protocol decode
------------------
Monoprice 5x1 HDMI switch
Protocol: NECx1
Main Device #: 8
Sub Device #: 8

EFC
058 Input 1
119 Input 2
249 Input 3
250 Input 4
244 Input 5
052 Input Up
056 Input Down

I then proceeded to download MakeHex and modify the NECx1.irp file and it now looks like this:

Device=8.8
Function=0..255

Protocol=NECx1
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=8,-8
Suffix=1,-78
Default S=D
R-Suffix=~D:1,1,-170
Form=*,D:8,S:8,F:8,~F:8,_;*,_

I ran the program and generated a file that had all of the HEX values. I then decided as a test to copy Function:58 from the file as I assumed that Function 58 would be the same for EFC 058 which would be Input 1? I then imported the file into my RTI remote control database as the RTI remote is able to read it.

When I try to use the code, nothing happens.

Can someone take a look and let me know if it is something that I did wrong. I am fairly new at this stuff so if anyone has recommendations, please feel free to suggest.

Thanks,

Brian
Thanks, and have a great day!
Brian
Post 2 made on Saturday May 27, 2006 at 10:43
Glackowitz
RC Moderator
Joined:
Posts:
May 2002
3,763
Brian, Try these out

Input 1
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0689 0157 0056 0015 0E94

Input 2
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 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 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0041 0015 0689 0157 0056 0015 0E94

Input 3
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0689 0157 0056 0015 0E94

Input 4
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0689 0157 0056 0015 0E94

Input 5
0000 006D 0022 0002 0157 00AC 0015 0016 0015 0016 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0041 0015 0016 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0041 0015 0016 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0689 0157 0056 0015 0E94

These are a device 8 only..they might not work, try using device 1.8.8 as well
I have only used the make hex a few times and it worked fine but I could be wrong on these

Last edited by Glackowitz on May 27, 2006 11:25.
The letters T and G are very close to each other on a keyboard. This recently became all too apparent to me and consequently I will never be ending a work email with the phrase "Regards" again.
Post 3 made on Saturday May 27, 2006 at 12:41
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
On May 27, 2006 at 09:38, Brian Garner said...
I contacted the company and
they sent me the following:

Wow! I know a lot of companies have adopted Pronto Hex as a format for publishing IR data, and JP1 may be comperable to Pronto Hex for the number of end users who work with IR signals in that form. But I don't think I've ever seen a device manufacturer publish their IR data in JP1 format (as you quoted).

The part that indicates NECx1 device 8.8 is equally valid for MakeHex as for JP1.

But EFC numbers are only valid in JP1 and related (OneForAll) remotes.

An EFC number is a stupidly encripted form of the function number, invented by OneForAll to keep function numbers published in that form from being useful to other brands of universal remote.

But the encription is crude enough that many people have posted programs and tables for decripting them back to the true function numbers.

15 Input 1
18 Input 2
25 Input 3
31 Input 4
28 Input 5
12 Input Up
13 Input Down
OP | Post 4 made on Saturday May 27, 2006 at 13:47
Brian Garner
Long Time Member
Joined:
Posts:
November 2004
35
Thanks everyone for the tips. Going to try it out later today. Now the wife wants me outside to do some gardening :(
Thanks, and have a great day!
Brian
OP | Post 5 made on Saturday May 27, 2006 at 21:08
Brian Garner
Long Time Member
Joined:
Posts:
November 2004
35
Again, I would like to say thanks. Everything works great now. Will have to do more reading on the EFC number. Didn't know that it was a proprietary number that was created just for the OneForAll remotes.
Thanks, and have a great day!
Brian
Post 6 made on Sunday May 28, 2006 at 07:23
johnsfine
IR Expert
Joined:
Posts:
September 2002
5,159
Most of the JP1 software works with both the EFC numbers (just for OneForAll and related remote) and OBC numbers (the non encripted function number).

The main JP1 programs (IR, KM and RM) each include translators to convert EFC to and from OBC.

When programming those remotes on the remote itself, rather than through JP1, only EFC numbers work, not OBC.

OBC = "Original Button Code" is just another name for the function number.
Post 7 made on Sunday October 16, 2011 at 18:22
jtreibick
Long Time Member
Joined:
Posts:
May 2007
15
When using my URC MX-900 remote I found that the above pronto hex did not work for me. The hex from the following page did work.

[Link: avsforum.com]

edit:now I see my mistake for trying to use the above hex directly with URC... either way the precompiled pronto hex is linked.

Last edited by jtreibick on October 31, 2011 19:18.
Post 8 made on Monday October 17, 2011 at 15:54
3FG
Select Member
Joined:
Posts:
August 2009
1,861
Yes, the Pronto Hex shown in post #2 are simply mistaken (and the post suggests that the codes may be incorrect). It was created using the NEC1 IR protocol instead of the correct NECx1, and confuses an EFC number for the actual function number. It shouldn't be expected to work with any remote.

The function numbers in post #3 are correct, and can be used with MakeHex to get the correct Pronto Hex. Of course, the above link also has the correct Pronto Hex.


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse