![background image](http://html.mh-extra.com/html/weinzierl/5193/5193_operation-and-installation-manual_953243001.webp)
©
2015 WEINZIERL ENGINEERING GmbH
2015-07-31
Page 1/2
Operation and installation manual
KNX IP BAOS 777
(Art. # 5193)
Interface and ObjectServer between LAN and KNX Bus
Picture 1: Photo of the device Picture 2: Typical application
Application
The KNX IP BAOS 777 from WEINZIERL is a universal IP Inter-
face and IP Gateway for the KNX Installation Bus. BAOS stands
for "Bus Access and Object Server" and provides an interface to
KNX installations both on the telegram level (KNXnet/IP Tunnel-
ing) as well as on datapoint level (KNX Group Objects / KNX
Application Layer) with semantic meta-data for rooms and func-
tions. With its integrated web server, the device allows the visu-
alization of buildings, rooms and functions in a standard web
browser on a PC or mobile device.
The device provides these possibilities to access an installation:
As
Programming Interface
On telegram level (KNXnet/IP Tunneling)
Can be used as bus interface for ETS® (Version 4.2 or
higher)
As
Residential Gateway
Via KNX IP BAOS Binary Protocol
Via KNX IP BAOS Web Services
Via KNX IP BAOS RESTful Web Services
Via
Web Application
Using a standard web browser
KNX IP BAOS 777 as Programming Interface
The KNX IP BAOS 777 can be used as interface to the KNX Bus
on the telegram level. It is compatible with the KNXnet/IP specifi-
cation and can be used as bus interface for ETS® or other pro-
grams that support the KNXnet/IP Tunnelling. It supports up to 8
simultaneous connections. The settings for the interface (e.g. IP
configuration) can be done with all the ETS product entries that
are available for this device.
KNX IP BAOS 777 as Residential Gateway
The KNX system is based on a specific protocol that is difficult to
implement for non-KNX devices. The KNX IP BAOS 777 maps
KNX data to an IT-friendly API (Application Programming Inter-
face). It greatly reduces the effort to connect e.g. control or
visualization tools to KNX. Also helpful is the storage of all data
point values – even if the device is not connected.
The KNX BAOS architecture not only allows access to the run-
time data, but also to the structure of the KNX installation. All
information about rooms in a building and the available functions
can be read as metadata from a client. With the ETS, the rooms
and the functions are defined, which should be available to the
user.
The KNX IP BAOS protocol is available in three different ver-
sions:
KNX IP BAOS Binary: A binary protocol that is espe-
cially suitable for small microcontroller.
KNX IP BAOS Web Services: A URL-based protocol
with JSON syntax compatible with KNX IP BAOS 771
and 772.
KNX IP BAOS RESTful Web Services: A URL-based
protocol with RESTful JSON syntax, which can be in-
tegrated into browser-based web applications.
The KNX IP BAOS 777 also features time and recording func-
tions available on the BAOS protocol.
KNX IP BAOS 777 via Web Browser
The KNX IP BAOS 777 has an integrated web server that allows
access to the device settings in a standard web browser.
With the help of the ETS product entry with building structure the
web server also offers visual representations of the entire KNX
installation including visualization of the building, rooms and
functions.
The data from the Residential Gateway are graphically displayed
in the browser and the functions can be operated directly via the
web interface. Timers are also available via the web server.
KNX IP BAOS 777 as application specific Gate-
way
To connect to non-KNX systems, the KNX IP BAOS 777 can be
used as an application specific Gateway (e.g. to connect heating
devices, audio applications and many more). In this case the
generic ETS product entry (with up to 2000 data points) can be
used for development purposes. Of course, individual product
entries can be developed. The datapoint types can be individual-
ly configured via ETS parameters.
BAOS SDK
Both for the use of the KNX IP BAOS 777 as a Residential
Gateway as well as for the development of application-specific
solutions the BAOS protocol must be implemented in the client.
For a quick and easy integration of BAOS Binary Services a free
SDK is available. More information about the BAOS SDK and the
free download can be found at
www.weinzierl.de
EN