Hi,

i have a Samsung top set box where i would like to research what discrete codes are available.

for this reason i would like to look at the learned codes that i got so far to see if i can determine a pattern in the learned signals.

i have an MX-850 and use the MX editor.

The MX editor can only analyze Pronto hex signals, but is there another way to get the learned data shown in some kind of format?

One thing i wondered was if there is some way to export from MX-editor into CCF or other format, or if maybe other editors (neo, pronto etc) can import MXF format?

If someone know a way of doing this plz answer here. I can supply an MXF file with the learned codes.

thx
Anders

I can easily decode signals from my MX-850 using my CaptureIR hardware and software.

I can also manually decode most signals from an .mxd file without hardware. But that is harder and I don't have a program to do it and I couldn't usefully describe the manual process.

If you email a file to me that I can easily load to my MX-850, I'll try to find time to use CaptureIR on those signals and post the results back here.

Hi John,

thanx a bunch! You got mail ;-)

Anders

I got the email. My MX-850 is at another location. I think I'll be there later today.

I tested it.

I assume the P-ON and P-OFF on page 2 of that configuration don't work. They are from a totally different code set than the resto of the signals.

The rest of the signals are from a protocol which in DecodeIR and MakeHex is called "Samsung36". (That name is from reverse engineering it. I have no idea what Samsung calls that protocol).

I checked MakeHex.zip and Samsung36.irp was not included. So here is the contents of that .irp file in case someone needs it before I re release MakeHex.zip

Device=32.0
define E=1
Function=0..255
Frequency=38000
One=498,-1498
Zero=498,-498
Form=;4488,-4492,d:8,s:8,498,-4498,e:4,f:8,-68,~f:8,498,-59154

Your signals all decoded the same as whatever I was looking at when I made that .irp file (the lines Device=32.0 and define E=1 should vary by device, but are the same between your device and whatever I was looking at then). I'll search shortly to see if I can find the thread on that topic. I don't recall anything, but there must have been one.

Your signals all decode as function numbers from 34 through 56. With a Pronto, it would be easy to just pull in all 256 possible functions and test them. With an MX, dragging all 256 functions via Universal Browser and then testing them, could get very tedious. Maybe you want to do that, or maybe you want to stay closer to the range of the learned signals.

I didn't find a thread at RC, nor a CCF file. I did find a JP1 file for a "Samsung DTB-H260F ATSC tuner" that matches your signals. The JP1 file is here:
[Link: hifi-remote.com]

The table of function_number -> function_name within that file is the only thing that would be of interest to a non JP1 user, so I extracted that here:

0 -> 1
1 -> 2
2 -> 3
3 -> 4
4 -> 5
5 -> 6
6 -> 7
7 -> 8
8 -> 9
9 -> 0
10 -> vol up
11 -> vol down
12 -> channel up
13 -> channel down
15 -> GUIDE
16 -> up arrow
17 -> down arrow
18 -> left arrow
19 -> right arrow
20 -> enter
21 -> EXIT
27 -> FAV CH
30 -> power
32 -> mute
33 -> INFO
34 -> GREEN BUTTON
35 -> ORANGE BUTTON
36 -> BLUE BUTTON
37 -> MENU
38 -> RED BUTTON
48 -> PRE CH
49 -> MTS
50 -> FREEZE
52 -> CAPTION
54 -> CH LIST
55 -> TIMER
57 -> ANTENNA
58 -> ASPECT
59 -> - (dash)

Here is a JP1 thread about converting this code set for use in an MX-700. Maybe you'll find something helpful there.
[Link: hifi-remote.com]

I don't see any indication in any of the connected files or threads than anyone tested for signals that were not on the original remote (any function numbers 0 through 255 that are not in the above list but which do something useful to the device).

Looking closer now, I see your file already includes differences from that list. Your file has:

30 On/Off
53 Audio
27 FavCH
49 Alt
50 Freez
52 Subtl
51 Text
36 Blue
35 Yellw
34 Green
38 Red
55 Timer
43 TV-RA
54 C.Lst
56 P.Siz
44 RETRN

Hi John,

first, i really appreciate you using your time helping me out here so thanx alot!

i tried all codes from 0-255 without much luck (first testing 30 worked as power toggle).

the only thing that happend was that 129 apparently works as toggle also. If you look at the bit pattern on 30 vs 129 they are very similar with only a few bits differing (see below).


ARGH i cant belive Samsung would create a TOAD for a brand new HDTV decoder -its just so stupid! :'-(

A thought: in another thread i remember you helping another user finding the discrete codes having only the toggle hex code to go by. This i gather would be because a certain best practice exists among IR developers to use certain bit variations as discrete on/off given a certain toggle hex code? Or have you just found out with personal experience that certain brands always use certain bit patterns for on/off given a certain toggle code?

I guess its clutching at straws, but i just want to make sure i have tried everything before officially labeling this brand new +$500 device as a TOAD :-((

30: toggle power
0000 006d 0000 0027 00ab 00aa 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 00ab 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0039 0013 0039 0013 0039 0013 0013 0013 0013 0013 0015 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0039 0013 0039 0013 08c9 0101 0100 0000 0000 0019 f600 aa00 0004 a200 0000 6d00 0000 2700 ab00 aa00 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 ab00 1300 3900 1300 1300 1300 1300 1300 1300 1300 3900 1300 3900 1300 3900 1300 3900 1300 3900 1300 1300 1300 1300 1300 1500 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 3900 1300 3900 1308 c901 0101 0000 0000 0000 1aab 00aa 0000 04a2 0000 006d 0000 0027 00ab 00aa 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 00ab 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0015 0013 0039 0013 0039 0013 0039 0013 0039 0013 0039 0013 0013 0013 0039 0013 0039 0013 08c9 0101 0100 0000 0000 001b 6000 aa00 0004 a200 0000 6d00 0000 2700 ab00 aa00 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 ab00 1300 3900 1300 1300

129:
0000 006d 0000 0027 00ab 00aa 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 00ab 0013 0039 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 003b 0013 0013 0013 0039 0013 0039 0013 0039 0013 0039 0013 0039 0013 0039 0013 0013 0013 08c9 0101 0100 0000 0000 005f f500 aa00 0004 a200 0000 6d00 0000 2700 ab00 aa00 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 ab00 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3b00 1300 3900 1300 1300 1300 3900 1300 3900 1300 3900 1300 3900 1300 3900 1300 1300 1308 c901 0101 0000 0000 0000 60aa 00aa 0000 04a2 0000 006d 0000 0027 00ab 00aa 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 00ab 0013 0039 0013 0013 0013 0013 0013 0013 0013 0039 0013 0039 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 0013 003b 0013 0013 0013 0013 0013 0039 0013 0039 0013 0039 0013 0039 0013 0039 0013 0013 0013 08c9 0101 0100 0000 0000 0061 5f00 aa00 0004 a200 0000 6d00 0000 2700 ab00 aa00 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 3900 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 1300 ab00 1300 3900 1300 1300

I don't know which thread you mean. But in such situations, I decode the signal. That would give me the set of 256 signal to try, just as I already gave you in this case. I also would do a scan of my large library of downloaded IR files (CCF, JP1, etc.) for matching signals (as I did to find that JP1 file I mentioned) and then I check those files to see if the people who posted those files included discretes. In this case they didn't. Usually there is no more I can do than that.


Nope.


A few brands have consistent rules for discrete codes. Most don't. Samsung certainly doesn't.


I don't know a good way to experiment. But there is another approach, with a decent chance of creating discrete On and/or Off for a device with none designed in. Since there is no systematic approach to finding it, most people don't waste the time, but I'll mention it.

The device ignores most commands when off, and it probably ignores all commands during a short moment while executing certain commands. The first "ignore" above may be fast enough to allow a work around for discrete On:

Issue some command instantly followed by a minimum length power toggle command. If the device is off, it will ignore the first, maybe fast enough to execute the second. If on, it would obey the first and fail to see the second.

For other devices (probably not a set to box) there is a very low power mode used for "off" which is not as good at understanding IR as full power mode. For those devices, one might find an imperfect power toggle signal that can only be understood when the device was on.

Usually the macro capability of the remote isn't fast enough to control timing that well, so instead, one combines the commands on the form line of the .irp file to put a mini macro into one Pronto Hex string.

Hi John,

i tried your suggestion and recorded a macro: with no delays inbetween, but no dice! Its not clear to me btw what you mean with a "minimum length power toggle".

any comments on what the difference between the 20 and the 129 power toggle?
It would seem that there is only a small difference on the significant bit (like 5f00 instead of 6000 and 005f f500 instead of 0019 f600 )

thx
Anders

The difference between 20 and 129 is a lot more than that. I don't know why 129 acts the same as 20.