ClearSCADA

This page provides information on version compatibility between clients and servers, as well as between servers for redundancy purposes.  Use this information during the upgrade process to determine the appropriate upgrade path for your system.
For information on client-server and server-server compatibility for newer versions, please refer to either the ClearSCADA Version Compatibility Matrix (2010R1 - 2014R1) or the ClearSCADA Version Compatibility Matrix.

Client - Server Compatibility

The following table shows ViewX client to server compatibility between different revisions of ClearSCADA. This includes major and minor releases.

In all cases, you should follow the upgrade instructions for the version to which you are upgrading.

  2005 R0 Client 2005 R1 Client 2007 R0 Client 2007 R0.1 Client 2007 R0.2 Client 2007 R1 Client 2007 R1.1 Client 2007 R1.2 Client 2007 R1.3 Client 2007 R1.4 Client 2009 R1 Client 2009 R1.1 Client 2009 R1.2 Client 2009 R1.3 Client 2009 R1.4 Client 2009 R2 Client 2009 R2.1 Client 2009 R2.2 Client 2009 R2.3 Client
2010 R1 Client 2010 R1.1 Client
2005 R0 Server
2005 R1 Server
*

2007 R0 Server
*

*


2007 R0.1 Server
*

*

*


2007 R0.2 Server
*

*

*


2007 R1 Server
*

*

*

*

*


2007 R1.1 Server
*

*

*

*

*


2007 R1.2 Server
*

*

*

*

*


2007 R1.3 Server
*

*

*

*

*

2007 R1.4 Server
*

*

*

*







2009 R1 Server
*

*

*

*

*

*

*

*

*

*


2009 R1.1 Server
*

*

*

*

*

*

*

*

*

*


2009 R1.2 Server
*

*

*

*

*

*

*

*

*

*


2009 R1.3 Server
*

*

*

*

*

*

*

*

*

*




2009 R2 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*
2009 R2.1 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*
2009 R2.2 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*
2009 R2.3 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*
2010 R1 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*
2010 R1.1 Server
*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*

*


For cases marked by a *, server emulation should be enabled on the server to ensure mimic compatibility with older clients connected to the system.

When upgrading a system with separate clients and servers, the recommended strategy is to upgrade the clients before the servers. If you must upgrade the servers first, we recommend using Server Emulation on the servers to ensure client compatibility during the upgrade process. See detailed upgrade instructions for your version.

The strategy to upgrade clients before servers was only adopted from ClearSCADA 2005 R1. Because of this, it is not possible to connect a ClearSCADA 2007 client to a ClearSCADA 2005 R0 server, because the ClearSCADA R0
server will reject connections from newer clients.





Server - Server Redundancy Compatibility

The following table shows server to server compatibility between different revisions of ClearSCADA. This includes major and minor versions as well as service packs.

  2005 R0 Sby 2005 R1 Sby 2007 R0 Sby 2007 R0.1 Sby 2007 R0.2 Sby 2007 R1 Sby 2007 R1.1 Sby 2007 R1.2 Sby 2007 R1.3 Sby 2007 R1.4 Sby
2009 R1 Sby 2009 R1.1 Sby
2009 R1.2 Sby
2009 R1.3 Sby
2009 R1.4 Sby 2009 R2 Sby 2009 R2.1 Sby 2009 R2.2 Sby 2009 R2.3 Sby
2010 R1 Sby 2010 R1.1 Sby
2005 R0 Main




2005 R1 Main



2007 R0 Main

2007 R0.1 Main


2007 R0.2 Main

2007 R1 Main

2007 R1.1 Main


2007 R1.2 Main

2007 R1.3 Main









2007 R1.4 Main









2009 R1 Main


2009 R1.1 Main









2009 R1.2 Main









2009 R1.3 Main
2009 R2 Main










2009 R2.1 Main
2009 R2.2 Main
2009 R2.3 Main
2010 R1 Main
2010 R1.1 Main
Starting in ClearSCADA 2007 R1.1, functionality was provided to allow ClearSCADA to be compatible with the previous version to allow upgrades to be performed on a Main-Standby system one server at a time i.e. to maintain system operation during the upgrade. Prior to ClearSCADA 2007 R1.1, upgrades of a Main-Standby pair of servers meant that both servers must be shutdown while the main server is upgraded.

Running a Mixed Version System

Running a system with mixed version servers is only recommended during the upgrade procedure. It is not advisable to run in a mixed version server environment for any longer than necessary.

There are various limitations to a system running a mixed version server environment. Clients connected to the standby server cannot:

  • Perform control operations such as Handdressing/Overrides etc
  • Accept/Remove/enter Alarm Responses
  • Insert/Delete/Modify Trend annotations or data
  • Insert/Delete/Modify Notes
  • Execute logic or script programs that perform write operations on database objects (eg. SetValue function in Client side scripts)
  • Set/Change Security or Colour Palette settings
  • Create/Import/Delete/Rename objects into the database
  • Enable/Disable alarms
  • Edit or save objects in the database
  • Convert objects from one type to another

If a user attempts any of these operations whilst connected to the standby server, the following message will be displayed:

Error attempting to: <Operation>
You attempted a write operation from a client connected to a Standby server, and the Standby server is running a different version of software to the Main server.
Write operations to standby servers running a different version of software to the main server are not supported.