|
|
|
The following page was printed from RemoteCentral.com:
NEC plasma hex codes: need help getting...
| |
|
Topic: | NEC plasma hex codes: need help getting started... This thread has 19 replies. Displaying posts 1 through 15. |
|
Post 1 made on Thursday February 16, 2006 at 16:43 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
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 ?
|
|
Post 2 made on Thursday February 16, 2006 at 17:12 |
Lyndel McGee RC Moderator |
Joined: Posts: | August 2001 13,006 |
|
|
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
|
Lyndel McGee Philips Pronto Addict/Beta Tester
|
|
OP | Post 3 made on Thursday February 16, 2006 at 17:20 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
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?
Last edited by jrubin
on February 16, 2006 18:05.
|
|
Post 4 made on Thursday February 16, 2006 at 17:25 |
Marky_Mark896 Select Member |
Joined: Posts: | January 2004 1,545 |
|
|
jrubin,
What NEC did you get? I should be getting my NEC 50" tomorrow afternoon. I ordered the XM50.
|
It's not just a hobby, it's an obsession... |
|
OP | Post 5 made on Thursday February 16, 2006 at 17:27 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
50XM5 (don't have it yet)
|
|
Post 6 made on Thursday February 16, 2006 at 21:19 |
johnsfine IR Expert |
Joined: Posts: | September 2002 5,159 |
|
|
On February 16, 2006 at 17:20, jrubin said...
Every single code has Custom 18. About half also have Subcustom 18. That is typical. There are many CCFs for devices with that mix of codes. Should I still use Subcustom as "st"? In that 4 digit number you want custom on the left and subcustom on the right. So the two values are 18E7 and 1818 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? 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.
|
|
OP | Post 7 made on Thursday February 16, 2006 at 21:55 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
On February 16, 2006 at 21:19, johnsfine said...
In that 4 digit number you want custom on the left and subcustom on the right. So the two values are 18E7 and 1818 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?)
Last edited by jrubin
on February 16, 2006 22:11.
|
|
Post 8 made on Friday February 17, 2006 at 02:40 |
Marky_Mark896 Select Member |
Joined: Posts: | January 2004 1,545 |
|
|
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.
|
It's not just a hobby, it's an obsession... |
|
OP | Post 9 made on Friday February 17, 2006 at 08:04 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
On February 17, 2006 at 02:40, Marky_Mark896 said...
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.
|
|
Post 10 made on Friday February 17, 2006 at 09:35 |
Lyndel McGee RC Moderator |
Joined: Posts: | August 2001 13,006 |
|
|
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.
|
Lyndel McGee Philips Pronto Addict/Beta Tester
|
|
OP | Post 11 made on Friday February 17, 2006 at 09:50 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
On February 17, 2006 at 09:35, Lyndel McGee said...
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 Thanks for the help. Just so I'm clear--CCSS in hexadecimal corresponds to 'stuv' in the Pronto IR code?
|
|
Post 12 made on Friday February 17, 2006 at 10:05 |
johnsfine IR Expert |
Joined: Posts: | September 2002 5,159 |
|
|
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.
|
|
OP | Post 13 made on Friday February 17, 2006 at 10:33 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
On February 17, 2006 at 10:05, johnsfine said...
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. Oh--thought that was a 'universal' model. Does that mean my example code in the 1st post won't necessarily work?
|
|
Post 14 made on Friday February 17, 2006 at 10:39 |
johnsfine IR Expert |
Joined: Posts: | September 2002 5,159 |
|
|
On February 17, 2006 at 10:33, jrubin said...
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.
|
|
OP | Post 15 made on Friday February 17, 2006 at 17:43 |
jrubin Long Time Member |
Joined: Posts: | February 2003 37 |
|
|
On February 17, 2006 at 10:39, johnsfine said...
Have you tested any of these codes since starting this thread? 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?
Last edited by jrubin
on February 17, 2006 18:24.
|
|
|
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.
|
|