Side Menu
SystemTera® | Version Information SystemTera 2.22


Version Information SystemTera 2.22

New or Improved Functionality

[STA-2682] – Improved PID Controller

The behaviour of the PID controller can be fine tuned using the following new parameters:

Parameter “Control output min step size”
Minimum change to the control output values. Use this to have less frequent but bigger changes to for example valve positions.
Default Value: 0

Parameter “Extended parameters”
Controls the visibility of the following parameters. In most cases these parameters can be left at their default values.

Parameter “Ud=0 when setpoint changed”
The differential term is set to zero if the setpoint is changed.
Default “Yes”

Parameter “Ui when setpoint changed”
Choose the calculation for the integral term right after a setpoint change.
Possible values: “Standard calculation”, “Reset internal error integral”, “Proportional adjustment of error integral”
Default: Reset internal error integral

Parameter “Reset interval around setpoint”
This defines the size of the epsilon neighbourhood around the setpoint where the calculation of the integral term reverts to the reset method instead of using the proportional method after a setpoint change. (0-1)
Default 0.05

Parameter “Anti windup memory”
When anti windup becomes active, this defines the number of control loop runs for which the control error is stored (1-10).
Default 10

Parameter “Anti windup phase out”
Phase out the part of the control offset integral which is to be lost when anti windup becomes active instead of just cutting it off.
Default “Yes”

Parameter “Anti windup phase out rate (%)”
At activation of anti windup a part of the control offset integral is defined as to be eliminated. This part is reduced per control loop execution by the percentage defined in this parameter.
Default 5%

Parameter “Reduce redundant control output”
Consecutive identical values for control output are only dispatched every 15 minutes.
Default “Yes”

[STA-2684] – New Rule Engine Rules: Operating Meters

Operating meters provide meters, which count both the number and duration of counting events. There are separate counter values for the sums for the current day, the current month, the previous month, the current year and since the last counter reset.

The following new rules are available:

Operating meter (input is on)

A counting event is defined as the input having a value not equal to zero.

Operating meter (input above threshold)

A counting event is defined as the input having a value above the defined threshold. In addition a hysteris can be supplied.

Operating meter (input above threshold)

A counting event is defined as the input having a value below the defined threshold. In addition a hysteris can be supplied.

Operating meter (integral of input value per hour)

The counter integrates input values across time. If the input is set to 2 for 15 minutes and set to 0 for 45 minutes the result is 0.5 after one hour has elapsed.

Operating meter (sum of input values)

The counter counts the total of all input values. The can be used to e.g. create a total for pulse counters.

[STA-2736] – Export of local data storage

The SystemTera.Manager now offers functionality to export data stored locally on the SystemTera.Server on a USB flash drive. During the export the SystemTera.Server needs to be online and connected with the SystemTera.Cloud. The export creates a .CSV file.

[STA-2741] – LocalDataStorage: Alert on module stopping

An alert is sent to the SystemTera.Cloud when the module for local data storage has to be stopped (e.g. because the flash drive has been removed).

[STA-2742] – SystemTera.Manager installation without local administrator privileges

Starting from this version the SystemTera.Manager can be installed without having local admin privileges on the Windows system.

Fixed Defects

[STA-1837] – Tables and Diagrams not showing any data

Previous System Behavior:

In rare cases an error on the SystemTera.Cloud SQL server prevented data for diagrams and tables to be provided. If this error occurred, it usually persisted until the server was rebooted.

System Behavior now:

The problem has been solved and the query always generates a valid execution plan.

[STA-2740] – SystemTera.Server restart due to SignalR watchdog

Previous System Behavior:

The SignalR component watchdog did not always use the correct interval for checking the operation of the component. As a result the watchdog sometimes caused unnecessary restarts of the component.

System Behavior now:

The system now works as specified.