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;
...
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 BAOS | Data point type | Used by TapHome virtual devices | Used by TapHome virtual variable | Comment |
---|---|---|---|---|
DPT 1 | 1 Bit, Boolean | |||
DPT 2 | 2 Bit, Control | |||
DPT 3 | 4 Bit, Dimming, Blinds | |||
DPT 4 | 8 Bit, Character Set | |||
DPT 5 | 8 Bit, Unsigned Value | |||
DPT 6 | 8 Bit, Signed Value | |||
DPT 7 | 2 Byte, Unsigned Value | |||
DPT 8 | 2 Byte, Signed Value | |||
DPT 9 | 2 Byte, Float Value | |||
DPT 10 | 3 Byte, Time | Implementing date and time from KNX into TapHome does not make sense. TapHome has its own internal date and time engine. | ||
DPT 11 | 3 Byte, Date | |||
DPT 12 | 4 Byte, Unsigned Value | |||
DPT 13 | 4 Byte, Signed Value | |||
DPT 14 | 4 Byte, Float Value | |||
DPT 15 | 4 Byte, Access | |||
DPT 16 | 14 Byte, String | Planned feature, coming soon | ||
DPT 17 | 1 Byte, Scene Number | |||
DPT 18 | 1 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;
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;