Versions Compared

Key

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

...

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 DescriptionScopeUnitDefault value
1IP AddressSpecifies the IP address of the KNXnet/IP gateway.IP addressNone
2Gateway Type

The type of the KNXnet/IP gateway. Supported types are

  • SEC_NETIP: secure KNXnet/IP tunnelling
  • NETIP: native KNXnet/IP tunnelling
  • NETIP_ROUTING: native KNXnet/IP routing
SEC_NETIP, NETIP, NETIP_ROUTINGNone
3PortThe UDP or TCP port number which is used to connect to the gateway.UDP or TCP port numberNone
4NameA unique human-readable name.StringNoneThe gateway's IP address.
5LocalityThis attribute can be used to specify the location of the gateway (can be any user-defined string).StringNone
6DescriptionThis attribute can be used to specify a human-readable text that further describes the gateway (can be any user-defined string).StringNone
7Source phys. KNX AddressThe physical KNX address used by the Core Server when sending telegrams. Only used for KNXnet/IP routing.KNX phys. addressNone
8Network Card IP AddressThe local network card IP address used by the Core Server. Only used for KNXnet/IP routing.IP addressNone
9Management CodeThe management code used for authentication to a secure KNXnet/IP tunnelling device. This must be identical to the code used within the ETS.StringNone
10Authentication CodeThe authentication code used for authentication to a secure KNXnet/IP tunnelling device. This must be identical to the code used within the ETS.StringNone

...