Side Menu
Categories
SystemTera® | Version Information SystemTera 2.23.1
1800
post-template-default,single,single-post,postid-1800,single-format-standard,ajax_fade,page_not_loaded,smooth_scroll,

Blog

Version Information SystemTera 2.23.1

Performing the Update

This update package is much larger as usual and requires up to 10 minutes of processing time after the download has been completed. During the upgrade process the server must not be reset or it might become unusable!

New or Improved Functionality

[STA-2549] – Updated Linux Kernel for Server V / VC

The Linux kernel was updated from version 3.12 to version 4.4.

[STA-2491] – Updated KNX Support Libraries and Linux Userland for Server V / VC

The entire Linux userland has been updated to the most recent stable version available. This includes security critical components such as the Nginx web server or the OpenSSL components used for data encryption. As a result the system is up to date again regarding bug fixes for security leaks which have been detected in commonly used Linux components.

The KNX communications library has also been updated.

As was the case before the SystemTera Server can also be used as a KNX TP bus interface for ETS to program KNX TP devices. To permit control of which physical addresses are used on the KNX TP Bus, two new properties have to be configured on the KNX bus:

Client addresses base: The first address used by an Ethernet gateway client (e.g. ETS) on the KNX TP Bus.

Client addresses cound: The number of consecutive physical addresses available for Ethernet gateway clients.

As a consequence of this update it has become possible to also program some older EIB devices such as the ABB JA/S4.6.1 actor, where ETS previously got stuck when trying to program the device via the System Tera Server V.

[STA-2815] – Server V: Enhanced Inputs

The direct inputs of the Server-V (analog, digital and pulse counter inputs) have been enhanced:

  1. It is now possible to configure the polling interval for each input separately instead of having one polling interval for all inputs. The minimum interval is still 100ms. The default has been decreased to 1 second.
  2. For digital inputs and PT1000 inputs there is a new property “ignore repeated values from bus” on the value attribute. When checked, only value changes are forwarded to associated data object attributes for processing. In previous versions it was not possible to configure this behavior and repeated values were always ignored.
  3. Pulse counter inputs offer the option “Debounce” in the property section “Behavior”. If debounce is selected, the pulse counter will count a maximum of one pulse every two polling intervals.
    For example: The input source is a a mechanical relais. The application should never generate more than one pulse per second. The relais is known to create 2 to 5 bounce events when closing. In this case set the polling interval to 500ms and activate “debounce”.
    Note: The System Tera Server Hardware is certified to count all pulses starting from 0.5 ms pulse and gap duration, and might count bounce events starting from 0.1 ms pulse / gap duration. Common reed relais will on occasion generate two pulses instead of one when not using the debounce option.

For existing configurations the “Inputs” node has been renamed to “Inputs (simplified)”. To access the new functionality, delete the “Inputs (simplified)” node and add an “Inputs” node to the SystemTera.Server V.

[STA-2839], [STA-2549] – Add support for USB to serial chips for Server V / VC

Support for a number of USB to serial chips such as the CH340 has been added to Server-V and Server-VC.

These chips are used in USB to RS232 and USB to RS485 interfaces from various vendors.

Fixed Defects

[STA-2828] – Server V / VC: KNXD driver may send telegrams too quickly

Previous System Behavior:

When rules or system startup create a situation where the Server V creates a lot of KNX telegrams in a short period of time, too may telegrams may be sent to the KNX bus and cause collisions with other devices on the bus.

System Behavior now:

When rules or system startup create a situation where the Server V creates a lot of KNX telegrams in a short period of time,a 5ms pause is enforced after each telegram before sending the next telegram to the KNX bus.