From OpenSCADAWiki
Jump to: navigation, search
Other languages:

Main differences between version 0.9 LTS and 0.8.0 LTS are:

  1. Location of the user project data and the lack of support and the concept "OpenSCADA Project" in 0.8.0 LTS.
  2. Old DB libraries in 0.8.0 LTS.
  3. Presence of a number of modules that were earlier versions in 0.8.0 LTS and actually completely rewritten at 0.9 LTS, and therefore they are completely incompatible:
  • DAQ.DiamondBoards — completely rewritten and incompatible;
  • DAQ.ICP_DAS — completely rewritten and incompatible;
  • DAQ.AMRDevs — in fact, it can be considered new, since the first, but until the only one, a complete source appeared there after release of 0.8.0 LTS;
  • Archive.DBArch — in fact, it can be considered new and actual, since its version at release 0.8.0 LTS was little use and therefore updated with one of the updates and is currently the same with 0.9 LTS.

In all other, version 0.9 LTS can execute user projects of the version 0.8.0 LTS and you can even leave old DB libraries (item 2) if the use of new causes problems or they have changed. If you used something from item 3 then their configuration should be fully or partially modified. So, overview paragraphs 1 and 2 of these differences.

At.png Updates must be made exclusively for configurations that have been previously upgraded to the latest 0.8.0 LTS update!

The difference in the location of user projects (item 1) must be resolved, because for launching user projects, 0.8.0 LTS uses individual command line scripts such as openscada_AGLKS, openscada_demo, openscada_start and that are missing in 0.9 LTS or work somewhat differently.

At.png Resolving the differences in the location of user projects does not occur automatically, for which you need to be able to use the console, and for the upgrade and start-up you will need the superuser access.

If you do not want to completely migrate your project to a separate and special folder you can, before the update, save the project startup script and the configuration file, and then return it and continue to run the user project at 0.9 LTS, which will mostly work "AS BEFORE" .

So, in the project model of the "AGLKS" TP example and saving the folder "~/.openscada", we do:


1. Preparing and updating the current configuration
  • update OpenSCADA to the latest 0.8.0 LTS update, according to the installation method;
  • actualize the user project, you can skip for updated configurations:
  • start up the user project;
  • start up development the graphical environment;
  • change the work DB to some other, and then return it, which will mark the need to save the entire project;
  • save.
At.png This operation may come in loss of the graphical environment configuration on the not latest LTS version.
1a. [AS BEFORE] Saving the startup script and configuration file by copying to some temporary folder
  • perform the procedure:
$ cp /usr/bin/openscada_AGLKS /var/tmp
$ cp /etc/oscada_AGLKS.xml /var/tmp


2. Upgrading OpenSCADA to the new version 0.9 LTS
  • change the ordinal user to the superuser;
  • completely remove 0.8.0 LTS, which on Debian based distributions is made by the command:
$ apt-get purge openscada*
  • install 0.9 LTS, as the package "openscada-model-aglks" or other virtual that more suitable to your project; for details, see "How to install"


3. Updating and restoring the configuration
3a. [AS BEFORE] Restoring the old script, configuration and modifying the links of some folders
  • perform the procedure:
$ rm /usr/bin/openscada_AGLKS; cp /var/tmp/openscada_AGLKS /usr/bin
$ cp /var/tmp/oscada_AGLKS.xml /etc
# Leave the superuser and perform
$ ln -sf /usr/share/openscada/icons ~/.openscada/icons
3b. [PROJECT] Transferring files of the user project to a separate folder, having previously left superuser
  • call an update command that does everything you need:
$ openscada-proj update AGLKS
# For a user project with data in the folder "~/.openscada/DATA"
$ openscada-proj update MyProjectName
  • or manually and if the initial configuration is very specific:
  • gather all the project files into a separate folder, in the OpenSCADA user projects folder which is typically "~/.openscada"; although 0.8.0 LTS does not regulate or mandate doing so, this practice has already been partly applied, so there is only need to put some parts of the project there:
$ mv ~/.openscada/ARCHIVES ~/.openscada/AGLKS
$ ln -s ../LibsDB ~/.openscada/AGLKS/LibsDB
$ ln -s ./ ~/.openscada/AGLKS/AGLKS
  • use the configuration file of the typical project of OpenSCADA 0.9 LTS, since the old one does not fit here and all the main configurations are stored in the main database:
$ cp /etc/oscada_start.xml ~/.openscada/AGLKS/oscada.xml
  • rename the main database file in "St.db" if it is not, because it is exactly that written in the configuration file;
  • replace old library databases or we can leave them if you have changed something there:
$ cp -R /usr/share/openscada/LibsDB/*.db ~/.openscada/LibsDB


4. Starting
  • [AS BEFORE] run the old script.
  • [PROJECT] run the updated project, even selecting into the project manager.


5. Differences and desired changes to the received update
  • [PROJECT] Reduce the address to the local database files of the project that looks like "./AGLKS/Model.db" and can be shortened to "Model.db."
  • Project of the visualization:
  • the reporter was completely rewritten, therefore on the main page of your project must be foreseen attributes of description of desirable reporters and the typical values can be obtained from the template project, of course if the libraries have been updated;
  • properties of the visualization project for controlling the parameters of the runtime window are predominantly moved to separate attributes of the home page and which, accordingly, need to be defined.