...
Info |
---|
! No telegrams are sent to the offline gateways. |
Info |
---|
! This definition file can also be generated using the ETS app import wizard (Studio → KNX → Inport NETx ETS App file ...) which generates the KNX gateway definitions from an exported ETS project. |
The structure of the gateway definition file is as follows:
...
Col# | Parameter | Description | Scope | Unit | Default value |
---|---|---|---|---|---|
1 | IP Address | Specifies the IP address of the KNXnet/IP gateway. | IP address | None | |
2 | Gateway Type | The type of the KNXnet/IP gateway. Supported types are
| SEC_NETIP, NETIP, NETIP_ROUTING | None | |
3 | Port | The UDP or TCP port number which is used to connect to the gateway. | UDP or TCP port number | None | |
4 | Name | A unique human-readable name. | String | None | The gateway's IP address. |
5 | Locality | This attribute can be used to specify the location of the gateway (can be any user-defined string). | String | None | |
6 | Description | This attribute can be used to specify a human-readable text that further describes the gateway (can be any user-defined string). | String | None | |
7 | Source phys. KNX Address | The physical KNX address used by the Core Server when sending telegrams. Only used for KNXnet/IP routing. | KNX phys. address | None | |
8 | Network Card IP Address | The local network card IP address used by the Core Server. Only used for KNXnet/IP routing. | IP address | None | |
9 | Management Code | The management code used for authentication to a secure KNXnet/IP tunnelling device. This must be identical to the code used within the ETS. | String | None | |
10 | Authentication Code | The authentication code used for authentication to a secure KNXnet/IP tunnelling device. This must be identical to the code used within the ETS. | String | None |
...