Hello!

My aim is to get pronto codes that look like this:
0000 0067 000D 000D 0060 0019 0018 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 03FB 0060 0018 0018 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0018 0018 0030 0018 0030 0018 0018 0018 0030 0018 0018 03E5

The problem is I have an old TV set that I can't find any info on anywhere on the net (Make: VOXSON). So I thought I would just use my PC to learn the remote. (don't have a PDA).

I installed some custom driers for my windows MCE infrared receiver and used a program called MceIrRec to learn the power button on my remote. However, what I get (converted to hex) looks like this:

86 7F 12 86 5F 86 7F 12 86 7F 13 86 7F 12 86 7F 12 86 5F 86 5F 86 5F 86 5F 85 60 85 7F 7F 7F 7F 7F 7F 7F 7F 2B 85 7F 13 86 5F 85 7F 13 86 7F 12 86 7F 13 85 7F 13 86 5F 86 5F 85 60 85 5F 86 5F 86 7F 7F 7F 7F 7F 7F 7F 7F 2A 86 7F 13 85 5F 86 7F 13 85 7F 13 86 7F 12 86 7F 13 86 5F 85 5F 86 5F 86 5F 86 5F 86 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 5F

My question is simple. How do I convert this into a pronto format - if at all possible.

Many thanks,

SeBsZ

Hard to say unless something is known about how MceIrRec formats/represents the information.

Most of us use a learning device that will format in Pronto Hex. Most of the available tools for analyzing codes are based on Pronto hex format.

What kind of a learning device? I want to do this preferably without having to buy any new hardware. I have an infrared receiver and I have a computer. Is there no software out there that will allow me to use my remote control and return pronto hex?

I understand that format (though I don't recall seeing it before).

I know how to translate it to approximate pronto hex. I don't know the basic clock rate and I assume the frequency wasn't captured at all, so such a translation wouldn't be correct enough to directly use.

By hand it would be a tedious translation, and I don't have time right now to write a simple C++ program to do it. If you want to try, see below.

Once translated to approximate pronto hex, you could use the JP1 version of IrTool with decodeir.dll to decode it. That probably will work and not care that the time scale and frequency are wrong.

If you get a correct decode, you can then use MakeHex to generate correct Pronto Hex.

The first four values in pronto hex are a header. For those use
0000 006D 0000 00nn
where you replace nn with the hex value of half the count of the values in the remainder of the pronto hex string (described below):

In your strange hex string notice whether each value is above 80 hex or below. Group together any that don't alternate above/below. At a glance I only see groups of below.

Subtract 80 from all the above 80 values, add together all members of each group (in hex), then add the required leading zeroes to make a four digit value.

For example the first few are translated
86 7F 12 86 5F 86 7F 12 86 7F 13 86 7F 12
to
6 7F+12 6 5F 6 7F+12 6 7F+13 6 7F+12
to
0006 0091 0006 005f 0006 0091 0006 0092 0006 0091

Many thanks. So I went ahead and converted the whole thing manually. Here are the intermediary steps I took: (I didn't do the whole thing in one go, I did it in chunks)

86 7F 12 86 5F 86 7F 12 86 7F 13 86 7F 12
6 7F+12 6 5F 6 7F+12 6 7F+13 6 7F+12
0006 0091 0006 005f 0006 0091 0006 0092 0006 0091

86 7F 12 86 5F 86 5F 86 5F 86 5F 85 60 85
6 7F +12 6 5F 6 5F 6 5F 6 5F 5 60 5
0006 0091 0006 005F 0006 005F 0006 005F 0006 005F 0005 0060 0005

7F 7F 7F 7F 7F 7F 7F 7F 2B 85 7F 13
7F+7F+7F+7F+7F+7F+7F+7F+2B 5 7F+13
03F8 0005 0092

86 5F 85 7F 13 86 7F 12 86 7F 13
6 5F 5 7F+13 6 7F+12 6 7F+13
0006 005F 0005 0092 0006 0091 0006 0092

85 7F 13 86 5F 86 5F 85 60 85 5F 86 5F 86
5 7F+13 6 5F 6 5F 5 60 5 5F 6 5F 6
0005 0092 0006 005F 0006 005F 0005 0060 0005 005F 0006 005F 0006

7F 7F 7F 7F 7F 7F 7F 7F 2A 86 7F 13 85 5F 86 7F 13 85
7F+7F+7F+7F+7F+7F+7F+7F+2A 6 7F+13 5 5F 6 7F+13 5
0422 0006 0092 0005 005F 0006 0092 0005

7F 13 86 7F 12 86 7F 13 86 5F 85 5F 86 5F 86
7F+13 6 7F+12 6 7F+13 6 5F 5 5F 6 5F 6
0092 0006 0091 0006 0092 0006 005F 0005 005F 0006 005F 0006

5F 86 5F 86 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F 5F
5F 6 5F 6 7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+7F+5F
005F 0006 005F 0006 07D0

In the end, here is my result:

0000 006D 0000 0024 0006 0091 0006 005f 0006 0091 0006 0092 0006 0091 0006 0091 0006 005F 0006 005F 0006 005F 0006 005F 0005 0060 0005 03F8 0005 0092 0006 005F 0005 0092 0006 0091 0006 0092 0005 0092 0006 005F 0006 005F 0005 0060 0005 005F 0006 005F 0006 0422 0006 0092 0005 005F 0006 0092 0005 0092 0006 0091 0006 0092 0006 005F 0005 005F 0006 005F 0006 005F 0006 005F 0006 07D0

I added the four words at the beginning and changed nn to 24 (which is correct since there are 0x48 words)

Unfortunately, this does not work when I try it on my TV :<. My TV in fact does nothing. Did I make a mistake?

Hopefully you can help me out. If this works then I will write the program myself.

I know you told me to use Irtool and Makehex, but these apps have not been that useful. When I use IrTOol to decode my HEX, it comes up with "Kenwood/Yamaha" device and some other info. Then when I click encode Hex, it gives me:

0000 006d 0000 0002 0006 0091 0006 005f

The program I use, however, needs RAW pronto. To clarify, the program I'm using (the reason why I need the pronto code), needs long pronto code (whatever its name). It accepts:

0000 006D 0000 0024 0006 0091 0006 005f 0006 0091 0006 0092 0006 0091 0006 0091 0006 005F 0006 005F 0006 005F 0006 005F 0005 0060 0005 03F8 0005 0092 0006 005F 0005 0092 0006 0091 0006 0092 0005 0092 0006 005F 0006 005F 0005 0060 0005 005F 0006 005F 0006 0422 0006 0092 0005 005F 0006 0092 0005 0092 0006 0091 0006 0092 0006 005F 0005 005F 0006 005F 0006 005F 0006 005F 0006 07D0

and doesn't accept:
0000 006d 0000 0002 0006 0091 0006 005f

Secondly, I have no idea what to do with makehex. Hopefully you can point me in the right direction.

I said to use the JP1 version of Irtool with decodeIr.dll

Tomorrow I'll be back at a computer where I have those programs, and I'll check whether they give useful results with the pronto hex string you posted.

DecodeIR DLL gives:

Protocol: RECS80
Device: 7
OBC: 32
EFC: 177

and that repeated 3 times

Those decodes are correct. However, we don't know the frequency or the timescale. Most IR protocols are used in only one frequency and timescale (per protocol), so once you have a decode you would know the correct frequency and timescale.

But RECS80 is used with several different frequencies and timescales. So we don't know which is correct.

MakeHex.zip contains two different .irp files for recs80. You could try each of those and see if one generates correct signals for your device. But there is a significant chance your TV uses some other frequency and timing, requiring changes to the .irp file.


Unfortunately, most such programs only understand pronto hex for modulated signals. Most RECS80 is unmodulated. Maybe you'll be lucky and either your program understands unmodulated or your TV uses modulated. If not, I may be able to kludge a .irp file for recs80 that looks to your program like it is modulated but generates a signal that looks unmodulated.

Meanwhile, which command was that, which you decoded? I have a big library of downloaded IR signals on which I can do fast automated scans. If there is another brand TV on which the same device number (7) and same function number (32) in RECS80 has the same function meaning (which I don't see in your posts) then likely that other TV uses the same frequency and timing of RECS80 as well.

Edit: I did that search anyway. Regardless of function name, I only found two instances of RECS80 device 7, function 32 in all my downloaded signals.

[Link: remotecentral.com]
is a Saba TV model T6360SH
That function is labeled with a down arrow (so it might be the down arrow function or it might be something like ch- or vol-).
The frequency and timing are close to recs80_68.irp, but maybe not close enough to use unmodified.

[Link: remotecentral.com]
is a Thomson TV model 32VT65J
That funchion is on the Ch- hard button, so I assume it is Ch-
The frequency and timing are closer to recs80_68.irp (than that other file is), but still maybe not close enough to use the .irp file unmodified.

Both of those are modulated RECS80, which is probably good news for any program with only a partial understanding of Pronto Hex.

Hi, I really appreciate your time and effort.

First of all I wanted to say that the function key I used on my remote to generate my decode is actually the power button. Strange that the matches you found are for totally different buttons. I guess this TV really is a unique one :P (and crappy one)

Anyway, something I else I wanted to tell you, is that even if I capture my remote's power button 4 times in a row, none of the four takes will be identical. That is the hex codes I get are all different from each other. Not by much, but they are off quite a bit. Is this bad?

Finally, if this takes so much time then it might not be worth the effort for me. I thought I could just take all my remotes (5-6 of them) and just learn them all using a nice program on my PC and get pronto codes for each of them. I need the pronto codes because I have a program that takes a pronto code and generates a wave audio file. I have built a very simple audio to infrared converter (with two IR leds and a resistor). Then when I play the audio file, the infrared LEDs will blink and the TV/device should react. If I could completely bypass pronto that would be much better (for example if I could find a way to use the raw hex and generate a wave file from that, but that would require modifying the program, which I did not wrote but have the source code for)

Any ideas on this? Basically I think that if it takes so much time to identify a single remote and then create pronto codes from them I don't think its worth it.

So hopefully you can help me out a last time and perhaps you know of a program that converts raw IR hex (The stuff I have in my first post that you helped me decode) to wave (audio files).

Thanks!

SeBsZ

P.S. - I really appreciate your help!

I don't think it would be very hard to write a program to do the translation you just did manually. It wouldn't be much harder to make that program pass the result to DecodeIr.dll and display the result.

Your IR capture system doesn't capture the modulation frequency, so decoding and reencoding the signals would be necessary to get the modulation frequency (in typical protocols where you can get it that way).

Your IR capture system would capture the timescale if we knew one timing constant inside that capture system, that I don't know. But reencode may be better for that as well.

So I don't think a direct conversion from the form you posted to wave would be practical. I certainly don't know of any program that does such a conversion. I don't recall even seeing the format you posted before this thread (though I probably did. I've looked at a lot of strange formats for IR signals in a lot of threads).

I see. Then why are there programs for PDAs that allow PDAs to learn remotes. Why aren't there such programs for say laptops with IR ports?

can you send me a email with the ir sound converter or maybe just te parts that you used greetz ruben