Hello there,

i need the hex codes for the LG 50PC1R (europe model) in CCF format. The thing is that i need
to get into a special service menu, which should be accessible with the
"functions" 251 - 255 as i have read.

I recorded (learning mode) the power-key with the following output

0000 0067 0000 0024 0168 00b2 0016 0016 0016 0016 0016 0044 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0044 0016 0044 0016 0016 0016 0044 0016 0044 0016 0044 0016 0044 0016 0044 0016 0016 0016 0016 0016 0016 0016 0044 0016 0016 0016 0016 0016 0016 0016 0016 0016 0044 0016 0044 0016 0044 0016 0016 0016 0044 0016 0044 0016 0044 0016 0044 0016 0660 0168 005a 0016 9d1e

If i use this hex key with the CCF format it works perfectly.

But i dont know what i have to modify to access functions form 251 till 255.

I tried to generate the hex codes i need with makehex and the correct settings i read here in the forums (NEC1, Device 4, Funktion 1 - 255) but it doesnt work :(

The generated hex code looks MUCH different to the (working) powerkey:

0000 006D 0022 0002 0157 00AC 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0689 0157 0056 0015 0E94

Also it seems that all other LG users have no problems with these codes, they all look the slightly the same but really different from my (working) power-key.

I like to use the functions from here (service menu etc.)

[Link: remotecentral.com]

In a german forum i read i have to use this with a pronto (i interpreted and generated
with makehex, also without any success)

Protokoll: Nec1
Device ID: 4
Function: 251 bis 255

Sorry for my bad english, im from germany :)

I hope someone can help me, i spend all the day with trying and without any success :((

Can anyone decode my learned IR Code like jarmstrong here?

[Link: remotecentral.com]

Maybe if someone can, he can tell me how to get the hex codes for the other functions
(1 - 255)?

That is NEC1 protocol (not a very good learn, but not bad enough to be surprising that you say it works). It is device 4, function 8.



That is device 4, function 196. Try function 8 from the generated signals. It still won't look like your learned function 8, but it will send the same signal to your device.


I see you chose the power on signal from that list and you correctly used the OBC number 196 (you should not use the EFC number 172). But you say it didn't work.

If your model even supports that command, it probably needs a long duration. Did you test it in a macro? Or did you test it alone on a button? I understand you will want to use it in a macro, but it is a good idea to test it by itself first. When an IR signal is the only action on a button's action list, you can send a long duration by pressing the button a long time (so you can find out whether a long duration makes it work). In a macro, sending a long duration is more complicated.


I did, but you could easily decode such signals yourself, using DecodeIr.dll plus the JP1 version of IrTool.exe
[Link: hifi-remote.com]
[Link: remotecentral.com]

Thank you very much!

I'll try to decode with the tools you linked.

I tried to send the signal a longer time (i didn't use macro and i don't need them).

All i need is to get working hex codes for the functions 251 till 255. They didnt work, so i thought i made something wrong with makehex, so i thought i should try my own generated hex codes at first with the power on function which also didnt work as i have written.

I use TotalRemote on my PDA.

I'm only doing this because i need to access a menu which is only accessible with a special service remote from LG. I got the codes and (251 till 255) now i only need the matching hex codes for the functions 251 till 255.

Maybe, can you generate these hex codes for me or tell me what am I doing wrong with makehex?

This is how i generated my Codes:

makehex nec1.irp myhexcodes.txt

content of nec1.irp:

Device=4
Function=0..255

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

Then i tried the matching functions that should work (like power, mute, etc.) and they didnt...

Thanks a lot johnsfine, it's so good not to be left alone with a problem and materia i don't understand :)

I tried function 8 - no go - it doesn't work.

I decoded my learned power-on and it was NEC12 Device 4 Function 8, when i decode
my non working hex function 8:

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

it says NEC1. Do i have to create a NEC12 hex code? (i don't know how to do that)

I think i am doing something wrong with makehex.....

it says NEC12 of course, sorry....

i tryed again with pushing the button a very long time without any success....

I found the english manual for the LG and on page 86 there is IR information. Function 8 should be correct for Power on...

REMOTE CONTROL IR CODES
(CHoexdae) Function Note
(CHoexdae) Function Note
0F TV R/C Button
0B INPUT R/C Button
08 POWER R/C Button (Power On/Off)
C4 POWER ON Discrete IR Code (Only Power On)
C5 POWER OFF Discrete IR Code (Only Power OFF)
60 PIP R/C Button
0E SLEEP R/C Button
20 TEXT R/C Button
0A I/II R/C Button
43 MENU R/C Button
79 ARC R/C Button
5B EXIT R/C Button
07 F R/C Button
06 G R/C Button
40 D R/C Button
41 E R/C Button
44 OK R/C Button
72 PIP PR- R/C Button
71 PIP PR+ R/C Button
63 SWAP R/C Button
61 PIP INPUT R/C Button
72 RED R/C Button
71 GREEN R/C Button
63 YELLOW R/C Button
61 BLUE R/C Button
02 VOL + R/C Button
03 VOL - R/C Button
00 PR + R/C Button
01 PR - R/C Button
09 MUTE R/C Button
53 LIST R/C Button
10 ~ 19 Number Key 0 ~ 9 R/C Button
1E FAVOURITE R/C Button
1A Q.VIEW R/C Button
64 SIZE R/C Button
62 PIP: POSITION, R/C Button
Teletext: UPDATE R/C Button
70 INDEX R/C Button
26 TIME R/C Button
2A REVEAL R/C Button
E0 + R/C Button
E1 - R/C Button

there is also additional information:

2. Remote Control IR Codes
■ Output waveform
Single pulse, modulated with 37.917KHz signal at 455KHz

Carrier frequency
FCAR = 1/TC = fOSC/12
Duty ratio = T1/TC = 1/3

and more, i uploaded the document here:

[Link: 212.75.33.120]

I have no guess what you are doing wrong. It should have worked.


NEC12 usually (and this time for sure) means an NEC1 signal was learned by some device that didn't understand the NEC1 repeat pattern. NEC1 is corect for your device. NEC12 is incorrect, but in a subtle way that often doesn't matter.

That confirms that the protocol is what is called NEC1 in MakeHex and in DecodeIr. It also shows the function numbers.

So far as I can tell, it doesn't tell the value of the "Custom Code" (which translates into the device number in MakeHex and DecodeIr). It mentions the Custom Code and tells you where the custom code is positioned within an NEC1 signal (but of course I already knew that). But it doesn't seem to say what value goes in that position.

We have plenty of other sources of information telling us the correct device number is 4. So I'm sure the device number is not the problem. Your results from MakeHex are also correct. So the problem has to be in how you used those Pronto Hex strings after getting them from MakeHex.

Ok. This is the way the HEX codes are getting to my PDA with
Total Remote:

I copy-n-paste all the content of myhexcodes.txt in the input
box from IRPanels which generates a CCF file. Then i upload
the CCF to my PDA and use it.

After pushing button 8 (which is function 8) no action on the TV. To
check if my Total Remote Software is doing its job, i edited the CCF
with ProntoEdit4 and put the learned code on Button 1. After reuploading
the CCF to the PDA, the Button 1 powers on the TV correctly.

Hm... could there be a problem with Total Remote and NEC1 protocol?

I'll try 2 other PDA softwares that are reading CCFs and tell my results
(something like TV remote controller, have to google around a bit).

I the problem is not my PDA (Vodafone VPA Compact II), but i think if the
total remote software correctly learns and sends learned signals, it should
also correctly send my own generated signals :)

I installed lirc on my Debian GNU Linux OS. Maybe i am successfull sending IR codes with it. The configuration seems to be more complicated than CCF (the configuration
file looks like your decode IR tool):

heres a sample from an other remote:

#
# this is a space encoded remote control from Technisat
#
# contributed by Christoph Bartelmus ([email protected])
#
# brand: Technisat
# model: 100 TS 008
# supported devices: satellite receiver ST 3004 S
#

begin remote

name TECHNISAT_ST3004S
bits 6
flags SPACE_ENC|CONST_LENGTH
eps 20
aeps 120

header 0 0
one 170 7440
zero 170 4920
plead 0
ptrail 170
plead 0
foot 0 0
repeat 0 0
pre_data_bits 5
pre_data 0x11
post_data_bits 0
post_data 0x0
pre 0 0
post 0 0
gap 121400
repeat_bit 2

begin codes
POWER 0x0000000000000001
MUTE 0x0000000000000006
0 0x000000000000000F
1 0x0000000000000010
2 0x0000000000000011
3 0x0000000000000012
4 0x0000000000000013
5 0x0000000000000014
6 0x0000000000000015
7 0x0000000000000016
8 0x0000000000000017
9 0x0000000000000018
VOL_UP 0x000000000000002E
VOL_DOWN 0x000000000000002F
CH_UP 0x0000000000000007
CH_DOWN 0x0000000000000008
LIST 0x0000000000000037
A/B 0x0000000000000024
TV/R 0x0000000000000002
BACK 0x0000000000000027
MENU 0x000000000000002B
OK 0x0000000000000036
ARROW_UP 0x0000000000000032
ARROW_DOWN 0x0000000000000033
ARROW_RIGHT 0x0000000000000035
ARROW_LEFT 0x0000000000000034
end codes

end remote

do you have a idea how to modify for NEC1 device 4 function 8 ? :)

The basic structure of the LIRC file you want would be the same as this one for NEC1 device 4
[Link: lirc.sourceforge.net]

Function 8 in the backwards hex used by LIRC is
20DF10EF

The 20DF in each function is the backwards hex for the custom code for the device number 4.

The 10 above is backwards hex for 8.

The last two digits (EF) must always be chosen so those two plus the function add up to FF. 10 hex plus EF hex equals FF hex.

Do you have an IR receiver connected to LIRC, or just an IR transmitter?

If you have an IR receiver, you can use LIRC to learn the signals from your PDA to diagnose what is wrong with them.

The original learned signal you posted in this thread was learned by your PDA, correct?

If your LIRC IR transmitter doesn't work at first, you have a way to learn the signals it transmits and decode them with IrTool and see what might be wrong. That isn't as informative as the reverse (learning the PDA's signals with LIRC) but anything that gives you details is better then the pass/fail testing with the actual device.

All my IR receive and transmit hardware is on Windows and Dos computers and none of it is compatible with winLIRC. I recently installed Debian Linux on one computer, but I haven't had time to set up hardware to try LIRC.

It's a IBM Thinkpad T60. I'm at setuping right now. Seems
to be a bit tricky (need to compile several kernel modules).

I think it's not only a receiver... i'll test it in the evening.


thats correct, the only working hex code was learned by total remote
with my PDA.



winLIRC supports only serial IR transmitter as far as i know. I don't know how
the built in IR transmitter in the thinkpad t60 behaves, i'll give it a try and report :)

Maybe whoever wrote the software for the PDA didn't understand the Pronto Hex format well enough.

Most Pronto Hex has 0000 as the third value. That software may not work right with any Pronto Hex for which the third value isn't 0000.

Perfect NEC1 has 0022 0002 as the third and fourth values. If you change those to 0000 0024 it becomes the same signal in NEC12, which isn't really correct, but is understood by your LG and apparently can be sent by your PDA software.

If you change the Form line in NEC1 to

Form=;16,-8,D:8,S:8,F:8,~F:8,1,-78,16,-4,1,-174

That should produce NEC12 (same as manually changing all the 0022 0002 to 0000 0024).