...
Name | Description | Scope | Unit | Default | Notes |
|---|---|---|---|---|---|
KNX.ServerPhysicalAddress | Specifies the physical KNX address of the NETx BMS Core Server for KNXnet/IP routing (not tunnelling). This address is |
...
provided in outgoing KNX telegrams. |
...
0.0.0 - 15.15. |
...
255 | KNX physical address | 15.15.255 |
...
KNX.Timeout | It specifies the timeout value for KNX "READ" request. This value is also used for read queries during the initialization phase of the system. |
...
2 - 60 | seconds | 10 | ||
KNX.PhysicalDeviceTimeout | Specifies the timeout value for the telegrams that are sent to check the availability of KNX devices. This value is used by device manager subsystem. |
...
1 - 600 | seconds | 3 | |||
KNX.PhysicalDeviceRetryCount | Specifies how often a physical device is polled before its status is considered to be offline. | positive integer | none | 3 | |
KNX.CyclicEventStartDelay | It specifies the start delay for cyclic Events. This value is used by event engine of the server. |
...
10 - 600 | seconds | 30 | ||
KNX.CyclicEventTelegramGap | It specifies the time gap between cyclic events (in milliseconds). This value is used by event engine of the server. |
...
100 - 3000 | milliseconds | 250 | ||
KNX.SetLinkOnReceive | The "link manager" the subsystem of the Server provides the opportunity to handle linked KNX group addresses that are defined within the ETS. This parameter activates the handling of these linked group addresses.
|
...
| ON, OFF | none | OFF | |
KNX.SetLinkOnSend | The "link manager" the subsystem of the BMS Server makes possible the managing of linked KNX group addresses. This parameter specifies whether the mechanism is to be released by sending KNX telegrams.
|
...
| ON, OFF | none | OFF | |
KNX.ShowUndefinedTelegrams | If this parameter is set, received KNX telegrams that have an unknown KNX group address (i.e. a group address that is not defined within the server) will be shown in the message window of the NETx BMS Core Studio.
|
...
| ON, OFF | none | OFF | ||
KNX.ResetOnDisconnect | If set to ON, the quality of KNX datapoints will be set to UNCERTAIN if the corresponding KNXnet/IP gateway is offline. If this parameter is set to OFF, the KNX datapoints will remain GOOD even if the gateway is offline. | ON, OFF | none | OFF | |
KNX.GatewayBufferSize | Size of the outgoing gateway buffer (in number of telegrams). If the buffer is full the oldest up to 10.000 telegrams are removed and thereby lost. | 1000 - 10000000 | telegrams | 50000 | available since 4.1.1004 |
KNX.RefreshAllValuesOnConnect | If a KNXnet/IP router is reconnecting to the server, the server can poll the current value of all datapoints that are assigned to this router.
|
...
| ON, OFF | none | OFF | deprecated since 4.0.1000 |
KNX.CyclicRefreshAllValues | It is possible that the system automatically updates the internal data base in defined time intervals. The updates are done by sending cyclic KNX "READ" telegrams.
|
...
|
...
ON, OFF | none | OFF | deprecated since 4.0.1000 | ||
KNX.CyclicRefreshAllValuesInterval | It specifies the time interval that is used for the cyclic refresh mechanism. Note that all defined KNX datapoints are queried during a refresh. Therefore, this interval has to be chosen depending on the amount of KNX datapoints within the project. If the value is too small, the previous refresh process may not be finish and thus it will overlap with the next. |
...
|
...
|
...
5 - 86400 | seconds | 10 | deprecated since 4.0.1000 | ||
KNX.CyclicRefreshAllValuesStartDelay | It specifies the delay of the first query process after the initialization of the server. |
...
10 - 600 | seconds | 60 | deprecated since 4.0.1000 | |
KNX.CyclicRefreshAllValuesTelegramGap | It specifies the time interval between two read request during a refresh process. The value of this interval must be greater than the value of the global system send interval. |
...
100 - 3000 | milliseconds | 250 | deprecated since 4.0.1000 | |
KNX.ReadIntervalFactor | Using this parameter, the interval between two KNX read requests can be extended. The interval between two KNX read requests is the specified KNX sending value multiplied with this factor. A missing value or the value "'0"' means that the specified KNX sending interval is used. |
...
1 - 10 | none | 0 | deprecated since 4.0.1000 |
Article applies to the following products:
NETx BMS Platform
NETx Multi Protocol Server