ClearSCADA Version Compatibility Matrix (2010R1 - 2014R1)

[sbeadle1]

📖 Home  Back  
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 older versions, please refer to the ClearSCADA Version Compatibility Matrix (2005R0 - 2010R1).
For information on client-server and server-server compatibility for newer versions, please refer to 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.

	2010 R1 Client	2010 R1.1 Client	2010 R1.2 Client	2010 R2 Client	2010 R2.1 Client	2010 R2.2 Client	2010 R3 Client	2010 R3.1 Client	2013 R1 Client	2013 R1.1 Client	2013 R1.1a Client	2013 R1.2 Client	2013 R2 Client	2013 R2.1 Client	2013 R2.2 Client	2014 R1 Client	2014 R1.1 Client
2010 R1 Server	✅	✅	✅	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R1.1 Server	✅	✅	✅	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R1.2 Server	✅	✅	✅	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R2 Server	✅	✅	✅	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R2.1 Server	✅ *	✅ *	✅ *	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R2.2 Server	✅ *	✅ *	✅ *	✅	✅	✅	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅ ✰	✅   ✰	❌	❌
2010 R3 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌
2010 R3.1 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	✅	✅	❌	❌
2013 R1 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	❌	❌
2013 R1.1 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	❌	❌
2013 R1.1a Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	❌	❌
2013 R1.2 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	✅	✅	✅	✅	❌	❌
2013 R2 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	❌	❌
2013 R2.1 Server	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅ *	✅	✅	✅	❌	❌
2013 R2.2 Server	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅   *	✅	✅	✅	❌	❌
2014 R1 Server	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2014 R1 Server	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅

For cases marked by a ⚠ , the checkbox in the Server Configuration->System Configuration->Security->Allow Insecure Connections, needs to be enabled. This setting was added to prevent client connections that do not support checksum and transaction IDs from connecting to the server that supports them.

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

For the cases marked by a ✰ , method pick actions will not work. Please refer to the Known Issues page of the release for more information.

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.

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.

	2010 R1 Sby	2010 R1.1 Sby	2010 R1.2 Sby	2010 R2 Sby	2010 R2.1 Sby	2010 R2.2 Sby	2010 R3 Sby	2010 R3.1 Sby	2013 R1 Sby	2013 R1.1 Sby	2013 R1.1a Sby	2013 R1.2 Sby	2013 R2 Sby	2013 R2.1 Sby	2013 R2.2 Sby	2014 R1 Sby	2014 R1.1 Sby
2010 R1 Main	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R1.1 Main	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R1.2 Main	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R2 Main	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R2.1 Main	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R2.2 Main	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R3 Main	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2010 R3.1 Main	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
2013 R1 Main	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅	✅
2013 R1.1 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅	✅
2013 R1.1a Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅	✅
2013 R1.2 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅	✅
2013 R2 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅	✅
2013 R2.1 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅	✅
2013 R2.2 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅	✅
2014 R1 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅	✅
2014 R1.1 Main	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	❌	✅

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


Go: Home Back