Parameter | KNX.ServerPhysicalAddress |
|---|---|
Description | It specifies the physical KNX address of the NETx BMS Core Server. This address is used by the outgoing KNX telegrams. |
Scope | 0.0.0 - 15.15.255 |
Unit | None |
Default value | 15.15.255 |
Parameter | KNX.Timeout |
|---|---|
Description | It specifies the timeout value for KNX "READ" request. This value is also used for read queries during the initialization phase of the system. |
Scope | 2 - 60 |
Unit | seconds |
Default value | 10 |
Parameter | KNX.PhysicalDeviceTimeout |
|---|---|
Description | It 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. |
Scope | 1 - 600 |
Unit | seconds |
Default value | 30 |
Parameter | KNX.CyclicEventStartDelay |
|---|---|
Description | It specifies the start delay for cyclic Events. This value is used by event engine of the server. |
Scope | 10 - 600 |
Unit | seconds |
Default value | 30 |
Parameter | KNX.CyclicEventTelegramGap |
|---|---|
Description | It specifies the time gap between cyclic events (in milliseconds). This value is used by event engine of the server. |
Scope | 100 - 3000 |
Unit | milliseconds |
Default value | 250 |
Parameter | KNX.SetLinkOnReceive |
|---|---|
Description | 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 - sets the linked KNX group addresses when corresponding KNX group telegram is received by the server OFF - not activated |
Scope | ON, OFF |
Unit | None |
Default value | OFF |
Parameter | KNX.SetLinkOnSend |
|---|---|
Description | 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 - sets the linked KNX group addresses when sending KNX telegrams OFF - not activated |
Scope | ON, OFF |
Unit | None |
Default value | OFF |
Parameter | KNX.ShowUndefinedTelegrams |
|---|---|
Description | 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 - shows undefined KNX telegrams OFF - not activated |
Scope | ON, OFF |
Unit | None |
Default value | OFF |
! Following KNX parameters are available only for compatibility reasons. In future versions they may vanish.
Parameter | KNX.RefreshAllValuesOnConnect |
|---|---|
Description | 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 - the KNX datapoints are polled after a reconnect OFF - not activated |
Scope | ON, OFF |
Unit | None |
Default value | OFF |
Parameter | KNX.CyclicRefreshAllValues |
|---|---|
Description | 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 - automatic updating is activated OFF - not activated |
Scope | ON, OFF |
Unit | None |
Default value | OFF |
!Attention: Note that activating cyclic refreshing of KNX datapoints may cause high amount of network traffic that may stress the connected KNX lines.
Parameter | KNX.CyclicRefreshAllValuesInterval |
|---|---|
Description | 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. |
Scope | 5 - 86400 |
Unit | seconds |
Default value | 10 |
Example: 10 datapoints for gateway 192.168.1.1 are defined. The global system send interval is set to 1 second ("send interval" can only be set in the NETx BMS Core Studio). In this case, an update process takes 10 seconds. If the "KNX.CyclicRefreshAllValuesInterval" parameter is set to 5 seconds, the next update process already starts after 5 seconds and tries to send read telegrams. Since the telegrams of the first refresh process are still under transmission, the request of the second process cannot be sent and so these requests will remain in the queue of the server. To solve this issue, the "KNX.CyclicRefreshAllValues TelegramGap" parameter has to be set accordingly.
Parameter | KNX.CyclicRefreshAllValuesStartDelay |
|---|---|
Description | It specifies the delay of the first query process after the initialization of the server. |
Scope | 10 - 600 |
Unit | seconds |
Default value | 60 |
Parameter | KNX.CyclicRefreshAllValuesTelegramGap |
|---|---|
Description | 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. |
Scope | 100 - 3000 |
Unit | milliseconds |
Default value | 250 |
Parameter | KNX.ResetOnDisconnect |
|---|---|
Description | 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. |
Scope | On, Off |
Unit | None |
Default value | On |
Parameter | KNX.ReadIntervalFactor |
|---|---|
Description | 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. |
Scope | 1 - 10 |
Unit | None |
Default value | 0 |