Jason, THANK YOU, I greatly appreciate your work. They did work great. The processor seems to respond better than it did previously with the learned commands. PLUS, now I have the discrete commands necessary to keep my wife happy.

Jason your NEC device code 16 reference got me all the codes about the same time you posted them. I used makehex to generate the complete NEC device code 16 list and just matched them up down the list. I found five more discrete codes that were not on the TCS sheet. I have figured out two of the 5, just because they were the next two on the NEC device code 16 list...

I think everyone is wanting to know HOW you converted the first one and HOW you knew it was NEC device code 16.

Hi Shaun,
First off I would like to say that I am no expert on Hex codes but I have done some reading on the subject. I am sure if Johnsfine (the person that wrote Make Hex “the best program ever written” I think!) reads this thread he will correct if I`m wrong or maybe have an easier way to do this. When I first saw your code posted it looked like a NEC code to me but it was a little longer than I was use to seeing (see below).

This is how I did it,

I first downloaded this file,(this was before you had posted the PDF file)

[Link: remotecentral.com]

I then loaded it in Pronto Edit NG version 3.1.3.0.Then looked at the hex codes and they read the same as the PRONTO EDIT NG CODE below (I`m using the code you posted above as an example).

YOUR CODE
9000 006d 0000 0002 0010 00ef 0013 00ec

I pasted your code into Pronto Edit NG to see what would happen and it converted it to,

PRONTO EDIT NG CODE
900A 006D 0000 0001 10EF 13EC

Now with hex codes the letters in the code when converted to decimal are as follows,
A=10
B=11
C=12
D=13
E=14
F=15

So to get the device number look at the Pronto Edit code and the 5th group of numbers/letters (10EF) you multiple the first digit by 16 and add the second digit (1 x 16 + 0 =16) this gives you the Device number of 16
Now take the 6th group and do the same (13EC) (1 x 16 + 3 =19) this gives you the function number of 19 which corresponds to the Make Hex file.

If any of the first two digits in the group were letters A,B,C,D,E or F just convert them to decimal as above and you can also use a Scientific Calculator to calculate them for you.

You should be able to find the Device number and Function number in “YOUR CODE” using a similar method by using group 5 and 7 and the last 2 Digits/Letters.

Hope this Helps!

PS. if you want to learn more about this go here


[Link: hifi-remote.com]

Jason,

I am still AMAZED at the fact that you recognized the code as an NEC code. To help the next person trying to do what I was wanting to do (that you DID), I wonder if the first 16 bits of the 24 bit code could be used to setup MAKEHEX to generate the code. That would eliminate the need to 'recognize' the code as 'x' .

Thanks again!

Oh yes I forgot to mention that any short NEC Hex code I have seen always starts with,

PRONTO EDIT NG CODE
900A 006D 0000 0001

Only the last 8 bits change

I would imagine the same for the code you posted,

YOUR CODE
9000 006d 0000 0002

Only the last 16 bits change


I have question for you Shaun;

Which Nevo remote are you using?
Do you like it?

I have had the Nevo SL for 2+ years and really like it. Before the Nevo, I had a Pronto for 5+ years. The Pronto is too big for most people to hold in one hand, but I like the Pronto Edit software better than the Nevo. The hard buttons on the Nevo really make it easy to use in the dark. I would prefer the newer Q50 with even more hard buttons. If you enable WiFi on the Nevo, the battery discharge time is VERY short... If I was buying a remote today, I would buy the Q50 or another SL.

I found another use for the makehex program last night. I am using Girder to control my PC running software to control my speakers. In the past it has been a pain to come up with generic IR codes for girder to receive via the IR reciever. So now, I'll just use device code X and have an endless supply without any effort or fear of duplicating one...

The reason I asked is because I program remotes for a Hifi company in Australia and we currently use Pronto RU960`s which sell`s for $900au ($600us) plus programing and won`t be available anymore which means we will have to use something else.I live in a small town of about 80,000 people and I would like to use the TSU9400 but trying to get people to spend $2100au ($1400us) on a remote is tough,we are getting so ripped off here!Thinking of using TSU9200 ($800au,$536us) for smaller jobs and Q50 ($1100au,$737us) for the larger jobs.I have a feeling the Q50 will go up in price soon!
I like the look of the Q50 and have played with software and seems a little limited.I don`t have a Q50 to play with,but from playing with the software and importing ccf and pdf files I see that you can`t actually see the hex code when you try to edit it,it just say`s learned.Is it the same when you learn a function from an original remote to the Q50 (just say`s learned) or does it learn as a revealed hex?
Do you happen to know how much memory the Q50 has?

I like to play with hex codes!

Due to proprietary software issues (Nevo and Pronto) the Nevo will not show any Hex code apart from what you paste into the software. The codes will work but are not accessible to look at.

Q50 Mem; 64 MB SDRAM & 32 MB NAND Flash

What store do you work at? If you don't mind answering.

What part do you find "limiting" about NSP?