Hi Tim

You will be able to control the Tvix with no problems downloading the xml from

Quim43 wrote:

Hi Tim

You will be able to control the Tvix with no problems downloading the xml from link The xml is for the Tvix 6500A and 7000A. I think you won't have problems to control the macmini, as there are some xml for Apple products.

There is no xml for your Sony and your Philips TV, but can be created if you have the IR codes.

Does this mean the Beo5 can simulate all codes if they are programmed into it? So the Beo5 is the ultimate universal remote?

Sure,

I use my Beo5 to control all my B&O stuff, my Tvix 6500, my sat receiver Clarke Tech, my lights, blinds and my Roomba vacuum 🙂

Tim wrote:

What about my other products?

- Sony BDP-S350 connected to a Philips TV in my Bedroom

- MacMini

- TVIX HD M-7000A

All these products can be directly controlled by the Beo5

OK thanks guys I'll pick up my Beo5 on mondy from my local dealer.

I have one question left. Are there any restrictions programming the Beo5? Means can every Hardware with an Ir-Remote be controled by the Beo5 or is there Hardware known as non compatible. 

This is a question for Keith, but I think Beo5 can control ALL Ir devices.

Tim wrote:

Quim43 wrote:

So the Beo5 is the ultimate universal remote?

HA!
I think the words you were looking for Tim, was "link

Andy T.

Beo5 can not control any IR, im sure Keith will explain wich protocols can be controlled. I my self had to bumb in a couple of things wich were not posible.

99% of 3rd party products CAN be controlled by the Beo5

The limiting factor is not protocol, but carrier frequency. The transmitting diodes have a range of frequencies in which they will work which is why the Beo5 has more than one transmitting IR diode.

99% of 3rd party infrared protocols use a frequency between 30 Khz and 60 Khz which the Beo5 can handle without a problem. The most common frequencies are:-

• 38Khz for NEC protocol
• 36KHZ for Philips RC5 protocol
• 40KHZ for Sony protocol

The Beo5 supports NEC, Philips RC5, bitstream and RAW protocols, well RAW is not actually a protocol, its what is says RAW timing data

NEC, RC5 and Bitstream are translated by the firmware in the Beo5, whereas the RAW data is transmitted as provided to the Beo5

This means that if the Beo5 only supported RAW, it could still be used for any 3rd party product, subject to the carrier frequency requirements.

In fact the "3rd party XML Generator" available for download only converts to RAW.

So, in conclusion, I totally standby my statement that 99% of 3rd party products can be controlled by the Beo5.

However setting up some of the XML files to control these products correctly can be a minefield if you don't completely understand the structure and how they work.