Assuming your image is the only thing your device shows without decoding the protocol, then its not clear to me how it defines User and Data.

I suggest to you that it is decoding the most common IR protocol called NEC

You can look link to a Beo5 sub-domain of Beoworld which I put together in about 2005. As far as protocols are concerned it is just as valid as for Beo5

There are many tools available which will read the IR and display the waveform, but not many can or do decode the protocol used.

So, without a tool to detect the protocol automatically you are left to decode it manually assuming you know how.

If you look HERE you will see the RC5 decode which along with the NEC protocol is pre-built into the Beo5/6 which makes things much easier.

In the end it is possible to make an XML file configured to control 95% of all IR products. You will need the Beo5/6 configuration tool to download teh XML fiel to your device. If you google "beo5 xml file beoworld" you will see a large number of threads on the subject.

Thank you for chimming in so fast Keith,

Pffffeew, this dont look easy but I will study it all carefully.

As you may have noticed, it's a cheap Chinese device so there is not much documentation on it.

But I think I've read somthing about Hitachi protocol somewhere? Does this helps?

Tnaks to Beoworld and many of your posts I (believe I) know how to upload tha xml to the remote.

The problem is to capture the IR and to translate it into something the Beo6 can handle.
The solution based on pronto device having failed because of translation issues, I hoped for that one to work. 

Please tell me it can!

If you have the pronto codes for each of your buttons then translation is fairly easy.

Post a few of your captured pronto codes and I will convert them into a simple xml file for you to try

I checked to see what protocol Hitachi generally use and it is NEC protocol

Attached is a Generic XML file for Hitachi

Keith Saunders wrote:

If you have the pronto codes for each of your buttons then translation is fairly easy.
Post a few of your captured pronto codes and I will convert them into a simple xml file for you to try.

Good morning Keith and thank you for your support.

I don't have pronto codes: I drop the idea of buying a pronto capture device some time ago when I figured out I still would need a "translator".

The idea behind this whole search is to be independent and not having to bother you each time I add a device or change configuration!

Keith Saunders wrote:

I checked to see what protocol Hitachi generally use and it is NEC protocol

Attached is a Generic XML file for Hitachi

I've carefully looked the link and picture you provided but I can't see a pattern or find a link between the waveform in my capture device and the xml you provided. Neither what to do with Data and User. All dark science to me!

The Phillips protocol code page on the beo5 website show details on the waveform but the NEC protocol page don't.

I wished it would be as simple as drawing the waveform with 0 and 1 in some kind of xml file but it seems it's not that easy.

Anyway. If on your side you can do something with the codes and waveform shown in my device, I would accept your proposal of xml file.
There is one device I'd like to add to my Beo6, actually the only other remote lying around. That would be just a on/off command.
Its a Yamaha processor but as far as I've tried it's not a generic Yamaha command. 

Thanks again.

I cannot decode the waveform from the image you provided because it lacks the timing detail required even if you wanted to manual translate it.

Attached is the overview diagram of the NEC protocol I did some years ago when I pointed out to B&O an error in their firmware related to the repeat pulse timing was in the wrong position

Attached is an actual captured NEC IR signal

Keith Saunders wrote:

I cannot decode the waveform from the image you provided because it lacks the timing detail required even if you wanted to manual translate it.

I was suspecting something like that and it dont surprises me: I had in the ID that IR decoder was just a gadget and more likely useless.

Is I told you I can't see a pattern or even words like "user" or "data" in the research I've done.
So that's a tech that must be left for those who have knowledge.

So long for my quest of a totally independent end versatile Beo6 Universe! 🙂

Thanks for your help.

Basically, you need a cheap, yet workable IR capture device and there are quite a few options around.

If you have a link box then you can capture most IR codes which gives you the actual pulse, pause timing which makes thing quite easy.

There are various small cheap devices like this one