Ergonomics of Sustainability, Innovation & Continuous Integration (Part 3)

In the previous blog articles we looked at the information that is essential to understand before initiating any upgrade sequence with zenon. In this article, we will look more closely at the specifics of updating a standalone system.

As a reminder, these are the possible zenon network types:

  • Standalone (single PC, no zenon network active)
  • Client – Server (single server)
  • Client – Server (redundant server)
  • Client – Server (circular-redundant server)

In our first example, we are going to upgrade a standalone system with one zenon project running from a zenon 7.20 system to zenon 7.50.

Step 1: Read back or import the Runtime project files in the Editor project in the old 7.20 version. Make sure that in the Editor for the current version of the project the settings for “RT changeable data” concerning de-compilation settings are set correctly.

Step 2: Create a Project or Workspace backup in the current 7.20 version.

Step 3: Install the zenon Editor of the new 7.50 version on the Engineering PC. Now both zenon Editor versions, 7.20 and 7.50, are installed and can be used (by starting them through the zenon Startup Tool).

Step 4: Upgrade the standalone Runtime.

Stop the Runtime and install the new version of the Runtime. Hint: Installation without demo projects is advisable.
Now both zenon Runtime versions – 7.20 and 7.50 – are installed on the PC. In the worst case scenario, you can always go back to using the 7.20 Runtime.
Following successful installation of the new Runtime, start it.

Hint: The installation changes the paths for the Runtime start. StartupTool: Enter the path to your project in the StartUpTool for the new 7.50 entry.
zenon Remote Transport: Retransmit the project and reset the start project on each client PC before restarting.
Now the Runtime of version 7.50 is executing the zenon project from version 7.20.

zenon_product_version_connectivity_-10You can now choose to follow steps 5a or 5b.

Step 5a: On the engineering PC, start the new version of the Editor. Compile the Runtime project files for the new version. Remote Transport the Runtime project files for the new version to the Runtime PC and reload the project.

Step 5b: You achieve the same result if you transfer the new Runtime project files to the Runtime PC before starting the Runtime of the new version. In this example, I would rate this as the preferable sequence.

It is up to you what sequence to use, I am simply outlining the possibilities here. This gives you the flexibility to plan your upgrade process according to your own needs.

Downtime lasts, in this example, for the duration of the installation of the new zenon Runtime and its subsequent start.

Upgrade Engineering PC only:

Perhaps you don’t want to upgrade the Runtime; you would prefer to continue to run it in version 7.20? No problem! You can do this by updating only the Engineering PC.

In the process described above, leave out Step 4 and do not install the Runtime of the new version.

Instead, on the engineering PC, start the new version of the Editor, compile the Runtime project files for zenon 7.20 and use it for the Runtime running in version 7.20.

Advantage:

  1. You can still serve older Runtimes with Runtime project files of its version where there is no need to use zenon’s latest features.
  2. At the same time, with the same Editor, you can create new projects using the new version and benefit from zenon’s latest developments and features.

zenon is flexible: it is up to you what sequence you use. Do it your way.

In the next blog post, we will have a look at a client-server system and how the upgrade proces s works there.

Tags: , , , ,

Leave a Reply