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 older versions, please select from the following pages:

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.

  2013 R2 Client 2013 R2.1 Client 2013 R2.2 Client 2014 R1 Client 2014 R1.1 Client 2015 R1 Client 2015 R1.1 Client 2015 R2 Client 2017 Client 2017 R2 Client
2013 R2 Server



2013 R2.1 Server



2013 R2.2 Server








2014 R1 Server




2014 R1.1 Server




2015 R1 Server




2015 R1.1 Server









2015 R2 Server









2017 Server









2017 Server R2










For cases marked by a (?) , these configurations are not verified during the testing of the release. We recommend either a staged step-by-step upgrade or thorough testing in an offline environment.

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. If you do not use Server Emulation to advise clients of the server's object versions to save, then it will be possible for later version clients to save mimics and other objects which are then not compatible with the older clients communicating to that server. 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.

  2013 R2 Sby 2013 R2.1 Sby 2013 R2.2 Sby 2014 R1 Sby 2014 R1.1 Sby 2015 R1 Sby 2015 R1.1 Sby 2015 R2 Sby 2017 Stby 2017 R2 Stby
2013 R2 Main






2013 R2.1 Main






2013 R2.2 Main









2014 R1 Main






2014 R1.1 Main







2015 R1 Main






2015 R1.1 Main









2015 R2 Main










2017 Main









2017 R2 Main









For cases marked by a (?) , these configurations are not verified during the testing of the release. We recommend either a staged step-by-step upgrade or thorough testing in an offline environment.

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 an upgraded 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.