ClearSCADA 2009 R1.2 Release Notes

[Anonymous user]

📖 Home  Back  

Product Enhancements

• "Severity" and "Area Of Interest" fields have been added to the CFX Export object Properties form.

• The labeling of various configuration fields on the CFX Export object has been improved. For example, the labels for live analyses flags have been made more consistent and all occurrences of 'Sub-Directory' have been changed (to 'Subdirectory') as used elsewhere in the product.

• The ODBC Driver has been enhanced to support multi-threaded ODBC client applications.

• Support for LP-1 type outstation has been added for the Kingfisher driver. Additionally more status information has been exposed on the outstation object (CPU Type, RAM Size) and the firmware version can now be accessed via a database property.

• Text alarm acceptance has been changed so as to allow duplicated text alarms to be accepted.

• The default value of the Anti-Alias setting for new mimics has been changed to be the value set via the default mimic parameters set via the Tools/Options dialog.

• The Id field in the CAlarm table has been changed to be a reference. This allows the reference function in SQL (De-Reference operator '->') to be used on this field.

• The name of the Crystal Reports tab "Export to WebX" has been changed to "Generate for WebX".

• The schema now shows an empty string for the "Description" if a metadata field has no description set. Also, the "Display Name" falls back to the configured view info string, if configured in the field, or empty string if none is set.

• Properties for array database objects can now be set from a JScript script.

Resolved Issues

CFX Export object

• Prevented attempts to perform a CFX Export to a specific file, using the default filename without specifying a format for the default file by invalidating the configuration for these settings. Previously, the attempt would be allowed but the export would fail with a rather unhelpful event message.

• Ensured that two consecutive failures to export generate only alarms/events for these failures, without an intermediate "CFX Export successful" event message. This had been caused by the clearing of the first alarm when the second export was set in progress.

• Improved CFX Export by ensuring that Flow Run configuration, event and historic data are correctly converted or scaled from specified input/contract units to appropriate CFX output units. Issues causing corruption of alphanumeric event data in the export file have been fixed.

Simple Drivers

• ODBC:

• The 64 Bit ODBC driver has been changed to return the correct values for arguments that expect 64 bit values.

• Fixed a bug in the ODBC driver, where ODBC client programs could fail to connect after the 60th successful connection attempt. A typical symptom of this problem is Crystal Reports failing to generate after a period of time.

• The ODBC Driver has been modified to process SQL Server "Text" columns. Note: DriverODBC will only read the first 65535 characters of any "Text" column.

Advanced Drivers

• SCADAPack Modbus:

• The RealFLO "Read Configuration" process has been modified to ensure that the AGA-8 gas composition ratios can be correctly read when the Composition Units are set to Mole Fraction.

• Corrected RealFLO driver to ensure that the "Minimum clock drift before RealFLO clock is set" is applied correctly.

• The polling of standard SCADAPackModbus points when attached to a RealFLO outstation has been corrected to make sure the driver does not get caught in a loop if the polling of the standard points overlaps with the flow run poll.

• DNP3:

• A problem was found in the DNP3 driver that caused an outstation to remain ahead of the polling queue after an application layer time-out. This could result in indefinable polling attempts to an outstation that is experiencing intermittent communications.

• The DNP3 protocol translation has been improved when translating file transfers.

• Fixed E-Series download configuration which was incorrectly downloading two entries for user and system point types.

• Corrected a problem with template instance conversion when both templates contained SCADAPack E-Series analogue or binary points.

• The Kingfisher driver has been corrected so that it will correctly recover the remaining event data in the outstation if a previous PSTN call failed mid-way through recovering the event data.

• A potential crash in advanced drivers which could occur during certain configuration changes to switched sets which resulted in them needing to be re-created has been fixed.

• Fixed a fault which could have caused most advanced drivers to crash if a point update was being processed at the same time a significant configuration change was being processed (or the point was deleted).

• A fault has been fixed in the Network channel code which caused the channel to erroneously fail, when in UDP mode, if a certain non-fatal error was received from the Windows sockets layer when checking if there was any more data to read.

• Prevent possible failure to establish communications with outstation on IEC60870-5-104 Master Driver.

Query Processor

• The crash in the list Filter dialog when trying to edit a clause that references a Time column and contains any equality comparison (==, <>, <= or >=) has been fixed.

• Fixed issue with embedded alarm lists where the list's filter would sometimes not be updated if both the Filter and System properties were animated.

• The data table processing in the query processor has been fixed so that an access plan of "Non-Unique By Column (Constrained)" returns the correct rows.

• Processed historic views in the query processor now support scan as an access path.

• Fixed a crash when using a data table with an access plan of "Non-Unique By Column (Constrained)", when no matching rows were returned.

Web Client

• A fault existed in the web server that could allow unauthorized users access to the system, bypassing ClearSCADA security controls. This has been corrected in this release of ClearSCADA by ensuring that the affected features are now subject to the same security controls applied across the rest of the system. It is strongly recommended that all users upgrade to the latest version of their installed ClearSCADA versions to take advantage of this fix and to ensure the security of their server.

• Manual Alarm redirection requests from the Web client are now proxied to the Main server if the client is connected to the Standby.

• The Str() function in the Web client has been corrected to use appropriate time zone settings when converting DATE values to strings.

• Fixed issue with standard method dialog in both ViewX and the Web client, where if an invalid value was entered for an argument resulting in an error dialog, then a valid value

entered without cancelling the method dialog, then an empty value would be sent to the server instead of the valid value.

• Fixed inactivity logout issues in ViewXCtrl:

• When inactivity logout occurred on a list or alarm list page, the logon page didn't redirect back to the list after logging back on.

• After an inactivity logout had occurred, subsequent instance of ViewXCtrl would logout after 10 seconds until IE was restarted.

• Fixed issues with dynamic position animations in the Web client.

• Modified the Web client to ensure animations using Username()/Locale() functions are updated when user changes when used on embedded mimics.

Miscellaneous:

• Fixed issue where a logic program's Trigger field would not be patched if the program was set to execute On Input Processed, unless the program code also referenced the trigger object or other objects affected by the move/rename. This could cause integrity check failures in cases where an instance program did get patched but the template program didn't.

• Fixed a problem when using SDK objects within templates and instances. SDK points in templates would incorrectly be instantiated as abstract points within the instance.

• The Grid Reference strings generated by the Grid Reference parameter are now correctly formatted. The configuration of these fields is now validated for correctness.

• The IsLoggedOn column in the CDBUser table will now be updated when the user logs on/off on the Standby server.

• The ELEMENT command in LOGIC has been fixed so that the server no longer throws an exception when the located element is empty.

• The logic methods GetVariable and SetVariable have been changed so that they require Read and Control privileges respectively.

• Modified 'Locate In Template' function in ViewX database navigator so that it locates the object in the template of the top-level instance instead of the immediate instance parent.

• Ensured that a point with an alarm limit profile is updated if the limit is crossed (and therefore the state has changed) when the value of the point isn't changing.

• When an alarm limit is using a profile, the calculation to apply hysteresis (including hysteresis of zero) was using the limit at the time of the previous update rather than the time of the new update, which means it could incorrectly determine that the new value is within the hysteresis and therefore the point hadn't changed state. This problem has been fixed in this release.

• When a point was configured with a mixture of fixed and variable limits (i.e. profiles) and one or more of the fixed limits were tuned, the value reported by the 'xxxxLimit' and 'xxxxLimitTuned' properties for the variable limits was (usually) zero. These now report the appropriate standard or alternate fixed limit (usually DBL_MAX, to signify fixed limit isn't used).

• Prevented a spurious error that occurred when a user with an expired password attempted to log onto ViewX connected to a standby server.

• Fixed the priority of the "transaction in progress" color for simple points. Previously a transaction in progress on a simple point would take priority over alarms or bad quality.

• A potential server crash that could occur when a client attempts to create an OPC DA group with the server under extreme loading has been fixed.

Previous Versions

• Click here for Release Notes from ClearSCADA 2009 R1.1.

• Click here for Release Notes from ClearSCADA 2009 R1.

• For Release Notes from earlier versions of the product, please refer to the Release Notes pages that can be found in the ClearSCADA Releases section of the Control Microsystems Resource Center.

Go: Home Back