...
The exported Excel has the following format:
Name | Object function | Device name | Path | Comm flag | Read flag | Write flag | Transm flag | Update flag | Init-read flag | Physical adr. | Reserved | Group addresses | Type information | Data type |
If bus voltage recovery,contact is>=0(unchange) | switch_1_switch | (Device name) | T | T | T | T | F | 10.10.1 | 1.1.1 | 1Bi | ||||
If bus voltage recovery,contact is>=0(unchange) | switch_2_switch | (Device name) | T | T | T | T | F | 10.10.1 | 1.1.2 | 1Bi | ||||
If bus voltage recovery,contact is>=0(unchange) | switch_3_switch | (Device name) | T | T | T | T | F | 10.10.1 | 1.1.3 | 1Bi |
This export format has to converted to the KNX Telegram Definitions that our NETx BMS Platform or NETx MP Server is using. In addition, the KNXnet/IP router or interface that is used by our server to connect to the KNX network has to be defined.
...
If multiple KNX group addresses shall be defined, you can also also import an Excel file.
The Excel must have the following format:
KNX grp. adr. | KNX gateway name | Priority | Data Size | Data Type | Signing () | Unit () | Description () | Read on reconnect (F) | Read cycl. interval (s) (0) | Persistent (F) | Synchronize (T) | |
1/1/1 | Router1 | LOW | 1BIT | DPT_1.001 | Relay1 | |||||||
1/1/2 | Router1 | LOW | 1BIT | DPT_1.001 | Relay2 | |||||||
1/1/3 | Router1 | LOW | 1BIT | DPT_1.001 | Relay3 |
After having configured the KNXnet/IP router and all group addresses, save all files and restart the Core Server. Afterwards, you can find the data points within the Item Tree: