The Masterlink Gateway does exactly what it says on the box, it converts Beolink sources and commands to a device connected to either the RS232 port or over the Ethernet connection and takes commands from the RS232 or Ethernet port and via macros setup in the Gateway triggers Beolink commands.

This product is not made by B&O.

The Gateway implements a "Masterlink Gateway Protocol" by default, but you can use your own protocol if you wish, but in my view that would normally only be used for testing.

The Masterlink Gateway protocol implemented in the latest firmware version 1.50 which is backward compatible with a previous version of Masterlink Gateway which was only really sold in the US provides five (5) types of messaging:-

Commands from the Device to the Beolink Products
Commands from the Device to the Masterlink Gateway macro programme
Status information from the products to the Device
Light and Control commands received by the products are forwarded to the Device
Authentication messages and configuration notifications for mobile applications
The Masterlink Gateway implements the source and command codes using exactly the same HEX codes as the Beo4/Beo5 and on the Beolink into what B&O calls a "Telegram" A telegram is normally made up of a start command followed by three (3) 8 bit bytes followed by a variable length data block.

Command data can be sent or received as follows:-

Via the Ethernet
Via the Ethernet using RS232 to Ethernet interfaces where distance is an issue
Direct RS232 connection
The setting up of the gateway is fairly straight forward if rather primative.

The first thing you have to do when the box is connected to the Beolink it will be used on is go through a procedure to allow the Gateway to identified each B&O product on the Beolink and assign a number to it between 1 and 16. Note, some B&O products may need a software update first before the gateway will work correctly.

You then need to setup your device(s) well just one external 3rd party device plus virtual buttons which are really only needed for testing but are considered a device. When setting up a device you use a product from the pull down list or Custom Settings. You would normally use custom settings to communicate with a product which either do not have a built 3rd party driver or does not need one depending on the device in question.

The last thing you need to do is setup your macros which will define what device command data triggers what Beolink source or command and/or what Beolink command sends what third party command to a particular device.

Below are a couple of screen shots to give you a flavour on how the units are setup