The Beovision 3 STB-C can only be updated with a chip change. Why there are only two entries, I cannot really understand why except I noted that you say that it uses table 5.27a except there is no version 5.27a as far as I am aware. The latest table version for Central Europe is version 4.29 and the entries are shown below. So, I can only assume, that

Ralf, Your Beovision 3-28 has a STB-C and its table of 3rd party STB's is defined by a physical chip installed in the set top box controller. So, this is NOT upgradeable by using a flash software tool, you have to replace a physical chip. In recent years the PUC was introduced which IS software upgradeable. So, when you see B&O documentation

These commands are neither Pronto HEX codes or Lintronics Timing codes. If you have the Pronto codes, then just post those and I will convert them for you.

The programme I used to create the buttons can be found at http://www.crystalbutton.com/

My image is from the circuit diagram which shows the pin connections which is the same connections as shown in Räuber's image. The wiring to the Control is shown in the user manual

The XML Converter Tool found on Beoworld only converts Lintronics timing codes to RAW encoding in the XML file meaning that some functions may not function 100% as original. However, you can use other facilities such as "Bitstream" which will provide you with almost 100% perfect results. The main exceptions mostly relate to Philips protocol

The first point to make is that you must add at least one B&O product to your configuration mainly because it then sets up a place for "Accessories" which you will need to add all your non B&O 3rd party products. I normally add a TV and then hide the buttons when in EDIT If you are only going to control non B&O products, then each

You may find the following helpful

I have seen the same forum entry as you about the DCT 6200 using the same IR codes, however I cannot convert a ccf file. I can only convert Pronto HEX files which are in the form of 0000 006A 0000 0002 0000 00B0 0000 0016 0000 0016 0000 0017 0000 0042 0000 0042 0000 0016 0000 0016 0000 0017 0000 0042 0000 0016 0000 0016 0000 0042 0000 0016 0000 0042

To produce the XML file, I found a forum posting with Hex Pronto codes which I converted for you. Other than the three comands you have tested, the only other pronto codes were the digits 0-9. Unless you can find more Pronto codes on the web somewhere, the only way to progress this is to get the original remote and capture the codes.