Just got the the list of remote codes from NEC. I've searched & read what's been posted on the forum (didn't really understand most of it) but need some guidance getting started

As an example the HEX code for Video1 is
Custom 18
Sub custom E7
Data 55

Does this mean the IR code should be
900A 006D 0000 0001 E718 55AA
?

I would suspect that that the E7 and 18 should be reversed, especially if the standard device ID is 24 decimal (18 hex).

Try em both but you may be on target. You could, in theory look at some other PCFs for the NEC Plasma, providing they are available and compare the codes.

Lyndel

Thanks.
Every single code has Custom 18.
About half also have Subcustom 18.

Should I still use Subcustom as "st"?


Also, why is the resulting code so much shorter than learned IR codes? Do I need to do anything else to this string, or just paste it into PPENG?

jrubin,

What NEC did you get? I should be getting my NEC 50" tomorrow afternoon. I ordered the XM50.

50XM5 (don't have it yet)

That is typical. There are many CCFs for devices with that mix of codes.


In that 4 digit number you want custom on the left and subcustom on the right. So the two values are
18E7 and 1818


Normal Pronto Hex is recording of the timing details of the IR signal. The condensed form of Pronto hex is just the id of the IR protocol and the data to be encoded into the signal. The firmware of the Pronto includes the encoding rules to translate that small amount of data into the correctly timed series of IR pulses.

Just paste the short 900A... string into PPENG where you would paste ordinary Pronto Hex.

I lost you on this--don't understand what you're referring to with the 4-digit number & what the 2 values correspond to.

thanks-

(should stuv be custom|subcustom?)

jrubin,

Stay in touch, because I am getting my 50MX5 this afternoon. We'll compare notes, and also remote codes, although I left my 7000 in South Carolina and moved to Toledo. I'll eventually have my 7000 again.

I set up an Excel spreadsheet that translates the hex codes into the Pronto format--I can email it to you if you want.

The 4-digit number is 18E7 or 1818. Remember these are hexadecimal digits. Hence, a 4-digit number.

18E7 -> 18 is code E7 is subcode
1818 -> 18 is code 18 is subcode

So, the format is CCSS where 'CC' is the custom code in hexadecimal and 'E7' or '18' is the subcode in hexadecimal.

What you may or may not know is that many vendors supply data in either hexadecimal ore decimal format. With a number like 18, it's hard to tell. However, when 'E7' is presented, you immediately suspect you are working with digits 0-9 and A-F which are known a base-16 or hexadecimal values.

Thanks for the help. Just so I'm clear--CCSS in hexadecimal corresponds to 'stuv' in the Pronto IR code?

The "stuv" you are quoting was just a placeholder I typed into some description in some other thread of how to construct "900A" format proto hex.

There is no generally accepted meaning for "stuv" in discussion of Pronto Hex.

But, the value 18E7 or 1818 that Lydel described as CCSS does correctly fit the position where I had "stuv" in that description in that other thread.

Oh--thought that was a 'universal' model. Does that mean my example code in the 1st post won't necessarily work?

Have you tested any of these codes since starting this thread?

I am pretty confident your example in the 1st post WON'T work, because you used E718 where you needed 18E7.

But the rule I described in that other thread (a few other threads, so I'm not sure which you got your info from) still applies. So if you use 18E7 not E718, I expect it to work.

Haven't gotten the display yet...


I really appreciate your help with this but you seem to be saying contradictory things in your above posts about the "900A 006D 0000 0001 stuv wxyz" format--
is this format (with stuv=CCss) the correct one to use?