Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TapHome KNX Gateway uses a KNX component from Weinzierl called BAOS. The gateway is in ETS listed under the Weinzierl name. BAOS is KNX certified.doc_tap_Knx_Gatew;

1.

...

 doc_tap_

...

Prod_data;

Download product database from page https://www.weinzierl.de/images/download/development/830/Weinzierl_83x_KNX_BAOS_Module_ETS4.zip

doc_tap_down_pag;Open ETS 5 → Catalogs → import Weinzierl product database from downloaded archive.

doc_tap_ets5;

2.

...

 doc_tap_

...

BAOS;

Change to Topology view in ETS project:  

doc_tap_topology;

From producer catalogue choose Weinzierl producer and find KNX BAOS 832 module. Insert module to appropriate area and line.

doc_tap_prod_cataloq;

3.

...

 

...

doc_tap_

...

Conf_baos;

...

    

doc_tap_select_baos;

...

doc_tap_Data_Baos;

Label in BAOSData point typeUsed by TapHome virtual devicesUsed by TapHome virtual variableComment
DPT 11 Bit, Boolean


DPT 22 Bit, Control


DPT 34 Bit, Dimming, Blinds


DPT 48 Bit, Character Set


DPT 58 Bit, Unsigned Value


DPT 68 Bit, Signed Value


DPT 72 Byte, Unsigned Value


DPT 82 Byte, Signed Value


DPT 92 Byte, Float Value


DPT 103 Byte, Time

Implementing date and time from KNX into TapHome does not make sense. TapHome has its own internal date and time engine.
DPT 113 Byte, Date

DPT 124 Byte, Unsigned Value


DPT 134 Byte, Signed Value


DPT 144 Byte, Float Value


DPT 154 Byte, Access


DPT 1614 Byte, String

Planned feature, coming soon
DPT 171 Byte, Scene Number


DPT 181 Byte, Scene Control

...



doc_tap_Group_Object;

For data point which are only written from TapHome select Communication, Read, Transmit options:

doc_tap_data_bod;

Image Modified

4.

...

 doc_tap_

...

Group_add;

...

  

doc_tap_addres_baos;

Repeat the steps 3. and 4. for all data points which you want to be communicated to TapHome.

doc_tap_step3_4;

5.

...

 doc_tap_

...

Down;

doc_tap_gate_board;