SIPLUS CMS X-Tools - Release Notes
SIPLUS CMS
English
Release 2012-09
9 / 12
2.26
Too small Ring Buffers may confuse Storage Profiles
In case the ring buffer of an offline data is much too small (e.g. it is overwritten multiple times per second), a
Storage Profile which is using this online data as input may not detect this error and can produce unwanted
results without a notification to the user.
2.27
Automatic Assigning of Sequence IDs can cause Damage
In case of Analyzing Models/User Functions which use recursion, the automatic assigning of sequence IDs can
result in an order of sequence which does not allow the desired calculation to run properly.
2.28
Possible wrong first Timestamps from ION SIMATIC TDC T001 Devices
The first timestamps which are delivered by an ION SIMATIC TDC T001 directly after the start of its Device
Profile can be wrong. They can cause log entries about timestamp errors after the start.
2.29
No cancelling of the Post Trigger Time through Storage Profiles for offline
Data
Storage Profiles which use offline data as input do not cancel the post trigger time even in case a start event
occurs during the post trigger time.
2.30
Memory Management
Although the memory management has been significantly improved in V 03.05, it is not able to cover all possible
effects of low memory. The current memory management does not consider the fragmentation of the address
room of the process, it does not use a totally deterministic approach for the order of Configuration Files and it
does not react in case the maximal free block of the process drops too low. The possible effects are that the
status of currently suspended and running Configuration Files is dependent to values which are not clearly visi-
ble to the user and that the status can be different for the same Configuration Files at different moments in time.
2.31
Data Snapshots may freeze the X-Tools Client
In case a to-be-created data snapshot has to process a big amount of data, the X-Tools Client could freeze
during this time.
2.32
Delay during the Creation of automatic Reports for offline Data
Monitoring Views which create reports on base of offline data may wait up to one second after each created
report. This delay can cause a long processing time in case of long offline data and/or a lot of to-be-created
reports.
2.33
/openMVF may discard changed Monitoring Views
In case /openMVF is used in order to open an already opened Monitoring View and in case this already opened
Monitoring View contains unsaved changes, /openMVF discards all of these changes and opens the Monitoring
View according to the current settings within the file at the disk.
2.34
Possibly not established Connection to Socket Devices
In case an Interface Profile for socket devices was paused it may not be able to establish the connection to its
configured devices after it is continued.
2.35
Pausing of Monitoring Views in low Memory Situations
Pausing of Monitoring Views may fail in case there is not enough memory available for the copying of the cur-
rently displayed online data.