Versions Compared

Key

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

...

NameDescriptionScopeUnitDefaultNotes
KNX.ServerPhysicalAddressIt specifies Specifies the physical KNX address of the NETx BMS Core Server for KNXnet/IP routing (not tunnelling). This address is used by the provided in outgoing KNX telegrams.0.0.0 - 15.15.255KNX physical address15.15.255
KNX.TimeoutIt specifies the timeout value for KNX "READ" request. This value is also used for read queries during the initialization phase of the system.2 - 60seconds10
KNX.PhysicalDeviceTimeoutSpecifies 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 - 600seconds3
KNX.PhysicalDeviceRetryCountSpecifies how often a physical device is polled before its status is considered to be offline.positive integer

none

3


KNX.CyclicEventStartDelayIt specifies the start delay for cyclic Events. This value is used by event engine of the server.10 - 600seconds30
KNX.CyclicEventTelegramGapIt specifies the time gap between cyclic events (in milliseconds). This value is used by event engine of the server.100 - 3000milliseconds250
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 - sets the linked KNX group addresses when corresponding KNX group telegram is received by the server
  • OFF - not activated
ON, OFFnoneOFF

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 - sets the linked KNX group addresses when sending KNX telegrams
  • OFF - not activated

ON, OFF

noneOFF

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 - shows undefined KNX telegrams
  • OFF - not activated

ON, OFF

noneOFF
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 - the KNX datapoints are polled after a reconnect
  • OFF - not activated

ON, OFF

noneOFFdeprecated 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 - automatic updating is activated
  • OFF - not activated
Warning

Note that activating cyclic refreshing of KNX datapoints may cause high amount of network traffic that may stress the connected KNX lines.


ON, OFF

noneOFFdeprecated 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.

Info

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.


5 - 86400

seconds10deprecated since 4.0.1000
KNX.CyclicRefreshAllValuesStartDelay

It specifies the delay of the first query process after the initialization of the server.

10 - 600

seconds60deprecated 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

250deprecated since 4.0.1000

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

noneOFFdeprecated 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

none0deprecated since 4.0.1000
KNX.GatewayBufferSizeSize 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 - 10000000telegrams50000available since 4.1.1004

...