Hi all!
I was very happy to find a lot of discrete codes for Samsung, especially for the inputs (since running through them with source select was a pain). Although I didn't find any mention for the recent LE-series, most of the codes for the older plasma models do also work with my LE32R41. Except for one: I can't find a code that works for selecting Ext.2.
Before trying out the 256 combinations that make most sense, I'd like to ask if anyone does know the code for Ext.2, or has any good suggestions.

I also experimented with MakeHex and DecodeIR but somehow I am not able to make MakeHex generate the codes that I already have: they consist of 15 interspersed with 40 and 15 (which are the bits, I guess). MakeHex however seems to generate 41 and 16 (that's when I use NECx2 and device 7.7 - which is also what DecodeIR suggests) .
With comparing the existing codes that I already have, I was able to find the mapping between a hex code and the eventual IR code myself. So my plan now is to just write a small Perl program that generates these IR codes.

Thanks for any suggestions.

The 40 and 15 are approximate durations measured during learning or generated by some program. The exact values don't matter at all.

41 will act just the same as 40. 16 will act just the same as 15.

IR transmit/receive is a very imprecise process. The signal received is a crude approximation of the signal sent. The encoding of information is designed to be immune to major distortions. In this case "15" just means "short" and "40" just means "long". 16 (or 17 or 18) is still short. 41 (etc.) is still long.

People tend not to believe this and want MakeHex to exactly match some target set of timings. If you want that, just adjust the "Time Base=564" in the .irp file slightly lower. The "long" is nominally three times the "short", so if you set the exact value for "15" you would get "15" and "3F". But if you select a tiny amount more than what would be exact for "15" the long should round up to "40" while the short rounds down to "15", just as the current 564 is a little low for an exact 16 so the long rounds down to "41".

Note the number on the end (0689 with my copy of MakeHex and NECx2.irp) is an even more crude approximation. Big changes in that value will have no effect on the actual device. It is affected by both the "TimeBase" number and the "Suffix" number in NECx2.irp. If you tweak those you could come quite close to whatever you think that last number should be, but I doubt you'd hit it exactly. Anyway, there is no reason to try to get more than crudely close to the desired value.

Thanks a lot. I wasn't aware of the fact that these numbers referred to timings. You also answered another question I had referring to the last value which in my case was sometimes 680 and sometimes 689 an a single time even 7xx.
BTW, these were not 'learned' values but values that I found here on the Discrete Codes section.
Anyway, with your info, I now know that the output of MakeHex should in fact work...
Will try it out tonight for sure...

Great! It all works now.
I generated the NECx2 codes and then used the IRPanels app to test the 256 codes. Apart from the Ext.2 that I was missing, I found a few other surprises :
* AV input (didn't know it existed)
* discrete Picture Modes
* discrete Picture Sizes (except for Auto-Wide, which is weird)
Also weird is that there are no discrete Sound Modes (not that I regret it since I use a separate amp anyway).
I've submitted the mappings file.

Who is running the files section of this site ? I still don't see my submission published anywhere here, even though I guess it's pretty interesting for Samsung owners.

Well, I for one would be very grateful to get hold of the Samsung codes. Could you email them to me, as they're not available in the files section yet?

glennza"at"jpopmail.com

Many thanks :)

Files take a while to appear in the files section.

If I understand correctly, Remby found three or four commands that aren't in the common lists of Samsung commands.

If you just post the function numbers of those four commands in this thread, that would make your discovery available to anyone else using MakeHex, and to users of other systems that don't use Pronto Hex (JP1 and LIRC and maybe others).

Thanks to the hints in this thread (I'm pretty new to all this stuff) I've been able to find the code I really needed for a Samsung LE26, which is direct access to the AV input.
It is NECx2, device 7.7 code 236.
Full code:
0000 006D 0000 0022 00AC 00AB 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 0015 0016 0015 0016 0015 0016 0015 0041 0015 0041 0015 0041 0015 0016 0015 0016 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 0041 0015 0016 0015 0016 0015 0016 0015 0689

I've spent ages today working this out, so I thought I'd post it in case it is useful to anyone else.
Ben