ClearSCADA 2009 R1.1 Release Notes

[sbeadle1]

📖 Home  Back  

Product Enhancements

• The Pager Driver has been modified to recognize responses from modems in the format CMEE(0,1,2). The Pager Driver has also been extended to support the more complex ranges such as (0-1,2-4,5,6,9,23-78,99). Such a response/range would result in the modem being set to the highest error reporting level we support - which remains as '2' (verbose).

Resolved Issues

• The ODBC Driver in ClearSCADA has been modified to release socket connections used when external applications connect to the database using ODBC.

• NOTE: This issue can cause any system running Crystal reports or external ODBC applications to fail when all available sockets on the machine are exhausted.

• It is recommended that all users upgrade to ClearSCADA 2009 R1.1 to resolve this problem.

• ClearSCADA 2009 R1 installed on the Finnish version of Windows would not allow Crystal Reports to be consecutively generated. This problem has been fixed and this Service Pack will allow users to generate the reports without any problems.

• The section "User Contact Details" in the Server Configuration Tool that allowed specific fields of a user object in the database to be renamed, has been removed in ClearSCADA 2009. This functionality was not compatible with the new approach to defining Extra Configuration and Data fields. Please follow the steps provided in the ClearSCADA 2009 R1.1 Known Issues page when upgrading a database containing fields that have been renamed this way.

Advanced Drivers

• A change has been made to stop the advanced driver from exiting during the start-up phase if errors are returned when reading database objects. This could occur if the object was deleted after the driver had enumerated the database objects it was interested in, but some of the objects were subsequently deleted. The driver now discards the reference to the object and continues which matches the behaviour of the driver when it is running.

• DNP3 Driver

• The DNP3 driver has been modified to ensure that if a request fails whilst a request for another outstation is in progress, then it will correctly reset the outstation state engine.

• The DNP3 Drivers' "Start communications" process was not handling receiving an invalid data link only message correctly. It has now been corrected to re-start the re-establishment timer on receipt of such an invalid message.

• The configuration validation of DNP3 Slave Outstation objects has been modified to ensure that an invalid address will not report an error when it is in a template.

• The DNP3 eNET driver has been modified to correctly issue controls to an eNET output point when the DNP Object Type is an Input group.

• SCADAPack E-Series DNP3 extension driver has been corrected to ensure that user derived output points (e.g. SCADAPack E-Series analogue output with a point type of User (Derived)) will accept DNP3 events using input group and variations.

• SCADAPack Modbus Driver

• The Scan Groups for SCADAPack Modbus Analog Points are now only evaluated at the start of the poll (the same as Retrieval Intervals) so that they no longer result in prolonged polls where the same point is recovered time and again because it has a very short Scan Group configured.

• An infinite loop which could occur in the SCADAPack Modbus database module if an invalid bit count (on a SCADAPack Digital Point) is configured (e.g. through automation interface) when DLOG is enabled has been fixed.

Go: Home Back