ClearSCADA 2007 R0.1 Release Notes

[Anonymous user]

📖 Home  Back  
ClearSCADA 2007 R0.1 is a service pack for ClearSCADA 2007 R0. This build does not contain any major new features, but is released to provide bug fixes and minor enhancements to existing functionality. It is recommended that all users of ClearSCADA 2007 install this build.

SCADAPack Modbus Driver Enhancements

• The last poll time on SCADAPack Modbus outstations is now updated after a Refresh request.

• Added master station persistence to SCADAPack Modbus points.

• Corrected processing of coil (0X references) and input (1X references) statuses for multi-bit (2 and 3 bit) digital points if the value crossed a byte boundary.

• Improved point address validation for SCADAPack Modbus points.

• Ensured that 'DLOG only' field on Digital Output points form is greyed out.

• Modified outstation address validation so that it does not report an error when a value of zero is used on an outstation that is contained within a template.

• Persistence fields of states 2 to 7 on SCADAPack Modbus digital points are now correctly enabled or disabled based on the bit count.

RealFLO Driver Enhancements

• Fixed various crashes in the RealFLO database module and driver.

• Corrected the combo box filter for Item field on RealFLO analog input points to correctly allow Differential Pressure when flow calculation is V-Cone and Source is Input.

• Updated RealFLO analog input points to allow 6-digit addressing.

• Ensured that RealFLO analog input point addresses are updated if the outstation is changed (on flow run) and the point address range is different.

DNP3 Driver Enhancements

• Corrected the DNP3 driver so that it does not use the configurable packet size limits (server configuration) for received packets but only uses them for transmitted messages.

• The last poll time on DNP3 outstations is now updated after a Refresh request.

• Fixed the client only installation of ClearSCADA to allow editing of eNET/SCADAPackES route tables.

• Improvements to IIN Status bits reporting. The driver now correctly uses the configured IIN severity for the Reset bit, function code not implemented, object unknown and out of range. An event will now be correctly logged for device trouble (abnormal), configuration corrupt, device busy (already executing) and event buffer overflow if the IIN Severity is configured for event only.

• Corrected the Reset Outstation method for DNP3 outstations to better handle scanner command timeouts.

• Corrected point processing in the driver if a class event was received for a point during an integrity poll which changed the quality. The class event would update the current value but the value would be updated a second time when the static data was processed.

• Corrected DNP3 eNET shared outstations so the correct DNP3 master address (from the shared set) is downloaded.

• Corrected DNP3 slave unsolicited message generation so that the ClassNMinEvents properties are used as per their description (i.e. when minimum number of events have been reached (equal to) it will trigger rather than greater than).

• Improved management of the poll timer settings to ensure that changes are applied immediately to the driver.

SCADAPackES Configuration Download Enhancements

• Corrected the minute part of the time zone offset so that it is downloaded as a fraction between 0 and 1 (not 0 to 0.6).

• Corrected the time zone offset calculation when using master station locale information where the server is in a time zone ahead of UTC and has a non-whole hour offset.

• Corrected the manually entered local time zone offset so that negative offsets can be entered.

• Corrected the field display name values for SCADAPackES ports 1, 2 and 3 fields on SCADAPackES outstations to indicate the correct port and not port 0.

Kingfisher Driver Enhancements

• Improved management of communications establishment retries.

• Improved the management of logged/event data that is received with a timestamp in the future.

• Ensured that changing the parent outstation for a Kingfisher remote outstation is handled correctly by the driver.

• Corrected the driver to ensure that it correctly applies the "Never Read Remote Directly" and "PSTN" options for Kingfisher remote outstations.

• Added option to Kingfisher outstations to allow out of sequence event log data to be processed, which may occur if the RTU clock is changed. This may result in duplicate historic entries when enabled.

TMX Driver Enhancements

• Improved PSTN call management.

• Changed TMX configuration mismatch report so that it doesn't check 'IO card type' and 'IO card number' when they are not applicable to the sensor type.

• Improved TMX channel management.

• Changed descriptions of line unit types on TMX channel form, to reflect Kuipers newer way of describing them: - Data and Speech (Single) - Speech Only (Dual Right) - Data Only (Dual Left).

• Improved the scaling of analog point alarm limits.

• Improved management of configuration download to the outstation.

• Improved handling of outstation location codes.

Logic Enhancements

• Fixed a potential server lock up when a user attempts to debug an ST program that executes a query referencing a data grid.

• Fixed a potential server crash when a user attempts to execute an ST program with more than 15 VAR_INPUT variables declared.

• Fixed a ViewX crash when a user attempts to add an array tag to an FBD.

• Fixed infinite loop in 'Replace All' in ST/script editor, when the replace text includes the search text.

• Fixed a ViewX crash when saving a logic program in a template with an instance of the program also open with the variables window on display.

• Fixed the ViewX Client to allow editing of Logic Function Block Diagrams when connected to ClearSCADA 2005 servers.

• Fixed a potential server deadlock that could occur if an extended SQL query was executed from a logic program. The deadlock would occur if

• logic program A used a method call to trigger the execution of logic program B, and

• logic program B executed an SQL query on the database, which was sufficiently long for the query to relinquish the database lock, and

• whilst program B had relinquished the database lock, a driver updated a point in the database.

This problem has been fixed by preventing SQL queries relinquishing the database lock if they are executed from logic. SQL queries requested from client connections or web requests will still relinquish the database lock as per usual.
This means that logic programs executing SQL have the potential to lock the server for an extended period, and this should be a design consideration when developing logic programs.

Trending Enhancements

• Improved the display of trends when in Processed Summary mode and the data for a pixel contains a mix of empty and non-empty values.

• Corrected the display of Processed Historic traces that use more than one source.

• The "Reset X And Y axis to Data" menu option in the X-Y plot context menu in WebX has been corrected to "Reset X and Y Axis To Defaults". It is now only displayed when an axis is set to "Range" or "Manual".

WebX Enhancements

• Fixed a memory leak in the server when a web client is displaying an alarm list.

• Fixed the error message displayed when a user changes a password via WebX and the two new passwords do not match.

• Fixed an issue with embedded lists in WebX sending a query request for the entire result set when first displayed instead of just the visible rows.

• Fixed the Specific Time option in the Go To Time dialog in WebX trends.

• Modified the secure web server to automatically generate a new self-signed certificate if none is already present.

• Fixed visibility of the zoom box on trends with dark backgrounds in WebX.

• The duration of the time axis of an X-Y Plot displayed in the WebX client now uses the duration configured in the plot, no longer defaulting to one day.

ODBC Enhancements

• Fixed crash in the ODBC client driver if logging is enabled and the SQL statement exceeds 512 characters.

• Fixed crash in the ODBC client driver that occurred when a string point was updated with a NULL value. NULL values are now stored with uncertain quality.

• Fixed a bug where extended event journal queries that returned no data did not release the database lock. Modified all extended searches to release the database lock at the same time at the second boundary to prevent parallel queries taking up 100% CPU.

• Fixed a potential server crash and/or temporary server freeze that could occur if a single prepared SQL query on the event journal was executed repeatedly and the query had either the ID or Source column referenced in the WHERE clause.

• Fixed crash in Query Processor when executing a query with a WHERE clause with no table dependencies that evaluates to FALSE.

Other Fixes and Enhancements

• Improved alarm redirection email management for greater compatibility with SMTP servers.

• Alarm redirections from alarm action calendar and roster objects can now be aborted correctly.

• When a point is overridden, the data reported by the outstation was stored in the database, but was not previously accessible. Added fields to point database tables for overridden put aside data (see 'PutAsideXXXXX' fields). Put aside value, time, state and quality are also shown in the point view dialog.

• Fixed ViewX password change and logon dialogs to allow passwords with up to 80 characters.

Please Note!: Following upgrade all user accounts with passwords that are longer than 16 characters will no longer allow the user to log on. The passwords on these accounts will need to be reset. User accounts with passwords that are 16 characters or less are not affected by this change.

• Fixed possible server crash if too much historic data was requested by a client in a processed historic request. Historic data requests are now limited to 5,000,000 items maximum.

• Added an Unsolicited Message Timeout to advanced drivers to avoid a channel becoming 'stuck' if the first part of an unsolicited message is received by a driver and the rest of the message is not received.

• Fixed server crash that occurred if "Link read-write" logging was enabled and one or more clients used compressed connections.

• The 'Switch Location' field on shared outstations is now only selectable on outstations that support this feature.

• Improved switched set heart beating support to ensure that when a significant change is made to the configuration of the set that no outstation can become permanently stuck heart beating on a channel.

• Ensured that number of consecutive read timeouts is reset when an unsolicited message is received on a channel. This avoids communications failures based on incorrect failures of the channel.

• Added browse buttons to the scan offset fields on simple driver scanner forms.

• String points (or string variables) can now be added to a string Value Map through the automation interface.

• Improved management of connections through the automation interface.

• Fixed OPC DA Historic tags and OPC HDA calls using relative times to use the client's time zone to calculate start and end times.

• Fixed a database exception that could have occurred if a user imported a whole database export that had non-default security configured on the root group.

• Fixed integrity check failure when an OPC Server is configured with a non-blank alarm source.

• Fixed bug which could cause template objects (points) to be created within an advanced driver which in turn could have lead to a crash in the database when the points value was updated.

• Fixed a ViewX crash when using a ViewX script to modify the SQL of an embedded list.

• Non-ClearSCADA (OPC only) systems are now excluded from the system trees in the ServerConfig and ServerStatus tools.

• Fixed a server exception that occurred if an invalid request was received from a ViewX client.

• Fixed a server crash that occurred if a user converted a point from one type to another, whilst that point was being displayed by one or more trends.

• Added new option to Filtered Value Maps called "Filtered Chronological Update" to allow Value Map events to be created from new updates (i.e. timestamp is newer than last update) which meet the configured criteria (e.g. exceed sig change dead band).

• Ensured that the Enable and Disable methods on points in instances are only available where the In Service flag is property overridden.

• Enumerated items displayed in the method action dialog are now translated using the dictionary.

• Fixed DriverOpcXmlDa to support Message Body length defined by connection closure as defined in RFC 2068, section 4.4 part 5.

• Fixed driver crash if a channel is configured with a start delay and the configuration of the channel is modified during the start delay period.

• Fixed client side scripts to allow access to aggregate methods and properties when the ClearSCADA server is configured to run in server emulation mode.

• Fixed a server crash which occurred when converting a shared outstation with group slaves to a non-shared outstation type (e.g. direct).

• Fixed a problem in the pager driver which could have caused it to report an erroneous alarm when terminating the TAP session. This could occur if the TAP service sent the optional information message during the terminate sequence.

• Point states/actions displayed in the event journal when issuing controls are now translated to the logged on user's language using the dictionary.

• Modified the OpcXmlDa driver to silently re-subscribe when configured to use subscription polls and the source OPC XML DA server drops the subscription.

• Fixed a bug which could cause objects (typically points) to be created within an advanced driver which should not be (e.g. in a template, out of service etc.) which in turn could have lead to a crash in the database when the points value was updated. This affected the RealFLO driver when it queried all of the points on a flow run.

• Added context sensitive help links to Kingfisher, Pager and SNMP drivers.

• Improved the management of 'NO CARRIER' messages from modems.

• Improved PSTN call statistics when handling incoming calls from unknown outstations.

• Ensure that if an extension driver (e.g. RealFLO) has been removed/uninstalled from the product, that the server and parent driver (e.g. SCADAPack Modbus) will still start correctly and not report the parent driver has no licence or cause the parent driver to crash.

• Ensured that changing the parent outstation for an IEC60870-5 ADSU outstation (master and slave) is handled correctly by the driver.

Go: Home Back