Download ClearSCADA 2010 R3.1 Release Notes

ClearSCADA
Software for Telemetry & Remote SCADA
Solutions

ClearSCADA 2010 R3.1
Release Notes
ClearSCADA 2010 R3.1 Release Notes
ClearSCADA 2010 R3.1 is the first service pack release of ClearSCADA 2010 R3. This release
contains a small number of product enhancements. Its main purpose is to resolve known issues with
ClearSCADA 2010 R3 to improve performance and reliability.
Product Enhancements










The trace line width for ad hoc trends in WebX has been made configurable. This can be
done using a new setting “Line Width” in the “WebX” configuration page in the Server
Configuration utility.
The alarm bell can now be sounded on embedded alarm lists. A new configuration option
called “Sound Alarm Bell” has been added to the property page of the embedded alarm list to
control this feature.
The user specific application data that includes the “Global Settings.dat” and head specific
settings files are now copied to the Schneider Electric folder after an upgrade when ViewX is
started up.
On upgrade, the installer will now copy the keys in the
“HKEY_CURRENT_USER\Software\Serck Controls” section to the new “Schneider
Electric\ClearSCADA” registry branch.
Updated Crystal Reports runtime to "Crystal Reports for Visual Studio 2010 (.NET Framework
4.0)" SP4 (from SP3).
A new method “SetCustomFields” has been added to the Event Journal aggregate on the
Root Group to allow multiple fields to be set.
Added support for translating database fields of type 'array of string' in addition to existing
support for 'string' fields, using the string dictionaries.
Added Historic capabilities to SEW310 Points, including activation 'Report' reason and OPCHDA interfaces.
Added support for SEW310 32 Bit Unsigned Counter in SVP which is included in the W310
firmware v6.50. This also includes backward compatibility of W310 firmware V6.03 (requires
'Install SMS' to advise ClearSCADA of SWVersion).
Added “ListObjectFlat” method to DB Server API, to list all of the objects in a class.
OPC Driver Improvements



OPC driver requests will now time out after a configurable interval. Two new fields have been
added to the OPC Server object configuration form for controlling active request timeouts –
one for control requests and another for refresh requests.
Queued request timeouts are controlled by the “Request Timeout” field in the “Drivers”
configuration page in the Server Configuration utility.
The “Refresh Type” that the OPC driver uses when issuing refresh requests has been made
configurable on the OPC Server database object form.
CFX Export Improvements


An option has been added to the “Export to CFX..” method dialog that allows the user to
select whether daily data is included in the exported.
Also added an option to the “Export to CFX..” method dialog that lets the user choose the
“Hourly History Type” – whether ‘one record per hour’ or ‘partial hour records’.
ClearSCADA 2010 R3.1 Release Notes
Page 2 of 7
Database Manager Improvements





A warning text has been added to the Database Manager to indicate that each server
instance requires a separate license.
An End User License Agreement has been added to the Database Manager and will display
on a separate screen.
The additional database instances added using the Database Manager utility will now display
as “ClearSCADA Server”.
Improved the warning message that is displayed when the user tries to remove a database
instance from the Database Manager.
The file locations for Configuration Changes, Data folders, Exception Dump files and
Configuration files has been corrected for newly added database instances.
Resolved Issues
Advanced Drivers

Prevented a possible crash in Advanced Drivers processes that occurred if objects
referencing common resource objects (e.g. Time Profiles, DynacardStores) are taken out of
service, deleted or reconfigured so they reference different common resources or the
common resource is deleted.
Schneider Electric Wade310


The SEW310 Channel's “ScannerSMS” process has been strengthened to avoid stalling of
channel's comms with modem.
Failure Event now logged by SEW310 Outstation for SMS Messages that fail to parse.
SCADAPack Modbus




Fixed a crash which occurred in the SCADAPack Modbus Extension driver when duplicate
DLOG IDs where detected.
Corrections to the Lufkin SAMS driver.
o The timestamp is correctly updated on Lufkin points when the address changes to
ensure the correct point is invalided should there be a duplicate address.
o Changed the term Dynagraph to Dynacard throughout.
o Changed digital point tab to 'Digital Point'.
Fixed Advanced Modbus DLOG Scan Rate not updating to latest saved configuration
The Advanced Modbus driver has been corrected to ensure a Refresh will always start at the
beginning of the poll sequence for Modbus/TCP outstations.
E-Series

Fixed the 'Display Points' query on SCADAPack E-Series I/O and remote outstations so that
the correct fields are included in the SQL query based on the enabled features (and to match
a 'standard' point list). Specifically, included 'CurrentMSStateDesc' when M/S alarm limits are
enabled (and 'CurrentStateDesc' when disabled), and 'QualityClassDesc' when point quality
ClearSCADA 2010 R3.1 Release Notes
Page 3 of 7

classification is enabled. Also corrected the label for the query to display pulse actions (to
match 'standard' query).
DNP3 SCADAPack System Derived Analog and Binary Points now have AltPointTypes.
IEC60870






Corrected calculation of absolute time when processing hourly range timestamps after having
received a spontaneous time update. The year was being calculated as year 40xx.
Corrected operation of the master when the channel is configured to use Local time with
daylight saving adjustment. The master driver could get stuck sending set clock commands
continuously.
Stopped the master driver from flagging the outstation as ‘healthy’ on receiving a link reset
command. This prevents the outstation going healthy and then failing again if the initial
general interrogation fails.
The 101 balanced slave has been modified so that it tries to initiate communications.
Previously it waited for a message from the master station.
Changed the retry of ‘set clock’ so that the time sent in the packet is correct for the time the
message is sent.
Raised protocol alarm if IEC6070-5-101 secondary layer detects a retry message that does
not match the original message sent.
TMX



Fixed the TMX outstation set 'One Shot' and 'Promoted Dial Out' methods which were broken
following the addition of the ‘one type’ argument to the outstation ‘One Shot’ method.
A new registry setting
"HKLM\SOFTWARE\Schneider Electric\ClearSCADA\DriverTMX\OneShotType" DWORD
(0 = all data, 1 = logged only, 2 = current only) determines what type of ‘One Shot’ is
performed by a set.
Fixed a TMX driver crash that could occur if the driver received a message with an invalid
length from the line unit. All valid TMX messages have a length of at least 6 bytes (plus 2 byte
checksum) and all shorter messages are now rejected.
After an online session to a TMX outstation ends, the line unit transmits a 'ready' message to
indicate that it’s ready to process further commands. However, if the line unit is reset after the
online session ends but before the 'ready' message is sent, the channel in the driver got stuck
(waiting for 'ready' message). This typically occurred with faulty line units where instead of
transmitting the 'ready' message it transmits a continuous stream of random bytes, requiring a
reset to restore the line unit to normal operation. Ensured that the line is dropped and channel
returns to ‘healthy’ (from ‘active’) if a ‘reset’ message is received from the line unit whilst
waiting for ‘ready’ message.
Simple Drivers

Corrected the order of parameters in the “Export to CFX..” method dialog to allow for the
unused filename parameter (when using Default Filename).
ClearSCADA 2010 R3.1 Release Notes
Page 4 of 7

Ensured that when a Scanner is deleted, any pending transactions for that scanner are also
deleted.
ViewX












Fixed a problem with tooltips flickering and causing drawing glitches in the Pick Action
Configuration Wizard.
The tooltip description on methods in the Pick Action Configuration Wizard has been
corrected to display the text properly.
Fixed a memory leak and increase in “GDI Objects” in ViewX when a mimic that contains a
list and broken reference is displayed.
A ViewX crash that occurred when debugging a logic program with the Variables window
displayed has been fixed.
Fixed a mimic load bug that could result in a ViewX crash or memory leak under certain error
conditions.
Fixed value formatting so that units are not appended if the format type is "Interval".
The “Line Style” property has been made configurable for traces with Style set to “Bar”.
Fixed a crash that could occur when simplifying polylines on mimics.
Fixed a memory leak when displaying Crystal reports in ViewX.
Fixed a crash that occurred when displaying the mimic properties dialog on operating systems
where the "Properties" string isn't translated into the default language of the operating
system.
A ViewX crash when selecting “Display Events” from an embedded alarm list has been fixed.
Fixed a bug that caused OPCAE links to be left behind after the user closes the Alarm Filter
Dialog.
Server



A server exception that occurred when “Historic Files” option is enabled while the server is
running has been fixed.
Fixed an exception that occurred when modifying Reference metadata fields when those
reference fields are displayed on property forms.
Fixed an exception that could occur if a client closed a connection to the server during a logon
whilst waiting for Windows/LDAP to authenticate password.
Redundancy



A bug has been fixed which prevented upgrading to a newer minor version (e.g. 69 to 72) if
the build number was older. This bug would prevent the upgraded standby server from
synchronising with the older main.
Events will now be to the standby server when alarms and events are disabled.
Fixed a standby server exception that occurred when “Alarms and Events” are enabled
/disabled.
ClearSCADA 2010 R3.1 Release Notes
Page 5 of 7
Alarm Handling



Fixed the permissions on the “Accepted” database field in the CAlarm table so it checks
'Accept Alarm' if the field is set to True and 'Unaccept Alarm' if setting the field to False.
Fixed various inconsistencies in alarm banner and list filter indication:
o Banner filter indicator was missing when starting up ViewX as guest (and guest user
had default alarm filter string).
o Bringing up the Options dialog or editing extra alarm columns caused the incorrect
filter to be applied /indicated in cases where the user had actively removed any
default filter.
o The user's default alarm filter clauses were not consistently applied before and after
using the alarm filter dialog to edit an embedded alarm list's filter string, resulting in
inconsistencies in the alarms actually displayed.
o The guest user was being created with explicit “Assigned” and “AlarmState” clauses
in his default alarm filter string, which was unnecessary and confusing.
Ensured alarms are not filtered by AOI when Area of Interest feature is disabled.
Miscellaneous














Added missing 'ClearSCADA.Core.pdb' and 'ClearSCADA.Client.pdb' files to the Core SDK.
Also added the debug versions of the 'ClearSCADA.Core.*' and 'ClearSCADA.Client.*' files to
the Core SDK.
Included abbreviated Czech month names instead of month numbers.
Fixed a memory leak in the server when displaying an alarm list over WebX where one of the
alarms had a response set.
When an exception occurs a zip file is generated containing the dump file and log files.
Ensured that log files are added to the zip if the filenames contain a dot (other than the dot for
the extension).
Improved the error message displayed when the keyword “PROGRAM” is entered in a
Structured Text Library.
Fixed the 'Enable' argument of “PropertyOverride” automation method and the “Recurse”
argument to the “SetSecurity” automation method so that value 'True' /’False’ is accepted.
Fixed the mounting of archive volumes containing historic data (raw or suppression).
Previously it was trying to insert raw files into suppression data and vice versa. Also, it
miscalculated the number of records in each suppression data file.
Fixed the releasing of database lock when archiving of event journal and configuration
changes so that it doesn't timeout and doesn't cause crash if granules are deleted whilst the
lock is released.
Fixed the formatting of dates, times and numbers when current locale uses a decimal point
separator other than dot (e.g. French uses comma). This only affected some third party
products, and not ClearSCADA itself.
Improved accumulators so that they are only reset if the report and reset configuration
change.
Fixed server crash when executing an SQL query using the “TOP PERCENT” clause and the
number of records is a fraction less than one. Also, changed the behaviour of “TOP
PERCENT” to round up, rather than down, when the number of records is a fraction. This now
matches Microsoft SQL Server's behaviour.
When using Windows authentication to logon, ensured that passwords aren't cached when
caching is disabled (cache time = zero). Previously passwords were cached but expired
immediately.
Fixed OPC Time dialog so that 'NOW' generates a sensible time for Offset fields.
Server configuration tool fixes to point quality classification and PSTN connection types:
ClearSCADA 2010 R3.1 Release Notes
Page 6 of 7
o
o
o
When a quality that is being used (by one or more points) is deleted it is added to an
internal list of deleted qualities. This list is then copied to a 'master' list of all deleted
qualities when changing page or applying changes. Apply changes uses the master
list to actually delete the qualities from the database, however items were never
removed from the master list so every time changes were applied it tried to delete the
same qualities again. This could delete a new quality with the same ID as one
previously deleted. When a new quality is allocated an ID the list control was not
updated to store the ID, preventing the new quality from being modified or deleted
until the user changed to a different page and then back again (which rebuilds the list
control).
When a PSTN connection type is changed or deleted it is added to an internal list of
either changed or deleted connection types. These had the same problem as
qualities above.
Deleting a changed, but not yet applied, connection type after changing to a different
page (and back again) didn't remove the connection type from the list of changed
connection types, as it only checked for changed connection types since the page
was opened.
ClearSCADA 2010 R3.1 Release Notes
Page 7 of 7