The KNX Serial Interface BAOS 870 serves as a simple integration solution for non-KNX devices. Designed as a RS-232 interface, the KNX Serial BAOS 870 uses the proven FT1.2 protocol (PEI 10) as message format and can thus be used as a programming interface for the ETS. Moreover, the device supports the BAOS protocol for accessing data points. This allows non-KNX devices to be fully integrated into a KNX network via a RS-232 link. For a quick start, a demonstration tool as well as an ETS entry with 250 group objects are available. Furthermore, individual ETS representations for OEM versions can be created.

The KNX IP Interface 731 is the successor of the well-tried KNX IP Interface 730. The new compact design has a width of only 1 module (18 mm) and is powered by the KNX bus.

· Interface between LAN and KNX bus

· KNXnet/IP Tunneling, 5 connections

· Bus powered

· Housing: Plastic

· Size: DIN rail mounted device, 1 unit, 18 mm

· Connectors: KNX, LAN RJ-45

- Power from KNX Bus

The unit KNX ENO 634 serves as a bidirectional gateway between EnOcean radio devices and the KNX/EIB bus. With this device, commands and measured values of EnOcean wireless sensors can be transferred to the KNX bus, for example, to control KNX actuators. Also EnOcean wireless actuators can be controlled via KNX.

For EnOcean sensors the device is based on the so-called EnOcean Equipment Profiles (EEP). The implemented profiles mostly are specified in the data sheets of the sensors. For the control of EnOcean actuators corresponding EEPs are emulated.

This means, the gateway sends radio telegrams such as a push button or a window contact. In addition the gateway supports logical and control functions and has a radio repeater included. The KNX ENO 634 is organized in 32 channels. Each channel can be assigned to one of the following functions:

Link to sensors:

• Switching and contact functions
  - Switching
  - Dimming
  - Shutter up/down
  - Scene
  - Window contacts
  - Window handles
  - access cards switches
  - push button switches
  
• Temperature sensors
• Humidity sensors
• Light sensors
• Presence sensors
• Gas sensors
• Room control devices
• Automated counter devices
• Environmental sensors (weather station)
• Digital inputs

Link to actuators:

• Relay
• Dimmer
• Shutter
• HVAC actuators (valves)

Control / logic:

• Timer
  - Delay
  - Tracking circuit

• Control
  - Two point controller (byte and float)
  - Continuous regulator
  - Heat demand requirements
  - Lighting control

• Logical functions
  - Gates (e.g. AND, OR, XOR)
  - Toggle

• Other
  - Trigger
  - Encoder
  - Watchdog
  

The configuration of the device and the channels is done using the ETS software via the KNX bus. For the teach-in of the wireless components the keys and the display in the device are used.

Mounting and connection

The mounting can be done on a wall surface (e.g. brick-work or wood). The mounting holes match for a 55 mm flush-mounted box. The power supply of the device is realized via the bus.

Repeater function

The repeater function is used for extend distances between sensors and actuators. The KNX ENO 634 is a so-called level-1 radio repeater.

Bus monitor function

The integrated bus monitor function is used for sys-tem diagnostics directly on the device. The device can display both EnOcean telegram as well as KNX telegrams.

The unit KNX ENO 630 serves as a unidirectional gateway between EnOcean radio devices and the KNX/EIB bus. With this device, commands and measured values of EnOcean wireless sensors can be transferred to the KNX bus, for example, to control KNX actuators.

For EnOcean sensors the device is based on the so-called EnOcean Equipment Profiles (EEP). The implemented profiles mostly are specified in the data sheets of the sensors. For the control of EnOcean actuators corresponding EEPs are emulated.

This means, the gateway sends radio telegrams such as a push button or a window contact. In addition the gateway supports logical and control functions and has a radio repeater included. The KNX ENO 630 is organized in 16 channels. Each channel can be assigned to one of the following functions:

Link from EnOcean sensor to KNX:
Switching and contact functions
Switching
Dimming
Shutter up/down
Scene
Window contacts
Window handles
Key cards switches
Ressure switches
Temperature sensors
Humidity sensors
Light sensors
Presence sensors
Gas sensors
Room control devices
Automated counter devices
Environmental sensors (weather station)
Digital inputs
Control / logic:

Timer
Delay
Tracking circuit
Control
Lighting control
Logical functions
Gates (e.g. AND, OR, XOR)
Toggle
Other
Trigger
Encoder
Watchdog
The configuration of the device and the channels is done using the ETS software via the KNX bus. For the teach-in of the wireless components the keys and the display in the device are used.

The unit KNX ENO 632 serves as a bidirectional gateway between EnOcean radio devices and the KNX bus. With this device, commands and measured values of EnOcean wireless sensors can be transferred to the KNX bus, for example, to control KNX actuators. Also EnOcean wireless actuators can be controlled via KNX. For EnOcean sensors the device is based on the EnOcean Equipment Profiles (EEP). The implemented profiles mostly are specified in the data sheets of the sensors. For the control of EnOcean actuators corresponding EEPs are emulated.

This means, the gateway sends radio telegrams such as a push button or a window contact. In addition the gateway supports logical and control functions and has a radio repeater included. The KNX ENO 632 is organized in 24 channels. Each channel can be assigned to one of the following functions:

Link from EnOcean sensor to KNX:

Switching and contact functions
Switching
Dimming
Shutter up/down
Scene
Window contacts
Window handles
Key cards switches
Pressure switches
Temperature sensors
Humidity sensors
Light sensors
Presence sensors
Gas sensors
Room control devices
Automated counter devices
Environmental sensors (weather station)
Digital inputs
Link from KNX to EnOcean actuator:

Switching
Dimming
Shutter
Control / logic:

Timer
Delay
Tracking circuit
Control
Lighting control
Logical functions
Gates (e.g. AND, OR, XOR)
Toggle
Other

Trigger
Encoder
Watchdog
The configuration of the device and the channels is done using the ETS software via the KNX bus. For the teach-in of the wireless components the keys and the display in the device are used.

Mounting and connection
The mounting can be done on a wall surface (e.g. brick-work or wood). The mounting holes match for a 55 mm flush-mounted box. The power supply of the device is realized via the bus.

The KNX IP Interface 751 is the successor of the well-tried KNX IP Router 750. The new compact design has a width of only 1 module (18 mm) and is powered by the KNX bus.
The device forwards telegrams between different KNX TP lines via LAN (IP) as a fast backbone and is an alternative to KNX line coupler. The KNX IP Router 751 can also be used in the ETS® as a programming interface. The KNX IP Router 751 has a full-range filter table and a large telegram buffer. The buttons and LEDs on the device allow a local diagnosis including the operating status and communication errors.

The KNX PowerSupply DGS 366 is a 640 mA bus power supply with high efficiency and a small footprint of only 4 units (72 mm). The device has a bus choke and additionally provides an output for auxiliary power.

  Power, diagnosis and logic functions

The integrated KNX node monitors output current, bus voltage and the temperature in the enclosure. Various logic functions are available for application purpose. The configuration is done with the ETS (version 4.2 or higher). An easy to read OLED display on the front panel enables the user to display the operating parameters locally on the device.

  Technical data

 Mechanical data

• Housing: plastic
• DIN rail mounted device, width: 4 modules (72mm)
• Weigth: approx 260 g

User Interface

• Four keys for on device settings
• OLED display
• KNX programming LED

KNX

• Device Model System B
• Compatible with ETS 4.2 (or higher)

Connectors

• Plug for external power supply 230 V AC
• Connector for KNX TP (red/black)
• Connector for auxiliary power output (yellow/white)

The KNX TP LineCoupler 650 connects two KNX segments (for example, a KNX line with a KNX area). It has a very compact design. The device has a filter table (8K bytes) and ensures a galvanic isolation between the lines. The coupler is compatible with the ETS® software from ETS4.2. The buttons on the front panel allow disabling the telegram filter for testing purposes. The LEDs indicate the operating status and communication errors on the bus.

  Technical data

 Mechanical data

• Housing: plastic
• DIN rail mounted device, width: 1 module (18 mm)
• Weigth: approx 40 g

User Interface

• two keys for on device settings
• three multi color LEDs
• KNX programming LED and KNX programming key

KNX

• Medium TP/TP
• Filter table 8k Byte

Power supply

• KNX main line approx. 5 mA
• KNX sub line approx. 3 mA

Connectors

• Connector for KNX-TP main line (red/black)
• Connector for KNX-TP sub line (red/black)

The KNX IP LineMaster 762 combines the central functions of a KNX bus line in a compact device (6TE): a 640 mA bus power supply with inductor, IP router and IP interface. In addition to the bus voltage, the power supply also has an auxiliary voltage output. The IP router in the device allows the forwarding of telegrams between different lines via a LAN (IP) as a fast backbone. Via the interface function the KNX line can be addressed directly from a PC (eg with ETS version 4.2 or higher).

The device operates according to the KNXnet/IP specification using core, device management, tunneling and routing. The configuration is done with the ETS (version 4.2 or higher). An easy-to-read OLED display on the front allows the display of the operating parameters locally on the device.

  Power supply with choke

The power supply with high efficiency of the KNX IP LineMaster 762 provides a 29V bus voltage for the KNX system and an additional output with auxiliary voltage for supplying other devices. Special operating conditions such as short circuit, overvoltage, overload or overtemperature are logged and can be read off the display. The current current consumption is also displayed. A reset of the connected bus nodes is possible via the keypad.

  KNX IP Router

The KNX IP LineMaster 762 integrated KNX IP router allows the transmission of telegrams to other lines via the LAN (IP) as a fast backbone (KNXnet/IP routing). The KNX IP LineMaster 762 thus also assumes the function of a KNX line coupler.

  KNX IP Interface

The KNX IP LineMaster 762 can be used as an interface for bus access via IP. The KNX system can be configured and monitored from any PC in the LAN (KNXnet/IP tunnelling).

  Technical data

 Mechanical data

• Housing: plastic
• DIN rail mounted device, width: 6 modules (108 mm)
• Weigth: approx 300 g

User Interface

• Four keys for on device settings
• OLED display
• KNX programming LED

Ethernet

• 100BaseT (100Mbit/s)
  
• 6 KNXnet/IP Tunneling connections

KNX

• Medium IP/TP
• Filter table 8 kByte (64k group addresses)
• compatible with ETS 4.2 (or higher)

Connectors

• Plug for external power supply 230 V AC
• Connector for KNX TP (red/black)
• Connector for auxiliary power output (yellow/white)
• LAN RJ-45 socket

KNX IP BAOS 773

The KNX IP BAOS 773 is used as Interface for connecting to KNX both on telegram level (KNXnet/IP Tunneling) and on data point level (KNX Application Layer). Clients can directly access Group Objects via either a Binary Protocol (over TCP/IP or UDP/IP) or via JSON (Java Script Object Notation) Web Services. The device is configured with the ETS and supports up to 250 Group Objects. 10 simultaneous client connections are supported.

BAOS is an acronym for “Bus Access and Object Server”. It is possible to connect to the KNX bus everywhere over LAN. Bus connection over the internet with KNX IP BAOS 773 is also possible. The device supports 5 simultaneous KNXnet/IP tunneling connections.

The buttons are for diagnostic purposes. The LEDs indicate the operating status and communication errors on the bus. Power is supplied via the KNX bus.

Weinzierl_773_KNX_IP_BAOS_Übersicht.png

  BAOS SDK

For quick and easy integration of BAOS services in your own projects there are two free SDKs available. First, the BAOS Binary SDK, a C++ implementation of the BAOS Binary Protocol. The following systems are supported:

    Windows
    Linux
    Mac OS X
    iOS

For the integration of BAOS Services in a Web browser, we offer the BAOS Web Services SDK. This SDK is based on HTTP and Java script, the BAOS Services provides a simple JavaScript API.

    SDK for BAOS Binary Services
    SDK for BAOS Web Services

 Technical data
Mechanical data

    Housing: plastic (PC)
    DIN rail mounted device, width: 1 unit (18mm)
    Weight: approx. 40g

Controls and indicators

    2 buttons and 3 LEDs (multicolor)
    KNX programming button with LED (red)

KNX

    Medium TP
    Device Model System B
    Max. Communication Objects: 250

Ethernet

    10BaseT (10Mbit/s)
    Supported internet protocols ARP, ICMP, IGMP, UDP/IP, TCP/IP, DHCP and Auto IP
    Up to 5 KNXnet/IP Tunelling connections  simultaneously
    KNX BAOS Binary Protocol V2.0
    KNX BAOS Web Services (JSON)

Power supply

    KNX Bus approx. 15 mA

Connectors

    Bus connector for KNX (red/black)
    LAN RJ-45 socket

KNX IP BAOS 773

The KNX IP BAOS 773 is used as Interface for connecting to KNX both on telegram level (KNXnet/IP Tunneling) and on data point level (KNX Application Layer). Clients can directly access Group Objects via either a Binary Protocol (over TCP/IP or UDP/IP) or via JSON (Java Script Object Notation) Web Services. The device is configured with the ETS and supports up to 250 Group Objects. 10 simultaneous client connections are supported.

BAOS is an acronym for “Bus Access and Object Server”. It is possible to connect to the KNX bus everywhere over LAN. Bus connection over the internet with KNX IP BAOS 773 is also possible. The device supports 5 simultaneous KNXnet/IP tunneling connections.

The buttons are for diagnostic purposes. The LEDs indicate the operating status and communication errors on the bus. Power is supplied via the KNX bus.

Weinzierl_773_KNX_IP_BAOS_Übersicht.png

  BAOS SDK

For quick and easy integration of BAOS services in your own projects there are two free SDKs available. First, the BAOS Binary SDK, a C++ implementation of the BAOS Binary Protocol. The following systems are supported:

    Windows
    Linux
    Mac OS X
    iOS

For the integration of BAOS Services in a Web browser, we offer the BAOS Web Services SDK. This SDK is based on HTTP and Java script, the BAOS Services provides a simple JavaScript API.

    SDK for BAOS Binary Services
    SDK for BAOS Web Services

 Technical data
Mechanical data

    Housing: plastic (PC)
    DIN rail mounted device, width: 1 unit (18mm)
    Weight: approx. 40g

Controls and indicators

    2 buttons and 3 LEDs (multicolor)
    KNX programming button with LED (red)

KNX

    Medium TP
    Device Model System B
    Max. Communication Objects: 250

Ethernet

    10BaseT (10Mbit/s)
    Supported internet protocols ARP, ICMP, IGMP, UDP/IP, TCP/IP, DHCP and Auto IP
    Up to 5 KNXnet/IP Tunelling connections  simultaneously
    KNX BAOS Binary Protocol V2.0
    KNX BAOS Web Services (JSON)

Power supply

    KNX Bus approx. 15 mA

Connectors

    Bus connector for KNX (red/black)
    LAN RJ-45 socket

KNX IP BAOS 773

The KNX IP BAOS 773 is used as Interface for connecting to KNX both on telegram level (KNXnet/IP Tunneling) and on data point level (KNX Application Layer). Clients can directly access Group Objects via either a Binary Protocol (over TCP/IP or UDP/IP) or via JSON (Java Script Object Notation) Web Services. The device is configured with the ETS and supports up to 250 Group Objects. 10 simultaneous client connections are supported.

BAOS is an acronym for “Bus Access and Object Server”. It is possible to connect to the KNX bus everywhere over LAN. Bus connection over the internet with KNX IP BAOS 773 is also possible. The device supports 5 simultaneous KNXnet/IP tunneling connections.

The buttons are for diagnostic purposes. The LEDs indicate the operating status and communication errors on the bus. Power is supplied via the KNX bus.

Weinzierl_773_KNX_IP_BAOS_Übersicht.png

  BAOS SDK

For quick and easy integration of BAOS services in your own projects there are two free SDKs available. First, the BAOS Binary SDK, a C++ implementation of the BAOS Binary Protocol. The following systems are supported:

    Windows
    Linux
    Mac OS X
    iOS

For the integration of BAOS Services in a Web browser, we offer the BAOS Web Services SDK. This SDK is based on HTTP and Java script, the BAOS Services provides a simple JavaScript API.

    SDK for BAOS Binary Services
    SDK for BAOS Web Services

 Technical data
Mechanical data

    Housing: plastic (PC)
    DIN rail mounted device, width: 1 unit (18mm)
    Weight: approx. 40g

Controls and indicators

    2 buttons and 3 LEDs (multicolor)
    KNX programming button with LED (red)

KNX

    Medium TP
    Device Model System B
    Max. Communication Objects: 250

Ethernet

    10BaseT (10Mbit/s)
    Supported internet protocols ARP, ICMP, IGMP, UDP/IP, TCP/IP, DHCP and Auto IP
    Up to 5 KNXnet/IP Tunelling connections  simultaneously
    KNX BAOS Binary Protocol V2.0
    KNX BAOS Web Services (JSON)

Power supply

    KNX Bus approx. 15 mA

Connectors

    Bus connector for KNX (red/black)
    LAN RJ-45 socket

KNX IO 510

• Compact Switching Actuator
• 2 Outputs Relays 230V ~, 8A, bi-stable
• Switching, staircase function, heating actuator
• Integrated logic and timer functions
• Connectors: KNX, plug-in screw connectors for IO
• DIN rail mounted device, 1 unit, 18 mm

The KNX IO 510 (2O) is a compact switching actuator with 2 bi-stable relay outputs. The actuator provides the function for universal outputs including scene control, timer, staircase lightning and to control heating valves (PWM for thermoelectric valve drives).

Two push buttons and three LEDs allow a local operation and visualization of the device state. In addition to the output channels the device includes 16 independent functions for logic or timer control.
  Technical data
 Mechanical data

    Housing: plastic
    DIN rail mounted device, width: 1 modules (18 mm)
    Weigth: approx 50g

User Interface

    two keys for on device settings
    three multi color LEDs
    KNX programming LED and KNX programming key

KNX

    Device Model System B
    Compatible with ETS 4.2 (or higher)

Connectors

    Connector for KNX Bus (red / black)
    Pluggable screw connector (3 poles) for actuator channel 1
    Pluggable screw connector (3 poles) for actuator channel 2

Output channels (actuator)

    Relay type: 230V ~ / 8A, bi-stable
    Depending on load type (capacitive or inductive)
    The switching power can be reduced significantly.

KNX IO 520

• Compact Blinds Actuator with Binary Input
• 1 Output Blinds, 230V ~, 8A
• Drive directions electrically locked against each other
• For blinds, roller shutters or window drives
• Drive to position via time calculation
• 2 Inputs 12..230 V, galvanically isolated
• Switching, dimming, blinds, scenes, boost counter
• Integrated logic and timer functions
• Connectors: KNX, plug-in screw connectors for IO
• DIN rail mounted device, 1 unit, 18 mm

The KNX IO 520 (1J2I) is a compact blind actuator with two additional binary inputs. The actuator is used to control a blind, a shutter or a window drive. The relay contacts are electrically interlocked. The inputs can be connected to conventional switches with an external voltage of 12 to 230 V. In the not configured state of the binary inputs control the actuator channel. Via commissioning the device using ETS® software the binary inputs can be used independently.

Two push buttons and three LEDs allow a local operation and visualization of the device state. In addition to the output and input channels the device includes 16 independent functions for logic or timer control.
  Technical data
 Mechanical data

    Housing: plastic
    DIN rail mounted device, width: 1 modules (18 mm)
    Weigth: approx 65 g

User Interface

    two keys for on device settings
    three multi color LEDs
    KNX programming LED and KNX programming key

KNX

    Device Model System B
    Compatible with ETS 4.2 (or higher)

Connectors

    Connector for KNX Bus (red / black)
    Pluggable screw connector (3 poles) for blind output
    Pluggable screw connector (3 poles) for binary input channel 1 and 2

Output channel (Blind actuator)

    Relay type: 230V ~ / 8A
    Inductive load (cosF = 0.4): 230V ~ / 3.5A

Input channel (Binary in)

    Voltage: 12 .. 230 V = ~
    Current: <1 mA

KNX IO 511

• Compact Switching Actuator with Binary Input
• 1 output relay
• Switching, staircase function, heating actuator
• 2 inputs 12..230 V, galvanically isolated
• Switching, dimming, blinds, scenes, impulse counter
  Zero crossing detection via input channel
• KNX compatible replacement for conventional
  impulse switches
• Integrated logic and timer functions
• Connectors: KNX, plug-in screw connectors for IO
• DIN rail mounted device, 1 unit, 18 mm

The KNX IO 511 (1O2I) is a compact switching actuator with 1 bi-stable output and 2 binary inputs. The actuator provides the function for universal outputs including scene control, timer, staircase lighting and heating valves (PWM for thermoelectric valve drives). The inputs can be connected to conventional switches with an external voltage of 12 to 230 V. In ex-factory settings the inputs are connected internally to the actuator. The actuator combined with input B1 serves as a latching relay. Input B2 is used for zero crossing detection.
Two push buttons and three LEDs allow a local operation and visualization of the device state.

In addition to the output and input channels the device includes 16 independent functions for logic or timer control.
  Technical data
 Mechanical data

    Housing: plastic
    DIN rail mounted device, width: 1 modules (18 mm)
    Weigth: approx 60 g

User Interface

    two keys for on device settings
    three multi color LEDs
    KNX programming LED and KNX programming key

KNX

    Device Model System B
    Compatible with ETS 4.2 (or higher)

Connectors

    Connector for KNX Bus (red / black)
    Pluggable screw connector (3 poles) for actuator channel 1
    Pluggable screw connector (3 poles) for input channel 2 and 3

Output channel (Actuator)

    Relay type: 230V ~ / 8A, bi-stable
    Depending on load type (capacitive or inductive)
    The switching power can be reduced significantly.

Input channels (Binary in)

    Voltage: 12 .. 230 V = ~
    Current: <1 mA

KNX IO 410

• Compact Binary Input
• 4 inputs 12..230 V, galvanically isolated
• Switching, dimming, blinds, scenes, impulse counter
• Integrated logic and timer functions
• Connectors: KNX, plug-in screw connectors for IO
• DIN rail mounted device, 1 unit, 18 mm

The KNX IO 410 (4I) is a compact binary input with 4 channels to control lights, shutter etc. The inputs can be connected to conventional switches with an external voltage of 12 to 230 V. Using as impulse counter is possible as well. Two push buttons and three LEDs allow a local operation and visualization of the device state.

In addition to the input channels the device includes 16 independent functions for logic or timer control.
  Technical data
 Mechanical data

    Housing: plastic
    DIN rail mounted device, width: 1 modules (18 mm)
    Weigth: approx. 50 g

User Interface

    two keys for on device settings
    three multi color LEDs
    KNX programming LED and KNX programming key

KNX

    Device Model System B
    Compatible with ETS 4.2 (or higher)

Connectors

    Connector for KNX Bus (red / black)
    Pluggable screw connector (3 poles) for binary input channel 1 and 2
    Pluggable screw connector (3 poles) for binary input channel 3 and 4

Input channels (Binary in)

    Voltage: 12 .. 230 V = ~
    Current: <1 mA

KNX IO 411

• Compact Binary Input
• Like KNX IO 410 (Art No. 5230)
• For dry contacts
• Contact voltage galvanically isolated

Binary input with 4 channels for controlling light, blinds, etc. with conventional switches or contacts. The inputs can be controlled with an external voltage of 12 to 230 V.

In addition to the input channels the device includes 16 independent functions for logic or timer control.
  Technical data
 Mechanical data

    Housing: plastic
    DIN rail mounted device, width: 1 modules (18 mm)
    Weigth: approx. 50 g

User Interface

    two keys for on device settings
    three multi color LEDs
    KNX programming LED and KNX programming key

KNX

    Device Model System B
    Compatible with ETS 4.2 (or higher)

Connectors

    Connector for KNX Bus (red / black)
    Pluggable screw connector (3 poles) for binary input channel 1 and 2
    Pluggable screw connector (3 poles) for binary input channel 3 and 4

Input channels (Binary in)

    Voltage: 12 .. 230 V = ~
    Current: <1 mA

KNX BAOS 838 Module kBerry (Art. No. 5208)
• KNX module with serial protocol
• Extension board for Raspberry Pi*
• 1000 communication objects
• Size: 56x35 mm
• Free BAOS SDK for Raspian (available at weinzierl.de)

The Weinzierl KNX BAOS Modules are a powerful solution for KNX connectivity on a compact circuit board at low costs. They are targeted at manufacturers who want to integrate existing or new products into the KNX system as full compliant devices with complete support of the ETS software.

The KNX BAOS Module 838 kBerry is an adaptation of the proven KNX BAOS modules specifically made for the Compatible with Raspberry Pi A, B, A+, B+, 2B, 3B; Raspberry Pi is a trademark of the Raspberry Pi Foundation" data-placement="top" data-template='

The KNX part of the kBerry Module is supplied by the bus voltage. To implement your software for the BAOS object server the BAOS SDK is available as a free download. For using the kBerry as telegram interface the kDrive-Express SDK can be used. For the kDrive-Express a free version is available, too.

  Customer Benefits

•  Low investments
• Optimal price-performance ratio
• Shorter development time
• For modular device concept
• Simple baseboard design
• Free demo software available

  Integrated Object Server

The benefit of the Object Server in the KNX BAOS Modules is the logical decoupling of the application from the KNX communication. The application can access the values of the communication objects without any knowledge of KNX telegram formats or KNX addresses used in the current installation. The KNX BAOS Module 838 kBerry offers up to 1000 data points.

The module autonomously generates and sends group telegrams. Received group telegrams will be interpreted in the module and the values will be stored in the addressed communication objects. The complete download of ETS is handled within the module.

  Quick start into KNX device development

For a quick start into the development of KNX devices we recommend our KNX BAOS Starter Kit. It contains a development board and two KNX BAOS Modules. For the development board we provide a free demo project which implements the BAOS protocol and a simple application. A demo tool for Windows® is available to test the BAOS protocol from a PC.

A generic ETS (Engineering Tool Software) database is available for setting the data types and linking the communication objects. Of course, it is also possible to create individual databases for your devices. So the KNX BAOS Modules allow a fast development of full value KNX devices which of course can be certified by the KNX Association.

  Ready to run

The kBerry SDK for the Raspberry Pi is available as a free download and allows the instant operation of the KNX BAOS Module 838 kBerry on the Raspberry Pi (which is not included in the sales kit)