ClearSCADA 2007 R0.2 Release Notes

[Anonymous user]

📖 Home  Back  
ClearSCADA 2007 Edition (Release 0.2) is the second service pack for ClearSCADA 2007 R0. This build contains some specific bug fixes and few product enhancements to improve performance and efficiency of the server.

Product Enhancements

• Support has been added for permanent standby servers with more than 14 characters in the node name.

• The Server Configuration Tool has been modified to

• connect to servers with the same major and minor versions.

• connect to servers that are in the Starting state.

• connect to servers running in Emulation mode.

• Improved DriverOPC diagnostic logging to provide timing information on OPC read/write operations.

• Event filtering has been modified to not send alarms or events with zero priority. This achieves a further reduction in events processed when a user takes or released exclusive control.

• Logic execution will now mark a program with invalid opcodes as failed.

• Server links have been modified to reclaim memory after a large request has been processed.

• Prevented server advise links from eventually using up all memory in the server when a client enters sleep mode.

• The Print and Print Preview options have been removed from value maps. Previously they did nothing.

Resolved Issues

Simple Drivers

• OPC Driver:

• The OPC DA client driver (DriverOPC) has been corrected to pass an empty string for the AccessPath parameter of each tag. Previously the

driver passed a NULL pointer, which caused operation with some OPC DA servers to fail.

• A potential server crash if the total number of OPC DA groups created exceeded 9999 has been fixed.

• Fixed the OPC Client driver (DriverOPC) to complete synchronous Refresh transactions requested from OPC Scanners.

• Fixed a potential server crash that could occur when a client attempts to create an OPC DA group with the server under extreme

loading.

• Fixed OPC HDA Total and Time Average calculations to report the correct values when the underlying raw data is not aligned on the second

boundary.

• Modbus Driver:

• The server exception that occurred when displaying the View dialog of a modbus scanner, if the channel was currently switched to the secondary

channel and was then been reconfigured to have no second port has been fixed.

• Fixed a problem where correctly configured Modbus points would not update and report bad quality. This problem occurred if the Modbus driver was

scanning a slave device via TCP, and the configured scan period was greater than the slave device timeout.

• The Telnet monitoring facility has been restored to simple driver log files.

• The server exception that occurred when displaying the View dialog of a Modbus scanner, if the channel was currently switched to the secondary

channel and was then been reconfigured to have no second port has been fixed.

• Fixed a potential simple driver crash if badly formed requests are sent to the browse interface of a simple driver.

• Fixed a simple driver issue where controls could get delayed if one or more severs were off-line. This issue only affected simple drivers using

software connections, e.g. OPC, ODBC or Modbus/TCP.

Advanced Drivers

• DNP3 Driver:

• The DNP3 eNET Configuration download has been corrected to send the correct network configuration parameters.

• The DNP3 driver has been improved to correctly handle comms being present on the dormant channel. The driver will no longer get stuck should this happen.

• Fixed eNET outstation's DNP3 and eNET point indices so that changing the number of bits on an eNET binary point and also changing either the point type or DNP object type (but not both) at the same type doesn't corrupt one of the indices. Changed the 'Foreign Keys' integrity check which was reporting false errors for DNP3 outstation's point index, for all 2-bit and 3-bit binary points.

• SCADAPack modbus Driver:

• Corrected point conversions to RealFLO analogue inputs to ensure it correctly copes with 6-digit addressing and other issues.

• 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.

• Fixed crash in SNMP Manager Driver which occurred when read an object of type IP Address. The formatting of IP Address values has also been modified so that something sensible is displayed.

• The pager driver has been modified to ensure it cannot attempt to shut down a channel thread twice. This could occur when the driver was shutting down but still sending a message.

• Fixed the rounding down (to the nearest whole inch) of the Crystal Report page margins when printing a report on the server.

• TMX Driver:

• Ensured that manual control requests to a TMX outstation are not queued behind pending lower priority scheduled requests (e.g. one shot) whilst waiting to start an online session.

• Allowed constants to be controlled during an online session to a TMX outstation. Previously constant controls issued whilst online were queued until the online session was stopped.

• Corrected text configuration (names, units and state descriptions) download to TMX outstations to ensure that each string is NULL terminated if it has to be truncated (because it is too long) to fit into the message. Without the NULL terminator the outstation doesn't display the text correctly on its local display.

• During an online session to a TMX outstation the line unit (LU) may force the session to end by sending a 'ready' message. When this occurred the channel's scanner became stuck waiting for a 'ready' message, which has already been received. Ensured that the driver drops the line straight away when this situation occurs. Fixed the TMX comms log translator to handle transition from online protocol back to the standard protocol when the switch is caused by the LU sending a 'ready' (or 'info' for SEAL090) message, rather than an end online request.

Query Processor

• Fixed a potential server crash that could occur when a connection is closed whilst an SQL query is still being processed on the connection.

• SQL queries will return the correct rows when ODBC scalar functions are used in the WHERE clause.

• Fixed the SQL query processor to ensure column aliases are assigned to the correct column.

• Fixed SQL UPDATE commands to correctly propagate changes to aggregate fields to instances.

Miscellaneous

• 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.

• Prevented unauthorised system access to users in the web client.

• Fixed issues with dynamic position animations in ViewXCtrl.

• Fixed issue with standard method dialog in both ViewX and ViewXCtrl, 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.

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

• Fixed server advise stall checks so that it does not erroneously fail the link if a new event is created more than two minutes after the last event and the stall checks kick in before the new event can be processed. This could cause drivers to be incorrectly restarted.

• Fixed client communications library DBClient.dll to only register the hidden window once. This fix avoids communication problems that occur when the Windows function RegisterClassEx() returns unexpected error codes for 2nd and subsequent registrations of the hidden window.

• Fixed problem with ViewX toolbar state in user profile somehow becoming corrupt, causing each log on to take longer than the last.

• Fixed a potential server crash when importing logic programs configured with a "Trigger" tag.

• Fixed occasional DBServer lock-up when changing log file paths.

• Fixed possible server crash when generating the "General Memory Usage" section of the snapshot log file.

• Fixed a potential crash in the Server Configuration tool when collapsing the tree in the left hand pane following a registry modification.

• Fixed the alarm list in both ViewX and WebX to sort the category field alphabetically.

• Fixed the ViewX method dialogue to display the correct value of single precision floating point numbers. Previously single precision floating point numbers containing fractions would be displayed with an excessive number of decimal places.

• Fixed clear user password dictionary method to propagate the cleared dictionary to standby servers.

• Fixed spin control in mimic Rotate Other dialog to cope with negative numbers properly. Modified range of spin control to Internal:-360.0, 360.0.

• Fixed ViewXCtrl crash/lock-up when accepting etc. an alarm with comment and the alarm is removed from the list (e.g. cleared) while the comment dialog is on display.

• Fixed server crash which occurs if an analogue point is configured with too many master-station alarm limits (more than 18).

• Fixed ST parse error when parsing expressions where there were no spaces between an additive operator and a constant value.

• Fixed ViewX crash when using an automatic logarithmic Y Axis on a trend to display digital data.

• Fixed infinite loop in Script editor Search and Replace.

• Fixed logic REAL_TO_STRING and LREAL_TO_STRING conversions to return the correct value. Previous conversions where limited to 6 decimal places.

• Modified parsing of received e-mail to ensure Subject header is at the start of a line. Some internet mail sites (e.g. Yahoo) can insert spurious header names in another header which previously lead to some confusion.

• Fixed logic error when writing to an array field using a VECTOR with a different element type to the array.

• Fixed exclusive control to work when requested via a standby server.

• Fixed crash in logic when using the MUX function with string arguments, and the value of the K argument is invalid.

• Fix server crash when displaying a mimic in ViewXCtrl which contains a text box whose value is animated from an array.

• Fixed problem with script libraries being truncated when saved if longer than 65536 characters.

• Fixed a possible server crash if a user's password expired whilst that user was logged on.

• Fixed disabling an alarm from the alarm banner when that disable action required the user to enter a note.

• Corrected problem with template instance conversion which could partially orphan off a point if the point was not in the instance being converted but its associated outstation was.

• Fixed memory leak in ViewX that occurred when a user navigated between mimics containing large numbers of polylines.

• The server has been modified to correctly handle a web request received with an unrealistically large value in the Content-Length header field.

• Server Licensing has been modified so that drivers that are stopping when license becomes valid (e.g. dongle is attached) are started, once they complete stopping.

• Fixed a potential main server crash following execution of the Web SOAP function SetValues via a standby server.

• Fixed server overload when exclusive control is used on large areas of the database.

• Point Alarm/Event processing when releasing an override and point no longer has any data (i.e. point had not been updated prior to override) has been changed. Previously an erroneous alarm/event may have been raised/logged, depending on the configuration of 'state 0'.

• Fixed a fault in the recovery of broken advise links where callbacks could be called on the wrong thread.

• Fixed a potential server crash when animating an element of a string array where the array index is out of range.

• The Web client will now display the correct page when hyperlinking from another page and not a white box with a red X in the corner.

• Alarm clients have been changed so that if an active alarm changes and should no longer be visible to a client (e.g. priority changed by a redirection action and client has a priority filter), the alarm is now correctly removed from the client.

• The server crash that occurred when displaying a trend with a state Y-axis with an empty system name in WebX has been fixed.

Previous Versions

• Click here for Release Notes from ClearSCADA 2007 R0.1.

• For Release Notes from earlier versions of the product, please refer to the Release Notes pages that can be found in the ClearSCADA Knowledge Base which is available on the Control Microsystems web site.

Go: Home Back